Apple Footer This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.

GEARDIFx.exe is part of DIFx Driver Installer and developed by GEAR Software, Inc. According to the GEARDIFx.exe version information. GEARDIFx.exe is usually located in the 'C: ProgramData 34BE82C4-E596-4e99-A1EBF69 ' folder. None of the anti-virus. Based on votes from 310 users.

Just been messing around with (Difx) to install device drivers onto Win XP boxes and found some annoying bugs (features?) on another wise great utility. I'm trying to quietly install drivers which are not signed by MS WHQL. To get them to install at all I've used authenticode to create a root certificate and a publishers certificate. I've signed the drivers with the trusted publisher certificate and now they will install fine with DPinst.exe and DifxApp (.msi). The problem is quiet installs with DifxApp. It fails completely on a /qn and on a /qb software first install it is not quiet and prompts for the user to plug in the device. Serial Xcad 2008 Professional.

However on a hardware first install the /qb switch works fine, without prompts. (Besides standard OS prompts for the hardware of course.) The DifxApp documentation says quiet installs work fine, without caveat. DIFxApp supports the silent installation of an MSI installation package. A silent installation does not display dialog boxes or messages to the user. The readme.txt however says authenticode signed drivers will fail always on Windows 2000 and WinXP because of the OS having to prompt. 1950 Minghi Torrent. An authenticode-signed, Plug and Play driver cannot be installed silently on Windows XP and Windows 2000.

This is due to the fact that both Windows XP and Windows 2000 do not recognize authenticode-signed drivers, as a result of which they will always attempt to display the unsigned driver dialog. But in silent mode, since they are not allowed to display any UI, the install will fail silently. Now I've seen it work silently with /qb so the failure isn't because of the OS and I'm a little concerned that MS have not seen that and actually moved this out of beta. I've gotten around the prompt using an AutoIt script so I can have installs without interaction. Another gripe is the automatically putting another entry in the ARP list.

Nice feature but some companies might not want it. (It may also cause problems with Managesoft which takes over the Add/Remove list).

A option to turn this on or off would be better. Fortunately there is an option to implement this with the Flags column. Otherwise I have found this to be a great utility to get WHQL signed drivers out there onto the users PCs. Cheers, Jeff Endres. Hi Guys, Finally made some progress with DiFxApp tools. But I am still not able to install my driver: I am getting following error in my installation log files: DIFXAPP: ERROR more than one driver package found in C: WINDOWS inf Has anyone experienced this error before.

I followed following steps: 1) Created the driver Installer database (Installshield Repackager as the original driver set up is not MSI) 2) Applied DiFxApp.msm to the Installer Database 3) Added the Component (which contains the INF file ) to the component table 4) Added Flag value in the component table to 8 for Legacy install (unsigned driver) 5) Saved the new merged MSI 6) Installed the driver Package with msiexec options for verbose logging As I am trying this for the first time, I might be having a completely wrong understanding. Kindly suggest. ORIGINAL: viv_bhatt1 Hi Guys, Finally made some progress with DiFxApp tools. But I am still not able to install my driver: I am getting following error in my installation log files: DIFXAPP: ERROR more than one driver package found in C: WINDOWS inf Has anyone experienced this error before. I followed following steps: 1) Created the driver Installer database (Installshield Repackager as the original driver set up is not MSI) 2) Applied DiFxApp.msm to the Installer Database 3) Added the Component (which contains the INF file ) to the component table 4) Added Flag value in the component table to 8 for Legacy install (unsigned driver) 5) Saved the new merged MSI 6) Installed the driver Package with msiexec options for verbose logging As I am trying this for the first time, I might be having a completely wrong understanding. Kindly suggest. Cheers, V Where are you delivering your source driver files to that you have set to install via DIFxAPP?

I used DIFxAPP 2 to sucessfully deploy an unsigned driver (using the flag value 8 - even though Wise PS5.6 saw this as a table error). I'm assuming you've set your MSI to copy your inf file to c: windows inf. The DifXApp documentation states that each 'driver package' needs to have it's own unique folder (MS recommend c: program files company title driver package), hence the 'more than one driver package found' message. I think I remember mention of unpredictable results if Difxapp finds more than one inf in the source folder. Difxapp will copy the inf file to c: windows inf when it doesn't find it there, and will also deal with installation of the drivers.

