[LoneCrusader]

***UPDATED 12-18-2010***

I have managed to fix the 2.1GHz CPU limit of Windows 95.
Completely with updates from Microsoft... when they claimed there was no fix for this.

Here's a link to the MSKB article on this issue.
Q312108 - Windows Protection Error in NDIS With a CPU That Is Faster Than 2.1 GHz

--------------------------------------------------------------------------------------
Version 2.0 Released 4-23-2010

New in this version:

- The need for two different versions has been eliminated, Version 2.0 can be used on all Windows 95 versions. (95\95A\95B\95C)

- Fixed a bug wherein an updated file from the AMDK6UPD.EXE patch would cause floppy drives in Windows 95\95A not to be recognized properly.

- Version 2.0 can be installed before or after the "Windows Protection Error in IOS" has been displayed. (Before is still the preferred method.)

- Version 2.0 can patch a Windows 95 installation in directories other than C:\WINDOWS.

- Version 2.0 includes further updated versions of some system files contained in the AMDK6UPD.EXE patch, rendering AMDK6UPD.EXE obsolete.

- Version 2.0 includes PTCHCDFS, a free update by Rudolph Loew that corrects the displayed size of DVD media.

- Version 2.0 includes the DUN14-95.EXE update on the FIX95CPU.ISO CD image to further facilitate use on virtual machines.
--------------------------------------------------------------------------------------

The README.TXT from FIX95CPU.ZIP, provides a detailed overview of this project, this issues it addresses, and the instructions for getting it to work. I will post it here:

------------------------------------------------------------------------------------------

--------------------------------------------------------------------------------------
Windows 95 High-Speed Processor Support v. 2.0 By LoneCrusader
--------------------------------------------------------------------------------------

CONTENTS OF THIS PACKAGE:
--------------------------------------

README.TXT - Self Explanatory.

FIX95CPU.EXE - Self-Extracting Bootable Floppy Disk image.

FIX95CPU.IMA - A standard image of the Bootable Floppy.
(For Virtual Machines.)

FIX95CPU.ISO - A standard Bootable CD image.
(For Virtual Machines, or systems without a floppy drive.)

DUN14-95.EXE - Microsoft Dial-Up Networking 1.4 Update for Windows 95.
(Should be installed in Windows after Setup has completed.)

--------------------------------------------------------------------------------------


NOTE:

The first section of this README will explain the issues addressed by this patch. If you are familiar with these issues, you may skip to the second section for step-by-step instructions.



SECTION ONE:
-------------------

Windows 95 has two specific errors when dealing with processors with speeds higher than 350 MHz. With a little patience however, both of these errors are fixable.

The first error occurs with processors greater than 350 MHz. Microsoft released a patch for this error, AMDK6UPD.EXE. This patch IS NOT just for AMD processors. It will work for Intel Pentium 4 processors as well. The problem with Microsoft's patch is that it must be run from within Windows. When your system encounters this error, you will not be able to boot into Windows. This error will be displayed on the first reboot during the installation process.

Here is the text of the error:

While initializing device IOS:
Windows Protection Error. You need to restart your computer.

The only way to fix this error is to manually install the files contained in the Microsoft AMDK6UPD.EXE patch. This package automates the process for you, so I will not go into further detail on that issue here.



The second error occurs with processors greater than 2.1 GHz. This problem also affected Windows 98 (First Edition), and Microsoft issued a HotFix for Windows 98, but not for Windows 95. According to Microsoft, there is no fix for this problem in Windows 95... WRONG! This error is very similar to the previous one, and it will also be displayed on the first reboot of the install process, after you have fixed the previous error.

Here is the text of the error:

While initializing device NDIS:
Windows Protection Error. You need to restart your computer.

This error is corrected by updated files contained in the DUN14-95.EXE Dial-Up Networking 1.4 Update for Windows 95. This package automates the process for you, so I will not go into further detail on that issue here.

