WinDbg used to load fine, but now hangs on boot

WINDBG
1

Although I am new to WinDbg from a career standpoint, I had been using it
to great success last month. However, we stopped for a while and removed
the serial cable.

A few days ago I tried to reconnect the null modem cable and start
everything up again, but Win2k hangs at the last 10% of the progress bar,
right before it goes to the desktop GUI and completes loading.

How can I diagnose this problem?

Here’s some info, and what I’ve already done.

Win2k SP2 on host and Win2k SP3 on target machine,
com1 on target, com2 on host, null modem cable, 115200 bps
WON’T HANG IF I UNPLUG THE SERIAL CABLE TO THE TARGET MACHINE
I tried slowing down to 38400 bps with the same result
WinDbg on Host machine just sits there saying “waiting to reconnect”
my driver “seems” ok to load at boot time, and will do so if cable is not
plugged in
com1 under device manager properties on target machine has a ! next to it.
This is a clue. However, I tried com2 with the same result.

Can someone suggest to me also what the latest version of WinDbg is, and
whether there is a “target side” set of s/w that could be or should be
updated as well?

Thanks - my deadline is (gulp) Monday to get this finished…

Cheers,

Jeff Long
President
Granite Precision Inc.

2

Problem might be in the Cable also. please change the cable and try.

Cyril
----- Original Message -----
From:
To: “Kernel Debugging Interest List”
Sent: Friday, August 01, 2003 3:57 AM
Subject: [windbg] WinDbg used to load fine, but now hangs on boot

> Although I am new to WinDbg from a career standpoint, I had been using it
> to great success last month. However, we stopped for a while and removed
> the serial cable.
>
> A few days ago I tried to reconnect the null modem cable and start
> everything up again, but Win2k hangs at the last 10% of the progress bar,
> right before it goes to the desktop GUI and completes loading.
>
> How can I diagnose this problem?
>
> Here’s some info, and what I’ve already done.
>
> Win2k SP2 on host and Win2k SP3 on target machine,
> com1 on target, com2 on host, null modem cable, 115200 bps
> WON’T HANG IF I UNPLUG THE SERIAL CABLE TO THE TARGET MACHINE
> I tried slowing down to 38400 bps with the same result
> WinDbg on Host machine just sits there saying “waiting to reconnect”
> my driver “seems” ok to load at boot time, and will do so if cable is not
> plugged in
> com1 under device manager properties on target machine has a ! next to it.
> This is a clue. However, I tried com2 with the same result.
>
> Can someone suggest to me also what the latest version of WinDbg is, and
> whether there is a “target side” set of s/w that could be or should be
> updated as well?
>
> Thanks - my deadline is (gulp) Monday to get this finished…
>
> Cheers,
>
> Jeff Long
> President
> Granite Precision Inc.
>
>
> —
> You are currently subscribed to windbg as: xxxxx@wipro.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

3

(1) Make sure you are using the right com ports on both machine. I would
turn the debugger off on the target machine and set up a hyperterminal
session on both both and type to make sure your cable and com ports are
correct.
(2) The ! in front of the com port is nornal if you have that com port
inuse in your boot.ini.
(3) Try pressing control break in windbg.
(4) Make sure your line parameters are correct like baud rate. In windbg
you can cycle thru the baud rate easy.
(5) Get the latest version of windbg from the internet. If Is FREE