Checked kernel and HAL included with Win8 WDK

NTDEV
1

Unless I’m completely missing something obvious here (and I could be, it’s
been a long week), the checked kernel and hal files located in C:\Program
Files (x86)\Windows Kits\8.0\Debug\Win8 are UNSIGNED (that is, they do not
have a Microsoft signature). As a sanity check I looked back at the Win7
checked kernel and hal files in the Win7 WDK and I see that they are signed.
I also checked the original kernel and hal that were installed with Win8,
and they are signed. But the Win8 versions in the Win8 WDK are not signed.

Of course, before I checked the signatures (or lack thereof) on these files,
I tried using them for an alternative Win8 boot configuration so that I
could test with the checked kernel and hal, and when I tried to boot with
those files, my system immediately reset and came back up into the seemingly
unstoppable “attempting repairs” process.

Am I completely missing something here, or was this a HUGE oversight on the
part of Microsoft?

I assume that the checked kernel and hal included with the actual complete
checked build of the OS will be signed, but as we all know, it’s not obvious
how to extract them from the ISO image without simply installing the whole
thing on a separate system just for the sake of copying the kernel and hal
files.

  • Jay
2

Oh, this gets more interesting. So I burn a DVD of the Win8 x64 checked
build ISO and attempt to install it (using the same machine where the retail
build of Win8 is installed, just swapping hard drives, as I have a removable
hard drive bay in that particular system). The DVD loads stuff for a minute
or two, and then I get an unhappy face saying there was a problem and the
system restarts. I got the same result after numerous attempts. Are the
files in the checked build ISO image also not signed, and is that why the
checked build install fails?

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jay Talbott
Sent: Friday, August 17, 2012 6:15 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Checked kernel and HAL included with Win8 WDK

Unless I’m completely missing something obvious here (and I could be, it’s
been a long week), the checked kernel and hal files located in C:\Program
Files (x86)\Windows Kits\8.0\Debug\Win8 are UNSIGNED (that is, they do not
have a Microsoft signature). As a sanity check I looked back at the Win7
checked kernel and hal files in the Win7 WDK and I see that they are signed.
I also checked the original kernel and hal that were installed with Win8,
and they are signed. But the Win8 versions in the Win8 WDK are not signed.

Of course, before I checked the signatures (or lack thereof) on these files,
I tried using them for an alternative Win8 boot configuration so that I
could test with the checked kernel and hal, and when I tried to boot with
those files, my system immediately reset and came back up into the seemingly
unstoppable “attempting repairs” process.

Am I completely missing something here, or was this a HUGE oversight on the
part of Microsoft?

I assume that the checked kernel and hal included with the actual complete
checked build of the OS will be signed, but as we all know, it’s not obvious
how to extract them from the ISO image without simply installing the whole
thing on a separate system just for the sake of copying the kernel and hal
files.

  • Jay

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

3

I have no idea, but I have a couple of thoughts.

1.) With the partial checked build, enable debugging, bootdebugging and
bootmgr debugging. Attach a debugger to all three (just use the same
setting for each and it will do it automatically), and enable the earliest
breakpoint you can.

When it breaks in:

X {bootmgr|winload|nt}!_*_Mask

Set each one to 0xFF

See if the traces help

2.) Just something to consider - historically there have been pretty
frequently problems with installing CHK builds.

I don’t know if setup debugging works anymore, so I’d look at (1) first, if
you’re interested.

I also gather that the boot process has changed too. Something about
having to disable hibernation or something like that. Not sure. GIYF here.

Good luck,

Mm
On Aug 17, 2012 7:40 PM, “Jay Talbott” wrote:

