Posted by Mike Saunders on June 11, 2008 at 08:02:04:
I do have CometAnywhere unspool printing working at a remote site through the internet.
Observation.
We are printing a barcode label that consists of 333 bytes.
Each label shows up in the Comet Spooler as a single job of 4 lines.
With the windows printer paused,
Each label, normally, shows up in the windows spooler as a single job of 333 bytes.
However frequently the single job is broken up into multiple jobs.
Total up the bytes in each and you still get 333 bytes.
So I might get a job with 100, a job with 233, and a job with na.
or I might get a job with 191, a job with 100, and a job with 42.
And the label still prints okay.
Looking for ideas on why the jobs would be broken up.
Is it windows spooler closing the job due to a delay in receiving then next packet of infomation?
Is is comet Spooler timing out and closing the job and starting a new one?
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.