We have a two part INF install that we use to install our multi-port
serial boards. One INF is for the board or bus driver and the other part
is for the Ports.
We make use of cocpyinf to help streamline the installs under XP and 2000,
but we have been having problems with the install stopping as it installs
each child serial port, generally to warn about it not being a signed
driver. We intend to have this driver signed soon but in the mean time
our customers will find being bothered about each child serial port
install by the Unsigned Driver Nag screen a less than good user
experience.
Is there any good way around this?
Any insight would be great.
Allan
The word I got from Microsoft is that this is the way is supposed to be for
unsigned driver. They told me that the only solution is getting the driver
signed.
-Evan
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Allan Smith
Sent: Friday, May 03, 2002 6:48 AM
To: NT Developers Interest List
Subject: [ntdev] Signed driver nag screen on multi file driver INF
installs?
We have a two part INF install that we use to install our multi-port
serial boards. One INF is for the board or bus driver and the other part
is for the Ports.
We make use of cocpyinf to help streamline the installs under XP and 2000,
but we have been having problems with the install stopping as it installs
each child serial port, generally to warn about it not being a signed
driver. We intend to have this driver signed soon but in the mean time
our customers will find being bothered about each child serial port
install by the Unsigned Driver Nag screen a less than good user
experience.
Is there any good way around this?
Any insight would be great.
Allan
You are currently subscribed to ntdev as: xxxxx@attbi.com
To unsubscribe send a blank email to %%email.unsub%%
I can see why they would make this the general case and signed drivers have
definite Software Quality plusses, but it would be nice if they only
displayed the Nag screen once for each driver component during each install.
In our case, once for the port driver and once for the bus portion.
Having the signed driver dialogue box come up for every port being installed
certainly does not add to a good user experience. In our case this could be
repeated 128 times or more. : -(
Allan
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
Sent: May 3, 2002 11:23 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Signed driver nag screen on multi file driver INF
installs?
The word I got from Microsoft is that this is the way is supposed to be for
unsigned driver. They told me that the only solution is getting the driver
signed.
-Evan
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Allan Smith
Sent: Friday, May 03, 2002 6:48 AM
To: NT Developers Interest List
Subject: [ntdev] Signed driver nag screen on multi file driver INF
installs?
We have a two part INF install that we use to install our multi-port
serial boards. One INF is for the board or bus driver and the other part
is for the Ports.
We make use of cocpyinf to help streamline the installs under XP and 2000,
but we have been having problems with the install stopping as it installs
each child serial port, generally to warn about it not being a signed
driver. We intend to have this driver signed soon but in the mean time
our customers will find being bothered about each child serial port
install by the Unsigned Driver Nag screen a less than good user
experience.
Is there any good way around this?
Any insight would be great.
Allan
You are currently subscribed to ntdev as: xxxxx@attbi.com
To unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to ntdev as: xxxxx@connecttech.com
To unsubscribe send a blank email to %%email.unsub%%
Allan,
you wrote on Friday, May 03, 2002, 17:32:42:
AS> I can see why they would make this the general case and signed
AS> drivers have definite Software Quality plusses, but it would be nice
AS> if they only displayed the Nag screen once for each driver component
AS> during each install. In our case, once for the port driver and once
AS> for the bus portion.
You can temporarily shut off that nag screen by setting the “Policy”
value in ‘HKLM\Software\Microsoft\Driver Signing’ to 00 (binary). Make
sure to back up the current setting first and restore it afterwards. The
same setting should be reflected in
‘HKCU\Software\Microsoft\Driver Signing’, however, it needs to be a
DWORD here. Just play with the driver signing options available via
Control Panel - System - Hardware tab - Driver Signing button to see how
it affects the registry values.
Ralf.
Well, they have this ‘nag screen’ for every driver that isn’t signed, there
is really no way they could know that your devices are all related. If they
only nagged once for a bus, then only one unsigned driver for one PCI device
would get a pop-up even if every PCI driver in the box was unsigned, follow?
That just isn’t doable. The solution is, get the driver signed before you
send it to customers. That is the whole idea BTW.
–
Bill McKenzie
“Allan Smith” wrote in message news:xxxxx@ntdev…
>
> I can see why they would make this the general case and signed drivers
have
> definite Software Quality plusses, but it would be nice if they only
> displayed the Nag screen once for each driver component during each
install.
> In our case, once for the port driver and once for the bus portion.
>
> Having the signed driver dialogue box come up for every port being
installed
> certainly does not add to a good user experience. In our case this could
be
> repeated 128 times or more. : -(
>
> Allan
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
> Sent: May 3, 2002 11:23 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Signed driver nag screen on multi file driver INF
> installs?
>
> The word I got from Microsoft is that this is the way is supposed to be
for
> unsigned driver. They told me that the only solution is getting the
driver
> signed.
>
> -Evan
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Allan Smith
> > Sent: Friday, May 03, 2002 6:48 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] Signed driver nag screen on multi file driver INF
> > installs?
> >
> >
> > We have a two part INF install that we use to install our multi-port
> > serial boards. One INF is for the board or bus driver and the other part
> > is for the Ports.
> >
> > We make use of cocpyinf to help streamline the installs under XP and
2000,
> > but we have been having problems with the install stopping as it
installs
> > each child serial port, generally to warn about it not being a signed
> > driver. We intend to have this driver signed soon but in the mean time
> > our customers will find being bothered about each child serial port
> > install by the Unsigned Driver Nag screen a less than good user
> > experience.
> >
> > Is there any good way around this?
> >
> > Any insight would be great.
> >
> > Allan
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@attbi.com
> > To unsubscribe send a blank email to %%email.unsub%%
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@connecttech.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
>
Thanks for the feedback. Now with the faster turn around and self testing
of many devices signing a driver before it goes out to any customers might
be doable. In the old days where it could take quite a while, this wasn’t
always practical.
We also beta test before officially singing a driver. For beta testers
getting 100s of these nag screens poses a serious issue.
We don’t want to get into poking around in the registry etc settings to get
around it but I suppose we could give beta testers the instructions on how
to turn off the non signed driver nag temporarily with an explanation. Not
sure if this will work under .NET though.
Allan
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Bill McKenzie
Sent: May 3, 2002 5:26 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
installs?
Well, they have this ‘nag screen’ for every driver that isn’t signed, there
is really no way they could know that your devices are all related. If they
only nagged once for a bus, then only one unsigned driver for one PCI device
would get a pop-up even if every PCI driver in the box was unsigned, follow?
That just isn’t doable. The solution is, get the driver signed before you
send it to customers. That is the whole idea BTW.
–
Bill McKenzie
“Allan Smith” wrote in message news:xxxxx@ntdev…
>
> I can see why they would make this the general case and signed drivers
have
> definite Software Quality plusses, but it would be nice if they only
> displayed the Nag screen once for each driver component during each
install.
> In our case, once for the port driver and once for the bus portion.
>
> Having the signed driver dialogue box come up for every port being
installed
> certainly does not add to a good user experience. In our case this could
be
> repeated 128 times or more. : -(
>
> Allan
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
> Sent: May 3, 2002 11:23 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Signed driver nag screen on multi file driver INF
> installs?
>
> The word I got from Microsoft is that this is the way is supposed to be
for
> unsigned driver. They told me that the only solution is getting the
driver
> signed.
>
> -Evan
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Allan Smith
> > Sent: Friday, May 03, 2002 6:48 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] Signed driver nag screen on multi file driver INF
> > installs?
> >
> >
> > We have a two part INF install that we use to install our multi-port
> > serial boards. One INF is for the board or bus driver and the other part
> > is for the Ports.
> >
> > We make use of cocpyinf to help streamline the installs under XP and
2000,
> > but we have been having problems with the install stopping as it
installs
> > each child serial port, generally to warn about it not being a signed
> > driver. We intend to have this driver signed soon but in the mean time
> > our customers will find being bothered about each child serial port
> > install by the Unsigned Driver Nag screen a less than good user
> > experience.
> >
> > Is there any good way around this?
> >
> > Any insight would be great.
> >
> > Allan
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@attbi.com
> > To unsubscribe send a blank email to %%email.unsub%%
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@connecttech.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
>
—
You are currently subscribed to ntdev as: xxxxx@connecttech.com
To unsubscribe send a blank email to %%email.unsub%%
Hello.
I think you can get from MS signature for your drivers for testing (not for
sale). In this case you can run QA test and then you will need to get real
logo for your drivers in order to sell them.
Regards,
Yan.
----- Original Message -----
From: “Allan Smith”
To: “NT Developers Interest List”
Sent: Monday, May 06, 2002 3:32 PM
Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
installs?
> Thanks for the feedback. Now with the faster turn around and self testing
> of many devices signing a driver before it goes out to any customers might
> be doable. In the old days where it could take quite a while, this wasn’t
> always practical.
>
> We also beta test before officially singing a driver. For beta testers
> getting 100s of these nag screens poses a serious issue.
>
> We don’t want to get into poking around in the registry etc settings to
get
> around it but I suppose we could give beta testers the instructions on how
> to turn off the non signed driver nag temporarily with an explanation.
Not
> sure if this will work under .NET though.
>
> Allan
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill McKenzie
> Sent: May 3, 2002 5:26 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
> installs?
>
> Well, they have this ‘nag screen’ for every driver that isn’t signed,
there
> is really no way they could know that your devices are all related. If
they
> only nagged once for a bus, then only one unsigned driver for one PCI
device
> would get a pop-up even if every PCI driver in the box was unsigned,
follow?
> That just isn’t doable. The solution is, get the driver signed before you
> send it to customers. That is the whole idea BTW.
>
> –
> Bill McKenzie
>
>
>
> “Allan Smith” wrote in message news:xxxxx@ntdev…
> >
> > I can see why they would make this the general case and signed drivers
> have
> > definite Software Quality plusses, but it would be nice if they only
> > displayed the Nag screen once for each driver component during each
> install.
> > In our case, once for the port driver and once for the bus portion.
> >
> > Having the signed driver dialogue box come up for every port being
> installed
> > certainly does not add to a good user experience. In our case this
could
> be
> > repeated 128 times or more. : -(
> >
> > Allan
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
> > Sent: May 3, 2002 11:23 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] RE: Signed driver nag screen on multi file driver INF
> > installs?
> >
> > The word I got from Microsoft is that this is the way is supposed to be
> for
> > unsigned driver. They told me that the only solution is getting the
> driver
> > signed.
> >
> > -Evan
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of Allan Smith
> > > Sent: Friday, May 03, 2002 6:48 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Signed driver nag screen on multi file driver INF
> > > installs?
> > >
> > >
> > > We have a two part INF install that we use to install our multi-port
> > > serial boards. One INF is for the board or bus driver and the other
part
> > > is for the Ports.
> > >
> > > We make use of cocpyinf to help streamline the installs under XP and
> 2000,
> > > but we have been having problems with the install stopping as it
> installs
> > > each child serial port, generally to warn about it not being a signed
> > > driver. We intend to have this driver signed soon but in the mean time
> > > our customers will find being bothered about each child serial port
> > > install by the Unsigned Driver Nag screen a less than good user
> > > experience.
> > >
> > > Is there any good way around this?
> > >
> > > Any insight would be great.
> > >
> > > Allan
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@attbi.com
> > > To unsubscribe send a blank email to %%email.unsub%%
> > >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@connecttech.com
> > To unsubscribe send a blank email to %%email.unsub%%
> >
> >
> >
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@connecttech.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@smlink.com
> To unsubscribe send a blank email to %%email.unsub%%
The devils advocate says:
Maybe one could have a co-installer for the bus-driver. This
co-installer would install a windows-hook ( maybe hidden app). The
hook code hides/dismiss the ‘nag-screen’. But this is sure more
fiddling than using some registry entry.
| Norbert Kawulski | mailto:xxxxx@stollmann.de |
| Stollmann E+V GmbH, Development | http://www.stollmann.de |
–If it’s ISDN or Bluetooth, make sure it’s driven by Stollmann–
“When you cease to dream you cease to live. - Malcom S. Forbes”
From what I know, a test signed driver needs to be installed on a machine
specifically set up as a test sign machine and will not work in general for
any machine.
Allan
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Yan Vugenfirer
Sent: May 6, 2002 11:19 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
installs?
Hello.
I think you can get from MS signature for your drivers for testing (not for
sale). In this case you can run QA test and then you will need to get real
logo for your drivers in order to sell them.
Regards,
Yan.
----- Original Message -----
From: “Allan Smith”
To: “NT Developers Interest List”
Sent: Monday, May 06, 2002 3:32 PM
Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
installs?
> Thanks for the feedback. Now with the faster turn around and self testing
> of many devices signing a driver before it goes out to any customers might
> be doable. In the old days where it could take quite a while, this wasn’t
> always practical.
>
> We also beta test before officially singing a driver. For beta testers
> getting 100s of these nag screens poses a serious issue.
>
> We don’t want to get into poking around in the registry etc settings to
get
> around it but I suppose we could give beta testers the instructions on how
> to turn off the non signed driver nag temporarily with an explanation.
Not
> sure if this will work under .NET though.
>
> Allan
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill McKenzie
> Sent: May 3, 2002 5:26 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
> installs?
>
> Well, they have this ‘nag screen’ for every driver that isn’t signed,
there
> is really no way they could know that your devices are all related. If
they
> only nagged once for a bus, then only one unsigned driver for one PCI
device
> would get a pop-up even if every PCI driver in the box was unsigned,
follow?
> That just isn’t doable. The solution is, get the driver signed before you
> send it to customers. That is the whole idea BTW.
>
> –
> Bill McKenzie
>
>
>
> “Allan Smith” wrote in message news:xxxxx@ntdev…
> >
> > I can see why they would make this the general case and signed drivers
> have
> > definite Software Quality plusses, but it would be nice if they only
> > displayed the Nag screen once for each driver component during each
> install.
> > In our case, once for the port driver and once for the bus portion.
> >
> > Having the signed driver dialogue box come up for every port being
> installed
> > certainly does not add to a good user experience. In our case this
could
> be
> > repeated 128 times or more. : -(
> >
> > Allan
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
> > Sent: May 3, 2002 11:23 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] RE: Signed driver nag screen on multi file driver INF
> > installs?
> >
> > The word I got from Microsoft is that this is the way is supposed to be
> for
> > unsigned driver. They told me that the only solution is getting the
> driver
> > signed.
> >
> > -Evan
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of Allan Smith
> > > Sent: Friday, May 03, 2002 6:48 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Signed driver nag screen on multi file driver INF
> > > installs?
> > >
> > >
> > > We have a two part INF install that we use to install our multi-port
> > > serial boards. One INF is for the board or bus driver and the other
part
> > > is for the Ports.
> > >
> > > We make use of cocpyinf to help streamline the installs under XP and
> 2000,
> > > but we have been having problems with the install stopping as it
> installs
> > > each child serial port, generally to warn about it not being a signed
> > > driver. We intend to have this driver signed soon but in the mean time
> > > our customers will find being bothered about each child serial port
> > > install by the Unsigned Driver Nag screen a less than good user
> > > experience.
> > >
> > > Is there any good way around this?
> > >
> > > Any insight would be great.
> > >
> > > Allan
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@attbi.com
> > > To unsubscribe send a blank email to %%email.unsub%%
> > >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@connecttech.com
> > To unsubscribe send a blank email to %%email.unsub%%
> >
> >
> >
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@connecttech.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@smlink.com
> To unsubscribe send a blank email to %%email.unsub%%
—
You are currently subscribed to ntdev as: xxxxx@connecttech.com
To unsubscribe send a blank email to %%email.unsub%%
Yes the co-installer route is a possibility, but it is so much easier to
just use the standard INF install method. I am wondering if we use the
install software first method using a simple setup.exe program (like in
toastpkg) if this would get around the nag screens?
I have not had a chance to check this yet.
Allan
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Norbert Kawulski
Sent: May 6, 2002 10:15 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
installs?
The devils advocate says:
Maybe one could have a co-installer for the bus-driver. This
co-installer would install a windows-hook ( maybe hidden app). The
hook code hides/dismiss the ‘nag-screen’. But this is sure more
fiddling than using some registry entry.
| Norbert Kawulski | mailto:xxxxx@stollmann.de |
| Stollmann E+V GmbH, Development | http://www.stollmann.de |
–If it’s ISDN or Bluetooth, make sure it’s driven by Stollmann–
“When you cease to dream you cease to live. - Malcom S. Forbes”
You are currently subscribed to ntdev as: xxxxx@connecttech.com
To unsubscribe send a blank email to %%email.unsub%%
If you’re just worried about your testers you don’t need to have them do any
registry spelunking, just have them use the supplied interface.
Control Panel->System->Hardware->Driver Signing and pick Ignore.
-scott
----- Original Message -----
From: “Allan Smith”
To: “NT Developers Interest List”
Sent: Monday, May 06, 2002 10:58 AM
Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
installs?
> >From what I know, a test signed driver needs to be installed on a machine
> specifically set up as a test sign machine and will not work in general
for
> any machine.
>
> Allan
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Yan Vugenfirer
> Sent: May 6, 2002 11:19 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
> installs?
>
> Hello.
>
> I think you can get from MS signature for your drivers for testing (not
for
> sale). In this case you can run QA test and then you will need to get real
> logo for your drivers in order to sell them.
>
> Regards,
> Yan.
>
> ----- Original Message -----
> From: “Allan Smith”
> To: “NT Developers Interest List”
> Sent: Monday, May 06, 2002 3:32 PM
> Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
> installs?
>
>
> > Thanks for the feedback. Now with the faster turn around and self
testing
> > of many devices signing a driver before it goes out to any customers
might
> > be doable. In the old days where it could take quite a while, this
wasn’t
> > always practical.
> >
> > We also beta test before officially singing a driver. For beta testers
> > getting 100s of these nag screens poses a serious issue.
> >
> > We don’t want to get into poking around in the registry etc settings to
> get
> > around it but I suppose we could give beta testers the instructions on
how
> > to turn off the non signed driver nag temporarily with an explanation.
> Not
> > sure if this will work under .NET though.
> >
> > Allan
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Bill McKenzie
> > Sent: May 3, 2002 5:26 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
> > installs?
> >
> > Well, they have this ‘nag screen’ for every driver that isn’t signed,
> there
> > is really no way they could know that your devices are all related. If
> they
> > only nagged once for a bus, then only one unsigned driver for one PCI
> device
> > would get a pop-up even if every PCI driver in the box was unsigned,
> follow?
> > That just isn’t doable. The solution is, get the driver signed before
you
> > send it to customers. That is the whole idea BTW.
> >
> > –
> > Bill McKenzie
> >
> >
> >
> > “Allan Smith” wrote in message news:xxxxx@ntdev…
> > >
> > > I can see why they would make this the general case and signed drivers
> > have
> > > definite Software Quality plusses, but it would be nice if they only
> > > displayed the Nag screen once for each driver component during each
> > install.
> > > In our case, once for the port driver and once for the bus portion.
> > >
> > > Having the signed driver dialogue box come up for every port being
> > installed
> > > certainly does not add to a good user experience. In our case this
> could
> > be
> > > repeated 128 times or more. : -(
> > >
> > > Allan
> > >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
> > > Sent: May 3, 2002 11:23 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] RE: Signed driver nag screen on multi file driver INF
> > > installs?
> > >
> > > The word I got from Microsoft is that this is the way is supposed to
be
> > for
> > > unsigned driver. They told me that the only solution is getting the
> > driver
> > > signed.
> > >
> > > -Evan
> > >
> > > > -----Original Message-----
> > > > From: xxxxx@lists.osr.com
> > > > [mailto:xxxxx@lists.osr.com]On Behalf Of Allan Smith
> > > > Sent: Friday, May 03, 2002 6:48 AM
> > > > To: NT Developers Interest List
> > > > Subject: [ntdev] Signed driver nag screen on multi file driver INF
> > > > installs?
> > > >
> > > >
> > > > We have a two part INF install that we use to install our multi-port
> > > > serial boards. One INF is for the board or bus driver and the other
> part
> > > > is for the Ports.
> > > >
> > > > We make use of cocpyinf to help streamline the installs under XP and
> > 2000,
> > > > but we have been having problems with the install stopping as it
> > installs
> > > > each child serial port, generally to warn about it not being a
signed
> > > > driver. We intend to have this driver signed soon but in the mean
time
> > > > our customers will find being bothered about each child serial port
> > > > install by the Unsigned Driver Nag screen a less than good user
> > > > experience.
> > > >
> > > > Is there any good way around this?
> > > >
> > > > Any insight would be great.
> > > >
> > > > Allan
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as: xxxxx@attbi.com
> > > > To unsubscribe send a blank email to %%email.unsub%%
> > > >
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@connecttech.com
> > > To unsubscribe send a blank email to %%email.unsub%%
> > >
> > >
> > >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@connecttech.com
> > To unsubscribe send a blank email to %%email.unsub%%
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@smlink.com
> > To unsubscribe send a blank email to %%email.unsub%%
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@connecttech.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@handsfreenetworks.com
> To unsubscribe send a blank email to %%email.unsub%%
>
You still will get the “nag” screen in XP.
----- Original Message -----
From: “Allan Smith”
To: “NT Developers Interest List”
Sent: Monday, May 06, 2002 5:00 PM
Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
installs?
> Yes the co-installer route is a possibility, but it is so much easier to
> just use the standard INF install method. I am wondering if we use the
> install software first method using a simple setup.exe program (like in
> toastpkg) if this would get around the nag screens?
>
> I have not had a chance to check this yet.
>
> Allan
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Norbert Kawulski
> Sent: May 6, 2002 10:15 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
> installs?
>
> The devils advocate says:
> Maybe one could have a co-installer for the bus-driver. This
> co-installer would install a windows-hook ( maybe hidden app). The
> hook code hides/dismiss the ‘nag-screen’. But this is sure more
> fiddling than using some registry entry.
>
>
> -----------------------------------------------------------------
> | Norbert Kawulski | mailto:xxxxx@stollmann.de |
> | Stollmann E+V GmbH, Development | http://www.stollmann.de |
> --If it’s ISDN or Bluetooth, make sure it’s driven by Stollmann–
>
> “When you cease to dream you cease to live. - Malcom S. Forbes”
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@connecttech.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@smlink.com
> To unsubscribe send a blank email to %%email.unsub%%
If you distribute your binary outside of your company, the intention is that
this binary should be signed. That is the binary should never go out
without being signed even for beta testing. Not saying I agree with this
necessarily, but that certainly is the intention the way I read it. And
honestly, once you beta something and send out the binaries, who knows where
those binaries might end up? I would want them signed. Well, I would want
them signed if I truly felt that showed a base level of testing. But, I am
not stating my opinion on that one way or another 
–
Bill McKenzie
“Allan Smith” wrote in message news:xxxxx@ntdev…
>
> From what I know, a test signed driver needs to be installed on a machine
> specifically set up as a test sign machine and will not work in general
for
> any machine.
>
> Allan
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Yan Vugenfirer
> Sent: May 6, 2002 11:19 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
> installs?
>
> Hello.
>
> I think you can get from MS signature for your drivers for testing (not
for
> sale). In this case you can run QA test and then you will need to get real
> logo for your drivers in order to sell them.
>
> Regards,
> Yan.
>
> ----- Original Message -----
> From: “Allan Smith”
> To: “NT Developers Interest List”
> Sent: Monday, May 06, 2002 3:32 PM
> Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
> installs?
>
>
> > Thanks for the feedback. Now with the faster turn around and self
testing
> > of many devices signing a driver before it goes out to any customers
might
> > be doable. In the old days where it could take quite a while, this
wasn’t
> > always practical.
> >
> > We also beta test before officially singing a driver. For beta testers
> > getting 100s of these nag screens poses a serious issue.
> >
> > We don’t want to get into poking around in the registry etc settings to
> get
> > around it but I suppose we could give beta testers the instructions on
how
> > to turn off the non signed driver nag temporarily with an explanation.
> Not
> > sure if this will work under .NET though.
> >
> > Allan
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Bill McKenzie
> > Sent: May 3, 2002 5:26 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Signed driver nag screen on multi file driver INF
> > installs?
> >
> > Well, they have this ‘nag screen’ for every driver that isn’t signed,
> there
> > is really no way they could know that your devices are all related. If
> they
> > only nagged once for a bus, then only one unsigned driver for one PCI
> device
> > would get a pop-up even if every PCI driver in the box was unsigned,
> follow?
> > That just isn’t doable. The solution is, get the driver signed before
you
> > send it to customers. That is the whole idea BTW.
> >
> > –
> > Bill McKenzie
> >
> >
> >
> > “Allan Smith” wrote in message news:xxxxx@ntdev…
> > >
> > > I can see why they would make this the general case and signed drivers
> > have
> > > definite Software Quality plusses, but it would be nice if they only
> > > displayed the Nag screen once for each driver component during each
> > install.
> > > In our case, once for the port driver and once for the bus portion.
> > >
> > > Having the signed driver dialogue box come up for every port being
> > installed
> > > certainly does not add to a good user experience. In our case this
> could
> > be
> > > repeated 128 times or more. : -(
> > >
> > > Allan
> > >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
> > > Sent: May 3, 2002 11:23 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] RE: Signed driver nag screen on multi file driver INF
> > > installs?
> > >
> > > The word I got from Microsoft is that this is the way is supposed to
be
> > for
> > > unsigned driver. They told me that the only solution is getting the
> > driver
> > > signed.
> > >
> > > -Evan
> > >
> > > > -----Original Message-----
> > > > From: xxxxx@lists.osr.com
> > > > [mailto:xxxxx@lists.osr.com]On Behalf Of Allan Smith
> > > > Sent: Friday, May 03, 2002 6:48 AM
> > > > To: NT Developers Interest List
> > > > Subject: [ntdev] Signed driver nag screen on multi file driver INF
> > > > installs?
> > > >
> > > >
> > > > We have a two part INF install that we use to install our multi-port
> > > > serial boards. One INF is for the board or bus driver and the other
> part
> > > > is for the Ports.
> > > >
> > > > We make use of cocpyinf to help streamline the installs under XP and
> > 2000,
> > > > but we have been having problems with the install stopping as it
> > installs
> > > > each child serial port, generally to warn about it not being a
signed
> > > > driver. We intend to have this driver signed soon but in the mean
time
> > > > our customers will find being bothered about each child serial port
> > > > install by the Unsigned Driver Nag screen a less than good user
> > > > experience.
> > > >
> > > > Is there any good way around this?
> > > >
> > > > Any insight would be great.
> > > >
> > > > Allan
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as: xxxxx@attbi.com
> > > > To unsubscribe send a blank email to %%email.unsub%%
> > > >
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@connecttech.com
> > > To unsubscribe send a blank email to %%email.unsub%%
> > >
> > >
> > >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@connecttech.com
> > To unsubscribe send a blank email to %%email.unsub%%
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@smlink.com
> > To unsubscribe send a blank email to %%email.unsub%%
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@connecttech.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
>