Thanks for the response.
No I must install it using the Add new hardware wizard, or using the install
program that we wrote.
I tried setupapi InstallHinfSection already but it didn't work. According to
fba.log there was no error, but driver was not visible in device manager.
In mean time I have solved problem using the brute force, I don't think that
it is the way it should be used though but it will work for me.
I have made the component that populate directly Enum, Class and Services
keys in registry so there is no need for PNP or installation.
Thanks again,
Slobodan
"Nick" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> Hi There,
>
> Does the driver install successfully if you were to right click on it and
> choose 'Install', if so I imagine you could create an FBA generic command
of
> executable rundll32.exe and parameters of something like
> setupapi.dll,InstallHinfSection DefaultInstall 128 %17%\myinf.inf
>
> So the effective command line you would have is
> C:\windows\system32\rundll32.exe setupapi.dll,InstallHinfSection
> DefaultInstall 128 C:\windows\inf\myinf.inf
>
> Notes
> It is important that there is no white space between
> setupapi,InstallHinfSection
> DefaultInstall can be as is or you can specify a specific section in your
> inf file (say if your inf file specifed a number of drivers and you only
> wanted one config)
> 128 is the defailt 'mode', the value of 'mode' can be 0 (reserved for the
> system) or 128 +0 to +4 i.e. a maximum of 132, this determines how setup
> should decide to perform a reboot, so you may want to leave at 128 since
you
> can specify a reboot in your component
> the %17% in the command line is true if you have already put your inf file
> in the default windows\inf directory otherwise you need to put the correct
> path in it
>
> There is some information in this in the platform SDK, you can look up
> InstallHinfSection and that will give you more information
>
> Hope this helps,
> Nick
>
> "Slobodan Brcin" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I can't make the component using the CD which will force the software
> device
> > driver to be enumerated(installed) during FBA phase.
> > I am able to install the driver manually using the Add Hardware Wizard
so
> > there are no dependency issues.
> >
> > This driver inf is equivalent to wave.inf let us say "Legacy Audio
> Driver".
> > I don't know what should be added to component to make one driver
> instance.
> >
> > If there is any idea, I would appreciate it.
> >
> >
> > Thanks,
> > Slobodan
> >
> >
> >
>
>
|
Similar Threads
