Debuggee not connected

Douglas Cuthbertson

unread,

Mar 3, 2003, 9:52:44 AM3/3/03

to

Hello,
I can't get windbg to connect to the target computer. I'd appreciate
any help someone here can provide. Here's my setup:

The target computer is running Windows 2000 Professional Debug/Checked
Build Service Pack 2.

The host computer is running Windows NT 4.0, SP6a.

If I boot the target without debugging enabled, I can run
hyperterminal on com1. The two computers are connected by a nul-modem
cable.

When I boot the target with debugging enabled it starts and, as
expected, com1 is not listed by the device manager.

When I start windbg on the host, I type Ctrl-K and enter Baud Rate:
57600 and Port: com1, the command window displays the following:

Opened \\.\com1
Waiting to reconnect...

I've tried rebooting the target, but there's no change in windbg's
status. I've also tried Ctrl-Alt-K to request an initial break. That
causes the target to hang during the boot process, but windbg still
thinks the debuggee is not connected.

Please give me some ideas on what I've missed. This is the first time
I've used windbg, so it's probably something basic.

Thank you,
Doug Cuthbertson

David Holcomb [MS]

unread,

Mar 3, 2003, 11:33:21 AM3/3/03

to

What are the specific boot.ini options you are using on the target machine?

Did you try Ctrl+Alt+A to change baud rates and then Ctrl+Alt+R to re-sync
and then try to break in with Ctrl+Break again?

--
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Douglas Cuthbertson" <doug.cut...@entegrity.com> wrote in message
news:d6b4eb12.03030...@posting.google.com...

Douglas Cuthbertson

unread,

Mar 3, 2003, 5:01:50 PM3/3/03

to

Hello David,
Thanks for replying. My boot.ini is:

[boot loader]
timeout=7
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect /debugport=com1 /baudrate=57600
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect

I ran two tests. First, I let the target finish booting and then
immediately tried Ctrl+Break on the host. The target stopped running
(it wouldn't respond to any input), but windbg still indicated that it
was waiting to reconnect. The Go command is greyed-out in the Debug
menu as well. So it seems that windbg can stop the target, but it
can't do anything else.

For the second test, I first tried Ctrl+Alt+A, Ctrl+Alt+R and
Ctrl+Break (so the first Ctrl+Break was with a baud rate of 115200). I
cycled through each baud rate. The target froze only after the baud
rate returned to 57600.

Regards,
Doug Cuthbertson

"David Holcomb [MS]" <dhol...@microsoft.com> wrote in message news:<3e6383d1$1...@news.microsoft.com>...

David Holcomb [MS]

unread,

Mar 3, 2003, 5:25:23 PM3/3/03

to

Does the target machine have Legacy USB support enabled in the BIOS? If so,
can you try disabling it?

Doug Cuthbertson

unread,

Mar 3, 2003, 6:23:17 PM3/3/03

to

The legacy USB support is already disabled.

Thanks,
Doug Cuthbertson

"David Holcomb [MS]" <dhol...@microsoft.com> wrote in message

news:3e63d652$1...@news.microsoft.com...