Revelation User Suspend Problem (AREV Specific)
At 05 JAN 1999 09:44:54PM Victor Engel wrote:
We have been experimenting with setting up the NLM to use the REVELATION user for added security. I have found a new problem that does not exist with the normal access mode. If you suspend and then change directories, the system will go berserk when returning (ERRMSG, etc.). I seem to recall that this also happened in version 1.X of Arev, although I don't remember exactly when the problem was resolved. The resolution is simple: always make sure you go back to the revboot directory before exiting from the DOS prompt. However, it would take some getting used to. I don't know if there are other users besides me who use SUSPEND or PC, so it may not be an issue for the users. However, the problem is worth noting.
At 05 JAN 1999 09:48PM ed wrote:
Before moving to win95 clients I use to to that quite frequently. As I recall we never (or hardly ever) had any problems. In win95, because of the suspend/locking problem. we don't ever suspend or pc out of Arev. We have developed another way of handling those requests.
At 06 JAN 1999 01:30PM Victor Engel wrote:
Same here. In fact, I shelled SUSPEND to prevent users from suspending unless they did so from DOS.
At 07 JAN 1999 12:18AM Curt Putnam wrote:
To what suspend/locking problem are you referring?
At 08 JAN 1999 08:32PM ed wrote:
On Novell networks using some of the early versions of the MS client for netware, when you did a PC or SUSPEND to get to dos to run some other program and then returned to AREV, record locking would no longer work. therefore, users could be editing the same record assuming they had exculsive use of it. more troublesome was that since locking was not working correctly, GFE's would occur almost immediately.
So the best solution use the NLM,
next use Novell Clients or both.