Not able to connect windbg on win7-32bits(test-pc)->winxp-32bits(dev-pc).

Hi,
I am trying to debug using com port(only option available), win7-32bits as
test machine and XP-32bits as Dev-PC using windbg but not able to create
debug connection. I have looked for all possible options, I have
enabled debug option properly, cheked cable(com cable) is working(on XP to
XP) but it is still not working.

My doubts:

  1. Is XP to win 7 debugging not allowed?
  2. Is any special setting required for Win 7?

*Note: With same pair of systems and same com cable I am able to debug when
both the systems have XP-32bits.*

Any input will help a lot.

/sarbojit

  1. Just to be clear, what’s happening when you start windbg?

  2. What was your bcdedit command line and what was your windbg
    command line?

mm

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Sarbojit Sarkar
Sent: Monday, July 26, 2010 9:44 AM
To: Kernel Debugging Interest List
Subject: [windbg] Not able to connect windbg on
win7-32bits(test-pc)->winxp-32bits(dev-pc).

Hi,

I am trying to debug using com port(only option available), win7-32bits as
test machine and XP-32bits as Dev-PC using windbg but not able to create
debug connection. I have looked for all possible options, I have enabled
debug option properly, cheked cable(com cable) is working(on XP to XP) but
it is still not working.

My doubts:

  1. Is XP to win 7 debugging not allowed?

  2. Is any special setting required for Win 7?

Note: With same pair of systems and same com cable I am able to debug when
both the systems have XP-32bits.

Any input will help a lot.

/sarbojit

— WINDBG 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

*Debugger is showing below message.*

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

Opened \.\COM1
Waiting to reconnect...

*bcdedit cmd line....*
C:\Users\Administrator>bcdedit

Windows Boot Manager

identifier {bootmgr}
device partition=D:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {5df2a356-9887-11df-aad3-85a2e8dd1651}
displayorder {ntldr}
{current}
toolsdisplayorder {memdiag}
timeout 30

Windows Legacy OS Loader

identifier {ntldr}
device partition=D:
path \ntldr
description Earlier Version of Windows

Windows Boot Loader

identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {5df2a358-9887-11df-aad3-85a2e8dd1651}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {5df2a356-9887-11df-aad3-85a2e8dd1651}
nx OptIn
usefirmwarepcisettings No
debug Yes

/sarbojit

On Tue, Jul 27, 2010 at 12:16 AM, M. M. O'Brien <
xxxxx@gmail.com> wrote:

  1. Just to be clear, what?s happening when you start windbg?

  2. What was your bcdedit command line and what was your windbg
    command line?

mm

*From:* xxxxx@lists.osr.com [mailto:
xxxxx@lists.osr.com] *On Behalf Of *Sarbojit Sarkar
*Sent:* Monday, July 26, 2010 9:44 AM
*To:* Kernel Debugging Interest List
*Subject:* [windbg] Not able to connect windbg on
win7-32bits(test-pc)->winxp-32bits(dev-pc).

Hi,

I am trying to debug using com port(only option available), win7-32bits
as test machine and XP-32bits as Dev-PC using windbg but not able to create
debug connection. I have looked for all possible options, I have
enabled debug option properly, cheked cable(com cable) is working(on XP to
XP) but it is still not working.

My doubts:

  1. Is XP to win 7 debugging not allowed?

  2. Is any special setting required for Win 7?

*Note: With same pair of systems and same com cable I am able to
debug when both the systems have XP-32bits.*

Any input will help a lot.

/sarbojit

--- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
other seminars visit: OSR Seminars – OSR To unsubscribe, visit
the List Server section of OSR Online at
ListServer/Forum


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
OSR Seminars – OSR

To unsubscribe, visit the List Server section of OSR Online at
ListServer/Forum

what’s your configuration for COM port and baudrate in debuger and debugee?
are you sure the COM connection line works fine?
if everything is fine, then click: “CTRL” + “BREAK” to start the debug.

Wan

On Tue, Jul 27, 2010 at 1:28 AM, Sarbojit Sarkar wrote:

