On Thu, 20 Oct 2005, RichK wrote:
... After that win98 would not boot - error "While
initializing device IOS Windows Protection Error. Same in
Safe Mode. ...
I see Rick has already posted this MSKB, which has good
troubleshooting steps for that error:
<http://support.microsoft.com/?kbid=263466&sd=RMVP>
Error Message: Initializing Device IOS Windows Protection
Error
Or you may want to try the following to see if it provides a
temporary quick fix, and perhaps allow booting back into
Windows. The offending audio driver software can then be
uninstalled.
-boot to command prompt only
-edit the following files:
[rem out any lines related to
the audio *hardware* driver]
C:\config.sys
C:\autoexec.bat
C:\Windows\win.ini
C:\Windows\system.ini
-change directory -> cd C:\Windows\System\Iosubsys
-list the directory and rename any audio hardware driver
file(s).
Reboot and cross your fingers. :)
To tell the truth I have come across the error MANY times.
<VBG> It's a risk of tinkering with the system. Tweak it till
it breaks! Usually it's a case of "I wonder if it will run
faster/smoother/whatever with that beta/tweaked/whatever
version? <scratching head>". :) Only one way to find out...
Well sometimes stuff don't want to play nice. Luckly, with
Win98, we still have our old friend, *DOS* as backup. :) I
usually boot to command prompt only (DOS), then go explore
around in the C:\Windows\System\Iosubsys directory. Most of the
time, a file in that directory is the culprit behind this type
error.
Sort the file list by date, and the files Win98 normally
installs there will become apparent. It's the other files that
need to be looked at.
Tried to reainstall (dirty) Win98, but getting an error
"Standard Mode: Fault in MS-DOS Extender. I'm dead in the
water for now.
Maybe after some sleep I'll have more energy to fight this
this thing :-))
Here's a MSKB regarding the error. Hope you've had a good
nights rest. :)
------------------------------
<http://support.microsoft.com/kb/q87239/>
Bad Fault in MS-DOS Extender
This error message occurs when the fault handler dispatcher in
DOSX.EXE generates another cascaded fault while trying to
handle a protected-mode exception. This error is usually caused
by one of the following factors:
-HIMEM.SYS is unable to control the A20 line.
-DOS=HIGH is not functioning properly (related to HIMEM.SYS
control).
-The RAM, static RAM (SRAM), single in-line memory module
(SIMM), or dynamic RAM (DRAM) chips are not functioning
properly.
-You are running DR DOS.
-The third-party memory manager is not configured correctly.
-The EMM386.EXE NOEMS x=A000-EFFF line is missing from the
Config.sys file.
-You have an old, out-of-date ROM BIOS.
-Your CMOS settings are incorrect.
-Your Windows files are old or corrupted. To test this, create
a new directory on the hard drive, and install Windows in that
directory.
-Your disks are corrupted.
-Your system is infected with the Form, Forms, Noint, or
Yankee Doodle virus.
------------------------------
--
----------------------------------------
WIN-HOME Archives: http://PEACH.EASE.LSOFT.COM/archives/WIN-HOME.html
Contact the List Owner about anything: [EMAIL PROTECTED]
Official Win-Home List Members Profiles Page
http://www.besteffort.com/winhome/Profiles.html
