Hi All
I recall that some time ago there was a fix posted on the Web for
the "IOS problem". I have lost the URL for this. (It was hinted that
it was scandalous that Microsoft knew about the problem but would
not provide the fix without a service charge.) Microsoft posts the
following about my problem:
"Microsoft has confirmed this to be a problem in Microsoft Windows
95 and OEM Service Releases. An update to address this problem is
now available, but should be applied only to systems experiencing
this specific problem. Unless you are severely impacted by this
specific problem, Microsoft does not recommend implementing this
update at this time. Contact Microsoft Technical Support for
additional information about the availability of this update."
Here's what the problem is:
After spending hours configuring a newly built computer yesterday,
and right before I was ready to make a backup, I got this message
after rebooting:
"Windows initializing device IOS: Windows protection error.
IOS failed to Initialize, Please restart."
Upon rebooting, I got "VMM32.VXD is required to run Windows.
If this file is not in your PATH, you may need to reinstall
Windows." I could only boot in Command Prompt mode.
After some finagling, I ended up where I would get get "VMM32.VXD
missing or corrupt" at boot, immediately followed by a Windows
shutdown message. VMM32.VXD was corrupt and I did indeed have to
reinstall. (It is not possible to replace VMM32.VXD because
Windows builds a custom version of this file for each system and
modifies the file as changes are made to this system.)
After doing a clean reinstall (disks newly fdisked and reformated)
this happended again. Microsoft says this happens with certain
software/hardware configurations. It is apparently a conflict
between VXDs that load at boot. (Of course, it could also be due
to a hardware problem.)
The system in question is a K6-2/400 using FIC VA503+ motherboard
with 128 MB of Micron EDO (SIMMs). There are no IDE devices...it's
using an Adaptec 2940 with 4 and 9 GB Fast SCSI-2 Narrow Seagate
drives, Toshiba 32X CDROM, and a Panasonic PD drive. Video is a
Matrox Mill 1, sound is a Creative SB AWE64, a Courier external
modem, PS/2 mouse, and a 300 Watt AT PS.
The system is Win98 but the scenario is exactly as Microsoft describes
for "the IOS problem" with Win95 OSR2. The KB articles were obtained
searching for "IOS and VMM32.VXD and Windows 98".
Thanks for any references or hints. The system is for a relative and
I cannot have this reoccurring every time a configuration change is
made. (What triggered it at first was installation of Office 97. The
second time it happened...after reinstalling...was when I formatted
a partitiom on the second hard drive.)
Regards,
Bill
PCSOFT's List Owner's:
Bob Wright<[log in to unmask]>
Drew Dunn<[log in to unmask]>
|