> Debugger is showing below message.
>
> Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Opened \.\COM1
> Waiting to reconnect…
>
> bcdedit cmd line…
> C:\Users\Administrator>bcdedit
>
> Windows Boot Manager
> --------------------
> identifier {bootmgr}
> device partition=D:
> description Windows Boot Manager
> locale en-US
> inherit {globalsettings}
> default {current}
> resumeobject {5df2a356-9887-11df-aad3-85a2e8dd1651}
> displayorder {ntldr}
> {current}
> toolsdisplayorder {memdiag}
> timeout 30
>
> Windows Legacy OS Loader
> ------------------------
> identifier {ntldr}
> device partition=D:
> path \ntldr
> description Earlier Version of Windows
>
> Windows Boot Loader
> -------------------
> identifier {current}
> device partition=C:
> path \Windows\system32\winload.exe
> description Windows 7
> locale en-US
> inherit {bootloadersettings}
> recoverysequence {5df2a358-9887-11df-aad3-85a2e8dd1651}
> recoveryenabled Yes
> osdevice partition=C:
> systemroot \Windows
> resumeobject {5df2a356-9887-11df-aad3-85a2e8dd1651}
> nx OptIn
> usefirmwarepcisettings No
> debug Yes
>
> /sarbojit
>
> On Tue, Jul 27, 2010 at 12:16 AM, M. M. O’Brien <
> xxxxx@gmail.com> wrote:
>
>> 1. Just to be clear, what’s happening when you start windbg?
>>
>> 2. What was your bcdedit command line and what was your windbg
>> command line?
>>
>>
>>
>> mm
>>
>>
>>
>> From: xxxxx@lists.osr.com [mailto:
>> xxxxx@lists.osr.com] *On Behalf Of *Sarbojit Sarkar
>> Sent: Monday, July 26, 2010 9:44 AM
>> To: Kernel Debugging Interest List
>> Subject: [windbg] Not able to connect windbg on
>> win7-32bits(test-pc)->winxp-32bits(dev-pc).
>>
>>
>>
>> Hi,
>>
>> I am trying to debug using com port(only option available), win7-32bits
>> as test machine and XP-32bits as Dev-PC using windbg but not able to create
>> debug connection. I have looked for all possible options, I have
>> enabled debug option properly, cheked cable(com cable) is working(on XP to
>> XP) but it is still not working.
>>
>>
>>
>> My doubts:
>>
>> 1. Is XP to win 7 debugging not allowed?
>>
>> 2. Is any special setting required for Win 7?
>>
>>
>>
>> Note: With same pair of systems and same com cable I am able to
>> debug when both the systems have XP-32bits.

>>
>>
>>
>> Any input will help a lot.
>>
>>
>>
>> /sarbojit
>>
>> — WINDBG 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
>>
>> —
>> WINDBG 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
>>
>
> — WINDBG 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
>

Sarbojit Sarkar wrote:

*Debugger is showing below message.*

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

Opened \.\COM1
Waiting to reconnect…

OK, so windbg thinks you want to debug using COM1. That’s fine.
However, according to your bcdedit output, you haven’t configured the
debug target to do debugging over a COM port. Did you use bcdedit to
set up a COM port, and set up the baud rate?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Indeed. Also, you might want to check /dbgsettings.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, July 27, 2010 12:16 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Not able to connect windbg on
win7-32bits(test-pc)->winxp-32bits(dev-pc).

Sarbojit Sarkar wrote:

*Debugger is showing below message.*

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

Opened \.\COM1
Waiting to reconnect…

OK, so windbg thinks you want to debug using COM1. That’s fine.
However, according to your bcdedit output, you haven’t configured the debug
target to do debugging over a COM port. Did you use bcdedit to set up a COM
port, and set up the baud rate?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


WINDBG 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

Sorry for late response.

Tim said,

> according to your bcdedit output, you haven’t configured the
>debug target to do debugging over a COM port.
Could you please let me where exactly you have found this? Because when I am
using /dbgsettings cmd it is showing,

debugtype Serial
debugport 1
baudrate 115200

Well my system is having win7-32bits & Winxp-32bits both OSes. I have
installed XP in c drive and Win7 in d drive but I have noticed that when I
boot the system in win7 it is showing current directory as C drive only and
when I boot in XP it is also showing current directory as c drive only.
Please let me know if this can be a issue.

When I boot the system in XP I am able to connect with same debug com port
cable so I am sure that cable is not a culprit here.

I am dumping the current settings here again. Please let me know if any
thing I am missing here.

On Tue, Jul 27, 2010 at 9:52 PM, M. M. O’Brien <
xxxxx@gmail.com> wrote:

Indeed. Also, you might want to check /dbgsettings.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, July 27, 2010 12:16 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Not able to connect windbg on
win7-32bits(test-pc)->winxp-32bits(dev-pc).

Sarbojit Sarkar wrote:
> *Debugger is showing below message.*
>
> Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c)
> Microsoft Corporation. All rights reserved.
>
> Opened \.\COM1
> Waiting to reconnect…

OK, so windbg thinks you want to debug using COM1. That’s fine.
However, according to your bcdedit output, you haven’t configured the debug
target to do debugging over a COM port. Did you use bcdedit to set up a
COM
port, and set up the baud rate?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


