NT install-locking up on file access (AREV Specific)
At 21 MAY 1999 11:05:35AM Jocelyn Amon wrote:
I have a client who is currently in the middle of switching from Novell to NT. I was informed of the change over at the last minute so was unable to research the correct method of installing Arev on NT.
We are currently running NT in test mode and have installed Arev. Mostly it seems OK but when a file has been written to a few times then it appears to 'lock up' when accessed later. Arev has to be killed off and restarted - break doesn't work. It appears to affect dictionary files mostly as these are written to by Arev sometimes when they are accessed.
On the advice of an Arev colleague I have selected LAN MANAGER in Arev as being the network. I was told the Revelation NT Service product is not required.
Other settings are the /X /M2048 on logging in and CONFIG.SYS is set to buffers=50, files=120.
After two days struggling with the problem with the NT engineer he has only just noticed that REV files are being left open, observed via the NT Service Manager Open Resources facility. This occurs even after Arev has shut down. I noticed that at least some of these files relate to files that are causing the lock up.
This is probably something that some of you have had happen before & I have checked for previous postings on the subject but can't find anything that relates to it. I also can't find anything on the Revelation site that is of help - what I have found is all related to the Revelation network product for NT.
Any help would be very much appreciated. We are running out of ideas and want to get this network bedded down ASAP.
Thanks in advance.
Jocelyn Amon
finsol@ts.co.nz
At 21 MAY 1999 02:55PM Tom Dunlop wrote:
Hi Jocelyn:
You might want to try this. Set files=200 in config.sys. Also, on the shortcut at the workstations, try setting EMS=4096. Hope this helps,
Tom Dunlop
Revelation Software
At 23 MAY 1999 12:17AM Kevin Gray wrote:
Think very seriously about installing the NT Service V1.5x
as without this you are tempting fate!
With the NT Service/NPP properly installed your system is more likely
to perform in a stable manner ALL OF THE TIME.
With work-stations available today you would be better advised to use
/X /M4096 in lieu of the 2048 setting.
Another important consideration is to run AREV in WINDOW mode rather
than Full Screen mode on the work station as this allows windows to
manage the desktop properly.
You should review the FAQ on running AREV under Windows.
Regards,
Kevin Gray
GRAYCORP
(email keving@graycorp.com.au)