At XP, can use Windebug + VirtualPC/Vmware to debug boot.
It seems Vista can’t support this method. How can I debug the boot process
at Vista?
Use bcdedit:
bcdedit /set {bootmgr} bootdebug on
bcdedit /set {bootmgr} debugtype 1394
bcdedit /set {bootmgr} channel 1
bcdedit /set {current} bootdebug on
bcdedit /set {current} debugtype 1394
bcdedit /set {current} channel 1
bcdedit /set {current} halbreakpoint on
bcedit /set {current} debug on
Instead of using current, you probably want to create a new
configuration:
bcdedit /copy {current} /D “YOUR NAME HERE”
This will create a new configuration based on {current} with some
unreasonable GUID for a name. You then perform the second set of steps
above, replacing {current} with the GUID.
The last thing you might wish to do is cause the new configuration to
be the default:
bcdedit /default {GUID}
>> xxxxx@hotmail.com 2007-02-26 21:02 >>>
At XP, can use Windebug + VirtualPC/Vmware to debug boot.
It seems Vista can’t support this method. How can I debug the boot
process
at Vista?
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Speaking of which, the bcd user interface is the only thing new with the
Vista release that is actually worse than DTM. Gosh, I never thought I
would look back fondly on both boot.ini and WHQL.
Oops what was that guid again?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Tuesday, February 27, 2007 10:52 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] How to debug boot at Vista?
Use bcdedit:
bcdedit /set {bootmgr} bootdebug on
bcdedit /set {bootmgr} debugtype 1394
bcdedit /set {bootmgr} channel 1
bcdedit /set {current} bootdebug on
bcdedit /set {current} debugtype 1394
bcdedit /set {current} channel 1
bcdedit /set {current} halbreakpoint on
bcedit /set {current} debug on
Instead of using current, you probably want to create a new
configuration:
bcdedit /copy {current} /D “YOUR NAME HERE”
This will create a new configuration based on {current} with some
unreasonable GUID for a name. You then perform the second set of steps
above, replacing {current} with the GUID.
The last thing you might wish to do is cause the new configuration to
be the default:
bcdedit /default {GUID}
>> xxxxx@hotmail.com 2007-02-26 21:02 >>>
At XP, can use Windebug + VirtualPC/Vmware to debug boot.
It seems Vista can’t support this method. How can I debug the boot
process
at Vista?
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Mark, I’m confused? Are you saying that you don’t find typing a GUID
convenient and not at all error prone? If so, I think you would be wise
to consider the large number of machines out there with 2^128 (or
whatever of GUID is) boot configurations.
mm
>> xxxxx@stratus.com 2007-02-27 11:02 >>>
Speaking of which, the bcd user interface is the only thing new with
the
Vista release that is actually worse than DTM. Gosh, I never thought I
would look back fondly on both boot.ini and WHQL.
Oops what was that guid again?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Tuesday, February 27, 2007 10:52 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] How to debug boot at Vista?
Use bcdedit:
bcdedit /set {bootmgr} bootdebug on
bcdedit /set {bootmgr} debugtype 1394
bcdedit /set {bootmgr} channel 1
bcdedit /set {current} bootdebug on
bcdedit /set {current} debugtype 1394
bcdedit /set {current} channel 1
bcdedit /set {current} halbreakpoint on
bcedit /set {current} debug on
Instead of using current, you probably want to create a new
configuration:
bcdedit /copy {current} /D “YOUR NAME HERE”
This will create a new configuration based on {current} with some
unreasonable GUID for a name. You then perform the second set of
steps
above, replacing {current} with the GUID.
The last thing you might wish to do is cause the new configuration to
be the default:
bcdedit /default {GUID}
>> xxxxx@hotmail.com 2007-02-26 21:02 >>>
At XP, can use Windebug + VirtualPC/Vmware to debug boot.
It seems Vista can’t support this method. How can I debug the boot
process
at Vista?
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Mark missed the wonderful conversation on this during beta, I for one was
complaining about BCDedit and was told that “most people will not use
BCDedit, since the average user will use the interfaces GUI interfaces that
allow limited support, and the large installations will use network
management tools to modify things”. I pointed out that neither case did
changes very often, but that developers need to change the settings all the
time, so what should they do, “the response was put up with BCDedit, or
hope for third party tools”. Gee the only people likely to use this tool
will hate it, but we don’t care!
Not only does the tool suck, but at the end they messed up debugger
handling, since I always have an entry for serial debugging, just in case
1394 goes flaky which it seems to do every few weeks, and always when I am
on deadline.
BCDedit is just one of the many reasons, I charge extra when my customers
want me to support Vista. I tell them the extra cost is for VAT (“Vista
Agravation and Trivails” ).
–
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
“Martin O’Brien” wrote in message
news:xxxxx@ntdev…
> Mark, I’m confused? Are you saying that you don’t find typing a GUID
> convenient and not at all error prone? If so, I think you would be wise
> to consider the large number of machines out there with 2^128 (or
> whatever of GUID is) boot configurations.
>
> mm
>
>>>> xxxxx@stratus.com 2007-02-27 11:02 >>>
> Speaking of which, the bcd user interface is the only thing new with
> the
> Vista release that is actually worse than DTM. Gosh, I never thought I
> would look back fondly on both boot.ini and WHQL.
>
> Oops what was that guid again?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
> Sent: Tuesday, February 27, 2007 10:52 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] How to debug boot at Vista?
>
> Use bcdedit:
>
> 1.
>
> bcdedit /set {bootmgr} bootdebug on
> bcdedit /set {bootmgr} debugtype 1394
> bcdedit /set {bootmgr} channel 1
>
> 2.
>
> bcdedit /set {current} bootdebug on
> bcdedit /set {current} debugtype 1394
> bcdedit /set {current} channel 1
> bcdedit /set {current} halbreakpoint on
>
> 3.
>
> bcedit /set {current} debug on
>
> Instead of using current, you probably want to create a new
> configuration:
>
> bcdedit /copy {current} /D “YOUR NAME HERE”
>
> This will create a new configuration based on {current} with some
> unreasonable GUID for a name. You then perform the second set of
> steps
> above, replacing {current} with the GUID.
>
> The last thing you might wish to do is cause the new configuration to
> be the default:
>
> bcdedit /default {GUID}
>
>
>>>> xxxxx@hotmail.com 2007-02-26 21:02 >>>
> At XP, can use Windebug + VirtualPC/Vmware to debug boot.
> It seems Vista can’t support this method. How can I debug the boot
> process
> at Vista?
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
You forgot the best part: Only in the world of BCDEdit is “deletevalue” the
opposite of “set”.
If you only want to enable debugging Just Say No to BCDEdit and use MsConfig
instead.
-scott
–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Martin O’Brien” wrote in message
news:xxxxx@ntdev…
> Mark, I’m confused? Are you saying that you don’t find typing a GUID
> convenient and not at all error prone? If so, I think you would be wise
> to consider the large number of machines out there with 2^128 (or
> whatever of GUID is) boot configurations.
>
> mm
>
>>>> xxxxx@stratus.com 2007-02-27 11:02 >>>
> Speaking of which, the bcd user interface is the only thing new with
> the
> Vista release that is actually worse than DTM. Gosh, I never thought I
> would look back fondly on both boot.ini and WHQL.
>
> Oops what was that guid again?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
> Sent: Tuesday, February 27, 2007 10:52 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] How to debug boot at Vista?
>
> Use bcdedit:
>
> 1.
>
> bcdedit /set {bootmgr} bootdebug on
> bcdedit /set {bootmgr} debugtype 1394
> bcdedit /set {bootmgr} channel 1
>
> 2.
>
> bcdedit /set {current} bootdebug on
> bcdedit /set {current} debugtype 1394
> bcdedit /set {current} channel 1
> bcdedit /set {current} halbreakpoint on
>
> 3.
>
> bcedit /set {current} debug on
>
> Instead of using current, you probably want to create a new
> configuration:
>
> bcdedit /copy {current} /D “YOUR NAME HERE”
>
> This will create a new configuration based on {current} with some
> unreasonable GUID for a name. You then perform the second set of
> steps
> above, replacing {current} with the GUID.
>
> The last thing you might wish to do is cause the new configuration to
> be the default:
>
> bcdedit /default {GUID}
>
>
>>>> xxxxx@hotmail.com 2007-02-26 21:02 >>>
> At XP, can use Windebug + VirtualPC/Vmware to debug boot.
> It seems Vista can’t support this method. How can I debug the boot
> process
> at Vista?
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
Roddy, Mark wrote:
Speaking of which, the bcd user interface is the only thing new with the
Vista release that is actually worse than DTM. Gosh, I never thought I
would look back fondly on both boot.ini and WHQL.Oops what was that guid again?
Absolutely correct. Programmers without enough to do changing something
that did not need to be changed.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Tim,
While I hate BCDedit, much of what was done with Vista for the boot
was highly needed. The problems with deploying Windows prior to Vista was
a nightmare, and many of the 3rd party deployment tools took hacks the we
condem all the time on forums like this. So, I am not against what the did
in principal, but:
- BCDedit is a total piece of garbage
- The stuff for accessing WIM should have been shipped with the OS
- The limitations they put on entries (things like only one way to
debug) are completely wrong.
–
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
“Tim Roberts” wrote in message news:xxxxx@ntdev…
> Roddy, Mark wrote:
>> Speaking of which, the bcd user interface is the only thing new with the
>> Vista release that is actually worse than DTM. Gosh, I never thought I
>> would look back fondly on both boot.ini and WHQL.
>>
>> Oops what was that guid again?
>>
>
> Absolutely correct. Programmers without enough to do changing something
> that did not need to be changed.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
Checkout http://www.vistabootpro.org
Cheers
Check Abdoul
“George” wrote in message news:xxxxx@ntdev…
> At XP, can use Windebug + VirtualPC/Vmware to debug boot.
> It seems Vista can’t support this method. How can I debug the boot process
> at Vista?
>
>
Tried Vista Boot Pro some time ago. But it did not set the debugging environment correctly. It seemed that all debugging options in its GUI did not work at all.
“Don Burn” wrote:
- The limitations they put on entries (things like only one way to
debug) are completely wrong.
I think you can specify different debug settings for each boot entry,
similar to the way boot.ini worked. For example, this should
override the default debug type specified with bcdedit /dbgsettings:
bcdedit /set {id} debugtype serial
To see supported debug options and their values, type
bcdedit /? types bootapp
–
This posting is provided “AS IS” with no warranties, and confers no
rights.