set driver signing to ignore but this didn’t work…
Thanks in advance!
And you had WinDbg connected with a valid connection between host and
target? Or did you simply set the boot option to disable driver signature
enforcement? If it’s the latter, you have to do that EVERY time you boot. If
you used “bcdedit” to set test signing, you MUST have a host/target
connection using KD/WinDbg.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Thursday, May 20, 2010 2:37 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to disable the whql warning for silent installation of
non whql driver on xp?
set driver signing to ignore but this didn’t work…
Thanks in advance!
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
__________ Information from ESET Smart Security, version of virus signature
database 5130 (20100519) __________
The message was checked by ESET Smart Security.
__________ Information from ESET Smart Security, version of virus signature
database 5130 (20100519) __________
The message was checked by ESET Smart Security.
I don’t believe that you need to have a kd session established to use testsigning; you do need one to load unsigned drivers (unless you want to do the F8 thing).
He’s also using XP, so this isn’t his problem.
x86_32 or x86_64?
mm
If you have set test signing via the bcdedit command you must have a kd
session connected on the host. I’m using it now and if I have not started
WinDbg and connected the target to the host, my driver gets the warning
dialogue.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@evitechnology.com
Sent: Thursday, May 20, 2010 10:24 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] How to disable the whql warning for silent installation
of non whql driver on xp?
I don’t believe that you need to have a kd session established to use
testsigning; you do need one to load unsigned drivers (unless you want to do
the F8 thing).
He’s also using XP, so this isn’t his problem.
x86_32 or x86_64?
mm
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
__________ Information from ESET Smart Security, version of virus signature
database 5132 (20100520) __________
The message was checked by ESET Smart Security.
__________ Information from ESET Smart Security, version of virus signature
database 5132 (20100520) __________
The message was checked by ESET Smart Security.
My bad - I didn’t realize that you were talking about the dialog box; I have no knowledge of that.
mm
You can use local test signing on vista/win7, install a test cert, and turn
test signing on using bcdedit and you do not need a debugger attached.
However, wasn’t the OP asking about XP?
Mark Roddy
On Thu, May 20, 2010 at 12:55 PM, Gary G. Little wrote:
> If you have set test signing via the bcdedit command you must have a kd
> session connected on the host. I’m using it now and if I have not started
> WinDbg and connected the target to the host, my driver gets the warning
> dialogue.
>
> Gary G. Little
> H (952) 223-1349
> C (952) 454-4629
> xxxxx@comcast.net
>
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@evitechnology.com
> Sent: Thursday, May 20, 2010 10:24 AM
> To: Windows System Software Devs Interest List
> Subject: RE:[ntdev] How to disable the whql warning for silent installation
> of non whql driver on xp?
>
> I don’t believe that you need to have a kd session established to use
> testsigning; you do need one to load unsigned drivers (unless you want to
> do
> the F8 thing).
>
> He’s also using XP, so this isn’t his problem.
>
> x86_32 or x86_64?
>
>
>
> mm
>
> —
> 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
>
>
> Information from ESET Smart Security, version of virus signature
> database 5132 (20100520)
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>
> Information from ESET Smart Security, version of virus signature
> database 5132 (20100520)
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>
> —
> 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 everyone for reply. Yes, I’m using a 32bit XP system. It’s not attached to any debugger and just pulls driver from a server every night and install and run some tests. The process is unattended. The whql warning diag window stops the whole process. I set the action to ignore in system property -> hardware tab -> driver signing -> ignore and this does not work.
>
Thanks everyone for reply. Yes, I’m using a 32bit XP system. It’s not
attached
to any debugger and just pulls driver from a server every night and
install
and run some tests. The process is unattended. The whql warning diag
window
stops the whole process. I set the action to ignore in system property
->
hardware tab -> driver signing -> ignore and this does not work.
It’s a bit curious… this link
http://www.mydigitallife.info/2007/12/07/disable-unsigned-driver-install
ation-dialog-prompt-in-windows-xp/ suggests going just what you did, but
I’ve never seen it work before either. I assume you clicked the “Make
this action the system default” checkbox.
James