Debug entry not working with dual boot

NTDEV
1

Debug entry not working with dual boot

I have multiple copies of Vista installed on the same machine - V1 and V2 but on separate disks- D1 and D2. I had debug entry for V1 - V1_DebugEntry working properly. Then I created debug entry for V2 - V2_DebugEntry. But by mistake I forgot to put the V1 and V1_DebugEntry in the displayorder and I was left with just V2 and V1_DebugEntry. I used the vista installation dvd to recover. After that V2_DebugEntry connects to winDbg on my host machine properly and I can debug but I lost V1_DebugEntry. So I re-created V1_DebugEntry but now with this new V1_DebugEntry I’m not able to connect to the winDbg. Is there any limitation on how many Debug entries we can have on a single machine?

For me V1_DebugEntry is more important, so I tried the following independent options but non of them worked:

  1. deleted V2_DebugEntry
  2. disconnected D2 from the system (system partition is on D1).
  3. deleted both V1_DebugEntry and V2_DebugEntry and then re-created V1_DebugEntry.

Any idea why this happening and how can I fix this?

Here is the output of bcdedit /enum all.

Windows Boot Manager

identifier {bootmgr}
device partition=D:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
displayorder {33a3da89-b150-11dd-bff0-00e081b08d62}
{default}
{current}
toolsdisplayorder {memdiag}
timeout 5

Windows Boot Loader

identifier {33a3da89-b150-11dd-bff0-00e081b08d62}
device partition=D:
path \Windows\system32\winload.exe
description Microsoft Vista Business
osdevice partition=D:
systemroot \Windows
resumeobject {7015c551-e37d-11dd-99b2-806e6f6e6963}

Windows Boot Loader

identifier {default}
device partition=D:
path \Windows\system32\winload.exe
description Microsoft Vista Business (DebugEntry)
osdevice partition=D:
systemroot \Windows
resumeobject {7015c551-e37d-11dd-99b2-806e6f6e6963}
debug Yes

Windows Boot Loader

identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Vista for Recovery
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {7f4448f5-b344-11dd-9b96-8ce1b591271e}
nx OptIn

Resume from Hibernate

identifier {7015c551-e37d-11dd-99b2-806e6f6e6963}
device partition=D:
path \Windows\system32\winresume.exe
description Windows Vista ™ Business (recovered)
inherit {resumeloadersettings}
filedevice partition=D:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Resume from Hibernate

identifier {7f4448f5-b344-11dd-9b96-8ce1b591271e}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Windows Memory Tester

identifier {memdiag}
device partition=D:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader

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

EMS Settings

identifier {emssettings}
bootems Yes

Debugger Settings

identifier {dbgsettings}
debugtype Serial
debugport 1

RAM Defects

identifier {badmemory}

Global Settings

identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings

identifier {bootloadersettings}
inherit {globalsettings}

Resume Loader Settings

identifier {resumeloadersettings}
inherit {globalsettings}

Thanks.

2

You have to set the debug options per configuration entry. It doesn’t
appear that you have them in this fashion below. For example, if you
look at {default}, you wont’ find any debug options. I never use the
global ones, as the really aren’t something that I want to apply to
everything.

In any case, using your global settings (and adding a baud rate, which
you should do), and what I think are your two installations (not sure
really):

bcdedit /set {default} debugtype serial
bcdedit /set {default} debugport 1
bcdedit /set {default} baudrate 1
bcdedit /set {default} debug on

bcdedit /set {current} debugtype serial
bcdedit /set {current} debugport 1
bcdedit /set {current} baudrate 1
bcdedit /set {current} debug on

Good luck,

mm

xxxxx@yahoo.com wrote:

Debug entry not working with dual boot

I have multiple copies of Vista installed on the same machine - V1 and V2 but on separate disks- D1 and D2. I had debug entry for V1 - V1_DebugEntry working properly. Then I created debug entry for V2 - V2_DebugEntry. But by mistake I forgot to put the V1 and V1_DebugEntry in the displayorder and I was left with just V2 and V1_DebugEntry. I used the vista installation dvd to recover. After that V2_DebugEntry connects to winDbg on my host machine properly and I can debug but I lost V1_DebugEntry. So I re-created V1_DebugEntry but now with this new V1_DebugEntry I’m not able to connect to the winDbg. Is there any limitation on how many Debug entries we can have on a single machine?

For me V1_DebugEntry is more important, so I tried the following independent options but non of them worked:

  1. deleted V2_DebugEntry
  2. disconnected D2 from the system (system partition is on D1).
  3. deleted both V1_DebugEntry and V2_DebugEntry and then re-created V1_DebugEntry.

Any idea why this happening and how can I fix this?

Here is the output of bcdedit /enum all.

Windows Boot Manager

identifier {bootmgr}
device partition=D:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
displayorder {33a3da89-b150-11dd-bff0-00e081b08d62}
{default}
{current}
toolsdisplayorder {memdiag}
timeout 5

Windows Boot Loader

identifier {33a3da89-b150-11dd-bff0-00e081b08d62}
device partition=D:
path \Windows\system32\winload.exe
description Microsoft Vista Business
osdevice partition=D:
systemroot \Windows
resumeobject {7015c551-e37d-11dd-99b2-806e6f6e6963}

