Sometime I just want to know how my freaking brain works, really :-).
In a folder that contains a lot of files and sub folders, I often create
folders with numeric prefix, so that those comes first on the list.
With same thing in mind, I had the folder name 1Drivers, and I was trying to
put 1Driver ( trying to be grammatically correct?).
After the initial fixes the file was already in good condition…
But those commands from kd to create a map file is worth every penny 
-pro
On Wed, Jun 3, 2009 at 11:58 AM, Prokash Sinha wrote:
> Looked at the file using gvim, did not find any blank space …
> But you just gave me the ‘ulitimate knife’ … That is the command lines
> … And that works …
>
> Thanks a bunch!
> -pro
>
>
> On Wed, Jun 3, 2009 at 11:24 AM, Scott Noone wrote:
>
>> It looks fine to me, I even pasted it into a text file here and .kdfiles
>> was
>> able to parse it fine:
>>
>> 1: kd> .kdfiles e:\projects\mapfile.ini
>> KD file assocations loaded from ‘e:\projects\mapfile.ini’
>> 1: kd> .kdfiles
>> KD file assocations loaded from ‘e:\projects\mapfile.ini’
>> \SystemRoot\system32\drivers\ndislwf.sys ->
>>
>> \HO64\c\WinDDK\7100.0.0\src\network\ndis\filter\objchk_win7_x86\i386\ndislwf.sys
>>
>> The only thing to check is that you don’t have any extra whitespace hiding
>> in the file itself. For example:
>>
>> # Comment goes here
>>
>> Will cause the parser to fail. Also, something like:
>>
>> map
>>
>> Would cause the parser to fail.
>>
>> You can have .kdfiles generate the file for you if you want, that would
>> remove any doubt:
>>
>> 1: kd> .kdfiles -c
>> KD file associations cleared
>> 1: kd> .kdfiles -m \SystemRoot\system32\drivers\ndislwf.sys
>>
>> \HO64\c\WinDDK\7100.0.0\src\network\ndis\filter\objchk_win7_x86\i386\ndislwf.sys
>> Added mapping for ‘\SystemRoot\system32\drivers\ndislwf.sys’
>> 1: kd> .kdfiles -s c:\map.ini
>> KD file assocations saved to ‘c:\map.ini’
>>
>> -scott
>>
>>
>> –
>> Scott Noone
>> Consulting Associate
>> OSR Open Systems Resources, Inc.
>> http://www.osronline.com
>>
>>
>> “Prokash Sinha” wrote in message news:xxxxx@windbg.
>> …
>> I did incorporate the suggestions and here is the file, now c:\ of the
>> host
>> is on share and visible from the target ( win 7 rc x86)…
>>
>>
>> Still the same thing, hope it’s nothing to do with 8.3 format. I’m using
>> windbg 6.11.0001.402
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> # At Home - Driver Map file - 6/3/2009
>> #
>>
>>
>> # Each driver file replacement is indicated by three lines in the driver
>> replacement map file.
>>
>>
>> # The first line consists of the word “map”.
>> # The second line specifies the path and file name of the old driver on
>> the
>> target computer.
>> # The third line specifies the full path of the new driver. This driver
>> can
>> be located on the host computer or on some other server.
>> # You can repeat this pattern of information any number of times.
>>
>>
>> map
>> \SystemRoot\system32\drivers\ndislwf.sys
>>
>> \HO64\c\WinDDK\7100.0.0\src\network\ndis\filter\objchk_win7_x86\i386\ndislwf.sys
>>
>>
>>
>>
>> On Wed, Jun 3, 2009 at 10:44 AM, Prokash Sinha
>> wrote:
>>
>> Thanks ( as usual ) Tim …
>>
>>
>> I’ve winddk folder shared, but I think you pointed out the \HO64\C.…
>>
>>
>> I had c$ instead of just c…
>>
>>
>> Let me try with that… From the target I know I can see the ~\winddk
>> using
>> explorer …
>>
>>
>> -pro
>>
>>
>>
>> On Wed, Jun 3, 2009 at 10:39 AM, Tim Roberts wrote:
>>
>> Prokash Sinha wrote:
>> > I must have something missing here !.
>> >
>> > This is my map file
>>
>> > …
>>
>> > # ??\c:\windows\system32\ndislwf.sys
>> > map
>> > \systemroot\windows\system32\ndislwf.sys
>> >
>> \HO64\WinDDK\7100.0.0\src\network\ndis\filter\objchk_win7_x86\i386\ndislwf.sys
>>
>>
>> One problem, one potential problem. First, “\Systemroot” is an alias to
>> the Windows directory, not to the Windows disk. You don’t need to add
>> “\windows”:
>> \Systemroot\system32\ndislwf.sys
>>
>> Next, do you really have a share from \HO64 called WinDDK that points
>> to the WinDDK directory? It’s possible, I’m just checking. I usually
>> share the whole disk, in which case it would be \HO64\c\WinDDK\7100…
>>
>> –
>> Tim Roberts, xxxxx@probo.com
>> Providenza & Boekelheide, Inc.
>>
>>
>> —
>> WINDBG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>>
>> —
>> WINDBG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
>