Ultra 4 port USB Hub driver issue

[Guest]

Walt,

Can you say that you're better off now than you were before? Also, the
other person who performed this procedure said that additionally he pointed
the prompts for drivers to C:\Windows\System32, rather than just to the C
drive. Not being there, I'm not sure that's a good tip or not. Anyway, he
said that, over time, these prompts eventually worked themselves out and
everything installed, but then that's just his experience. Post back on any
news. I'm curious about this procedure, since it seems somewhat unorthodox
to say the least. I wonder who and how someone figured this out.

 

[Guest]

Yes, I am better off. Once the devices were recognized and drivers installed,
I continued to get the same "driver needs to be installed" message, so I said
to stop looking and don't post the message for this device any longer. All
the devices are available when plugged in, so looks like I'm good to go.
Thanks for the support and help. I'm happy to have the problem resolved.

Walt

 

[Guest]

Walt,

Fantastic! You're 100%? This is the 2nd time that that procedure produced
such a great result, on this forum, as far as I know. I've only seen it used
twice here. Both times, the results were the same.

 

[Guest]

Yes, I'm 100%. Added my Canon camera last night. Vista found a driver on my
hard drive, said it wasn't certified but I installed it anyway. I think the
"not certified" driver warning is a bug because I only load certified /
approved software and drivers, not junk, and that was the 2nd warning I
received. Anyway, I'm good, and thanks for your help.

Walt

 

[Guest]

Walt,

It shouldn't be a bug giving you the "not certified" message. That message
should mean that the drivers haven't been tested by Microsoft and "certified"
(by Microsoft) as working properly in Vista. Vendors are supposed to submit
their drivers to Microsoft for testing and "certification" before they
release them to the public. A lot of vendors do this, but some don't.
Microsoft has found that most crashes in Windows are caused by "uncertified"
drivers, thus the requirement that drivers be "certified," and when they
aren't you get a message for your information in case you have a problem.
You likely already knew this, but just in case.

 

[Guest]

Walt,

We now have a 3rd person who has successfully performed this procedure.
However, this person's experience was a little different. After removing all
those inf files, he got a BSOD when rebooting. After several failed
attempts, he managed to boot into safe mode. In safe mode, he connected his
USB and pointed it to System32, and Vista installed the drivers. After that,
he managed to boot into standard mode, and all is well with his system. This
procedure can cause anxiety.

 

[Guest]

I never thought about accessing SM to load the drivers but a good idea.
Thanks for letting me know.

I realize the issue with the certified drivers, but as this procedure
finally produced a better result than no driver at all, I wanted to take the
chance.

Thanks
Walt

 

[Guest]

Walt,

I suspect that he got the BSOD because he didn't connect his USB after
completing the procedure and before his initial boot. I think he may have
been lucky to install drivers after getting a BSOD. Any landing you can walk
away from is a good landing.

Most uncertified drivers don't cause a problem, just enough do to cause
problems (Microsoft takes the blame), so that Microsoft throws a fit when
vendors distribute drivers without submitting them for testing.