Hi, everyone…
I’ve tired of trying to connect host and target computers with comm cable using kernel debugger and windbg. I’v got good null-modem rs232 cable, I’ve connected two computers with it on com1 ports on both of them, I’ve checked the connection with direct connection (both computers have win2k installed) provided with windows 2000 (I hadn’t checked it with hyperterminal, but does this really matters? I’ve coped a couple of files over the com port and everything was allright.), I’ve added second string to boot.ini on the target machine with /fastdetect /debug /debugport=com1 /baudrate=115200 (maybe I should delete /fastdetect???), the following happens on windbg command window:
Microsoft (R) Windows Debugger Version 6.0.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \.\com1
Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: c:\winnt\symbols
Executable search path is: c:\winnt\system32
and nothing more! It can wait years! I got correct debug symbols on host and target machine… Well I don’t know what else I should do to make it work… Does anybody have an advice?
Thanks…
Try disabling “Legacy USB Support” in the BIOS for both the systems. This
works around a known issue with some Intel chipsets that interfere with com
ports during system initialization.
Hope this helps,
Niraj
-----Original Message-----
From: Andrew Sloven [mailto:xxxxx@amurshipyard.ru]
Sent: Thursday, October 03, 2002 12:22 AM
To: NT Developers Interest List
Subject: [ntdev] Kernel debugging…
Hi, everyone…
I’ve tired of trying to connect host and target computers with comm cable
using kernel debugger and windbg. I’v got good null-modem rs232 cable, I’ve
connected two computers with it on com1 ports on both of them, I’ve checked
the connection with direct connection (both computers have win2k installed)
provided with windows 2000 (I hadn’t checked it with hyperterminal, but does
this really matters? I’ve coped a couple of files over the com port and
everything was allright.), I’ve added second string to boot.ini on the
target machine with /fastdetect /debug /debugport=com1 /baudrate=115200
(maybe I should delete /fastdetect???), the following happens on windbg
command window:
Microsoft (R) Windows Debugger Version 6.0.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Opened <file:> \.\com1
Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: c:\winnt\symbols
Executable search path is: c:\winnt\system32
----------------------------------------------------------------------------
------------------
and nothing more! It can wait years! I got correct debug symbols on host and
target machine… Well I don’t know what else I should do to make it work…
Does anybody have an advice?
Thanks…
—
You are currently subscribed to ntdev as: xxxxx@netapp.com
To unsubscribe send a blank email to %%email.unsub%%</file:>
Try disabling “Legacy USB Support” in the BIOS for both the systems. This
works around a known issue with some Intel chipsets that interfere with com
ports during system initialization.
Hope this helps,
Niraj
-----Original Message-----
From: Andrew Sloven [mailto:xxxxx@amurshipyard.ru]
Sent: Thursday, October 03, 2002 12:22 AM
To: NT Developers Interest List
Subject: [ntdev] Kernel debugging…
Hi, everyone…
I’ve tired of trying to connect host and target computers with comm cable
using kernel debugger and windbg. I’v got good null-modem rs232 cable, I’ve
connected two computers with it on com1 ports on both of them, I’ve checked
the connection with direct connection (both computers have win2k installed)
provided with windows 2000 (I hadn’t checked it with hyperterminal, but does
this really matters? I’ve coped a couple of files over the com port and
everything was allright.), I’ve added second string to boot.ini on the
target machine with /fastdetect /debug /debugport=com1 /baudrate=115200
(maybe I should delete /fastdetect???), the following happens on windbg
command window:
Microsoft (R) Windows Debugger Version 6.0.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Opened <file:> \.\com1
Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: c:\winnt\symbols
Executable search path is: c:\winnt\system32
----------------------------------------------------------------------------
------------------
and nothing more! It can wait years! I got correct debug symbols on host and
target machine… Well I don’t know what else I should do to make it work…
Does anybody have an advice?
Thanks… .</file:>
MessageOh!!! Thank you VERY much!!! It helped! :)))
/regards/
----- Original Message -----
From: Jaiswal, Niraj
To: NT Developers Interest List
Sent: Thursday, October 03, 2002 6:57 PM
Subject: [ntdev] RE: Kernel debugging…
Try disabling “Legacy USB Support” in the BIOS for both the systems. This works around a known issue with some Intel chipsets that interfere with com ports during system initialization.
Hope this helps,
Niraj
Hi
Your baudrate at target machine and host machine is same?
Vysyaraju Dali Raju
Vysyaraju Daliraju, / Systems Software Engineer
SBS Technologies, 8371C Central Ave. / Newark, CA 94560
Phone: 510-742-2570 / Fax: -2501 / EMail: xxxxx@sbs.com
mailto:xxxxx >
-----Original Message-----
From: Andrew Sloven [mailto:xxxxx@amurshipyard.ru]
Sent: Thursday, October 03, 2002 12:22 AM
To: NT Developers Interest List
Subject: [ntdev] Kernel debugging…
Hi, everyone…
I’ve tired of trying to connect host and target computers with comm cable
using kernel debugger and windbg. I’v got good null-modem rs232 cable, I’ve
connected two computers with it on com1 ports on both of them, I’ve checked
the connection with direct connection (both computers have win2k installed)
provided with windows 2000 (I hadn’t checked it with hyperterminal, but does
this really matters? I’ve coped a couple of files over the com port and
everything was allright.), I’ve added second string to boot.ini on the
target machine with /fastdetect /debug /debugport=com1 /baudrate=115200
(maybe I should delete /fastdetect???), the following happens on windbg
command window:
----------------------------------------------------------------------------
------------------
Microsoft (R) Windows Debugger Version 6.0.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Opened <file:> \.\com1
Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: c:\winnt\symbols
Executable search path is: c:\winnt\system32
----------------------------------------------------------------------------
------------------
and nothing more! It can wait years! I got correct debug symbols on host and
target machine… Well I don’t know what else I should do to make it work…
Does anybody have an advice?
Thanks…
—
You are currently subscribed to ntdev as: xxxxx@sbs.com
To unsubscribe send a blank email to %%email.unsub%%</file:></mailto:xxxxx>
Sure, baudrates are the same… 115200.
/regards/
----- Original Message -----
From: Vysyaraju Daliraju
To: NT Developers Interest List
Sent: Friday, October 04, 2002 2:35 AM
Subject: [ntdev] RE: Kernel debugging…
Hi
Your baudrate at target machine and host machine is same?
Vysyaraju Dali Raju
Vysyaraju Daliraju, / Systems Software Engineer
SBS Technologies, 8371C Central Ave. / Newark, CA 94560
Phone: 510-742-2570 / Fax: -2501 / EMail: xxxxx@sbs.com mailto:xxxxx</mailto:xxxxx>