Initializing device IOS: Windows protection error.

[G0AOZ]

Been asked to put WIN95 OSR2 onto a Clevo notebook running a 2GHz Celeron. Get this well known error at startup, whether in normal or safe mode. This is what I've tried so far:-

1. REMing out virtually everything in CONFIG.SYS and AUTOEXEC.BAT files.

2. Tried deleting the RMM.PDR file in the IOSUBSYS sub-dir.

3. Tried running this installation on another machine and then loading IOSUPD.EXE (version 174,672 bytes 27-Aug-97). N.B. File seemingly cannot be run other than in Windows.

None of the above appears to make any difference. I was told that when IOSUPD.EXE was run, it would produce IOSFIX.EXE and RMM2UDP.EXE together with some explanatory .TXT files. No sign anywhere on the disk of the .EXE or the .TXT files.

It has also been suggested that selecting "Logged" from the Startup Menu would enable the BOOTLOG.TXT to be examined. I have selected that option, but cannot find the file anywhere. I assume the boot process never gets far enough along to start producing this log - is that correct?

Any further thoughts at all please...?

ROGER - G0AOZ.

 

[wolluf]

Does it have to be 95?

Can you disable any hardware in the bios (never done this on a laptop/notebook - but have had success installing with reduced hardware set on desktop when 95 & 98 have given that error)?

You may just be out of luck of course - 95 being too old to cope with the hardware.

 

[G0AOZ]

Dunno why, but yes it has to be 95. Tried disabling hardware in the BIOS - makes no difference. Just out of curiosity I ran the AMD fix and that changes the message to just a plain ol' "Windows protection error". So I've lost the IOS initialization failure, or have I?

ROGER - G0AOZ.

 

[micker377]

What OS is on the laptop now? Is the OSR2 a "Full" install, or an "Upgrade" for Win 95?

 

[G0AOZ]

Disk was wiped prior to a brand new full install of OSR2. Installation process went through fine up until the first "reboot", then the error message occurred. Ran some hardware diags which confirm machine is running fine, and it will also run XP Pro ok. The "Windows protection error" message comes up irrespective of selecting normal and safe mode.

ROGER - G0AOZ.

 

[G0AOZ]

Problem now solved...

Discovered the BOOTLOG.TXT file is hidden and in the root directory. This showed SETVER.EXE was the first problem the system encountered. Knocked that out, then found HSFLOP.PDR also caused a hiccup. Renamed that, and system booted up ok. Not the end of the story though... System hung when trying to close down. I found that running the AMDK6UPD.EXE utility from within Windows solved the problem, and of course remembered to get rid of the HSFLOP.PDR which had been generated again.

ROGER - G0AOZ.