Simple print hangs program (AREV Specific)
At 17 NOV 1998 01:10:28AM James Barrett wrote:
For many years, a 16 user AREV1.x system has performed smoothly thru
many hardware generations & Novell upgrades. Printing to local or
network printers was never a problem. The current workstations are
Zenith pentiums running W95 version B. AREV1.X has run them for the
last 14 months. After converting to AREV 3.12, a simple List … (PE)
command freezes the program if W95 is set to print directly to the
local printer. If the spooler is used, it 'works' the disk for 9-10
seconds & finally prints. What could have changed between 1.x & 3.12
to impact LPT1 so drastically? (The problem happens either with or
without network drivers loaded.)
At 17 NOV 1998 02:59AM Curt Putnam wrote:
I suspect that you need to bypass the W95 spooler and associated print drivers if you can. Printing with Arev & W95 always crashed by HP driver - W98 is much better.
At 17 NOV 1998 11:40AM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura, Inc.[/url] wrote:
Only thing I can think of was a change in how the logical PRN port was opened during initial setup of AREV.EXE to handle the effects of SHARE.EXE.
I don't know exactly how this would impact the system, but I can see it making some difference.
At 18 NOV 1998 04:55AM Steve Smith wrote:
Sounds like a printer initialization problem (clash). These are my guesses.
Choose a printer port you do not normally use, eg. LPT3
Try running a PDISK LPT3 (S) at application startup. At the same time
from DOS run
CAPTURE Q=myqueuename TI=5 NB NFF L=3
ahead of your AREV session (use a batch file), and see if that helps.
Otherwise, run PDISK PRN at application startup.
I have had local printer drivers (especially ones with spoolers permanently loaded) under Win 95 interfere with LPT1 and AREV.
Good Luck,
Steve
At 18 NOV 1998 09:32AM Larry Wilson wrote:
It has to do with the way AREV closes the print file. Some time back, there was a program called NOTHING.EXE (Steve Smith's I think), and afer the print job, doing a PCPERFORM of NOTHING would close the spool file and cause the system to print immediately. To check this out, right after you print, logout of AREV, and if the printing starts right away, that's the problem.
There's a similar problem on NT, but I haven't worked on it to find the fix yet.
I think I have NOTHING around here somewhere (can one, really, find NOTHING?) . If you need it, email me. I will also post it on my DOWNLOADs page on my website unless the author (whomever that is) objects.
Larry
At 18 NOV 1998 11:32AM Victor Engel wrote:
Do you really need a NOTHING.EXE file? I use a NOTHING.BAT file whose contents consist of the single line:
REM
At 18 NOV 1998 02:51PM Steve Smith wrote:
I use ERRLEV0.COM
AT TCL, perform the following:
EVAL OSWRITE \B8004CCD21\ TO C:\AREV\ERRLEV0.COM
It's good to see that some days, other developers get nothing done
Steve