I have found that sometimes, if I’ve rebooted the host machine while the
target machine is sitting up and idle, I can not get a debug session. I
reboot the target machine, and I can then get a debug session. Another
gotcha that real low-tech is a boot.ini file that has both a debug and a
non-debug entry, and the non-debug’s the defaultI sometimes miss the
opportunity to choose the correct debug session, leaving me in non-debug,
w/o an ability to connect target/host.
Hello,
On Sun, Jul 13, 2003 at 03:15:59PM -0400, xxxxx@worldnet.att.net
wrote:
Another gotcha that real low-tech is a boot.ini file that has both a debug
and a non-debug entry, and the non-debug’s the default. I sometimes miss
the
opportunity to choose the correct debug session, leaving me in non-debug,
w/o an ability to connect target/host.
I’m not sure if this was meant as a question, but I will answer
nevertheless: Just change the order of the debug and non-debug entry, and
you will end up with a debugged windows every time you boot unless you
specify otherwise.
Spiro.