submix8c, on 24 February 2010 - 11:38 AM, said:
AFAIKR the MS AMD Patch was specifically for the 350mhz (although heard reports of others).
Not slamming the project as it sounds great and should "cure" any problems with installation on "real" PC's. May try installing Win95RTM/OSRx.y onto a "real" partition just to give it a go (yeah, I have all of them in some form or another).
BTW, installing the DUN (and other items) should be able to "integrate" into actual install using the MSBATCH.INF (remember your other thread?) the same way as UBCD98SE did. If need be, I'll scrounge up the "basics" of the how-to to assist. Not much on projects nowadays except to fix my own up and relative's ignorance. I could at least supply the "raw files" (if not too large for a ZIP) used (the actual process files, not the remainder/proprietary EXE, etc.) to let you late-comers peruse (lots of BAT files too).
I can't speak from experience on the VPC issues, however I think he is referring to VPC7 for Windows 7, not VPC2007.
The MS AMD Patch works for many processors besides the 350MHz. I used it for years on AMDK6-2 550MHz systems before being forced to upgrade to 98 because of a game I wanted to play. It is also required for Pentium 4 processors, and I have used it to successfully install 95 on a P4 2.0GHz system.
Above 2.1GHz, Windows 95 will crash with the NDIS error referenced in the first post. MS claimed there was no fix for this in 95, but issued a HotFix for 98FE that contained an updated NDIS.VXD. It just so happens, the NDIS.VXD contained in the DUN14-95 update also fixes the error. MS neglected to mention this.
The reason for this particular project is that you cannot boot into Windows (not even safe mode) to install the MS patches. Windows will crash on the first reboot during setup. This project manually copies the AMDK6UPD files and the updated NDIS.VXD into Windows so that Windows Setup can continue normally.
It may be possible to use MSBATCH to install DUN14-95 during Setup, (as discussed with BeatZero above) but you must first be able to continue setup, if the updated files are not copied after the first reboot, Setup will crash. And, if the updated files are simply placed in the \WIN95 folder before setup, or copied before setup, WININIT.EXE will crash and not properly compress VMM32.VXD.
This post has been edited by LoneCrusader: 24 February 2010 - 12:07 PM