Print Delay (AREV Specific)
At 23 JAN 2003 03:32:40PM John Stranberg Jr wrote:
We are getting a 24 sec print delay in receipt printing.
We have a custom point of sale application running on Arev v2.1
I have been operating on Win95 until recently upgrading to WinXP Pro.
We have the XP print drivers for the printer. Print test is OK, no delay.
Is there some special code we can include within the application to execute the print to LPT1 immediately?
At 23 JAN 2003 03:48PM Richard Hunt wrote:
John,
Hmmmmm… maybe one or both of these commands may do it.
EXECUTE 'SETPRINTER 1'
EXECUTE "PDISK PRN (O S)"
At 23 JAN 2003 06:59PM John Stranberg Jr wrote:
Well, that didn't seem to work. I assume you would add the code on the line following PRINTER ON . Do you include the word EXECUTE in the code line? I tried it both ways.
Any other ideas?
At 23 JAN 2003 08:09PM Richard Hunt wrote:
John,
Yea, they are RBASIC statements. They would be done after the PRINTER OFF, kinda like at the end of the printing.
At 23 JAN 2003 08:10PM Curt Putnam wrote:
I solved my problem by printing to disk (via PDISK) and then typing the file to the printer. Ex:
PERFORM "PDISK TEMP (OS"
Printer ON
Print ….
Printer OFF
PERFORM "PDISK PRN (S"
PCPERFORM "TYPE TEMP ] PRN"
PCPERFORM "DEL TEMP ] NUL"
At 24 JAN 2003 03:04AM [url=http://www.sprezzatura.com" onMouseOver=window.status= Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
We have an internal document describing several possible fixes to this. Drop a mail to [email protected] and we'll send you a copy.
World Leaders in all things RevSoft
At 24 JAN 2003 10:26AM Michael Slack wrote:
Yes, there is a built in print delay. I believe there is even a setting for it. It's there to allow the computer and/or the network to make sure that its gotten all of the print job before it actually prints it out. What you can do is add a "PDISK PRN" after the last "PRINTER OFF" command to tell the computer/network that the job is done and to start printing now and by-pass the delay.
Michael Slack
At 24 JAN 2003 11:40AM Matt Sorrell wrote:
John,
Are you using a Novell client? There is a setting under "Default Capture" for the client config called "Auto Endcap". We set this to true. Also, I have found that some things sent to the printer don't always close the print queue correctly and the system holds the job waiting for the eoj signal. Sometimes executing "PRINTER OFF" will close the job, but another trick I use that has always worked for me is to do a "PERFORM 'PC EXIT EXIT'" from within the program. All this does is shell out to DOS and immediately return.
For some reason this forces the machine to close the print job and everything prints fine.