Cannot debug Windows Vista via Null Modem

NTDEV
1

Hi, All

I had read the help of WinDbg for several days. However, I could not
debug kernel from a remote computer. In my environment, the target
computer is a PC with Win2k, WinXP and Vista. (all OSes had been
updated to latest.) The host computer is a Notebook with WinXP, USB
serial port, and these two computers are connected using Null Modem
115200 8N1. This configuration is working fine for Win2k and WinXP.
After the target computer starts, I could get the message like

Opened \.\com1
Waiting to reconnect…
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is:
C:\Windows\Symbols;SRV*D:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
System Uptime: not available

However, in Vista I didn’t get anything from it. Even if I open a
PuTTY to monitor the serial port. Vista does not send anything to the
port, but XP and 2k do.

Could anyone give me some suggestion to set my Vista to enable kernel
debugging via serial port. I set my Vista using following commands

Microsoft Windows [Version 6.0.6000] - Windows Vista Enterprise from MSDN

D:\>bcdedit /bootdebug on
The operation completed successfully.

D:\>bcdedit /debug on
The operation completed successfully.

D:\>bcdedit /dbgsettings
debugtype Serial
debugport 1
baudrate 115200

I also test if bootdebug or debug is off. However, there is still no
message sent from Vista. I had checked the serial port. The serial
port works fine under Vista with PuTTY, and the target computer only
got 3 serial port, COM1(phyiscal), COM20/COM21(bluetooth virtual
serial port). Hence, I think there are some mistakes on my Vista
settings. any suggestion? thanks.

Regards, Mihs

This message was sent using IMP, the Internet Messaging Program.

2

Hi, Mihs,

On your Vista Target, you can try an F8 boot (press F8 immediately after the
Bios messages disappear from the screen) and you get a list of choices, one
of them being to Run with Debugging on. Maybe that’s what’s missing, I don’t
know. I do this with 1394 and it works fine.

Alberto.

----- Original Message -----
From: “Ming-I Hsieh”
To: “Windows System Software Devs Interest List”
Sent: Tuesday, September 11, 2007 9:49 PM
Subject: [ntdev] Cannot debug Windows Vista via Null Modem

Hi, All

I had read the help of WinDbg for several days. However, I could not
debug kernel from a remote computer. In my environment, the target
computer is a PC with Win2k, WinXP and Vista. (all OSes had been
updated to latest.) The host computer is a Notebook with WinXP, USB
serial port, and these two computers are connected using Null Modem
115200 8N1. This configuration is working fine for Win2k and WinXP.
After the target computer starts, I could get the message like

Opened \.\com1
Waiting to reconnect…
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is:
C:\Windows\Symbols;SRVD:\localsymbolshttp://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
System Uptime: not available

However, in Vista I didn’t get anything from it. Even if I open a
PuTTY to monitor the serial port. Vista does not send anything to the
port, but XP and 2k do.

Could anyone give me some suggestion to set my Vista to enable kernel
debugging via serial port. I set my Vista using following commands

Microsoft Windows [Version 6.0.6000] - Windows Vista Enterprise from MSDN

D:>bcdedit /bootdebug on
The operation completed successfully.

D:>bcdedit /debug on
The operation completed successfully.

D:>bcdedit /dbgsettings
debugtype Serial
debugport 1
baudrate 115200

I also test if bootdebug or debug is off. However, there is still no
message sent from Vista. I had checked the serial port. The serial
port works fine under Vista with PuTTY, and the target computer only
got 3 serial port, COM1(phyiscal), COM20/COM21(bluetooth virtual
serial port). Hence, I think there are some mistakes on my Vista
settings. any suggestion? thanks.

Regards, Mihs

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

Hi, alberto.

Thanks for ur suggestion. I had checked it before with a clear
Vista(w/o any additional software and only 1 serial port, COM1). But
it does not work. If I could not solve this problem in this week, I
think I will buy a 1394 for trying since my notebook.

Regards, Mihs

Quoting Alberto Moreira :

> Hi, Mihs,
>
> On your Vista Target, you can try an F8 boot (press F8 immediately
> after the Bios messages disappear from the screen) and you get a list
> of choices, one of them being to Run with Debugging on. Maybe that’s
> what’s missing, I don’t know. I do this with 1394 and it works fine.
>
> Alberto.
>
>
> ----- Original Message ----- From: “Ming-I Hsieh”
>
> To: “Windows System Software Devs Interest List”
> Sent: Tuesday, September 11, 2007 9:49 PM
> Subject: [ntdev] Cannot debug Windows Vista via Null Modem
>
>
> Hi, All
>
> I had read the help of WinDbg for several days. However, I could not
> debug kernel from a remote computer. In my environment, the target
> computer is a PC with Win2k, WinXP and Vista. (all OSes had been
> updated to latest.) The host computer is a Notebook with WinXP, USB
> serial port, and these two computers are connected using Null Modem
> 115200 8N1. This configuration is working fine for Win2k and WinXP.
> After the target computer starts, I could get the message like
>
> Opened \.\com1
> Waiting to reconnect…
> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established.
> Symbol search path is:
> C:\Windows\Symbols;SRVD:\localsymbolshttp://msdl.microsoft.com/download/symbols
> Executable search path is:
> Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
> Built by: 2600.xpsp_sp2_gdr.070227-2254
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
> System Uptime: not available
>
> However, in Vista I didn’t get anything from it. Even if I open a
> PuTTY to monitor the serial port. Vista does not send anything to the
> port, but XP and 2k do.
>
> Could anyone give me some suggestion to set my Vista to enable kernel
> debugging via serial port. I set my Vista using following commands
>
> Microsoft Windows [Version 6.0.6000] - Windows Vista Enterprise from MSDN
>
> D:>bcdedit /bootdebug on
> The operation completed successfully.
>
> D:>bcdedit /debug on
> The operation completed successfully.
>
> D:>bcdedit /dbgsettings
> debugtype Serial
> debugport 1
> baudrate 115200
>
> I also test if bootdebug or debug is off. However, there is still no
> message sent from Vista. I had checked the serial port. The serial
> port works fine under Vista with PuTTY, and the target computer only
> got 3 serial port, COM1(phyiscal), COM20/COM21(bluetooth virtual
> serial port). Hence, I think there are some mistakes on my Vista
> settings. any suggestion? thanks.
>
> Regards, Mihs
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

4

Can you disable the virtual serials ( bluetooh ones) and then restart the
client, then hit cntl+break couple times to see if those few lines are
being spewed out or not …

-pro

Hi, alberto.

Thanks for ur suggestion. I had checked it before with a clear
Vista(w/o any additional software and only 1 serial port, COM1). But
it does not work. If I could not solve this problem in this week, I
think I will buy a 1394 for trying since my notebook.

Regards, Mihs

