I have Windows XP on the target computer and Windows 2000 on the host
computer. I have null modem cable connection, I have tested it under MS-DOS.
I have modified the boot.ini (…/fastdetect /debugport=COM1
/baudrate=19200), I have set up the symbol file path ont the host
(SRV*e:\websymbols*http://msdl.microsoft.com/download/symbols;E:\NctFewKb\ob
jchk\i386), the source file path , and the image file path
(E:\NctFewKb\objchk\i386). I have set the baudrate and COM-port on the host.
I start WinDbg…Kernel Debud and then I start the target with [debug
enabled] settings, the host writes “Waiting for connection” and then I can
see black screen on the target, I am waiting, waiting and waiting and
nothing happens.
I try several settings in the symbol path and sometimes the host Writes
“connected to Windows Xp…symbol file:…Source files: … Image files:…”
and then black screen on the target and nothing happens.
Earlier I used Win2000 on the target with the same settings as you can see
above and everything worked well.
First I would ask if you are using the latest WinDbg? Go to http://www.microsoft.com/ddk/debugging/ to insure you are. Do not use the
one provided with the DDK as it is woefully out of date and is known to be
fraught with problems.
Secondly, are you sure you cables are connected to the proper COM ports and
using the same baudrate? Try using something like HyperTerminal to perform
simple serial data transfers between the connections before trying to
establish a debug connection. BTW, even though the COM is utilizing serial
communications, 19200 is a tad bit slow. You might want to try 115200
instead.
Thirdly, this is the wrong forum for WinDbg issues. You need to make your
post to the WinDbg newsgroup which OSR hosts.
“Ferenc Deák” wrote in message news:xxxxx@ntdev… > > Hi, > > I have Windows XP on the target computer and Windows 2000 on the host > computer. I have null modem cable connection, I have tested it under MS-DOS. > I have modified the boot.ini (…/fastdetect /debugport=COM1 > /baudrate=19200), I have set up the symbol file path ont the host > (SRVe:\websymbolshttp://msdl.microsoft.com/download/symbols;E:\NctFewKb\ob > jchk\i386), the source file path , and the image file path > (E:\NctFewKb\objchk\i386). I have set the baudrate and COM-port on the host. > I start WinDbg…Kernel Debud and then I start the target with [debug > enabled] settings, the host writes “Waiting for connection” and then I can > see black screen on the target, I am waiting, waiting and waiting and > nothing happens. > > I try several settings in the symbol path and sometimes the host Writes > “connected to Windows Xp…symbol file:…Source files: … Image files:…” > and then black screen on the target and nothing happens. > > Earlier I used Win2000 on the target with the same settings as you can see > above and everything worked well. > > What can be wrong? > > Ferenc > > > > >
Try pressing Ctrl-Break a couple times, Alt-Ctrl-R a couple times, and then
Ctrl-Break a couple times again. The later versions of WinDbg are messed up.
“Ferenc Deák” wrote in message news:xxxxx@ntdev… > > Hi, > > I have Windows XP on the target computer and Windows 2000 on the host > computer. I have null modem cable connection, I have tested it under MS-DOS. > I have modified the boot.ini (…/fastdetect /debugport=COM1 > /baudrate=19200), I have set up the symbol file path ont the host > (SRVe:\websymbolshttp://msdl.microsoft.com/download/symbols;E:\NctFewKb\ob > jchk\i386), the source file path , and the image file path > (E:\NctFewKb\objchk\i386). I have set the baudrate and COM-port on the host. > I start WinDbg…Kernel Debud and then I start the target with [debug > enabled] settings, the host writes “Waiting for connection” and then I can > see black screen on the target, I am waiting, waiting and waiting and > nothing happens. > > I try several settings in the symbol path and sometimes the host Writes > “connected to Windows Xp…symbol file:…Source files: … Image files:…” > and then black screen on the target and nothing happens. > > Earlier I used Win2000 on the target with the same settings as you can see > above and everything worked well. > > What can be wrong? > > Ferenc > > > > >
> Try pressing Ctrl-Break a couple times, Alt-Ctrl-R a couple times, and
then
Ctrl-Break a couple times again. The later versions of WinDbg are
messed up.
Which later versions are messed up? 6.1.0017.0 seems to work for me.
I did notice that the problem was over a 19.2 serial connection. That is
very slow. Perhaps bumping the speed up to something reasonable like
115.2 might goose the 'bag into action.
If it works for you, great. It is not working for everybody. I have been
reporting it to MS and they acknowledge the problem.
“Mark Roddy” wrote in message news:xxxxx@ntdev… > > > > Try pressing Ctrl-Break a couple times, Alt-Ctrl-R a couple times, and > > then > > Ctrl-Break a couple times again. The later versions of WinDbg are > > messed up. > > > > Which later versions are messed up? 6.1.0017.0 seems to work for me. > > I did notice that the problem was over a 19.2 serial connection. That is > very slow. Perhaps bumping the speed up to something reasonable like > 115.2 might goose the 'bag into action. > > =========================== > Mark Roddy > Consultant, Microsoft DDK MVP > Hollis Technology Solutions > xxxxx@hollistech.com > www.hollistech.com > 603-321-1032 > > > >
So what exactly is ‘it’? And do you know when the bag fell down again?
-----Original Message-----
From: Doug [mailto:xxxxx@hotmail.com]
Sent: Wednesday, February 19, 2003 8:46 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Windbg problem
If it works for you, great. It is not working for everybody. I have been
reporting it to MS and they acknowledge the problem.
“Mark Roddy” wrote in message news:xxxxx@ntdev… > > > > Try pressing Ctrl-Break a couple times, Alt-Ctrl-R a couple times, > > and then Ctrl-Break a couple times again. The later versions of > > WinDbg are messed up. > > > > Which later versions are messed up? 6.1.0017.0 seems to work for me. > > I did notice that the problem was over a 19.2 serial connection. That is > very slow. Perhaps bumping the speed up to something reasonable like > 115.2 might goose the 'bag into action. > > =========================== > Mark Roddy > Consultant, Microsoft DDK MVP > Hollis Technology Solutions > xxxxx@hollistech.com > www.hollistech.com > 603-321-1032 > > > >