SCO 3.2v5.0.5. No VisonFS or Samba yet.
I'm stuck with an application where support insists that the names of the
printers remain hard coded in their application. At least it uses the
stock SCO print spooler. The problem is that the customer wants to use
transparent printing to print to local printers attached to Wyse 150+
terminals, and Windoze 98SE computers using Tiny Term. I can easily make
it print using either:
belch-report | lprint -
However, I need to integrate local printing into the SCO print spooler to
keep the application vendors support staff happy. They went into
hysterics when I found the secret printer configuration file and hacked
it into functionality. However, that has been declared politically
I used Digiboards transparent print driver for the terminals, so that's
done. But how do I convince the SCO print spooler to do a transparent
print to a Windoze telnet session? Lprint doesn't work with scoansi or
ansi because someone ran out of space for tokens in termcaps and left out
the PN and PS tokens. Do I have to hack the spooler script to pipe the
output to lprint or imbed PS and PN tokens in the script? Surely,
there's an easier way.
The application vendors support personality also suggested I install
VisionFS so that OSR5 can print to a shared Windoze printer on a PC. Can
it do that? If so, that would bypass the transparent print problem.
Drivel: I tried to sell them print servers (the right answer), but they
decided that would be to "complex" and expensive. Duh.
150 Felker St #D Santa Cruz CA 95060
831-421-6491 pager 831-429-1240 fax
http://www.cruzio.com/~jeffl/sco/ SCO stuff