Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Windows 95 2.1GHz CPU Limit BROKEN!

- - - - -

  • Please log in to reply
201 replies to this topic

#151
YCG96

YCG96
  • Members
  • 6 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Windows 95 CDROM's are not bootable. :whistle:

That's... the upgrade versions are not bootable whether on floppy or CD-ROM, but I just realized that the CD-ROM I used is the Windows 95 "for PCs without Windows" CD-ROM.

If you're just going to copy and re-modify it each time you install, why not just use FIX95CPU as-is? :unsure:

I actually tried to use FIX95CPU 2.0 "as-is" - I tried to use it the first time just after Windows 95 was installed and just before it booted for the first time, but then when Windows 95 booted for the first time, the "Setting up Hardware" process seemed to reinstall some of the VxDs that were replaced when I ran FIX95CPU from the Windows 95 CD-ROM and I got the same old Windows protection error during the next boot, and I used FIX95CPU the second time after that happened, but despite the fact that FIX95CPU 2.0 was slightly updated so it should also work after Windows 95 tries to boot and displays the Windows protection error, I still got the same old Windows protection error after running FIX95CPU.


How to remove advertisement from MSFN

#152
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator

That's... the upgrade versions are not bootable whether on floppy or CD-ROM, but I just realized that the CD-ROM I used is the Windows 95 "for PCs without Windows" CD-ROM.
...
I actually tried to use FIX95CPU 2.0 "as-is" - I tried to use it the first time just after Windows 95 was installed and just before it booted for the first time, but then when Windows 95 booted for the first time, the "Setting up Hardware" process seemed to reinstall some of the VxDs that were replaced when I ran FIX95CPU from the Windows 95 CD-ROM and I got the same old Windows protection error during the next boot, and I used FIX95CPU the second time after that happened, but despite the fact that FIX95CPU 2.0 was slightly updated so it should also work after Windows 95 tries to boot and displays the Windows protection error, I still got the same old Windows protection error after running FIX95CPU.

I'm not aware of any bootable Windows 95 CD's, for PC's without Windows or otherwise. But it's simple enough to create your own bootable CD.

Anyway..

If you are using a "For PC's Without Windows" CD then it must be 95/95A rather than 95B/95C because the B/C versions only exist as OEM CDROMs.

I have seen some errors reported using FIX95CPU with 95/95A. I did not have a copy of 95/95A to test with when I created FIX95CPU, so the results on those earlier versions may not be ideal or exactly the same as 95B/95C. :}

#153
peter777

peter777

    Junior

  • Members
  • Pip
  • 54 posts
  • OS:XP Pro x86
  • Country: Country Flag

