> -----Original Message----- > From: Branko Horvat [mailto:branko_hor...@hotmail.com] > Sent: Thursday, September 13, 2012 12:57 > To: wix-users@lists.sourceforge.net > Subject: Re: [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' />
Actually I reviewed your original message. You're forgetting to link in the difxapp_x??.wixlib libraries which are in your WiX bin directory. These are required for the correct DIFxApp binaries and table to be linked into your installer package. > > > > >> <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!!! It should be very rare that you actually need to use RemoveFolder. > >> <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. Actually you have to copy the entire driver hierarchy. Have you not reviewed the INF files? Your driver installation will fail if you don't include all files referred to by the INF files, which includes more than just the SYS file. At the very least, your driver will appear unsigned and then fail to install and/or show unsigned driver pop-ups because the signature requires all files in the catalog to be present. Anyone can copy some random files, but if you want to actually *install* the driver, you need the complete driver - not just pieces of it. ------------------------------------------------------------------------------ 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
