Memory Optimization For AREV (AREV Specific)
At 05 APR 2002 04:21:55PM Jim Dierking wrote:
I have been setting up a test server and configured a couple of new machines as workstations. Both have Win98SE2. One workstation has
378k of memory available according to "WHO" and the other only 241k.
The 378k machine shows expanded memory at the pif and at who. The 241k machine does not have any expanded memory. I checked config.sys
on both machines and there is no memory configuration there. Why
does one machine have expanded memory for AREV and the other doesn't?
TIA, Jim
At 05 APR 2002 05:34PM Don Miller - C3 Inc. wrote:
There have been several posts about this issue over the past several years. However, in AREV, you should NEVER see more than 4096 K of Expanded Memory. The command line should be AREV {appname}/M4096X. The shortcut memory choices should be EMS 4096, XMS None, Uses High Memory Area, unchecked. When you create the shortcut on the machine that doesn't show EMS in AREV, does the shortcut memory properties indicate that the machine is not configured to use EMS??? Make sure the CONFIG.SYS file does NOT use the NOEMS parameter on the EMM386 line and that HIMEM.SYS preceeds the EMM386 line. Compare the CONFIG.SYS and AUTOEXEC.BAT files on the two machines. Make sure they match the files of the one that DOES have EMS enabled. You might want to review the COMPAQ issues on this board too.
Don Miller
At 05 APR 2002 06:50PM Jim Dierking wrote:
Hello Don,
The memory I am referring to is the results of the "WHO" command at
TCL and the available memory amount. In this particular case both
machines have no config sys entries whatever. Is it possible to
have expanded memory without such parameters in the config.sys?
Also you made reference to COMPAQ issues. I am unfamiliar with this,
could you explain?
Thanks, Jim
At 05 APR 2002 07:22PM David Kafka wrote:
Jim,
I don't know why, but I do know that I've seen some Win98SE machines allow EMS without an explicit EMM386.EXE statement in CONFIG.SYS and others not. Every Win98 machine I've tried (no Compaqs) seems to be OK if you do set up config.sys.
I wish there was a solution for Win ME machines. Right now I have a client who has added a Dell notebook with ME to their network, and I haven't found a trick to enable EMS on it.
David
At 08 APR 2002 11:26AM Don Miller - C3 Inc. wrote:
In order for you to start AREV properly on a machine that has EMS (no matter how it gets it), use the line AREV /M4096X in the command line. Usually EMS is enabled in the CONFIG.SYS, but some versions enable it via a set of Registry entries. The reason to restrict AREV to 4096K or less of EMS is that the address space wraps around itself above 4096K .. making a mess. Note the X parameter above allows AREV to store both Code and Data in EMS. If you leave out the X, then only code will be located there.
To view the Compaq issues, do a Search on this site using COMPAQ AND EMS. David Kafka observes that there are some machines using Win ME and other operating systems that just won't enable EMS.
Don Miller
C3 Inc.
At 08 APR 2002 03:36PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Jim,
Sometimes Windows allocates EMS automatically, sometimes it does not. While there are ways you can modify the registry, it's easier to just add a CONFIG.SYS file to the offending machines. The commands and settings are the same as they've always been. All you need is the HIMEM and EMM386 entries. Windows will load the rest to it's defaults.
World Leaders in all things RevSoft
At 29 MAY 2002 08:11PM Eduardo Ortiz wrote:
Hi Jim:
I had the same problem (EMS) with Compaq PC's Deskpro EN, and the problem was related with a conflict between inbuit NIC and EMS. And I received support here. A Temp measure was desactivated de inbuit NIC and insert a new one, this fix the problem. But the optimal measure was to get one patch in compaq web page (SP19584) and the problem dissapeared.
Eduardo