dbTalk Databases Forums  

Lost tail-end of reports through Specialix SX on Windows NT 4

comp.databases.pick comp.databases.pick


Discuss Lost tail-end of reports through Specialix SX on Windows NT 4 in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Steve
 
Posts: n/a

Default Lost tail-end of reports through Specialix SX on Windows NT 4 - 05-18-2006 , 10:19 AM






Hello

I am trying to fix a problem that has existed for ages, since the Specialix
SX 8-port unit was installed ages ago. We've worked around the problem in
the past but I now need to get it fixed!

The problem doesn't appear to be handshaking, in that all report contents
are fine, irrespective of the length of the report. It's just when we reach
the tail end of the report, that it will miss off part of the last line and
the form-feed character.

It's a Specialix SX box, connected to a host card in Windows NT. I've tried
various baud rates and checked the protocol etc.

There are a great number of similar problems with Specialix, posted in
various Unix groups, but I can't see a solution.

Does anyone here have experience of this?




Reply With Quote
  #2  
Old   
Ed Sheehan
 
Posts: n/a

Default Re: Lost tail-end of reports through Specialix SX on Windows NT 4 - 05-18-2006 , 10:28 AM






You'll probably get more specific help on this, but at first glance it looks
like the serial port isn't flushing its buffer, causing the report to
truncate the last n characters, 'n' being the size of the buffer.

Possibly a jumper or configuration setting.

A second possibility comes to mind: flow control. There may be a setting
which defines/sets the xoff character. Perhaps it's set to the FF character?

Something to do until an expert on the Specialix responds...

Ed

"Steve" <ffskf (AT) jhre8329r32 (DOT) com> wrote

Quote:
Hello

I am trying to fix a problem that has existed for ages, since the
Specialix
SX 8-port unit was installed ages ago. We've worked around the problem in
the past but I now need to get it fixed!

The problem doesn't appear to be handshaking, in that all report contents
are fine, irrespective of the length of the report. It's just when we
reach
the tail end of the report, that it will miss off part of the last line
and
the form-feed character.

It's a Specialix SX box, connected to a host card in Windows NT. I've
tried
various baud rates and checked the protocol etc.

There are a great number of similar problems with Specialix, posted in
various Unix groups, but I can't see a solution.

Does anyone here have experience of this?






Reply With Quote
  #3  
Old   
Steve
 
Posts: n/a

Default Re: Lost tail-end of reports through Specialix SX on Windows NT 4 - 05-18-2006 , 04:30 PM



Quote:
"Ed Sheehan" <NOedsSPAM (AT) xmission (DOT) com> wrote in message
news:e4i3qp$p73$1 (AT) news (DOT) xmission.com...
You'll probably get more specific help on this, but at first glance it
looks like the serial port isn't flushing its buffer, causing the report
to truncate the last n characters, 'n' being the size of the buffer.
Thanks for the help on this Ed. I think you might be on the right track
there. Sometimes when we take the printer off line and then back on again,
it prints a few missing characters from the previous report, so yes, they're
still in the buffer.

If we print a massive report, we don't lose anything - only the last few
characters.

If I can't fix this, we'll have to install a network print server, but it's
frustrating that the Specialix box has always been like this - I don't rate
them very highly. They don't seem to work well with modems either.




Reply With Quote
  #4  
Old   
Steve
 
Posts: n/a

Default Re: Lost tail-end of reports through Specialix SX on Windows NT 4 - 05-19-2006 , 06:29 AM



Quote:
"Glen B" <no$pamwebmaster@no$pamforallspec.com> wrote
Are you using 3 or 4-wire serial drops? If you are, how are you
configuring the host connector for each port?
We're using pins 2, 3 and 7 on the serial connections. I don't understand
what you mean by 'configuring the host connector for each port'.

If you mean the protocol, it's as follows...

8 data bits, no parity, 1 stop bit
9600 baud
XON/XOFF handshaking





Reply With Quote
  #5  
Old   
Ron White
 
Posts: n/a

Default Re: Lost tail-end of reports through Specialix SX on Windows NT 4 - 05-19-2006 , 08:44 AM



Steve wrote:
Quote:
"Glen B" <no$pamwebmaster@no$pamforallspec.com> wrote
Are you using 3 or 4-wire serial drops? If you are, how are you
configuring the host connector for each port?

