Prev: Raw PDO shows up as unspecified device in Windows 7
Next: Logitech Wingman Force 3D
From: Don Burn on 12 Jun 2010 16:55
And have you tested this works? AFAIK this is another doc error in MSDN.


Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr



> -----Original Message-----
> From: kalbun [mailto:kalbun(a)discussions.microsoft.com]
> Posted At: Saturday, June 12, 2010 4:44 PM
> Posted To: microsoft.public.development.device.drivers
> Conversation: Right Click Install on Windows 7 64 Bit
> Subject: Re: Right Click Install on Windows 7 64 Bit
>
> What you are saying does not seem completely correct.
> For non-signed drivers you can add the [DefaultInstall] section that
> allows
> you to install from right-click.
> Here is what MSDN says
> (http://www.microsoft.com/communities/newsgroups/en-
> us/default.aspx?dg=microsoft.public.development.device.drivers&tid=7fda430e-
> 6cca-435f-8e03-397b3ec84026&cat=en_US_f21c06d1-a77b-4ccf-be60-
> a4f0a7801247&lang=en&cr=US&sloc=&p=1&mid=baafd8ac-857a-4f35-a50e-25f4df97c264)
>
> "Providing a DefaultInstall section is optional. If an INF file does not
> include a DDInstall section, selecting "Install" after right-clicking on
> the
> file name causes an error message to be displayed."
>
> On the other hand, it seems that if the driver package is signed you are
> obliged NOT to have the DefaultInstall section.
>
> G.
>
> "Doron Holan [MSFT]" wrote:
>
> > you cannot right click install a pnp driver
> >
> > d
>
>
> __________ Information from ESET Smart Security, version of virus
> signature
> database 5192 (20100612) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>

From: Tim Roberts on 13 Jun 2010 22:14
kalbun <kalbun(a)discussions.microsoft.com> wrote:
>
>What you are saying does not seem completely correct.

No, Don is right.

>For non-signed drivers you can add the [DefaultInstall] section that allows
>you to install from right-click.

Well, I think you have cause and effect backwards.

The [DefaultInstall] thing is nothing more than a poor man's software
installer. It lets you copy files and make registry entries, explicitly.
It does not create a device node, and it has nothing to do with
plug-and-play. So, a [DefaultInstall]-based INF cannot be submitted to
WHQL. A plug-and-play INF must have a DDInstall section that matches a
plug-and-play ID, not [DefaultInstall].

>"Providing a DefaultInstall section is optional. If an INF file does not
>include a DDInstall section, selecting "Install" after right-clicking on the
>file name causes an error message to be displayed."

That should say "DefaultInstall", not "DDInstall".

>On the other hand, it seems that if the driver package is signed you are
>obliged NOT to have the DefaultInstall section.

Sort of. An INF with [DefaultInstall] is not PnP.
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
First  |  Prev  | 
Pages: 1 2
Prev: Raw PDO shows up as unspecified device in Windows 7
Next: Logitech Wingman Force 3D