>Some comments below; they may not fix your problem, but point to other
>issues in the WXS:
Thanx for all your hints!
>
>> -----Original Message-----
>> From: Branko Horvat [mailto:branko_horvat@...]
>> Sent: Wednesday, September 12, 2012 09:27
>> To: wix-users@...
>> Subject: [WiX-users] wix ftdi drivers
>>
>> C:\Users\hob\Documents\WiX\ftdiinstall.wsx(29)
>> C:\Users\hob\Documents\WiX\ftdiinstall.wsx(42)
>
>The WSX you attached got cut off at various points, can you show which lines
>of code were indicated by the faulty lines #29 and #42?
Both difx:Driver tags are referred to:
<difx:Driver Sequence='1' AddRemovePrograms='no' Legacy='yes'
PlugAndPlayPrompt='no' ForceInstall='yes' />
<difx:Driver Sequence='2' AddRemovePrograms='no' Legacy='yes'
PlugAndPlayPrompt='no' ForceInstall='yes' />
>
>> <Component Id='CompanyDirCom' Guid='A97A6647-E36F-4C9B-AFA1-
>> EA65D51D0C08'>
>>
>>
>> <RemoveFolder Id='RemoveCompanyDir' On='uninstall' />
>
>You don't need to have RemoveFolder. This element can be completely
>removed. The directories you create will be removed anyway on uninstall.
>
>This is true for all instances of RemoveFolder in your example code.
>
I didn't have it at the beginning. But compiler (candle.exe) demanded it (maybe
I didn't have components at that time yet). Also the keyValues was demanded at
the same time (it said a keyValue must exist not a file), if I am not mistaken.
So, I've removed it and now it looks fine. Thanx!!!
>> <difx:Driver Sequence='1' AddRemovePrograms='no' Legacy='no'
>> PlugAndPlayPrompt='no' ForceInstall='yes' />
>
>I would suggest changing "ForceInstall" to "no". If you set it to "yes"
>like in your example, you could force downgrading the driver to an older
>version if the user's system had a newer version of the driver installed.
>That may cause compatibility problems with other software and devices
>installed on the customer's computer that also uses an FTDI driver.
>
Ok, I've changed it to 'no'.
>> <File Id='BusDriverSys' Source='i386\ftdibus.sys' />
>> <File Id='BusDriverInf' Source='ftdibus.inf' />
>> <File Id='BusDriverCat' Source='ftdibus.cat' />
>
>You can't install files in a component into multiple directories. You'll
>have to split this into at least two components: one for the i386 directory
>and one for the parent directory containing INF/CAT files. Also, you're
>missing some of the files from the FTDI driver package - your list of files
>is incomplete. Put the difxapp:Driver element in the parent directory
>component containing the INF file.
>
>The same issues apply to the FTDI port section you listed below.
That makes me thinking as well. Thanks! - I just wanted to copy twice all three
files (.inf and .cat from root driver directory and .sys from i386
subdirectory) into the common directory and I achieved it at the beginning my
<file> tags. So, I have to deny your opinion. So when I didn't bother with
installation (using difx:Driver tag, the file copied as I wanted: into
FtdiBusDriver and FtdiPortDriver directores.
But, I certainly think I should copy all the driver hierarchy and leave it as
it is because of .inf files.
I am very grateful for all your suggestions! Namely all above mentioned
mestakes after using light.exe remain!
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