WINDBG 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


WINDBG 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

forgot to demp bcdedit cmd and /dbgsettings output.

C:\Users\Administrator>bcdedit

Windows Boot Manager

identifier {bootmgr}
device partition=D:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {5df2a356-9887-11df-aad3-85a2e8dd1651}
displayorder {ntldr}
{current}
toolsdisplayorder {memdiag}
timeout 30

Windows Legacy OS Loader

identifier {ntldr}
device partition=D:
path \ntldr
description Earlier Version of Windows

Windows Boot Loader

identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {5df2a358-9887-11df-aad3-85a2e8dd1651}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {5df2a356-9887-11df-aad3-85a2e8dd1651}
nx OptIn
usefirmwarepcisettings No
debug Yes

C:\Users\Administrator>bcdedit /dbgsettings
debugtype Serial
debugport 1
baudrate 115200
The operation completed successfully.

/sarbojit

On Wed, Aug 11, 2010 at 2:02 PM, Sarbojit Sarkar wrote:

> Sorry for late response.
>
> Tim said,
> >> according to your bcdedit output, you haven't configured the
> >>debug target to do debugging over a COM port.
> Could you please let me where exactly you have found this? Because when I
> am using /dbgsettings cmd it is showing,
>
> debugtype Serial
> debugport 1
> baudrate 115200
>
> Well my system is having win7-32bits & Winxp-32bits both OSes. I have
> installed XP in c drive and Win7 in d drive but I have noticed that when I
> boot the system in win7 it is showing current directory as C drive only and
> when I boot in XP it is also showing current directory as c drive only.
> Please let me know if this can be a issue.
>
> When I boot the system in XP I am able to connect with same debug com port
> cable so I am sure that cable is not a culprit here.
>
> I am dumping the current settings here again. Please let me know if any
> thing I am missing here.
>
>
> On Tue, Jul 27, 2010 at 9:52 PM, M. M. O'Brien <
> xxxxx@gmail.com> wrote:
>
>> Indeed. Also, you might want to check /dbgsettings.
>>
>>
>> mm
>>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
>> Sent: Tuesday, July 27, 2010 12:16 PM
>> To: Kernel Debugging Interest List
>> Subject: Re: [windbg] Not able to connect windbg on
>> win7-32bits(test-pc)->winxp-32bits(dev-pc).
>>
>> Sarbojit Sarkar wrote:
>> > Debugger is showing below message.
>> >
>> > Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c)
>> > Microsoft Corporation. All rights reserved.
>> >
>> > Opened \.\COM1
>> > Waiting to reconnect...
>>
>> OK, so windbg thinks you want to debug using COM1. That's fine.
>> However, according to your bcdedit output, you haven't configured the
>> debug
>> target to do debugging over a COM port. Did you use bcdedit to set up a
>> COM
>> port, and set up the baud rate?
>>
>> --
>> Tim Roberts, xxxxx@probo.com
>> Providenza & Boekelheide, Inc.
>>
>>
>> ---
>> WINDBG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> OSR Seminars – OSR
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> ListServer/Forum
>>
>>
>> ---
>> WINDBG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> OSR Seminars – OSR
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> ListServer/Forum
>>
>
>

It all looks OK to me…

Any chance the COM port number changes on the Win7 install? It’s a fairly
ridiculous guess on my part, but this problem is odd enough that it’s worth
checking.

-scott


Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Sarbojit Sarkar” wrote in message
news:xxxxx@windbg…
forgot to demp bcdedit cmd and /dbgsettings output.

C:\Users\Administrator>bcdedit

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=D:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {5df2a356-9887-11df-aad3-85a2e8dd1651}
displayorder {ntldr}
{current}
toolsdisplayorder {memdiag}
timeout 30

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=D:
path \ntldr
description Earlier Version of Windows

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {5df2a358-9887-11df-aad3-85a2e8dd1651}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {5df2a356-9887-11df-aad3-85a2e8dd1651}
nx OptIn
usefirmwarepcisettings No
debug Yes

C:\Users\Administrator>bcdedit /dbgsettings
debugtype Serial
debugport 1
baudrate 115200
The operation completed successfully.

/sarbojit

On Wed, Aug 11, 2010 at 2:02 PM, Sarbojit Sarkar
wrote:

Sorry for late response.

Tim said,
>> according to your bcdedit output, you haven’t configured the
>>debug target to do debugging over a COM port.
Could you please let me where exactly you have found this? Because when I am
using /dbgsettings cmd it is showing,

debugtype Serial
debugport 1
baudrate 115200

