[dencorso]

Probably VCache explosion...
Try adding this to system.ini (if there isn't a [vcache] section, create one):

[vcache]
MaxFileCache=393216

[LoneCrusader]

peter777, on 15 November 2012 - 04:00 AM, said:

Have moved Win95b HDD to another computer, and then got a message "Insufficient memory to initialize Windows" message.

Then I changed the appropriate line in system.ini as

Add the following line in the [386Enh] section of the file

      MaxPhysPage=30000

and that got rid of the error message. But now it has an error message "Windows protection error" when I try to boot to Win95b


Here is CONFIG.SYS

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE

[COMMON]
SHELL=C:\COMMAND.COM C:\ /E:4096 /P
files=125
LASTDRIVE=Z

and here is AUTOEXEC.BAT

C:\WINDOWS\COMMAND\doskey
set path=c:\windows;c:\windows\command
win

The computer has 2 Gb RAM. What causes the "Windows protection error" message ?

Peter

dencorso, on 15 November 2012 - 11:48 PM, said:

Probably VCache explosion...
Try adding this to system.ini (if there isn't a [vcache] section, create one):

[vcache]
MaxFileCache=393216

Probably a good idea to update VCACHE.VXD as well. Even 95B comes with VCACHE.VXD v4.00.950.

The updated VCACHE.VXD v4.00.1111 for 95 B/C OSR2.x in Q194827 is 2x the size of the old 95/95A version.
Q194827.EXE

This post has been edited by LoneCrusader: 16 November 2012 - 12:08 AM

[nzwill]

I'm installing an ISO of Windows 95 in Windows Virtual PC 7 and I have followed the instructions for the patch, and it appears to have worked (no more pesky windows protection error message), but now when Windows restarts post the patch being applied and begins to install various driver files it seems that it's now looking in the wrong place for them - it's looking inside X:\WIN95 for the various driver files and not finding them because they're all packed up in .cab folders that it doesn't seem to recognise.

Is this something that other people have encountered before, and if so what is a suitable workaround? I apologise for the low level of detail in the post and if this is something that is normally considered trivial, my fluency in all this is not particularly high (yet).

[LoneCrusader]

nzwill, on 18 November 2012 - 11:04 AM, said:

I'm installing an ISO of Windows 95 in Windows Virtual PC 7 and I have followed the instructions for the patch, and it appears to have worked (no more pesky windows protection error message), but now when Windows restarts post the patch being applied and begins to install various driver files it seems that it's now looking in the wrong place for them - it's looking inside X:\WIN95 for the various driver files and not finding them because they're all packed up in .cab folders that it doesn't seem to recognise.

Is this something that other people have encountered before, and if so what is a suitable workaround? I apologise for the low level of detail in the post and if this is something that is normally considered trivial, my fluency in all this is not particularly high (yet).

It's normal for Setup to extract its driver (and other) files from the .CABs, that's how all versions of Windows 9x install...

The X:\WIN95 reference must be something unique to your setup, because there are no such references in FIX95CPU. It sounds like the PATH to your CDROM drive (or .ISO mounted as CDROM) has been changed since the first round of Setup.

Maybe with more details I could be of more help...

This post has been edited by LoneCrusader: 18 November 2012 - 02:33 PM

[submix8c]

A couple of details needed -
1 - "Virtual PC 7" - what's that? It appears to be the Apple Mac version. What OS is the Host? Do you mean VPC-2007?
2 - How did you install? CD-Boot ("attached" ISO image) or Floppy Boot?

[peter777]

dencorso, on 15 November 2012 - 11:48 PM, said:

Probably VCache explosion...
Try adding this to system.ini (if there isn't a [vcache] section, create one):

[vcache]
MaxFileCache=393216

Thanks, I tried that, but still got the "Windows protection error" message.

Will try the next suggestion, although I couldn't find VCACHE.VXD. I wonder what path it is in >

Peter

[peter777]

LoneCrusader, on 16 November 2012 - 12:01 AM, said:

Probably a good idea to update VCACHE.VXD as well. Even 95B comes with VCACHE.VXD v4.00.950.

The updated VCACHE.VXD v4.00.1111 for 95 B/C OSR2.x in Q194827 is 2x the size of the old 95/95A version.
Q194827.EXE

When I booted to DOS, and did a recursive 'dir' to search for VCACHE.VXD, it did not find the file, inside the c:\windows path.

I downloaded the Q194827.EXE file, booted to DOS again, and got a "This program cannot be run in DOS mode".

This mobo has a 3.0 GHz CPU also.

Peter

This post has been edited by peter777: 21 November 2012 - 02:59 AM

[peter777]

Have logged to BOOTLOG.TXT, and the lines with 'fail' are ..

Quote

[0014C7EE] Loading Vxd = ndis2sup.vxd
[0014C7EF] LoadFailed = ndis2sup.vxd

[0014C7F2] Loading Vxd = vserver.vxd
[0014C7F3] LoadFailed = vserver.vxd

[0014C804] Loading Vxd = vshare
[0014C804] LoadFailed = vshare

There aere 6 lines that refence VCACHE ..

Quote

[0014C7E9] Loading Vxd = VCACHE
[0014C7E9] LoadSuccess = VCACHE

[0014C80A] SYSCRITINIT = VCACHE
[0014C80A] SYSCRITINITSUCCESS = VCACHE

[0014C80F] DEVICEINIT = VCACHE
[0014C80F] DEVICEINITSUCCESS = VCACHE

If I try to boot to Win safemode, it very quickly just goes to DOS. Hmm, I might try running SETUP.

Ah, I can't run that in DOS either.

Btw, the file FIXCPU.ISO only conatins one file - DUN14-95.EXE , is that okay ? Seems weird for an image of a boot disk.

Peter

This post has been edited by peter777: 21 November 2012 - 04:33 AM

[LoneCrusader]

peter777, on 21 November 2012 - 02:45 AM, said:

Will try the next suggestion, although I couldn't find VCACHE.VXD. I wonder what path it is in >

peter777, on 21 November 2012 - 02:57 AM, said:

When I booted to DOS, and did a recursive 'dir' to search for VCACHE.VXD, it did not find the file, inside the c:\windows path.

I downloaded the Q194827.EXE file, booted to DOS again, and got a "This program cannot be run in DOS mode".

peter777, on 21 November 2012 - 04:06 AM, said:

Btw, the file FIXCPU.ISO only conatins one file - DUN14-95.EXE , is that okay ? Seems weird for an image of a boot disk.

VCACHE.VXD is merged into VMM32.VXD along with several other VXD's during the second phase of SETUP, so you won't find the file after that.

All MS HotFixes require Windows to run. Pretty useless when you can't boot to Windows to begin with. That's why I created FIX95CPU to install the updated CPU fixes. In order to update your VCACHE.VXD, you will need to manually extract VCACHE.OSR (it contains two VCACHE files, one for 95/95A and one for 95B/95C) from the HotFix file I linked, rename it to VCACHE.VXD, and manually place it in your WINDOWS\SYSTEM\VMM32 folder.

The Boot Image of an .ISO is not visible without tools for viewing/extracting/editing etc. FIX95CPU.ISO contains a boot image of the FIX95CPU floppy, with DUN14-95.EXE added to the "normal" part of the ISO for convenience.

I wish you success in your endeavor, but in my personal experience, if you want to use more than 512MB of RAM, you will need RLoew's RAM Limitation Patch. Several users here report success using up to ~1.5GB with the tweaks you have been experimenting with, but those tweaks never worked on any of my systems. (Also, many of those users are using 98SE, which may handle the larger RAM amounts better than standard 95B/C can.) The patch has a DEMO version that runs for 10 minutes. You might try downloading it and see if it cures your problem.

[peter777]

I have now run FIX95CPU, all went okay, used the ISO on a CD and booted to that, restarted and got the usual "Windows protection error" message.

LoneCrusader, on 21 November 2012 - 06:13 AM, said:

In order to update your VCACHE.VXD, you will need to manually extract VCACHE.OSR (it contains two VCACHE files, one for 95/95A and one for 95B/95C) from the HotFix file I linked, rename it to VCACHE.VXD, and manually place it in your WINDOWS\SYSTEM\VMM32 folder.

How do I do that ? Is it running EXTRACT.EXE on Q194827.EXE ?

LoneCrusader, on 21 November 2012 - 06:13 AM, said:

I wish you success in your endeavor, but in my personal experience, if you want to use more than 512MB of RAM, you will need RLoew's RAM Limitation Patch. Several users here report success using up to ~1.5GB with the tweaks you have been experimenting with, but those tweaks never worked on any of my systems. (Also, many of those users are using 98SE, which may handle the larger RAM amounts better than standard 95B/C can.) The patch has a DEMO version that runs for 10 minutes. You might try downloading it and see if it cures your problem.

Thanks, I might have to try the demo.

Peter

[LoneCrusader]

peter777, on 21 November 2012 - 11:04 PM, said:

How do I do that ? Is it running EXTRACT.EXE on Q194827.EXE ?

You will need to use WinZip, WinRar, 7-Zip, etc, to extract the file from inside the HotFix on another computer. MS HotFixes are usually "Self-Extracting Executables" and can be opened with archiving programs.

[peter777]

Have placed the VCACHE.VXD in the path WINDOWS\SYSTEM\VMM32 , rebooted, same message. Looks like I might have to try RLoew's RAM Limitation patch

Thanks for your help,

Peter

[LoneCrusader]

peter777, on 21 November 2012 - 11:31 PM, said:

Have placed the VCACHE.VXD in the path WINDOWS\SYSTEM\VMM32 , rebooted, same message. Looks like I might have to try RLoew's RAM Limitation patch

Thanks for your help,

Peter

No problem.

Let us know if the patch works for you!

[peter777]

The patch didn't work either, so now back to square one, as they say.

[LoneCrusader]

You said you moved the HDD from another computer... I'm assuming you have data/programs on it that you wished to save? If not, I recommend a clean installation of 95B, just in case there are any old settings/drivers/files left over from the previous machine that may be causing errors.

[peter777]

I do have the original diskettes, by now I'd dount I would be able to read them, with errors. I may use WINE ; have tested running Ms Works under it, seems to run okay.

I think the only way to get 95b to run again, is to transfer the HDD back to the old computer ( a 350 mHz cpu I think).

Thanks for your help,

Peter

[LoneCrusader]

Since the older machine still works, you might try one last thing.

Put the HDD back in the older machine.
Boot into Safe Mode.
Go into the Device Manager and remove anything and everything that is listed there.
Then Shut Down and try the HDD in the new machine again.

If any older drivers are causing problems, this should correct it. If it doesn't, then you should be able to reconnect the HDD to the older machine again and let it redetect devices.

This post has been edited by LoneCrusader: 22 November 2012 - 12:25 AM

[peter777]

Okay, thanks. I will try that.

[peter777]

LoneCrusader, on 22 November 2012 - 12:25 AM, said:

Since the older machine still works, you might try one last thing.

Put the HDD back in the older machine.
Boot into Safe Mode.
Go into the Device Manager and remove anything and everything that is listed there.
Then Shut Down and try the HDD in the new machine again.

If any older drivers are causing problems, this should correct it. If it doesn't, then you should be able to reconnect the HDD to the older machine again and let it redetect devices.

I have been able to boot into Windows 'Safe mode' on the newer computer, the one with 2 Gb ram. Have removed everything I could from the Device Manager, restarted and still get the same message.

I can boot into Safe Mode though. But it hangs after about 10 mins, how do I uninstall " RLoew's RAM Limitation patch" ?

Peter

This post has been edited by peter777: 26 November 2012 - 08:07 PM

[peter777]

Have uninstalled the " RLoew's RAM Limitation patch", and try to boot into safe mode and get a msg "Insufficient memory".

Is there any way around that, or do I have to place the HDD back into the old machine ?

The ram is 2 Gb and the CPU is 3.0 Ghz in the newer computer, that doesn't like win95b.

Peter