Re:Target system jerky with Windbg connected over USB-to-serial adapter. Also, driver mappi

WINDBG
1

I believe that:

  1. The path must exactly match the ImagePath value in the registry;
    that is, character for character (I'm not sure about case) - i. e. -
    %SystemRoot%\System32\Drivers\MYDRIVER.SYS will not match any of the
    forms that would probably be equivalent in any other situation: i. e. -
    System32\Drivers\MYDRIVER.SYS; C:\Windows\System32\Drivers\MYDRIVER.SYS,
    \Windows\System32\Drivers\MYDRIVER.SYS, et. c.

The easiest thing to do is just do an lml, find the entry for your
driver, and copy and paste it (or something like that).

  1. Although I do not know, given the above (which is documented), I'm
    dubious that the whole map file mechanism handles paths with spaces
    correctly; there are other WinDbg commands that definitely do not. I
    think that any of the spaces, the double quotes, or the 8.3 notation
    (assuming that generation of such names has not been disabled) name
    would be likely to cause a failed string match.

  2. While as long as your driver is not a boot driver, "Program Files"
    should be OK, at least for the time being, I would just move your
    driver, assuming that is an option. The 8.3 name restriction on boot
    drivers is documented, but I'd swear I've seen some violate this.

mm

>> xxxxx@steadingsoftware.com 2006-10-17 12:20 >>>
2) I found out about the magical variable _NT_KD_FILES that tells the
target system to
load your local driver instead of the one on the target. The document
says the map file
should be in the form:

map
\Systemroot\system32\drivers\mydriver.sys
e:\development\mydriver\objchk_wnet_x86\i386\mydriver.sys

This doesn't work for me. Our driver on the target machine loads to a
location in Program Files\Common Files - is it because of >spaces in the
name? I tried putting it in quotes, as well as using 8.3 names like
PROGRA~1, no luck.

you might want to check what the ImagePath value is in the registry. I
have observed problems with paths of the sort

%SystemRoot%\system32\Drivers\mydriver.sys

but I find that changing it to

system32\Drivers\mydriver.sys

makes everything work...

Rod

You are currently subscribed to windbg as: unknown lmsubst tag
argument: ''
To unsubscribe send a blank email to xxxxx@lists.osr.com