I need to run a batch or a exe from inno setup(something like
installshield) to install drivers for a Pnp usb device with FTD2XX
drivers from FTDI.
Now from a batch i call:
C:\WINDOWS\System32\rundll32.exe setupapi,InstallHinfSection
DefaultInstall 132 .\ftd2xx.inf

and i can successfully see the install dialog appear, all the drivers
files are copyied in the right places, oemxx.ing is created, but when i
plug in the device the same dialog appear and i need to reinstall
drivers again in order to make it work.
I noticed that after the batch, in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\
there is no Vid_0403&Pid_6001 key as expected

So how can i full manually install this device without interaction with
the user?
Hi Andrea

RE: manual install driver for pnp device by pavel_a

pavel_a
Mon Mar 06 08:19:29 CST 2006

"andrea.visinoni@gmail.com" wrote:
> I need to run a batch or a exe from inno setup(something like
> installshield) to install drivers for a Pnp usb device with FTD2XX
> drivers from FTDI.
> Now from a batch i call:
> C:\WINDOWS\System32\rundll32.exe setupapi,InstallHinfSection
> DefaultInstall 132 .\ftd2xx.inf

Wrong way. InstallHinfSection can not install PnP drivers.
(of course unless this FTDI INF launches something else)

> and i can successfully see the install dialog appear, all the drivers
> files are copyied in the right places, oemxx.ing is created, but when i
> plug in the device the same dialog appear and i need to reinstall
> drivers again in order to make it work.
> I noticed that after the batch, in
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\
> there is no Vid_0403&Pid_6001 key as expected
>
> So how can i full manually install this device without interaction with
> the user?

Use DifX.
Then, if you wish, pack DifX setup with Inno Setup.

--PA


Re: manual install driver for pnp device by Uwe

Uwe
Wed Mar 08 10:44:18 CST 2006

There's a section "Pre-installing Driver Files" in the DDK documentation
under "Device Installation/Design Guide/Writing a Device Installation
Application".

Have a look.


<andrea.visinoni@gmail.com> schrieb im Newsbeitrag
news:1141641985.014568.33920@p10g2000cwp.googlegroups.com...
>I need to run a batch or a exe from inno setup(something like
> installshield) to install drivers for a Pnp usb device with FTD2XX
> drivers from FTDI.
> Now from a batch i call:
> C:\WINDOWS\System32\rundll32.exe setupapi,InstallHinfSection
> DefaultInstall 132 .\ftd2xx.inf
>
> and i can successfully see the install dialog appear, all the drivers
> files are copyied in the right places, oemxx.ing is created, but when i
> plug in the device the same dialog appear and i need to reinstall
> drivers again in order to make it work.
> I noticed that after the batch, in
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\
> there is no Vid_0403&Pid_6001 key as expected
>
> So how can i full manually install this device without interaction with
> the user?
> Hi Andrea
>



Re: manual install driver for pnp device by andrea

andrea
Thu Mar 09 02:18:12 CST 2006

using SetupCopyOEMInf in order to pre-install drivers, has the same
effect of runnign rundll32.exe as i see.

section "Pre-installing Driver Files" said:
"When the user plugs in the device, the PnP Manager recognizes the
device, finds the INF file copied by SetupCopyOEMInf, and installs the
drivers copied in Step 2"

for me (and for this driver) is not really true, when i plug in the
device windows iterate through oemxx.inf and found that my device is
supported by ftd2xx but even if all the driver files are in the right
place he ask me again to install them.
well this driver is not signed, maybe is a problem?
Andrea


Re: manual install driver for pnp device by Pavel

Pavel
Thu Mar 09 16:32:15 CST 2006

<andrea.visinoni@gmail.com> wrote in message news:1141892292.030736.231120@u72g2000cwu.googlegroups.com...
> using SetupCopyOEMInf in order to pre-install drivers, has the same
> effect of runnign rundll32.exe as i see.
>
> section "Pre-installing Driver Files" said:
> "When the user plugs in the device, the PnP Manager recognizes the
> device, finds the INF file copied by SetupCopyOEMInf, and installs the
> drivers copied in Step 2"
>
> for me (and for this driver) is not really true, when i plug in the
> device windows iterate through oemxx.inf and found that my device is
> supported by ftd2xx but even if all the driver files are in the right
> place he ask me again to install them.
> well this driver is not signed, maybe is a problem?
> Andrea

No, unsigned driver causes a different popup ("new device found").
If you get a prompt for missing files, this is because you have not
copied the files to the right place. The INF and system32\drivers folders
actually are NOT a right place to preinstall your files.
Please read DDK documentation.

--PA



Re: manual install driver for pnp device by andrea

andrea
Thu Mar 09 17:55:13 CST 2006

the prompt is not for missing files, it's simply the same as before.
drivers files are placed in the right place because is .inf file that
tell where to put them


Re: manual install driver for pnp device by Pavel

Pavel
Sat Mar 11 15:35:09 CST 2006

<andrea.visinoni@gmail.com> wrote in message news:1141948513.737791.33280@j52g2000cwj.googlegroups.com...
> the prompt is not for missing files, it's simply the same as before.
> drivers files are placed in the right place because is .inf file that
> tell where to put them

Then yes, this can be caused by unsigned driver.
But still your assumption that you can preinstall files in this way in XP is wrong.
Once in win9x days this was correct, but now it is not.

--PA