Quoting Alberto Moreira :
>
>> Hi, Mihs,
>>
>> On your Vista Target, you can try an F8 boot (press F8 immediately
>> after the Bios messages disappear from the screen) and you get a list
>> of choices, one of them being to Run with Debugging on. Maybe that’s
>> what’s missing, I don’t know. I do this with 1394 and it works fine.
>>
>> Alberto.
>>
>>
>> ----- Original Message ----- From: “Ming-I Hsieh”
>>
>> To: “Windows System Software Devs Interest List”
>> Sent: Tuesday, September 11, 2007 9:49 PM
>> Subject: [ntdev] Cannot debug Windows Vista via Null Modem
>>
>>
>> Hi, All
>>
>> I had read the help of WinDbg for several days. However, I could not
>> debug kernel from a remote computer. In my environment, the target
>> computer is a PC with Win2k, WinXP and Vista. (all OSes had been
>> updated to latest.) The host computer is a Notebook with WinXP, USB
>> serial port, and these two computers are connected using Null Modem
>> 115200 8N1. This configuration is working fine for Win2k and WinXP.
>> After the target computer starts, I could get the message like
>>
>> Opened \.\com1
>> Waiting to reconnect…
>> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
>> Kernel Debugger connection established.
>> Symbol search path is:
>> C:\Windows\Symbols;SRVD:\localsymbolshttp://msdl.microsoft.com/download/symbols
>> Executable search path is:
>> Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
>> Built by: 2600.xpsp_sp2_gdr.070227-2254
>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
>> System Uptime: not available
>>
>> However, in Vista I didn’t get anything from it. Even if I open a
>> PuTTY to monitor the serial port. Vista does not send anything to the
>> port, but XP and 2k do.
>>
>> Could anyone give me some suggestion to set my Vista to enable kernel
>> debugging via serial port. I set my Vista using following commands
>>
>> Microsoft Windows [Version 6.0.6000] - Windows Vista Enterprise from
>> MSDN
>>
>> D:>bcdedit /bootdebug on
>> The operation completed successfully.
>>
>> D:>bcdedit /debug on
>> The operation completed successfully.
>>
>> D:>bcdedit /dbgsettings
>> debugtype Serial
>> debugport 1
>> baudrate 115200
>>
>> I also test if bootdebug or debug is off. However, there is still no
>> message sent from Vista. I had checked the serial port. The serial
>> port works fine under Vista with PuTTY, and the target computer only
>> got 3 serial port, COM1(phyiscal), COM20/COM21(bluetooth virtual
>> serial port). Hence, I think there are some mistakes on my Vista
>> settings. any suggestion? thanks.
>>
>> Regards, Mihs
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

5

Hi, Prokash

I had just checked it according to ur suggestion with a clear Vista
(no bluetooth, no virtual serial port and any additional softwares).
But it still does not work.

Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \.\com1
Waiting to reconnect…

While windbg in host computer is always the initial message, and there
is not message from target computer via null modem, I think there is
some issue to incur the target computer does not send message to host
computer. But the same environment is work if I changed the OS of
target to XP or 2k. XD

Regards, Mihs

Quoting xxxxx@garlic.com:

Can you disable the virtual serials ( bluetooh ones) and then restart the
client, then hit cntl+break couple times to see if those few lines are
being spewed out or not …

-pro

> Hi, alberto.
>
> Thanks for ur suggestion. I had checked it before with a clear
> Vista(w/o any additional software and only 1 serial port, COM1). But
> it does not work. If I could not solve this problem in this week, I
> think I will buy a 1394 for trying since my notebook.
>
> Regards, Mihs
>
> Quoting Alberto Moreira :
>>
>>> Hi, Mihs,
>>>
>>> On your Vista Target, you can try an F8 boot (press F8 immediately
>>> after the Bios messages disappear from the screen) and you get a list
>>> of choices, one of them being to Run with Debugging on. Maybe that’s
>>> what’s missing, I don’t know. I do this with 1394 and it works fine.
>>>
>>> Alberto.
>>>
>>>
>>> ----- Original Message ----- From: “Ming-I Hsieh”
>>>
>>> To: “Windows System Software Devs Interest List”
>>> Sent: Tuesday, September 11, 2007 9:49 PM
>>> Subject: [ntdev] Cannot debug Windows Vista via Null Modem
>>>
>>>
>>> Hi, All
>>>
>>> I had read the help of WinDbg for several days. However, I could not
>>> debug kernel from a remote computer. In my environment, the target
>>> computer is a PC with Win2k, WinXP and Vista. (all OSes had been
>>> updated to latest.) The host computer is a Notebook with WinXP, USB
>>> serial port, and these two computers are connected using Null Modem
>>> 115200 8N1. This configuration is working fine for Win2k and WinXP.
>>> After the target computer starts, I could get the message like
>>>
>>> Opened \.\com1
>>> Waiting to reconnect…
>>> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
>>> Kernel Debugger connection established.
>>> Symbol search path is:
>>> C:\Windows\Symbols;SRVD:\localsymbolshttp://msdl.microsoft.com/download/symbols
>>> Executable search path is:
>>> Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
>>> Built by: 2600.xpsp_sp2_gdr.070227-2254
>>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
>>> System Uptime: not available
>>>
>>> However, in Vista I didn’t get anything from it. Even if I open a
>>> PuTTY to monitor the serial port. Vista does not send anything to the
>>> port, but XP and 2k do.
>>>
>>> Could anyone give me some suggestion to set my Vista to enable kernel
>>> debugging via serial port. I set my Vista using following commands
>>>
>>> Microsoft Windows [Version 6.0.6000] - Windows Vista Enterprise from
>>> MSDN
>>>
>>> D:>bcdedit /bootdebug on
>>> The operation completed successfully.
>>>
>>> D:>bcdedit /debug on
>>> The operation completed successfully.
>>>
>>> D:>bcdedit /dbgsettings
>>> debugtype Serial
>>> debugport 1
>>> baudrate 115200
>>>
>>> I also test if bootdebug or debug is off. However, there is still no
>>> message sent from Vista. I had checked the serial port. The serial
>>> port works fine under Vista with PuTTY, and the target computer only
>>> got 3 serial port, COM1(phyiscal), COM20/COM21(bluetooth virtual
>>> serial port). Hence, I think there are some mistakes on my Vista
>>> settings. any suggestion? thanks.
>>>
>>> Regards, Mihs
>>>
>>> ----------------------------------------------------------------
>>> This message was sent using IMP, the Internet Messaging Program.
>>>
>>>
>>>
>>> —
>>> NTDEV is sponsored by OSR
>>>
>>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> http://www.osr.com/seminars
>>>
>>> To unsubscribe, visit the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer —
>>> NTDEV is sponsored by OSR
>>>
>>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> http://www.osr.com/seminars
>>>
>>> To unsubscribe, visit the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

6

Can you check the port’s baudrate setting on the client. Control
Panel->Systems and Maintenance -> Device manager -> Ports -> COM1 (Right clk
and see properties ).

That’s all I can think of.

Also from the client side, you use the resynch using windbg menu to see if
any of the baud rate takes …

-pro

