WinXP &.PDF printing problem (intermittant)

[Guest]

When printing large jobs (i.e. 20,000+ pages) from a .PDF file and using a
WinXP/sp2 machine and an HP5si printer (40MB RAM) & driver (most recent) the
print jobs occassionaly, but not always, start printing out garbage
characters midway thru the job. The characters are not extended ASCII
characters but rather various square shapes and other four sided geometric
figures. The weird part is that its just an occassional problem, and all of
the smaller print jobs print fine. Would upping the RAM likely solve this
problem ? Or is it something else ? TIA ...

 

[David H. Lipman]

From: "E-Double" <[email protected]>

| When printing large jobs (i.e. 20,000+ pages) from a .PDF file and using a
| WinXP/sp2 machine and an HP5si printer (40MB RAM) & driver (most recent) the
| print jobs occassionaly, but not always, start printing out garbage
| characters midway thru the job. The characters are not extended ASCII
| characters but rather various square shapes and other four sided geometric
| figures. The weird part is that its just an occassional problem, and all of
| the smaller print jobs print fine. Would upping the RAM likely solve this
| problem ? Or is it something else ? TIA ...

Is that with an internal HP JetDirect in the 5si or are you connected directly to the
printer ?

 

[Guest]

External JetDirect 300x ...

 

[David H. Lipman]

From: "E-Double" <[email protected]>

| External JetDirect 300x ...
|

With e a 5si you can and should be using an internal JetDirect.

I suggest swapping out the unit with another and test printing again. If the problem goes
away, then it was the jetDirect bastardizing the print job. Either that or try a direct
connection for the test(s).

If you do replace the external unit I suggest replacing it with an internal unit

 

[Leythos]

From: "E-Double" <[email protected]>

| External JetDirect 300x ...
|

With e a 5si you can and should be using an internal JetDirect.

I suggest swapping out the unit with another and test printing again. If the problem goes
away, then it was the jetDirect bastardizing the print job. Either that or try a direct
connection for the test(s).

If you do replace the external unit I suggest replacing it with an internal unit

I've seen the same thing with multiple types of printers and multiple
types of network connections.

To the OP, try testing by connecting DIRECTLY to the printer - or setup
a local printer by IP to your printer instead of using the server as the
spooler and let us know if that fixes it.

 

[Guest]

cool, will do - thanks guys.

e.

I've seen the same thing with multiple types of printers and multiple
types of network connections.

To the OP, try testing by connecting DIRECTLY to the printer - or setup
a local printer by IP to your printer instead of using the server as the
spooler and let us know if that fixes it.