Hi all

I have AREV v3.12 and Win95 and Novell 4.x Lan.

We used to be able to print from AREV but the network techs seem to have deleted the crucial printer queue.

I have tried using other printer queues from the standard settings but I usually get messages like "printer offline"

I also get some other message that flashes up on the screen too quick for me to read it. Does anyone know a way of logging all the stuff out of the DOS Arev session so I can read it? Even when I go back onto TCL and re-execute the SUSPEND CAPTURE command I still can't read the response it gives.

So in our system we use a command that looks like

SUSPEND EXIT CAPTURE /Q=.LMS3-Q.MYBUILDING.MYDEPT /NT /NB /NFF /TI=0

which I understand to execute some sort of Novell command which should assign the printer after the Q bit to print my report. But LMS3-Q has been deleted, ie if you try to browse to it from win95 printer settings, it isn't there.

When I look in the Win95 settings for printers I do have, they have network paths something like

LPT1:(\\MYUNC\.PRINTQ0.MYSERVER)

When I substitute the .PRINTQ0.MYSERVER bit into the /Q= bit of the capture command I get various messages I don't get to read flashed up faster than Superman in a hurry or when I execute from TCL directly I get "This device does not exist on the network. error? Reading device, abort retry fail" and no printout.

What should I be sticking after the /Q= bit and how to I capture Superman's messages? and how do I find out more about making this stuff work?

Scott

LMS/Healthsolve

SUSPEND EXIT CAPTURE /Q=.LMS3-Q.MYBUILDING.MYDEPT /NT /NB /NFF /TI=0 ] FILE.TXT

Will send the output to the file named

Scott,

The /ti=0 causes the print job to not release until you exit the application(AREV). Try /ti=10 if you are printing through the network. If you are printing locally(LPT1), and are using AREV3.12

RUNMENU STARTUP

Options

Workstation

Hardware

Yeild time to Windows - Set to yes.

Hope this helps,

Dale Walker

[email protected]

Scott ..

You might also check to see if the bogus queue is being captured either in a login-script line or from the client desktop. Sometimes it is useful to run AREV out of a batch file that removes printer captures before the app starts (setting them to local mode) and then doing your own capture from within the app itself:

SYSPEND EXIT CAPTURE … statements from a VOC Login script

Don Miller

C3 Inc.

Hi All

Thanks for your help.

Our system, the way it executes the suspend exit capture commands wouldn't let me have a ]c:\temp\fred.txt to capture the output. Most annoying.

Eventually it was a combination of typing the queue bit correctly. I borrowed it from the details of the printer settings (pasted into notepad and printed out to increase accuracy). My first attempts I had got inconsistent hyphens and underscores (as on the network trees but that is another story). Strangely when I put the \\serverbit into /S= bit I got "please select a queue that is on the server" which was weird. But that was probably related to the second problem.

The omnipotent but not omniscient gods of networking had disconnected some of the printer queues, so while the queues were still accepting jobs, they were no longer associated with any physical printer. Curses. When I got one of the lesser network gods to help me find real printer queues I was fine.

I also found out some more stuff about the Capture command by entering Capture /? ALL from DOS. Well I never have been a novell guru.

So at least we have avoided the need to hang a printer off the back of a workstation.

I feel like a blind person in a room with the furniture being rearranged as fast as I figure out where it is.

Scott.

View this thread on the forum...