On 9/11/07, Ming-I Hsieh wrote:
>
> Hi, Prokash
>
> I had just checked it according to ur suggestion with a clear Vista
> (no bluetooth, no virtual serial port and any additional softwares).
> But it still does not work.
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Opened \.\com1
> Waiting to reconnect…
>
> While windbg in host computer is always the initial message, and there
> is not message from target computer via null modem, I think there is
> some issue to incur the target computer does not send message to host
> computer. But the same environment is work if I changed the OS of
> target to XP or 2k. XD
>
> Regards, Mihs
>
> Quoting xxxxx@garlic.com:
>
> > Can you disable the virtual serials ( bluetooh ones) and then restart
> the
> > client, then hit cntl+break couple times to see if those few lines are
> > being spewed out or not …
> >
> > -pro
> >
> >
> >> Hi, alberto.
> >>
> >> Thanks for ur suggestion. I had checked it before with a clear
> >> Vista(w/o any additional software and only 1 serial port, COM1). But
> >> it does not work. If I could not solve this problem in this week, I
> >> think I will buy a 1394 for trying since my notebook.
> >>
> >> Regards, Mihs
> >>
> >> Quoting Alberto Moreira :
> >>
> >>> Hi, Mihs,
> >>>
> >>> On your Vista Target, you can try an F8 boot (press F8 immediately
> >>> after the Bios messages disappear from the screen) and you get a list
> >>> of choices, one of them being to Run with Debugging on. Maybe that’s
> >>> what’s missing, I don’t know. I do this with 1394 and it works fine.
> >>>
> >>> Alberto.
> >>>
> >>>
> >>> ----- Original Message ----- From: “Ming-I Hsieh”
> >>>
> >>> To: “Windows System Software Devs Interest List”
> >>> Sent: Tuesday, September 11, 2007 9:49 PM
> >>> Subject: [ntdev] Cannot debug Windows Vista via Null Modem
> >>>
> >>>
> >>> Hi, All
> >>>
> >>> I had read the help of WinDbg for several days. However, I could not
> >>> debug kernel from a remote computer. In my environment, the target
> >>> computer is a PC with Win2k, WinXP and Vista. (all OSes had been
> >>> updated to latest.) The host computer is a Notebook with WinXP, USB
> >>> serial port, and these two computers are connected using Null Modem
> >>> 115200 8N1. This configuration is working fine for Win2k and WinXP.
> >>> After the target computer starts, I could get the message like
> >>>
> >>> Opened \.\com1
> >>> Waiting to reconnect…
> >>> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
> >>> Kernel Debugger connection established.
> >>> Symbol search path is:
> >>> C:\Windows\Symbols;SRVD:\localsymbols
> http://msdl.microsoft.com/download/symbols
> >>> Executable search path is:
> >>> Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
> >>> Built by: 2600.xpsp_sp2_gdr.070227-2254
> >>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
> >>> System Uptime: not available
> >>>
> >>> However, in Vista I didn’t get anything from it. Even if I open a
> >>> PuTTY to monitor the serial port. Vista does not send anything to the
> >>> port, but XP and 2k do.
> >>>
> >>> Could anyone give me some suggestion to set my Vista to enable kernel
> >>> debugging via serial port. I set my Vista using following commands
> >>>
> >>> Microsoft Windows [Version 6.0.6000] - Windows Vista Enterprise from
> >>> MSDN
> >>>
> >>> D:>bcdedit /bootdebug on
> >>> The operation completed successfully.
> >>>
> >>> D:>bcdedit /debug on
> >>> The operation completed successfully.
> >>>
> >>> D:>bcdedit /dbgsettings
> >>> debugtype Serial
> >>> debugport 1
> >>> baudrate 115200
> >>>
> >>> I also test if bootdebug or debug is off. However, there is still no
> >>> message sent from Vista. I had checked the serial port. The serial
> >>> port works fine under Vista with PuTTY, and the target computer only
> >>> got 3 serial port, COM1(phyiscal), COM20/COM21(bluetooth virtual
> >>> serial port). Hence, I think there are some mistakes on my Vista
> >>> settings. any suggestion? thanks.
> >>>
> >>> Regards, Mihs
> >>>
> >>> ----------------------------------------------------------------
> >>> This message was sent using IMP, the Internet Messaging Program.
> >>>
> >>>
> >>>
> >>> —
> >>> NTDEV is sponsored by OSR
> >>>
> >>> For our schedule of WDF, WDM, debugging and other seminars visit:
> >>> http://www.osr.com/seminars
> >>>
> >>> To unsubscribe, visit the List Server section of OSR Online at
> >>> http://www.osronline.com/page.cfm?name=ListServer —
> >>> NTDEV is sponsored by OSR
> >>>
> >>> For our schedule of WDF, WDM, debugging and other seminars visit:
> >>> http://www.osr.com/seminars
> >>>
> >>> To unsubscribe, visit the List Server section of OSR Online at
> >>> http://www.osronline.com/page.cfm?name=ListServer
> >>
> >>
> >>
> >> ----------------------------------------------------------------
> >> This message was sent using IMP, the Internet Messaging Program.
> >>
> >>
> >>
> >> —
> >> NTDEV is sponsored by OSR
> >>
> >> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> http://www.osr.com/seminars
> >>
> >> To unsubscribe, visit the List Server section of OSR Online at
> >> http://www.osronline.com/page.cfm?name=ListServer
> >>
> >
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

7

Hi, Prokashs

I had just checked the baudrate settings in bcdedit and device
manager. It’s right, 115200. However, I don’t think the problem was
incurred from baudrate because I don’t see anything in AccessPort. If
the baudrate is wrong, the AccessPort should report some garbage, but
nothing now.

BTW, had any suggestion for 1394 card for Vista? The null modem had
taken too much time. If 1394 is working, I think I will give up null
modem to keep my schedule.

Regards, Mihs

Quoting Prokash Sinha :

