Lock-up in Win 3.1 (AREV Specific)
At 08 DEC 1997 09:00:40AM C.Miller wrote:
I know this has been discussed before, but I can't find the
earlier discussion of it.
The situation is a Novell network with Windows 3.1 workstations
and AREV 2.12. No NLM (which to my understanding is not required
anyway). This system experiences frequent seizures on AREV,
but not in the other applications on the network. The seizures
are sometimes accompanied by reported "Indexing transaction lock
etc…" messages, and when it happens, all of the AREV workstations
are frozen. The problem is usually cleared by logging all of the
workstations out and logging them back in.
Again, what are the Windows 3.1 or AREV settings necessary to
prevent this frequent seizure?
At 08 DEC 1997 10:20AM John Duquette wrote:
Hi,
What your problem sounds like is that you are suspending arev by backgrounding the application. You should check the pif settings for the application (on the second page of the arev.pif there is a check box for always suspend, make sure its not checked)
Also make sure you have allocated adequate files for the application in the config.sys
One more thing you might consider. The lockups appear to be on indexing so you might want to setup a dedicated indexer.
John Revelation