RE: Problems using .kdfiles to replace boot time dri vers

I am fairly sure that the serial connection is good - I’ve been using this
configuration for ~ a year with no communication problems. I have not tried
.kdfiles with any other drivers – the ones I am interested in debugging are
all boot time hence my excitement at finding a way of doing this (although
it is painfully slow even at 115KB).

I’m interested in your comment about disabling legacy USB – unfortunately
this is not possible since the system only has USB for kb/mouse. Can you
elaborate as to why this might be a problem?

/simgr

-----Original Message-----
From: David Holcomb [mailto:xxxxx@microsoft.com]
Sent: Monday, May 26, 2003 10:23 PM
To: Kernel Debugging Interest List

Our developer suggests you try to verify your serial connection is 100%
reliable and legacy USB support is disabled in your BIOS.

I am curious if this only happens in the very special case of your boot
driver. Otherwise do you have any problems with debugging this target
in kernel mode? Or have you tried .kdfiles with any other driver
(non-boot driver or other boot driver)?

You also might want to see if it repros on another machine with your
same boot driver loaded. If it repros on another machine too (hopefully
different hardware and also with legacy USB support disabled), it would
seem more likely that there is a problem with the special boot loader or
the debugger.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Graham, Simon
Sent: Thursday, May 22, 2003 10:40 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Problems using .kdfiles to replace boot time dri
vers

Sorry - should have included that;
. 3790 on the target
. XP-SP1 on the windbg host
. windbg 6.2.7.4.
. The debug version of the NTLDR I am using is from the 3790 DDK.

/simgr

-----Original Message-----
From: David Holcomb [mailto:xxxxx@microsoft.com]
Sent: Thursday, May 22, 2003 1:31 PM
To: Kernel Debugging Interest List

What OS is this happening with, and what version of the debugger?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Graham, Simon
Sent: Thursday, May 22, 2003 9:42 AM
To: Kernel Debugging Interest List
Subject: [windbg] Problems using .kdfiles to replace boot time drivers

I recently discovered the article on the OSR web page indicating that
replacement of boot time drivers is indeed possible and then found the
text in the new windbg help indicating how to do this - however, I’m
still having problems getting it to work - wondering if anyone has any
suggestions.

The problem I am getting is that the replacement fails part way through
downloading the new driver; for example:

KD: Accessing ‘c:\testsymbols\sraio.sys’
(\WINNT\system32\DRIVERS\sraio.sys)
File size
51K…



…BdPullRemoteFile:
BdReadRemoteFile failed! (c000000d)

I also get c00000011 (end of file). I know this file is OK because I
have since copied it manually to the target and it loads/runs just fine.

/simgr


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@stratus.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


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