We had this problem also with our FPD26 apps when our users started upgrading to Windows 2000 and Windows XP. We found out that changing the following registry key to 1 (from the original value of 15) resolves this problem and there is no longer a delay:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW\LPT_Timeout


There is another registry setting too that we set, but I cannot remember what it is now. I'll look and see if I can find it, and if so, I'll post it with this message.

Tracy

>Hi Mike,
>
>I was wondering if the person you relayed this for ever got this to work. We recently upgraded a clients' workstation to Win2k from Win98 (actually, it was a clean install). They are still running lots of legacy FPDos apps. This is the last issue we are dealing with. I'd hate to have to go in and put a SET PRINTER everywhere there is output. (he's runnning SBT vers 8 and lots of custom apps) Interestingly, it doesn't do it on everything (SBT seems to be better than the custom stuff, but I haven't really checked the code yet). It really irritates the client that he has to wait 20-30 seconds to print a test label on his dot matrix!
>
>I'm hoping the registry fix will work for him, but I want to make sure before I make another trip over there.
>
>This is one of those "don't spend too much time on it" projects.
>
>>I've been asked to relay a question about a FoxPro DOS app that prints to a recipet printer using SET PRINTER and ??.
>>
>>When printing, it delays the output of the printer by several minutes on NT/2000/XP but not on 9x/ME. I think they said it has somethign to do with the Spooler holding on to it but I don't remeber for sure.
>>
>>Anyone know how to work around this?
>>
>>Thanks.