EMS, Windows XP, updates (AREV Specific)
At 19 JAN 2004 12:44:05PM Charles Milner wrote:
I've posted messages previously about getting EMS to work on PCs running Windows XP.
This is a new twist, and a possible warning about Windows XP updates.
I have 2 PCs. Both run Windows XP Home Edition. One is a 2.4 Ghz P4 with 512MB RAM. The other is an AMD K62 333Mhz. Until very recently both could run AREV (2.03) and use EMS memory.
But now, EMS is inactive on both of them. I use the 2.4 Ghz PC more often than the 333 Mhz PC for obvious reasons. So the loss of EMS could have been caused by some odd new driver, or new software. But the 333 Mhz PC is realy changed.
What they both have in common is that the Windows XP update function is enabled and set to automatic. So from time to time, they each produce a message saying that updates to Windows are available and ask me to install them. Which I have been doing. And now, I have 2 PCs which once could use EMS memory, and now cannot.
Has anyone had a similar experience? Does anyone know of a Windows XP update which somehow is either disabling EMS, or causing some other kind of memory interference?
At 19 JAN 2004 01:17PM The Sprezzatura Group wrote:
Don't know if this will help but it looks interesting!
http://www.columbia.edu/~em36/wpdos/emsxp.html
The Sprezzatura Group
World Leaders in all things RevSoft
At 19 JAN 2004 08:30PM C Mansutti wrote:
Are you sure you haven't added another peripheral to the PC?
For Instance:
If I have certain USB devices plugged in at boot up on my PC, EMS is disabled. If they are unplugged, EMS is enabled. I can then plug them in and I still have EMS.
I've Never had XP flavours affect the EMS.
Claude
At 19 JAN 2004 09:45PM Charles Milner wrote:
Thanks, that seemed to do it.
I removed the USB "memory" drive from the front USB ports on my PC, did a re-boot, and voila, EMS memory was re-enabled.
Interestingly, I left the USB devices connect to the back of my PC, and there was no difference.
So the windows updates were not to blame(!)