I'm trying to install Windows 95 (version 4.00.950) Slovenian and whenever the computer restarts after the installation, it greets me with the fammiliar, yet so annoying message "Windows protection error. You must restart your computer.". I applied the FIX95CPU patch according to the instructions provided, yet not success.

On the other hand, the same error appeared on build 1111 (also Slovenian) and the patch fixed it. I tried various installation settings but I can't get it to work normally, only in DOS mode, through which I can't install the damn 1.4 networking update that is said to fix this error.

Any help?

are you using real hardware or a virtual machine?

Microsoft Virtual PC 2007 SP1. A VM with 64MB of RAM, 500MB VHD, network and HAV are turned off.

does not happen with me, I suggest you use VMware in 5.x mode for it, since the protection error does not happen there then.

I'm trying VirtualBox but the VM freezes when booting from 98 SE bootdisk with CD-ROM support...

EDIT: Fixed the freezing part but CPU fix still doesn't work...

for the FIX95CPU fix, make sure after you've applied the fix you use the original ESDI_506.pdr driver from the original build (in this case, Win95 Slovenian 4.00.950) and the floppy driver (HSFLOP.PDR) from Nashville Build 999

Disable hardware virtualisation in VPC

he already did it.

When I developed FIX95CPU I had no copies of 95 RTM or 95A to test on. I received (and still receive) reports that it does work on those versions, but the other day I had a report on another forum that it does not. And now here as well. I plan to do some further experimenting and testing, if I can manage to find the time...

I am not sure if you tried This, maybe yes but if not, you can try

That particular post was about an experimental method of "slipstreaming" the updated files. It did NOT work as intended. The OP's current problem is related to the fact that he is using 95 RTM, not 95 OSR 2.x.

@The Distractor: in case you've noticed, I said they're turned OFF.

@LoneCrusader: Exactly. The fix does not work on build 950 (RTM), but works on build 1111 (OSR 2.1). Anyway, I'll try to figure something out...

for me it worked on the RTM build (4.00.950)