Sign in to follow this  
Followers 0
Petr

Windows 95 unofficial patches

14 posts in this topic

Hi,

I have tried to create the patch for Q312108 - Windows Protection Error in NDIS with a CPU That Is Faster Than 2.1 GHz since Microsoft stated that

Microsoft has no plans to make an update available for this problem for Windows 95 because Windows 95 is in the "non-supported" phase of the product lifecycle.

It is possible that the problem was resolverd in ndis.vxd 4.00.1113 that is part of Windows 95 Dial-Up Networking 1.4 Upgrade - it is in msnet95.cab

Just to be sure I have backported the code from 4.10.2000 version in original Q312108 hotfix to 4.00.1113 and created version 4.00.1114.

I have also patched the code in 4.00.950 version and created 4.00.951 version.

This file can be easily manually replaced but backup the original file in case of anything unusual.

Here are the files:

NDIS.VXD 4.00.951 for Windows 95, Windows 95 SP1 and Windows 95 OSR1

NDIS.VXD 4.00.1114 for Windows 95 OSR2.x

NDIS.VXD 4.00.1113 extracted from DUN 1.4

If anybody is able to test Windows 95 on >2.1 GHz system and Windows have the problem described in Q312108, i.e. "While initializing device NDIS: Windows protection error" during boot, please test these files if they really cure the problem.

Petr

Edited by Petr
0

Share this post


Link to post
Share on other sites

Q192841 - Difficulties Using AMD K6-2 or Athlon Central Processing Unit update for AMD processor with 350+ MHz (amdk6upd.exe package) is for Windows 95 OSR2 only.

I remember that some time ago I had problem with esdi_506.pdr and scsiport.pdr on Windows 95 (original) so I patched them the same way as the OSR2 files were patched. Here are:

ESDI_506.PDR 4.00.957 (patched 4.00.956)

SCSIPORT.PDR 4.00.952 (patched 4.00.951)

It is possible that even the 4.00.1119 and 4.00.1112 versions will work in original Windows 95 but this is just to be sure.

It is hard to say what is correct, Q153471 has ESDI_506.PDR 4.00.954 for Windows 95 Gold and 4.00.1116 for Windows 95 OSR2, but in Q252215 the 4.00.1116 ESDI_506.PDR is intended for Windows 95 Gold. Rather confusing.

If anybody will encounter any problem with additional files in Windows 95 original, i.e. Hsflop.pdr, Cdfs.vxd, Disktsd.vxd, Int13.vxd, Ios.vxd and Vfbackup.vxd please let me know and I will try to patch them too.

Petr

0

Share this post


Link to post
Share on other sites

I feel some deja vu.

Several mothns ago i've downloaded 'Unofficial Windows 95 modern processors update' from some OSBA server.

I had a lot of modified VXDs.

If i'll find them on my PC i'll upload them somewhere.

0

Share this post


Link to post
Share on other sites
It is possible that the problem was resolverd in ndis.vxd 4.00.1113 that is part of Windows 95 Dial-Up Networking 1.4 Upgrade - it is in msnet95.cab

no Petr. 4.00.1113 of ndis.vxd does NOT fix the Q312108 problems under ANY version of Win95. Win95 has other missing functions or "dependencies" in their VXD and DLL files that were included in Win98/ME's DLL/VXD files.

take for instance KERNEL32.DLL. compare version 4.10.2222 of kernel32.dll with 4.00.950, 4.00.1111 and 4.03.1212 of kernel32.dll

I remember that some time ago I had problem with esdi_506.pdr and scsiport.pdr on Windows 95 (original) so I patched them the same way as the OSR2 files were patched. Here are:

ESDI_506.PDR 4.00.957 (patched 4.00.956)

SCSIPORT.PDR 4.00.952 (patched 4.00.951)

unfortunately, the Q273468 hotfix for Win95 [bundled in IomegaWare software and Iomega drivers and I do use an old Iomega 100Mb parallel ZIP drive] installs ESDI_506.PDR version 4.00.1116 under original release of Win95. I did use 4.00.1119 of esdi_506.pdr under original Win95 edition and I had no problems.

