Page 9
Part Number: 45051581
Printing
Job batching
If job batching is enabled, multiple jobs received by the Fiery EXP4110 close together are
printed as a single job. Control job batching through the Job Batching Delay option in Setup.
If this option is set to 0, job batching is disabled. If this option is set to a non-zero value, jobs
that are received within this number of seconds are batched.
If job batching is enabled:
• The job information displayed on the printer for batched jobs is not correct, because the
jobs are considered one job. Command WorkStation and the Job Log show the correct
information for the individual jobs.
• After printing is complete, the job status remains Printing until the Job Batching
Delay expires.
• Jobs with the Save Fast Reprint option selected and jobs printed through the Print and
Hold command in Command WorkStation are not batched. They are always printed as
individual jobs.
Printing delay on Windows 2000/XP
With Windows 2000 and Windows XP, all MS-DOS printing is done through the Windows
NT spooler system. In order to know when to send a job to the spooler, a timeout is set
on the printer port. Once a job is printed to the port, if this timeout passes with no more data
presented to the port, the print job is sent to the spooler. The default timeout is 15 seconds.
Therefore, there is a 15-second delay before the print job starts printing. Microsoft has
documented this issue in the following web page:
http://support.microsoft.com/default.aspx?id=kb;en-us;Q101850
A computer using any version of Windows 2000 or Windows XP (including the Windows
2000 data server) requires the following changes. If you use Citrix or terminal services, the
changes must also be implemented on the Windows 2000 server running Citrix/Terminal
Services, as well as each workstation that uses the Windows 2000 or Windows XP
operating system.
To decrease the timeout, use the following procedure to edit these registry settings:
• HKEY_LOCAL_MACHINE
• SYSTEM
• CurrentControlSet
• Control
• WOW
• LPT_Timeout
WARNING
: Using REGEDT32 can cause serious damage to your operating system.
Make sure to follow these steps exactly.
