[rloew]

I have determined that the USB Controller and Root Hub Drivers have the same Registry Configuration before and after updating from the Windows 98SE RTM Drivers to those in U98SESP3 Version 3.7. This means that they do not have to be removed. This is also true of the USB Mouse Driver except for the need for WDMSTUB. This makes it possible to install U98SESP3 without requiring a PS/2 Keyboard or Mouse. There appears to be a flaw in WDMSTUB that occurs when the Hardware Installer tries to run a new Instance of it while it is already running.

For those of you who are desperate or enjopy Herculean tasks, here is the Procedure:

1. If using my RAM Limitation Patch, make a backup of WINDOWS\SYSTEM\VMM32\VMM.VXD if any.
2. Install U98SESP3 but do not reboot at end.
3. Unplug but do not remove USB Devices. Keep Keyboard and Mouse connected.
4. If using my RAM Limitation Patch Replace original VMM.VXD saved in step 1. If there was none, delete the new one.
5. Go to WINDOWS\SYSTEM\PRECOPY folder.
6. From SP3.CAB, extract USBCCGP.SYS, UHCD.SYS and HOTPLUG.DLL.
7. Put USBCCGP.SYS and UHCD.SYS in WINDOWS\SYSTEM32\DRIVERS folder.
8. Put HOTPLUG.DLL in WINDOWS\SYSTEM folder.
9. Go to WINDOWS\INF folder.
10. Edit the HIDDEV.INF File. Remove the text WDMSTUB.SYS and the following comma.
11. Edit the USBSTOR.INF File. Remove the text WDMSTUB.SYS and the following comma.
12. Edit the WINDOWS\WIN.INI File. At the end of the [windows] Section add the following line:

SkipMouseRedetect=0

13. Reboot into Safe Mode.
14. Go into Device Manager.
15. Remove all entries in the Keyboard Section.
16. Remove the System and Consumer Control Devices in the HID Section.
17. Remove all Composite Device entries in the USB Section.
18. Remove all Mass Storage Device entries in the USB Section.
19. Remove USB 2.0 Root Hubs in the USB Section.
20. Remove Enhanced Controller entries in the USB Section.
21. Remove other entries in the USB Section except the remaining Controller and Root Hub entries.
22. Remove USB Devices in the STORAGE, SCSIAdapter, Hard Disk, Disk Drives and any Vendor Named Section.
23. Install my WDMEX.VXD (still Alpha but enough for this task) and skip to Step 27.
Or run Steps 24-26.
24. Run REGEDIT.
25. Search for "usbhub.sys". Find the first one that is named NTMPDriver. This should be one of the USB Root Hub entries.
26. Replace the data with "wdmstub.sys,usbhub.sys".
27. Reboot.
28. You will probably encounter lockups as devices are loaded. If so reboot and try again. You may have to do this more than once.
29. Edit the WINDOWS\WIN.INI File to remove the SkipMouseRedetect Line added earlier.
30. If using my RAM Limitation Patch, remove the MaxPhysPage Line from WINDOWS\SYSTEM.INI and either remove or adjust the MaxFileCache Line.

This procedure works on one of my Computers. There is no guarantee it will work on yours.
It assumes that you are using the original USB Drivers that come with Windows 98SE for the Controllers, USB Keyboard and Mouse.

[Hu$tle]

You expect users to go through 30 steps instead of 5 just to get things working? You must be out your mind to think that. Not only that, you expect us to purchase 2 of your programs when its cheaper to borrow a PS/2 device or buy one from a pawn shop. I don' t think you have common sense at all. You say WDMDTUB is flawed but you have yet to come up with a better solution. So far WDMSTUB has been working and its free. You and your prices can go suck an egg until you choke. If you software is so great, then you should be working for Microsoft or Apple.

[rloew]

Hu$tle, on 18 September 2012 - 09:51 PM, said:

You expect users to go through 30 steps instead of 5 just to get things working?

You can take your flames somewhere else.

I guided people to the 5 step procedure in Post #1. This 30 step procedure is for people who do not have PS/2 Ports and cannot use a PS/2 device.

My RAM Limitation Patch is compromised by the installation of the SP. I added instructions for people who already are using the RAM Limitation Patch. If you don't have the RAM Limitation Patch installed, you can ignore the steps listed.

My WDMEX.VXD program is an alternative to WDMSTUB without the flaw mentioned. If you bothered to read the instructions, I give an alternative procedure that gets around the flaw but of course involves more work.

If I was working for Microsoft, there wouldn't be any programs for Windows 98.

