[LoneCrusader]

peter777, on 29 November 2012 - 12:24 AM, said:

LoneCrusader, on 28 November 2012 - 11:59 PM, said:

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.

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.

[peter777]

LoneCrusader, on 21 December 2012 - 11:21 PM, said:

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

[LoneCrusader]

peter777, on 22 December 2012 - 07:21 PM, said:

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

Peter

Ok, here goes 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.


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

[peter777]

LoneCrusader, on 22 December 2012 - 11:41 PM, said:

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.

LoneCrusader, on 22 December 2012 - 11:41 PM, said:

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.

LoneCrusader, on 22 December 2012 - 11:41 PM, said:

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.

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

Thanks,

Peter

[LoneCrusader]

peter777, on 22 December 2012 - 11:58 PM, said:

Okay, thanks for this update.

No problem, and good luck!

[peter777]

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

[LoneCrusader]

peter777, on 03 January 2013 - 11:41 PM, said:

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!

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.

[peter777]

LoneCrusader, on 03 January 2013 - 11:52 PM, said:

[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.

LoneCrusader, on 03 January 2013 - 11:52 PM, said:

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 ??

LoneCrusader, on 03 January 2013 - 11:52 PM, said:

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

This post has been edited by peter777: 04 January 2013 - 12:02 AM

[LoneCrusader]

peter777, on 04 January 2013 - 12:01 AM, said:

Maybe related to deleting all devices ??

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

peter777, on 04 January 2013 - 12:01 AM, said:

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

It's OK, I'm just worried now about helping you recover your system. 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...

peter777, on 04 January 2013 - 12:01 AM, said:

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.

[peter777]

LoneCrusader, on 04 January 2013 - 12:13 AM, said:

[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.

LoneCrusader, on 04 January 2013 - 12:13 AM, said:

It's OK, I'm just worried now about helping you recover your system. 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...

LoneCrusader, on 04 January 2013 - 12:13 AM, said:

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

[LoneCrusader]

peter777, on 04 January 2013 - 12:32 AM, said:

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.

peter777, on 04 January 2013 - 12:32 AM, said:

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.

[LoneCrusader]

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:

Quote

@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

[peter777]

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

[LoneCrusader]

peter777, on 04 January 2013 - 04:05 AM, said:

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.

[peter777]

Thanks, the only files that end in "O20" are shown in the attached file.

Peter

Attached File(s)

•  snapshot1.jpg (229.25K)
  Number of downloads: 8

This post has been edited by peter777: 04 January 2013 - 06:39 PM

[LoneCrusader]

peter777, on 04 January 2013 - 06:36 PM, said:

Thanks, the only files that end in "O20" are shown in the attached file.

Peter

Ok, that's fine. The ones that I referred to in \VMM32 "IF any ... are there" would only be there in the event that they had been updated since the original installation was done. Otherwise they are already packed into VMM32.VXD.

What's the version number of the VMM.O20 that was present? It's the only one that falls into this category it seems. Interesting, had you updated this file before?

This post has been edited by LoneCrusader: 04 January 2013 - 09:18 PM

[peter777]

The manual uninstall went okay, but Windows is running in MS-DOS mode now. It also said the MBR was modified - possible virus. I used to run AVG on this W95 box, but it's no longer updated. Also, can't uninstall AVG for some reason.

There are intermitant hangs, but could be the display driver, it doesn't have the correct drivers yet. Great that the W95B is back again though, thanks very much for your help.

LoneCrusader, on 04 January 2013 - 09:17 PM, said:

[What's the version number of the VMM.O20 that was present? It's the only one that falls into this category it seems. Interesting, had you updated this file before?

I don't think I would have updated that file, but the 'patch' for using extra ram does I think. The files are

vmm32.bad 7/5/05
vmm32.vxd 11/27/12

.O20 is not there anymore, but from the backup, it is 7/5/05

Thanks for all your help,

Peter

[peter777]

These hangs are like what happens when the ram patch is installed, but I don't have it installed ??

Even when I leave the computer just in Explorer, it hangs ? Could be the MS-DOS mode ?

Peter

[LoneCrusader]

Did you uninstall the Demo RAM patch BEFORE you tried to install XUSBSUPP?

[peter777]

Yes, the demo ram patch was uninstalled. I don't have the XUSBSUPP installed now, as that was uninstalled.

I wonder why Windows is running in MS-DOS mode though ?

Peter

This post has been edited by peter777: 04 January 2013 - 11:33 PM