JUST UPGRADED THE NETWORK FROM 3.12 TO NETWARE 4.11. USING AREV 3.12 AND NLM 1.12. WE HAD NO PROBLEMS IN NETWARE 3.12 BUT SINCE THE CHANGE, SUSPENDING FROM THE APPLICATION AND EDITING ANY DOS FILE WHETHER ON DOS OR WIN'95 WORKSTATIONS, DOES NOT ALLOW ME TO GO BACK TO AREV. PLEASE HELP AS SUSPENDING AND CALLING A COMMUNICATION SOFTWARE TO DIAL OUT IS AN INTEGRAL PART OF OUR APPLICATION PROCEDURE. THE CONFIG.SYS LOADS THE VLM.EXE ETC IN HIGH FOR DOS WORKSTATIONS. FILES ARE SET AT 50 AND BUFFERS AT 30.

ANYONE WITH ANY SUGGESTIONS PLEASE LET ME KNOW WHAT TO DO. APPRECIATE ALL THE RESPONSES.

(All CAPS is generally considered SHOUTING)…

Now to the problem… Does each user have his/her own AREV USERname? Is the problem with conflicts in the .SUS (suspend rollout files)? Since we know that all of OUR users have C: drives, we point our rollout files to C:\REVWORK. (This is fast, eliminates a lot of network traffic, and, eliminates the problems such as those you mention.)

On NT Workstation, under some situations, we get an "Error 4" on reloading AREV. This seem only to be be a minor nuisance.

If this is not relevant, specifically what error does AREV report if any?

Good Luck!

Re: ERROR 4 on NT after AREV suspends,

Try calling a batch file which calls your executable, then calls

as its last line, ERRLEV0.COM. At TCL, to create this file, perform the following:

EVAL OSWRITE \B8004CCD21\ TO C:\AREV\ERRLEV0.COM

It resets the DOS error level to zero. Then AREV doesn't trip.

Steve

Thanks Steve! That would have been the next thing I would have tried. I guess it helps to help others.

The error you describe will occur if

(a) you have the rollout.sus file set to a network drive

(b) you delete the rollout.sus file during a suspend

© you load a TSR program and forget to unload it during a suspend.

Steve

View this thread on the forum...