- Did you have any of the USB Support updates previously installed on this Win95 HDD?
(MAJOR changes to several core system files, so we need to know whether we're working with pre-USB 95B or post-USB 95B.)


I would be interested to apply the fix/patch for 95B, to support USB drives please.

Peter

#154
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator


- Did you have any of the USB Support updates previously installed on this Win95 HDD?
(MAJOR changes to several core system files, so we need to know whether we're working with pre-USB 95B or post-USB 95B.)


I would be interested to apply the fix/patch for 95B, to support USB drives please.

Peter

-Any luck getting past the protection error?


Microsoft made one heck of a mess with the USB updates for Windows 95. :wacko: As long as you know what to do beforehand, then you should be OK. If not, it can be extremely confusing.

There are two official USB Support packages.

The first of which (USBSUPP.EXE) had two versions issued (first version was bugged and should NOT be used).
Then USBUPD2.EXE was issued to correct bugs in the first package.
Finally there were several "HotFix" files issued that further updated the drivers.

Then, on top of that, there are semi-complete unofficial packages to support USB Flash Drives (which may be superseded in the near future.) :whistle:

I have been planning to merge all of these updates into a single package to simplify things. If you're willing to wait a couple of days, I will try to get it assembled. If you want to go ahead and wade through the mess, I will walk you through it. :angel

#155
peter777

peter777

    Junior

  • Members
  • Pip
  • 54 posts
  • OS:XP Pro x86
  • Country: Country Flag

-Any luck getting past the protection error?


No, unfortunately.

I have been planning to merge all of these updates into a single package to simplify things. If you're willing to wait a couple of days, I will try to get it assembled. If you want to go ahead and wade through the mess, I will walk you through it. :angel


Okay thanks, that would be great. USB support for the (old) W95B computer would be better than trying to work with either CD's or floppy drives, to get data to and fro. :thumbup

That is all assuming this protection error can't be fixed, as I will then have to put the W95B HDD back into the old computer, 350 Mhz CPU. Will then see if I can get a KVM that supports 3 computers; a tad bit easier.

Peter

Edited by peter777, 29 November 2012 - 12:27 AM.


#156
YCG96

YCG96
  • Members
  • 6 posts
  • OS:Windows 7 x86
  • Country: Country Flag

then it must be 95/95A rather than 95B/95C

I exactly said:

I tested it in Windows Virtual PC with:
...
* Windows 95 Retail ("for PCs without Windows") - all optional components were installed

so you should have been sure that it's neither Windows 95A/B/C, not either the original version or Windows 95A, because the retail floppy disks/CD-ROM were never updated except when Internet Explorer 1 was released.

I did not have a copy of 95/95A to test with

Do you have one now?
If not, however, the retail version "for PCs without Windows" is interestingly still available in some stores, although mostly moved to the Collectables section or something like that in each of those stores.

#157
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator

I exactly said:


I tested it in Windows Virtual PC with:
...
* Windows 95 Retail ("for PCs without Windows") - all optional components were installed

so you should have been sure that it's neither Windows 95A/B/C, not either the original version or Windows 95A, because the retail floppy disks/CD-ROM were never updated except when Internet Explorer 1 was released.


Yes. And I said this in my slipstreaming instructions:

THIS SLIPSTREAM METHOD IS FOR WINDOWS 95 B OSR 2.0/2.1 AND WINDOWS 95 C OSR 2.5 ONLY!
HAS NOT BEEN TESTED WITH WINDOWS 95 ORIGINAL OR WINDOWS 95 A!

:whistle:
but nonetheless, I'm happy that you got it to work, and it's not worth splitting hairs over. Welcome to MSFN. :hello:

Do you have one now?
If not, however, the retail version "for PCs without Windows" is interestingly still available in some stores, although mostly moved to the Collectables section or something like that in each of those stores.

I do have a copy of 95 Original/RTM now, but I've had so many other projects going on that I haven't had any time to devote to experimenting with it. :}

#158
jaclaz

jaclaz

    The Finder

  • Developers
  • 13,406 posts
  • OS:none specified
  • Country: Country Flag
Just for the record, the version:

Windows 95 "for PCs without Windows"

is only listed on many sources as being a set of 3" 1/2 floppies (and NO CD-ROM) :unsure: example:
http://www.emsps.com...ls/mswin95v.htm

Could you share the MS part number and (possibly) a photo of the actual CD?

And/or additionally the file dates:
http://support.micro...kb/158238/en-us

Does it look *like* this one (which seemingly is the French version) - but this seems an OEM one:
http://www.amazon.co..._pr_product_top

Compare with:
http://thebuyonlinec...6121017-4226423

This could be it? - still seems to me an OEM one
http://www.amazon.co...=A2LGHWXS2DEZ7I

This one could be it (the box) but if you zoom in on the image you see in top left that it is the 3.5" floppy version:
http://www.ebay.com/...=p2047675.l2557
it is possible that this same version was made on CD.



jaclaz

#159
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator

...
And/or additionally the file dates:
http://support.micro...kb/158238/en-us
...


OEM Service Release 2.5 4.03.1214* (4.00.950C) 8/24/96-11/18/97


Wow.. my OSR 2.5 CD is dated 12-01-1997 12:16 PM (GMT, shows as 7:16 AM in EST).

Not mentioned on the list... :whistle:
I didn't know I had something unique. :w00t:

#160
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 3,888 posts
  • OS:none specified
  • Country: Country Flag

Wow.. my OSR 2.5 CD is dated 12-01-1997

...and mine is 11/26/97...

#161
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator


I have been planning to merge all of these updates into a single package to simplify things.

Okay thanks, that would be great. USB support for the (old) W95B computer would be better than trying to work with either CD's or floppy drives, to get data to and fro. :thumbup

That is all assuming this protection error can't be fixed, as I will then have to put the W95B HDD back into the old computer, 350 Mhz CPU. Will then see if I can get a KVM that supports 3 computers; a tad bit easier.

Peter

Peter, if you're still following this thread I have created a preliminary version of the "merged update" that I was referring to. It contains all of the official Windows 95 USB updates merged into one installation package. It doesn't contain any unofficial items yet, (including USB Storage drivers) as these are still incomplete.

I've had it done for a while now but hadn't seen you around. I should have posted before... but anyhow, if you're interested in the update, just let me know and I will post a link to download it.

#162
peter777

peter777

    Junior

  • Members
  • Pip
  • 54 posts
  • OS:XP Pro x86
  • Country: Country Flag

Peter, if you're still following this thread I have created a preliminary version of the "merged update" that I was referring to. It contains all of the official Windows 95 USB updates merged into one installation package. It doesn't contain any unofficial items yet, (including USB Storage drivers) as these are still incomplete.

I've had it done for a while now but hadn't seen you around. I should have posted before... but anyhow, if you're interested in the update, just let me know and I will post a link to download it.


Yes, thanks, I'm interested in the USB updates that you have created. :)

Peter

#163
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator


Yes, thanks, I'm interested in the USB updates that you have created. smile.gif

Peter

Ok, here goes :whistle: lol

It's best if you remove all devices again, put the hard drive back in the old computer for this, and uninstall the Demo RAM patch.

Once this update is installed, there is a chance that it may enable you to get past the issues you were having with the newer machine, because it installs a newer VMM.VXD kernel that has a bugfix for newer processors. I can't say for sure if it will help or not, as we were never able to determine the source of your error, but it remains a possibility.

So, once you have XUSBSUPP installed, if you still want to try the newer machine again, simply re-install the Demo RAM patch and remove devices again for a new test. If it doesn't work still, you can always put it back in the old computer... again... lol. laugh.gif


Notes for anyone else who may be interested in or download this:

This package is experimental!
It renders ALL earlier official and unofficial USB Support packages for Windows 95 OBSOLETE and should NOT be used with any of them!
See the enclosed XUSBSUPP.TXT for further information.


XUSBSUPP.ZIP - 901.0 Kb

Edited by LoneCrusader, 22 July 2013 - 02:42 AM.


#164
peter777

peter777

    Junior

  • Members
  • Pip
  • 54 posts
  • OS:XP Pro x86
  • Country: Country Flag

It's best if you remove all devices again, put the hard drive back in the old computer for this, and uninstall the Demo RAM patch.


Okay, thanks for this update. :D

Once this update is installed, there is a chance that it may enable you to get past the issues you were having with the newer machine, because it installs a newer VMM.VXD kernel that has a bugfix for newer processors. I can't say for sure if it will help or not, as we were never able to determine the source of your error, but it remains a possibility.


That would be great, even if it's only a chance.

So, once you have XUSBSUPP installed, if you still want to try the newer machine again, simply re-install the Demo RAM patch and remove devices again for a new test. If it doesn't work still, you can always put it back in the old computer... again... lol. :lol:


Yes, as long as I can always go back to the hdd in the old computer, if need be.

Thanks,

Peter

#165
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator

Okay, thanks for this update. :D

No problem, and good luck! :yes:

#166
peter777

peter777

    Junior

  • Members
  • Pip
  • 54 posts
  • OS:XP Pro x86
  • Country: Country Flag
I booted into safe mode and removed all devices. Then, hoping that the new update will fix this problem (on the new computer), I then installed the XUSBSUPP. Went okay, restarted and got lots of messages related to MSDUN, just selected option to skip file. Now when I retarted either in Win or safe Mode, get the message VMM32.VXD was not found or damaged.

Will place the HDD into the old computer again, hopefully there is a fix to get around the VMM32.VXD message.

Peter

#167
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator

I booted into safe mode and removed all devices. Then, hoping that the new update will fix this problem (on the new computer), I then installed the XUSBSUPP. Went okay, restarted and got lots of messages related to MSDUN, just selected option to skip file. Now when I retarted either in Win or safe Mode, get the message VMM32.VXD was not found or damaged.

Will place the HDD into the old computer again, hopefully there is a fix to get around the VMM32.VXD message.

Peter

Yikes! :ph34r:

I meant for you to install XUSBSUPP with the HDD in the old computer, and make sure it was OK there before trying it in the new one. Maybe I wasn't clear...

I don't know why you would be seeing anything related to MSDUN, I've never encountered that before. It is completely unrelated to USB and shares no common files.

Now we will need to get XUSBSUPP uninstalled to get rid of the VMM32.VXD error... but if you can't boot to Normal or Safe Mode, it's going to be a real pain, probably requiring several Deletes & Renames from pure DOS.

#168
peter777

peter777

    Junior

  • Members
  • Pip
  • 54 posts
  • OS:XP Pro x86
  • Country: Country Flag

[I meant for you to install XUSBSUPP with the HDD in the old computer, and make sure it was OK there before trying it in the new one. Maybe I wasn't clear...


You were perfectly clear in your instructions, I was just hoping that, ... maybe, maybe, it would work, .. sorry. :blushing:

I don't know why you would be seeing anything related to MSDUN, I've never encountered that before. It is completely unrelated to USB and shares no common files.


Maybe related to deleting all devices ??

Now we will need to get XUSBSUPP uninstalled to get rid of the VMM32.VXD error... but if you can't boot to Normal or Safe Mode, it's going to be a real pain, probably requiring several Deletes & Renames from pure DOS.


Deletes/copies/renames don't bother me, as that (new) computer is dual boot. I can boot into Linux, 'see' the dos drives/files, and do copies,etc.

Thanks for your help,

Peter

Edited by peter777, 04 January 2013 - 12:02 AM.


#169
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator

Maybe related to deleting all devices ??

Probably. Do you have a Dial-Up Modem in the new machine? (Or the old one?)

You were perfectly clear in your instructions, I was just hoping that, ... maybe, maybe, it would work, .. sorry. :blushing:

It's OK, I'm just worried now about helping you recover your system. :ph34r: I've never encountered this problem, or anything similar, using the USBSUPP packages. I have seen something similar when using the 95 Unofficial Service Pack (mentioned previously in the thread), which rendered one of my test machines unbootable.

I made sure that XUSBSUPP would "uninstall" properly before I released it, but that only works if you are able to boot into Windows. I didn't anticipate running into this...

Deletes/copies/renames don't bother me, as that (new) computer is dual boot. I can boot into Linux, 'see' the dos drives/files, and do copies,etc.

I will have to set up a test VM and install XUSBSUPP, try to "uninstall" it manually, and then make a list of what changes need to be made.

#170
peter777

peter777

    Junior

  • Members
  • Pip
  • 54 posts
  • OS:XP Pro x86
  • Country: Country Flag

[Probably. Do you have a Dial-Up Modem in the new machine? (Or the old one?)


There may be an inboard modem in either of those computers, but definitely I don't use DUN for Win95b, or internet or the network.

It's OK, I'm just worried now about helping you recover your system. :ph34r: I've never encountered this problem, or anything similar, using the USBSUPP packages. I have seen something similar when using the 95 Unofficial Service Pack (mentioned previously in the thread), which rendered one of my test machines unbootable.


Oops, I hope we can get this one going again.

I made sure that XUSBSUPP would "uninstall" properly before I released it, but that only works if you are able to boot into Windows. I didn't anticipate running into this...

I will have to set up a test VM and install XUSBSUPP, try to "uninstall" it manually, and then make a list of what changes need to be made.


Sorry to put you to so much trouble. I do have a WIN95B folder on that HDD, it has CAB files 02 to 28, plus a whole lot of other files, if need be. But you need Windows even to run EXTRACT I think.

Thanks,

Peter

#171
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator

There may be an inboard modem in either of those computers, but definitely I don't use DUN for Win95b, or internet or the network.

Ok, it's probably irrelevant anyhow. MSDUN (I believe) and XUSBSUPP (I know) copy all of their files to the required locations when installed anyhow, so "Skipping" the redundant file copies called by the various .INF's should not affect the machine.

Oops, I hope we can get this one going again.

Sorry to put you to so much trouble. I do have a WIN95B folder on that HDD, it has CAB files 02 to 28, plus a whole lot of other files, if need be. But you need Windows even to run EXTRACT I think.

Thanks,

Peter

Yes, I certainly hope we can recover the system, especially since you can't do a reinstall.

EXTRACT can be run from DOS, but VMM32.VXD is "built" during installation. The VMM32.VXD inside the .CAB files is only a "starter" file. Other .VXD's are combined with it during the second phase of SETUP.

XUSBSUPP makes backups of all the files it changes/updates, so I believe it is possible to recover, but I will have to test it before we take a chance with your system.

#172
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator

Ok, here is a step by step, directory by directory list of instructions for removing XUSBSUPP from an unbootable machine.


*BE ABSOLUTELY CERTAIN THAT YOU LEAVE ALL OF THE FILES WITH AN .O20 EXTENSION AND ONLY RENAME COPIES OF THEM!*


1.) In the root C:\ folder:
Be sure AUTOEXEC.BAT is blank unless your system had any previous specific settings in it.
If these lines are present, delete them:

@ECHO OFF
if not exist %winbootdir%\system\vmm32.o20 copy %winbootdir%\system\vmm32.vxd %winbootdir%\system\vmm32.o20
cd %winbootdir%\system
devlib -u vmm32.vxd
rplcldr %winbootdir%\system\vmm32\vmm.vxd %winbootdir%\system\vmm32.vxd
devlib -p vmm32.vxd



2.) In the C:\WINDOWS folder:
Delete:
VFWWDM32.DLL


3.) In the C:\WINDOWS\INF folder:
Delete:
USB.INF
IMAGE.INF
NODRIVER.INF

