Proposal: Integrate SDI Tool Support into Topgrade

[niStee]

Hi Topgrade Team and Community,

I would like to propose adding an optional integration with SDI Tool, a utility that offers extensive driver management and installation options. This feature would allow Topgrade to not only manage system updates but also to support driver maintenance through SDI Tool’s command-line interface.
Feature Overview

The idea is to enable Topgrade to interact with SDI Tool, either by:

Detecting if SDI Tool is installed on the system.
Optionally invoking SDI Tool commands during maintenance operations.

For example, consider using SDI Tool’s command-line switches (detailed on their settings page) to enable tasks like:

Installing specific drivers (e.g., “-install ”).
Running in 7z archiver mode (“-7z”) for handling driver driverpacks.
Logging and autoupdate features (e.g., “-autoupdate”, “-verbose:”).

Benefits for Users

Streamlined Driver Management:

Integrating SDI Tool will allow users to leverage its powerful driver install and update capabilities directly from Topgrade.

Enhanced Automation:

Users can automate tasks like driver installation or update verification by incorporating SDI Tool’s command switches. For instance, if a system update is detected, Topgrade might trigger SDI Tool commands to check and install recommended driver updates.

Optional Feature:

Since not every user will need or use SDI Tool, this integration should be opt-in. Detection mechanisms or configuration flags can be implemented to enable SDI Tool support only when desired.

Implementation Considerations

Integration Points:

Identify parts of Topgrade’s workflow where SDI Tool can be useful. For instance, after executing system updates, Topgrade could check for driver updates via SDI Tool using commands such as:

• “-checkupdates”

• “-autoupdate”

• Other switches like “-install” for specific hardware IDs.

Configuration Management:

SDI Tool uses configuration options (e.g., “-drp_dir”, “-index_dir”) saved in its sdi.cfg file. A simple integration could allow users to specify these settings or point Topgrade to a pre-configured SDI Tool environment.

Error Handling:

Handle cases where SDI Tool is not installed or returns an error. For example, if a command returns an exit code indicating a required reboot (e.g., 0x80000001) or any other error, Topgrade should notify the user with actionable feedback.

User Control:

Provide clear documentation and configuration options so that users can enable or disable SDI Tool integration. This may include a command-line flag or settings entry within Topgrade.

Example Use Case

Imagine a scenario where a user runs Topgrade to update their system. During this process, Topgrade checks for the presence of SDI Tool. If found, based on the user’s configuration, Topgrade could automatically:

Execute a snapshot of driver states.
Invoke SDI Tool with parameters such as “-autoupdate” or “-install ”.
Log driver installation details using SDI Tool’s verbose logging (e.g., “-verbose:20”).

Discussion Points

What are the potential challenges or dependencies from integrating SDI Tool?
Are there specific scenarios where this integration would be especially beneficial?
Should we consider additional configuration support (e.g., reading the sdi.cfg file) to allow even more granular customization?

I look forward to your feedback on this proposal and any suggestions on how to best integrate SDI Tool in a way that benefits our community.

Thanks for considering this idea!

[GideonBear]

Maybe it's also worth looking at SDIO (1, 2)? SDIO is open source (SDI says it's open source but the SourceForge code is private), and has had commits as recently as 2 weeks ago; so it's at least actively maintained. I'm guessing it's a fork of SDIO, and that SDI is no longer maintained; in that case I would strongly oppose adding support for SDI, but SDIO seems fine.

[niStee]

#1269