I've seen mentioned in other posts here that the maximum amount of expanded memory you can uses is 4MB.
Is this limit because of stability issues ?
I've had a few odd occurences recently on systems with 8MB of expanded memory allocated, and reducing the memory to 4MB "appears" to make these issues go away.
Thanks,
Michael Moran
The AREV code constrains the whole program to 4096 KB of expanded memory. So you'll see frequent posts here containing AREV /XM4096 or AREV /X /M4096.
It is best not to allocate any more than this for the reasons you describe.
Steve ..
If memory serves (and it sometimes doesn't), I recall that AREV will actually allocate more than 4096MB of EMS, but unfortunately, the address will "wrap" and then the data can get corrupted. I recall seeing a machine that allocated 16MB of EMS (out of 32MB) but the only thing that was valid was the page-frame. The 'X' switch which allocates both code and data into EMS produced really bizarre results.
Do you remember this as well?? BTW, I think this was in AREV 2.12.
Don M.
"If memory serves"
Is this expanded memory?
C'mon Vector
The topic is Expanded Memory .. mine seems to be contracting. I was just recalling something off the top of my head. Didn't go digging in my old yellowed papers to find out. I think it was discussed a long time on the old CompuServe forum.
Don M.
What's the command line switch for contracting memory?
If you work twice as many years as a contractor, do you have to double your contracting memory?
Oh, that it did. I've seen odd video corruption and all sorts of things. You gotta limit it down to 4M or some truly strange things will happen.
One of the things you can do these days, is fiddle with the registry and other settings and give it a bit more than 640K for the low memory.
The Sprezzatura Group
World Leaders in all things RevSoft