>Hi All,
>
>FPD 2.6 application works under Windows Terminal Services.
>
>Customers on several locations experience large delays after sending a printing job and before the actual printing starts -- the FPD 2.6 task is frozen from 1 to 5 minutes for any printing job, regardless of the size.
>
>With Windows Server 2003 it's getting even worse -- larger delays and less controllable situation.
>
>Any workaround?

One thing to check first is LPT_Timeout: http://support.microsoft.com/default.aspx?scid=kb;en-us;102059

The default of 15 seconds is way too long for modern fast computers, it can be reliably set to 5 seconds or less unless you have long reports with large pauses for calculations between pages.

I vaguely remember having delay problems a couple of years ago getting FPD2.5 to run on my W2K Pro box. I ended up specifying the COMMAND.COM shell instead of CMD.EXE; my custom CONFIG.NT file for FPD is as follows:

dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=100

shell=%SystemRoot%\system32\command.com /e:1024

Memory settings:
Conventional: Total: Auto Initial Environment: Auto
Expanded (EMS) Memory: 0
Extended (XMS) Memory: 0
MS-DOS Protected Mode (DPMI) Memory: Auto (Ed Rauh recommended 15360KB which is probably smarter)

His recommendations for memory settings etc. in Recommendations for memory configuration for FPDOS/FPW under Win32 OS FAQ #15468