HMah wrote:
> Hi David:
>
> Can you reduce the 10sec dalay, when using nvPRNq, before the
> printing actually starts?
>
Yes, There are actually 3 separate features which effect how a job is submitted to the Windows Print Queue. There are two background events always occurring (for nvPRNq). Keep in mind, they are using “Timer Events” and only perform a task when the timer clicks (more like a repeating “alarm clock”). The minimum time event is 1 second – so the fastest any job can begin “printing” is 2 seconds. However, we have no control over the speed/time once the Windows print queue receives the print job.
There is a simple way to check timer settings. Double click the “Book with the red arrow” (in the middle) and a box will pop-up showing you the current settings.
=============
The DirScanFreq decides how often to look for a new print job (in seconds).
The SpoolerTimeOut decides how “Old” a job must be, before sending it to the Window’s Print Queue. “Old” is defined as having received no more input from NewViews.
The NoHogCPU forces the program to “wait its turn” with all the other windows programs. Regardless of the setting, it rarely consumes more than a few percent of the CPU cycles. This is really useful when printing LARGE Jobs (like 50 pages).
Installed with the nvPRN.exe program, you should have an INI file called “nvPRNq.ini”
NOTE: IT must have the same name as the exe file to work correctly.
nvprnq.exe
nvprnq.ini
With any word/text processer, add or modify the 3 lines below
DirScanFreq=1
SpoolerTimeOut=1
NoHogCPU=0
Perhaps more detail than you wanted, but . . . . I will promise to be more “short” in the future 
I Hope this helps
David
