I'm wondering if any of you have come across this one. At one location with about 20 PC's, 2 of them seem to be having this problem. When the workstation is left idle for some time (???? we're trying to pin the time down), ARev 'locks up'.

I'm thinking it may have something with the keep alive packets for the NLM. NLM_STATS reports version 1.10 for both the server and client (although I thought I had installed 1.12 for the TSR). It's a Novell server 3.12, these are Win95 workstations, configured the same way as everyone else.

Is there a setting we may be missing, an upgrade we need (although I don't know why only 2 workstations are involved if that's the case)???

Any ideas, comments, things to look at . . . would be appreciated.

Thanks,

Jeff

Jeff,

Did you check the shortcut properties for the program? Maybe windows is stealing timeslice due to idleness, or is not allowing it to run in the background (which, if compounded with a third-party screensaver, could be bad).

-Scott

We did check shortcuts, 'suspend background processing' is not checked, screen savers have been turned off. I actually had one user run ARev with nothing else running, and she continues to experience the problem.

You could always try lowering its idle sensitivity. If it's Win3.11, you could also disable the OS from detecting idle time, and you should make sure the TSR is being loaded before windows is loaded.

If it's Win95 (or if it's 3.11 and the above check out ok), try putting a /r:16 and /c:120 at the end of the TSR line as parameters (did I already say that?).

-Scott

Also make sure that some power feature is not kicking in and disconnecting you from the network. This would appear as if the machine is locked. We had this problem on a coupleof machines that would lock up after 15 min of idle time

IF YOU ARE RUNNING THE NLM THEN PUT THE /P PARAMETER AFTER THE LHIPXTSR ON YOUR WORKSTATIONS. THIS SOLVED THE PROBLEM FOR US.

View this thread on the forum...