Prev: virtual adapter driver
Next: Power policy for raw PDO
From: Rafael R. on 26 Feb 2010 12:33
I've been trying to install a Windows 7 Sensor for the past few days. It
appears that DIFx doesn't support the "Sensor" driver type and attempts to
fallback to Plug n' Play, which simply gets my driver into the Driver Store.

What's the deployment strategy for Windows Sensors? Am I stuck writing
low-level SetupAPI code? Is there a timeline for Sensor support?
From: Doron Holan [MSFT] on 26 Feb 2010 13:02
what do the log files say?

--

This posting is provided "AS IS" with no warranties, and confers no rights.


"Rafael R." <RafaelR(a)discussions.microsoft.com> wrote in message
news:635E4C1D-711E-45C2-A488-8B88718D8BE0(a)microsoft.com...
> I've been trying to install a Windows 7 Sensor for the past few days. It
> appears that DIFx doesn't support the "Sensor" driver type and attempts to
> fallback to Plug n' Play, which simply gets my driver into the Driver
> Store.
>
> What's the deployment strategy for Windows Sensors? Am I stuck writing
> low-level SetupAPI code? Is there a timeline for Sensor support?

From: Rafael R. on 26 Feb 2010 20:29
Hi Doron,

Here's what shows up in DPINST.log:

INFO: Installing INF file '<inf>' (Plug and Play).
INFO: Looking for Model Section [Microsoft.NTAMD64]...
INFO: No matching devices found in INF "<inf>" on the Machine.
INFO: No drivers installed. No devices found that match driver(s)
contained in '<inf>'.
INFO: RETURN: DriverPackageInstallW (0xE000020B)
INFO: No matching device was found for '<inf>'. Driver will be installed
when plugged in.
INFO: Created entry in Add or Remove Programs for '<inf>'.

It appears DIFx has an overall lack of CoInstaller support.

/rafael

"Doron Holan [MSFT]" wrote:

> what do the log files say?
>
> --
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Rafael R." <RafaelR(a)discussions.microsoft.com> wrote in message
> news:635E4C1D-711E-45C2-A488-8B88718D8BE0(a)microsoft.com...
> > I've been trying to install a Windows 7 Sensor for the past few days. It
> > appears that DIFx doesn't support the "Sensor" driver type and attempts to
> > fallback to Plug n' Play, which simply gets my driver into the Driver
> > Store.
> >
> > What's the deployment strategy for Windows Sensors? Am I stuck writing
> > low-level SetupAPI code? Is there a timeline for Sensor support?
>
> .
>
From: Doron Holan [MSFT] on 1 Mar 2010 12:48
does your INF has a model section Microsoft.NTAMD64? if not, what model
sections does it have? DIFx has coinstaller support

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.


"Rafael R." <RafaelR(a)discussions.microsoft.com> wrote in message
news:A151A02D-83E8-4335-B937-9E6599286C94(a)microsoft.com...
> Hi Doron,
>
> Here's what shows up in DPINST.log:
>
> INFO: Installing INF file '<inf>' (Plug and Play).
> INFO: Looking for Model Section [Microsoft.NTAMD64]...
> INFO: No matching devices found in INF "<inf>" on the Machine.
> INFO: No drivers installed. No devices found that match driver(s)
> contained in '<inf>'.
> INFO: RETURN: DriverPackageInstallW (0xE000020B)
> INFO: No matching device was found for '<inf>'. Driver will be installed
> when plugged in.
> INFO: Created entry in Add or Remove Programs for '<inf>'.
>
> It appears DIFx has an overall lack of CoInstaller support.
>
> /rafael
>
> "Doron Holan [MSFT]" wrote:
>
>> what do the log files say?
>>
>> --
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "Rafael R." <RafaelR(a)discussions.microsoft.com> wrote in message
>> news:635E4C1D-711E-45C2-A488-8B88718D8BE0(a)microsoft.com...
>> > I've been trying to install a Windows 7 Sensor for the past few days.
>> > It
>> > appears that DIFx doesn't support the "Sensor" driver type and attempts
>> > to
>> > fallback to Plug n' Play, which simply gets my driver into the Driver
>> > Store.
>> >
>> > What's the deployment strategy for Windows Sensors? Am I stuck writing
>> > low-level SetupAPI code? Is there a timeline for Sensor support?
>>
>> .
>>
 | 
Pages: 1
Prev: virtual adapter driver
Next: Power policy for raw PDO