AREV printing in Windows (AREV Specific)
At 14 JUL 1998 04:48:15PM Don Bakke wrote:
What generally causes the problem where AREV print jobs don't get released until AREV is exited?
Windows 3.11
AREV 3.12
Novell 4.11
Printing to a local printer (LPT1)
Other workstations print fine
TIA,
dbakke@srpcs.com
At 14 JUL 1998 05:17PM Victor Engel wrote:
What print manager are you using? If a Netware print manager, it is probably the way the timeout for the auto-endcap is set up. You can find out the current settings by suspending to DOS and typing CAPTURE /SH. You can also edit the properties of your printer in Windows 95 to find the same information.
At 14 JUL 1998 05:18PM Victor Engel wrote:
I should have mentioned that it is possible to set up capture with an option to NOT autoendcap (NA, I believe).
At 14 JUL 1998 08:16PM Don Bakke wrote:
Hi Victor,
I'm not sure about the version of Print Manager, but I would have assumed the one that comes with Windows for Workgroups 3.11.
Aside from this, would the timeout be a relevant issue when this is printing to a local port? LPT2 and LPT3 are captured but LPT1 is always left alone.
Thanks for your help,
dbakke@srpcs.com
At 15 JUL 1998 05:20AM Tony Marler @ Prosolve wrote:
Donald,
Are you certain that LPT1 is local. As Victor mentioned suspend to DOS and type CAPTURE /SH to show current settings.
If so then try an turn off Windows Print Manager in Control Panel, Printers for LPT1 to get direct printing to port.
Tony
At 15 JUL 1998 09:30AM Don Bakke wrote:
Tony,
Are you certain that LPT1 is local. As Victor mentioned suspend to DOS and type CAPTURE /SH to show current settings.
Yes I'm sure.
If so then try an turn off Windows Print Manager in Control Panel, Printers for LPT1 to get direct printing to port.
This just might work, since I know that another workstation that does work has its Print Manager turned off. I'll give it a shot. Thanks.
dbakke@srpcs.com
At 16 JUL 1998 01:36AM Curt Putnam wrote:
The ENDCAP function can often be stimulated and/or simulated by doing:
PC EXIT VER ] NUL
At 19 JUL 1998 11:05PM Kevin at KPW wrote:
Don,
We had some print release problems with Win95 stations.
We changed our print procedures to perform an automatic
EXECUTE "SETPRINTER x" before and after print execution.
This triggered a printer reset which then eliminated our
particular problems.
Regards,
Kevin at KPW
email kpw1@compuserve.com
At 21 JUL 1998 05:44PM Mike Ruane, WinWin Solutions Inc. wrote:
Don-
Have you tried a PDISK PRN from tcl to see if it flushes the job?
If so, try a perform 'PDISK PRN' from your program's termination, from the voc word running rlist, etc.
Mike
At 22 JUL 1998 09:14AM Don Bakke wrote:
Hi Mike,
No, can't say that I tried that. I ended up disabling Print Manager in the meantime and that cleared the problem right up.
Thanks,
dbakke@srpcs.com