> Can you check the port’s baudrate setting on the client. Control
> Panel->Systems and Maintenance -> Device manager -> Ports -> COM1 (Right clk
> and see properties ).
>
> That’s all I can think of.
>
> Also from the client side, you use the resynch using windbg menu to see if
> any of the baud rate takes …
>
> -pro
>
>
> On 9/11/07, Ming-I Hsieh wrote:
>>
>> Hi, Prokash
>>
>> I had just checked it according to ur suggestion with a clear Vista
>> (no bluetooth, no virtual serial port and any additional softwares).
>> But it still does not work.
>>
>> Microsoft (R) Windows Debugger Version 6.7.0005.1
>> Copyright (c) Microsoft Corporation. All rights reserved.
>>
>> Opened \.\com1
>> Waiting to reconnect…
>>
>> While windbg in host computer is always the initial message, and there
>> is not message from target computer via null modem, I think there is
>> some issue to incur the target computer does not send message to host
>> computer. But the same environment is work if I changed the OS of
>> target to XP or 2k. XD
>>
>> Regards, Mihs
>>
>> Quoting xxxxx@garlic.com:
>>
>> > Can you disable the virtual serials ( bluetooh ones) and then restart
>> the
>> > client, then hit cntl+break couple times to see if those few lines are
>> > being spewed out or not …
>> >
>> > -pro
>> >
>> >
>> >> Hi, alberto.
>> >>
>> >> Thanks for ur suggestion. I had checked it before with a clear
>> >> Vista(w/o any additional software and only 1 serial port, COM1). But
>> >> it does not work. If I could not solve this problem in this week, I
>> >> think I will buy a 1394 for trying since my notebook.
>> >>
>> >> Regards, Mihs
>> >>
>> >> Quoting Alberto Moreira :
>> >>
>> >>> Hi, Mihs,
>> >>>
>> >>> On your Vista Target, you can try an F8 boot (press F8 immediately
>> >>> after the Bios messages disappear from the screen) and you get a list
>> >>> of choices, one of them being to Run with Debugging on. Maybe that’s
>> >>> what’s missing, I don’t know. I do this with 1394 and it works fine.
>> >>>
>> >>> Alberto.
>> >>>
>> >>>
>> >>> ----- Original Message ----- From: “Ming-I Hsieh”
>> >>>
>> >>> To: “Windows System Software Devs Interest List”
>> >>> Sent: Tuesday, September 11, 2007 9:49 PM
>> >>> Subject: [ntdev] Cannot debug Windows Vista via Null Modem
>> >>>
>> >>>
>> >>> Hi, All
>> >>>
>> >>> I had read the help of WinDbg for several days. However, I could not
>> >>> debug kernel from a remote computer. In my environment, the target
>> >>> computer is a PC with Win2k, WinXP and Vista. (all OSes had been
>> >>> updated to latest.) The host computer is a Notebook with WinXP, USB
>> >>> serial port, and these two computers are connected using Null Modem
>> >>> 115200 8N1. This configuration is working fine for Win2k and WinXP.
>> >>> After the target computer starts, I could get the message like
>> >>>
>> >>> Opened \.\com1
>> >>> Waiting to reconnect…
>> >>> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
>> >>> Kernel Debugger connection established.
>> >>> Symbol search path is:
>> >>> C:\Windows\Symbols;SRVD:\localsymbols
>> http://msdl.microsoft.com/download/symbols
>> >>> Executable search path is:
>> >>> Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
>> >>> Built by: 2600.xpsp_sp2_gdr.070227-2254
>> >>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
>> >>> System Uptime: not available
>> >>>
>> >>> However, in Vista I didn’t get anything from it. Even if I open a
>> >>> PuTTY to monitor the serial port. Vista does not send anything to the
>> >>> port, but XP and 2k do.
>> >>>
>> >>> Could anyone give me some suggestion to set my Vista to enable kernel
>> >>> debugging via serial port. I set my Vista using following commands
>> >>>
>> >>> Microsoft Windows [Version 6.0.6000] - Windows Vista Enterprise from
>> >>> MSDN
>> >>>
>> >>> D:>bcdedit /bootdebug on
>> >>> The operation completed successfully.
>> >>>
>> >>> D:>bcdedit /debug on
>> >>> The operation completed successfully.
>> >>>
>> >>> D:>bcdedit /dbgsettings
>> >>> debugtype Serial
>> >>> debugport 1
>> >>> baudrate 115200
>> >>>
>> >>> I also test if bootdebug or debug is off. However, there is still no
>> >>> message sent from Vista. I had checked the serial port. The serial
>> >>> port works fine under Vista with PuTTY, and the target computer only
>> >>> got 3 serial port, COM1(phyiscal), COM20/COM21(bluetooth virtual
>> >>> serial port). Hence, I think there are some mistakes on my Vista
>> >>> settings. any suggestion? thanks.
>> >>>
>> >>> Regards, Mihs
>> >>>
>> >>> ----------------------------------------------------------------
>> >>> This message was sent using IMP, the Internet Messaging Program.
>> >>>
>> >>>
>> >>>
>> >>> —
>> >>> NTDEV is sponsored by OSR
>> >>>
>> >>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> >>> http://www.osr.com/seminars
>> >>>
>> >>> To unsubscribe, visit the List Server section of OSR Online at
>> >>> http://www.osronline.com/page.cfm?name=ListServer —
>> >>> NTDEV is sponsored by OSR
>> >>>
>> >>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> >>> http://www.osr.com/seminars
>> >>>
>> >>> To unsubscribe, visit the List Server section of OSR Online at
>> >>> http://www.osronline.com/page.cfm?name=ListServer
>> >>
>> >>
>> >>
>> >> ----------------------------------------------------------------
>> >> This message was sent using IMP, the Internet Messaging Program.
>> >>
>> >>
>> >>
>> >> —
>> >> NTDEV is sponsored by OSR
>> >>
>> >> For our schedule of WDF, WDM, debugging and other seminars visit:
>> >> http://www.osr.com/seminars
>> >>
>> >> To unsubscribe, visit the List Server section of OSR Online at
>> >> http://www.osronline.com/page.cfm?name=ListServer
>> >>
>> >
>> >
>> >
>> > —
>> > NTDEV is sponsored by OSR
>> >
>> > For our schedule of WDF, WDM, debugging and other seminars visit:
>> > http://www.osr.com/seminars
>> >
>> > To unsubscribe, visit the List Server section of OSR Online at
>> > http://www.osronline.com/page.cfm?name=ListServer
>> >
>>
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

8

I know 1394 works usually.

When you checked the baudrate, did you looked at the windbg client machine (
where the windbg client window is running = not on the target machine )

-pro

