🚀 go-pugleaf

This sounds like a problem that I had encountered under Windows 2000. It is not a driver bug, but rather a bug in the spooling subsystem used by all drivers.

The good news is that this problem can be worked around by turning off spooling which is also the bad news. Printing directly to a device without spooling does tie up both the device and the application program.

The spooling subsystem bug is/was that it was not calculating the remaining disk space left on large NTFS-formatted disk volumes. Typically I would see this problem occur when my spool file would reach a somewhere between 300 and 500 megabytes in size. This didn't happen for disk volumes formatted as FAT-32.

We reported the problem to Microsoft quite a while back. However, I personally haven't seen the bug rear its hoary head in a very long time. I just assumed that one or more of the services packs (either 2 or 3) fixed the bug. Upon reading your post, I did attempt to choke the horse with a monster file on the queue. Couldn't get it to fail anymore with my systems running Windows 2000 SP3 with all Microsoft updates.

This is a long shot, but assuming that you have all Microsoft's critical and recommended updates applied for Windows 2000, you should try applying the Multiple Master patch described at <http://www.adobeforums.com/cgi-bin/webx?13@@.1de5b45b>. It has some system updates that may possibly include the fix to this problem. Let us know if it helps.

- Dov