- Oct 11, 2002
- 46
- 0
- 0
When I boot my computer at home, it gets through the POST sucessfully, displays the Windows logo, then goes to a black screen with the message:
While initializing device IOS:
ERROR: Real mode system memory allocation failed.
It will go into safe mode. Scanreg and scandisk do not show any errors. Also, no errors were found using the Norton tools that are available in safe mode. I reinstalled the OS (Win98) from a restore disk. I still get the same error.
I cannot for the life of me think of anything I did that would cause a problem. Last night, I was doing some basic web browsing, copying some CDs using Nero, and doing some downloads. Specifically, I downloaded some WinXP drivers (from manufacturers, ATI, canon, microtech, etc) in antipation of an upgrade, and I downloaded some Pocket PC nursing software for my wife. When I put the Pocket PC in the cradle, Active Sync screwed up and the machine froze. When I rebooted, I got the above error.
Could active sync be causing this problem? Would I reinstall Active Sync to correct it?
Could this be a hardware problem with the actual stick of memory?
Any suggestions?
While initializing device IOS:
ERROR: Real mode system memory allocation failed.
It will go into safe mode. Scanreg and scandisk do not show any errors. Also, no errors were found using the Norton tools that are available in safe mode. I reinstalled the OS (Win98) from a restore disk. I still get the same error.
I cannot for the life of me think of anything I did that would cause a problem. Last night, I was doing some basic web browsing, copying some CDs using Nero, and doing some downloads. Specifically, I downloaded some WinXP drivers (from manufacturers, ATI, canon, microtech, etc) in antipation of an upgrade, and I downloaded some Pocket PC nursing software for my wife. When I put the Pocket PC in the cradle, Active Sync screwed up and the machine froze. When I rebooted, I got the above error.
Could active sync be causing this problem? Would I reinstall Active Sync to correct it?
Could this be a hardware problem with the actual stick of memory?
Any suggestions?