We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!
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.
Introduce a feature in Snappy Driver Installer Origin (SDIO) that scans for devices with hardware IDs (HWIDs) not currently covered in the driver packs, checks whether the installed drivers have valid certificate chains, and then suggests a contribution workflow for users to upload/share those drivers with the SDIO community.
Motivation
- Expand coverage: Many users encounter obscure or legacy devices whose drivers are not yet included in SDIO’s packs.
- Preserve rare drivers: Without a contribution pipeline, signed but uncommon drivers risk being lost over time.
- Community empowerment: SDIO is community‑driven; enabling safe contributions strengthens its sustainability.
- Audit‑proofing: Certificate validation ensures only trusted drivers are suggested for upload, reducing risk of tampered binaries.
Proposed Workflow
- HWID Scan: SDIO already detects HWIDs. Extend this to flag devices with no matching driver in the packs.
- Certificate Check: Verify that the installed driver has a valid signature chain (e.g., WHQL or vendor‑signed).
- Contribution Prompt: Offer the user an option to export the driver package (
.inf+ binaries) into a structured archive.
I like your thinking. Over the last couple of months I've been developing a tool to verify driver packages and compile driver packs to augment the usual ones. This is going well and the new SDIO driver pack is the result of this.
As you know the signatures are stored in a security catalog (*.cat) which I'm still learning how to read.
This would be a useful tool, I'll keep it mind and work towards it.
I've been working on this this week and will have something ready for testing in the next week or so
Here's what I have so far. Give it a run and see if you think it will be useful. Extract to your SDIO directory and check the txt file for additional info.Introduce a feature in Snappy Driver Installer Origin (SDIO) that scans for devices with hardware IDs (HWIDs) not currently covered in the driver packs, checks whether the installed drivers have valid certificate chains, and then suggests a contribution workflow for users to upload/share those drivers with the SDIO community.
Motivation
- Expand coverage: Many users encounter obscure or legacy devices whose drivers are not yet included in SDIO’s packs.
- Preserve rare drivers: Without a contribution pipeline, signed but uncommon drivers risk being lost over time.
- Community empowerment: SDIO is community‑driven; enabling safe contributions strengthens its sustainability.
- Audit‑proofing: Certificate validation ensures only trusted drivers are suggested for upload, reducing risk of tampered binaries.
Proposed Workflow
- HWID Scan: SDIO already detects HWIDs. Extend this to flag devices with no matching driver in the packs.
- Certificate Check: Verify that the installed driver has a valid signature chain (e.g., WHQL or vendor‑signed).
- Contribution Prompt: Offer the user an option to export the driver package (
.inf+ binaries) into a structured archive.
https://www.glenn.delahoy.com/downloads/sdio/SDIOBackupDrivers100.zip
