Debugging Driver Install (INF)

Andy Neillans

Hi all,

I believe that XP / Vista both don't like my inf (which I had thought that I
had decorated correctly).
Microsoft's ChkInf doesn't show a problem up either, however both OS's fail
to install...

So ... my question is: Is there any way to put the driver installation / Add
New Hardware wizard into a Debug mode where I can find out exactly what is
going on?

Regards,

Andy Neillans

ajay

On Jun 26, 4:46 pm, "Andy Neillans" <a...@neillans.co.uk> wrote:
> Hi all,
>
> I believe that XP / Vista both don't like my inf (which I had thought that I
> had decorated correctly).
> Microsoft's ChkInf doesn't show a problem up either, however both OS's fail
> to install...
>
> So ... my question is: Is there any way to put the driver installation / Add
> New Hardware wizard into a Debug mode where I can find out exactly what is
> going on?
>
> Regards,
>
> Andy Neillans


Hi Andy,

U can see "windows\setupapi.log" and "windows\inf\setupapi.dev.log"
files. These files are created by Windows it self while installing any
driver. "setupapi.dev.log" file can only be found in Vista.

Regards,
Ajay

Don Burn

First, does ChkInf show any warnings? I find that warnings from ChkInf can
be as fatal as errors.
If this does not work, enable the SetupApi logging (search the WDK there is
a lot of data on this), to see what is failing.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

"Andy Neillans" <andy@neillans.co.uk> wrote in message
news:E4F05561-7889-49A8-9F3E-63C428E74CF1@microsoft.com...
> Hi all,
>
> I believe that XP / Vista both don't like my inf (which I had thought
> that I had decorated correctly).
> Microsoft's ChkInf doesn't show a problem up either, however both OS's
> fail to install...
>
> So ... my question is: Is there any way to put the driver installation /
> Add New Hardware wizard into a Debug mode where I can find out exactly
> what is going on?
>
> Regards,
>
> Andy Neillans

Andy Neillans

Hi Don,

Well, there are the following warnings, but I don't believe them to be an
issue - maybe I'm wrong.

Line 77: (W22.1.2083) Section [BBCAP.SERVICES.NTX86] not referenced
Line 80: (W22.1.2083) Section [BBCAP.SERVICES.NTAMD64] not referenced
Line 83: (W22.1.2083) Section [BBCAP_SERVICE_INST] not referenced
Line 93: (W22.1.2083) Section [BBCAP_EVENTLOG_ADDREG] not referenced
Line 97: (W22.1.2083) Section [BBCAP_SERVICE_INST64] not referenced
Line 104: (W22.1.2083) Section [BBCAP_EVENTLOG_INST] not referenced
Line 107: (W22.1.2083) Section [BBCAP_EVENTLOG_ADDREG64] not referenced
Line 117: (W22.1.2083) Section [BBCAP.SOFTWARESETTINGS] not referenced
Line 120: (W22.1.2083) Section [BBCAP_SOFTWAREDEVICESETTINGS] not referenced
Line 132: (W22.1.2083) Section [BBCAP.GENERALCONFIGDATA] not referenced

I've based my inf on the Mirror driver sample inf in the DDK, but decorated
it for x64 support too.

Digging into the setupapi.dev.log on vista, shows some more puzzling errors:
Installing a NULL driver!
A NULL driver installation is not allowed for this type of device!
Cleaning up failed installation (e0000219)
Error 0xe0000219: The installation failed because a function driver was not
specified for this device instance.


Regards,

Andy Neillans

