Small jobs print, large jobs don't, on NT workstations (AREV Specific)
At 17 APR 1998 04:37:12PM Jim Tassano [email protected] wrote:
We have AREV 2.12 on a small network (the workstations run Windows 3.11, and the server has W95), using Windows NT. The workstations do not print properly when printing a job of any size. Small jobs (e.g. print screens) run just fine, but reports of any size do not. They hang in the middle somewhere and resetting is often the only way out.
I have programmed in the option to issue, when bringing up the AREV program, the command "net use LPT1 \\fileserver\printername", and can use PDISK PRN to quickly send a small job to the printer. The large ones just stop, it seems. Windows applications print just fine from these 2 workstations.
Any ideas? Specifics?
Thanks,
Jim Tassano
At 18 APR 1998 09:09PM Mike Ruane, WinWin Solutions Inc wrote:
Jim-
Sounds like a timeout problem (no kidding, he says)
How about Pdisk-ing the reports to a local file, then send them to the printer. You can do this with a VOC word.
ie-
TCL
PDISK C:\MYREPORT.TXT
REPORT_PROGRAM
PDISK PRN
SUSPEND EXIT COPY C:\MYREPORT.TXT LPT1
It ought to work, it does for us….
Hope it helps-
Mike Ruane
WinWin Solutions Inc.
At 19 APR 1998 05:04AM Egbert Poell wrote:
PCPERFORM 'COPY …'
works much nicer.
No screenswapping!
Egbert Poell
Mecomp Automatisering
At 19 APR 1998 10:58AM Mike Ruane, WinWin Solutions Inc. wrote:
True-
although I really don;t notice a screenswap with the 'SUSPEND EXIT', it is usually pretty fast.
Also, doing a PCPERFORM makes the process co-exist with whatever memory arev is already using; SUSPEND frees up much more memory.
An alternative would also be 'PC EXIT..' but the same applies as PCPERFORM.
Mike
ps- How did you like the Interactive Arev/OI demo on our website?
At 25 APR 1998 07:13AM Aaron Kaplan wrote:
Are the printers (as defined through Win95) set to go to a queue/server or map through a port? When you set up the printers, it should say they are being used by MS DOS programs.
I know you said you're using Win31 stations, but you say you have a Win95 server on an NT network. Not really possible, since you'd need and NT server to have a NT network. Otherwise, it's a simple peer-peer/LANMAN type net.
Even if the jobs timeout though, they should send something to the printer, even if it's just part of it. Have you checked the spool paths on the server to see if anything ever gets written?
