Win XP/AREV312 Printing locks workstation (AREV Specific)
At 27 JAN 2005 10:25:36AM Leon Shaffer wrote:
We are have a few workstations that when they print one document immediately after another, AREV locks up and will not release itself and of course slows the workstation to a crawl.
i.e.
Print an Invoice
then immediately (within a couple of seconds) print another invoice
AREV menu turns completely black and never recovers
—–System Information—–
Network - Novell 4.11 with SP9
Workstation - Windows XP with SP2 and all updates, Novell Client
4.9 with SP2HPrinter - Network printer (HP Laserjet)
Command within program(s)
I have tried both the Capture command from with AREV andalso the PERFORM 'SUSPEND EXIT CHPLJ.BAT' commandNo other program has a problem printing to the printer(s), including
Work, Excel, Outlook, etc.
If the user waits until the 1st Invoice or document has completely printed and then waits about 3 seconds, they can print another invoice or document and it is fine…it is only when they attempt to
print multiple documents and it is only on Win XP machines.
Another clue might be that any document printed from AREV take a long time to print (about 30-40 seconds) even though the timeout option in the capture command is set to 5 seconds…this is also a little frustrating - why does it take so long for a document to print where other workstations (especially W98 Worstations) print almost immediately…
Any suggestions are welcomed and appreciated…
At 27 JAN 2005 01:52PM Matt Sorrell wrote:
Leon,
Are your printers on a Novell or Windows print queue?
You might take a look at this thread, as I had a similar issue.
This really cleared things up for me.
msorrel@greyhound.com
At 27 JAN 2005 02:16PM Leon Shaffer wrote:
Matt,
Thank you for your answer. The printer are on a Novell queue.
I have discovered that the locking problem is specifically with
issuing the
PERFORM 'SUSPEND EXIT CHPIIISI.BAT'
If I comment this line out and run the program, it works like the
eveready battery..it prints and prints and prints and prints
with no problem. I am modifying the SYSTEM.INI file and the registry
to test it as well.