LoneCrusader, on 24 February 2010 - 10:44 AM, said:
DUN14-95.EXE is too large to fit on a floppy disk, so there is no way to have it on the same "Disk" as the batch file. One solution to this might be to use an ISO editing program and add DUN14-95 to the bootable FIX95CPU.ISO...
I made a combination boot disc that has the original MS .exe's in the non-bootable area, and combines the two patches on one disc. This disc is all you need for VPC 7 and may be useful for some regular installs. Use it as normal for a boot disc, and type PATCHA for the 95ALL version of the batch file and PATCHBC for the 95B&C version. DUN14-95 is automatically placed in a folder on the C drive when one of the patch programs is executed. Users with virtual programs other than VPC 7 can install Win 95 normally by turning off hardware virtualization, and then the patches can both be installed from within Windows.
Files (note different web address than previously, sorry):
(self extracting archive)
I could only test patches for 95 OSR 2, because I don't have 95A, and the microsoft update patches for OSR 2 to 2.1 and 2.1 to 2.5 are no longer on the update site.
Also, I could not reproduce the 2.1 Ghz IOS error, perhaps because I never had the network running until after I had the DUN14-95 patch installed. Which program do you have to run to get this second problem?
While I agree it would be convenient to have the CPU and RAM fixes combined, RLoew's RAM patch
is not free, so it cannot be distributed in such a manner. It is the only method of installing more than 512 MB of RAM on a 9X system that I personally recommend however. I have been using it for over a year on my 98SE system with 1.5 GB of RAM. If you decide to purchase a copy, it is worth every penny.
It works great with VPC also. FWIW, all four virtualization programs I tried would boot with <=946MB but not >=947MB of RAM, but could get to >3GB (limited by the programs, not the RAM patch) with patch installed.