but that was just for testing purposes only. had to remove original Win95 off an old PC and installed Win95 OSR2 to get FAT32 and DMA support for HDs. PCI bus mastering is not included in original version of Win95 and was added in the OSR2 releases.

Edited by erpdude8
0

Share this post


Link to post
Share on other sites

It is possible that the problem was resolverd in ndis.vxd 4.00.1113 that is part of Windows 95 Dial-Up Networking 1.4 Upgrade - it is in msnet95.cab

no Petr. 4.00.1113 of ndis.vxd does NOT fix the Q312108 problems under ANY version of Win95.

Why do you think this? I have analyzed the code and it seems that th 2.1 GHz problem was really resolved. Or have you tested the file and still got the "While initializing device NDIS: Windows protection error"?

Petr

0

Share this post


Link to post
Share on other sites
Why do you think this? I have analyzed the code and it seems that th 2.1 GHz problem was really resolved. Or have you tested the file and still got the "While initializing device NDIS: Windows protection error"?

because I am STILL skeptical and I do NOT believe it until you have shown and conducted further testing of v4.00.1113 of ndis.vxd on an actual Win95 SR2 machine with a 2.1GHz CPU.

post your results so that I can be fully convinced, Petr.

Edited by erpdude8
0

Share this post


Link to post
Share on other sites

Petr, running Win95 OSR2 on VMWare Server, on my Athlon64 X2 (@ 2.01GHz) (Using only one CPU for virtualization), with the 4.00.1114 patch, I still get a protection error on bootup, specifically after turning on file and printer sharing.

I used VMware's DiskMount utility to write the file into the virtual disk (which is what I use on a nearly daily basis to do things like this).

EDIT: I was wrong about the version number - it was 4.00.950 B, NOT OSR2. I tried the older release, and it works fine. Thanks ;)

Edited by jimmsta
0

Share this post


Link to post
Share on other sites
Petr, running Win95 OSR2 on VMWare Server, on my Athlon64 X2 (@ 2.01GHz) (Using only one CPU for virtualization), with the 4.00.1114 patch, I still get a protection error on bootup, specifically after turning on file and printer sharing.

I used VMware's DiskMount utility to write the file into the virtual disk (which is what I use on a nearly daily basis to do things like this).

And the error message is "While initializing device NDIS: Windows protection error"?

Have you tried Windows 98 first edition without and with the Q312108 patch?

I tried Windows 95 (4.00.950), 95 OSR2 (4.00.1111), 98 (4.10.1998) in Virtual PC 2004 on box with Pentium D 820 (2.8 GHz) and no protection error appeared even with clean install.

NDIS.VXD is the lowest layer above the network card driver and all network comunication should go thru it.

The only Windows protection error I have experienced on Windows 95 in Virtual PC 2004 environment was with Ntkern.vxd 4.03.1212, 4.03.1213 was OK.

I'm not experienced with VMware and I don't have any other machine with AMD processor than K6-2/400.

Petr

0

Share this post


Link to post
Share on other sites

I editted the above post.

The odd thing is, the original NDIS.VXD file in this install (original Build 950 B, clean install), has a version number of 4.00.1111, which I expected to mean that the 4.00.1114 patch was the correct patch... however, it is not. The .950 patch is the correct patch for this version of Win95.

0

Share this post


Link to post
Share on other sites
Petr, running Win95 OSR2 on VMWare Server, on my Athlon64 X2 (@ 2.01GHz) (Using only one CPU for virtualization), with the 4.00.1114 patch, I still get a protection error on bootup, specifically after turning on file and printer sharing.

I used VMware's DiskMount utility to write the file into the virtual disk (which is what I use on a nearly daily basis to do things like this).

EDIT: I was wrong about the version number - it was 4.00.950 B, NOT OSR2. I tried the older release, and it works fine. Thanks ;)