You will have more room for those eggs when you take your foot out of your mouth.

[Foxbat]

Hu$tle, on 18 September 2012 - 09:51 PM, said:

You expect users to go through 30 steps instead of 5 just to get things working?

Hu$tle, please lighten up. You're looking for problems where there isn't any.

rloew posted this temporary solution at the request of PROBLEMCHYLD. It is complex, and he doesn't have to post it, yet he did in order to help those who can't wait for a better solution. Nowhere does it mention the purchase of his software. He is only making sure that users of his patches don't run into any issues. Those who have his patch will follow the indicated steps, and those who do not will skip it. If you do not like the current solution, give him more time to test and produce a better one.

[zuko1]

@ Hu$tle I'm just grateful for any help with windows 98 albeit payed for or free. Without the GENIUSES on this forum Windows 98/ME would have been dead years ago. I'v amazed friends of mine with what Windows 98 is capable of these days and it's all thanks to these VERY skilled programmers who put the time in to help this aging operating system.

[PROBLEMCHYLD]

rloew

What about creating an WDMEX.VXD version to the same point where WDMSTUB.SYS is? Maybe add your WDMEX.VXD to SP3. If its equivalent to WDMSTUB.SYS, then there is no lost. This might be helpful in the future. The extended version, users will have to pay for. If its not a good solution, I'll keep trying to come up with a better one.

This post has been edited by PROBLEMCHYLD: 19 September 2012 - 03:27 PM

[jaclaz]

Cannot remember if already talked about .
I came across this and thought it might be of use (or completely fail to):
http://retired.beyon...ls/dddtools.htm

Quote

Device Driver Remover for Windows 95 & Windows 98
Writing PNP device drivers under Windows 95 or 98? The Remove Driver Utility follows Microsoft's directions layed out in the Device Driver Kit, to remove all traces of your device driver. This allows Windows to ask for a new driver once the device is plugged in again. Great for USB WDM Device Driver Programming.

http://retired.beyon...ools/remove.zip

jaclaz

[PROBLEMCHYLD]

jaclaz, on 02 October 2012 - 09:49 AM, said:

Cannot remember if already talked about .
I came across this and thought it might be of use (or completely fail to):
http://retired.beyon...ls/dddtools.htm

Quote

Device Driver Remover for Windows 95 & Windows 98
Writing PNP device drivers under Windows 95 or 98? The Remove Driver Utility follows Microsoft's directions layed out in the Device Driver Kit, to remove all traces of your device driver. This allows Windows to ask for a new driver once the device is plugged in again. Great for USB WDM Device Driver Programming.

http://retired.beyon...ools/remove.zip

jaclaz

Thanks, but this won't work. It doesn't automate the tasks needed to delete all necessary drivers. With the tool, one will have manually delete which is not ideal. Its basically the same as going through Safemode. We need a tool to scan for all USB devices, delete them, reboot and re-detect on startup without the users input. I haven't given up yet and have no intentions to do so. If we don't find a universal solution, I will be forced to rest my hand.

[Drugwash]

I'll be looking into this as soon as I can take a break from the other projects (most importantly Dll Details, which must be brought to a better level). The issue popped up earlier in the SP thread and I've mentioned there the care that must be taken when building such tool, not to break something else or allow its usage for malicious purposes.

Anyway, it's good that the USB input devices issue came up now as it offers the necessary edge to approach the subject in the right manner. Problem is, I don't have a USB keyboard to test with - actually there is one Logitech G15, but it's defective and couldn't fix it as it needs spare parts. I do have a working USB mouse but that's not enough to test such tool, if/when I get to work on it. And come to think about it, there might not be any spare machine around for testing, with a USB 2.0 controller... Ugh!

[loblo]

PROBLEMCHYLD, on 16 October 2012 - 02:08 PM, said:

Thanks, but this won't work. It doesn't automate the tasks needed to delete all necessary drivers. With the tool, one will have manually delete which is not ideal. Its basically the same as going through Safemode. We need a tool to scan for all USB devices, delete them, reboot and re-detect on startup without the users input. I haven't given up yet and have no intentions to do so. If we don't find a universal solution, I will be forced to rest my hand.

Isn't deleting all the USB keys under HKLM\Enum, which can be done with a batch file using reg.exe or the silent import of a registry file with key deletion entries, enough?

That should flush everything out, removing all the junk that accumulates there, and whatever USB device is still plugged on your machine should be redetected and reinstalled automatically on reboot, no?

This post has been edited by dencorso: 16 October 2012 - 08:59 PM