.kdfiles with boot start drivers on Vista

Anyone been able to use .kdfiles -m in WinDbg with boot start drivers on
Vista? After much wailing and gnashing of teeth I am thinking it can't be
done. Anyone?

I have seen some posts on this but they all either go no where or the people
replying didn't read very well.

Here is what I have tried. I tried using bcdedit to turn on the boot
debugger. Here is my output from WinDbg:

Waiting to reconnect...
BD: Boot Debugger Initialized
Connected to Windows Boot Debugger 6000 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is:

From the kd prompt I set >sxe ld:mydriver.sys and the debugger promptly
broke after all of the boot start drivers had been loaded?? The .kdfiles
mapping to my driver never kicked.

I am connecting WinDbg via NULL modem cable COM1 115200 baud.

I also tried loading a checked build of WinLoad.exe...still no love.

I can't seem to get the debugger to hook during boot.

HELP? Anyone? I have seen several veteran driver devs ask this same
question with no real help. If it isn't possible, it would be nice of
someone to just say so. In my case this would sure save me a butt-load of
time.

Thanks.

Bill M.

Bill
Fri Apr 20 10:50:57 CDT 2007

For anyone interested, I posted this same question to OSR's windbg list and
got this response from Doron Holan at Microsoft:

>kdfiles for boot start drivers does not work with the new Vista loader.
>We hope to add it back in the next client release of Windows.
>
>d

Bill M.

"Bill McKenzie" <bkmckenzie@sbcglobal.net> wrote in message
news:u6mTd7sgHHA.3412@TK2MSFTNGP02.phx.gbl...
> Anyone been able to use .kdfiles -m in WinDbg with boot start drivers on
> Vista? After much wailing and gnashing of teeth I am thinking it can't be
> done. Anyone?
>
> I have seen some posts on this but they all either go no where or the
> people replying didn't read very well.
>
> Here is what I have tried. I tried using bcdedit to turn on the boot
> debugger. Here is my output from WinDbg:
>
> Waiting to reconnect...
> BD: Boot Debugger Initialized
> Connected to Windows Boot Debugger 6000 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established.
> Symbol search path is:
>
> From the kd prompt I set >sxe ld:mydriver.sys and the debugger promptly
> broke after all of the boot start drivers had been loaded?? The .kdfiles
> mapping to my driver never kicked.
>
> I am connecting WinDbg via NULL modem cable COM1 115200 baud.
>
> I also tried loading a checked build of WinLoad.exe...still no love.
>
> I can't seem to get the debugger to hook during boot.
>
> HELP? Anyone? I have seen several veteran driver devs ask this same
> question with no real help. If it isn't possible, it would be nice of
> someone to just say so. In my case this would sure save me a butt-load of
> time.
>
> Thanks.
>
> Bill M.
>

Mark
Sun Apr 22 16:22:18 CDT 2007

On Fri, 20 Apr 2007 10:50:57 -0500, "Bill McKenzie"
<bkmckenzie@sbcglobal.net> wrote:

>For anyone interested, I posted this same question to OSR's windbg list and
>got this response from Doron Holan at Microsoft:
>
>>kdfiles for boot start drivers does not work with the new Vista loader.
>>We hope to add it back in the next client release of Windows.
>>
>>d
>
>Bill M.
>

I'm not 100% convinced that the mechanism provided for boot start
.kdfiles is reliable for any version of the os. Last time I tried it
was just an 'ntldr corrupt' event.