On 9/11/07, Ming-I Hsieh wrote:
>
> Hi, Prokashs
>
> I had just checked the baudrate settings in bcdedit and device
> manager. It’s right, 115200. However, I don’t think the problem was
> incurred from baudrate because I don’t see anything in AccessPort. If
> the baudrate is wrong, the AccessPort should report some garbage, but
> nothing now.
>
> BTW, had any suggestion for 1394 card for Vista? The null modem had
> taken too much time. If 1394 is working, I think I will give up null
> modem to keep my schedule.
>
> Regards, Mihs
>
> Quoting Prokash Sinha :
>
> > Can you check the port’s baudrate setting on the client. Control
> > Panel->Systems and Maintenance -> Device manager -> Ports -> COM1 (Right
> clk
> > and see properties ).
> >
> > That’s all I can think of.
> >
> > Also from the client side, you use the resynch using windbg menu to see
> if
> > any of the baud rate takes …
> >
> > -pro
> >
> >
> > On 9/11/07, Ming-I Hsieh wrote:
> >>
> >> Hi, Prokash
> >>
> >> I had just checked it according to ur suggestion with a clear Vista
> >> (no bluetooth, no virtual serial port and any additional softwares).
> >> But it still does not work.
> >>
> >> Microsoft (R) Windows Debugger Version 6.7.0005.1
> >> Copyright (c) Microsoft Corporation. All rights reserved.
> >>
> >> Opened \.\com1
> >> Waiting to reconnect…
> >>
> >> While windbg in host computer is always the initial message, and there
> >> is not message from target computer via null modem, I think there is
> >> some issue to incur the target computer does not send message to host
> >> computer. But the same environment is work if I changed the OS of
> >> target to XP or 2k. XD
> >>
> >> Regards, Mihs
> >>
> >> Quoting xxxxx@garlic.com:
> >>
> >> > Can you disable the virtual serials ( bluetooh ones) and then restart
> >> the
> >> > client, then hit cntl+break couple times to see if those few lines
> are
> >> > being spewed out or not …
> >> >
> >> > -pro
> >> >
> >> >
> >> >> Hi, alberto.
> >> >>
> >> >> Thanks for ur suggestion. I had checked it before with a clear
> >> >> Vista(w/o any additional software and only 1 serial port, COM1). But
> >> >> it does not work. If I could not solve this problem in this week, I
> >> >> think I will buy a 1394 for trying since my notebook.
> >> >>
> >> >> Regards, Mihs
> >> >>
> >> >> Quoting Alberto Moreira :
> >> >>
> >> >>> Hi, Mihs,
> >> >>>
> >> >>> On your Vista Target, you can try an F8 boot (press F8 immediately
> >> >>> after the Bios messages disappear from the screen) and you get a
> list
> >> >>> of choices, one of them being to Run with Debugging on. Maybe
> that’s
> >> >>> what’s missing, I don’t know. I do this with 1394 and it works
> fine.
> >> >>>
> >> >>> Alberto.
> >> >>>
> >> >>>
> >> >>> ----- Original Message ----- From: “Ming-I Hsieh”
> >> >>>
> >> >>> To: “Windows System Software Devs Interest List” <
> xxxxx@lists.osr.com>
> >> >>> Sent: Tuesday, September 11, 2007 9:49 PM
> >> >>> Subject: [ntdev] Cannot debug Windows Vista via Null Modem
> >> >>>
> >> >>>
> >> >>> Hi, All
> >> >>>
> >> >>> I had read the help of WinDbg for several days. However, I could
> not
> >> >>> debug kernel from a remote computer. In my environment, the target
> >> >>> computer is a PC with Win2k, WinXP and Vista. (all OSes had been
> >> >>> updated to latest.) The host computer is a Notebook with WinXP, USB
> >> >>> serial port, and these two computers are connected using Null Modem
> >> >>> 115200 8N1. This configuration is working fine for Win2k and WinXP.
> >> >>> After the target computer starts, I could get the message like
> >> >>>
> >> >>> Opened \.\com1
> >> >>> Waiting to reconnect…
> >> >>> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
> >> >>> Kernel Debugger connection established.
> >> >>> Symbol search path is:
> >> >>> C:\Windows\Symbols;SRVD:\localsymbols
> >> http://msdl.microsoft.com/download/symbols
> >> >>> Executable search path is:
> >> >>> Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
> >> >>> Built by: 2600.xpsp_sp2_gdr.070227-2254
> >> >>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
> >> >>> System Uptime: not available
> >> >>>
> >> >>> However, in Vista I didn’t get anything from it. Even if I open a
> >> >>> PuTTY to monitor the serial port. Vista does not send anything to
> the
> >> >>> port, but XP and 2k do.
> >> >>>
> >> >>> Could anyone give me some suggestion to set my Vista to enable
> kernel
> >> >>> debugging via serial port. I set my Vista using following commands
> >> >>>
> >> >>> Microsoft Windows [Version 6.0.6000] - Windows Vista Enterprise
> from
> >> >>> MSDN
> >> >>>
> >> >>> D:&gt;bcdedit /bootdebug on
> >> >>> The operation completed successfully.
> >> >>>
> >> >>> D:&gt;bcdedit /debug on
> >> >>> The operation completed successfully.
> >> >>>
> >> >>> D:&gt;bcdedit /dbgsettings
> >> >>> debugtype Serial
> >> >>> debugport 1
> >> >>> baudrate 115200
> >> >>>
> >> >>> I also test if bootdebug or debug is off. However, there is still
> no
> >> >>> message sent from Vista. I had checked the serial port. The serial
> >> >>> port works fine under Vista with PuTTY, and the target computer
> only
> >> >>> got 3 serial port, COM1(phyiscal), COM20/COM21(bluetooth virtual
> >> >>> serial port). Hence, I think there are some mistakes on my Vista
> >> >>> settings. any suggestion? thanks.
> >> >>>
> >> >>> Regards, Mihs
> >> >>>
> >> >>> ----------------------------------------------------------------
> >> >>> This message was sent using IMP, the Internet Messaging Program.
> >> >>>
> >> >>>
> >> >>>
> >> >>> —
> >> >>> NTDEV is sponsored by OSR
> >> >>>
> >> >>> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> >>> http://www.osr.com/seminars
> >> >>>
> >> >>> To unsubscribe, visit the List Server section of OSR Online at
> >> >>> http://www.osronline.com/page.cfm?name=ListServer —
> >> >>> NTDEV is sponsored by OSR
> >> >>>
> >> >>> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> >>> http://www.osr.com/seminars
> >> >>>
> >> >>> To unsubscribe, visit the List Server section of OSR Online at
> >> >>> http://www.osronline.com/page.cfm?name=ListServer
> >> >>
> >> >>
> >> >>
> >> >> ----------------------------------------------------------------
> >> >> This message was sent using IMP, the Internet Messaging Program.
> >> >>
> >> >>
> >> >>
> >> >> —
> >> >> NTDEV is sponsored by OSR
> >> >>
> >> >> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> >> http://www.osr.com/seminars
> >> >>
> >> >> To unsubscribe, visit the List Server section of OSR Online at
> >> >> http://www.osronline.com/page.cfm?name=ListServer
> >> >>
> >> >
> >> >
> >> >
> >> > —
> >> > NTDEV is sponsored by OSR
> >> >
> >> > For our schedule of WDF, WDM, debugging and other seminars visit:
> >> > http://www.osr.com/seminars
> >> >
> >> > To unsubscribe, visit the List Server section of OSR Online at
> >> > http://www.osronline.com/page.cfm?name=ListServer
> >> >
> >>
> >>
> >>
> >> ----------------------------------------------------------------
> >> This message was sent using IMP, the Internet Messaging Program.
> >>
> >>
> >>
> >> —
> >> NTDEV is sponsored by OSR
> >>
> >> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> http://www.osr.com/seminars
> >>
> >> To unsubscribe, visit the List Server section of OSR Online at
> >> http://www.osronline.com/page.cfm?name=ListServer
> >>
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

9

Hi, Prokash

No, I checked the Vista machine. The host computer with windbg is Windows XP.

Regards, Mihs

Quoting Prokash Sinha :

> I know 1394 works usually.
>
> When you checked the baudrate, did you looked at the windbg client machine (
> where the windbg client window is running = not on the target machine )
>
> -pro
>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

10

The baud rate has to match to see anything from the target to the client
over null-serial …

Please check that too.

-pro

On 9/11/07, Ming-I Hsieh wrote:
>
> Hi, Prokash
>
> No, I checked the Vista machine. The host computer with windbg is Windows
> XP.
>
> Regards, Mihs
>
> Quoting Prokash Sinha :
>
> > I know 1394 works usually.
> >
> > When you checked the baudrate, did you looked at the windbg client
> machine (
> > where the windbg client window is running = not on the target machine )
> >
> > -pro
> >
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

11

Hi, Prokash

The default settings of both machines (in Device Manager) had been
changed as 115200 8N1. But Vista is still not sending anything to the
host computer. Actually, I think the biggest problem is not baudrate
since AccessPort does not report anything. If the baudrate is wrong
and the configuration is fine, some garbage should appear in
AccessPort, but nothing now.

Anyway, if null modem is not working for Vista, I could buy a 1394
card for kernel debugging, and leave null modem to debug XP and 2k. In
recent days, I had checked all parameters which I could find out and
any parameters are right, even if the help of Debug Tools for Windows
is a little old for Vista RTM. In this moment, I am interesting if
anyone is success to enable kernel debugger for Vista via null modem,
or this function is broken?

Regards, Mihs

Quoting Prokash Sinha :

> The baud rate has to match to see anything from the target to the client
> over null-serial …
>
> Please check that too.
>
> -pro
>
>
> On 9/11/07, Ming-I Hsieh wrote:
>>
>> Hi, Prokash
>>
>> No, I checked the Vista machine. The host computer with windbg is Windows
>> XP.
>>
>> Regards, Mihs
>>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

12

Can you get a simple communication loop working, with HyperTerminal or
similar things? This sounds like a setup problem, so condsider the
following:

On the host, Verify the com port things are connected to, remember
this is the com port you put in WinDBG not the one you put in BcdEdit.
On the target verify that the com port specified in Bcdedit is the
correct com port. REMEMBER, JUST BECAUSE A MACHINE HAS ONE COM PORT DOES
NOT GUARANTEE IT IS COM1
Try a link with a slow speed of something like 19200 with
hyperterminal, if that works try the debugger with the same settings.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

