We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Posting here because it's not a directly SDIO program doubt.
Given a few packages (.cab) with exactly same:
- Driver name, date, HWID, version, .INF, details, systems, etc. and UpdateID (from Microsoft Drivers Catalog)
And different:
- DLLs (same file name but different if binary compared)
Wich one shoul I choose?
Here the Hadrware ID, version date and version number don´t apply because all are the same.
Thanks in advance.
PS: By the way, the screenshoot shows a newer driver than the actually present in DP_SDIO 😉
gee whiz, nothing like choices. I dunno, they all look the same from here. The only thing I can think of is they did a number of bug fixes and released them under the same build number. My inclination would be to go for the one with the latest binary modified dates and be prepared to roll it all back when it fails.
this happens a lot in the Microsoft Drivers Catalog. same INF/version/UpdateID usually means the vendor re-spun the binaries without bumping the version — hotfixes, signing changes, or OS-specific tweaks. if SDIO shows them all as equivalent, safest bet is the package with the newest file timestamps inside the CAB. if it’s a class driver, windows will usually roll back cleanly anyway. annoying, but pretty normal catalog behavior.
I've found the Microsoft Update Catalog really useful when Windows Update doesn't pick up the right driver. Just make sure the hardware ID matches your device before installing, since there can be several similar-looking driver packages.