JetDirect 500X Woes

[Mark Olbert]

When I try to print large files (spool size > 150MB) to my Deskjet 5550 that's hung off of a
JetDirect 500X, I frequently run into problems (this is under Windows XP SP1).

The XP print spooler complains that the document didn't print, but when I try to delete the entry in
the spool queue, nothing happens. I've discovered, by trial and error, that if I restart the Windows
print spooler service I can >>sometimes<< delete the bad document. At other times, restarting the
print spooler results in the document printing (even though it's marked as Error in the spooler
queue), and other times nothing happens at all, and I have to reboot my computer.

I'm wondering if I've got some conflict between the Windows printer driver settings and the
JetDirect (e.g., maybe I shouldn't be having Windows do any spooling at all). I say this because I
can't believe HP would ship a piece of junk, which is effectively what the 500X is on my system
right now (i.e., I need a print server that "just works", not one that needs to be babied every step
of the way).

Any advice and/or suggestions on how to solve this problem would be appreciated.

- Mark

[Matter of contention]

On Fri, 19 Dec 2003 11:03:34 -0800, Mark Olbert <mark@arcabama.com>
wrote:

|When I try to print large files (spool size > 150MB) to my Deskjet 5550 that's hung off of a
|JetDirect 500X, I frequently run into problems (this is under Windows XP SP1).
|
|The XP print spooler complains that the document didn't print, but when I try to delete the entry in
|the spool queue, nothing happens. I've discovered, by trial and error, that if I restart the Windows
|print spooler service I can >>sometimes<< delete the bad document. At other times, restarting the
|print spooler results in the document printing (even though it's marked as Error in the spooler
|queue), and other times nothing happens at all, and I have to reboot my computer.
|
|I'm wondering if I've got some conflict between the Windows printer driver settings and the
|JetDirect (e.g., maybe I shouldn't be having Windows do any spooling at all). I say this because I
|can't believe HP would ship a piece of junk, which is effectively what the 500X is on my system
|right now (i.e., I need a print server that "just works", not one that needs to be babied every step
|of the way).
|
|Any advice and/or suggestions on how to solve this problem would be appreciated.

I have a client w a 500x that has performed for years. The reports
that they produce have photo pages so the firm needed laser and color
printing(this was long before color laser became affordable). Early
deskjets would not network reliably and they got a 2000c when it was
introduced. It just retired it in favor of a color laser.

How does your 5550 print the "offending" jobs when connected to a box
rather than the 500x and the same question when connected to a box but
shared over a lan.

good kuck w it-moc