I have a .inf file and a .sys file and a couple of dll’s. to install the
driver manually i do from elevated command prompt :
devcon install driver.inf HID\driver
I want some pointers on how to make the installer for this driver . Thanks.
Also when i work in windows 7 64bit , i am required to sign the driver
before installing it . How do i distribute the signature in windows and how
will it be verified ?
PS: I am a complete noob when it comes to things related to drivers.
Take a look at Driver Install Frameworks for the how to install the
driver. This has multiple approaches but they are all pretty easy to
use. You will need a signing certificate from one of the vendors that
Microsoft approves, if you have that you don’t need to distribute the
cert, only the signed driver package.
Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“Rajat goyal” wrote in message news:xxxxx@ntdev:
> I have a .inf file and a .sys file and a couple of dll’s. to install the
> driver manually i do from elevated command prompt :
>
> devcon install driver.inf HID\driver
>
> I want some pointers on how to make the installer for this driver . Thanks.
>
> Also when i work in windows 7 64bit , i am required to sign the driver
> before installing it . How do i distribute the signature in windows and how
> will it be verified ?
>
> PS: I am a complete noob when it comes to things related to drivers.
Rajat goyal wrote:
I have a .inf file and a .sys file and a couple of dll’s. to install
the driver manually i do from elevated command prompt :|devcon install driver.inf HID\driver|
No, no, no, no!!! That does NOT do what you think it does. “devcon
install” is an enticing-sounding tool, but it CANNOT be used to install
plug-and-play drivers. What that command does is create a FAKE device
with the ID you specify, then load your driver to handle that fake
device. Your driver will not be talking to real hardware.
Do not install drivers manually. The best way is to use something like
“dpinst” to help do your installation. If necessary, you can use
“devcon update” to replace the drivers with your set, but “devcon
install” will NOT do it.
||
I want some pointers on how to make the installer for this driver .
Thanks.
What I do is use a simple installer based on NSIS that copies the driver
package to the user’s disk, then invokes DPInst (which I also have to
ship in my package) to pre-install the drivers in the driver store,
where plug-and-play can find them.
Also when i work in windows 7 64bit , i am required to sign the driver
before installing it . How do i distribute the signature in windows
and how will it be verified ?
When you sign the driver, your certificate will be embedded in the sys
file. In addition, when you sign it, you have to use a “cross
certificate” (available either from Microsoft or from the certificate
authority) that continues the chain of trust all the way to the
Microsoft Code Verification Authority. The kernel, then, only has to
verify that the trust chain is valid, and that the chain ends with the
Microsoft Code Verification Authority. It doesn’t actually verify your
signature.
This means that you must use a very specific kind of certificate. It
must be a Class 3 Code-Signing Certificate issued by one of the short
list of vendors that has a cross-certificate for kernel driver signing.
VeriSign, GlobalSign, and Thawte qualify, at least. We talked about
GoDaddy last week, but I don’t remember whether the discussion ended up
positive or negative.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
On Thu, May 31, 2012 at 10:33 AM, Tim Roberts wrote:
> Rajat goyal wrote:
> >
> > I have a .inf file and a .sys file and a couple of dll’s. to install
> > the driver manually i do from elevated command prompt :
> >
> > |devcon install driver.inf HID\driver|
>
> No, no, no, no!!! That does NOT do what you think it does. “devcon
> install” is an enticing-sounding tool, but it CANNOT be used to install
> plug-and-play drivers. What that command does is create a FAKE device
> with the ID you specify, then load your driver to handle that fake
> device. Your driver will not be talking to real hardware.
>
> Do not install drivers manually. The best way is to use something like
> “dpinst” to help do your installation. If necessary, you can use
> “devcon update” to replace the drivers with your set, but “devcon
> install” will NOT do it.
>
In this case I believe the device is virtual. In which case I would just
distribute devcon and have the installer execute that (taking note of the
return code)
You are not allowed to redistribute devcon as is. If he wants a virtual hid miniport enumerated, the hw id should not start with "HID" because hidclass enumerated pdos use that prefix, not the parent miniport stack.
d
debt from my phone
From: Daniel Newton
Sent: 5/30/2012 6:47 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installer for windows 7/8 driver .
On Thu, May 31, 2012 at 10:33 AM, Tim Roberts > wrote:
Rajat goyal wrote:
>
> I have a .inf file and a .sys file and a couple of dll’s. to install
> the driver manually i do from elevated command prompt :
>
> |devcon install driver.inf HID\driver|
No, no, no, no!!! That does NOT do what you think it does. “devcon
install” is an enticing-sounding tool, but it CANNOT be used to install
plug-and-play drivers. What that command does is create a FAKE device
with the ID you specify, then load your driver to handle that fake
device. Your driver will not be talking to real hardware.
Do not install drivers manually. The best way is to use something like
“dpinst” to help do your installation. If necessary, you can use
“devcon update” to replace the drivers with your set, but “devcon
install” will NOT do it.
In this case I believe the device is virtual. In which case I would just distribute devcon and have the installer execute that (taking note of the return code)
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Yes it is a virtual root enumerated driver created by Daniel Newton (
http://code.google.com/p/vmulti/ ) himself .
I am using hardware id that starts with “HID/” and the driver seems to be
working fine.
On Thu, May 31, 2012 at 8:24 AM, Doron Holan wrote:
> You are not allowed to redistribute devcon as is. If he wants a virtual
> hid miniport enumerated, the hw id should not start with "HID" because
> hidclass enumerated pdos use that prefix, not the parent miniport stack.
>
> d
>
> debt from my phone
> ------------------------------
> From: Daniel Newton
> Sent: 5/30/2012 6:47 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Installer for windows 7/8 driver .
>
>
> On Thu, May 31, 2012 at 10:33 AM, Tim Roberts wrote:
>
>> Rajat goyal wrote:
>> >
>> > I have a .inf file and a .sys file and a couple of dll’s. to install
>> > the driver manually i do from elevated command prompt :
>> >
>> > |devcon install driver.inf HID\driver|
>>
>> No, no, no, no!!! That does NOT do what you think it does. “devcon
>> install” is an enticing-sounding tool, but it CANNOT be used to install
>> plug-and-play drivers. What that command does is create a FAKE device
>> with the ID you specify, then load your driver to handle that fake
>> device. Your driver will not be talking to real hardware.
>>
>> Do not install drivers manually. The best way is to use something like
>> “dpinst” to help do your installation. If necessary, you can use
>> “devcon update” to replace the drivers with your set, but “devcon
>> install” will NOT do it.
>>
>
> In this case I believe the device is virtual. In which case I would just
> distribute devcon and have the installer execute that (taking note of the
> return code)
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging
> and other seminars visit: http://www.osr.com/seminars To unsubscribe,
> visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
Rajat Goyal,
AH6,227
Bits Pilani Goa , India
http://goyalrajat.in
> No, no, no, no!!! That does NOT do what you think it does. "devcon
install" is an enticing-sounding tool, but it CANNOT be used to install
plug-and-play drivers. What that command does is create a FAKE device
with the ID you specify, then load your driver to handle that fake
device. Your driver will not be talking to real hardware.
Correct. “devcon dp_add” is the command to install the driver package.
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
It works, but it is not correct. a user mode app can enumerate by enumerator (ie the first part of the hardware ID, the “HID” part in your case) and since the HID enumerator means it is a HID device that supports the HID IOCTLs and APIs, it can be opened as a HID. A HID miniport cannot be opened as a HID.
d
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Rajat goyal
Sent: Wednesday, May 30, 2012 9:31 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installer for windows 7/8 driver .
Yes it is a virtual root enumerated driver created by Daniel Newton ( http://code.google.com/p/vmulti/ ) himself .
I am using hardware id that starts with “HID/” and the driver seems to be working fine.
On Thu, May 31, 2012 at 8:24 AM, Doron Holan > wrote:
You are not allowed to redistribute devcon as is. If he wants a virtual hid miniport enumerated, the hw id should not start with "HID" because hidclass enumerated pdos use that prefix, not the parent miniport stack.
d
debt from my phone
________________________________
From: Daniel Newton
Sent: 5/30/2012 6:47 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installer for windows 7/8 driver .
On Thu, May 31, 2012 at 10:33 AM, Tim Roberts > wrote:
Rajat goyal wrote:
>
> I have a .inf file and a .sys file and a couple of dll’s. to install
> the driver manually i do from elevated command prompt :
>
> |devcon install driver.inf HID\driver|
No, no, no, no!!! That does NOT do what you think it does. “devcon
install” is an enticing-sounding tool, but it CANNOT be used to install
plug-and-play drivers. What that command does is create a FAKE device
with the ID you specify, then load your driver to handle that fake
device. Your driver will not be talking to real hardware.
Do not install drivers manually. The best way is to use something like
“dpinst” to help do your installation. If necessary, you can use
“devcon update” to replace the drivers with your set, but “devcon
install” will NOT do it.
In this case I believe the device is virtual. In which case I would just distribute devcon and have the installer execute that (taking note of the return code)
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
–
Rajat Goyal,
AH6,227
Bits Pilani Goa , India
http://goyalrajat.in
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>You are not allowed to redistribute devcon as is.
Can you elaborate on this? I believe dpinst is re-distributable, what is
the difference here?
On Thu, May 31, 2012 at 2:54 PM, Doron Holan wrote:
> You are not allowed to redistribute devcon as is. If he wants a virtual
> hid miniport enumerated, the hw id should not start with "HID" because
> hidclass enumerated pdos use that prefix, not the parent miniport stack.
>
> d
>
> debt from my phone
> ------------------------------
> From: Daniel Newton
> Sent: 5/30/2012 6:47 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Installer for windows 7/8 driver .
>
> On Thu, May 31, 2012 at 10:33 AM, Tim Roberts wrote:
>
>> Rajat goyal wrote:
>> >
>> > I have a .inf file and a .sys file and a couple of dll’s. to install
>> > the driver manually i do from elevated command prompt :
>> >
>> > |devcon install driver.inf HID\driver|
>>
>> No, no, no, no!!! That does NOT do what you think it does. “devcon
>> install” is an enticing-sounding tool, but it CANNOT be used to install
>> plug-and-play drivers. What that command does is create a FAKE device
>> with the ID you specify, then load your driver to handle that fake
>> device. Your driver will not be talking to real hardware.
>>
>> Do not install drivers manually. The best way is to use something like
>> “dpinst” to help do your installation. If necessary, you can use
>> “devcon update” to replace the drivers with your set, but “devcon
>> install” will NOT do it.
>>
>
> In this case I believe the device is virtual. In which case I would just
> distribute devcon and have the installer execute that (taking note of the
> return code)
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging
> and other seminars visit: http://www.osr.com/seminars To unsubscribe,
> visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
Anything under the redist subtree is redistributable, anything not under the tree is not. Dpinst is under the redist tree
d
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Newton
Sent: Wednesday, May 30, 2012 10:30 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installer for windows 7/8 driver .
You are not allowed to redistribute devcon as is.
Can you elaborate on this? I believe dpinst is re-distributable, what is the difference here?
On Thu, May 31, 2012 at 2:54 PM, Doron Holan > wrote:
You are not allowed to redistribute devcon as is. If he wants a virtual hid miniport enumerated, the hw id should not start with "HID" because hidclass enumerated pdos use that prefix, not the parent miniport stack.
d
debt from my phone
________________________________
From: Daniel Newton
Sent: 5/30/2012 6:47 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installer for windows 7/8 driver .
On Thu, May 31, 2012 at 10:33 AM, Tim Roberts > wrote:
Rajat goyal wrote:
>
> I have a .inf file and a .sys file and a couple of dll’s. to install
> the driver manually i do from elevated command prompt :
>
> |devcon install driver.inf HID\driver|
No, no, no, no!!! That does NOT do what you think it does. “devcon
install” is an enticing-sounding tool, but it CANNOT be used to install
plug-and-play drivers. What that command does is create a FAKE device
with the ID you specify, then load your driver to handle that fake
device. Your driver will not be talking to real hardware.
Do not install drivers manually. The best way is to use something like
“dpinst” to help do your installation. If necessary, you can use
“devcon update” to replace the drivers with your set, but “devcon
install” will NOT do it.
In this case I believe the device is virtual. In which case I would just distribute devcon and have the installer execute that (taking note of the return code)
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Thanks Doron,
Another discussion is here
http://www.osronline.com/showThread.CFM?link=118557
It seems that one is able to copy the parts of the devcon source that they
need in order to create a specific driver installer binary.
Also cheers for the heads up regarding the use of "HID" in the hardware id
On Thu, May 31, 2012 at 5:40 PM, Doron Holan wrote:
> Anything under the redist subtree is redistributable, anything not under
> the tree is not. Dpinst is under the redist tree
>
>
>
> d
>
> ****
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Daniel Newton
> Sent: Wednesday, May 30, 2012 10:30 PM
>
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Installer for windows 7/8 driver .
>
>
>
> >You are not allowed to redistribute devcon as is.
>
> Can you elaborate on this? I believe dpinst is re-distributable, what is
> the difference here?
>
> On Thu, May 31, 2012 at 2:54 PM, Doron Holan
> wrote:
>
> You are not allowed to redistribute devcon as is. If he wants a virtual
> hid miniport enumerated, the hw id should not start with "HID" because
> hidclass enumerated pdos use that prefix, not the parent miniport stack.
>
> d
>
> debt from my phone
> ------------------------------
>
> *From: *Daniel Newton
> *Sent: *5/30/2012 6:47 PM
> *To: *Windows System Software Devs Interest List
> *Subject: *Re: [ntdev] Installer for windows 7/8 driver .
>
> On Thu, May 31, 2012 at 10:33 AM, Tim Roberts wrote:
>
> Rajat goyal wrote:
> >
> > I have a .inf file and a .sys file and a couple of dll’s. to install
> > the driver manually i do from elevated command prompt :
> >
> > |devcon install driver.inf HID\driver|
>
> No, no, no, no!!! That does NOT do what you think it does. “devcon
> install” is an enticing-sounding tool, but it CANNOT be used to install
> plug-and-play drivers. What that command does is create a FAKE device
> with the ID you specify, then load your driver to handle that fake
> device. Your driver will not be talking to real hardware.
>
> Do not install drivers manually. The best way is to use something like
> “dpinst” to help do your installation. If necessary, you can use
> “devcon update” to replace the drivers with your set, but “devcon
> install” will NOT do it.
>
>
> In this case I believe the device is virtual. In which case I would just
> distribute devcon and have the installer execute that (taking note of the
> return code)
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
Correct. you can derive from the sample, you can’t ship the sample as is, with the name as is
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Newton
Sent: Thursday, May 31, 2012 12:19 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installer for windows 7/8 driver .
Thanks Doron,
Another discussion is here http://www.osronline.com/showThread.CFM?link=118557
It seems that one is able to copy the parts of the devcon source that they need in order to create a specific driver installer binary.
Also cheers for the heads up regarding the use of "HID" in the hardware id
On Thu, May 31, 2012 at 5:40 PM, Doron Holan > wrote:
Anything under the redist subtree is redistributable, anything not under the tree is not. Dpinst is under the redist tree
d
From: xxxxx@lists.osr.commailto:xxxxx [mailto:xxxxx@lists.osr.commailto:xxxxx] On Behalf Of Daniel Newton
Sent: Wednesday, May 30, 2012 10:30 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installer for windows 7/8 driver .
>You are not allowed to redistribute devcon as is.
Can you elaborate on this? I believe dpinst is re-distributable, what is the difference here?
On Thu, May 31, 2012 at 2:54 PM, Doron Holan > wrote:
You are not allowed to redistribute devcon as is. If he wants a virtual hid miniport enumerated, the hw id should not start with "HID" because hidclass enumerated pdos use that prefix, not the parent miniport stack.
d
debt from my phone
________________________________
From: Daniel Newton
Sent: 5/30/2012 6:47 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installer for windows 7/8 driver .
On Thu, May 31, 2012 at 10:33 AM, Tim Roberts > wrote:
Rajat goyal wrote:
>
> I have a .inf file and a .sys file and a couple of dll’s. to install
> the driver manually i do from elevated command prompt :
>
> |devcon install driver.inf HID\driver|
No, no, no, no!!! That does NOT do what you think it does. “devcon
install” is an enticing-sounding tool, but it CANNOT be used to install
plug-and-play drivers. What that command does is create a FAKE device
with the ID you specify, then load your driver to handle that fake
device. Your driver will not be talking to real hardware.
Do not install drivers manually. The best way is to use something like
“dpinst” to help do your installation. If necessary, you can use
“devcon update” to replace the drivers with your set, but “devcon
install” will NOT do it.
In this case I believe the device is virtual. In which case I would just distribute devcon and have the installer execute that (taking note of the return code)
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>
Daniel Newton wrote:
>You are not allowed to redistribute devcon as is.
Can you elaborate on this? I believe dpinst is re-distributable, what
is the difference here?
Note that you can cut-and-paste code from devcon into your own utilities
(that’s really what it’s there for). You just can’t redistribute the
binary.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Aside the devcon questions - what are BKMs
for installing shared usermode components with a driver:
API DLLs, control applets etc. ?
( the old good DLLs like for win7 - not the win8 Metro insanity)
We’ve seen some people create subdirs under system32,
others install directly to system 32 or syswow64…
Thanks,
– pa
Pavel A. wrote:
Aside the devcon questions - what are BKMs
for installing shared usermode components with a driver:
API DLLs, control applets etc. ?
( the old good DLLs like for win7 - not the win8 Metro insanity)We’ve seen some people create subdirs under system32,
others install directly to system 32 or syswow64…
Here’s my philosophy. If I’m installing it in the INF file, then it
belongs in system32 and syswow64. My capture drivers all have ksproxy
plugins, and I copy those to system32 or syswow64 in the INF. Really,
there is no other good choice. Control panel applets really need to go
in system32 as well.
For other DLLs, the choice is not so clear. COM is nice because I can
leave the DLL anywhere and include a pointer in the registry. I hate
PATH inflation, so I’d much rather put a shared API DLL in system32
instead of putting a single DLL in a folder that has to be added to the
path.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Thank you, Tim
“Tim Roberts” wrote in message news:xxxxx@ntdev…
> Pavel A. wrote:
>> Aside the devcon questions - what are BKMs
>> for installing shared usermode components with a driver:
>> API DLLs, control applets etc. ?
>> ( the old good DLLs like for win7 - not the win8 Metro insanity)
>>
>> We’ve seen some people create subdirs under system32,
>> others install directly to system 32 or syswow64…
>
> Here’s my philosophy. If I’m installing it in the INF file, then it
> belongs in system32 and syswow64. My capture drivers all have ksproxy
> plugins, and I copy those to system32 or syswow64 in the INF. Really,
> there is no other good choice. Control panel applets really need to go
> in system32 as well.
>
> For other DLLs, the choice is not so clear. COM is nice because I can
> leave the DLL anywhere and include a pointer in the registry. I hate
> PATH inflation, so I’d much rather put a shared API DLL in system32
> instead of putting a single DLL in a folder that has to be added to the
> path.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>