rloew

USB Keyboards and Mice

50 posts in this topic

OMG ! Welcome to the forum, I hope. My 1st post/comments.

I hope I don't fuel the (usb) fire any more, but here goes.

Has anyone else had an install problem with 98 SE SP 3.x, when your system has both a USB keyboard & mouse ?

Mine is: Viewsonic KBM-KU-306 & MS Comfort Optical Mouse 3000

MB=Asus A7N8X - nVidia nForce2 controllers - AMD Anthalon 1300 CPU - 512 Mb Ram

Did a fresh clean install Win 98 SE. Installed all necessary drivers to eliminate any unknown devices in the System /Device Manager section,

including (nVidia ?) usb20_98me.exe Ver 2.0.8 (that removed a PCI Universal Serial Bus-unknown ? device)

Installed IE 5.5 & Dirextx 9.0c. Did a MS Backup of my C: drive All worked fine to this point

Now I installed SP 3.6 main updates only. When install was finished, I shut down.

Then I would reboot to Safe Mode, to remove any and all USB stuff in the device manager. (As to your usb 2.0 notice/instructions)

KB & Mouse had to remain attached or PC won't boot up.

Hope that was correct procedure to follow. Upon S/D & Reboot: detection of Standard Open HCI Usb Host Controller started.

Was seeking files usb.inf & then Sp3.cab. When finished installing software your hardware requires dialog message popped up, both

the mouse & keyboard locked up/no response. SD & reboot again to add new H.W. wizard window looking to install Standard Open HCI Usb Host Controller

again, and again no response from mouse or KB. This continues to reoccur on every reboot, No KB or mouse. Tried at least 6 times with no success.

Booted to safe mode to restore my previously backed up system (replace all files & restore Registry & H.W. settings)

Interesting note after System restore is all my Usb storage devices were recognized and usable. About 6 different ones. Could do fast removal also.

@ReK67:

There is a problem when Installing USB Keyboards and Mice. Initially the BIOS uses SMI to emulate a PS/2 Keyboard and Mouse, allowing the USB Keyboard and Mouse to be used in DOS and during Boot. When the USB Controller Drivers are started, they take over, telling the SMI to stop Emulating. The Compatability Drivers for the Keyboard and Mouse only recognize PS/2 Devices.

This disables the Keyboard and Mouse until the Windows Keyboard and Mouse Drivers are loaded. Unfortunately, as you have discovered, you are unable to Install the Drivers without access to the Keyboard and Mouse causing a Catch 22. You were able to Install them initially because the Windows Installer suppressed the Dialogs that you are getting hung up on.

There are a number of options. A partial list follows:

1. Attach a PS/2 Keyboard and/or Mouse, in addition to the USB Keyboard and Mouse, either is enough. Use the PS/2 Device to reply to the Dialogs.

2. Manually Disable, not remove, all of the USB Controllers in Safe Mode. Make sure your USB Keyboard and Mouse are not connected to the same Controller. Reboot, you should have access again. Enable one Controller and reboot. Repeat until you get an Installation Dialog. Either the Keyboard or the Mouse should still be working. If not you have to move one and start over. If one is working you can use it to install the Driver for the other. You should then be able to reenable all of the Controllers, reboot, and install the remaining Driver with the other Device.

Although I can't say for sure, I don't think it is the SP that caused the problem. More likely it was the Driver refresh. The Instructions don't take into account USB Keyboards and Mice.

I would have Posted this as a reply but the original Thread is locked.

Edited by rloew
0

Share this post


Link to post
Share on other sites

I was just about to ask you to shed some light on this specific issue. Thanks

I will list your instructions in version 3.7.

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

I was just about to ask you to shed some light on this specific issue. Thanks

I will list your instructions in version 3.7.

I'm not sure the instructions I listed are suitable for the SP. They were intended to help recover after the damage was done.

It may be OK not to remove the USB Keyboard and Mouse Drivers themselves, just the Controllers. This needs to be tested. It would be a much better solution than the ones I posted.

0

Share this post


Link to post
Share on other sites

I have some good news :thumbup Thanks ReK67, rloew and jaclaz.

I have found you doNOT need safe mode to delete the USB drivers only if you have done the following below.

The first 3 registry applies to all Win98 systems.

