Novell/Win95 printer hesitation from Arev (AREV Specific)
At 23 JUL 1998 11:33:03AM Steven Danielson wrote:
I have a printer hesitation problem. I am using Arev 3.03 on a Novel network. I'm running Novell 3.12 on the server. I have a network printer set up accessed by 3 stations. Two stations are running on the Novell and when they print they have about a 2 or 3 second hesitation which is just fine. They are not running Win95. The are running: LSL.COM, SMC8000.COM, IPXODI.COM, and NETX.EXE.
The third station is running Win95 and the MS networks driver, and it has a 2 MINUTE PRINTER DELAY; but ONLY IN AREV! When I print from some other software program there is only a few second delay. When I drop out of Arev the printer prints the pending Arev print jobs immediately.
Any ideas why it's hesitating?
Any help greatly appreciated. Thank You.
At 23 JUL 1998 12:21PM Victor Engel wrote:
It sounds like you are capturing your printer port and have it set up to autoendcap after 2 minutes. To check, from a DOS prompt type CAPTURE /SH. This will show you your capture settings.
The printout goes immediately when logging out of Arev because you are closing the printer port. Typing PDISK PRN from TCL may have the same effect. I've found that sending an EOF to the printer port also sometimes does the trick. Or, you can issue an ENDCAP and then CAPTURE your port again. I think typing SUSPEND may also do the trick.
At 24 JUL 1998 01:28AM Curt Putnam wrote:
Steven,
After each print job, you can do a:
pc exit ver ] nul
which will release the print job immediately. I use this in all Novell hosted reports to do the equivilant of an ENDCAP.
At 24 JUL 1998 11:20AM Jim Horvath wrote:
The information in the other responses is good so far as it goes, but since you didn't mention the LH NLM in your system setup, I would advise you to avoid all solutions that involve suspending to DOS from AREV (SUSPEND or PCPERFORM). If you do, your AREV session will lose its ability to hold file locks and you will eventually corrupt your data tables (GFE's)
Under Windows 95, do all of your printer capturing (including CAPTURE SH) from a separate DOS window, not from a suspended AREV session. Or use the Win95 printer properties capture settings. You can also capture a printer port in a .BAT file which you run before starting AREV by specifying a Batch file under the AREV shortcut program properties.
Victor's "PDISK PRN" solution should work OK.
Jim