chytil@tuvie (Inst.f.Techn.Informatik) (10/27/90)
We have three printers (well, actually two printers and a plotter)
connected to a DN3500 running 10.2.0.5 . Spooling is done via lpd
and prf -- the Aegis hack :-( .
I've inserted a line in rc.user just before starting up the appropiate
prsvr which reads
tctl -line 1 -sync -parity even -speed 19200
yet the lines are not set accordingly after the prsvr comes up. This is
especially nasty with sync, as You can imagine.
Note that this setup has worked for a month or so, and these effects may
have to to with the pre10q -daemon I've enabled a week ago. But then, I'm
not so experienced with Aegis-internals ( These are the only occasions where
I wish I would :-( ).
Has anybody else had these effects before or could drop me clue as to where
my mistake might be, if any ?
Thanx in advance
Georg
--
<------------Golden apples of the sun, silver apples of the moon-------------->
Chytil Georg Systemdamager@Dep. of VLSI (vlsivie) TU Wien A-1040 Wien Austria
chytil@vlsivie.{tuwien.ac.at,uucp} chytil@egh780.una.at +43/(0)222/58801/8146
#include <extra_disclaimer.h> Don't panic! Fax: +43/(0)222/569697krowitz@RICHTER.MIT.EDU (David Krowitz) (10/29/90)
Most of the print server drivers (the files in /sys/hardcopy/drivers) will initialize the output stream when they first start up. This initialization may or may not match your printer's current setup (eg. you wish to use XON/XOFF handshaking via the tctl -sync option, the server may wish to use RTS/CTS handshaking via the tcl -cts_enable -rts_enable options). Either change the settings on your printer (and also get a cable which matches those settings!) or use /com/tcl *after* the print server has been started *and* has had time to load and init the driver. This can take 10 to 20 seconds after /sys/hardcopy/prsvr has been started. -- David Krowitz krowitz@richter.mit.edu (18.83.0.109) krowitz%richter.mit.edu@eddie.mit.edu krowitz%richter.mit.edu@mitvma.bitnet (in order of decreasing preference)