DIFxAPP - Subfolder Query
Hi All,
I have created an MSI to install Dell (Lexmark) 962 MFD drivers using DIFx, with a source folder structure that contains a language subfolder (‘english’). In the DRVSTORE folder created by DIFx custom actions on install of the MSI, the primary folder contains all its files as expected, but the subfolder created called ‘english’ is empty, and ‘file not found’ errors display. Is this a limitation of DIFx? Do all files have to reside in the same folder as the INF?
Any information you'd like to share would be most appreciated.
thx, TenBob.
I have created an MSI to install Dell (Lexmark) 962 MFD drivers using DIFx, with a source folder structure that contains a language subfolder (‘english’). In the DRVSTORE folder created by DIFx custom actions on install of the MSI, the primary folder contains all its files as expected, but the subfolder created called ‘english’ is empty, and ‘file not found’ errors display. Is this a limitation of DIFx? Do all files have to reside in the same folder as the INF?
Any information you'd like to share would be most appreciated.
thx, TenBob.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
kkaminsk
19 years ago
As far as I understand DIFx the INF tells DIFx where to find the files for driver installation. You should only have to tell DIFx where the inf file is located then have the correct file structure with the INF file. Maybe you have found a bug with DIFx, the file structure is not correct or bad inf formatting? Also ensure you are running the latest version 2.0.
Posted by:
TenBob
19 years ago
Thanks for your reply.
The INF file works when using the hardware wizard, so the language files & INF file must work correctly (the INF file looks good to me, but I'm no expert!).
For information, I created my MSI using both Installshield X and the Wise MSI template, and both have the same issue.
I wonder if anyone else has found or can recreate this behaviour? I have searched and found nothing on the web..... Maybe this is one for Microsoft?
TenBob.
The INF file works when using the hardware wizard, so the language files & INF file must work correctly (the INF file looks good to me, but I'm no expert!).
For information, I created my MSI using both Installshield X and the Wise MSI template, and both have the same issue.
I wonder if anyone else has found or can recreate this behaviour? I have searched and found nothing on the web..... Maybe this is one for Microsoft?
TenBob.
Posted by:
kkaminsk
19 years ago
I would strongly urge you to check which version of DIFx is in the template. I was looking a few weeks ago a Wise's and it still was not at version 2.0. Still if the INF works fine without DIFx then you would hope DIFx could find the drivers. I would definately make sure you are running the newest version because I found 1.0 to either be hit or miss with drivers. Also though it should not make a difference you could try running a GUI app called DPInst.exe. If DPInst.exe can do it then DIFx definately should do it. DPInst.exe will help take the MSI out of the picture.
Posted by:
TenBob
19 years ago
ORIGINAL: kkaminsk
I would strongly urge you to check which version of DIFx is in the template. I was looking a few weeks ago a Wise's and it still was not at version 2.0. Still if the INF works fine without DIFx then you would hope DIFx could find the drivers. I would definately make sure you are running the newest version because I found 1.0 to either be hit or miss with drivers. Also though it should not make a difference you could try running a GUI app called DPInst.exe. If DPInst.exe can do it then DIFx definately should do it. DPInst.exe will help take the MSI out of the picture.
I checked the version in the Wise MSI & InstallShield X, and they are both version 1.0
I have just downloaded version 2 of the tools and re-authored my MSI. Guess what? IT WORKS!!![:D]
Thanks for your help!
TenBob
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.