.kdfiles doesn't work on boot

Observed on various versions of WinDbg and WinXP:

  1. “.kdfiles c:\mydrv\mymap.ini”
  2. Install the driver with a bug
  3. Hit a bugcheck
  4. “.reboot”
  5. On reboot, the debugger prints the size of mydrv.sys, but fails to
    transfer it to the target machine - never prints any dots.

The same works fine when disabling/enabling the device in the DevMgr

mymap.ini

map
system32\drivers\mydrv.sys
c:\mydrv\objchk_w2k_x86\i386\mydrv.sys
map
\Systemroot\system32\drivers\mydrv.sys
c:\mydrv\objchk_w2k_x86\i386\mydrv.sys

I’ve seen this happening everytime the driver on the target machine is
write protected. Remove the write protection and everything worked fine
for me.

Robin Mitra

Ivan Bublikov wrote:

Observed on various versions of WinDbg and WinXP:

  1. “.kdfiles c:\mydrv\mymap.ini”
  2. Install the driver with a bug
  3. Hit a bugcheck
  4. “.reboot”
  5. On reboot, the debugger prints the size of mydrv.sys, but fails to
    transfer it to the target machine - never prints any dots.

The same works fine when disabling/enabling the device in the DevMgr

mymap.ini

map
system32\drivers\mydrv.sys
c:\mydrv\objchk_w2k_x86\i386\mydrv.sys
map
\Systemroot\system32\drivers\mydrv.sys
c:\mydrv\objchk_w2k_x86\i386\mydrv.sys

We’ve also see this with anti-virus software, generally. Or anything
that would hold the file open, prohibiting a copy to occur.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Robin Mitra
Sent: Monday, April 18, 2005 2:13 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] .kdfiles doesn’t work on boot

I’ve seen this happening everytime the driver on the target machine is
write protected. Remove the write protection and everything worked fine
for me.

Robin Mitra

Ivan Bublikov wrote:

Observed on various versions of WinDbg and WinXP:

  1. “.kdfiles c:\mydrv\mymap.ini”
  2. Install the driver with a bug
  3. Hit a bugcheck
  4. “.reboot”
  5. On reboot, the debugger prints the size of mydrv.sys, but fails to
    transfer it to the target machine - never prints any dots.

The same works fine when disabling/enabling the device in the DevMgr

mymap.ini

map
system32\drivers\mydrv.sys
c:\mydrv\objchk_w2k_x86\i386\mydrv.sys
map
\Systemroot\system32\drivers\mydrv.sys
c:\mydrv\objchk_w2k_x86\i386\mydrv.sys


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

The target machine has no antivirus, and mydrv.sys isn’t write-ptotected.

“Jason Shay” wrote in message
news:xxxxx@windbg…
We’ve also see this with anti-virus software, generally. Or anything
that would hold the file open, prohibiting a copy to occur.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Robin Mitra
Sent: Monday, April 18, 2005 2:13 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] .kdfiles doesn’t work on boot

I’ve seen this happening everytime the driver on the target machine is
write protected. Remove the write protection and everything worked fine
for me.

Robin Mitra

Ivan Bublikov wrote:
> Observed on various versions of WinDbg and WinXP:
>
> 1. “.kdfiles c:\mydrv\mymap.ini”
> 2. Install the driver with a bug
> 3. Hit a bugcheck
> 3. “.reboot”
> 4. On reboot, the debugger prints the size of mydrv.sys, but fails to
> transfer it to the target machine - never prints any dots.
>
> The same works fine when disabling/enabling the device in the DevMgr
>
>
> mymap.ini
> -------------
> map
> system32\drivers\mydrv.sys
> c:\mydrv\objchk_w2k_x86\i386\mydrv.sys
> map
> \Systemroot\system32\drivers\mydrv.sys
> c:\mydrv\objchk_w2k_x86\i386\mydrv.sys
>
>


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

.kdfiles will not work for boot drivers (like acpi.sys, disk.sys etc.). In
order to use it with these drivers you have to install a special version of
NTLDR. Search for “Replacing Boot Drivers” in WinDbg help.

Gregory

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ivan Bublikov
Sent: Wednesday, April 20, 2005 10:01 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] .kdfiles doesn’t work on boot

The target machine has no antivirus, and mydrv.sys isn’t write-ptotected.

“Jason Shay” wrote in message
news:xxxxx@windbg…
We’ve also see this with anti-virus software, generally. Or anything that
would hold the file open, prohibiting a copy to occur.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Robin Mitra
Sent: Monday, April 18, 2005 2:13 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] .kdfiles doesn’t work on boot

I’ve seen this happening everytime the driver on the target machine is write
protected. Remove the write protection and everything worked fine for me.

Robin Mitra

Ivan Bublikov wrote:
> Observed on various versions of WinDbg and WinXP:
>
> 1. “.kdfiles c:\mydrv\mymap.ini”
> 2. Install the driver with a bug
> 3. Hit a bugcheck
> 3. “.reboot”
> 4. On reboot, the debugger prints the size of mydrv.sys, but fails to
> transfer it to the target machine - never prints any dots.
>
> The same works fine when disabling/enabling the device in the DevMgr
>
>
> mymap.ini
> -------------
> map
> system32\drivers\mydrv.sys
> c:\mydrv\objchk_w2k_x86\i386\mydrv.sys
> map
> \Systemroot\system32\drivers\mydrv.sys
> c:\mydrv\objchk_w2k_x86\i386\mydrv.sys
>
>


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


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