A road named NoNameUno

Now that I've a debugging setup that I can use, I need a bunch of softwares (applications, drivers etc.)...

I used the latest wdk 7001 to build the example windows kernel socket based EchoSrver, built the ndis 6.0 filter. And I used an older version of wdk 6001 that has the source for Intel 10/100 adapter based miniport. Since I'm using ndis6.0, I was looking for the 60 build, and it is there...

So now I've three drivers that I want to install and modify when I want to probe or add something. I knew there is a kd command .kdfiles that takes a map file, but I was stumbling a bit since the parser is not that talkative to tell you much when something goes wrong. But here is the example file anyone can use -

 #start of mapfile - there is no blank lines between the line starting with map command and the #following two line. And you can multiple driver mapping using same sort of 3 lines

# 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

\??\c:\windows\system32\ndislwf.sys

\\HO64\C$\WinDDK\7100.0.0\src\network\ndis\filter\objchk_win7_x86\i386\ndislwf.sys

#endof mapfile

Since I would be exercising the wsk based echo server, I needed a user level echo client. There are plenty of examples you can find on the internet for this, but the one like most is from the site for a book I used in the past named "Practical socket programming in C". It does not take more than an hour to build the client and user mode server in case you need to have that too.

I installed all the three drivers on the test machine, and the test code in the host machine. I'm set to debug now ...