Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Remote UUCP Dialup printer problem with OS 5.0.5

0 views
Skip to first unread message

JiffyPoP

unread,
Mar 26, 1999, 3:00:00 AM3/26/99
to
Hello folks!

I'm having a problem with a remote dialup uucp printer and offer this plea
for help. :) I will describe my problems then will outline the current
config.

Problems:

1) The print spooler will successfully dial and connect to the printer,
deliver the print job and then spool the next job in the queue. The problem
here is that it never disconnects from the site once the first print job has
been delivered. To remedy this, I have added +++\dATH to the
/usr/lib/uucp/Dialers entry for the printer. This really is not the best
way to do this, but it works for now. Any suggestions on a more graceful
way to accomplish this?

2) As stated before, the print jobs are delivered to the printer and the
printer prints them. The problem that is occurring with the print job
itself is that when the job is "spooled" three pages of 3 lines of "X"s
appear at the end of the job. I know this happens through the spooler as a
direct print to the device does not produce the Xs at all. We use Equinox
Super Serial boards and can watch and capture the data being sent and
received on any serial port for the card. I have this information and would
be willing to email it to anyone that is interested. While watching this
device I did notice that if I issue "cat <somefile> | lp -dlp2" and watch
the output, the Xs appear at the end of the job. I issue "cat <somefile>
>/dev/tty1b5" the print job works fine. Any suggestions?

Configuration:

UNIX: SCO OS 5.0.5
Printer: Tektronix 880 serial Impact Printer
Printer type: uucp dialup
Modems: QBlazer 33.6 each end
Serial Interface: Equinox SST - 48 Ports of Serial Connections
/usr/spool/lp/admins/lp/printers/lp2/configuration:
Banners: off
Content types: simple
Dial: XXXXXXX
Fault: beginning
Interface: /usr/spool/lp/model/dumb
Printer type: unknown
Number of banners: 0
/usr/lib/uucp/Dialers entry:

printer =, -, "" +++\dATH\r\c OK\r
AT&FQ0E0V1&D2&C0S0=0X4S2=043\r\c OK\r ATDT\T\r\c CONNECT
&printer =,-, "" +++\dATH\r\c OK\r ATE0Q1H\r\c
OK\r
/usr/lib/uucp/Devices entry:

ACU tty1b5 - 9600 printer

If you need more information about configurations, please email me at
rmc...@execpc.com and I will get you anything that you need. As stated
before, this configuration does work, it just appends Xs at the end of the
job. The interface portion is a standard interface model from SCO.


Thanks in advance. I appreciate all the help I can get on this.

have a GREAT day!

Richard McKay
rmc...@execpc.com


Kevin Smith

unread,
Mar 26, 1999, 3:00:00 AM3/26/99
to
Use the modem control device (tty1B5 most likely) and make sure you
have a cable that has at least DTR and CD wired through, and make
sure the modem is not setup to hold CD high and is also setup to
reset on loss of DTR. Generally at&d3&c1 (or &d2&c1)

SCO will drop DTR at the end of the connection causing the modem
to reset. SCO will also detect loss of CD and abort the connection.

The lower case device names (tty1b5) are non modem control devices
which will prevent SCO from detecting carrier loss (DTR will still
go up and down).

Since you're not hanging up at the end of the call you probably are
ignoring DTR at the modem (&D0) or have it wired up from some other
signal line.

--
Do two rights make | Kevin Smith, ShadeTree Software, Philadelpha, PA, USA
a libertarian | 001-215-487-3811 shady.com,kevin bbs.cpcn.com,sysop

0 new messages