[RESOLVED] Win95/98

[Clayton]

I have been receiving a "Windows protection error" message when shutting down in Windows 95 (it's happening also after a Windows 98 upgrade). This computer has an AMD K6 2 300MHz. I am aware of this problem and the fix for this CPU at 350MHz and Win95 (but not with the 300MHz with Win95/98).

The HDD is a Seagate and unfortunately has a drive overlay (OnTrack V 9.02. I don't know if this is part of the problem or not.

Any fixes/advice?

[ReBoot]

Time to dig out a full install of 98. The upgrade is a little buggy.
Try reinstalling win over top of itself. Should fix the error.

------------------
Who needs a life, I have Internet!

[Darren Wilson]

what sound card do you have???

It is known that some MIDI configurations on sound cards can conflict by using the same address as the busmaster drivers.

[Clayton]

It is on-board sound (an Amptron motherboard). Device Manager indicates drivers for CMI8338/C3DX PCI Audio. The MIDI driver is a DOS Mode MPU-401 Emulator. ???

I'll try disabling it and see what happens. Thanks for the input from both Darren and reboot!

[Clayton]

Well, I tried both suggestions. Neither stopped the Windows Protection error from recurring. When I installed Win98 from a full version, I couldn't get a full restart/reboot. So, I uninstalled. I'm back to a "functioning" Win95 but still have the error on shutdown. More ideas? Thanks for your help!

[Darren Wilson]

try updating the drivers for your sound card form http://www.pcchips.com and select the M598 fo rthe correct drivers.

[CharlesB]

Have you tried bypassing the startup programs as Win95 comes up? There could be a utility that is running that could cause this kind of a problem. When the system boots up wait until you see the hourglass of Win95 come up and press the shift key (does'nt matter which one). This will bypass the Startup group and the programs loading from the win.ini file allowing for a mostly clean boot into Win95.
I say "mostly" because there are some programs that may come up that are not part of the Startup group but this should hopefully keep the program that is causing the problem dormant if there is a program that is doing it. And while you're at it you may want to keep the config.sys and autoexec.bat files from running by renaming them by typing ren config.sys *.t00 (I use t00 as there may already be a config.bak). Try this and hopefully it may work for you. http://www.windrivers.com/cgi-bin/forum/smile.gif