dbTalk Databases Forums  

printerSetCurrent slow on new PC

comp.databases.paradox comp.databases.paradox


Discuss printerSetCurrent slow on new PC in the comp.databases.paradox forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Toby Sleigh
 
Posts: n/a

Default printerSetCurrent slow on new PC - 10-25-2005 , 04:26 AM






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



Reply With Quote
  #2  
Old   
Mark Bannister
 
Posts: n/a

Default Re: printerSetCurrent slow on new PC - 10-25-2005 , 08:36 AM






Toby Sleigh wrote:
Quote:
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
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.


Reply With Quote
  #3  
Old   
Toby Sleigh
 
Posts: n/a

Default Re: printerSetCurrent slow on new PC - 10-25-2005 , 09:05 AM




"Mark Bannister" <markRemove (AT) ThisINjection-Moldings (DOT) com> wrote


Quote:
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.
There seems to be no correlation between the number of printers and the
delay.
For example my dev PC currently has ten printers installed, some no longer
exist and most aren't connected, and this switches in 1.5secs. The new PCs
have only two printers installed and connected but they take 12secs or more
to switch.
Also the delay appears indifferent as to whether a printer is physically
connected or not.

Toby




Reply With Quote
  #4  
Old   
Liz McGuire
 
Posts: n/a

Default Re: printerSetCurrent slow on new PC - 10-25-2005 , 09:44 AM



Toby,

Put the Zebra on LPT1 and use TextStream to make your labels**. Put
the HP on another port and set it as your default printer. No more
need to swap printers.

**uses EPL2 - I use ZPL for the printers here, and once you get the
hang of it, it's easy - EPL probably isn't much different.

Liz


Toby Sleigh wrote:
Quote:
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.


Reply With Quote
  #5  
Old   
Mark Bannister
 
Posts: n/a

Default Re: printerSetCurrent slow on new PC - 10-25-2005 , 09:44 AM



Toby Sleigh wrote:
<Snip>
Quote:
Also the delay appears indifferent as to whether a printer is physically
connected or not.


Hmmm, I'm not sure then. Some of the issues seen were printers that
were not actually showing up in the printer list (I think) and had to be
deleted in the registry.
I do know that on my portable it will sometimes look for a long time for
a network printer that is only available here at work. This printer is
a network device. Could be drivers.... maybe someone else has some
better ideas.
You might try Filemon or Regmon just to see what it is actually doing
http://www.sysinternals.com/.

Mark B.


Reply With Quote
  #6  
Old   
user@domain.invalid
 
Posts: n/a

Default Re: printerSetCurrent slow on new PC - 01-02-2006 , 07:50 AM



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


Toby Sleigh a écrit :

Quote:
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



Reply With Quote
  #7  
Old   
Toby Sleigh
 
Posts: n/a

Default Re: printerSetCurrent slow on new PC - 01-03-2006 , 02:12 PM




<user (AT) domain (DOT) invalid> wrote

Quote:
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

Thanks for suggestion but they are all there.

Toby




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.