"Don Burn" <burn@stopspam.windrvr.com> wrote in message
news:eGSKuu%23tHHA.292@TK2MSFTNGP02.phx.gbl...
> First, does ChkInf show any warnings? I find that warnings from ChkInf
> can be as fatal as errors.
> If this does not work, enable the SetupApi logging (search the WDK there
> is a lot of data on this), to see what is failing.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>
> "Andy Neillans" <andy@neillans.co.uk> wrote in message
> news:E4F05561-7889-49A8-9F3E-63C428E74CF1@microsoft.com...
>> Hi all,
>>
>> I believe that XP / Vista both don't like my inf (which I had thought
>> that I had decorated correctly).
>> Microsoft's ChkInf doesn't show a problem up either, however both OS's
>> fail to install...
>>
>> So ... my question is: Is there any way to put the driver installation /
>> Add New Hardware wizard into a Debug mode where I can find out exactly
>> what is going on?
>>
>> Regards,
>>
>> Andy Neillans
>
>

Don Burn

Well on the not referenced sections should any of those be referenced?
Assuming you took mirror and replaced it with BBCAP then I would think you
would want the BBCAP_SERVICE_INST section since that sets up the service,
and I suspect most of the other sections.

Check your BBCAP.SERVICES section, and see if it should not reference some
of these.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

"Andy Neillans" <andy@neillans.co.uk> wrote in message
news:A1D4AE7D-C915-4CE7-80A5-AEAA3335B6B8@microsoft.com...
> Hi Don,
>
> Well, there are the following warnings, but I don't believe them to be an
> issue - maybe I'm wrong.
>
> Line 77: (W22.1.2083) Section [BBCAP.SERVICES.NTX86] not referenced
> Line 80: (W22.1.2083) Section [BBCAP.SERVICES.NTAMD64] not referenced
> Line 83: (W22.1.2083) Section [BBCAP_SERVICE_INST] not referenced
> Line 93: (W22.1.2083) Section [BBCAP_EVENTLOG_ADDREG] not referenced
> Line 97: (W22.1.2083) Section [BBCAP_SERVICE_INST64] not referenced
> Line 104: (W22.1.2083) Section [BBCAP_EVENTLOG_INST] not referenced
> Line 107: (W22.1.2083) Section [BBCAP_EVENTLOG_ADDREG64] not referenced
> Line 117: (W22.1.2083) Section [BBCAP.SOFTWARESETTINGS] not referenced
> Line 120: (W22.1.2083) Section [BBCAP_SOFTWAREDEVICESETTINGS] not
> referenced
> Line 132: (W22.1.2083) Section [BBCAP.GENERALCONFIGDATA] not referenced
>
> I've based my inf on the Mirror driver sample inf in the DDK, but
> decorated it for x64 support too.
>
> Digging into the setupapi.dev.log on vista, shows some more puzzling
> errors:
> Installing a NULL driver!
> A NULL driver installation is not allowed for this type of device!
> Cleaning up failed installation (e0000219)
> Error 0xe0000219: The installation failed because a function driver was
> not specified for this device instance.
>
>
> Regards,
>
> Andy Neillans
>
> "Don Burn" <burn@stopspam.windrvr.com> wrote in message
> news:eGSKuu%23tHHA.292@TK2MSFTNGP02.phx.gbl...
>> First, does ChkInf show any warnings? I find that warnings from ChkInf
>> can be as fatal as errors.
>> If this does not work, enable the SetupApi logging (search the WDK there
>> is a lot of data on this), to see what is failing.
>>
>>
>> --
>> Don Burn (MVP, Windows DDK)
>> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>> Website: http://www.windrvr.com
>> Blog: http://msmvps.com/blogs/WinDrvr
>> Remove StopSpam to reply
>>
>> "Andy Neillans" <andy@neillans.co.uk> wrote in message
>> news:E4F05561-7889-49A8-9F3E-63C428E74CF1@microsoft.com...
>>> Hi all,
>>>
>>> I believe that XP / Vista both don't like my inf (which I had thought
>>> that I had decorated correctly).
>>> Microsoft's ChkInf doesn't show a problem up either, however both OS's
>>> fail to install...
>>>
>>> So ... my question is: Is there any way to put the driver installation
>>> / Add New Hardware wizard into a Debug mode where I can find out
>>> exactly what is going on?
>>>
>>> Regards,
>>>
>>> Andy Neillans
>>
>>
>