> Oh, this gets more interesting. So I burn a DVD of the Win8 x64 checked
> build ISO and attempt to install it (using the same machine where the
> retail build of Win8 is installed, just swapping hard drives, as I have a
> removable hard drive bay in that particular system). The DVD loads stuff
> for a minute or two, and then I get an unhappy face saying there was a
> problem and the system restarts. I got the same result after numerous
> attempts. Are the files in the checked build ISO image also not signed, and
> is that why the checked build install fails?
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] On Behalf Of Jay Talbott
> Sent: Friday, August 17, 2012 6:15 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Checked kernel and HAL included with Win8 WDK
>
> ****
>
> Unless I?m completely missing something obvious here (and I could be, it?s
> been a long week), the checked kernel and hal files located in C:\Program
> Files (x86)\Windows Kits\8.0\Debug\Win8 are UNSIGNED (that is, they do not
> have a Microsoft signature). As a sanity check I looked back at the Win7
> checked kernel and hal files in the Win7 WDK and I see that they are
> signed. I also checked the original kernel and hal that were installed with
> Win8, and they are signed. But the Win8 versions in the Win8 WDK are not
> signed.
>
> **
>
> Of course, before I checked the signatures (or lack thereof) on these
> files, I tried using them for an alternative Win8 boot configuration so
> that I could test with the checked kernel and hal, and when I tried to boot
> with those files, my system immediately reset and came back up into the
> seemingly unstoppable ?attempting repairs? process.
>
> ****
>
> Am I completely missing something here, or was this a HUGE oversight on
> the part of Microsoft?
>
>
>
> I assume that the checked kernel and hal included with the actual complete
> checked build of the OS will be signed, but as we all know, it?s not
> obvious how to extract them from the ISO image without simply installing
> the whole thing on a separate system just for the sake of copying the
> kernel and hal files.
>
> ****
>
> - Jay
>
>
>
>
> —
> 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
>

4

WITH the debugger attached and boot debug enabled?

Just checking…

Peter
OSR

5

Usually the symptom of constantly trying to boot, then you might is some thing like this " :slight_smile: " without the quote is that by default Memory dumping is not configured properly. So I would is to have an (1) install of Win8 off of the RTM, it should work (2) set the dump configuration as per your choice (3) Use an admin priv’ed cmd line to create the necessary BCD entries, hence debug boot. (4) Assuming that the checked build of hal and ntoskrnl.exe are already extracted and given by MSFT, replace those in place…

Now get the client WINDBG started, ALT+CNTL + K ( i think) to make the debugger break at the earliest load…

Reboot the target…

Should be able to break in !!!

-pro

On Aug 17, 2012, at 7:39 PM, Jay Talbott wrote:

Oh, this gets more interesting. So I burn a DVD of the Win8 x64 checked build ISO and attempt to install it (using the same machine where the retail build of Win8 is installed, just swapping hard drives, as I have a removable hard drive bay in that particular system). The DVD loads stuff for a minute or two, and then I get an unhappy face saying there was a problem and the system restarts. I got the same result after numerous attempts. Are the files in the checked build ISO image also not signed, and is that why the checked build install fails?

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Jay Talbott
Sent: Friday, August 17, 2012 6:15 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Checked kernel and HAL included with Win8 WDK

Unless I?m completely missing something obvious here (and I could be, it?s been a long week), the checked kernel and hal files located in C:\Program Files (x86)\Windows Kits\8.0\Debug\Win8 are UNSIGNED (that is, they do not have a Microsoft signature). As a sanity check I looked back at the Win7 checked kernel and hal files in the Win7 WDK and I see that they are signed. I also checked the original kernel and hal that were installed with Win8, and they are signed. But the Win8 versions in the Win8 WDK are not signed.

Of course, before I checked the signatures (or lack thereof) on these files, I tried using them for an alternative Win8 boot configuration so that I could test with the checked kernel and hal, and when I tried to boot with those files, my system immediately reset and came back up into the seemingly unstoppable ?attempting repairs? process.

Am I completely missing something here, or was this a HUGE oversight on the part of Microsoft?

I assume that the checked kernel and hal included with the actual complete checked build of the OS will be signed, but as we all know, it?s not obvious how to extract them from the ISO image without simply installing the whole thing on a separate system just for the sake of copying the kernel and hal files.

  • Jay

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 athttp://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

6

My strategy for installed the checked build on a system that it doesn’t easily install on is:

  1. Boot non-checked WinPE (If you don’t have WinPE 4.0 and WinPE 3.x fails to install Win 8, it MIGHT work to boot a non-checked OS install disk, hit shift-F10 to get a command window, change the DVD, and run the checked OS setup program from the command window)

  2. Run the OS install app on the checked DVD

  3. BEFORE the first boot, from WinPE, run BCDEDIT and set whatever debugger parameters you want

  4. Boot the target OS and use the debugger to skip asserts

