We have an AREV 3.12 / DOS problem on a 16 workstation system NT sp4, NT Service, with win98 workstations. We think it may be a timing problem so we are running the workstations at 10mhz v. 100 and that helped half the workstations running in the same building as the server. The other half of the workstations are connected by fiber and are still having lockups. When it happens one workstation goes first then all in the same building go. It appears to be a dos problem because we get the dos message "Fatal error reading drive …. etc. abort retry fail". We cannot recover by keying 'R' and have to kill the dos session and restart the Arev app. Other programs in windows are not affected or recover without locking. We have set the dos properties to expanded memory=4096, extended memory=none, background processing=not checked (enabled), and idle sensitivity to near low. Any other ideas would be appreciated.

[email protected]

I have seen NT time out some workstation connections when their activity halts for a timeout period (usually 10 minutes). There are disconnection timeout parameters set in either the workstation registry and in the server registry. Try increase these (search on Conn or Disconn).

One solution I tried was a background task (written in VB) to write a small file (containing the system date/time) to the server very few minutes. Surprisingly this method worked, and kept the connections open.

I have published the articles here in the forums some time ago (about Jan 1999 ?)

Steve

Jim

Is there any chance that there is a 3D screen saver cutting in on the NT server. Seen all sorts of problems with this & NT Service.

Tony

That error is generally characteristic of lost network access. You didn't mention whether all access is lost to the AREV drive, or only AREV's access. If the former, it could be any sort of network issue, like hub lockups, 10/100 buffering problems, etc.

View this thread on the forum...