"Automatically detect and update drivers and software"
That's what I use.
![]() | Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years. Thanks, CNET Support |
I'm trying to overwrite drivers not intended for my PC with the correct ones. So, I downloaded INF_AllOS_8.3.1.1009_PV_Intel.exe from Intel and read the docs. I've run it twice using different command line configurations. The result is that there are only four replaced .pnf files in Windows/inf (no other known changes), and I still have the same problems in the Device Manager (can't re-install Universal Serial Bus Controller for example). Specs at bottom of this post.
My questions:
1- Was I mistaken to run INF_AllOS_8.3.1.1009_PV_Intel.exe with command lines C:\>INF_AllOS_8.3.1.1009_PV_Intel.exe -overall -overide -L 0409 -S and then C:\>INF_AllOS_8.3.1.1009_PV_Intel.exe -A -L 0409 -S ? The reason for the second version was that I didn't see some files unpack that the help docs discussed.
2- Is there a tutorial somewhere for completely overwriting an incorrect driver set? My PC is basically functioning but I'm pretty sure the Device Manager problems started when I ran the wrong Intel installer about a month ago.
Mobo - D865GBF
RAM - 4 GB
Bios - BF86510A.86A.0077.P25.0508040031
OS - Win XP Pro SP3
Discussion is locked
Haven't had any RAM or other memory problems to date, and the Intel page at that link states that the max is same as what I have. Anyway ...
According to Intel, the file I named is the correct chipset installer. Simply double-clicking the exe from Explorer didn't address my problems, hence digging farther into the help docs and using command line options.
The BIOS I have was the latest when I installed it several weeks ago.
I'll try that link using automatic detection, although I remember having some problem getting it to function, even with the latest IE. But that was quite a while back.
Just start over. Windows XP installed in about 20 minutes last month and we take notes so we have the right steps for the next time. Sometimes you find an install too broken to spend time on. Well, that's not entirely true. The office charges by the hour so fixing a broke install costs more than starting over so that's what we do if safe mode and removing broke devices doesn't help.
Keep in mind there was this one client that insisted the device manager was perfect even if all devices worked. We loved them.
Bob
Why not go get the latest chipset driver and use the usual install?
It's also possible the BIOS is out of date or is set to disable the controller. This is a very old OS and I'm finding folk trying to install it on say USB 3.0 boards and failing gloriously.
Bob