The Win 7 checked build frequently would assert in the ACPI driver early in the boot. The checked DVD unfortunately uses the checked OS for the install, so things fail before you even get a chance to install the OS. Once you figure out which driver asserts, you can replace ONLY that driver with the non-checked on, or else always boot with the debugger attached.

Jan

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Friday, August 17, 2012 8:23 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Checked kernel and HAL included with Win8 WDK

Usually the symptom of constantly trying to boot, then you might is some thing like this " :slight_smile: " without the quote is that by default Memory dumping is not configured properly. So I would is to have an (1) install of Win8 off of the RTM, it should work (2) set the dump configuration as per your choice (3) Use an admin priv’ed cmd line to create the necessary BCD entries, hence debug boot. (4) Assuming that the checked build of hal and ntoskrnl.exe are already extracted and given by MSFT, replace those in place…

Now get the client WINDBG started, ALT+CNTL + K ( i think) to make the debugger break at the earliest load…

Reboot the target…

Should be able to break in !!!

-pro

On Aug 17, 2012, at 7:39 PM, Jay Talbott wrote:

Oh, this gets more interesting. So I burn a DVD of the Win8 x64 checked build ISO and attempt to install it (using the same machine where the retail build of Win8 is installed, just swapping hard drives, as I have a removable hard drive bay in that particular system). The DVD loads stuff for a minute or two, and then I get an unhappy face saying there was a problem and the system restarts. I got the same result after numerous attempts. Are the files in the checked build ISO image also not signed, and is that why the checked build install fails?

From: xxxxx@lists.osr.commailto:xxxxx [mailto:xxxxx@lists.osr.com]mailto: On Behalf Of Jay Talbott
Sent: Friday, August 17, 2012 6:15 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Checked kernel and HAL included with Win8 WDK

Unless I’m completely missing something obvious here (and I could be, it’s been a long week), the checked kernel and hal files located in C:\Program Files (x86)\Windows Kits\8.0\Debug\Win8 are UNSIGNED (that is, they do not have a Microsoft signature). As a sanity check I looked back at the Win7 checked kernel and hal files in the Win7 WDK and I see that they are signed. I also checked the original kernel and hal that were installed with Win8, and they are signed. But the Win8 versions in the Win8 WDK are not signed.

Of course, before I checked the signatures (or lack thereof) on these files, I tried using them for an alternative Win8 boot configuration so that I could test with the checked kernel and hal, and when I tried to boot with those files, my system immediately reset and came back up into the seemingly unstoppable “attempting repairs” process.

Am I completely missing something here, or was this a HUGE oversight on the part of Microsoft?

I assume that the checked kernel and hal included with the actual complete checked build of the OS will be signed, but as we all know, it’s not obvious how to extract them from the ISO image without simply installing the whole thing on a separate system just for the sake of copying the kernel and hal files.

- Jay

—
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 athttp://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:></mailto:xxxxx>

7

Ok, I’ll first confess that last week was a long frustrating week, so I
probably wasn’t thinking things through as well as I should have been at the
time. It wasn’t dawning on me that as long as the debugger was hooked up, I
should be able to boot with unsigned components, including the kernel and
HAL. I guess I figured since the checked kernel and HAL had been signed in
prior releases that they always had to be signed, debugger or not. My bad.

That being said, yes, the boot configuration for booting with the checked
build was definitely configured for debug, and I’m almost 100% certain
(although I am now questioning myself) that the debugger was also running.

I had been doing some Win8 driver debugging using the retail kernel when I
decided to switch to the checked kernel and hal. I copied the boot entry for
the regular boot that already had the debugger settings specified and just
modified it for the checked components and verified that it also had
debugging enabled. When I booted I got a selection of which boot option that
I want to boot with that comes up during the boot cycle, albeit much later
in the process than it used to be. If I selected the original (retail)
option, it completes the boot and everything works fine. If I selected the
checked build option, the system immediately reset (no crash dump, no
nothing - it just immediately went back to the BIOS startup screen).

Also, even if there was some sort of operator error involved here, what
explains why I couldn’t get the full checked build to install from the DVD I
burned to a fresh blank hard drive in the same machine where the retail
build installed correctly?