>"Bill McKenzie" <bkmckenzie@sbcglobal.net> wrote in message
>news:u6mTd7sgHHA.3412@TK2MSFTNGP02.phx.gbl...
>> Anyone been able to use .kdfiles -m in WinDbg with boot start drivers on
>> Vista? After much wailing and gnashing of teeth I am thinking it can't be
>> done. Anyone?
>>
>> I have seen some posts on this but they all either go no where or the
>> people replying didn't read very well.
>>
>> Here is what I have tried. I tried using bcdedit to turn on the boot
>> debugger. Here is my output from WinDbg:
>>
>> Waiting to reconnect...
>> BD: Boot Debugger Initialized
>> Connected to Windows Boot Debugger 6000 x86 compatible target, ptr64 FALSE
>> Kernel Debugger connection established.
>> Symbol search path is:
>>
>> From the kd prompt I set >sxe ld:mydriver.sys and the debugger promptly
>> broke after all of the boot start drivers had been loaded?? The .kdfiles
>> mapping to my driver never kicked.
>>
>> I am connecting WinDbg via NULL modem cable COM1 115200 baud.
>>
>> I also tried loading a checked build of WinLoad.exe...still no love.
>>
>> I can't seem to get the debugger to hook during boot.
>>
>> HELP? Anyone? I have seen several veteran driver devs ask this same
>> question with no real help. If it isn't possible, it would be nice of
>> someone to just say so. In my case this would sure save me a butt-load of
>> time.
>>
>> Thanks.
>>
>> Bill M.
>>
>


=====================
Mark Roddy DDK MVP
Windows Vista/2003/XP Consulting
Device and Filesystem Drivers
Broken Driver Code? Call us.
Hollis Technology Solutions 603-321-1032
www.hollistech.com

Bill
Sun Apr 22 20:08:55 CDT 2007

That's a bummer...it sure is a useful feature and would be MUCH more useful
for boot start drivers.

Bill M.

"Mark Roddy" <markr@hollistech.com> wrote in message
news:9dkn235gka2sv9qn4feka6h49c4u9j6d89@4ax.com...
> On Fri, 20 Apr 2007 10:50:57 -0500, "Bill McKenzie"
> <bkmckenzie@sbcglobal.net> wrote:
>
>>For anyone interested, I posted this same question to OSR's windbg list
>>and
>>got this response from Doron Holan at Microsoft:
>>
>>>kdfiles for boot start drivers does not work with the new Vista loader.
>>>We hope to add it back in the next client release of Windows.
>>>
>>>d
>>
>>Bill M.
>>
>
> I'm not 100% convinced that the mechanism provided for boot start
> .kdfiles is reliable for any version of the os. Last time I tried it
> was just an 'ntldr corrupt' event.
>
>>"Bill McKenzie" <bkmckenzie@sbcglobal.net> wrote in message
>>news:u6mTd7sgHHA.3412@TK2MSFTNGP02.phx.gbl...
>>> Anyone been able to use .kdfiles -m in WinDbg with boot start drivers
>>> on
>>> Vista? After much wailing and gnashing of teeth I am thinking it can't
>>> be
>>> done. Anyone?
>>>
>>> I have seen some posts on this but they all either go no where or the
>>> people replying didn't read very well.
>>>
>>> Here is what I have tried. I tried using bcdedit to turn on the boot
>>> debugger. Here is my output from WinDbg:
>>>
>>> Waiting to reconnect...
>>> BD: Boot Debugger Initialized
>>> Connected to Windows Boot Debugger 6000 x86 compatible target, ptr64
>>> FALSE
>>> Kernel Debugger connection established.
>>> Symbol search path is:
>>>
>>> From the kd prompt I set >sxe ld:mydriver.sys and the debugger promptly
>>> broke after all of the boot start drivers had been loaded?? The
>>> .kdfiles
>>> mapping to my driver never kicked.
>>>
>>> I am connecting WinDbg via NULL modem cable COM1 115200 baud.
>>>
>>> I also tried loading a checked build of WinLoad.exe...still no love.
>>>
>>> I can't seem to get the debugger to hook during boot.
>>>
>>> HELP? Anyone? I have seen several veteran driver devs ask this same
>>> question with no real help. If it isn't possible, it would be nice of
>>> someone to just say so. In my case this would sure save me a butt-load
>>> of
>>> time.
>>>
>>> Thanks.
>>>
>>> Bill M.
>>>
>>
>
>
> =====================
> Mark Roddy DDK MVP
> Windows Vista/2003/XP Consulting
> Device and Filesystem Drivers
> Broken Driver Code? Call us.
> Hollis Technology Solutions 603-321-1032
> www.hollistech.com