4.00.950B is OSR2! It's OSR2.0 or 2.1. OSR 2.5 probably would be this or similar to 4.00.950C.

0

Share this post


Link to post
Share on other sites

Petr, running Win95 OSR2 on VMWare Server, on my Athlon64 X2 (@ 2.01GHz) (Using only one CPU for virtualization), with the 4.00.1114 patch, I still get a protection error on bootup, specifically after turning on file and printer sharing.

I used VMware's DiskMount utility to write the file into the virtual disk (which is what I use on a nearly daily basis to do things like this).

EDIT: I was wrong about the version number - it was 4.00.950 B, NOT OSR2. I tried the older release, and it works fine. Thanks ;)

4.00.950B is OSR2! It's OSR2.0 or 2.1. OSR 2.5 probably would be this or similar to 4.00.950C.

try installing the AMD-K6-2 patch (AMDK6UPD.EXE) under Win95 OSR2.0, OSR2.1 or OSR2.5 and then use version 4.00.1114 of the NDIS.VXD file on your AMD system.

The only Windows protection error I have experienced on Windows 95 in Virtual PC 2004 environment was with Ntkern.vxd 4.03.1212, 4.03.1213 was OK.

Version 4.03.1213 of NTKERN.VXD is included in the AMDK6UPD.EXE patch found here.

Edited by erpdude8
0

Share this post


Link to post
Share on other sites
Petr, running Win95 OSR2 on VMWare Server, on my Athlon64 X2 (@ 2.01GHz) (Using only one CPU for virtualization), with the 4.00.1114 patch, I still get a protection error on bootup, specifically after turning on file and printer sharing.

HAH, that proves my point. ndis.vxd v4.00.1114 alone didnt fix the "protection error", especially when running Win95 OSR2 on an AMD-processor based machine with very high speed AMD CPU.

jimmsta, see if you can install the AMDK6UPD.EXE patch your Win95 SR2 on your VMWare server and then install 4.00.1114 of the ndis.vxd file to see if the "protection error" message goes away.

I feel some deja vu.

Several mothns ago i've downloaded 'Unofficial Windows 95 modern processors update' from some OSBA server.

I had a lot of modified VXDs.

If i'll find them on my PC i'll upload them somewhere.

can you post this in another download site like Rapidupload.com or MyTempdir.com, Tihiy? I HATE DOWNLOADING STUFF FROM RAPIDSHARE!!!! I now consider the Rapidshare site a POOR choice to download files unless users have paid for a premium account there.

0

Share this post


Link to post
Share on other sites

I have tried to create the patch for Q312108 - Windows Protection Error in NDIS with a CPU That Is Faster Than 2.1 GHz

...

It is possible that the problem was resolverd in ndis.vxd 4.00.1113 that is part of Windows 95 Dial-Up Networking 1.4 Upgrade - it is in msnet95.cab

...

If anybody is able to test Windows 95 on >2.1 GHz system and Windows have the problem described in Q312108, i.e. "While initializing device NDIS: Windows protection error" during boot, please test these files if they really cure the problem.

Q192841 - Difficulties Using AMD K6-2 or Athlon Central Processing Unit update for AMD processor with 350+ MHz (amdk6upd.exe package) is for Windows 95 OSR2 only.

I remember that some time ago I had problem with esdi_506.pdr and scsiport.pdr on Windows 95 (original) so I patched them the same way as the OSR2 files were patched....

Better late than never... :angel

I can confirm ALL of your results Petr. :yes:

NDIS.VXD v. 4.00.1113 from DUN14-95.EXE fixes the Q312108 error on ALL versions of Windows 95, and when combined with the AMDK6UPD.EXE HotFix can be used to run Windows 95 on >2.1GHz CPUs.

I have created a scripted installer for all of these updates, FIX95CPU, which can be found here.

FIX95CPU can update all versions of Windows 95 now, thanks to your patched files for 95 RTM. Thanks for all your efforts! :thumbup

Edited by LoneCrusader
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.