Copy & Rename the Copy:
NODRIVER.020 to NODRIVER.INF


4.) In the C:\WINDOWS\SYSTEM folder:
Delete:
RPLCLDR.EXE (If exists.)
DEVLIB.EXE (If exists.)
UHCD.SYS
USBD.SYS
USBHUB.SYS
OPENHCI.SYS
USBCAMD.SYS
IMAGECLS.SYS
VFWWDM.DRV
CONAGENT.EXE
KERNEL32.DLL
KRNL386.EXE
MSGSRV32.EXE
REDIRECT.MOD
SPOOLSS.DLL
WINOA386.MOD

Copy & Rename the Copy:
CONAGENT.020 to CONAGENT.EXE
KERNEL32.020 to KERNEL32.DLL
KRNL386.020 to KRNL386.EXE
MSGSRV32.020 to MSGSRV32.EXE
REDIRECT.020 to REDIRECT.MOD
SPOOLSS.020 to SPOOLSS.DLL
WINOA386.020 to WINOA386.MOD

Rename:
VMM32.VXD to VMM32.BAD (Can be deleted once all of this is successful.)

***Important!!!
Copy & Rename the Copy:
VMM32.O20 to VMM32.VXD

BE ABSOLUTELY SURE TO LEAVE VMM32.O20!
(I also advise making an extra backup copy of the good VMM32.O20, say VMM32.ORI)