13

Can you get the 2 systems to talk via hyperterminal?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Ming-I Hsieh
Sent: Wednesday, September 12, 2007 1:40 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Cannot debug Windows Vista via Null Modem

Hi, Prokash

The default settings of both machines (in Device Manager) had been
changed as 115200 8N1. But Vista is still not sending anything to the
host computer. Actually, I think the biggest problem is not baudrate
since AccessPort does not report anything. If the baudrate is wrong
and the configuration is fine, some garbage should appear in
AccessPort, but nothing now.

Anyway, if null modem is not working for Vista, I could buy a 1394
card for kernel debugging, and leave null modem to debug XP and 2k. In
recent days, I had checked all parameters which I could find out and
any parameters are right, even if the help of Debug Tools for Windows
is a little old for Vista RTM. In this moment, I am interesting if
anyone is success to enable kernel debugger for Vista via null modem,
or this function is broken?

Regards, Mihs

Quoting Prokash Sinha :

> The baud rate has to match to see anything from the target to the client
> over null-serial …
>
> Please check that too.
>
> -pro
>
>
> On 9/11/07, Ming-I Hsieh wrote:
>>
>> Hi, Prokash
>>
>> No, I checked the Vista machine. The host computer with windbg is Windows
>> XP.
>>
>> Regards, Mihs
>>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

14

Hi, Burn:

Thanks for ur suggestions. I had checked the port is bound at com1,
and the null modem is working fine for WinXP/Win2K with kernel
debugging/hyperterminal, and Vista for hyperteriminal. However, it
does not work for Vista with kernel debugging.

Hence, I think the hardware is fine since the target machine with 3
OSes, Win2K, WinXP, and Vista. But there is only Vista does not work
for kernel debugging. However, other functions are working fine.

For a slow baudrate, I will check it tomorrow. But I think it’s not
work since nothing was sent out from Vista via serial port. But in
this moment, I had no solutions for this null modem, and I will check
it. Anyway, I think it’s time to order a IEEE1394 card for target
machine to make the kernel debugging work since null modem is never
the key issue for my development schedule.

Of course, if it works, it would be better. :smiley:

Regards, Mihs

Quoting Don Burn :

> Can you get a simple communication loop working, with HyperTerminal or
> similar things? This sounds like a setup problem, so condsider the
> following:
>
> On the host, Verify the com port things are connected to, remember
> this is the com port you put in WinDBG not the one you put in BcdEdit.
> On the target verify that the com port specified in Bcdedit is the
> correct com port. REMEMBER, JUST BECAUSE A MACHINE HAS ONE COM PORT DOES
> NOT GUARANTEE IT IS COM1
> Try a link with a slow speed of something like 19200 with
> hyperterminal, if that works try the debugger with the same settings.
>
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

15

Hi Mark:

Yes, the hyperterminal works fine while the target computer is Vista,
XP, or Win2K. I think the basic settings for the serial port is right
except the kernel debugging for Vista. Actually, everything is fine
except the kernel debugging of Vista via null modem.

Regards, Mihs

Quoting Mark Rodriquez :

> Can you get the 2 systems to talk via hyperterminal?
>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

16

I have been doing debug on vista for several months, so I know that it works. Have you rechecked your BCDEDIT settings?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Ming-I Hsieh
Sent: Wednesday, September 12, 2007 11:15 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Cannot debug Windows Vista via Null Modem

Hi Mark:

Yes, the hyperterminal works fine while the target computer is Vista,
XP, or Win2K. I think the basic settings for the serial port is right
except the kernel debugging for Vista. Actually, everything is fine
except the kernel debugging of Vista via null modem.

Regards, Mihs

Quoting Mark Rodriquez :

> Can you get the 2 systems to talk via hyperterminal?
>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

17

Hi, Mark:

Ok, it’s glad to hear the system works for your computer. May u post
your bcdedit settings for me. Hence, I could try to set it via your
settings. In my machine, I had enable debug and dbgsettings. However,
it does not work.

Regards, Mihs

Quoting Mark Rodriquez :

> I have been doing debug on vista for several months, so I know that
> it works. Have you rechecked your BCDEDIT settings?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Ming-I Hsieh
> Sent: Wednesday, September 12, 2007 11:15 AM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] Cannot debug Windows Vista via Null Modem
>
> Hi Mark:
>
> Yes, the hyperterminal works fine while the target computer is Vista,
> XP, or Win2K. I think the basic settings for the serial port is right
> except the kernel debugging for Vista. Actually, everything is fine
> except the kernel debugging of Vista via null modem.
>
> Regards, Mihs
>
> Quoting Mark Rodriquez :
>
>> Can you get the 2 systems to talk via hyperterminal?
>>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

18

Make sure it’s a TI chipset, or get it from th e OSROnline website.

–
The personal opinion of
Gary G. Little

“Ming-I Hsieh” wrote in message
news:xxxxx@ntdev…
Hi, Prokashs

I had just checked the baudrate settings in bcdedit and device
manager. It’s right, 115200. However, I don’t think the problem was
incurred from baudrate because I don’t see anything in AccessPort. If
the baudrate is wrong, the AccessPort should report some garbage, but
nothing now.

BTW, had any suggestion for 1394 card for Vista? The null modem had
taken too much time. If 1394 is working, I think I will give up null
modem to keep my schedule.

Regards, Mihs

Quoting Prokash Sinha :