We're using pins 2, 3 and 7 on the serial connections. I don't understand
what you mean by 'configuring the host connector for each port'.

If you mean the protocol, it's as follows...

8 data bits, no parity, 1 stop bit
9600 baud
XON/XOFF handshaking



I have not had serial devices for many years now but I
did have an RS6000 with DigiPort Servers before the Microsoft
plague infected us. If I recall correctly (which I would
not bet on) we had to bridge pins 6, 8 and 20 at the
printer end so the buffer would empty at the end of a
print job. Something to try that takes only a few minutes.
Who knows, it might even work.

Ron White

--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.com<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access


Reply With Quote
  #6  
Old   
Jeffrey Kaufman
 
Posts: n/a

Default Re: Lost tail-end of reports through Specialix SX on Windows NT 4 - 05-19-2006 , 10:30 AM



This is old stuff, but hey, you are running on old stuff.

on the printer end:
2 3 7 (green. red, black)

on the server end:
1 2 3 7 (white, red, green, black)
jump 4 5
jump 6 8 20

I hope this helps.
Jeff


"Ron White" <ron (AT) eckel (DOT) com> wrote

Quote:
Steve wrote:
"Glen B" <no$pamwebmaster@no$pamforallspec.com> wrote
Are you using 3 or 4-wire serial drops? If you are, how are you
configuring the host connector for each port?

We're using pins 2, 3 and 7 on the serial connections. I don't
understand
what you mean by 'configuring the host connector for each port'.

If you mean the protocol, it's as follows...

8 data bits, no parity, 1 stop bit
9600 baud
XON/XOFF handshaking



I have not had serial devices for many years now but I
did have an RS6000 with DigiPort Servers before the Microsoft
plague infected us. If I recall correctly (which I would
not bet on) we had to bridge pins 6, 8 and 20 at the
printer end so the buffer would empty at the end of a
print job. Something to try that takes only a few minutes.
Who knows, it might even work.

Ron White

--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.com<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access



Reply With Quote
  #7  
Old   
BobJ
 
Posts: n/a

Default Re: Lost tail-end of reports through Specialix SX on Windows NT 4 - 05-19-2006 , 06:50 PM



Consider the possibility that there is a DB9 in there somewhere. Also,
never forget signal ground - pin 7 on DB25 I think but not sure - which will
cause trouble if missing.
But the problem appears to be flushing the buffer anyway, not the wiring.
BobJ
"Glen B" <no$pamwebmaster@no$pamforallspec.com> wrote

Quote:
Sorry for a re-post, if it happens. My original post has not shown up on
giganews yet. They usually show up within a couple of minutes of posting.

"Ron White" <ron (AT) eckel (DOT) com> wrote in message
news:446dcbd6$0$5439$b9f67a60 (AT) news (DOT) newsdemon.com...
Steve wrote:
"Glen B" <no$pamwebmaster@no$pamforallspec.com> wrote
Are you using 3 or 4-wire serial drops? If you are, how are you
configuring the host connector for each port?

We're using pins 2, 3 and 7 on the serial connections. I don't
understand what you mean by 'configuring the host connector for each
port'.

If you mean the protocol, it's as follows...

8 data bits, no parity, 1 stop bit
9600 baud
XON/XOFF handshaking


That is a typical setup. Most of the information provided below is correct
for the 3-wire configuration you should be using.



I have not had serial devices for many years now but I
did have an RS6000 with DigiPort Servers before the Microsoft
plague infected us. If I recall correctly (which I would
not bet on) we had to bridge pins 6, 8 and 20 at the
printer end so the buffer would empty at the end of a
print job. Something to try that takes only a few minutes.
Who knows, it might even work.

Ron White


My host-side DB25 to RJ45 is wired with DB25 pins 4 and 5 wired together.
This is so that the serial ports don't sit and wait for "go ahead" signals
from unconnected device signal pins. The device side varies by type of
device. DTE and DCE devices require different jumpering depending on the
signal levels required. DCE devices (modems, some printers, etc) require
data set ready to be tied to data carrier detect (6 to 8). DTE devices
(terminals, some printers, and other devices that required DSR) should
have
6 and 20 wired together so that DSR is applied when DTR is. So... You are
absolutely correct in that wiring pins 6,8, and 20 together will always
provide the proper signal levels for any serial device when using 3-wire
RS232.

Glen






Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.