I strongly recommend that you install DUN14-95.EXE normally from inside Windows 95 when Setup is completed, whether you use Dial-Up Internet or not. This installer corrects the NDIS Windows Protection Error itself, however several other updated files for networking services are contained in the DUN14-95 update that cannot be applied by this DOS installer.



NOTE:
This update renders the AMDK6UPD.EXE patch OBSOLETE, as it installs newer versions of some system files contained within AMDK6UPD.EXE. While the main purpose of this update is to enable the use of High-Speed Processors, I decided to include any available newer versions of the system files already contained in this patch.


List of Issues (MSKB Articles) FIXED by this update:

Q192841 - Difficulties Using AMD K6-2 or Athlon Central Processing Unit
Q234259 - Revision to AMD K6-2/350 Central Processing Unit Update
Q312108 - Windows Protection Error in NDIS with CPU Faster Than 2.1 GHz
Q231942 - Cannot Undock Notebook Computer with LS-120 Removable Drive
Q175629 - Large IDE Hard Disk May Run In Compatibility Mode
Q274175 - Error Opening/Copying File/Folder Eight Levels Deep on CD-ROM

This update also includes a patched version of CDFS.VXD using PTCHCDFS, a free update by Rudolph Loew (rloew) to fix the incorrect size values reported by Windows 9X for DVD's. A bug exists in Windows 95/95A that causes DVD sizes over 4GB to not have their byte counts displayed properly, but the correct total size of the DVD will still be displayed.

