Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

What's the difference between "DevCon.exe" and "InfDefaultInstall.exe" for installing .inf ?

iFengHuangiFengHuang Member Posts: 41

I'm planning to deploy my product with Inno Setup, including a driver.
After some searches, I find that DevCon and InfDefaultInstall seem to be able to do this.
What's the difference between them? Which is better?

Comments

  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 7,213

    I’m not sure what you’re planning, but you can’t redistribute Devcon. It’s contrary to the
    MSFT license terms.

    Peter

    Peter Viscarola
    OSR
    @OSRDrivers

  • iFengHuangiFengHuang Member Posts: 41

    @Peter_Viscarola_(OSR) said:
    I’m not sure what you’re planning, but you can’t redistribute Devcon. It’s contrary to the
    MSFT license terms.

    Peter

    :/ Thanks, So I think I have to choose InfDefaultInstall.

  • Doron_HolanDoron_Holan Member - All Emails Posts: 10,433
    via Email
    I have never heard of anyone depending on InfDefaultInstall in their installer. Why not call DiInstallDriver yourself so you understand if a reboot is needed directly?
    d
  • iFengHuangiFengHuang Member Posts: 41

    @Doron_Holan said:
    I have never heard of anyone depending on InfDefaultInstall in their installer. Why not call DiInstallDriver yourself so you understand if a reboot is needed directly?

    See here Installation of Callout Drivers,

    A callout driver can be installed by right-clicking the driver's setup information file (INF) file and selecting Install from the pop-up menu that appears.

    When you do this, it just call InfDefaultInstall.exe and parse the .inf file full path as param.

    So this for me is the simpliest way works with Inno Setup.

  • Doron_HolanDoron_Holan Member - All Emails Posts: 10,433
    via Email
    You are conflating a developer scenario with a setup/installer scenario. What is good for the developer is not good for the installer. How are you handling the case where you need to reboot when calling InfDefaultInstall?
    d
  • iFengHuangiFengHuang Member Posts: 41
    edited May 13

    @Doron_Holan said:
    You are conflating a developer scenario with a setup/installer scenario. What is good for the developer is not good for the installer. How are you handling the case where you need to reboot when calling InfDefaultInstall?

    I tested the deployment environment and never needed to restart it. During the development and deployment tests, I never restarted and had not any problems.

  • Doron_HolanDoron_Holan Member - All Emails Posts: 10,433
    via Email
    Then clearly you will never need to handle a reboot

    d
    d
  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 7,213

    Then clearly you will never need to handle a reboot

     
    Post of the week, right there. And it's only Monday!
     
    That, Mr. Holan, is an impressive achievement.
     

     
    Peter

    Peter Viscarola
    OSR
    @OSRDrivers

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Developing Minifilters 29 July 2019 OSR Seminar Space
Writing WDF Drivers 23 Sept 2019 OSR Seminar Space
Kernel Debugging 21 Oct 2019 OSR Seminar Space
Internals & Software Drivers 18 Nov 2019 Dulles, VA