We are running AREV 2.03 on a Novell 3.2 network. The computers are Windows 98, Windows 95, and Windows 3.11. We are capturing our print queue to LPT1 in the login script, not through Windows. We worked out some bugs, and they can print their reports. However, they are supposed to print out 3 copies of each report and now the 3.x stations are only printing out 1 copy. The 98 and 95 workstations are working fine. The 3.x stations are running VLM.EXE ver 1.20 rev B. The other strange thing is that when I go to the workstations and type "CAPTURE SH", the 98 and 95 workstations show Timeout =35 sec and copies =3, but the 3.x stations show Timeout =10 and copies 1. The timeout in the capture statement in the login script is set to 10. It's as if something is overriding it. As I said, the 98 and 95 workstations are printing correctly (meaning, printing the appropriate number of copies as specified by AREV). The 3.x stations are not printing the appropriate number of copies.

Check the autoexec.bat in the 3.x machines

Dale

One of the FIRST things I did was to check the autoexec.bat. Could you be more specific as to what I need to check? There is no capture statement in it. I added the capture in the autoexec.bat and we still had print problems as previously indicated in another issue. Therefore, I removed it.

Is it possible that the Win3.x machines are reseting printer capture within Windows (i.e. saved capture settings) that are overriding what you have in system login script? Does it print 3 copies if you manually override prior to loading Arev ?

Tony

Add a capture command specifying one copy in a batch file that calls AREV.EXE, and switch the Windows desktop shortcuts on all workstations to use this batch file. Also check that the printer itself has no internal settings specifying multiple copies.

The Windows printer settings for the network print devices should be adjusted to specify one copy only.

If you get stuck then you can try (no guarantees) the Novell capture verb I wrote for RBasic - it's free and on my website. Call it twice in succession from the AREV login script. If you run this app on other servers then the Novell version function can be used to detect the network type automatically.

Steve

http://www.state-of-the-art.com.au

Thank you , I will try that

I checked the Windows settings. There are no capture settings in Windows. I killed any permanent settings that were being captured in Windows. They are capturing solely through the login script.

Actually, I guess I would need to call three copies in the batch file since they need to print three copies? Is that right? Would the batch file basically call AREV and then have a capture statement indicating the number of copies? Forgive my ignorance, but I am learning AREV as I go. I am in no way formally or informally trained on it.

Velice,

- this looks like a Windows setup problem and not an AREV setup problem, so ignore my advice to use the capture object from my website.

- it looks as though the Win 3.11 PCs (check their Print Manager setup, or printer setup via the "Network" icon) have different

capture settings specified.

- It may pay to disable Print manager (there is a checkbox for

this) on the Win 3.11 PCs and see if this helps (ie. one less

factor).

The 1.20B VLM is stable and reliable, but if you use ipxodi.com then skip the /ad parameters - they save memory but can mess up printing.

The batch file will look something like (assuming you use x:\arevpath for arev.exe) -

capture q=… ti=35 nb nff etc…

x:

cd\arevpath

arev.exe …

Just a guess, but maybe something in Windows is overriding the settings? The capture stuff in the printer set-up for instance. Been a long time since I loaded up a Win 3.1, but I seem to remember there being something there.

The Sprezzatura Group

[/i]World leaders in all things RevSoft[/i]

You may have multiple CAPTURE.EXE(s), do a find on all drives including local drives and remove the incorrect version.

View this thread on the forum...