Well my system is having win7-32bits & Winxp-32bits both OSes. I have
installed XP in c drive and Win7 in d drive but I have noticed that when I
boot the system in win7 it is showing current directory as C drive only and
when I boot in XP it is also showing current directory as c drive only.
Please let me know if this can be a issue.

When I boot the system in XP I am able to connect with same debug com port
cable so I am sure that cable is not a culprit here.

I am dumping the current settings here again. Please let me know if any
thing I am missing here.

On Tue, Jul 27, 2010 at 9:52 PM, M. M. O’Brien
wrote:

Indeed. Also, you might want to check /dbgsettings.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, July 27, 2010 12:16 PM
To: Kernel Debugging Interest List

Subject: Re: [windbg] Not able to connect windbg on
win7-32bits(test-pc)->winxp-32bits(dev-pc).

Sarbojit Sarkar wrote:
> Debugger is showing below message.
>
> Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c)
> Microsoft Corporation. All rights reserved.
>
> Opened \.\COM1
> Waiting to reconnect…

OK, so windbg thinks you want to debug using COM1. That’s fine.
However, according to your bcdedit output, you haven’t configured the debug
target to do debugging over a COM port. Did you use bcdedit to set up a COM
port, and set up the baud rate?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


WINDBG 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


WINDBG 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

Sarbojit Sarkar wrote:

Tim said,
>> according to your bcdedit output, you haven’t configured the
>>debug target to do debugging over a COM port.
Could you please let me where exactly you have found this? Because
when I am using /dbgsettings cmd it is showing,

debugtype Serial
debugport 1
baudrate 115200

Sorry, I didn’t see that.

Well my system is having win7-32bits & Winxp-32bits both OSes. I have
installed XP in c drive and Win7 in d drive but I have noticed that
when I boot the system in win7 it is showing current directory as C
drive only and when I boot in XP it is also showing current directory
as c drive only. Please let me know if this can be a issue.

Nope. It’s not uncommon for a multi-boot installation to have this kind
of drive letter renumbering. Not important.

When I boot the system in XP I am able to connect with same debug com
port cable so I am sure that cable is not a culprit here.

And your XP’s boot.ini has /debugport=1 /baudrate=115200?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

And on the host, connected to the other end of that serial cable, you fire
up WinDbg, start a Kernel Debugging session, and then set the baud rate to
115200, and the comport to the port you plugged in the serial cable.

One point: No you may NOT use a USB to serial converter on the target. The
target requires a hardwired serial comport. You can use a USB to serial
converter on the host.

Gary G. Little

H (952) 223-1349

C (952) 454-4629

xxxxx@comcast.net

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Sarbojit Sarkar
Sent: Wednesday, August 11, 2010 3:34 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Not able to connect windbg on
win7-32bits(test-pc)->winxp-32bits(dev-pc).

forgot to demp bcdedit cmd and /dbgsettings output.

C:\Users\Administrator>bcdedit

Windows Boot Manager


identifier {bootmgr}

device partition=D:

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

resumeobject {5df2a356-9887-11df-aad3-85a2e8dd1651}

displayorder {ntldr}

{current}

toolsdisplayorder {memdiag}

timeout 30

Windows Legacy OS Loader


identifier {ntldr}

device partition=D:

path \ntldr

description Earlier Version of Windows

Windows Boot Loader


identifier {current}

device partition=C:

path \Windows\system32\winload.exe

description Windows 7

locale en-US

inherit {bootloadersettings}

recoverysequence {5df2a358-9887-11df-aad3-85a2e8dd1651}

recoveryenabled Yes

osdevice partition=C:

systemroot \Windows

resumeobject {5df2a356-9887-11df-aad3-85a2e8dd1651}

nx OptIn

usefirmwarepcisettings No

debug Yes

C:\Users\Administrator>bcdedit /dbgsettings

debugtype Serial

debugport 1

baudrate 115200

The operation completed successfully.

/sarbojit

On Wed, Aug 11, 2010 at 2:02 PM, Sarbojit Sarkar
wrote:

Sorry for late response.

Tim said,

>> according to your bcdedit output, you haven’t configured the
>>debug target to do debugging over a COM port.

Could you please let me where exactly you have found this? Because when I am
using /dbgsettings cmd it is showing,

debugtype Serial

debugport 1

baudrate 115200

Well my system is having win7-32bits & Winxp-32bits both OSes. I have
installed XP in c drive and Win7 in d drive but I have noticed that when I
boot the system in win7 it is showing current directory as C drive only and
when I boot in XP it is also showing current directory as c drive only.
Please let me know if this can be a issue.

When I boot the system in XP I am able to connect with same debug com port
cable so I am sure that cable is not a culprit here.

