![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi I've got an app that needs to print labels and reports so frequently switches printers using printerSetCurrent(). This has been working perfectly ok for last couple of years on a selection of h/w and o/s versions.( Win2000 SP4, WIN XP SP1 & SP2) All Pdoxwin 11. Recently my company bought a batch of up to date PCs ( P4 .. Sorry can't recall exact spec but all WinXP SP1 and everything goes like the clappers.) and now there is a very significant delay with printerSetCurrent(). Investigating the problem further I've found a wide range of times for printerSetCurrent. I've tried some test timings; for example my dev PC ( Athlon XP2500 512Mb Win XP SP2) switches in approx 1.2 seconds, an older Win2000 SP4 PC switches in approx 0.4 sec, a WinXP SP1 laptop takes about 3 secs but the new PCs ( Win XP SP1 ) take on average 14 seconds. This delay really disrupts the flow of the app. These times are seen whether or not the printers are physically attached to the PC. The usual configuration is a Zebra TLP2844 on the USB i/f and usually a HP laserjet nn on LPT1. I've tried installing the Laserjets driver as HP Laserjet Series2 but this makes no difference. I've tried swapping the Zebra onto LPT1, again no difference. Any suggestions of what to try next most welcome. Toby This sounds like the Windows searching for printers that aren't there or |
#3
| |||
| |||
|
|
This sounds like the Windows searching for printers that aren't there or are not currently connected. There are several threads on this on the pnews groups. Windows will *sometimes* spend an inordinate amount of time looking for printers that are not connected. Odd things can trigger this activity. Mark B. |
#4
| |||
| |||
|
|
The usual configuration is a Zebra TLP2844 on the USB i/f and usually a HP laserjet nn on LPT1. I've tried installing the Laserjets driver as HP Laserjet Series2 but this makes no difference. I've tried swapping the Zebra onto LPT1, again no difference. |
#5
| |||
| |||
|
|
Also the delay appears indifferent as to whether a printer is physically connected or not. |
#6
| |||
| |||
|
|
Hi I've got an app that needs to print labels and reports so frequently switches printers using printerSetCurrent(). This has been working perfectly ok for last couple of years on a selection of h/w and o/s versions.( Win2000 SP4, WIN XP SP1 & SP2) All Pdoxwin 11. Recently my company bought a batch of up to date PCs ( P4 .. Sorry can't recall exact spec but all WinXP SP1 and everything goes like the clappers.) and now there is a very significant delay with printerSetCurrent(). Investigating the problem further I've found a wide range of times for printerSetCurrent. I've tried some test timings; for example my dev PC ( Athlon XP2500 512Mb Win XP SP2) switches in approx 1.2 seconds, an older Win2000 SP4 PC switches in approx 0.4 sec, a WinXP SP1 laptop takes about 3 secs but the new PCs ( Win XP SP1 ) take on average 14 seconds. This delay really disrupts the flow of the app. These times are seen whether or not the printers are physically attached to the PC. The usual configuration is a Zebra TLP2844 on the USB i/f and usually a HP laserjet nn on LPT1. I've tried installing the Laserjets driver as HP Laserjet Series2 but this makes no difference. I've tried swapping the Zebra onto LPT1, again no difference. Any suggestions of what to try next most welcome. Toby |
#7
| |||
| |||
|
|
hi, try looking the default style file, on your *.fsl the files are *.fp or *.FT I now that if the default fp or ft file of your fsl are not present on your machine, it can be a reason of your problem. and sorry for the bad english. Filipe |
![]() |
| Thread Tools | |
| Display Modes | |
| |