need regedit for a faster printer

  • Thread starter Thread starter robert lipsett
  • Start date Start date
R

robert lipsett

I am looking for a regedit to speed up a printer problem in windows xp home.
I know that a regedit exist to limit the amount of time the computer waits
to send printer information to a printer. I know that all print information
goes through a que spooler even though you specify direct to printer and raw
format. The 10 second delay is very annoying especially when I am printing
information on forms that have where there are 3 distict forms on the
tractor feed paper within the sive of a normal piece of paper. I sometimes
hit the tear button to get the form before the last item prints due to the
delay. I know this regedit exist because I had it before but right now I
lost it due to the computer crashing and being reloaded. Any help would be
appreciated
 
Try switching youre printer from the printer port to usb,it will take 1/4 of
the time...regedit deals with the OS files/software in xp
 
that is not an option due to the fact that the software I am using is
written to only output to the lpt connection and my printer is only lpt
capable ( dot matrix printer)
 
robert lipsett wrote :
I am looking for a regedit to speed up a printer problem in windows xp home.
I know that a regedit exist to limit the amount of time the computer waits
to send printer information to a printer. I know that all print information
goes through a que spooler even though you specify direct to printer and raw
format. The 10 second delay is very annoying especially when I am printing
information on forms that have where there are 3 distict forms on the
tractor feed paper within the sive of a normal piece of paper. I sometimes
hit the tear button to get the form before the last item prints due to the
delay. I know this regedit exist because I had it before but right now I
lost it due to the computer crashing and being reloaded. Any help would be
appreciated
Click to expand...

Sounds to me you are running an old DOS application:
http://www.google.com/search?q=xp+spooler+timeout+dos
 
robert lipsett wrote :
thanks for the link it looks like what I need
Click to expand...

Please note that if your application supports printing to a file named
LPT1 instead of directly to the physical port LPT1, is a much better
solution to your problem.
 
robert lipsett wrote :

Please note that if your application supports printing to a file named
LPT1 instead of directly to the physical port LPT1, is a much better
solution to your problem.
Click to expand...


Please note that LPT1 is a reserved name in DOS and Windows and can
*not* be used for a file name. It has nothing to do with whether the
application supports it.
 
Ken Blake, MVP wrote :
Please note that LPT1 is a reserved name in DOS and Windows and can
*not* be used for a file name. It has nothing to do with whether the
application supports it.
Click to expand...

Yep - writing to a device name does not create a typical file on a
drive. An application writing to a "file" does not distinguish between
a real file name and a reserved device name. The DOS copy command is an
example of this (e.g. "copy filename.txt lpt1").

For DOS applications there are usually two ways of outputting print
data:
1. To a file (in this case a device name called LPT1)
2. Directly to the printer (via the BIOS or a hardware I/O-port)

Windows grabs both of them.
Using method [1], Windows knows when a print job is finished, and
begins printing immediately. In method [2], the DOS application sends
data without indicating an end of job, so Windows does not know if the
application is still computing print data or if the print job is
actually finished.
In a multitasking environment it must know this before sending data to
the printer - that's why it waits for about 15 seconds before assuming
an end of the print job.
 
Back
Top