EMM386.exe Locking AREV (AREV Specific)
At 06 JUN 1998 09:31:36PM Robert Popoff wrote:
I have a new Gateway Notebook which like all our workstations, we create a DOS Icon to start Arev applications using Windows 95 clients. This new notebook will hang if we use the emm385.exe 2048 when starting arev. Any suggestions? Our config.sys looks like:
DOS,UMB
device=c:\windows\himem.sys
device=c:\windows\emm386.exe 2048
Have tried putting in a SETVER.exe as well. No better. When I remove the EMM386.exe, the application starts up fine. But they need the expanded memory. Thanks
At 08 JUN 1998 03:45AM Egbert Poell wrote:
You should add the word "RAM" like
device=c:\windows\emm386.exe RAM 2048
You can omit the 2048 if you want.
Good luck
Egbert Poell
Revelation consultant
Mecomp Automatisering
At 09 JUN 1998 08:02AM Robert Popoff wrote:
I put the RAM in the statement and got the same results. Have any other suggestions?
At 10 JUN 1998 11:45AM Jim Jefferson wrote:
Robert:
You shouldn't need to use the EMM306.EXE in CONFIG.SYS if you're running Windows 95. Search the Knowledgebase on this site and you will find information on configuring a shortcut properly.
Essentially, though, you will want to change the properties on your shortcut under the Memory tab. Set EMS to 4096, and set XMS to "None". This should take care of your problem.
At 13 JUN 1998 02:04PM Aaron Kaplan wrote:
You shouldn't need to use the EMM306.EXE in CONFIG.SYS if you're running Windows 95.
Not always accurate. Some Win95 machines (like my late, lamented laptop) and my old 486/66 required it. My P2 does not. The Compaq I had might have, can't remember it all. Think it's related to build issues with Win95, but not all workstations load EMM386.EXE at load up. If the EMS option is availble on the shortcut, you're fine. If not, you have to load it and HIMEM.SYS in your CONFIG.SYS instead of relying on the system default one.
At 13 JUN 1998 02:06PM Aaron Kaplan wrote:
What's the command line for ARev?