> Can you check the port’s baudrate setting on the client. Control
> Panel->Systems and Maintenance -> Device manager -> Ports -> COM1 (Right
> clk
> and see properties ).
>
> That’s all I can think of.
>
> Also from the client side, you use the resynch using windbg menu to see if
> any of the baud rate takes …
>
> -pro
>
>
> On 9/11/07, Ming-I Hsieh wrote:
>>
>> Hi, Prokash
>>
>> I had just checked it according to ur suggestion with a clear Vista
>> (no bluetooth, no virtual serial port and any additional softwares).
>> But it still does not work.
>>
>> Microsoft (R) Windows Debugger Version 6.7.0005.1
>> Copyright (c) Microsoft Corporation. All rights reserved.
>>
>> Opened \.\com1
>> Waiting to reconnect…
>>
>> While windbg in host computer is always the initial message, and there
>> is not message from target computer via null modem, I think there is
>> some issue to incur the target computer does not send message to host
>> computer. But the same environment is work if I changed the OS of
>> target to XP or 2k. XD
>>
>> Regards, Mihs
>>
>> Quoting xxxxx@garlic.com:
>>
>> > Can you disable the virtual serials ( bluetooh ones) and then restart
>> the
>> > client, then hit cntl+break couple times to see if those few lines are
>> > being spewed out or not …
>> >
>> > -pro
>> >
>> >
>> >> Hi, alberto.
>> >>
>> >> Thanks for ur suggestion. I had checked it before with a clear
>> >> Vista(w/o any additional software and only 1 serial port, COM1). But
>> >> it does not work. If I could not solve this problem in this week, I
>> >> think I will buy a 1394 for trying since my notebook.
>> >>
>> >> Regards, Mihs
>> >>
>> >> Quoting Alberto Moreira :
>> >>
>> >>> Hi, Mihs,
>> >>>
>> >>> On your Vista Target, you can try an F8 boot (press F8 immediately
>> >>> after the Bios messages disappear from the screen) and you get a list
>> >>> of choices, one of them being to Run with Debugging on. Maybe that’s
>> >>> what’s missing, I don’t know. I do this with 1394 and it works fine.
>> >>>
>> >>> Alberto.
>> >>>
>> >>>
>> >>> ----- Original Message ----- From: “Ming-I Hsieh”
>> >>>
>> >>> To: “Windows System Software Devs Interest List”
>> >>>
>> >>> Sent: Tuesday, September 11, 2007 9:49 PM
>> >>> Subject: [ntdev] Cannot debug Windows Vista via Null Modem
>> >>>
>> >>>
>> >>> Hi, All
>> >>>
>> >>> I had read the help of WinDbg for several days. However, I could not
>> >>> debug kernel from a remote computer. In my environment, the target
>> >>> computer is a PC with Win2k, WinXP and Vista. (all OSes had been
>> >>> updated to latest.) The host computer is a Notebook with WinXP, USB
>> >>> serial port, and these two computers are connected using Null Modem
>> >>> 115200 8N1. This configuration is working fine for Win2k and WinXP.
>> >>> After the target computer starts, I could get the message like
>> >>>
>> >>> Opened \.\com1
>> >>> Waiting to reconnect…
>> >>> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
>> >>> Kernel Debugger connection established.
>> >>> Symbol search path is:
>> >>> C:\Windows\Symbols;SRVD:\localsymbols
>> http://msdl.microsoft.com/download/symbols
>> >>> Executable search path is:
>> >>> Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
>> >>> Built by: 2600.xpsp_sp2_gdr.070227-2254
>> >>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
>> >>> System Uptime: not available
>> >>>
>> >>> However, in Vista I didn’t get anything from it. Even if I open a
>> >>> PuTTY to monitor the serial port. Vista does not send anything to the
>> >>> port, but XP and 2k do.
>> >>>
>> >>> Could anyone give me some suggestion to set my Vista to enable kernel
>> >>> debugging via serial port. I set my Vista using following commands
>> >>>
>> >>> Microsoft Windows [Version 6.0.6000] - Windows Vista Enterprise from
>> >>> MSDN
>> >>>
>> >>> D:&gt;bcdedit /bootdebug on
>> >>> The operation completed successfully.
>> >>>
>> >>> D:&gt;bcdedit /debug on
>> >>> The operation completed successfully.
>> >>>
>> >>> D:&gt;bcdedit /dbgsettings
>> >>> debugtype Serial
>> >>> debugport 1
>> >>> baudrate 115200
>> >>>
>> >>> I also test if bootdebug or debug is off. However, there is still no
>> >>> message sent from Vista. I had checked the serial port. The serial
>> >>> port works fine under Vista with PuTTY, and the target computer only
>> >>> got 3 serial port, COM1(phyiscal), COM20/COM21(bluetooth virtual
>> >>> serial port). Hence, I think there are some mistakes on my Vista
>> >>> settings. any suggestion? thanks.
>> >>>
>> >>> Regards, Mihs
>> >>>
>> >>> ----------------------------------------------------------------
>> >>> This message was sent using IMP, the Internet Messaging Program.
>> >>>
>> >>>
>> >>>
>> >>> —
>> >>> NTDEV is sponsored by OSR
>> >>>
>> >>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> >>> http://www.osr.com/seminars
>> >>>
>> >>> To unsubscribe, visit the List Server section of OSR Online at
>> >>> http://www.osronline.com/page.cfm?name=ListServer —
>> >>> NTDEV is sponsored by OSR
>> >>>
>> >>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> >>> http://www.osr.com/seminars
>> >>>
>> >>> To unsubscribe, visit the List Server section of OSR Online at
>> >>> http://www.osronline.com/page.cfm?name=ListServer
>> >>
>> >>
>> >>
>> >> ----------------------------------------------------------------
>> >> This message was sent using IMP, the Internet Messaging Program.
>> >>
>> >>
>> >>
>> >> —
>> >> NTDEV is sponsored by OSR
>> >>
>> >> For our schedule of WDF, WDM, debugging and other seminars visit:
>> >> http://www.osr.com/seminars
>> >>
>> >> To unsubscribe, visit the List Server section of OSR Online at
>> >> http://www.osronline.com/page.cfm?name=ListServer
>> >>
>> >
>> >
>> >
>> > —
>> > NTDEV is sponsored by OSR
>> >
>> > For our schedule of WDF, WDM, debugging and other seminars visit:
>> > http://www.osr.com/seminars
>> >
>> > To unsubscribe, visit the List Server section of OSR Online at
>> > http://www.osronline.com/page.cfm?name=ListServer
>> >
>>
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

19

That really does not answer Don’s overlying question: Can you get Vista
Hyterterminal talkiing to the XP HyperTerminal?

The 1394 switch, is the best solution, though.

–
The personal opinion of
Gary G. Little

“Ming-I Hsieh” wrote in message
news:xxxxx@ntdev…
Hi, Burn:

Thanks for ur suggestions. I had checked the port is bound at com1,
and the null modem is working fine for WinXP/Win2K with kernel
debugging/hyperterminal, and Vista for hyperteriminal. However, it
does not work for Vista with kernel debugging.

Hence, I think the hardware is fine since the target machine with 3
OSes, Win2K, WinXP, and Vista. But there is only Vista does not work
for kernel debugging. However, other functions are working fine.

For a slow baudrate, I will check it tomorrow. But I think it’s not
work since nothing was sent out from Vista via serial port. But in
this moment, I had no solutions for this null modem, and I will check
it. Anyway, I think it’s time to order a IEEE1394 card for target
machine to make the kernel debugging work since null modem is never
the key issue for my development schedule.

Of course, if it works, it would be better. :smiley:

Regards, Mihs

Quoting Don Burn :

> Can you get a simple communication loop working, with HyperTerminal or
> similar things? This sounds like a setup problem, so condsider the
> following:
>
> On the host, Verify the com port things are connected to, remember
> this is the com port you put in WinDBG not the one you put in BcdEdit.
> On the target verify that the com port specified in Bcdedit is the
> correct com port. REMEMBER, JUST BECAUSE A MACHINE HAS ONE COM PORT DOES
> NOT GUARANTEE IT IS COM1
> Try a link with a slow speed of something like 19200 with
> hyperterminal, if that works try the debugger with the same settings.
>
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

20

Well, Mr. Little, next time read the entire thread before you post …
sheeesh …

–
The personal opinion of
Gary G. Little

