Sigh...
The following recipient(s) could not be reached:
'[EMAIL PROTECTED]' on 2006 11 22 5:04 PM
The e-mail account does not exist at the organization this
message was sent to. Check the e-mail address, or contact the recipient
directly to find out the correct address.
On 11/22/06, Mike Dimmick <[EMAIL PROTECTED]> wrote:
The best approach is to email the DIFx team: [EMAIL PROTECTED] Address
found at http://www.microsoft.com/whdc/driver/install/difxtools.mspx#EHE.
--
Mike Dimmick
------------------------------
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Scott Palmer
*Sent:* 21 November 2006 20:52
*To:* wix-users@lists.sourceforge.net
*Subject:* [WiX-users] DIFxApp and unsigned drivers
Hello,
I've been given the job of creating a new installer for our product that
needs to install a few device drivers for custom hardware.
I'm using WiX v3 not v2 (because there is no way in hell I'm going to
supply 8.3 filenames).
I built a DIFxApp.wixlib that would work with WiX v3 based on a post I
found among this list and it seemed to work. My installer linked properly
after that. The problem I am having is that while the driver files appear
to get installed, the actual installation of the device does not happen.
After a reboot new hardware is detected and the device drivers are found,
but I want that to happen during the install.
Even worse is the fact that when I un-install the drivers THEN the system
attempts to install the device, only now some of the files are missing since
they have already been removed as part of the un-install.
I'm at my wits end trying to figure out if it is possible to use DIFxApp
at all or if it is simply broken when used with unsigned drivers or WiX 3.
The CustomActions are obviously running, I've checked the log to confirm
that they are doing something.
The section in my WiX source file for the drivers looks like this:
<Component Id="DriverFiles" Guid="MY_REAL_GUID_IS_HERE">
<difxapp:Driver DeleteFiles="no" ForceInstall="no" Sequence="10"
Legacy="yes" PlugAndPlayPrompt="no"/>
<File Id="DriverINF" Source="..\..\MyDeviceProject\" Name="MyDevice.inf"
Vital="yes" KeyPath="yes" DiskId="1" />
<File Id="DriverSYS" Source="..\..\MyDeviceProject\i386\Free\" Name="
MyDevice.sys" Vital="yes" KeyPath="no" DiskId="1" />
</Component>
At this point I'm think perhaps I should drop DIFxApp altogether and use
my own custom action to cram the driver into the system.
Also, it seems that the DIFxApp actions are scheduled to run after
'InstallFiles'.. I would really like to have them run after 'DuplicateFiles'
because I think it would allow me to cut down the size of the installer
slightly. Is that easy to do?
Thanks in advance!
Scott
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
