Hi
When I’m trying to install my NDIS IM driver in WinXp, I get the
“Windows logo program message box” with the “continue” and stop
installation buttons.
I know that for commercial use, drivers need some kind of license, and
I’ve heard of WHQL and Verisign.
Can someone please tell me which one of the licenses does NDIS IM
need? Is Verisign should be enough?
Thanks.
> I know that for commercial use, drivers need some kind of license
Actually, I never heard about anything like that…
and I’ve heard of WHQL and Verisign.
They have rather different meaning. WHQL is all about compatibility and programming techniques
( a driver that, say, hooks SSDT has no chance of ever getting signed), and Verisign signature is all about identification ( it just confirms that driver writer’s identity is known - nothing more than that).
In any case, they are optional under any OS, apart from 64-bit Vista - there are *plenty* of commercially-available drivers that have no signature at all, and, hence, you see the above mentioned dialog box when you install them. 64-bit Vista is a different story - indeed, it would not load an unsigned driver
Can someone please tell me which one of the licenses does NDIS IM need?
As long as you are speaking about 32-bit Windows (including Vista) and pre-Vista 64-bit Windows,
you don’t really need a signature at all.
Is Verisign should be enough?
If you are interested in Windows logo you need WHQL signature, which is true for all Windows versions - Verisign is of no help here…
Anton Bassov
Thanks for the info.
Hi,
Thanks for the detailed response.
Vista 64 is not in our scope at the moment. We only need support Win2k
? WinVista in both 32 & 64 bit except for Vista.
My main objective is to make that the “Windows logo program message
box” disappear. For the moment, the license itself is less important.
If I understood right, the “Windows logo program message box” is seen
if the driver didn’t pass the WHQL test and got Microsoft’s signature.
So:
On 4/22/07, xxxxx@hotmail.com wrote:
> > I know that for commercial use, drivers need some kind of license
>
> Actually, I never heard about anything like that…
>
> > and I’ve heard of WHQL and Verisign.
>
> They have rather different meaning. WHQL is all about compatibility and programming techniques
> ( a driver that, say, hooks SSDT has no chance of ever getting signed), and Verisign signature is all about identification ( it just confirms that driver writer’s identity is known - nothing more than that).
>
> In any case, they are optional under any OS, apart from 64-bit Vista - there are plenty of commercially-available drivers that have no signature at all, and, hence, you see the above mentioned dialog box when you install them. 64-bit Vista is a different story - indeed, it would not load an unsigned driver
>
> > Can someone please tell me which one of the licenses does NDIS IM need?
>
> As long as you are speaking about 32-bit Windows (including Vista) and pre-Vista 64-bit Windows,
> you don’t really need a signature at all.
>
> > Is Verisign should be enough?
>
> If you are interested in Windows logo you need WHQL signature, which is true for all Windows versions - Verisign is of no help here…
>
> Anton Bassov
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
Comments inline:
wrote in message news:xxxxx@ntdev…
>> I know that for commercial use, drivers need some kind of license
>
> Actually, I never heard about anything like that…
A lot of firms require WHQL signed drivers, so in the general sense his
statement about commercial use is correct since it makes it easier to sell
you product.
>> and I’ve heard of WHQL and Verisign.
>
> They have rather different meaning. WHQL is all about compatibility and
> programming techniques
> ( a driver that, say, hooks SSDT has no chance of ever getting signed),
> and Verisign signature is all about identification ( it just confirms
> that driver writer’s identity is known - nothing more than that).
Actually, Verisign is needed to get WHQL, since you need to log in with a
Verisign ID.
> In any case, they are optional under any OS, apart from 64-bit Vista -
> there are plenty of commercially-available drivers that have no
> signature at all, and, hence, you see the above mentioned dialog box when
> you install them. 64-bit Vista is a different story - indeed, it would
> not load an unsigned driver
There are a lot of unsigned commercial drivers, and there are a lot of
firms that will not buy them. Also, Vista allows installation of drivers
IIRC by non-administrators if they ar WHQL signed.
>> Can someone please tell me which one of the licenses does NDIS IM need?
>
> As long as you are speaking about 32-bit Windows (including Vista) and
> pre-Vista 64-bit Windows,
> you don’t really need a signature at all.
Again, it depends on your customer base, Anton is correct it is not
required by Microsoft, but it is desirable from a sales point of view.
>> Is Verisign should be enough?
>
> If you are interested in Windows logo you need WHQL signature, which is
> true for all Windows versions - Verisign is of no help here…
As I said earlier Verisign is required to get a WHQL signature and to get
access to the WinQUAL database. One of the great things about WHQL is if
the system crashes due to your driver and the uses chooses “Send Error
Report” you can get the dump and perhaps fix the problem. Otherwise you
will never know it happened, and people will just blame your firm.
–
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
To make the Unsigned Driver warning dialog box disappear your NDIS IM driver
must have been tested using the WHQL Hardware Compatibility Test (HCT) NDIS
Tests or (possibly) using the newer Driver Test Manager (DTM) NDIS tests.
Some information can be found at the URL:
http://www.microsoft.com/whdc/winlogo/drvsign/drvsign.mspx
You need a Verisign code signing ID simply to open a WHQL account. You must
have a WHQL account to even be able to submit a test results package to WHQL
for them to give you a WHQL signature (assuming that your tests pass).
You then need to perform the HCT or DTM tests exactly as specified by WHQL
and submit the test results to WHQL using your account. Before you actually
run your HCT or DTM tests you will temporarily sign your “driver package”
(your .SYS, .INF. .CAT and possibly other files referenced by your .INF)
using your code signing ID. This step is not the actual “signature” for your
driver package, but simply lets WHQL know for sure that the driver package
being submitted is actually from the WHQL account that it is being submitted
on.
Run the tests. Collect the results and make a “submission package” to be
sent to WHQL. They will review the results and send the WHQL-sugned package
back to you.
You must perform tests on all OS that you want to have signature for.
This is, unfortunately, a time-consuming and complex process - particularly
if you have not done it before.
Another issue is that WHQL will stop accepting submissions made using the
HCT after about June 1. After that you must use the newer DTM to make tests.
The DTM is difficult to use and has no public Microsoft support; DTM support
is strictly on a paid per-incident basis. 
Good luck,
Thomas F. Divine
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-284270-
xxxxx@lists.osr.com] On Behalf Of Omer B
Sent: Sunday, April 22, 2007 10:14 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] NDIS IM driver signingThanks for the info.
Hi,
Thanks for the detailed response.
Vista 64 is not in our scope at the moment. We only need support Win2k
- WinVista in both 32 & 64 bit except for Vista.
My main objective is to make that the “Windows logo program message
box” disappear. For the moment, the license itself is less important.If I understood right, the “Windows logo program message box” is seen
if the driver didn’t pass the WHQL test and got Microsoft’s signature.
So:
- Verisign is only used for identification of the driver, and
therefore won’t have any effect for the presence of that message box?- As a company, my interest to have Verisign signature is for the
“safety” of my customers?- Why for example when File Filter drivers and TDI drivers are
install and running I don’t see the “Windows logo program message
box”?- So is there any way to “Silently” install my IM and bypass this
“Windows logo” window? I don’t see how an IM driver can be installed
with only CreateService. In the IM INF files there are much more
registry operations then what CreateService does.On 4/22/07, xxxxx@hotmail.com wrote:
> > > I know that for commercial use, drivers need some kind of license
> >
> > Actually, I never heard about anything like that…
> >
> > > and I’ve heard of WHQL and Verisign.
> >
> > They have rather different meaning. WHQL is all about compatibility
> and programming techniques
> > ( a driver that, say, hooks SSDT has no chance of ever getting
> signed), and Verisign signature is all about identification ( it just
> confirms that driver writer’s identity is known - nothing more than
> that).
> >
> > In any case, they are optional under any OS, apart from 64-bit Vista
> - there are plenty of commercially-available drivers that have no
> signature at all, and, hence, you see the above mentioned dialog box
> when you install them. 64-bit Vista is a different story - indeed, it
> would not load an unsigned driver
> >
> > > Can someone please tell me which one of the licenses does NDIS IM
> need?
> >
> > As long as you are speaking about 32-bit Windows (including Vista)
> and pre-Vista 64-bit Windows,
> > you don’t really need a signature at all.
> >
> > > Is Verisign should be enough?
> >
> > If you are interested in Windows logo you need WHQL signature, which
> is true for all Windows versions - Verisign is of no help here…
> >
> > Anton Bassov
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
> >
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
Don,
> Actually, I never heard about anything like that…
A lot of firms require WHQL signed drivers, so in the general sense his
statement about commercial use is correct since it makes it easier to sell you product.
Please don’t confuse the terms “desireable” and “required” - the very term “licence” invariably implies strictly the latter…
Of course it is better, from the commercial perspective, to have your driver signed - it would be just stupid to argue about it. However, it is not an absolute requirement, so that signing a driver and obtaining a licence are two different things
> They have rather different meaning. WHQL is all about compatibility and
> programming techniques
> ( a driver that, say, hooks SSDT has no chance of ever getting signed),
> and Verisign signature is all about identification ( it just confirms
> that driver writer’s identity is known - nothing more than that).
Actually, Verisign is needed to get WHQL, since you need to log in with a
Verisign ID.
This is true, but, once the OP wants to avoid message box altogether he needs WHQL - Verisign signature alone is not enough here. Therefore, his IM needs to meet some certain requirements when it comes to implementation, although he can get Verisign signature regardless of programming techniques it employs…
Anton Bassov
OK, we don’t need the licence. This driver is a part from a whole
product and an organization decision whatever to buy the product or
not is not effected from this parameter.
Also, the driver itself is really compatible to all Microsoft
standards, and isn’t doing anything “bad”.
There is no way to bypass this dialog? installing this driver in a
manual way (by doing the necessary registry changes myself for
example) won’t work ?
On 4/22/07, xxxxx@hotmail.com wrote:
> Don,
>
> >> Actually, I never heard about anything like that…
>
> > A lot of firms require WHQL signed drivers, so in the general sense his
> > statement about commercial use is correct since it makes it easier to sell you product.
>
> Please don’t confuse the terms “desireable” and “required” - the very term “licence” invariably implies strictly the latter…
>
> Of course it is better, from the commercial perspective, to have your driver signed - it would be just stupid to argue about it. However, it is not an absolute requirement, so that signing a driver and obtaining a licence are two different things
>
> >> They have rather different meaning. WHQL is all about compatibility and
> >> programming techniques
> >> ( a driver that, say, hooks SSDT has no chance of ever getting signed),
> >> and Verisign signature is all about identification ( it just confirms
> >> that driver writer’s identity is known - nothing more than that).
>
> > Actually, Verisign is needed to get WHQL, since you need to log in with a
> > Verisign ID.
>
> This is true, but, once the OP wants to avoid message box altogether he needs WHQL - Verisign signature alone is not enough here. Therefore, his IM needs to meet some certain requirements when it comes to implementation, although he can get Verisign signature regardless of programming techniques it employs…
>
> Anton Bassov
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
> Why for example when File Filter drivers and TDI drivers are
install and running I don’t see the “Windows logo program message
box”?
Ironically, you gave an answer to the above question yourself - here are your words:
I don’t see how an IM driver can be installed with only CreateService. In the IM INF
files there are much more registry operations then what CreateService does.
You install TDI filter simply by clicking on its .INF file, i.e. without either PnP Manager’s or NetCfg’s involvement - the only thing this installation does is creating the service in the registry. However, NDIS IM is much more complex installation that requires NetCfg’s involvement. This is why you get this message box…
So is there any way to “Silently” install my IM and bypass this “Windows logo” window?
Well, certainly, you can try to play around with the registry, but, unless you *REALLY* know what you are doing, you are more than likely to screw it up - quite a few changes under HKLM\SYSTEM\CurrentControlSet\Control\Class{4D36E972-E325-11CE-BFC1-08002bE10318} and HKLM\SYSTEM\CurrentControlSet\Control\Network registry keys are requited
My main objective is to make that the “Windows logo program message box” disappear.
WHQL certification is the best option here…
Anton Bassov
> -----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-284274-
xxxxx@lists.osr.com] On Behalf Of Omer B
Sent: Sunday, April 22, 2007 11:35 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] NDIS IM driver signingOK, we don’t need the licence. This driver is a part from a whole
product and an organization decision whatever to buy the product or
not is not effected from this parameter.
[PCAUSA] There is no “license” at all - except for any license you may
invent to specify what rights exist between you and your customers.
The idea of “license” is strictly between you and your customers and has
nothing at all to do with driver signing and the unsigned driver warnings.
Also, the driver itself is really compatible to all Microsoft
standards, and isn’t doing anything “bad”.There is no way to bypass this dialog? installing this driver in a
manual way (by doing the necessary registry changes myself for
example) won’t work ?
[PCAUSA] It would be foolish of you to attempt to make the registry changes
necessary to install a NDIS driver yourself. Horrible idea.
There are many reasons for this. For example: How would you deal with the
case that the user uninstalled an adapter and replaced it with another?
Would your registry hack be smart enough to even detect that this is
happening, much less properly re-bind the new adapter to the correct
components?
Better to live with the unsigned driver warning, I think.
Or go through the steps necessary to get the driver signed by WHQL.
Thomas F. Divine
On 4/22/07, xxxxx@hotmail.com wrote:
> > Don,
> >
> > >> Actually, I never heard about anything like that…
> >
> > > A lot of firms require WHQL signed drivers, so in the general sense
> his
> > > statement about commercial use is correct since it makes it easier
> to sell you product.
> >
> > Please don’t confuse the terms “desireable” and “required” - the very
> term “licence” invariably implies strictly the latter…
> >
> > Of course it is better, from the commercial perspective, to have
> your driver signed - it would be just stupid to argue about it.
> However, it is not an absolute requirement, so that signing a driver
> and obtaining a licence are two different things
> >
> > >> They have rather different meaning. WHQL is all about
> compatibility and
> > >> programming techniques
> > >> ( a driver that, say, hooks SSDT has no chance of ever getting
> signed),
> > >> and Verisign signature is all about identification ( it just
> confirms
> > >> that driver writer’s identity is known - nothing more than that).
> >
> > > Actually, Verisign is needed to get WHQL, since you need to log in
> with a
> > > Verisign ID.
> >
> > This is true, but, once the OP wants to avoid message box altogether
> he needs WHQL - Verisign signature alone is not enough here. Therefore,
> his IM needs to meet some certain requirements when it comes to
> implementation, although he can get Verisign signature regardless of
> programming techniques it employs…
> >
> > Anton Bassov
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
> >
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
“Omer B” wrote in message news:xxxxx@ntdev…
> OK, we don’t need the licence. This driver is a part from a whole
> product and an organization decision whatever to buy the product or
> not is not effected from this parameter.
>
> Also, the driver itself is really compatible to all Microsoft
> standards, and isn’t doing anything “bad”.
>
> There is no way to bypass this dialog? installing this driver in a
> manual way (by doing the necessary registry changes myself for
> example) won’t work ?
Don’t go there, there a several lawsuits that have arisen from bozo’s doing
things to hide the popup (or cause the correct button to be pushed so it
disapears immediately). All you will do with trying to hide the popup
(unless you sign the driver) is to ruin your firms and your reputation.
–
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
You know, it is not that I’m looking for shortcuts, bu people here are
so “afraid” from the length and the bureaucracy of the process of
getting a WHQL certification that they think about canceling this
feature.
Sound strange, I know… but what can i do ?
So you say that manual installation (manualy change the registry) will
do the job? and i must reboot the system if i do it this way, right ?
On 4/22/07, xxxxx@hotmail.com wrote:
> > Why for example when File Filter drivers and TDI drivers are
> > install and running I don’t see the “Windows logo program message
> > box”?
>
> Ironically, you gave an answer to the above question yourself - here are your words:
>
> > I don’t see how an IM driver can be installed with only CreateService. In the IM INF
> > files there are much more registry operations then what CreateService does.
>
> You install TDI filter simply by clicking on its .INF file, i.e. without either PnP Manager’s or NetCfg’s involvement - the only thing this installation does is creating the service in the registry. However, NDIS IM is much more complex installation that requires NetCfg’s involvement. This is why you get this message box…
>
> > So is there any way to “Silently” install my IM and bypass this “Windows logo” window?
>
> Well, certainly, you can try to play around with the registry, but, unless you REALLY know what you are doing, you are more than likely to screw it up - quite a few changes under HKLM\SYSTEM\CurrentControlSet\Control\Class{4D36E972-E325-11CE-BFC1-08002bE10318} and HKLM\SYSTEM\CurrentControlSet\Control\Network registry keys are requited
>
> > My main objective is to make that the “Windows logo program message box” disappear.
>
> WHQL certification is the best option here…
>
> Anton Bassov
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
“Omer B” wrote in message news:xxxxx@ntdev…
> You know, it is not that I’m looking for shortcuts, bu people here are
> so “afraid” from the length and the bureaucracy of the process of
> getting a WHQL certification that they think about canceling this
> feature.
>
> Sound strange, I know… but what can i do ?
>
> So you say that manual installation (manualy change the registry) will
> do the job? and i must reboot the system if i do it this way, right ?
>
First, can your driver pass the WHQL tests? Even if you are not going to
get a logo you should be trying to run them since they are a way to find
bugs. Now if you driver passes the tests it will take less time to get
logo’d than it will do implement any of the hacks people can suggest.
The only challenge comes if you driver does not pass the logo tests, and
you feel the tests are in error, otherwise this is a typically a week and a
couple hundred dollars. So before going to great lengths and doing it
wrong, run the tests and see if you can do it right.
–
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
I didn’t run the WHQL tests so i still don’t know… but it’s a good
idea to start.
Any special idea for me not to pass them ?
How much time does it take from the time you pass them until you get
the certification?
From most of what I’ve read about this process, it’s sounds pretty long…
On 4/22/07, Don Burn wrote:
>
> “Omer B” wrote in message news:xxxxx@ntdev…
> > You know, it is not that I’m looking for shortcuts, bu people here are
> > so “afraid” from the length and the bureaucracy of the process of
> > getting a WHQL certification that they think about canceling this
> > feature.
> >
> > Sound strange, I know… but what can i do ?
> >
> > So you say that manual installation (manualy change the registry) will
> > do the job? and i must reboot the system if i do it this way, right ?
> >
> First, can your driver pass the WHQL tests? Even if you are not going to
> get a logo you should be trying to run them since they are a way to find
> bugs. Now if you driver passes the tests it will take less time to get
> logo’d than it will do implement any of the hacks people can suggest.
>
> The only challenge comes if you driver does not pass the logo tests, and
> you feel the tests are in error, otherwise this is a typically a week and a
> couple hundred dollars. So before going to great lengths and doing it
> wrong, run the tests and see if you can do it right.
>
>
> –
> 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
>
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
Thomas,
I’m sorry, i always confuse between licence and certificate.
Anyway, after my IM is manually installed and i do a reboot - isn’t
the OS will take care all the scenarios you’ve just described ?
On 4/22/07, Thomas F. Divine wrote:
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com [mailto:bounce-284274-
> > xxxxx@lists.osr.com] On Behalf Of Omer B
> > Sent: Sunday, April 22, 2007 11:35 AM
> > To: Windows System Software Devs Interest List
> > Subject: Re: [ntdev] NDIS IM driver signing
> >
> > OK, we don’t need the licence. This driver is a part from a whole
> > product and an organization decision whatever to buy the product or
> > not is not effected from this parameter.
> [PCAUSA] There is no “license” at all - except for any license you may
> invent to specify what rights exist between you and your customers.
>
> The idea of “license” is strictly between you and your customers and has
> nothing at all to do with driver signing and the unsigned driver warnings.
>
> >
> > Also, the driver itself is really compatible to all Microsoft
> > standards, and isn’t doing anything “bad”.
> >
> > There is no way to bypass this dialog? installing this driver in a
> > manual way (by doing the necessary registry changes myself for
> > example) won’t work ?
> >
> [PCAUSA] It would be foolish of you to attempt to make the registry changes
> necessary to install a NDIS driver yourself. Horrible idea.
>
> There are many reasons for this. For example: How would you deal with the
> case that the user uninstalled an adapter and replaced it with another?
> Would your registry hack be smart enough to even detect that this is
> happening, much less properly re-bind the new adapter to the correct
> components?
>
> Better to live with the unsigned driver warning, I think.
>
> Or go through the steps necessary to get the driver signed by WHQL.
>
> Thomas F. Divine
>
> >
> >
> >
> > On 4/22/07, xxxxx@hotmail.com wrote:
> > > Don,
> > >
> > > >> Actually, I never heard about anything like that…
> > >
> > > > A lot of firms require WHQL signed drivers, so in the general sense
> > his
> > > > statement about commercial use is correct since it makes it easier
> > to sell you product.
> > >
> > > Please don’t confuse the terms “desireable” and “required” - the very
> > term “licence” invariably implies strictly the latter…
> > >
> > > Of course it is better, from the commercial perspective, to have
> > your driver signed - it would be just stupid to argue about it.
> > However, it is not an absolute requirement, so that signing a driver
> > and obtaining a licence are two different things
> > >
> > > >> They have rather different meaning. WHQL is all about
> > compatibility and
> > > >> programming techniques
> > > >> ( a driver that, say, hooks SSDT has no chance of ever getting
> > signed),
> > > >> and Verisign signature is all about identification ( it just
> > confirms
> > > >> that driver writer’s identity is known - nothing more than that).
> > >
> > > > Actually, Verisign is needed to get WHQL, since you need to log in
> > with a
> > > > Verisign ID.
> > >
> > > This is true, but, once the OP wants to avoid message box altogether
> > he needs WHQL - Verisign signature alone is not enough here. Therefore,
> > his IM needs to meet some certain requirements when it comes to
> > implementation, although he can get Verisign signature regardless of
> > programming techniques it employs…
> > >
> > > Anton Bassov
> > >
> > > —
> > > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> > >
> > > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> > >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
> So you say that manual installation (manualy change the registry) will do the job?
It really depends on how you understand things - I think that after having read what Thomas,
Don and myself said on the issue, the above question may be asked only by someone with comprehension problems…
You know, it is not that I’m looking for shortcuts, bu people here are
so “afraid” from the length and the bureaucracy of the process of
getting a WHQL certification that they think about canceling this feature.
Then just leave it unsigned!!! Don’t you understand that manual installation is going to set users against your product much more than displayed message box??? I can assure you that you are more than likely to get into a scandal (probably, even a lawsuit) when this “feature” gets detected by customers. What is the point of going for trouble???
Anton Bassov
> -----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-284287-
xxxxx@lists.osr.com] On Behalf Of Omer B
Sent: Sunday, April 22, 2007 12:58 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] NDIS IM driver signingThomas,
I’m sorry, i always confuse between licence and certificate.
Anyway, after my IM is manually installed and i do a reboot - isn’t
the OS will take care all the scenarios you’ve just described ?
[PCAUSA] After you have gone through the WHQL signing process and have
received the WHQL-signed driver package, then when you install the
WHQL-signed driver package you won’t get the warnings.
Thomas F. Divine
On 4/22/07, Thomas F. Divine wrote:
> >
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com [mailto:bounce-284274-
> > > xxxxx@lists.osr.com] On Behalf Of Omer B
> > > Sent: Sunday, April 22, 2007 11:35 AM
> > > To: Windows System Software Devs Interest List
> > > Subject: Re: [ntdev] NDIS IM driver signing
> > >
> > > OK, we don’t need the licence. This driver is a part from a whole
> > > product and an organization decision whatever to buy the product or
> > > not is not effected from this parameter.
> > [PCAUSA] There is no “license” at all - except for any license you
> may
> > invent to specify what rights exist between you and your customers.
> >
> > The idea of “license” is strictly between you and your customers and
> has
> > nothing at all to do with driver signing and the unsigned driver
> warnings.
> >
> > >
> > > Also, the driver itself is really compatible to all Microsoft
> > > standards, and isn’t doing anything “bad”.
> > >
> > > There is no way to bypass this dialog? installing this driver in a
> > > manual way (by doing the necessary registry changes myself for
> > > example) won’t work ?
> > >
> > [PCAUSA] It would be foolish of you to attempt to make the registry
> changes
> > necessary to install a NDIS driver yourself. Horrible idea.
> >
> > There are many reasons for this. For example: How would you deal with
> the
> > case that the user uninstalled an adapter and replaced it with
> another?
> > Would your registry hack be smart enough to even detect that this is
> > happening, much less properly re-bind the new adapter to the correct
> > components?
> >
> > Better to live with the unsigned driver warning, I think.
> >
> > Or go through the steps necessary to get the driver signed by WHQL.
> >
> > Thomas F. Divine
> >
> > >
> > >
> > >
> > > On 4/22/07, xxxxx@hotmail.com
> wrote:
> > > > Don,
> > > >
> > > > >> Actually, I never heard about anything like that…
> > > >
> > > > > A lot of firms require WHQL signed drivers, so in the general
> sense
> > > his
> > > > > statement about commercial use is correct since it makes it
> easier
> > > to sell you product.
> > > >
> > > > Please don’t confuse the terms “desireable” and “required” - the
> very
> > > term “licence” invariably implies strictly the latter…
> > > >
> > > > Of course it is better, from the commercial perspective, to have
> > > your driver signed - it would be just stupid to argue about it.
> > > However, it is not an absolute requirement, so that signing a
> driver
> > > and obtaining a licence are two different things
> > > >
> > > > >> They have rather different meaning. WHQL is all about
> > > compatibility and
> > > > >> programming techniques
> > > > >> ( a driver that, say, hooks SSDT has no chance of ever getting
> > > signed),
> > > > >> and Verisign signature is all about identification ( it just
> > > confirms
> > > > >> that driver writer’s identity is known - nothing more than
> that).
> > > >
> > > > > Actually, Verisign is needed to get WHQL, since you need to log
> in
> > > with a
> > > > > Verisign ID.
> > > >
> > > > This is true, but, once the OP wants to avoid message box
> altogether
> > > he needs WHQL - Verisign signature alone is not enough here.
> Therefore,
> > > his IM needs to meet some certain requirements when it comes to
> > > implementation, although he can get Verisign signature regardless
> of
> > > programming techniques it employs…
> > > >
> > > > Anton Bassov
> > > >
> > > > —
> > > > Questions? First check the Kernel Driver FAQ at
> > > http://www.osronline.com/article.cfm?id=256
> > > >
> > > > To unsubscribe, visit the List Server section of OSR Online at
> > > http://www.osronline.com/page.cfm?name=ListServer
> > > >
> > >
> > > —
> > > Questions? First check the Kernel Driver FAQ at
> > > http://www.osronline.com/article.cfm?id=256
> > >
> > > To unsubscribe, visit the List Server section of OSR Online at
> > > http://www.osronline.com/page.cfm?name=ListServer
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
> >
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer