.kdfiles and boot start and 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.

.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

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill McKenzie
Sent: Thursday, April 19, 2007 3:22 PM
To: Kernel Debugging Interest List
Subject: [windbg] .kdfiles and boot start and 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.


You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Much thanks Doron! I was still beating my head against this one…saved me
a bruise or two.

Btw, I am guessing “.sxe ld:blah.sys” doesn’t work either at boot start
time?

Bill M.

“Doron Holan” wrote in message
news:xxxxx@windbg…
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

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill McKenzie
Sent: Thursday, April 19, 2007 3:22 PM
To: Kernel Debugging Interest List
Subject: [windbg] .kdfiles and boot start and 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.


You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

I don’t know whether it is possible or not. However, based on some of
the replies from certain ops, I would say that the safe assumption is
that it no one who knows is going to say, for whatever reason.

>> xxxxx@sbcglobal.net 2007-04-19 18:22 >>>
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.


You are currently subscribed to windbg as: xxxxx@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Don’t know, but I would trust your empirical evidence. OTOH, while the
boot loader loaded the image, it has not yet called into the image’s
entry point yet, so if you have the symbols, you can set a bp on
blah!DriverEntry or use the PDRIVER_OBJECT to find the entrypoint’s
address

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill McKenzie
Sent: Thursday, April 19, 2007 4:24 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] .kdfiles and boot start and Vista

Much thanks Doron! I was still beating my head against this
one…saved me
a bruise or two.

Btw, I am guessing “.sxe ld:blah.sys” doesn’t work either at boot start
time?

Bill M.

“Doron Holan” wrote in message
news:xxxxx@windbg…
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

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill McKenzie
Sent: Thursday, April 19, 2007 3:22 PM
To: Kernel Debugging Interest List
Subject: [windbg] .kdfiles and boot start and 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.


You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

>OTOH, while the

boot loader loaded the image, it has not yet called into the image’s
entry point yet

Yeah I noticed that.

if you have the symbols, you can set a bp on
blah!DriverEntry or use the PDRIVER_OBJECT to find the entrypoint’s
address

Actually I tried that and I could not get the debugger to break at
DriverEntry even though the breakpoint seemed to be resolved okay by WinDbg.
DbgBreakPoint() never fails :frowning:

Can you guys fix that too :slight_smile:

Thanks for the information!

Bill M.

“Doron Holan” wrote in message
news:xxxxx@windbg…
Don’t know, but I would trust your empirical evidence. OTOH, while the
boot loader loaded the image, it has not yet called into the image’s
entry point yet, so if you have the symbols, you can set a bp on
blah!DriverEntry or use the PDRIVER_OBJECT to find the entrypoint’s
address

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill McKenzie
Sent: Thursday, April 19, 2007 4:24 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] .kdfiles and boot start and Vista

Much thanks Doron! I was still beating my head against this
one…saved me
a bruise or two.

Btw, I am guessing “.sxe ld:blah.sys” doesn’t work either at boot start
time?

Bill M.

“Doron Holan” wrote in message
news:xxxxx@windbg…
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

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill McKenzie
Sent: Thursday, April 19, 2007 3:22 PM
To: Kernel Debugging Interest List
Subject: [windbg] .kdfiles and boot start and 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.


You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com