Windows 2000 Memory Hog (AREV Specific)
At 17 JUL 2001 11:43:38AM Brad Clawson wrote:
We are running AREV 3.1 on an Novel 5.1 server and have begun to use Windows 2000 workstations as clients. It appears that the dos window running the arev app takes over all of the available memory. Is there a way to restrict or set the amount of memory available to arev?
At 17 JUL 2001 12:44PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
Do you mean memory or do you mean CPU utilisation? AREV is unlikely to grab all of the memory as it steals EMS and there are physical limits as to how much of this it can actually grab!
For CPU utilisation check out CPU Plus.
World Leaders in all things RevSoft
At 17 JUL 2001 02:11PM Warren wrote:
However in NT4.0 I have seen the NTVDM session that ARev runs under allocate as much as 32MB for some reason. Workstations with < 64MB would grind away very slowly due to the disk paging.
At 17 JUL 2001 03:09PM Don Miller - C3 Inc. wrote:
I've never seen this. How are you starting AREV? Typically the command line is AREV /M4096X. Check the properties in the shortcut to make sure that XMS is Disabled, EMS restricted to 4096, Protected Mode Auto, Uses HMA disabled. Check in CONFIG.NT to make sure that FILES=200, etc.
AREV's defaults are to allocate 1/2 of the EMS available to itself, although it can't use beyond 4096K. In a 128MB memory machine with nothing else running and without the proper switches set, it could allocate 64MB of combined memory, even though it can't use it.
Don Miller
C3 Inc.
At 17 JUL 2001 07:03PM Warren wrote:
I never did tease out the parameters behind this. But upping the system memory to 128MB seemed to make the problem go away. Tweaking the pif seemed to make little difference
I should correct my earlier post and say this would typically happen under NT 4.0 Server not WS. My guess that server protects the memory workspaces much more stringently than Workstation does thus consuming a larger workspace. Why it would grab up to 64MB is beyond me.
At 18 JUL 2001 08:53AM Don Miller - C3 Inc. wrote:
Warren..
I've don't normally run AREV on NT Server because it seems to have trouble with seeing it's local C: drive as a network resource (locking issues). I once had the NT Service go crash-boom when I did this. It had to be completely re-installed in order to set things straight. I suspect that you're right about the way NT Server protects the workspace, though. Just as a FYI, 256 MB memory on NT Server seems to be about right as a good performance minimum.
Don Miller
C3 Inc.
At 09 AUG 2001 03:17PM Sean Leyne wrote:
Don,
The solutions to that problems is to create a drive mapping which maps path to the 'network' drive.
We use this for our install a never have any problems running an Arev session on the server with other clients also connected.