Windows Boot Loader

identifier {default}
device partition=D:
path \Windows\system32\winload.exe
description Microsoft Vista Business (DebugEntry)
osdevice partition=D:
systemroot \Windows
resumeobject {7015c551-e37d-11dd-99b2-806e6f6e6963}
debug Yes

Windows Boot Loader

identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Vista for Recovery
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {7f4448f5-b344-11dd-9b96-8ce1b591271e}
nx OptIn

Resume from Hibernate

identifier {7015c551-e37d-11dd-99b2-806e6f6e6963}
device partition=D:
path \Windows\system32\winresume.exe
description Windows Vista ™ Business (recovered)
inherit {resumeloadersettings}
filedevice partition=D:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Resume from Hibernate

identifier {7f4448f5-b344-11dd-9b96-8ce1b591271e}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Windows Memory Tester

identifier {memdiag}
device partition=D:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader

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

EMS Settings

identifier {emssettings}
bootems Yes

Debugger Settings

identifier {dbgsettings}
debugtype Serial
debugport 1

RAM Defects

identifier {badmemory}

Global Settings

identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings

identifier {bootloadersettings}
inherit {globalsettings}

Resume Loader Settings

identifier {resumeloadersettings}
inherit {globalsettings}

Thanks.

3

>V1_DebugEntry. So I re-created V1_DebugEntry but now with this new V1_DebugEntry I’m not able to

connect to the winDbg. Is there any limitation on how many Debug entries we can have on a single
machine?

All of this was working for me for around a year with Vista and Server 2008. Now it works for me with also Win7 client and 2008 R2 in the boot menu - 3 OSes debug/release, and also the “previous version” item which can load another 5 OSes also debug/release.

You did something incorrectly. For instance, there is no need to add anything to display order - just use "bcdedit /copy {current} /d “Microsoft Windows Vista”, save the GUID and then “bcdedit /debug {guid} on”.

No need in recovery CD if you can boot another Vista and re-create the missing entry using “bcdedit”, just update the partition drive letters there.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

4

> bcdedit /set {default} debugtype serial

bcdedit /set {default} debugport 1
bcdedit /set {default} baudrate 1
bcdedit /set {default} debug on

Everything except “debug on” belong to the global BCD store as “dbgsettings”, I never tried to set these per-entry.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

5

You definitely can include all of these as osloader settings (as
‘bcdedit /? TYPES OSLOADER’ will show). I am not saying it’s better or
worth (though this way makes more sense to me), but it does work, and in
the case of something like a kd connection and a hypervisor connection,
I don’t see how else you could do it (I use that daily).

mm

Maxim S. Shatskih wrote:

> bcdedit /set {default} debugtype serial
> bcdedit /set {default} debugport 1
> bcdedit /set {default} baudrate 1
> bcdedit /set {default} debug on

Everything except “debug on” belong to the global BCD store as “dbgsettings”, I never tried to set these per-entry.

6

> the case of something like a kd connection and a hypervisor connection,

/dbgsettings default to COM1-115200 and are already in the osloader section, so, “/debug {guid} on” is enough.

As about Hyper-V - for the debugger, it is still the COM port.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

7

I am not familiar with ‘/dbgsettings,’ but I don’t believe that your
statement about Hyper-V is not correct. I use 1394 daily for this
purpose, and it’s in the windbg documentation.

http://msdn.microsoft.com/en-us/library/cc901392.aspx

mm

Maxim S. Shatskih wrote:

> the case of something like a kd connection and a hypervisor connection,

/dbgsettings default to COM1-115200 and are already in the osloader section, so, “/debug {guid} on” is enough.

As about Hyper-V - for the debugger, it is still the COM port.

8

Yes, I was about debugging Hyper-V guests, not Hyper-V itself or the root partition.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

“Martin O’Brien” wrote in message news:xxxxx@ntdev…
>I am not familiar with ‘/dbgsettings,’ but I don’t believe that your
> statement about Hyper-V is not correct. I use 1394 daily for this
> purpose, and it’s in the windbg documentation.
>
>
> http://msdn.microsoft.com/en-us/library/cc901392.aspx
>
> mm
>
>
>
>
>
> Maxim S. Shatskih wrote:
>>> the case of something like a kd connection and a hypervisor connection,
>>
>> /dbgsettings default to COM1-115200 and are already in the osloader section, so, “/debug {guid} on” is enough.
>>
>> As about Hyper-V - for the debugger, it is still the COM port.
>>
>

9

I had a similiar experience trying to get debug options working again after using VISTA recovery CD.

I tried using “dbgsettings” along with “debug on” and although no error was reported, I could never get it to work. “Debug on” seemed to take but none of the “dbgsettings” were ever reflected in any of the configuration entries and I could never connect.

What finally worked was setting the debugtype, debugport, and baudrate debug options discreetly just as MM described:

bcdedit /set {default} debugtype serial
bcdedit /set {default} debugport 1
bcdedit /set {default} baudrate 1

bcdedit /set {current} debugtype serial
bcdedit /set {current} debugport 1
bcdedit /set {current} baudrate 1

Judy