> How about moving this to the WINDBG forum, since it has nothing to do with
file systems.
Yes, that would be better, but since it’s been started here
and also lots of FSD folks can use it, I will reply here 
Besides what is in the User’s Manual, do you have any other tips?
This is what I do:
I have a link on desktop, which is “Windbg for VMWARE”
and contains:
“C:\Program Files\Debugging Tools for Windows\windbg.exe” -k com:port=\.\pipe\com_1,pipe
All my images of NT-based systems are configured as
- normal OS run
- OS with kernel debugging enabled.
When I need to debug something:
- I create clone of desired target platform
- Start the image
- As soon as the image is running (in BIOS it’s OK),
I start Windbg from the shortcut above - Windbg should with no problems connect to the virtual machine
You need to ensure that the virtual machine is running sooner than
Windbg, otherwise VMWARE complains about the pipe being open already.
That also applies to reset of the OS (restart is OK tho)
For some time, I was unable to run debug session of Windows NT 4.0,
but that’s because my Windbg is too new. And NT 4.0 is dead anyway
so I don’t care
I think there are no other tips, besides the obvious ones
like get your symbol files properly configured, etc.
L.