home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 9
/
novell-nsepro-1992-vol09.iso
/
download
/
212prt.txt
< prev
next >
Wrap
Text File
|
1992-03-16
|
6KB
|
133 lines
#: 17258 S6/Installation/Upgrde
16-Jan-89 10:14:22
Sb: NETWORK PRINTERS
Fm: Edward Langer 75170,100
To: SYSOP (X)
I'm having trouble printing to our network printers. I'm running Advanced
Netware 286 version 2.12 (Dedicated, Non-SFT) on an ALR 20386DT file server
(with about 4 MB RAM). (This is a 386 machine running a 20 Mhz.)
Printer 0 is set up as COM1:, 9600 Baud, 7 Data Bits, Even Parity, 1 Stop Bit,
Use Xon/Xoff. Printer 1 is set up as COM2:, 9600 Baud, 8 Data Bits, No Parity
1 Stop Bit, Use Xon/Xoff.
The problem is that my printers and plotters will work for a time, but then
will report framing or data transfer errors. For instance, my HP Laser Jet,
connected to Printer 1, will report an Error 40 ("Error occurred while
transfering data from computer"). Nothing seems to correct the problem
consistently; even taking down the file server and bringing it back up does not
always correct the problem.
I have no trouble connecting the printers when the server is down and booted
under DOS. This seems to indicate that the COM ports themselves are working
properly and that my data transmission configurations are set properly. Also,
my printers work properly using the same configurations on a Compaq Deskpro 286
server running Advanced Netware 2.0a.
Any ideas? Thanks?
-----
From John:
Try using DTR instead of Xon/Xoff
-----
Date: 17-Jan-89 07:56 CST
From: Edward Langer [75170,100]
Subj: NETWORK PRINTERS
I cannot use any sort of hardware handshaking (I'm using a line driver that
does not permit it.)
Is there some known problem with using XON/XOFF under 2.12? I had no problem
using it under 2.0a.
I'm getting some heat here because I'm supposed to be getting a VERY expensive
laser plotter to the server. I had NO problem attaching the plotter to our
other server which is still running 2.0a. (But I was able to do that for
testing only; not as a permanent fix.)
Any help would really be appreciated! Thanks.
-----
Yes, v2.12 has some sketchy undocumented problems with the serial ports
for printing
possible solutions
(1)(WORKS EVERYTIME) use the parallel port, if the printer is serial only
get a parallel to serial convertor, I recommend Black Box for this,
make sure the convertor converts ALL 8 BITS (some do only 7 bits,
stripping the high bit)
(2)Try "reverse" protocols, such as the server doing Xon/Xoff and the
printer doing DTR or vica versa, it seems counter intuitive but works
in many cases
(3)how we doing?
<<John>>
-----
#: 17499 S6/Installation/Upgrde
17-Jan-89 17:13:12
Sb: XON vs. DTR
Fm: Edward Langer 75170,100
To: SYSOP (X)
[Part of the thread of this message is lost because we communicated via
Easyplex.]
John, your fix to the "sketchy" 2.12 bug in using Xon/Xoff with a Network
serial printer worked! I set the server to use Xon/Xoff and the plotter to
expect DTR (hardware handshaking). I agree, this is "counter-intuitive," which
is probably why I pulled so many hairs out trying to solve this before getting
your suggestion.
But Hey! Novell! How can you be aware of a "sketchy" bug and a possible fix
and not shout about! I mean, Netware's support of network printer has been
around since 1492 it's not like it's a new and ecoteric feature. If you
suspect a bug there's got to be a way to get the message out.
I'm not sounding off at NOVUSER of NOVFORUM (you guys are great). But for the
end user, frustration can be high enough to lead to a coronary. Somehow, all
known or suspected bugs should make it to some forum somewhere even before a
fix is developed. That would save countless wasted hours and much agravation.
[Have I been belly aching? Sorry, didn't mean to. Just venting steam.]
Anyway, thanks for your help in tackling this!
Press <CR> for next or type CHOICES !
***MORE TO THE SAGA*********>>>>>
#: 17865 S6/Installation/Upgrde
19-Jan-89 08:50:37
Sb: #17499-XON vs. DTR
Fm: Edward Langer 75170,100
To: Edward Langer 75170,100 (X)
A follow up on 2.12's problem with using Xon/Xoff to send output to a network
serial printer . . . your "counter-intuitive" solution was to set the server to
use Xon/Xoff and the plotter to use DTR (hardware handshaking) . . . this
worked, though I can't explain how that's even possible.
The solution is not completely satisfactory, however. The communication seems
to be working in only one direction, server to plotter. But the communication
needs to work the other way around, too, so that the plotter can tell the
server when it's off-line, out of paper, buffer full, etc.
I'd appreciate if you could get the powers that be to continue investigating
the bug. Much obliged!
-----
Yes Sir Ed, that is definitely a problem condition,
recommendation is to send all plots to CAPTURE files for NPRINTING
that way you don't have to regen the plot at least if you were
lose it..
v2.15 supposedly fixes this..
Novell counters by saying they've never experienced this...they are trying
again though to recreate...stay tuned
<<John>>