Gape

98 SE SP 3.32

2,361 posts in this topic

Guys, what exactly is the problem with MS' usbhub20.sys and Win98SE? I forgot and finding that info in such long topic isn't easy. Besides, I'm looking at my VIA VT6202 USB 2.0 Hub driver details panel and it says usbhub20.sys 5.00.2195.6891 (Microsoft). The controller also uses a MS driver usbehci.sys 5.00.2195.6882, with USBPORT.SYS 5.00.2195.5652.

My Lexmark X1150 printer/scanner works fine (used to, cartriges are now dry), the CSR Bluetooth dongle is also active and running fine and whatever USB Flash stick I plug into the only free outlet, works without any issue.

So, again, what seems to be the problem with that driver and VIA USB chipsets...?

I have been trying to figure out the same thing. I don't understand how the MS file works with your Via but not others.

I confirm xRayeR's results:

In my experience, the last USBPORT.SYS to work OK in Win 98SE is v. 5.0.2195.5652, while for USBSTOR.SYS (in case one installs it with WDMSTUB.SYS v. 5.0.0.6 from NUSB30E) it's v. 5.0.2195.6773 (from KB823086). And for USBEHCI.SYS, the latest version that works is v. 5.0.2195.6882 (the latest available for W2k, check it here). Now, in what regards USBHUB20.SYS, it's more complicated: almost all chipsets work ok with v. 5.0.2195.6891, but VIA's don't. For VIA's chipsets, one needs VIA's own USBHUB20.SYS v. 4.90.3000.11 (findable inside VIA_USB2_V270p1-L-M), in order to avoid BSOD's on removing (hot-deplugging) USB 2.0 HUBs from the machine. Note that it must be substituted by hand, in true DOS, because NUSB3.3 contains v. 5.0.2195.6891, so it's really a downgrade.

Yippe! I did have a USBHUB20.SYS v. 4.90.3000.11 that I found last week. Just booted the sp3 Compaq 6350 into dos and replaced the existing usbhub20 with the via.. rebooted... and voila ... no bsod or crashes anywhere in sight. I've been plugging and unplugging various flash drives for the last 20 minutes and each new one is recognized and the system plays nice when I remove any of them. I'll keep my fingers crossed.

Thanks you guys.

One system down and five more to test. This is fun.

0

Share this post


Link to post
Share on other sites

So if i understood correctly, the only issue would be "BSOD's on removing (hot-deplugging) USB 2.0 HUBs", as per dencorso's quote above.

I'm not quite sure if "unplugging USB 2.0 HUBS" is the accurate statement, or if it's about USB 2.0 DEVICES. Truth be told, I never unplug any USB device without first ejecting it from the systray icon, especially to make sure any possible cache has been flushed, in order to avoid corrupt files.

However, if that's the only issue, then we may be better off trying to fix it using this particular file set through patches of some kind, instead of going around looking for harder-to-implement solutions.

0

Share this post


Link to post
Share on other sites

Here is another crazy idea. I can remove USBHUB20.SYS from Main Updates altogether. After that, create a batch file to prompt users to install the specific version for their systems. Me personally, I'm not looking to downgrade files but I am and will be considerate of others. So far using the newer files has only increase performance because no has complained about any decrease in performance. And yes, my system flies :thumbup

Warning! Remove all USB devices before continuing........

Do your system contain any VIA Technologies hardware? Press (Y)es (N)o

If no option is chosen, then you will not have any USB 2.0 drivers unless you manually place the file in its respective directory. Doing it this way, the wrong driver would never get installed. I just need someone to create the batch file. Then everyone will be happy :thumbup

P.S

Then we are back to the people who have multiple USB2.0 devices. We need a one file fits all or trouble might be headed our way :o Drugwash makes a good point, I would rather patch the Microsoft version thats known to work with all chipset except VIA then to use the VIA which might not work with most chipsets.

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

I confirm xRayeR's results:

In my experience, the last USBPORT.SYS to work OK in Win 98SE is v. 5.0.2195.5652, while for USBSTOR.SYS (in case one installs it with WDMSTUB.SYS v. 5.0.0.6 from NUSB30E) it's v. 5.0.2195.6773 (from KB823086). And for USBEHCI.SYS, the latest version that works is v. 5.0.2195.6882 (the latest available for W2k, check it here). Now, in what regards USBHUB20.SYS, it's more complicated: almost all chipsets work ok with v. 5.0.2195.6891, but VIA's don't. For VIA's chipsets, one needs VIA's own USBHUB20.SYS v. 4.90.3000.11 (findable inside VIA_USB2_V270p1-L-M), in order to avoid BSOD's on removing (hot-deplugging) USB 2.0 HUBs from the machine. Note that it must be substituted by hand, in true DOS, because NUSB3.3 contains v. 5.0.2195.6891, so it's really a downgrade.

Also non-letal BSODs are possible when disabling/removing controller or hub.

This issue mentioned by Tihiy is precisely the one due to USBHUB20.SYS v. 5.0.2195.6891 and VIA chipsets. While one can recover from the BSOD, the only sensible thing to do at that point is to restart or shutdown the machine.

So if i understood correctly, the only issue would be "BSOD's on removing (hot-deplugging) USB 2.0 HUBs", as per dencorso's quote above.

I'm not quite sure if "unplugging USB 2.0 HUBS" is the accurate statement, or if it's about USB 2.0 DEVICES. Truth be told, I never unplug any USB device without first ejecting it from the systray icon, especially to make sure any possible cache has been flushed, in order to avoid corrupt files.

However, if that's the only issue, then we may be better off trying to fix it using this particular file set through patches of some kind, instead of going around looking for harder-to-implement solutions.

As far as I remember, one has to insert a true USB 2.0 hub, then plug one or more USB 2.0 devices to it, then remove them. Then, if and when one removes the hub, and only then, presto: instant BSOD! I've only had 1st hand experience with hubs, to reproduce this particular BSOD, although Tihiy did mention controllers, too. The hub I used, and still use is one like this (care because there are USB 1.x and USB 2.0 versions of it, and only the USB 2.0 causes the BSOD):

Rotating-USB-Hub-H-005-.jpg

0

Share this post


Link to post
Share on other sites

I got an all VIA machine to play with now.

3.10 has been solid for me so far, but looks like after installing it the start menu is having the old "windows 98" graphics.

0

Share this post


Link to post
Share on other sites

I got an all VIA machine to play with now.

3.10 has been solid for me so far, but looks like after installing it the start menu is having the old "windows 98" graphics.

The Windows start menu changes to the default by design because people wanted the original icons/start banner. This is not a bug. You will need to check the box Windows Millennium Edition/Windows 2000 Theme for the updated icons, only after you have installed Main Updates. Do USBHUB20.SYS 5.0.2195.6891 work with your VIA chipset? Thank you very much for helping me get SP3.x stable :thumbup I think 3.10 will be for many users to come. Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

As far as I remember, one has to insert a true USB 2.0 hub, then plug one or more USB 2.0 devices to it, then remove them. Then, if and when one removes the hub, and only then, presto: instant BSOD! I've only had 1st hand experience with hubs, to reproduce this particular BSOD, although Tihiy did mention controllers, too. The hub I used, and still use is one like this (care because there are USB 1.x and USB 2.0 versions of it, and only the USB 2.0 causes the BSOD):

Rotating-USB-Hub-H-005-.jpg

Hmmm... :unsure:

This is HIGHLY speculative. No idea whether this would be the case or not!

Any chance that such a device would be treated as a "Composite Device?"

If so, there may or may not be differences in behavior now that changes have been made to NUSB, etc.

Under Win98SE and Win2K, composite devices use USBHUB.SYS (or USBHUB20.SYS for USB2).

Under WinME and WinXP, composite devices use USBCCGP.SYS.

Now that the Windows ME USB1.1 stack and ME-style USB.INF (with use of USBCCGP.SYS) has been implemented, such devices MAY not depend on USBHUB20.SYS anymore.

So the bug may not even exist at all so long as one has a complete collection of the latest unofficial USB updates. :blink:

Someone who knows more about this than me please chime in... :ph34r::lol:

0

Share this post


Link to post
Share on other sites

Sorry guys for the inconvenience, but I forgot to change the version number in a few INF files. This only applies to some of the options installed by SP3.10. Main Updates are ok and all options should install properly now. You will only witness errors in SP3.10 depending on which options you choose. I have release 3.11 and fixed all issues. Installation time is now at 4 minutes 10 seconds instead of 3 minutes 52 seconds approximately :(:}:o:no:

0

Share this post


Link to post
Share on other sites
Warning! Remove all USB devices before continuing........

Do your system contain any VIA Technologies hardware? Press (Y)es (N)o

A small tool could automatically detect the presence of a VIA controller/hub. Remember not everyone using 9x may be computer-literate enough to know what hardware they're operating.

Unfortunately, the tools I can build are all quite large to be used for a single operation. I promised myself I'd try to create a SP installer from scratch, complete with full memory detection, hardware detection, files patching (Explorer icons and all) and other necessary features, but I'm not sure I'll get to see this dream come true, due to the strong heartaches I've been having since yesterday. :(

In the mean time, if those BSOD errors are recoverable, there could be a fair warning about this possiblity at install time and just let it be until we manage to come up with a reasonable solution. Personally I have no such external USB 2.0 HUB to test with; the only external hub on my main machine is the one created by the Lexmark by the name of Generic USB Hub, which is driven by usbhub.sys 5.00.2195.6689 and USBCCGP.SYS 5.1.2600.5585 (just like the other USB 1.1 Root Hubs from the on-board chipset) and is connected to one of the VIA USB 2.0 ports.

0

Share this post


Link to post
Share on other sites

...

but I'm not sure I'll get to see this dream come true, due to the strong heartaches I've been having since yesterday. :(

...usbhub.sys 5.00.2195.6689...

Always put your health first. You will get to it someday ;)

Do you mean USBHUB20.SYS? :unsure:

0

Share this post


Link to post
Share on other sites

I have to report that, despite my best efforts, I've been utterly unable to elicit a BSOD from Usbhub20.sys v. 5.0.2195.5605. :yes:

Rest assured that the hub I used is not seen as a Composite Device, but simpliy as a "Generic USB Hub" (USB 2.0, High Speed) from Alcor Micro (VID=0x058F; PID=0x6254).

0

Share this post


Link to post
Share on other sites

I have to report that, despite my best efforts, I've been utterly unable to elicit a BSOD from Usbhub20.sys v. 5.0.2195.5605. :yes:

Rest assured that the hub I used is not seen as a Composite Device, but simpliy as a "Generic USB Hub" (USB 2.0, High Speed) from Alcor Micro (VID=0x058F; PID=0x6254).

Aha! :w00t:

Only bad thing is now I'm going to have to dig around through all those files and see if there are any versions later than 5.0.2195.5605 but before 5.0.2195.6891. :wacko::lol:

0

Share this post


Link to post
Share on other sites

Well, AFAIK, Win2k SP4 has v. 5.0.2195.6655 and KB829759 has v. 5.0.2195.6824, but there should be plenty more with lower numbers... :}

But let's let people test v. 5.0.2195.5605 some more, before starting that hunt...

0

Share this post


Link to post
Share on other sites

...

but I'm not sure I'll get to see this dream come true, due to the strong heartaches I've been having since yesterday. :(

...usbhub.sys 5.00.2195.6689...

Always put your health first. You will get to it someday ;)

Do you mean USBHUB20.SYS? :unsure:

I don't think so. There sure is a usbhub.sys 5.00.2195.6689 (USB 1.x) but I don't think that version of usbhub20.sys was ever released.

0

Share this post


Link to post
Share on other sites

Well, AFAIK, Win2k SP4 has v. 5.0.2195.6655 and KB829759 has v. 5.0.2195.6824, but there should be plenty more with lower numbers... :}

But let's let people test v. 5.0.2195.5605 some more, before starting that hunt...

Sounds good. I don't think I'm up to that search tonight anyhow... :zzz:

I don't think so. There sure is a usbhub.sys 5.00.2195.6689 (USB 1.x) but I don't think that version of usbhub20.sys was ever released.

I thought the version number didn't sound right, but USBHUB.SYS should be 4.90.3002 on a 98SE system with the current updates, unless some Win2K USB1 stack files have been added... :unsure:

EDIT:

I remember now, some discussion was made earlier about using the Win2K USB1.1 stack. Not a matter of universal agreement as I recall. :angel

Edited by LoneCrusader
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.