“Gary G. Little” wrote in message
news:xxxxx@ntdev…
> Make sure it’s a TI chipset, or get it from th e OSROnline website.
>
> –
> The personal opinion of
> Gary G. Little
>
> “Ming-I Hsieh” wrote in message
> news:xxxxx@ntdev…
> Hi, Prokashs
>
> I had just checked the baudrate settings in bcdedit and device
> manager. It’s right, 115200. However, I don’t think the problem was
> incurred from baudrate because I don’t see anything in AccessPort. If
> the baudrate is wrong, the AccessPort should report some garbage, but
> nothing now.
>
> BTW, had any suggestion for 1394 card for Vista? The null modem had
> taken too much time. If 1394 is working, I think I will give up null
> modem to keep my schedule.
>
> Regards, Mihs
>
> Quoting Prokash Sinha :
>
>> Can you check the port’s baudrate setting on the client. Control
>> Panel->Systems and Maintenance -> Device manager -> Ports -> COM1 (Right
>> clk
>> and see properties ).
>>
>> That’s all I can think of.
>>
>> Also from the client side, you use the resynch using windbg menu to see
>> if
>> any of the baud rate takes …
>>
>> -pro
>>
>>
>> On 9/11/07, Ming-I Hsieh wrote:
>>>
>>> Hi, Prokash
>>>
>>> I had just checked it according to ur suggestion with a clear Vista
>>> (no bluetooth, no virtual serial port and any additional softwares).
>>> But it still does not work.
>>>
>>> Microsoft (R) Windows Debugger Version 6.7.0005.1
>>> Copyright (c) Microsoft Corporation. All rights reserved.
>>>
>>> Opened \.\com1
>>> Waiting to reconnect…
>>>
>>> While windbg in host computer is always the initial message, and there
>>> is not message from target computer via null modem, I think there is
>>> some issue to incur the target computer does not send message to host
>>> computer. But the same environment is work if I changed the OS of
>>> target to XP or 2k. XD
>>>
>>> Regards, Mihs
>>>
>>> Quoting xxxxx@garlic.com:
>>>
>>> > Can you disable the virtual serials ( bluetooh ones) and then restart
>>> the
>>> > client, then hit cntl+break couple times to see if those few lines are
>>> > being spewed out or not …
>>> >
>>> > -pro
>>> >
>>> >
>>> >> Hi, alberto.
>>> >>
>>> >> Thanks for ur suggestion. I had checked it before with a clear
>>> >> Vista(w/o any additional software and only 1 serial port, COM1). But
>>> >> it does not work. If I could not solve this problem in this week, I
>>> >> think I will buy a 1394 for trying since my notebook.
>>> >>
>>> >> Regards, Mihs
>>> >>
>>> >> Quoting Alberto Moreira :
>>> >>
>>> >>> Hi, Mihs,
>>> >>>
>>> >>> On your Vista Target, you can try an F8 boot (press F8 immediately
>>> >>> after the Bios messages disappear from the screen) and you get a
>>> >>> list
>>> >>> of choices, one of them being to Run with Debugging on. Maybe that’s
>>> >>> what’s missing, I don’t know. I do this with 1394 and it works fine.
>>> >>>
>>> >>> Alberto.
>>> >>>
>>> >>>
>>> >>> ----- Original Message ----- From: “Ming-I Hsieh”
>>> >>>
>>> >>> To: “Windows System Software Devs Interest List”
>>> >>>
>>> >>> Sent: Tuesday, September 11, 2007 9:49 PM
>>> >>> Subject: [ntdev] Cannot debug Windows Vista via Null Modem
>>> >>>
>>> >>>
>>> >>> Hi, All
>>> >>>
>>> >>> I had read the help of WinDbg for several days. However, I could not
>>> >>> debug kernel from a remote computer. In my environment, the target
>>> >>> computer is a PC with Win2k, WinXP and Vista. (all OSes had been
>>> >>> updated to latest.) The host computer is a Notebook with WinXP, USB
>>> >>> serial port, and these two computers are connected using Null Modem
>>> >>> 115200 8N1. This configuration is working fine for Win2k and WinXP.
>>> >>> After the target computer starts, I could get the message like
>>> >>>
>>> >>> Opened \.\com1
>>> >>> Waiting to reconnect…
>>> >>> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
>>> >>> Kernel Debugger connection established.
>>> >>> Symbol search path is:
>>> >>> C:\Windows\Symbols;SRVD:\localsymbols
>>> http://msdl.microsoft.com/download/symbols
>>> >>> Executable search path is:
>>> >>> Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
>>> >>> Built by: 2600.xpsp_sp2_gdr.070227-2254
>>> >>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
>>> >>> System Uptime: not available
>>> >>>
>>> >>> However, in Vista I didn’t get anything from it. Even if I open a
>>> >>> PuTTY to monitor the serial port. Vista does not send anything to
>>> >>> the
>>> >>> port, but XP and 2k do.
>>> >>>
>>> >>> Could anyone give me some suggestion to set my Vista to enable
>>> >>> kernel
>>> >>> debugging via serial port. I set my Vista using following commands
>>> >>>
>>> >>> Microsoft Windows [Version 6.0.6000] - Windows Vista Enterprise from
>>> >>> MSDN
>>> >>>
>>> >>> D:&gt;bcdedit /bootdebug on
>>> >>> The operation completed successfully.
>>> >>>
>>> >>> D:&gt;bcdedit /debug on
>>> >>> The operation completed successfully.
>>> >>>
>>> >>> D:&gt;bcdedit /dbgsettings
>>> >>> debugtype Serial
>>> >>> debugport 1
>>> >>> baudrate 115200
>>> >>>
>>> >>> I also test if bootdebug or debug is off. However, there is still no
>>> >>> message sent from Vista. I had checked the serial port. The serial
>>> >>> port works fine under Vista with PuTTY, and the target computer only
>>> >>> got 3 serial port, COM1(phyiscal), COM20/COM21(bluetooth virtual
>>> >>> serial port). Hence, I think there are some mistakes on my Vista
>>> >>> settings. any suggestion? thanks.
>>> >>>
>>> >>> Regards, Mihs
>>> >>>
>>> >>> ----------------------------------------------------------------
>>> >>> This message was sent using IMP, the Internet Messaging Program.
>>> >>>
>>> >>>
>>> >>>
>>> >>> —
>>> >>> NTDEV is sponsored by OSR
>>> >>>
>>> >>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> >>> http://www.osr.com/seminars
>>> >>>
>>> >>> To unsubscribe, visit the List Server section of OSR Online at
>>> >>> http://www.osronline.com/page.cfm?name=ListServer —
>>> >>> NTDEV is sponsored by OSR
>>> >>>
>>> >>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> >>> http://www.osr.com/seminars
>>> >>>
>>> >>> To unsubscribe, visit the List Server section of OSR Online at
>>> >>> http://www.osronline.com/page.cfm?name=ListServer
>>> >>
>>> >>
>>> >>
>>> >> ----------------------------------------------------------------
>>> >> This message was sent using IMP, the Internet Messaging Program.
>>> >>
>>> >>
>>> >>
>>> >> —
>>> >> NTDEV is sponsored by OSR
>>> >>
>>> >> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> >> http://www.osr.com/seminars
>>> >>
>>> >> To unsubscribe, visit the List Server section of OSR Online at
>>> >> http://www.osronline.com/page.cfm?name=ListServer
>>> >>
>>> >
>>> >
>>> >
>>> > —
>>> > NTDEV is sponsored by OSR
>>> >
>>> > For our schedule of WDF, WDM, debugging and other seminars visit:
>>> > http://www.osr.com/seminars
>>> >
>>> > To unsubscribe, visit the List Server section of OSR Online at
>>> > http://www.osronline.com/page.cfm?name=ListServer
>>> >
>>>
>>>
>>>
>>> ----------------------------------------------------------------
>>> This message was sent using IMP, the Internet Messaging Program.
>>>
>>>
>>>
>>> —
>>> NTDEV is sponsored by OSR
>>>
>>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> http://www.osr.com/seminars
>>>
>>> To unsubscribe, visit the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer
>>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
>
>