Quote:>I have set up a network printer on my SCO OpenServer 5.04 system on lp0. It
>is a HP400. When I performed a test print from my Win95 machine, it took 5
>mins for it to start printing.
It's an HP4000. Since you say it's a "network printer", I'll
assume that you have it plugged into the parallel port on your
computer and that you have used the "Hp Network Managerie" (HPNP)
to configure it as a print server.
Quote:>My questions is, Is this normal? I mean, I have done network printing
>before between WinNT machines, and it happens after the page has been
Nope. 5 minute print jobs of simple files are not normal. 5
minute print jobs of files that require heavy processing on the
Windoze 95 box are typical. Which are you doing?
Also, the print job will not begin printing until the Windoze 95
application has finished processing.
Quote:>Any information is appreciated with this curious problem.
>BTW I hope this is enough information.
It's not. I can't tell if it's the Windoze 95 machine or the
OSR5 print spooler. Let's see if we can assign the blame in an
1. Is the parallel port configured in the BISO for anything
other than a "normal" parallel port? SCO Unix does not support
EPP, bi-directional or ECP parallel features.
2. Does this box have two parallel ports? If so, they cannot
both share IRQ=7. One must be on IRQ=5.
3. How does it print locally on the OSR5 box? Try printing
something simple (text file) with:
lp -d printername filename
Does it go quickly or take another 5 minutes? You can determine
print status with:
4. Are there any more workstations available that can be used
for testing? Try lpr printing from one of them. Does it do the
same thing? If so, then it's the OSR5 box. If not, then fix the
Windoze 95 machine.
Suggestion: Upgrade to the HP4000N (network) with the built in
JetDirect card. Windoze can access it directly with either
tcp/ip or ipx/spx (You need ipx/spx to run JetAdmin from Windoze
95). The versatility of having a printer that can be easily
moved to anywhere on the network and will print from anything is
In SCO Unix 3.2v4.2 the parallel port was a major cpu cycle hog.
If I sent a monster file to a parallel port connected printer, it
would slow the system down to a crawl for the duration. I
haven't check if this is still the case in OSR5 because not one
of my current customers (or my office) have parallel printers
connected to the server. I use stand alone print servers or
built in JetDirect cards exclusively.
[x]email [x]news [ ]mailing list
Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
(408)699-0483 pgr (408)426-1240 fax (408)336-2558 home