Just a follow up regarding DifX v2.0. Nice to see some of the features i had gripes with being resolved with the new version. However the core issue has not been addressed. That is silent installs of unsigned drivers in an enterprise environment. I have tried Difx to install a driver signed by a trusted authority (me) and with the bit16 flag set. The driver will install on /qb and /qn but with a prompt. (/q is supposed to be quiet!) This also causes the machine to hang if installed via Group Policy.

MS has put this down to a OS issue that will be resolved with Longhorn, (twiddle my thumbs while i wait for that?) but it is possible to install silently with a modified version of DifxApp. This shows that the WHQL check is built into the DifxApp. I can understand the concern of allowing installation of unsigned drivers in general, but if a driver has been signed by an appropriate authority (Root or Trusted Publisher) it should not be a requirement for the user to click a button to have the application installed. Well this particular driver has been pushed back to the manufacturer and we will see how we go. -- Regards, Jeff. I have found many versions of DIFx.msm and DIfx.dll and unable to decide which version to use.

Can you tell me which version to use, i want to register legacy drivers for windows 2000. I am using the following method to add legacy drivers to my installation msi which i got from this site itself: 1) Locate the.INF file which the legacy installation uses to install the drivers. Inspect this file in notepad and work out all the files that the driver requires to be installed. This could be as little as a.SYS file, a.CAT file (assuming the driver is signed) and of course the.INF file itself. There may, however be more files (such as DLL's) that are mentioned in the.INF - the key thing here is to get a full list of the files the driver needs. 2) In the MSI package you are developing, create a separate folder named (say) DriverFilesFolder and locate this as a subfolder of the main application folder (e.g.

C: Program Files Dymo DriverFilesFolder). 3) Next create a new component named (say) DriverFiles.

Move all the files that you listed from step 1) above into this component and set one of them as the keypath for the component - I usually mark the.SYS file as the keypath. The destination of this component should be the folder you created at step 2) 4) Next include the DIFx 2.0 Merge Module into your MSI package - it's named DIFxApp.msm 5) Incorporating this merge module will, among other things, have introduced a new table into your package, named MsiDriverPackages, you will need to edit this table directly (e.g. Use Direct Editor in InstallShield, or use ORCA). In the Component column, you need to enter the name of the component you created in step 3) above.

If the drivers are signed (i.e. You have a.CAT file) then you can set the Flags column to 0, otherwise you could use 8 for 'legacy mode', more of which later. The Sequence column can be left blank - it's only used if you are installing several separate drivers and want to control the order they are installed in. 6) That should be all that is needed for DIFx to 'do it's thing'. You should now go through the rest of your snapshot package removing anything else that is driver-related this would include. (i) any other instances of the.INF file, typically being deployed to the INF folder (ii) any other instances of the.SYS file, typically being deployed to the System32 Drivers folder. (iii) any other instances of files you listed in step 1) other than those you have put into your new component.

(iv) any.PNF files that your capture picked up (v) anything in the registry under HKLM SYSTEM CurrentControlSet Enum Root or HKLM SYSTEM CurrentControlSet Enum USB A final word on legacy mode for DIFx 2.0. I think if your drivers are unsigned, then when a non-admin user plugs the device in for the first time, you will still get a prompt for administrator credentials - but the rest of the installation should require no further interaction if you have managed to get all the above working.

With signed drivers, this isn't an issue. You should be using 2.01 and that can be found here. As for #3 I thought you would want to set the.inf as the key path. (it has been a while since I've done this) If your driver has multiple inf files that must be installed in order you might have to make multiple components in multiple directories so that you can sequence the driver installations. Maybe they fixed this but the last time I tried that only DPINST would install multiple drivers.

ORIGINAL: karan_gupta I am trying to include DIFXApp.msm into the package and getting MSIdriverpackages as a new table but when i try to install it gives an error saying that package needs a Dll to complete the installation. Is there any dll i have to include also or just the merge module in my package Hello, It does sound like you may have overlooked one of the DLL files that the driver itself needs. Have you checked through the.INF file(s) using an editor to see if any DLL files are referenced in there which you may have not (yet) included in the component used for the.SYS and.INF files? Regards, Spartacus.