I will give it all a go again today now that my mind is fresh…

  • Jay

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-511107-
xxxxx@lists.osr.com] On Behalf Of xxxxx@osr.com
Sent: Friday, August 17, 2012 8:08 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Checked kernel and HAL included with Win8 WDK

WITH the debugger attached and boot debug enabled?

Just checking…

Peter
OSR

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

8

Jay,

On the full install, are you getting an ASSERT? There is an ASSERT in
the ACPI driver that has hit me on every system I have used (Dell, HP,
and others) since Windows XP. You basically have to install with the
debugger set up, to get the checked build on the system. I haven’t
researched how that is done for Win8, but for Win7 they documented it
pretty well.

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“Jay Talbott” wrote in message
news:xxxxx@ntdev:

> Ok, I’ll first confess that last week was a long frustrating week, so I
> probably wasn’t thinking things through as well as I should have been at the
> time. It wasn’t dawning on me that as long as the debugger was hooked up, I
> should be able to boot with unsigned components, including the kernel and
> HAL. I guess I figured since the checked kernel and HAL had been signed in
> prior releases that they always had to be signed, debugger or not. My bad.
>
> That being said, yes, the boot configuration for booting with the checked
> build was definitely configured for debug, and I’m almost 100% certain
> (although I am now questioning myself) that the debugger was also running.
>
> I had been doing some Win8 driver debugging using the retail kernel when I
> decided to switch to the checked kernel and hal. I copied the boot entry for
> the regular boot that already had the debugger settings specified and just
> modified it for the checked components and verified that it also had
> debugging enabled. When I booted I got a selection of which boot option that
> I want to boot with that comes up during the boot cycle, albeit much later
> in the process than it used to be. If I selected the original (retail)
> option, it completes the boot and everything works fine. If I selected the
> checked build option, the system immediately reset (no crash dump, no
> nothing - it just immediately went back to the BIOS startup screen).
>
> Also, even if there was some sort of operator error involved here, what
> explains why I couldn’t get the full checked build to install from the DVD I
> burned to a fresh blank hard drive in the same machine where the retail
> build installed correctly?
>
> I will give it all a go again today now that my mind is fresh…
>
> - Jay
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com [mailto:bounce-511107-
> > xxxxx@lists.osr.com] On Behalf Of xxxxx@osr.com
> > Sent: Friday, August 17, 2012 8:08 PM
> > To: Windows System Software Devs Interest List
> > Subject: RE:[ntdev] Checked kernel and HAL included with Win8 WDK
> >
> >


> >
> > WITH the debugger attached and boot debug enabled?
> >
> > Just checking…
> >
> > Peter
> > OSR
> >
> >
> > —
> > 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

9

I have been running with the checked x64 kernel and HAL from the WDK with no
problem, so it’s not fundamentally broken in my experience. You are correct
though that they are unsigned, which is different from previous kit
releases.

That being said, yes, the boot configuration for booting with the checked
build was definitely configured for debug, and I’m almost 100% certain
(although I am now questioning myself) that the debugger was also running.

Are you also sure that boot debugging was enabled? Note that this is an
independent step from enabling debug:

bcdedit /set bootdebug on

This has been a required step for loading unsigned boot start drivers for
quite a while. With this option enabled, you should see this warning printed
out in the debugger during boot:

*** Windows is unable to verify the signature of
the file \Windows\system32\ntoskrnl.chk. It will be allowed to load
because the boot debugger is enabled.
*** Windows is unable to verify the signature of
the file \Windows\system32\hal.chk. It will be allowed to load
because the boot debugger is enabled.

-scott

–
Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Jay Talbott” wrote in message news:xxxxx@ntdev…

Ok, I’ll first confess that last week was a long frustrating week, so I
probably wasn’t thinking things through as well as I should have been at the
time. It wasn’t dawning on me that as long as the debugger was hooked up, I
should be able to boot with unsigned components, including the kernel and
HAL. I guess I figured since the checked kernel and HAL had been signed in
prior releases that they always had to be signed, debugger or not. My bad.

That being said, yes, the boot configuration for booting with the checked
build was definitely configured for debug, and I’m almost 100% certain
(although I am now questioning myself) that the debugger was also running.

