Re-mapping Memory for EMS to run AREV V3.12 (AREV Specific)
At 23 JUL 2001 03:47:48AM kevin gray wrote:
IBM have advised that Yes there is a problem with gaining EMS on
their ThinkPad X20.
Our client was told to have their software people re-map the memory
to make EMS available because for just one PC they will not do it!
This begs the question ….. how to achieve this on a laptop?
We previously had to perform memory mapping on an Osborne PC (that
was in 1995 though) but we are not confident in performing that task
on a laptop with all of its related PCI/MCIA issues.
Has anyone had any success here?
Kind Regards,
Kevin Gray
Graycorp
(email kevin@graycorp.com.au)
At 23 JUL 2001 07:04AM Joe Doscher wrote:
Kevin;
I have a WinBook Laptop. When I first got it I could not get EMS and was told my the company EMS was not supported. However, after loading HIMEM.SYS and EMM386.exe in the config.sys file (Win98 os) and then using the /M switch's different values for EMM386 I finally had EMS active.
Hope this helps.
JoeD
At 24 JUL 2001 02:15PM Donald Bakke wrote:
Kevin,
Based on Joe's suggestion I began experimenting with the different M parameters. The valid entries are M1 through M14 (although 10-14 are for computers with 512K of memory.) I tried them all and M5 is the only one that seems to work. I still get a warning message when the machine loads EMM386 but I haven't noticed any problems otherwise. Here is my CONFIG.SYS settings:
device=c:\windows\himem.sys
device=c:\windows\emm386.exe 4096 m5
dos=high,umb
Hope this works for your ThinkPad.
dbakke@srpcs.com
At 24 JUL 2001 06:58PM kevin gray wrote:
What I should have advised is that the operating system is Win 2000
Professional so the emm386.exe method is inappropriate.
This is still a critical issue for the client as no standard settings
make any difference so we have to attempt to include and exclude
memory address ranges and we are not at all happy to do that.
Has anyone been successful in this process?
According to IBM there is a conflict with the network card within the unit that blocks EMM.
Regards,
Kevin Gray
At 24 JUL 2001 09:01PM Donald Bakke wrote:
Kevin,
Sorry for being a little dense, but why is EMM386 innappropriate for Win2000? I know NT-based stations have to be editted a little differently (CONFIG.NT versus CONFIG.SYS I believe), but I thought they still used the expanded memory manager to emulate EM.
dbakke@srpcs.com
At 25 JUL 2001 05:15AM kevin gray wrote:
Don, I am definitely the dumb one ……
Given the circumstances of the case what would be the settings that
we should use to make EMM available?
Very uneasy about this …..
Regards,
Kevin
At 25 JUL 2001 09:48AM Donald Bakke wrote:
Kevin,
I'm pretty sure that you take the configuration that I posted previously and put that into your CONFIG.NT file. If it doesn't already exist then simply create one. You might have to play with the "M" parameter like Joe suggested. However, I'm assuming that the A20 that you are trying to configure and our A21's are really the same machine so "M5" might be the first option you try.
dbakke@srpcs.com
At 25 JUL 2001 04:47PM Warren wrote:
The default config.nt file in the System32 folder should be annotated as to the settings for EMM.
See also the Micrsoft Knowledge Base article on Debugging MS-DOS program problems on NT/2000 which I posted a link in a reply to you in an earlier thread on Win2000 started by yourself.