We've got this zebra bar code printer that was originally connected to the server on serial, but we had some issues with hand shaking so we connected its parallel port to a HP printer server.
Someone/thing upset the wired connection (not in the OS) today and now it doesnt print.
I can access the HP print server config page via a browser and it says that a Zebra is attached – good.
Looking at lpstat reports that it is connected to tty08 – the serial port it hasnt used for two years.
Using the network printer config confirmation within SCO ADMIN found the Zebra on port 192.168.1.105 ok the first time, but failed on the 2nd.

I know this printer doesnt have a script like other text printers so it may be tricky, running RealWorld software means product support is next to nil from the vendor.

I have cancelled jobs for this printer, disabled/enabled the printer to no avail. Are there other processes to kill/cancel?

I am guessing that the professional Unix man who set the printer up on the HP server was ok with the lpstat report so I am loathe to remove/add the printer.

So, should I backup the script in /usr/spool/lp/admins/lp/scripts (cant remember exactly), remove all traces of any existence if it is connected serially and ethernet and re-add it via SCO Admin HP printer network thingo?

I did a SCO admin course in '94 so I am a little rusty on this O/S, let alone this version.
Thanks in advance,
JohnW