I had been doing some Win8 driver debugging using the retail kernel when I
decided to switch to the checked kernel and hal. I copied the boot entry for
the regular boot that already had the debugger settings specified and just
modified it for the checked components and verified that it also had
debugging enabled. When I booted I got a selection of which boot option that
I want to boot with that comes up during the boot cycle, albeit much later
in the process than it used to be. If I selected the original (retail)
option, it completes the boot and everything works fine. If I selected the
checked build option, the system immediately reset (no crash dump, no
nothing - it just immediately went back to the BIOS startup screen).

Also, even if there was some sort of operator error involved here, what
explains why I couldn’t get the full checked build to install from the DVD I
burned to a fresh blank hard drive in the same machine where the retail
build installed correctly?

I will give it all a go again today now that my mind is fresh…

  • Jay

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-511107-
xxxxx@lists.osr.com] On Behalf Of xxxxx@osr.com
Sent: Friday, August 17, 2012 8:08 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Checked kernel and HAL included with Win8 WDK

WITH the debugger attached and boot debug enabled?

Just checking…

Peter
OSR

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

10

I don’t know for sure what I wasn’t doing right on Friday, but I finally got
it working earlier this morning and, ultimately, I think I’ve solved the
problem that I was trying to resolve.

Thanks to everybody who contributed to my brain finally doing all the right
things to make it work.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-511258-
xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Monday, August 20, 2012 8:53 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Checked kernel and HAL included with Win8 WDK

I have been running with the checked x64 kernel and HAL from the WDK with
no
problem, so it’s not fundamentally broken in my experience. You are
correct
though that they are unsigned, which is different from previous kit
releases.

>That being said, yes, the boot configuration for booting with the checked
>build was definitely configured for debug, and I’m almost 100% certain
>(although I am now questioning myself) that the debugger was also
running.

Are you also sure that boot debugging was enabled? Note that this is an
independent step from enabling debug:

bcdedit /set bootdebug on

This has been a required step for loading unsigned boot start drivers for
quite a while. With this option enabled, you should see this warning
printed
out in the debugger during boot:

*** Windows is unable to verify the signature of
the file \Windows\system32\ntoskrnl.chk. It will be allowed to load
because the boot debugger is enabled.
*** Windows is unable to verify the signature of
the file \Windows\system32\hal.chk. It will be allowed to load
because the boot debugger is enabled.

-scott

–
Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Jay Talbott” wrote in message news:xxxxx@ntdev…

Ok, I’ll first confess that last week was a long frustrating week, so I
probably wasn’t thinking things through as well as I should have been at
the
time. It wasn’t dawning on me that as long as the debugger was hooked up,
I
should be able to boot with unsigned components, including the kernel and
HAL. I guess I figured since the checked kernel and HAL had been signed in
prior releases that they always had to be signed, debugger or not. My bad.

That being said, yes, the boot configuration for booting with the checked
build was definitely configured for debug, and I’m almost 100% certain
(although I am now questioning myself) that the debugger was also running.

I had been doing some Win8 driver debugging using the retail kernel when I
decided to switch to the checked kernel and hal. I copied the boot entry
for
the regular boot that already had the debugger settings specified and just
modified it for the checked components and verified that it also had
debugging enabled. When I booted I got a selection of which boot option
that
I want to boot with that comes up during the boot cycle, albeit much later
in the process than it used to be. If I selected the original (retail)
option, it completes the boot and everything works fine. If I selected the
checked build option, the system immediately reset (no crash dump, no
nothing - it just immediately went back to the BIOS startup screen).

Also, even if there was some sort of operator error involved here, what
explains why I couldn’t get the full checked build to install from the DVD
I
burned to a fresh blank hard drive in the same machine where the retail
build installed correctly?

I will give it all a go again today now that my mind is fresh…

  • Jay

> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:bounce-511107-
> xxxxx@lists.osr.com] On Behalf Of xxxxx@osr.com
> Sent: Friday, August 17, 2012 8:08 PM
> To: Windows System Software Devs Interest List
> Subject: RE:[ntdev] Checked kernel and HAL included with Win8 WDK
>
> [quote]
> I tried using them for an alternative Win8 boot configuration
> [/quote]
>
> WITH the debugger attached and boot debug enabled?
>
> Just checking…
>
> Peter
> OSR
>
>
> —
> 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