The last 4 are specifically for my system hardware. If you guys find all the necessary keys after the first 3 that are listed, we might have something. I created a REG file from all of my USB devices plugged in, that will delete the drivers. After the installation of Main Updates, I did NOT reboot but imported the registry file to delete the drivers. I did NOT remove any USB devices. I rebooted and every single device that was left plugged in were re-detected. If everyone does this for their systems it would be a lot easier. Novices will have to follow the original instructions if they are not up to this. You'll have to find your own keys because every system is different. I'm working on your problem ReK67. The procedure would only need to be done once unless new USB drivers has been added.

1. [HKEY_LOCAL_MACHINE\Enum\HID]

2. [HKEY_LOCAL_MACHINE\Enum\USB]

3. [HKEY_LOCAL_MACHINE\Enum\USBSTOR]

4. [HKEY_LOCAL_MACHINE\Enum\PCI\VEN_1033&DEV_0035&SUBSYS_17351033&REV_43]

5. [HKEY_LOCAL_MACHINE\Enum\PCI\VEN_1033&DEV_00E0&SUBSYS_00E01735&REV_04]

6. [HKEY_LOCAL_MACHINE\Enum\PCI\VEN_1033&DEV_0035&SUBSYS_10331033&REV_43]

7. [HKEY_LOCAL_MACHINE\Enum\PCI\VEN_8086&DEV_7112&SUBSYS_00000000&REV_01]

P.S

If we all start posting our keys we can have a full list.

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

@PROBLEMCHYLD

I am not sure to get the last part of your post. :unsure:

The "last four" keys are hardware dependent, every hardware will have it's own Ven and Dev.

VEN_1033&DEV_0035&REV_43 is a PCI to USB Host controller by NEC

VEN_1033&DEV_00E0&REV_04 is a USB 2.0 Host Controller by NEC

VEN_8086&DEV_7112&REV_01 is a PIIX4/4E/4M USB Interface by Intel Corporation

http://www.pcidatabase.com/

and:

http://web.archive.org/web/20070901052015/http://members.datafast.net.au/~dft0802/downloads.htm

(maybe PCI.ZIP can be *somehow* reused in combination with the csv or tab delimited available from tne pcidatabase site)

jaclaz

0

Share this post


Link to post
Share on other sites

@PROBLEMCHYLD

I am not sure to get the last part of your post. :unsure:

The "last four" keys are hardware dependent, every hardware will have it's own Ven and Dev.

VEN_1033&DEV_0035&REV_43 is a PCI to USB Host controller by NEC

VEN_1033&DEV_00E0&REV_04 is a USB 2.0 Host Controller by NEC

VEN_8086&DEV_7112&REV_01 is a PIIX4/4E/4M USB Interface by Intel Corporation

http://www.pcidatabase.com/

and:

http://web.archive.org/web/20070901052015/http://members.datafast.net.au/~dft0802/downloads.htm

(maybe PCI.ZIP can be *somehow* reused in combination with the csv or tab delimited available from tne pcidatabase site)

jaclaz

The last 4 are for my system. I just posted them as an example so users will have an idea on what to look for.

If everyone did this, it would be easy just to import the reg file before or after running main updates.

I have been playing with this for a few hours trying to make sure everything works. So far so good.

0

Share this post


Link to post
Share on other sites

I have found you doNOT need safe mode to delete the USB drivers only if you have done the following below.

The first 3 registry applies to all Win98 systems.

1. [HKEY_LOCAL_MACHINE\Enum\HID]

2. [HKEY_LOCAL_MACHINE\Enum\USB]

3. [HKEY_LOCAL_MACHINE\Enum\USBSTOR]

These 5 also need to be deleted for a more complete cleanup:

1. [HKEY_LOCAL_MACHINE\Enum\SCSI]

2. [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\HID]

3. [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\SCSIAdapter]

4. [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Storage]

5. [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\USB]

A program will be needed to recurse the PCI keys to identify the USB Controller Drivers.

In addition, individual Driver Manufacturers create their own Keys in Enum and Class for their IOS Drivers as well.

This approach, like the one in USESP3, will be problematical for USB Keyboard and Mouse Users.

A more selective approach is needed.

0

Share this post


Link to post
Share on other sites

The last 4 are for my system. I just posted them as an example so users will have an idea on what to look for.

If everyone did this, it would be easy just to import the reg file before or after running main updates.

I have been playing with this for a few hours trying to make sure everything works. So far so good.

Actually, it would be easier if you could test the mentioned PCI.EXE and verifies that it can identify correctly your hardware.

I mean, we have already a complete list of PCI devices, no need to rebuild it piece by piece by user's contribution, let's see if we can find a way to use the existing lists and tools in such a way to make your procedure easy to replicate to the final users.

jaclaz

0

Share this post


Link to post
Share on other sites

