Hi,
Are there any command line options to devcon to be a little more verbose
than:
devcon failed.
when attempting to test install new drivers?
When I was using XP, a \windows\setupapi.log file was created/modified
during such installs. I don’t seem to have such a log on Windows 7.
How do I debug installation of new drivers?
Thanks,
-PWM
There should be a log of this type. Providing the exact version and
bit-ness of the Windows 7 may help. If 64-bit make sure you are looking
with the 64-bit Windows Explorer running as Administrator. I have found
that even on 32-bit Win7 you can’t copy memory.dmp from the windows
directory without admin privileges.
“Peter W. Morreale” wrote in message
news:xxxxx@ntdev…
>
>
> Hi,
>
> Are there any command line options to devcon to be a little more verbose
> than:
>
> devcon failed.
>
>
> when attempting to test install new drivers?
>
> When I was using XP, a \windows\setupapi.log file was created/modified
> during such installs. I don’t seem to have such a log on Windows 7.
>
> How do I debug installation of new drivers?
>
> Thanks,
> -PWM
>
>
http://blogs.msdn.com/doronh/archive/2006/08/31/734412.aspx
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Peter W. Morreale
Sent: Sunday, November 15, 2009 8:51 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] devcon logs?
Hi,
Are there any command line options to devcon to be a little more verbose
than:
devcon failed.
when attempting to test install new drivers?
When I was using XP, a \windows\setupapi.log file was created/modified
during such installs. I don’t seem to have such a log on Windows 7.
How do I debug installation of new drivers?
Thanks,
-PWM
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
On Sun, 2009-11-15 at 21:02 -0800, David Craig wrote:
There should be a log of this type. Providing the exact version and
bit-ness of the Windows 7 may help. If 64-bit make sure you are looking
with the 64-bit Windows Explorer running as Administrator. I have found
that even on 32-bit Win7 you can’t copy memory.dmp from the windows
directory without admin privileges.
Right, probably should be. But there isn’t. 
I am a newbie to Windows. How can I find out what bits I am running?
Best I can find is “control-panel”->“system” which tells me “Windows 7
Enterprise”. (activated)
It is 64bit.
THanks,
-PWM
“Peter W. Morreale” wrote in message
> news:xxxxx@ntdev…
> >
> >
> > Hi,
> >
> > Are there any command line options to devcon to be a little more verbose
> > than:
> >
> > devcon failed.
> >
> >
> > when attempting to test install new drivers?
> >
> > When I was using XP, a \windows\setupapi.log file was created/modified
> > during such installs. I don’t seem to have such a log on Windows 7.
> >
> > How do I debug installation of new drivers?
> >
> > Thanks,
> > -PWM
> >
> >
>
>
>
> —
> 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
On Mon, 2009-11-16 at 06:02 +0000, Doron Holan wrote:
Thanks for this. However I still do not have a \windows\setupapi.log
file.
The current registry DWORD for LOG_LEVEL is 0xc8004040, which LogControl
(as well as http://msdn.microsoft.com/en-us/library/ms791349.aspx )
tells me is verbose, w/timestamps, and writes to log file as well as
debugger.
Rebooted several times, (and attempted devcon install/update(s)) no log
file. Am I looking in the wrong location?
This is new Win7 install, w/ updates, and the 7600.16385 driver kit, 4
+GiB of free space. It is a 64bit install. I do not know how to find
the precise release/version of my bits.
Pretty sure the only setting(s) I have changed are to add paths to the
Path env var.
Thanks,
-PWM
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Peter W. Morreale
Sent: Sunday, November 15, 2009 8:51 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] devcon logs?Hi,
Are there any command line options to devcon to be a little more verbose
than:devcon failed.
when attempting to test install new drivers?
When I was using XP, a \windows\setupapi.log file was created/modified
during such installs. I don’t seem to have such a log on Windows 7.How do I debug installation of new drivers?
Thanks,
-PWM
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminarsTo 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/seminarsTo unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
That is enough information. What are you using to ‘look’ for the setup
logs? I repeat, 64-bit versions of Windows need 64-bit ‘Explorer’ type
programs or other factors come into play that will hide the files.
However, your previous posts told you why your driver won’t load. 64-bit
and no signature == no load, never, not going to happen. F8 and windbg can
be used to get it to load, but must be used on each boot.
Maybe you should begin with the 32-bit versions first. You can sign 32-bit
drivers - sys and/or cat, but it is not required.
“Peter W. Morreale” wrote in message
news:xxxxx@ntdev…
> On Sun, 2009-11-15 at 21:02 -0800, David Craig wrote:
>> There should be a log of this type. Providing the exact version and
>> bit-ness of the Windows 7 may help. If 64-bit make sure you are looking
>> with the 64-bit Windows Explorer running as Administrator. I have found
>> that even on 32-bit Win7 you can’t copy memory.dmp from the windows
>> directory without admin privileges.
>>
>
> Right, probably should be. But there isn’t.
>
> I am a newbie to Windows. How can I find out what bits I am running?
>
> Best I can find is “control-panel”->“system” which tells me “Windows 7
> Enterprise”. (activated)
>
> It is 64bit.
>
>
> THanks,
> -PWM
>
>
>> “Peter W. Morreale” wrote in message
>> news:xxxxx@ntdev…
>> >
>> >
>> > Hi,
>> >
>> > Are there any command line options to devcon to be a little more
>> > verbose
>> > than:
>> >
>> > devcon failed.
>> >
>> >
>> > when attempting to test install new drivers?
>> >
>> > When I was using XP, a \windows\setupapi.log file was created/modified
>> > during such installs. I don’t seem to have such a log on Windows 7.
>> >
>> > How do I debug installation of new drivers?
>> >
>> > Thanks,
>> > -PWM
>> >
>> >
>>
>>
>>
>> —
>> 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
>
>
> When I was using XP, a \windows\setupapi.log file was created/modified
during such installs. I don’t seem to have such a log on Windows 7.
Correct. They changed the names.
Search for “*.log” files in your Windows installation directory.
My Win7/32 finds names like “setupact.log”, “setuperr.log”,
“DPINST.log”, “WindowsUpdate.log”, “setupapi.app.log”,
“setupapi.dev.log”. (Win7/64 should use the same names.)
Warning: some of these names can be found multiple times, use the most
current ones (=the ones from the “correct” path).
On Mon, 2009-11-16 at 09:32 -0800, David Craig wrote:
That is enough information. What are you using to ‘look’ for the setup
logs? I repeat, 64-bit versions of Windows need 64-bit ‘Explorer’ type
programs or other factors come into play that will hide the files.
Thanks for the reply.
What I was using to ‘look’ for the log files was a ‘Checked build’ cmd
window with:
% dir c:\windows*log
I do not find setupapi.log, nor the wdf log files that Doron’s blog
references. The above was sufficient on XP (where I first started) but
obviously is not correct for 64bit W7.
I also looked using computer->local disk->windows and the log files do
not exist either.
I’m unsure whether I am using 64-bit ‘Explorer’ type programs or not.
However, your previous posts told you why your driver won’t load. 64-bit
and no signature == no load, never, not going to happen. F8 and windbg can
be used to get it to load, but must be used on each boot.
My understanding was that devcon did not require a signed driver for
test installs. Apparently this changed with Win7? Or is it possibly
because I had used a 32-bit XP install first?
Can I use the ‘test’ signing sample .bat script to create a catalog
file?
Maybe you should begin with the 32-bit versions first. You can sign 32-bit
drivers - sys and/or cat, but it is not required.
I would be *elated* to begin with 32bit, if I knew how. Quite frankly,
I would run 16bit if I could make some progress. 
Is that an option during OS install?
I am using the Win 7 x86 Checked Build Environment for building.
Apparently this is defaulting to 64-bit (since the emulated CPU is
64bit)
Looking at the env vars in the checked build cmd window, I see that
USERPROFILE is defined to C:\Users\Pete, so is it safe to assume that I
am not running as the admin? How do I run as the admin?
I apologize for all these stupid questions. I’m doing the best I can
at the moment and deeply appreciate all the help.
Thanks,
-PWM
“Peter W. Morreale” wrote in message
> news:xxxxx@ntdev…
> > On Sun, 2009-11-15 at 21:02 -0800, David Craig wrote:
> >> There should be a log of this type. Providing the exact version and
> >> bit-ness of the Windows 7 may help. If 64-bit make sure you are looking
> >> with the 64-bit Windows Explorer running as Administrator. I have found
> >> that even on 32-bit Win7 you can’t copy memory.dmp from the windows
> >> directory without admin privileges.
> >>
> >
> > Right, probably should be. But there isn’t.
> >
> > I am a newbie to Windows. How can I find out what bits I am running?
> >
> > Best I can find is “control-panel”->“system” which tells me “Windows 7
> > Enterprise”. (activated)
> >
> > It is 64bit.
> >
> >
> > THanks,
> > -PWM
> >
> >
> >> “Peter W. Morreale” wrote in message
> >> news:xxxxx@ntdev…
> >> >
> >> >
> >> > Hi,
> >> >
> >> > Are there any command line options to devcon to be a little more
> >> > verbose
> >> > than:
> >> >
> >> > devcon failed.
> >> >
> >> >
> >> > when attempting to test install new drivers?
> >> >
> >> > When I was using XP, a \windows\setupapi.log file was created/modified
> >> > during such installs. I don’t seem to have such a log on Windows 7.
> >> >
> >> > How do I debug installation of new drivers?
> >> >
> >> > Thanks,
> >> > -PWM
> >> >
> >> >
> >>
> >>
> >>
> >> —
> >> 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
You might want to add a ‘/s’ to that dir command to include subdirs in the search.
Good luck,
mm
Peter W. Morreale wrote:
What I was using to ‘look’ for the log files was a ‘Checked build’ cmd
window with:% dir c:\windows*log
They’ve been moved (as of Vista). If you had done a recursive search:
dir /s c:\windows*.log
you would have found them in c:\windows\inf.
I’m unsure whether I am using 64-bit ‘Explorer’ type programs or not.
If you are on a 64-bit system, then Explorer is a 64-bit program.
My understanding was that devcon did not require a signed driver for
test installs. Apparently this changed with Win7? Or is it possibly
because I had used a 32-bit XP install first?
There are two different signatures at work here. The signature you are
thinking of is the install-time signature. It’s lack merely shows you
the “this driver is unsigned” warning, which you can choose to bypass.
It applies only at install time, to all systems.
The 64-bit systems have an additional requirement, called KMCS –
kernel-mode code signing. This check is done at LOAD time, so even if
you get your driver installed, it will not load unless it is signed, or
unless you bypass the signing by using the F8 boot-time option or
attaching a kernel debugger. You cannot use a test certificate for
this. You must have a valid class 3 code-signing certificate from one
of the short list of vendors that have a “cross-signing certificate”
available.
Can I use the ‘test’ signing sample .bat script to create a catalog
file?
Yes, but it will not help with KMCS. For that, you either need a real
certificate, or a bypass at every boot.
I would be *elated* to begin with 32bit, if I knew how. Quite frankly,
I would run 16bit if I could make some progress.Is that an option during OS install?
It is a separate install image.
I am using the Win 7 x86 Checked Build Environment for building.
Apparently this is defaulting to 64-bit (since the emulated CPU is
64bit)
You really do have some confusion here. Vista and Windows 7 are
available in both 32-bit and 64-bit flavors. They are separate
installation discs. The actual processor is not relevant; what matters
is which flavor of the system you install.
If you are running a 64-bit system, then you MUST build in an x64 build
environment. A 32-bit driver (that is, one built in the x86
environment) will not run on a 64-bit system. The bittedness MUST
match. A 32-bit app will run on 64-bit Windows, but not a driver.
Looking at the env vars in the checked build cmd window, I see that
USERPROFILE is defined to C:\Users\Pete, so is it safe to assume that I
am not running as the admin? How do I run as the admin?
It depends on whether the user “Pete” was created as admin. You can
check this in the Users control panel applet.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Replies inline:
“Peter W. Morreale” wrote in message
news:xxxxx@ntdev…
> On Mon, 2009-11-16 at 09:32 -0800, David Craig wrote:
>> That is enough information. What are you using to ‘look’ for the setup
>> logs? I repeat, 64-bit versions of Windows need 64-bit ‘Explorer’ type
>> programs or other factors come into play that will hide the files.
>>
>
> Thanks for the reply.
>
> What I was using to ‘look’ for the log files was a ‘Checked build’ cmd
> window with:
>
> % dir c:\windows*log
>
Definitely a Unix/Linux background. We normally use *.log, but your syntax
works on XP SP3 32-bit.
> I do not find setupapi.log, nor the wdf log files that Doron’s blog
> references. The above was sufficient on XP (where I first started) but
> obviously is not correct for 64bit W7.
>
> I also looked using computer->local disk->windows and the log files do
> not exist either.
>
> I’m unsure whether I am using 64-bit ‘Explorer’ type programs or not.
>
I don’t have a 64-bit system setup currently, but under Start, All programs,
Accessories, there should be two Windows Explorers. One will say it is
64-bit. I know this to be true on Vista, but maybe it changed under Win7.
>
>
>> However, your previous posts told you why your driver won’t load. 64-bit
>> and no signature == no load, never, not going to happen. F8 and windbg
>> can
>> be used to get it to load, but must be used on each boot.
>>
>
> My understanding was that devcon did not require a signed driver for
> test installs. Apparently this changed with Win7? Or is it possibly
> because I had used a 32-bit XP install first?
>
This is also true for Vista. 64-bit versions of Windows from Vista onward,
REQUIRE a signed driver. Novell should have a Class 3 code signing
certificate and a cross-certificate suitable for that certificate that will
sign and be recognized on any system in the world. Test signing will also
work. I have posted a batch file that works to sign both the cat and sys
files. It also works for 32-bit if you get the inf2cat parameters correct
and my current batch files do handle signing both since I have to release to
QA.
> Can I use the ‘test’ signing sample .bat script to create a catalog
> file?
>
>
>> Maybe you should begin with the 32-bit versions first. You can sign
>> 32-bit
>> drivers - sys and/or cat, but it is not required.
>>
>
> I would be elated to begin with 32bit, if I knew how. Quite frankly,
> I would run 16bit if I could make some progress.
>
Look at hollistech.com and under resources the latest version of
ddkbuild.bat. It will handle allowing you to build which ever target you
want from any editor that can pass parameters. There is a tutorial under an
earlier version that shows how to configure Microsoft’s Visual Studio to use
that batch file. You can, of course, just use the various WDK build
environments and enter ‘BLD’ or ‘build -ceZ’ from your source directory.
Those environments will not place you back in your source tree. NEVER use
the WDK’s src subdirectory to put your files. You don’t want to pollute the
samples.
> Is that an option during OS install?
>
> I am using the Win 7 x86 Checked Build Environment for building.
> Apparently this is defaulting to 64-bit (since the emulated CPU is
> 64bit)
>
> Looking at the env vars in the checked build cmd window, I see that
> USERPROFILE is defined to C:\Users\Pete, so is it safe to assume that I
> am not running as the admin? How do I run as the admin?
>
> I apologize for all these stupid questions. I’m doing the best I can
> at the moment and deeply appreciate all the help.
>
> Thanks,
> -PWM
>
>
>>
>> “Peter W. Morreale” wrote in message
>> news:xxxxx@ntdev…
>> > On Sun, 2009-11-15 at 21:02 -0800, David Craig wrote:
>> >> There should be a log of this type. Providing the exact version and
>> >> bit-ness of the Windows 7 may help. If 64-bit make sure you are
>> >> looking
>> >> with the 64-bit Windows Explorer running as Administrator. I have
>> >> found
>> >> that even on 32-bit Win7 you can’t copy memory.dmp from the windows
>> >> directory without admin privileges.
>> >>
>> >
>> > Right, probably should be. But there isn’t.
>> >
>> > I am a newbie to Windows. How can I find out what bits I am running?
>> >
>> > Best I can find is “control-panel”->“system” which tells me “Windows 7
>> > Enterprise”. (activated)
>> >
>> > It is 64bit.
>> >
>> >
>> > THanks,
>> > -PWM
>> >
>> >
>> >> “Peter W. Morreale” wrote in message
>> >> news:xxxxx@ntdev…
>> >> >
>> >> >
>> >> > Hi,
>> >> >
>> >> > Are there any command line options to devcon to be a little more
>> >> > verbose
>> >> > than:
>> >> >
>> >> > devcon failed.
>> >> >
>> >> >
>> >> > when attempting to test install new drivers?
>> >> >
>> >> > When I was using XP, a \windows\setupapi.log file was
>> >> > created/modified
>> >> > during such installs. I don’t seem to have such a log on Windows 7.
>> >> >
>> >> > How do I debug installation of new drivers?
>> >> >
>> >> > Thanks,
>> >> > -PWM
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> —
>> >> 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
>
>
David Craig wrote:
This is also true for Vista. 64-bit versions of Windows from Vista onward,
REQUIRE a signed driver. Novell should have a Class 3 code signing
certificate and a cross-certificate suitable for that certificate that will
sign and be recognized on any system in the world. Test signing will also
work.
Not for 64-bit KMCS purposes, it won’t. You can satisfy the
install-time signature check with a test signature, but not the
load-time 64-bit KMCS check.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
On Mon, 2009-11-16 at 11:00 -0800, Tim Roberts wrote:
Peter W. Morreale wrote:
…They’ve been moved (as of Vista). If you had done a recursive search:
dir /s c:\windows*.log
you would have found them in c:\windows\inf.
25+ years ago when I was first starting out, I lost out on a job because
I failed the DOS test.
Obviously, the same would hold true for today as well.
You really do have some confusion here.
Yes. And you have no idea how much of that you cleared up with this
post.
I owe you a beer, or 6.
Thanks,
-PWM
On Mon, 2009-11-16 at 12:39 -0800, David Craig wrote:
>
This is also true for Vista. 64-bit versions of Windows from Vista onward,
REQUIRE a signed driver. Novell should have a Class 3 code signing
certificate and a cross-certificate suitable for that certificate that will
sign and be recognized on any system in the world. Test signing will also
work. I have posted a batch file that works to sign both the cat and sys
files. It also works for 32-bit if you get the inf2cat parameters correct
and my current batch files do handle signing both since I have to release to
QA.
Thanks David. Yes, I’m sure that Novell has such a cert. I will
investigate getting a copy.
Will also investigate your ddkbuild script.
Thanks again for the info.
-PWM
Test signatures do work with 64 bit drivers as long as the target system is
in test signing mode and the test cert is installed on the target system.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com]
On Behalf Of Tim Roberts
Sent: Monday, November 16, 2009 4:05 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Re:Re:devcon logs?
David Craig wrote:
This is also true for Vista. 64-bit versions of Windows from Vista
onward, REQUIRE a signed driver. Novell should have a Class 3 code
signing certificate and a cross-certificate suitable for that
certificate that will sign and be recognized on any system in the
world. Test signing will also work.
Not for 64-bit KMCS purposes, it won’t. You can satisfy the install-time
signature check with a test signature, but not the load-time 64-bit KMCS
check.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
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
I don’t know how we do it here, but we have test signing that works for
64-bit drivers to load properly. They may be based upon the real
certificate from Verisign. We also have a cross-certificate from Microsoft
that matches it. Is it the final signatures? I am not sure and another
group handles the final packaging. I know it loads with what I have and it
says it is from Verisign. I just use it and don’t try and figure out how it
all works. I am lucky in that I don’t have to know. From the comments, I
feel for those who have to write the code and then go through all the
hassles to get it signed and working. I think that our test signing may be
based upon a certificate everyone has access to and I have never had to
understand it all.
“Tim Roberts” wrote in message news:xxxxx@ntdev…
> David Craig wrote:
>>
>> This is also true for Vista. 64-bit versions of Windows from Vista
>> onward,
>> REQUIRE a signed driver. Novell should have a Class 3 code signing
>> certificate and a cross-certificate suitable for that certificate that
>> will
>> sign and be recognized on any system in the world. Test signing will
>> also
>> work.
>
> Not for 64-bit KMCS purposes, it won’t. You can satisfy the
> install-time signature check with a test signature, but not the
> load-time 64-bit KMCS check.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
Ddkbuild.bat is used by a lot of people all over the world. Others have
similar batch files to obtain the same results with in some cases additional
processing such as symbol servers, source servers, and signing, including
the creation of cat files. I have batch files that use ddkbuild.bat via a
call and when it returns do the additional processing. We also have other
batch files that are used that do it all without Mark’s batch file. Those
we have to maintain and it takes a while to find all the changes needed to
support a new WDK or even worse, a pre-release of selective header and
library files that have to be merged into a temporary WDK when the new
version has not even been brought to Alpha level. Being inbox can be fun
and a lot of work.
“Peter W. Morreale” wrote in message
news:xxxxx@ntdev…
> On Mon, 2009-11-16 at 12:39 -0800, David Craig wrote:
>
>> >
>> This is also true for Vista. 64-bit versions of Windows from Vista
>> onward,
>> REQUIRE a signed driver. Novell should have a Class 3 code signing
>> certificate and a cross-certificate suitable for that certificate that
>> will
>> sign and be recognized on any system in the world. Test signing will
>> also
>> work. I have posted a batch file that works to sign both the cat and sys
>> files. It also works for 32-bit if you get the inf2cat parameters
>> correct
>> and my current batch files do handle signing both since I have to release
>> to
>> QA.
>
> Thanks David. Yes, I’m sure that Novell has such a cert. I will
> investigate getting a copy.
>
> Will also investigate your ddkbuild script.
>
> Thanks again for the info.
>
> -PWM
>
>
>
>
David Craig wrote:
I don’t know how we do it here, but we have test signing that works for
64-bit drivers to load properly. They may be based upon the real
certificate from Verisign. We also have a cross-certificate from Microsoft
that matches it. Is it the final signatures?
Well, if you have a real code-signing certificate and a
cross-certificate to match it, then you are doing a real KMCS signature,
not a test signature.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
It’s been a while since I last actually set it up, but as I recall, test signing works fine for KMCS purposes, without any real certificates.
mm