This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Installing Device Drivers Vista
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2008
10:41 AM
Installing Device Drivers Vista
Im installing a signed device driver silently on Vista using the dpinst. The exit code is invalid basically because Vista is prompting do you want to installthis device driver, but Im installing silently.
Is there a work around or is the DIFX 2.10 utility a workable solution?
Is there a work around or is the DIFX 2.10 utility a workable solution?
(8) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 05, 2008
02:48 AM
If your driver package has been signed successfully for Windows Vista you should be able to install the device driver package 'silently'. How do you call DPInst? What kind of InstallShield project do you use?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 05, 2008
03:21 AM
Hi Nick
Im using a Basic Installshield Project.
These are the command lines
Sprintf(CmdLine, '/PATH "%s" /S /SW', INFFolder);
I have also used
Sprintf(CmdLine, '/PATH "%s" /Q', INFFolder);
If I install in UI mode it starts to install the device driver and then Vista pops up a message something like 'Device Driver Installation detected do you want to install or cancel'. In silent mode this cannot appear hence the -2147418112 error exit code I recieve from Installshields LaunchApplication function.
If I run the device driver install in UI mode and then re-run in silent mode I receive a 0 exit code.
Im using a Basic Installshield Project.
These are the command lines
Sprintf(CmdLine, '/PATH "%s" /S /SW', INFFolder);
I have also used
Sprintf(CmdLine, '/PATH "%s" /Q', INFFolder);
If I install in UI mode it starts to install the device driver and then Vista pops up a message something like 'Device Driver Installation detected do you want to install or cancel'. In silent mode this cannot appear hence the -2147418112 error exit code I recieve from Installshields LaunchApplication function.
If I run the device driver install in UI mode and then re-run in silent mode I receive a 0 exit code.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 05, 2008
05:05 AM
What´s the main reason using DPInst instead of DIFxAPP which can be used inside Basic MSI projects for driver components. Have you tried that?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 05, 2008
07:49 AM
Hi Nick
Main reason for using DPInst is that the project does not use Features and Components. The project uses custom tables in DirectEditor to dynamically create its own custom Features (Modules) and Components.
I have a copy of DIFX 2.10, would there be an advantage of using that? Failing that I will ensure the drivers are properly signed.
Main reason for using DPInst is that the project does not use Features and Components. The project uses custom tables in DirectEditor to dynamically create its own custom Features (Modules) and Components.
I have a copy of DIFX 2.10, would there be an advantage of using that? Failing that I will ensure the drivers are properly signed.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 05, 2008
08:44 AM
Normally UI mode does not have elevated privileges, so I suggest that´s the reason why DPInst fails. The requestedExecutionLevel of the embedded manifest of DPInst is set to 'highestAvailable'.
I would recommend to launch DPInst with a deferred custom action in system context.
I would recommend to launch DPInst with a deferred custom action in system context.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 05, 2008
09:38 AM
Hi Nick
I did want to try and avoid using a deferred CA, but seems I have no chocie at this point.
It now works with the CA type changed.
Thanks for your time and effort.
I did want to try and avoid using a deferred CA, but seems I have no chocie at this point.
It now works with the CA type changed.
Thanks for your time and effort.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 05, 2008
10:35 AM
You could also use a InstallScript CA during the UI sequence using LaunchApplication with LAAW_OPTION_USE_SHELLEXECUTE
and 'runas' as the lpVerb of the SHELLEXECUTEINFO Structure.
That would launch the application with elevated privileges but would also raise UAC.
and 'runas' as the lpVerb of the SHELLEXECUTEINFO Structure.
That would launch the application with elevated privileges but would also raise UAC.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 06, 2008
05:48 AM
Yes I may try that, thanks again for your help.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)