I have found you doNOT need safe mode to delete the USB drivers only if you have done the following below.

The first 3 registry applies to all Win98 systems.

1. [HKEY_LOCAL_MACHINE\Enum\HID]

2. [HKEY_LOCAL_MACHINE\Enum\USB]

3. [HKEY_LOCAL_MACHINE\Enum\USBSTOR]

These 5 also need to be deleted for a more complete cleanup:

1. [HKEY_LOCAL_MACHINE\Enum\SCSI]

2. [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\HID]

3. [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\SCSIAdapter]

4. [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Storage]

5. [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\USB]

A program will be needed to recurse the PCI keys to identify the USB Controller Drivers.

In addition, individual Driver Manufacturers create their own Keys in Enum and Class for their IOS Drivers as well.

This approach, like the one in USESP3, will be problematical for USB Keyboard and Mouse Users.

A more selective approach is needed.

Thanks, I am trying to figure out the USB Keyboard and Mouse issue. Came across this in the process. I think you guys are a big help with the links and suggestions.

Here's a before and after screenshot of the USBDEL.REG files.

It works as if I deleted all the drivers in safe mode. It works before or after main updates.

You can see that my Human Interface Devices, Storage Device and Universal Serial Bus controller are gone after the import of the reg file.

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

Here's a before and after screenshot of the USBDEL.REG files.

It works as if I deleted all the drivers in safe mode. It works before or after main updates.

You can see that my Human Interface Devices, Storage Device and Universal Serial Bus controller are gone after the import of the reg file.

Deleting the Enum Keys works but leaves a lot of clutter in the Class Key.

Your file will need a list of every USB Controller ID in existence.

I have a .REG File that deletes both Keys entirely and replaces them with a bare minimum set of non-discoverable entries. It comes in handy when moving Windows 9x from one machine to another.

0

Share this post


Link to post
Share on other sites

Deleting the Enum Keys works but leaves a lot of clutter in the Class Key.

Your file will need a list of every USB Controller ID in existence.

I have a .REG File that deletes both Keys entirely and replaces them with a bare minimum set of non-discoverable entries. It comes in handy when moving Windows 9x from one machine to another.

I need a tool like Devcon. I was just experimenting trying to come up with a universal solution. I won't give up though.

The PCI.EXE did recognize my hardware but not my USB 2.0 adapter.

Thats means another tool will have to be added for add-on adapters.

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

The PCI.EXE did recognize my hardware but not my USB 2.0 adapter.

Thats means another tool will have to be added for add-on adapters.

You mean the HKEY_LOCAL_MACHINE\Enum\PCI\VEN_8086&DEV_7112&SUBSYS_00000000&REV_01 or an actual USB device (under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\USB or where)? :unsure:

That tool is limtied to PCI, by design.

Can you see them with USBview (GUI):

http://www.ftdichip.com/Support/Utilities.htm

jaclaz

0

Share this post


Link to post
Share on other sites

I too had the USB Keyboard + Mouse problem + overcame it with PS/2 Keyboard / Mouse like rloew advised (But hate using them for all the known reasons) but, it was worth it just to use this service pack as it's so good. If the USB Keyboard/Mouse fix could be implemented into the installer it would be the best SP i ever used in 98 se . P.S Thanks rloew for starting this Thread as i too wanted to reply to the last one but couldn't. P.P.S I did manage to get them working with drivers from the 98 CD but it reverted back to non functional on restart.

Edited by zuko1
0

Share this post


Link to post
Share on other sites

I too had the USB Keyboard + Mouse problem + overcame it with PS/2 Keyboard / Mouse like rloew advised (But hate using them for all the known reasons) but, it was worth it just to use this service pack as it's so good. If the USB Keyboard/Mouse fix could be implemented into the installer it would be the best SP i ever used in 98 se . P.S Thanks rloew for starting this Thread as i too wanted to reply to the last one but couldn't. P.P.S I did manage to get them working with drivers from the 98 CD but it reverted back to non functional on restart.

I need some tools to work with. I need some suggestions. I am working on it as we speak searching high and low.

I wonder if some type of emulator can be used or a generic safe mode driver? :ph34r:

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

Thank you ALL for your advice & replies !

I was just made aware of this new topic via an email from rloew (personal conversation)

I kept watching the SP 3.6 topic for response and saw none.

I will read all, carefully, and reply as soon as I can with my progress.

I just wanted to reply quickly, to let all know that I am not ignoring your attempts for solutions.

Thanks again for making me feel welcome and for your help.

ReK67

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.