5.) In the C:\WINDOWS\SYSTEM\VMM32 folder:
Delete:
NTKERN.VXD
VMM.VXD
VMCPD.VXD
VTD.VXD
VXDLDR.VXD
VPICD.VXD
VCOND.VXD
VWIN32.VXD

IF there are any of the above files in this folder with a .O20 extension, Copy them and Rename the Copy back to .VXD.


6.) When you boot the 95 installation again, it will error, saying it can't find NTKERN.VXD.
Ignore this and press a key to continue.


7.) If any Driver Instalalation dialogs appear, cancel them.
When the machine is booted, go into the Device Manager and remove any USB devices still showing.


8.) Then go under Add/Remove Programs and Remove "USB Supplement to OSR2."
This will get rid of the extra .O20 files but they MUST be there for the uninstaller or this uninstall can destroy your system.
It will also get rid of the NTKERN error message.



I hope this will recover your system back to the status quo ante-XUSBSUPP.. lol :lol: :angel

#173
peter777

peter777

    Junior

  • Members
  • Pip
  • 54 posts
  • OS:XP Pro x86
  • Country: Country Flag
Thanks for those very detailed instructions. I can safely remove all lines in AUTOEXEC.BAT, the CONFIG.SYS has

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

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

Is that okay ?

Also, I will backup the complete drive before doing anything.

Thanks,

Peter

#174
LoneCrusader

LoneCrusader

    Resistere pro causa resistentiam.

  • MSFN Sponsor
  • 798 posts
  • OS:98SE
  • Country: Country Flag

Donator

Thanks for those very detailed instructions. I can safely remove all lines in AUTOEXEC.BAT, the CONFIG.SYS has

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

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

Is that okay ?

Also, I will backup the complete drive before doing anything.

Thanks,

Peter

No problem. :)

CONFIG.SYS is not altered by XUSBSUPP, so it's fine to leave as-is.

Good idea to back up the entire drive. :yes:

#175
peter777

peter777

    Junior

  • Members
  • Pip
  • 54 posts
  • OS:XP Pro x86
  • Country: Country Flag
Thanks, the only files that end in "O20" are shown in the attached file.

Peter

Attached Files


Edited by peter777, 04 January 2013 - 06:39 PM.





2 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users


    Google (1)


How to remove advertisement from MSFN