Re: [WiX-users] wix ftdi drivers
James, Mission completed!!! At least at this issue. Thx for the difx:Driver displacement tip. After that, from the log it was obvious there were missing files in missing amd64 directory. I looked into both .inf files and provided the 64bit directories (for both .inf files) and :-) the installer could successfully install the ftdi drivers. I am still a little bit confused, why the installer put the directories under C:\Program Files (x86) as it obviously demands x64 versions of files. But I'm fully satisfied with that so far. No, I can focus on finer stuff around WiX. I think I will even help with localization with Slovenian version of installer. James, thanks a lot for great help! Best regards, Branko P.S. For those who also need to install ftdi drivers on windows on your own (for instance you don't have Internet on the computer), via WiX ver. 3.6 I provide my experience bellow: I'm using such candle command: candle.exe -ext WixDifxAppExtension ftdiinstall.wsx Since my xml source of the wix is ftdiinstall.wsx (provided bellow). WixDifxAppExtension is extension, of course. Have a look also of the xml namespace int the root tag of the xml to reference on the difx: ... preffixed tags as difx:Driver ... in my case. This command produces ftdiinstall.wixobj. Then I use the folllowing light.exe command: light.exe -ext WixDifxAppExtension difxapp_x64.wixlib ftdiinstall.wixobj -out ftdiinstall.msi ftdiinstall.wixobj is produces by candle.exe and the output is ftdiinstall.msi (it may be optional). You may need to include difxapp_x86 instead when you have 32-bit architecture of the computer. Since I didn't get explicit result reply if installation was successful or not, I had to check it (check the expected directories with copied driver files, check Add/remove apps under control panel if it was selected to be included there (difx:Driver ... attributes), or just unplug the network cable and uninstall the drivers (via Device Manager - right click uninstall and checkbox on delete files; then use your installer and replug the device via USB). The finer way to check if something went wrong is using logging with installing (in this case you don't doubleclick the ftdiinstall.msi in my case but): msiexec /i ftdiinstall.msi /L* LogFile.txt /i means install (/x would mean uninstall) /L* means create full logging into LogFile.txt. I must emphasize I had all the needed files in the same directory as the installer files. Otherwise you would need the -b path for light.exe. And my ftdiinstall.wsx (wix source file) is as follows: ?xml version='1.0' encoding='windows-1252'? Wix xmlns='http://schemas.microsoft.com/wix/2006/wi' xmlns:difx='http://schemas.microsoft.com/wix/DifxAppExtension' Product Name='FTDI Drivers Installer' Id='E00E5A99-913D-4C68-98BF-B43A471CD45D' Language='1033' Codepage='1252' Version='1.0' Manufacturer='Pieps GmbH' UpgradeCode='6179804D-2231-47D0-B569-B9E04B5C0712' Package Id='*' Keywords='install deploy ftdi driver' Description='FTDI Driver Installer' Comments='Installs FTDI drivers' Manufacturer='Pieps GmbH' InstallerVersion='100' Languages='1033' Compressed='yes' SummaryCodepage='1252' InstallScope='perMachine' / Media Id='1' Cabinet='FTDIInstall.cab' EmbedCab='yes' DiskPrompt='FTDI Driver Media' / Property Id='DiskPrompt' Value='FTDI Driver Install Media' / Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Directory Id='CompanyDir' Name='Pieps' Directory Id='INSTALLDIR' Name='FtdiDrivers' Directory Id='FtdiBusDriverDir' Name='FtdiBusDriver' Component Id='FtdiBusDriverComp' Guid='C96288D7-0C58-44DB-85A6-F6E2B102BFCB' difx:Driver Sequence='1' AddRemovePrograms='yes' Legacy='no' PlugAndPlayPrompt='no' ForceInstall='no' / File Id='FtdiBusINF' Source='.\ftdibus.inf' Vital='yes' / File Id='FtdiBusCAT' Source='.\ftdibus.cat' / File Id='BusFtd2xx' Source='.\ftd2xx.h' / /Component Directory Id='Bus32' Name='i386' Component Id='BusArch32Comp' Guid='5BE845A4-9787-4218-B578-22878B31231B' File Id='FtdiBusSYS' Source='.\i386\ftdibus.sys' Vital='yes' / File Id='FtBusUiDLL' Source='.\i386\ftbusui.dll' / File Id='Ftd2xxDLL' Source='.\i386\ftd2xx.dll' / File Id='FtLangDLL' Source='.\i386\FTLang.Dll' /
Re: [WiX-users] wix ftdi drivers
James,
I realised the RemoveFolder tags are necesary because I am installint into
userprofile,
not for all users on a computer as I hope it want ask admin permission to
install.
If I remove difx:Driver tag then I can reproduce the file hierarchy - actually
not as originally is,
since there are two .inf in the same directory. And, as I read somewhere, each
driver must be
int seperate directory for wix (and thus also in a seperate component). I
solved it that way
that both created directories contain it's own subdirectory with x86 files
(originally it was common).
I took a look of all needed files in both inf. files.
So the bottom line is I can manage to procuse file hierarchy as I wish (as I
suppose is expected).
When I uncomment difx:Driver tags the same errors as till now:
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(33) : error LGHT0094 : Unresolved ref
erence to symbol 'CustomAction:MsiProcessDrivers' in section 'Product:{E00E5A99-
913D-4C68-98BF-B43A471CD45D}'.
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(53) : error LGHT0094 : Unresolved ref
erence to symbol 'CustomAction:MsiProcessDrivers' in section 'Product:{E00E5A99-
913D-4C68-98BF-B43A471CD45D}'.
This is when I use: light.exe -ext WixDifxAppExtension ftdiinstall.wixobj
When I use:
C:\Users\hob\Documents\WiXlight.exe -ext WixDifxAppExtension
-ext D:\tmp\ftdi\difxapp_x86.wixlib ftdiinstall.wixobj
(you see I even tried with absolute path)
it says:
light.exe : error LGHT0144 : The extension 'D:\tmp\ftdi\difxapp_x86.wixlib'
could not be loaded because of the following reason:
Could not load file or assembly 'file:///D:\tmp\ftdi\difxapp_x86.wixlib'
or one of its dependencies.
The module was expected to contain an assembly manifest.
This makes me think this is for .net environment.
--
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix ftdi drivers
A .wixlib is not a WixExtension so you cannot use the -ext switch.
On Fri, Sep 14, 2012 at 5:55 AM, Branko Horvat branko_hor...@hotmail.comwrote:
James,
I realised the RemoveFolder tags are necesary because I am installint into
userprofile,
not for all users on a computer as I hope it want ask admin permission to
install.
If I remove difx:Driver tag then I can reproduce the file hierarchy -
actually not as originally is,
since there are two .inf in the same directory. And, as I read somewhere,
each driver must be
int seperate directory for wix (and thus also in a seperate component). I
solved it that way
that both created directories contain it's own subdirectory with x86 files
(originally it was common).
I took a look of all needed files in both inf. files.
So the bottom line is I can manage to procuse file hierarchy as I wish (as
I suppose is expected).
When I uncomment difx:Driver tags the same errors as till now:
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(33) : error LGHT0094 :
Unresolved ref
erence to symbol 'CustomAction:MsiProcessDrivers' in section
'Product:{E00E5A99-
913D-4C68-98BF-B43A471CD45D}'.
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(53) : error LGHT0094 :
Unresolved ref
erence to symbol 'CustomAction:MsiProcessDrivers' in section
'Product:{E00E5A99-
913D-4C68-98BF-B43A471CD45D}'.
This is when I use: light.exe -ext WixDifxAppExtension ftdiinstall.wixobj
When I use:
C:\Users\hob\Documents\WiXlight.exe -ext WixDifxAppExtension
-ext D:\tmp\ftdi\difxapp_x86.wixlib ftdiinstall.wixobj
(you see I even tried with absolute path)
it says:
light.exe : error LGHT0144 : The extension 'D:\tmp\ftdi\difxapp_x86.wixlib'
could not be loaded because of the following reason:
Could not load file or assembly 'file:///D:\tmp\ftdi\difxapp_x86.wixlib'
or one of its dependencies.
The module was expected to contain an assembly manifest.
This makes me think this is for .net environment.
--
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
virtually,
Rob Mensching
http://RobMensching.com LLC
--
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix ftdi drivers
On 14-Sep-12 08:55, Branko Horvat wrote: I realised the RemoveFolder tags are necesary because I am installint into userprofile, not for all users on a computer as I hope it want ask admin permission to install. Admin privileges are required to install drivers. When I use: C:\Users\hob\Documents\WiXlight.exe -ext WixDifxAppExtension -ext D:\tmp\ftdi\difxapp_x86.wixlib ftdiinstall.wixobj Don't add -ext for difxapp_x86.wixlib. -- sig://boB http://joyofsetup.com/ -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix ftdi drivers
James,
I realised the RemoveFolder tags are necesary because I am installint into
userprofile, not for all users on a computer as I hope it want ask admin
permission to install.
1. Drivers run in kernel mode and have complete control over everything on
the computer at the lowest level. How would you expect to install such a
potentially-dangerous piece of software without being administrator?
There is no such thing as a per-user driver install. There is no such
thing as non-administrators installing a driver. Any such thing would be a
pretty serious breach of security in any operating system - not just
Windows.
You'd best set up your Windows installer package to install as per-machine,
and not per-user. I don't see how a per-user installer that loads a driver
would make any sense at all, or have a happy ending. Ours installs as
per-machine and I've had zero complaints about it.
2. Why would you need RemoveFolder tags just for a per-user install?
Again, this makes no sense and you shouldn't need them even on a per-user
installation.
If I remove difx:Driver tag then I can reproduce the file hierarchy -
actually
not as originally is, since there are two .inf in the same directory. And,
as I
read somewhere, each driver must be int seperate directory for wix (and
thus also in a seperate component). I solved it that way that both created
directories contain it's own subdirectory with x86 files (originally it
was
common).
I took a look of all needed files in both inf. files.
Correct, difx:Driver can handle only one INF at a time in a directory. You
have to install into two separate directories.
So the bottom line is I can manage to procuse file hierarchy as I wish (as
I
suppose is expected).
When I uncomment difx:Driver tags the same errors as till now:
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(33) : error LGHT0094 :
Unresolved ref erence to symbol 'CustomAction:MsiProcessDrivers' in
section 'Product:{E00E5A99- 913D-4C68-98BF-B43A471CD45D}'.
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(53) : error LGHT0094 :
Unresolved ref erence to symbol 'CustomAction:MsiProcessDrivers' in
section 'Product:{E00E5A99- 913D-4C68-98BF-B43A471CD45D}'.
This is when I use: light.exe -ext WixDifxAppExtension ftdiinstall.wixobj
When I use:
C:\Users\hob\Documents\WiXlight.exe -ext WixDifxAppExtension -ext
D:\tmp\ftdi\difxapp_x86.wixlib ftdiinstall.wixobj
(you see I even tried with absolute path) it says:
light.exe : error LGHT0144 : The extension
'D:\tmp\ftdi\difxapp_x86.wixlib'
could not be loaded because of the following reason:
Could not load file or assembly 'file:///D:\tmp\ftdi\difxapp_x86.wixlib'
or one of its dependencies.
The module was expected to contain an assembly manifest.
This makes me think this is for .net environment.
Well, yeah. You specified that difxapp_x86.wixlib was a WiX extension. WiX
extensions are managed .NET assemblies. So it's no surprise you ran into
this error. Look at the light syntax for properly linking in a wixlib file.
Wixlib files are NOT WiX extensions, they are very different.
--
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix ftdi drivers
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
Re: [WiX-users] wix ftdi drivers
-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
[WiX-users] wix ftdi drivers
Hello,
I would
like to install two ftdi (VCP: USB to COM) drivers with WiX, among others app
stuff. I have the last WiX, i.e. v3.6. I’m bugging with it for quite some days.
I’ve read quite a lot of stuff about WiX and about drivers installation. I
haven’t checked both .inf files with ChkINF yet, but I suppose they are fine
since we use it already. I haven’t used explicit CustomAction as I saw in some
suggestions as It looks like old stuff. Well I’m using plain .wsx with
Notepad++ and command prompt candle.exe and light.exe in Win 7. I know
both drivers has to be in separate WiX components. I used difx:Driver tag as
you can see below. I have a ref in xmlns to the Difxapp extension. I used the
switches –ext in candle and light as I guessed. Maybe I’m following the wrong
path. Please, help. But as with that switch the candle compiler produce no
errors, I assume it is all right. Please, direct me to some driver installation
(two drivers even!) with WiX 3.6.
The
following is ok:
candle.exe
-ext WixDifxappExtension ftdiinstall.wsx
But after
this, I get errors:
light -ext
WixDifxappExtension ftdiinstall.wixobj
Namely:
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(29)
: error LGHT0094 : Unresolved ref
erence to
symbol 'CustomAction:MsiProcessDrivers' in section 'Product:{E00E5A99-
913D-4C68-98BF-B43A471CD45D}'.
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(42)
: error LGHT0094 : Unresolved ref
erence to
symbol 'CustomAction:MsiProcessDrivers' in section 'Product:{E00E5A99-
913D-4C68-98BF-B43A471CD45D}'.
My wsx is:
?xml
version='1.0' encoding='windows-1252'?
Wix
xmlns='http://schemas.microsoft.com/wix/2006/wi'
xmlns:difx='http://schemas.microsoft.com/wix/DifxAppExtension'
Product Name='FTDI Drivers Installer'
Id='E00E5A99-913D-4C68-98BF-B43A471CD45D' Language='1033' Codepage='1252'
Version='1.0' Manufacturer='Pieps GmbH'
UpgradeCode='6179804D-2231-47D0-B569-B9E04B5C0712'
Package Id='*' Keywords='install deploy ftdi driver' Description='FTDI
Driver Installer' Comments='Installs FTDI drivers'
Manufacturer='Pieps GmbH' InstallerVersion='100' Languages='1033'
Compressed='yes' SummaryCodepage='1252' /
Media Id='1' Cabinet='FTDIInstall.cab' EmbedCab='yes' DiskPrompt='FTDI
Driver Media' /
Property Id='DiskPrompt' Value='FTDI Driver Install Media' /
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='AppDataFolder'
Directory Id='CompanyDir' Name='Pieps'
Component Id='CompanyDirCom' Guid='A97A6647-E36F-4C9B-AFA1-EA65D51D0C08'
RemoveFolder Id='RemoveCompanyDir' On='uninstall' /
RegistryValue Root='HKCU' Key='SOFTWARE/Pieps' Name='Uninstall'
Type='string' Value='1.0.14.0' KeyPath='yes' /
/Component
Directory Id='INSTALLDIR' Name='FtdiDrivers'
Component Id='DriversDirComp'
Guid='0CC61F38-0C9B-4D15-B89A-29DC27DF44FD'
RemoveFolder Id='RemoveFtdiDrivers' On='uninstall' /
RegistryValue Root='HKCU' Key='SOFTWARE/Pieps' Name='Uninstall'
Type='string' Value='1.0.14.0' KeyPath='yes' /
/Component
Directory Id='FtdiBusDriverDir' Name='FtdiBusDriver'
Component Id='FtdiBusDriver' Guid='C96288D7-0C58-44DB-85A6-F6E2B102BFCB'
RemoveFolder Id='RemoveBusDriverDir' On='uninstall' /
RegistryKey Root='HKCU' Key='SOFTWARE\FtdiBusDriver\Uninstall'
Re: [WiX-users] wix ftdi drivers
Some comments below; they may not fix your problem, but point to other issues in the WXS: -Original Message- From: Branko Horvat [mailto:branko_hor...@hotmail.com] Sent: Wednesday, September 12, 2012 09:27 To: wix-users@lists.sourceforge.net 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? 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. 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. 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. -- 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
Re: [WiX-users] Wix and Drivers
After checking all what I can get it seems I have to use custom action now to proceed. Is that a correct assumption? So is the order then: 1) install the driver files in the Driver Store 2) calling a custom action to install the printer? the way to go or do I have overseen something in Wix? Regards Friedrich - 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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix and Drivers
Ok I was able to advance a bit. I know have an installer which installes the file properly in the DriverStore. However I still have to install the printer driver by opening the Add Printer Wizard. The installation after that works smoothless, but how can that be done during installation time? Are there any extra rules to write? Or how can I proceed from here? Regards Friedrich - 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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix and Drivers
Well I'm trying to build a Installer for a printer driver. Now I looked through all the examples, and checked this mailing list also but I'm kind of stuck. The only example I could find about Wix and .inf files was in the Vista WinDDK. But I do not get it neverthelss. I currently have: a .inf file which I can use to install via the Add Printer Wizard. all the files end in there proper places of course. But now comes the point I simply do not get, what are the needed steps to integrate the information from this .inf file into an installer package? Regards Friedrich - 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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix and Drivers
You probably want the DIFxApp framework, which is supported in WiX. Try looking here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/DevInst_d/hh/DevInst_d/difxapp_b5f94034-5f86-4603-869d-bd64df80b946.xml.asp Rob Friedrich Dominicus wrote: Well I'm trying to build a Installer for a printer driver. Now I looked through all the examples, and checked this mailing list also but I'm kind of stuck. The only example I could find about Wix and .inf files was in the Vista WinDDK. But I do not get it neverthelss. I currently have: a .inf file which I can use to install via the Add Printer Wizard. all the files end in there proper places of course. But now comes the point I simply do not get, what are the needed steps to integrate the information from this .inf file into an installer package? Regards Friedrich - 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.phpp=sourceforgeCID=DEVDEV - 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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix and Drivers
Rob Hamflett [EMAIL PROTECTED] writes: You probably want the DIFxApp framework, which is supported in WiX. Try looking here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/DevInst_d/hh/DevInst_d/difxapp_b5f94034-5f86-4603-869d-bd64df80b946.xml.asp thanks I found it also, but as written I do not get the example really. So I asked for a few other things. However I've installed it all have printed it and will see whether it can give me answers to the stuff I do not understand Regards Friedrich - 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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix and Drivers
Friedrich,
The below works for me using Difx:
Component Id=MyDriver.inf Guid={XX----}
DriverForceInstall=no DriverSequence=1 DriverLegacy=yes
DriverAddRemovePrograms=no
File Id=MyDriver.inf Name=MyDriver.inf src=MyDriver.inf
Vital=yes KeyPath=yes /
/Component
Component Id=MyDriver.sys
Guid={XX----}
File Id= MyDriver.sys Name=MyDriver.sys
src=MyDriver.sys Vital=yes KeyPath=yes /
/Component
Component Id=MyDriver.dll
Guid={XX----}
File Id= MyDriver.dll Name= MyDriver.dll src=
MyDriver.dll Vital=yes KeyPath=yes /
/Component
Then you need to include the path to the appropriate DIFxApp.wixlib in
your light and that should work. I'm using an older, 2x version of Wix
but this should be fine with 3.
Thanks,
Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Friedrich
Dominicus
Sent: Thursday, December 14, 2006 7:20 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix and Drivers
Rob Hamflett [EMAIL PROTECTED] writes:
You probably want the DIFxApp framework, which is supported in WiX.
Try looking here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/DevIns
t_d/hh/DevInst_d/difxapp_b5f94034-5f86-4603-869d-bd64df80b946.xml.asp
thanks I found it also, but as written I do not get the example
really. So I asked for a few other things. However I've installed it
all have printed it and will see whether it can give me answers to the
stuff I do not understand
Regards
Friedrich
-
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.phpp=sourceforgeCID=DEVDE
V
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
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.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix and Drivers
Thomas Svare [EMAIL PROTECTED] writes:
Friedrich,
The below works for me using Difx:
Component Id=MyDriver.inf Guid={XX----}
DriverForceInstall=no DriverSequence=1 DriverLegacy=yes
DriverAddRemovePrograms=no
File Id=MyDriver.inf Name=MyDriver.inf src=MyDriver.inf
Vital=yes KeyPath=yes /
/Component
Thanks, I'll try my luck with it. But did I mention that I have
unidrv-based printer here? Now I found two docs 'Printer Installation
in Windows Vista' and 'How to Install Windows Drivers with Software
Applications'
They do not even mention Wix, I have no idea whether that means
1) good (will work with Wix anyway if you just happen to know how ;-)
2) bad (will not work with Wix) ...
Regards
Friedrich
-
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.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix and Drivers
0. Note that there is a bug open on Difx and WiX v3. WiX v2 should work fine
but there is something going wrong that I haven't had a chance to look into for
Difx integration in WiX v3.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Friedrich
Dominicus
Sent: Thursday, December 14, 2006 08:50
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix and Drivers
Thomas Svare [EMAIL PROTECTED] writes:
Friedrich,
The below works for me using Difx:
Component Id=MyDriver.inf Guid={XX----}
DriverForceInstall=no DriverSequence=1 DriverLegacy=yes
DriverAddRemovePrograms=no
File Id=MyDriver.inf Name=MyDriver.inf src=MyDriver.inf
Vital=yes KeyPath=yes /
/Component
Thanks, I'll try my luck with it. But did I mention that I have
unidrv-based printer here? Now I found two docs 'Printer Installation
in Windows Vista' and 'How to Install Windows Drivers with Software
Applications'
They do not even mention Wix, I have no idea whether that means
1) good (will work with Wix anyway if you just happen to know how ;-)
2) bad (will not work with Wix) ...
Regards
Friedrich
-
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.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
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.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
