http://www.flexbeta.net/forums/lofiversion/index.php/t8373.html=====================
Modify your VISTA Boot Menu
=====================Do you also have several cryptical entries in your personal new VISTA bootloader?
Does it look like:
Legacy (pre-Longhorn) Microsoft Windows Operating System
Microsoft Windows
Microsoft Windows
Microsoft Windows
Microsoft Windows
....
Don't know which Windows is which entry?
Then you need this new guide with my experiences!
You will get a "new" boot menu! For example:
Legacy (pre-VISTA) XP, 2000, 2003, WIN98x
VISTA 5259 TAP
VISTA 5231 IDX
WINDOWS SERVER 2003======
Theory
======Till VISTA build 5231 we have had the new VISTA LOADER and for XP, 2000, 2003
and Win 98 the all known NTLDR called NT Loader or NT Bootloader and the mirror
of that is BOOT.INI...
With VISTA 5259 we have a new hierarchy:
First loader: VISTA loader called bootmgr, a "BOOTMANAGER"
Second Loader: NTLDR (XP,2003,98...)
VISTA looks in its "DATA STORE", were the new entries will be hold.
In the beta state of VISTA we have only two programs, which can help us:
MSCONFIG (which does not see the legacy OS)
BCDEDIT.EXE
==========
BCDEDIT.EXE
==========Please press START and RUN (have you activate "RUN"? >Go to ADMINISTRATOR, right-click Taskbar, Properties, Start Menu, Start Menu Customize, check Run command, OK) and type in:
command and press OK.
Yes, it looks like MS-DOS! It's name is Windows DOS...
Then you must type in:
bcedit and the nice program starts and shows for example this:
Microsoft® Windows DOS
©Copyright Microsoft Corp 1990-2001.
D:\USERS\ADMINI~1>bcdedit
Windows Boot Manager
--------------------
Identifier: {bootmgr}
Type: 10100002
Device: partition=C:
Description: Windows Boot Manager
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Default: {871d699a-68d1-11da-9f30-eb66f9279051}
Display order: {legacy}
{871d699a-68d1-11da-9f30-eb66f9279051}
{d3e15d7c-66fb-11da-83c4-f23116dca051}
{77e994d8-64b9-11da-afd6-cd1e42667751}
{748c9ce4-6497-11da-b587-ba41a6a3f856}
{6bde53aa-630a-11da-b591-bb4bd04c9f19}
{d9b222a6-5f5b-11da-8e9c-87c5457d571e}
{eafe9a2c-558c-11da-86bb-9237c2e1a919}
{3ffee100-4b31-11da-b300-e812ef50ad19}
{eda3906c-438e-11da-b934-f4ecbe0a3419}
{4f964faa-3d7a-11da-bb88-b7df6f4d4219}
Timeout: 3
Windows Legacy OS Loader
------------------------
Identifier: {legacy}
Type: 10300006
Device: partition=C:
Path: \ntldr
Description: Legacy (pre-Longhorn) Microsoft Windows Operating System
Windows Boot Loader
-------------------
Identifier: {871d699a-68d1-11da-9f30-eb66f9279051}
Type: 10200003
Device: partition=H:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {emssettings}
{dbgsettings}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Windows device: partition=H:
Windows root: \Windows
No Execute policy: OptIn
Windows Boot Loader
-------------------
Identifier: {d3e15d7c-66fb-11da-83c4-f23116dca051}
Type: 10200003
Device: partition=H:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {emssettings}
{dbgsettings}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Windows device: partition=H:
Windows root: \Windows
No Execute policy: OptIn
Windows Boot Loader
-------------------
Identifier: {77e994d8-64b9-11da-afd6-cd1e42667751}
Type: 10200003
Device: partition=H:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {emssettings}
{dbgsettings}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Windows device: partition=H:
Windows root: \Windows
No Execute policy: OptIn
Windows Boot Loader
-------------------
Identifier: {748c9ce4-6497-11da-b587-ba41a6a3f856}
Type: 10200003
Device: partition=D:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=D:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes
Windows Boot Loader
-------------------
Identifier: {6bde53aa-630a-11da-b591-bb4bd04c9f19}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes
Windows Boot Loader
-------------------
Identifier: {d9b222a6-5f5b-11da-8e9c-87c5457d571e}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes
Windows Boot Loader
-------------------
Identifier: {eafe9a2c-558c-11da-86bb-9237c2e1a919}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes
Windows Boot Loader
-------------------
Identifier: {3ffee100-4b31-11da-b300-e812ef50ad19}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes
Windows Boot Loader
-------------------
Identifier: {eda3906c-438e-11da-b934-f4ecbe0a3419}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes
Windows Boot Loader
-------------------
Identifier: {4f964faa-3d7a-11da-bb88-b7df6f4d4219}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes
D:\USERS\ADMINI~1>Sorry - a long one, but you will see, I have several entries of the same kind.
Partition H:\ three times and J:\ even more...
=========
Backup first!
=========First of all, we need a backup/copy of our boot entries!
Step 1: Change to ADMINISTRATOR
Step 2: Type in:
bcdedit -?This will show us the HELP MENU of bcdedit.exe:
H:\USERS\ADMINI~1>bcdedit -?
BCDEDIT - Boot Configuration Data Store Editor
The Bcdedit.exe command-line tool modifies the boot configuration data store.
The boot configuration data store contains boot configuration parameters and
controls how the operating system is booted. These parameters were previously
in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile
RAM entries (in Extensible Firmware Interface-based operating systems). You can
use Bcdedit.exe to add, delete, edit, and append entries in the boot
configuration data store.
For detailed command and option information, type bdedit.exe /? . For
example, type "bcdedit.exe /? /createstore" (without quotes).
For command and option information, please run "bcdedit /? " where
is one of the help topics listed below.
/bootdebug Enables or disables boot debugging for a boot application.
/bootems Enables or disables Emergency Management Services for a boot
application.
/bootsequence Sets the one-time boot sequence for the boot manager.
/copy Makes copies of entries in the store.
/create Creates new entries in the store.
/createstore Creates a new and empty boot configuration data store.
/dbgsettings Sets the global debugger parameters.
/debug Enables or disables kernel debugging for an operating system
entry.
/default Sets the default entry that the boot manager will use.
/delete Deletes entries from the store.
/deletevalue Deletes entry options from the store.
/displayorder Sets the order in which the boot manager displays the multiboot
menu.
/ems Enables or disables Emergency Management Services for an
operating system entry.
/emssettings Sets the global Emergency Management Services parameters.
/enum Lists entries in the store.
/export Exports then contents of the system store to a file. This file
can be used later to restore the state of the system store.
formats Displays the formats of the data required by the /set command.
id Displays the identifier parameter options that can be used
in several Bcdedit commands such as /create and /copy.
/import Restores the state of the system store using a backup file
created with the /export command.
/set Sets entry option values in the store.
/store Specifies the boot configuration data store to use.
/timeout Sets the boot manager time-out value.
/types Displays the data types required by the /set and /deletevalue
commands.
/v Displays all entry identifiers in full, rather than using
shorthand notation for the well-known identifiers.
H:\USERS\ADMINI~1>Step 3: Type in:
bcdedit -? exportYou will get:
H:\USERS\ADMINI~1>bcdedit -? export
bcdedit /export
This command exports the contents of the system store into a file. This file
can be used later to restore the state of the system store. This command is
only valid for the system store.
The filename to be used as the desination for the export.
If the filename contains spaces, it must be enclosed in
double quotes (").
Example:
The following example will export the system store to the specified file:
bcdedit /export "C:\Data\BCD Backup"
H:\USERS\ADMINI~1>Step 4: Please make a new folder: C:\DATA
Step 5: Type in:
bcdedit /export "C:\Data\BCD Backup"You have now a BACKUP of bootmgr entries! With "import" you are able to restore it!!
You can afterwards also safe your new entries, no problem like:
bcdedit /export "C:\Data\BCD My New Boot Entries"
==========================
DELETE DOUBLE ENTRIES IN bootmgr
==========================In the next step we will wipe out the double entries. (Always use your OWN identifiers!
My used one are only for explanation!!)
Step 6: Look at the double entries like: Device: partition=H:
Step 7: Type in:
bcdedit -? deleteYou will get:
H:\USERS\ADMINI~1>bcdedit -? delete
bcdedit -delete [-f]
This command will delete an entry from the boot configuration data store.
This specifies the identifier of the boot entry to be
deleted.
[-f] bcdedit will not delete any entries that have a well known
identifier. To force such a delete operation, specify this
flag.
Examples:
The following command will delete the specified OS entry from the store:
bcdedit -delete {cbd971bf-b7b8-4885-951a-fa03044f5d71}
The following command will delete the legacy OS loader entry from the store:
bcdedit -delete {legacy} -f
H:\USERS\ADMINI~1>bcdedit -delete {4f964faa-3d7a-11da-bb88-b7df6f4d4219}
The operation completed successfully.
H:\USERS\ADMINI~1>Let explain with the follow examples of my bootmgr entries:
Windows Boot Loader
-------------------
Identifier: {871d699a-68d1-11da-9f30-eb66f9279051}
Type: 10200003
Device: partition=H:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {emssettings}
{dbgsettings}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Windows device: partition=H:
Windows root: \Windows
No Execute policy: OptIn
Windows Boot Loader
-------------------
Identifier:
{d3e15d7c-66fb-11da-83c4-f23116dca051}Type: 10200003
Device: partition=H:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {emssettings}
{dbgsettings}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Windows device: partition=H:
Windows root: \Windows
No Execute policy: OptIn
I want to delete the second (blue) one:
Identifier: {d3e15d7c-66fb-11da-83c4-f23116dca051}
Step 8: Type in:
bcdedit -delete {d3e15d7c-66fb-11da-83c4-f23116dca051}It is away!
All of this commands needs only the correct Identifier to scratch!
Now we can delete all other double entries in the same way.
=====================
RENAME ENTRIES in boot menu
=====================The next step is to rename the entries.
The easiest one is the one you are in. If you have bootet VISTA 5259 TAP
you must type in:
Step 9: Type in: H:\USERS\ADMINI~1>
bcdedit -set DESCRIPTION "VISTA 5259 TAP"The operation completed successfully. Test it:
H:\USERS\ADMINI~1>
bcdeditThe desription of your booted VISTA has changed from only "Microsoft Windows" to
"VISTA 5259 TAP"!
You can now boot in a other VISTA build, maybe 5231 or another. In 5231 for example there is also a BCDEDIT.EXE and you must type in the same with an other description or you are in VISTA 5259 and
you want to change the description from your "other" VISTA.
Step 10: Type in: H:\USERS\ADMINI~1>
bcdedit -set {748c9ce4-6497-11da-b587-ba41a6a3f856} DESCRIPTION "VISTA 5231 IDX"You have easily changed the description of your second VISTA, if have use the correct IDENTIFIER!
From my 6 entries about WINDOWS SERVER 2003 I have deleted 5 and renamed the last:
H:\USERS\ADMINI~1>
bcdedit -set {6bde53aa-630a-11da-b591-bb4bd04c9f19} DESCRIPTION "WINDOWS SERVER 2003"=============================
START XP/2000/20003/98x automatically
=============================Now to the following problem:
You want to boot in your XP (2003, WIN98x) automatically?
MSCONFIG does not yet! Look in!
BCDEDIT does!
Step 11: Type in:
bcdedit ? defaultYou will get:
H:\USERS\ADMINI~1>bcdedit -? default
This command sets the default entry that the boot manager will use when the
time-out expires.
bcdedit /default
Specifies the identifier of the boot entry to be used as the
default when the time-out expires.
Examples:
The following command sets the specified entry as the default boot manager
entry:
bcdedit /default {cbd971bf-b7b8-4885-951a-fa03044f5d71}
The following command sets the legacy Windows loader (Ntldr) as the default
entry:
bcdedit /default {legacy}
H:\USERS\ADMINI~1>So a easy task, isn't it? You only must do Step12!
Step 12: Type in:
bcdedit /default {legacy}To look at the correct entry, look at "DEFAULT":
Microsoft® Windows DOS
©Copyright Microsoft Corp 1990-2001.
H:\USERS\ADMINI~1>bcdedit
Windows Boot Manager
--------------------
Identifier: {bootmgr}
Type: 10100002
Device: partition=C:
Description: Windows Boot Manager
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Default: {legacy}
Display order: {legacy}
{current}
{d3e15d7c-66fb-11da-83c4-f23116dca051}
{77e994d8-64b9-11da-afd6-cd1e42667751}
{748c9ce4-6497-11da-b587-ba41a6a3f856}
{6bde53aa-630a-11da-b591-bb4bd04c9f19}
{d9b222a6-5f5b-11da-8e9c-87c5457d571e}
{eafe9a2c-558c-11da-86bb-9237c2e1a919}
{3ffee100-4b31-11da-b300-e812ef50ad19}
{eda3906c-438e-11da-b934-f4ecbe0a3419}
{4f964faa-3d7a-11da-bb88-b7df6f4d4219}
Timeout: 3Yes, it worked!
========================
CHANGE {legacy} to a nicer one!
=======================In the next and last step we will learn to change the description entry of {legacy} from:
Legacy (pre-Longhorn) Microsoft Windows Operating System
to a neater one like:
Legacy (pre-VISTA) XP, 2000, 2003 , WIN98x
Step 13: Type in:
bcdedit -set {legacy} DESCRIPTION "Legacy (pre-VISTA) XP, 2000, 2003, WIN98x"Let's have a look, how it worked:
Windows Legacy OS Loader
------------------------
Identifier: {legacy}
Type: 10300006
Device: partition=C:
Path: \ntldr
Description: Legacy (pre-VISTA) XP, 2000, 2003, WIN98xPefect!
With that renamed entry you will go directly in your NTLDR loader and there is working the good old
well known BOOT.INI!
Nice program, the BCDEDIT.EXE, isn't it?
Like I have read anywhere in internet MS is planning to give us a GUI for that bootmgr editing!
I hope, we will get a fast, safe, and nice VISTA 2006!
Have fun with BCDEDITing and please, don't forget to make first my described BCD Backup before
you fiddle to much and nothing worked for you after reboot.
HELP: After everey step type in: bcdedit and you will see what have worked.
Look at the "Windows Device", "Description" and "Identifiers".
Have fun!