Rudolph Loew has also created a free UDF filesystem driver for reading UDF formatted CD's/DVD's in Windows 95. It can be obtained from his site at {http://rloew1.no-ip.com} or mirror at {http://rloew.mysite.com}.

Many thanks go out to Rudolph Loew for his assistance with this project!



SECTION TWO:
-------------------

Follow these Instructions to get Windows 95 up and running.

You Will Need:

Blank Floppy Disk or Blank CD
Files Contained In FIX95CPU.ZIP

NOTE:
If your system does not have a floppy drive, the FIX95CPU.ISO Bootable CD image in this package can be used (with Nero or a similar CD burning program) to create a bootable CD that can be used instead of a floppy.

NOTE:
These instructions and the FIX95CPU installer assume that you are installing Windows 95 to C:\ Drive !!!


1. On another computer, use the self-extracting Floppy Disk image (FIX95CPU.EXE) or the Bootable CD image (FIX95CPU.ISO) provided in FIX95CPU.ZIP to create a custom Boot Disk that will contain this patch.

2. Prepare your system and run Windows 95 Setup.

3. When Windows 95 asks you to Restart, insert the Boot Disk or Boot CD that you created with the enclosed image, and click Finish. You should have the Boot Disk or Boot CD inserted BEFORE Windows Setup continues and the IOS error is displayed in order to speed up the boot process by combining .VXD's with WININIT.EXE, but this version allows for installation after the IOS error has been displayed.

4. The Boot Disk will start your computer in DOS mode, and you will be given an opportunity to view this README file. Choose Y or N, and then all you need to do is press SPACE to bring up the next page of the README, or to apply the patch. The program will output its actions to the screen so you can see what is being done.

Pressing CTRL-C at any time will terminate the FIX95CPU program.

5. When finished, press SPACE to reboot your system, then remove the Boot Disk or Boot CD so Windows 95 Setup can continue normally.

6. When Setup is complete and your Windows Desktop loads, run DUN14-95.EXE, and you will be prompted to restart. When your computer restarts, the DUN14-95 update will finish its setup operations and ask you a second time to restart.

7. When your computer restarts this last time, you have successfully completed this operation. Install the drivers for your hardware and your programs.

Have Fun!

--------------------------------------------------------------------------------------

KNOWN ISSUES:
-------------

1. If you plan to install the Microsoft USB Supplement to Windows 95 OSR2 (USBSUPP.EXE), be aware that this update will sometimes overwrite the file C:\WINDOWS\SYSTEM\VMM32\NTKERN.VXD without prompting you to keep the newer file already installed by this patch. If this occurs, the following error will be displayed:

While initializing device NTKERN:
Windows Protection Error. You need to restart your computer.

This can be corrected by recopying the NTKERN.VXD contained in this patch to your system.

--------------------------------------------------------------------------------------


LEGAL INFO:
-----------

THIS SOFTWARE IS PROVIDED FREE OF CHARGE WITH ABSOLUTELY NO WARRANTIES OR GUARANTEES.

BY USING THIS SOFTWARE, YOU AGREE THAT YOU USE IT AT YOUR OWN RISK AND OF YOUR OWN FREE WILL.

THE AUTHOR(S) OF THIS SOFTWARE SHALL NOT BE HELD LIABLE FOR ANYTHING RESULTING FROM THE USE OR MISUSE OF THIS SOFTWARE.

IF YOU MODIFY THIS SOFTWARE, PLEASE REMEMBER TO CREDIT THE ORIGINAL AUTHOR(S) FOR THE ORIGINAL CONCEPT(S).


--------------------------------------------------------------------------------------


This software brought to you by Conner McCoy (LoneCrusader) with assistance from Rudolph Loew (rloew).


--------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------

***UPDATE 12-18-2010***
Slipstreaming instructions added Here.

Microsoft issued a Hotfix for this problem in Windows 98 FE. It contains an updated version of NDIS.VXD that only works in 98. Apparently they forgot (intentionally? ) or never realized that the updated version of NDIS.VXD in the DUN14-95 update solves this problem as well.

Of course this isn't going to do you much good if Windows 95 drivers do not exist for your hardware. If you have version 3.40.1001 of the Intel Chipset INF Installation Utility, it still contains 95 Drivers covering the 845 chipset, which I know was used on motherboards supporting up to 3.06GHz processors.

The system used for this test:
--------------------------------------
Motherboard: Soyo SY-P4I845PE
Processor: 3.06GHz Intel Pentium 4 w/ Hyper Threading
Memory: 512MB Kingston DDR 333
Video Card: ATI Radeon 8500 LE 128MB
Audio & LAN: Onboard

[BenoitRen]

Nice. But why are you installing the AMDK6 patch twice? (once manually, once automatically)

[jaclaz]

Nice.



jaclaz

[BeatZero]

win95 working fine!
AMD Atlhon™ 64 processor 4000+ 2.40 ghz
mobo asus av8
512 ram

thanks LoneCrusader

BeatZero

[LoneCrusader]

BenoitRen, on Jan 25 2010, 09:11 AM, said:

Nice. But why are you installing the AMDK6 patch twice? (once manually, once automatically)

**EDIT 2-10-2010**
It does not appear to be necessary to do this. I have changed the instructions to reflect that.

BeatZero, on Jan 25 2010, 10:29 AM, said:

win95 working fine!
AMD Atlhon™ 64 processor 4000+ 2.40 ghz
mobo asus av8
512 ram

thanks LoneCrusader

BeatZero

Congrats, I'm glad someone else is interested and can confirm my results.
I might have to try my hand at making a "patch" that would automate some of this if people are interested.


Now if only RLoew's RAM patch worked in 95

This post has been edited by LoneCrusader: 10 February 2010 - 03:42 PM

[MDGx]

Very nice work...

[the_guy]

Can you just copy ndis.vxd at the same time the files from the K6-2 patch are copied over?

I'd test it, but I don't have access to a PC with a CPU over 2.1 GHz to run in Virtual PC.

[Fredledingue]

BenoitRen, on Jan 25 2010, 03:11 PM, said:

Nice. But .... (once manually, once automatically)

"Nice" that's all you have to say Ben?
I expected you to be more enthousiastic....

[dencorso]

Great work, LoneCrusader!
This thread is now added to the Important "Stickified" [Pinned] 95/98/98 SE/ME Topics.

[LoneCrusader]

the_guy, on Jan 28 2010, 12:36 PM, said:

Can you just copy ndis.vxd at the same time the files from the K6-2 patch are copied over?
I'd test it, but I don't have access to a PC with a CPU over 2.1 GHz to run in Virtual PC.

**EDIT 2-10-2010**
Incorrect information removed.
This is possible if you allow the IOS error to be displayed and allow VMM32.VXD to be compressed before copying the K62 patch + NIDS.VXD. (See instructions above.)

I strongly recommend installing DUN14-95.EXE normally when Setup is complete however, it contains several other updated system files related to Networking, whether you use Dial-Up Internet or not.

dencorso, on Jan 28 2010, 08:33 PM, said:

Great work, LoneCrusader!
This thread is now added to the Important "Stickified" [Pinned] 95/98/98 SE/ME Topics.

Wow
I never thought I would be worthy of that list. Thanks guys!

This post has been edited by LoneCrusader: 10 February 2010 - 03:45 PM

[MDGx]

I've uploaded the file here [2.78 MB]:
http://www.mdgx.com/spx/FIX95CPU.ZIP

[re-ZIPped using 7-zip, "shaved off" a few more bytes = smaller file size. ]


HTH

[LoneCrusader]

MDGx, on Jan 29 2010, 07:50 AM, said:

I've uploaded the file here [2.78 MB]:
http://www.mdgx.com/spx/FIX95CPU.ZIP

[re-ZIPped using 7-zip, "shaved off" a few more bytes = smaller file size. ]


HTH

Thanks MDGx

@everyone else:

I'm open to suggestions on how this "patch" might be improved, If some of you get to test it, please give me some feedback.

Good Luck!

[BenoitRen]

Fredledingue, on Jan 28 2010, 08:18 PM, said:

BenoitRen, on Jan 25 2010, 03:11 PM, said:

Nice. But .... (once manually, once automatically)

"Nice" that's all you have to say Ben?
I expected you to be more enthousiastic....

Well, I'm not affected by the 2.1 Ghz limitation, and don't plan on getting a faster processor or another computer any timle soon.

[BeatZero]

Hi LoneCrusader, MDGx, Dencorso
I built a Slipstreamer to implement this project automatically installing Windows 95.

"Folders iosubsys and vmm32"; Moved to CPUFIX.CAB all new files (*. VXD, *. PDR) and extracted from this, not the original Win95 .CAB's

"Ndis.vxd"; the script extracts the "net.inf" and changes, and "Ndis.vxd" is not copied during the installation, is also removed part of the REGISTRY, no more error: "Ndis.vxd missing...".
PS: DUP14-95 correct these changes after ...

"Client for NetWare Networks"; With a change in the "Netcli.inf", let the installation proceed without disabling this service...

"DUP14-95.exe"; Added in the Session "RunOnce" from "SETUPC.INF" (HKLM,Software\Microsoft\Windows\CurrentVersion\Run,Dun14-95,"c:\win95\Dun14-95.exe /q")
DUP14-95.exe is installed in unattended mode with Windows 95 Setup

will install the Windows 95 now?

prepare the hard disk
copy the "WIN95" folder from Windows 95 cdrom to "C:\"
copy CPUFIX.BAT, CPUFIX.CAB and DUP14-95.exe to the "C:\WIN95"
From the "c:\WIN95" type "cpufix.bat" and wait for the complete installation

Yes, restart


Uhoo!!


finished


Download CPUFIX: http://www.sendspace.com/file/enw21a
Download DUN14-95: http://download.microsoft.com/download/win...us/dun14-95.exe

give me some feedback

My System

Windows 95 4.00.950 B (Portuguese Brazil)

AMD Atlhon 64 Processor 4000+ 2.41GHZ
Mobo Asus A8v Deluxe
512 MB
Gforce 5200

This post has been edited by BeatZero: 29 January 2010 - 09:52 PM

[MDGx]

I don't have Win95 installed anymore so I can't actually test your scripts, but I took a look at the BAT file, and looks like it should do what it claims.
Good work.

Pls let me know if you want this new version uploaded at my site, eventually to replace the older one.
Until then, the new one is here [2.54 MB]:
http://www.mdgx.com/spx/FX95CPU2.ZIP
(also contains DUN14-95.EXE + your old README.txt).

You just need to update your ReadMe text file now.

HTH

[BeatZero]

MDGx, on Jan 30 2010, 02:59 AM, said:

You just need to update your ReadMe text file now.

HTH

ok, not really been very clear with my README, I am sorry for my bad English
but I'll edit soon ok, try to explain how it works in more detail

This post has been edited by BeatZero: 30 January 2010 - 12:04 AM

[rloew]

LoneCrusader, on Jan 25 2010, 12:15 PM, said:

Now if only RLoew's RAM patch worked in 95

I looked at the 1217 Version of Windows 95 VMM.VXD.
Making a Version of my Patch for Windows 95 looks doable, but requies more extensive modifications, since it was designed for even less Memory than Windows 98.
I do not have a Windows 95 Test Setup.

[LoneCrusader]

rloew, on Jan 30 2010, 01:09 AM, said:

LoneCrusader, on Jan 25 2010, 12:15 PM, said:

Now if only RLoew's RAM patch worked in 95

I looked at the 1217 Version of Windows 95 VMM.VXD.
Making a Version of my Patch for Windows 95 looks doable, but requies more extensive modifications, since it was designed for even less Memory than Windows 98.
I do not have a Windows 95 Test Setup.

I'll be your first volunteer
If you're willing to give it a shot, I'll test it as many times as you need me to.

I have copies of Windows 95 B and C, and the motherboard that I used for the processor test can use up to 2GB RAM. I have some boards that can use 4GB as well.

I looked at VMM.VXD in my 95C setup and I have version 1216.

**EDIT 2-10-2010**
Incorrect information removed.

VMM32.VXD was modified by the USBSUPP.EXE patch, it no longer has a Version tab and there are also VMM32.TMP and VMM32.o20, all modified/created on the day I installed that patch.

This post has been edited by LoneCrusader: 10 February 2010 - 03:48 PM

[MDGx]

LoneCrusader, on Jan 30 2010, 12:05 AM, said:

... there are also VMM32.TMP and VMM32.o20, all modified/created on the day I installed that patch.

Those are backup copies made by installs such as DUN14. Their purpose is to restore older versions of those files in case you decide to uninstall the newer one.

So if the new one works ok, you can safely delete the older backups.

HTH

[dencorso]

LoneCrusader, on Jan 30 2010, 05:05 AM, said:

I looked at VMM.VXD in my 95C setup and I have version 1216. VMM32.VXD seems to have been modified by the DUN14-95.EXE patch, it no longer has a Version tab and there are also VMM32.TMP and VMM32.o20, all modified/created on the day I installed that patch.

When a file that exists inside VMM32.VxD is present also in the %windir%/SYSTEM/VMM32 folder, the version in that folder gets loaded instead of the one packed inside VMM32.VxD.
Moreover, during the compilation of VMM32.VxD, windows strips the version info from the VxDs it'll then pack together, so that when you extract any VxD from inside VMM32.VxD, you'll get a file lacking the version info, although otherwise perfect and functional. So, a binary comparison with the original VxD is the only way to confirm the version of a VxD extracted from VMM32.VxD: if you compare it to the right original file, it'll be byte-by-byte identical, except for lacking the version info section. I use BeyondCompare to do it, but that's not a free software, so maybe you'll prefer to use some freeware alternative to it...
In order to see a list of all the VxDs inside VMM32.VxD (or extract some or all of them, if you so want) you'll need Clive Turvey's VxDLib. VxDLib can also repack files into VMM32.VxD (but this one feature I never did test myself)...
And to see what VxD are loaded and running in your system, in real time, you'll need the fantastic APSoft VxDView.
And, last, but not least, The Truth About VMM32.VXD is the best article about VMM32.VxD I've ever found, and much worthy of being read.