# NT 5 Notes From ReinerF

First, delete any extranous copies of the following files off your test machine:
(you will be copying the "good" ones to the system32 dir)
ntsd.exe
imagehlp.dll (the one that lives in \nt\idw\path1st and \nt\idw are the same, and they can stay but nuke the rest)
msdbi.dll
mspdb50.dll
nddeexts.dll
ntsdexts.dll
splexts.dll
userexts.dll
vdmexts.dll
You will need the following files that match the ones you used to build the binaries:
You can copy these off your build machine to your test machine.
imagehlp.dll (on your build machine the imagehlp.dll in nt\idw should be the same as in \nt\idw\path1st. BTW, you should copy this binary over the one in the system32 on your build machine anyway!)
mspdb50.dll (in \nt\mstools)
You will need the following files that are from the NT4sp1 share:
The files havent changed between sp1 and sp3 so that is why we copy them from the sp1 share. The share is \\ntbuilds\release\usa\1381sp1\\fre.wks\system32\*exts*.dll
nddeexts.dll
ntsdexts.dll
splexts.dll
userexts.dll
vdmexts.dll
You will need the following files that are from the NT5 current build share:
These files are available on \\ntbuilds\release\usa\latest.tst\\fre.wks\
ntsd.exe
msdbi.dll
Copy all the files in red from the correct locations as outlined above to the winnt\system32 directory on your test machine. You will heceforth have no problems debugging on NT4. All of the debugger extensions will work properly and you will be able to redirect your symbol path so you dont even need to copy the symbols locally (the !sympath command will let you do this). You will also be able to use pdb's or dbg's, either one will work properly.
Its just that easy.
-reiner