I am dumping the current settings here again. Please let me know if any
thing I am missing here.

On Tue, Jul 27, 2010 at 9:52 PM, M. M. O’Brien
wrote:

Indeed. Also, you might want to check /dbgsettings.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, July 27, 2010 12:16 PM
To: Kernel Debugging Interest List

Subject: Re: [windbg] Not able to connect windbg on
win7-32bits(test-pc)->winxp-32bits(dev-pc).

Sarbojit Sarkar wrote:
> Debugger is showing below message.
>
> Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c)
> Microsoft Corporation. All rights reserved.
>
> Opened \.\COM1 <file:>
> Waiting to reconnect…

OK, so windbg thinks you want to debug using COM1. That’s fine.
However, according to your bcdedit output, you haven’t configured the debug
target to do debugging over a COM port. Did you use bcdedit to set up a COM
port, and set up the baud rate?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


WINDBG 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


WINDBG 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

— WINDBG 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</file:>

Scott Noone wrote:

It all looks OK to me…

Any chance the COM port number changes on the Win7 install? It’s a fairly
ridiculous guess on my part, but this problem is odd enough that it’s worth
checking.

That should be irrelevant. The COM port numbers in the kernel debugger
sense are raw BIOS COM ports, not Windows COM ports. That is, when you
give a port number, you are really specifying a specific I/O port set
and IRQ number.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Also many serial ports allow via the BIOS to have non-standard COM#, port
address, and IRQ to be assigned. Don’t do it!!! Go with the standard
values.

“Tim Roberts” wrote in message news:xxxxx@windbg…
> Scott Noone wrote:
>> It all looks OK to me…
>>
>> Any chance the COM port number changes on the Win7 install? It’s a fairly
>> ridiculous guess on my part, but this problem is odd enough that it’s
>> worth
>> checking.
>
> That should be irrelevant. The COM port numbers in the kernel debugger
> sense are raw BIOS COM ports, not Windows COM ports. That is, when you
> give a port number, you are really specifying a specific I/O port set
> and IRQ number.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>

Well is there any possibility that some security check is restricting windbg
to connect target machine(win7)? Asking this because with same settings and
same hardware I can connect to target machine (winXP).

I have disabled all firewalls but still issue persists. So if you know can
think of some thing else please let me know.

On Thu, Aug 12, 2010 at 4:27 AM, David Craig wrote:

> Also many serial ports allow via the BIOS to have non-standard COM#, port
> address, and IRQ to be assigned. Don’t do it!!! Go with the standard
> values.
>
> “Tim Roberts” wrote in message news:xxxxx@windbg…
>
>> Scott Noone wrote:
>>
>>> It all looks OK to me…
>>>
>>> Any chance the COM port number changes on the Win7 install? It’s a fairly
>>> ridiculous guess on my part, but this problem is odd enough that it’s
>>> worth
>>> checking.
>>>
>>
>> That should be irrelevant. The COM port numbers in the kernel debugger
>> sense are raw BIOS COM ports, not Windows COM ports. That is, when you
>> give a port number, you are really specifying a specific I/O port set
>> and IRQ number.
>>
>> –
>> Tim Roberts, xxxxx@probo.com
>> Providenza & Boekelheide, Inc.
>>
>>
>>
> —
> WINDBG 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
>

Not if you’re talking about a direct KD connection.

If you’re talking about some remote debugging scenario, perhaps; I’m a
little lost at this point between this thread another one like it.

mm

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Sarbojit Sarkar
Sent: Thursday, August 12, 2010 2:37 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Not able to connect windbg on
win7-32bits(test-pc)->winxp-32bits(dev-pc).

Well is there any possibility that some security check is restricting windbg
to connect target machine(win7)? Asking this because with same settings and
same hardware I can connect to target machine (winXP).

I have disabled all firewalls but still issue persists. So if you know can
think of some thing else please let me know.

On Thu, Aug 12, 2010 at 4:27 AM, David Craig wrote:

Also many serial ports allow via the BIOS to have non-standard COM#, port
address, and IRQ to be assigned. Don’t do it!!! Go with the standard
values.

“Tim Roberts” wrote in message news:xxxxx@windbg…

Scott Noone wrote:

It all looks OK to me…

Any chance the COM port number changes on the Win7 install? It’s a fairly
ridiculous guess on my part, but this problem is odd enough that it’s worth
checking.

That should be irrelevant. The COM port numbers in the kernel debugger
sense are raw BIOS COM ports, not Windows COM ports. That is, when you
give a port number, you are really specifying a specific I/O port set
and IRQ number.



Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


WINDBG 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

— WINDBG 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