Win95, Novell and...PDISK? (AREV Specific)
At 08 JAN 1998 02:04:49PM David Rysdam wrote:
For many years we generated/printed reports using the following basic algorithm:
do novell capture cr=filename l1
generate report and print to lpt1
endcap
nprint filename q=queue
When we moved to Windows 95 (using the MS Novell Client) we found that this no longer worked. After much research we determined that the "capture" command didn't work normally with the MS Novell Client. Because of reported instability with Novell's Client32 we didn't want to use that.
We had written an AREV capture wrapper function to the Novell capture program, so to overcome the above problem I re-wrote the wrapper. Now, if the capture is to a printer nothing changes, but if the capture is to a file it issues a pdisk filename. Then in the endcap wrapper I do a regular Novell endcap and a pdisk prn.
We have given some of our users access to a pair of programs we call "StartReport/EndReport". Here's the basic idea behind that:
User issues StartReport (printer options)
User does a list criteria, etc (p)
User issues EndReport (print queue name)
Inside the StartReport is buried a capture to file (meaning that in my modified capture we do a pdisk) and inside the EndReport is an endcap (now a pdisk prn) and a Novell nprint.
Here's the problem: Occasionally, a user will do a StartReport/EndReport and attempt to exit AREV and the machine will lock up on the way out. A power-cycling is necessary.
Unfortunately, the problem is not reproducible on command. But we DO know that it's something with the Start/EndReports because we've had many instances where that was all the user did while in AREV.
Any comments?
I can be reached by responding to this item or at [email protected]
At 08 JAN 1998 04:54PM Victor wrote:
A power-cycling is necessary.
At least you'll get some good excercise.
At 09 JAN 1998 09:24AM Aaron Kaplan wrote:
Besides that Client32 seems to be working better, at least with later releases, it could be that the same issues that are affecting CAPTURE are affecting NPRINT. Why not just try a standard print file ] lptx?
At 09 JAN 1998 06:02PM David Rysdam wrote:
I can't just print to an lpt because I'm not capturing them to print queues.