[BCDEDIT! ARRRGH!]

Dont trust WINBETA to release ver 6000 because their bcdedit is from another build.... hmmm

Proof: I now have Vista Ultimate RTM now (ver 6) FROM MSDN's site... no kidding.

Interesting to me how lamers like winbeta can post stuff on the net calling it vista RTM ver 6.6000

but I think their guy is building ISOs out of anything he can find to make it look like vista RTM...

Must be something to do with "unlimited rearm" ....

either way the only working bcdedit that works with the WAIK's instructions is this copy of RTM i have direct from msdn.

So disregard the last 3 posts.....

[BCDEDIT! ARRRGH!]

Ok scratched that last idea quick... what I did instead is tried to use the RTM ver bcdedit like this:

For reference: My Vista is installed on V:\

and ive got a C:\ its my XP drive....

and ive got a network mapped drive Y:\ (which is really V:\TFTPRoot shared and loop mounted to Y:\ heh )

In the **** WAIK it keeps saying: "Bcdedit –store c:\BCD –create whatver {blah blah}"

I now interpret that as: "Bcdedit /create whatver {blah blah}"

I make sure the BCD I edit is the right one by comparing file sizes... so far I havent finished that...

The reasons are:

1) Its the next thing I need to do and ive been putting it off

2) I cant seem to specify the C:\BCD as in the WAIK's instructions... so since I am not allowed to specify the one I want to edit within the command then what the hell am I really editing?

Y:\>dir

Volume in drive Y is Vista

Volume Serial Number is 6E0E-4E5A

Directory of Y:\

12/10/2006 09:22 PM <DIR> .

12/10/2006 09:22 PM <DIR> ..

12/10/2006 09:22 PM 8,192 BCD

12/10/2006 09:17 PM <DIR> Boot

1 File(s) 8,192 bytes

3 Dir(s) 28,278,714,368 bytes free

Y:\>bcdedit

Windows Boot Manager

--------------------

identifier {bootmgr}

device partition=C:

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

displayorder {ntldr}

{current}

toolsdisplayorder {memdiag}

timeout 30

Windows Legacy OS Loader

------------------------

identifier {ntldr}

device partition=C:

path \ntldr

description Earlier Version of Windows

Windows Boot Loader

-------------------

identifier {current}

device partition=V:

path \Windows\system32\winload.exe

description Microsoft Windows Vista

locale en-US

inherit {bootloadersettings}

osdevice partition=V:

systemroot \Windows

resumeobject {7ff84399-88c8-11db-8f95-ade44ef0acc0}

nx OptIn

Y:\>Bcdedit /create {ramdiskoptions} /d "Ramdisk options"

A description for the new entry must be specified.

Run "bcdedit /?" for command line assistance.

What I did here was type my own quotation marks rather than use the copy and pasted ones from the WAIK (wack) guide... seems M$ has a couple of tricks up their sleeves to still p*** me off!)

So with good quotes:

Y:\>Bcdedit /create {ramdiskoptions} /d "Ramdisk options"

The entry {ramdiskoptions} was successfully created.

Y:\>bcdedit /set {ramdiskoptions} ramdisksdidevice boot

The operation completed successfully.

Y:\>bcdedit /create /d "WyWinPE Boot Image" /application osloader

The entry {d819fccc-88dc-11db-831a-0016ec20b410} was successfully created.

Y:\>bcdedit /create {bootmgr} /d "Windows VISTA BootManager"

An error occurred while attempting the specified create operation.

The specified entry already exists.

Y:\>Bcdedit -createstore c:\BCD

The specified command line is not valid.

Run "bcdedit /?" for command line assistance.

Y:\>Bcdedit /createstore y:\BCD

The store creation operation has failed.

Cannot create a file when that file already exists.

Y:\>Bcdedit /createstore y:\Boot\BCD

The store creation operation has failed.

Access is denied.

Y:\>Bcdedit

Windows Boot Manager

--------------------

identifier {bootmgr}

device partition=C:

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

displayorder {ntldr}

{current}

toolsdisplayorder {memdiag}

timeout 30

Windows Legacy OS Loader

------------------------

identifier {ntldr}

device partition=C:

path \ntldr

description Earlier Version of Windows

Windows Boot Loader

-------------------

identifier {current}

device partition=V:

path \Windows\system32\winload.exe

description Microsoft Windows Vista

locale en-US

inherit {bootloadersettings}

osdevice partition=V:

systemroot \Windows

resumeobject {7ff84399-88c8-11db-8f95-ade44ef0acc0}

nx OptIn

Y:\>bcdedit /set {d819fccc-88dc-11db-831a-0016ec20b410} systemroot \Windows

The operation completed successfully.

Y:\>bcdedit /set {d819fccc-88dc-11db-831a-0016ec20b410} detecthal Yes

The operation completed successfully.

Y:\>bcdedit /set {d819fccc-88dc-11db-831a-0016ec20b410} winpe Yes

The operation completed successfully.

Y:\>bcdedit /set {d819fccc-88dc-11db-831a-0016ec20b410} osdevice ramdisk=[boot]\

Boot\WinPE.wim,{ramdiskoptions}

The operation completed successfully.

Y:\>bcdedit /set {d819fccc-88dc-11db-831a-0016ec20b410} device ramdisk=[boot]\Bo

ot\WinPE.wim,{ramdiskoptions}

The operation completed successfully.

Y:\>bcdedit /create {bootmgr} /d "Windows VISTA BootManager"

An error occurred while attempting the specified create operation.

The specified entry already exists.

Y:\>Bcdedit /set {bootmgr} timeout 30

The operation completed successfully.

Y:\>Bcdedit /set displayorder {d819fccc-88dc-11db-831a-0016ec20b410}

The element data type specified is not recognized, or does not apply to the

specified entry.

Run "bcdedit /?" for command line assistance.

Y:\>bcdedit /? set

This command sets an entry option value in the boot configuration data store.

bcdedit [/store <filename>] /set [{<id>}] <datatype> <value>

<filename> Specifies the store to be used. If this option is not

specified, the system store is used. For more information,

run "bcdedit /? store".

<id> Specifies the identifier of the entry to be modified. If not

specified, {current} is used. For more information about

identifiers, run "bcdedit /? ID".

<datatype> Specifies the option data type that will be created or

modified. Run "bcdedit /? TYPES" for more information about

data types.

<value> Specifies the value that should be assigned to the option. The

format of <value> depends on the data type specified. Run

"bcdedit /? FORMATS" for more information about data formats.

Examples:

The following command sets the application device to the partition C: for the

specified operating system entry:

bcdedit /set {cbd971bf-b7b8-4885-951a-fa03044f5d71} device partition=C:

The following command sets the application path to

\windows\system32\winload.exe for the specified operating system entry:

bcdedit /set {cbd971bf-b7b8-4885-951a-fa03044f5d71} path

\windows\system32\winload.exe

The following command sets the NX policy to OptIn for the current operating

system boot entry.

bcdedit /set nx optin

Y:\>bcdedit /? displayorder

This command sets the display order to be used by the boot manager.

bcdedit /displayorder <id> [...] [ /addfirst | /addlast | /remove ]

<id> [...] Specifies a list of identifiers that make up the

display order. At least one identifier must be specified

and they must be separated by spaces. For more information

about identifiers, run "bcdedit /? ID".

/addfirst Adds the specified entry identifier to the top of

the display order. If this switch is specified, only a

single entry identifier may be specified. If the specified

identifier is already in the list, it will be moved to the

top of the list.

/addlast Adds the specified entry identifier to the end of

the display order. If this switch is specified, only a

single entry identifier may be specified. If the specified

identifier is already in the list, it is moved to the

end of the list.

/remove Removes the specified entry identifier from the

display order. If this switch is specified, only a single

entry identifier may be specified. If the identifier is

not in the list then the operation has no effect. If

the last entry is being removed, then the display order

value is deleted from the boot manager entry.

Examples:

The following command sets two OS entries and the NTLDR based OS loader in

the boot manager display order:

bcdedit /displayorder {802d5e32-0784-11da-bd33-000476eba25f}

{cbd971bf-b7b8-4885-951a-fa03044f5d71} {ntldr}

The following command adds the specified OS entry to the end of the boot

manager display order:

bcdedit /displayorder {802d5e32-0784-11da-bd33-000476eba25f} /addlast

Y:\>Bcdedit /displayorder {d819fccc-88dc-11db-831a-0016ec20b410}

The operation completed successfully.

Y:\>bcdedit

Windows Boot Manager

--------------------

identifier {bootmgr}

device partition=C:

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

displayorder {d819fccc-88dc-11db-831a-0016ec20b410}

toolsdisplayorder {memdiag}

timeout 30

Windows Boot Loader

-------------------

identifier {d819fccc-88dc-11db-831a-0016ec20b410}

device ramdisk=[boot]\Boot\WinPE.wim,{ramdiskoptions}

description WyWinPE Boot Image

osdevice ramdisk=[boot]\Boot\WinPE.wim,{ramdiskoptions}

systemroot \Windows

detecthal Yes

winpe Yes

Y:\>

Ill now Install VirtualPC 2007 beta and see if I can boot using any BCDs ive just created... (yep got a few to test cuz i have no idea which one was just written! time to check timestamps/sizes I guess

sheesh

[BCDEDIT! ARRRGH!]

The first email you sent me was flagged as spam because of your nonsensical subject line.

I really would have preferred you including a link to my post, rather than copying and pasting the entire thing into this forum. Its much easier to keep all of the information in one place, in case updates are made.

As for your specific issue, it is possibly because of the typo in my post (I copied the typo in the documentation and forgot to correct it). Check the updated notes on Step 2-5 on my article now. (And please don't copy the entire updated post here).

The latest edition of the article can always be found here:

http://flimflan.com/blog/InstallingVistaOn...oshibaM200.aspx

Yo dude, fixed the post! ;-)

Point taken... just trying to keep all the relevant research here and got a lil carried away! lol

Anyways, bad news guys.

I installed Vista RTM (ver 6000 x86) today and this is what I'm getting... looks like the WAIK PXE boot guide is f***ED for RTM bcdedit..

What makes matters worse... I got the BDD 2007 RC1 today (it finally works snap-in wise)

and it is pretty nice... I downloaded WAIK from within the BDD interface thinking that it would have UPDATED instructions pertinent to the current RTM bcdedit.exe

Hell no!

Proof:

V:\Windows\System32>Bcdedit -createstore c:\BCD

The specified command line is not valid.

Run "bcdedit /?" for command line assistance.

V:\Windows\System32>Bcdedit /createstore c:\BCD

The operation completed successfully.

As you can see the proof is in the -createstore that is now /createstore

f***ing lame.

As a solution I am going to try and boot into WINPE2 cd (thanks josh)

and copy c:\windows\system32\bcdedit.exe to bcdedit.bak

and

copy x:\windows\system32\bcdedit.exe c:\windows\system32\bcdedit.exe

and see if I can use the proper bcdedit with josh's updated commands.

cheers?

[BCDEDIT! ARRRGH!]

Pixieboots - I've just wasted most of my morning screwing around with bcdedit, and it turned out that like you I was using the version on Vista RC2. Very frustrating. Even worse, I didn't check this forum!

One problem - presumably this means you can actually only have a single PE 2.0 image if you do it this way, because it will always try to load the bootfiles from tftproot/boot. I'm using 2003 RIS to serve the image.

I can only seem to find the BDD 2007 beta, even though I'm a volume licence customer. I rang MS today and they had no idea where I could get it. The beta version seems to be missing WDS and it doesn't have that documentation about booting via a PXE server. Where did you get yours?

BTW buddy, I'm glad my post here saved ya some time... after you get your WAIK downloaded let me know if you could manage to do this:

Follow this guys steps ->>> flimflan.com/blog thanks josh!

Then if you can get PXE booted winpe2.0 then post the BCD file!!!! (its NOT illegal to post)

Thanks!

-pixieboots

[BCDEDIT! ARRRGH!]

Pixieboots - I've just wasted most of my morning screwing around with bcdedit, and it turned out that like you I was using the version on Vista RC2. Very frustrating. Even worse, I didn't check this forum!

One problem - presumably this means you can actually only have a single PE 2.0 image if you do it this way, because it will always try to load the bootfiles from tftproot/boot. I'm using 2003 RIS to serve the image.

I can only seem to find the BDD 2007 beta, even though I'm a volume licence customer. I rang MS today and they had no idea where I could get it. The beta version seems to be missing WDS and it doesn't have that documentation about booting via a PXE server. Where did you get yours?

I got mine from the same place as the fellow who responded below you....

BTW guys I tried VistaBootPro... and I see nowhere on it where you can configure it to boot the wim......

Mainly because you can choose "Add new operating system entry" but then you are forced to choose to load it from a drive letter... a grave mistake if your trying to load from /Boot nuff said.

am I missing something?

[BCDEDIT! ARRRGH!]

hint: "bcdedit /? /addfirst"

took me a lot of time til I had figured out that the last command line in the docs is wrong. At least for me that worked out too a BCD that allows to PXE boot WinPE 2.0.

I really dont see what your saying man... "use the man page" isnt really very helpful for everyone.

Bcdedit –store c:\BCD –create {bootmgr} /d “Windows VISTA BootManager” /inherit {dbgsettings}

Bcdedit –store c:\BCD –set {bootmgr} timeout 30

Bcdedit –store c:\BCD –set displayorder {guid1} {guid2} ... ;

Similar to this format above..

Please help.

[BCDEDIT! ARRRGH!]

perhaps if you broke it up a little

bcdedit /timeout 3

bcdedit /default {ntldr} <<XP

works

Works for building a BCD file to PXE boot winpe??? cuz it looks to me like your making up a XP/NTLDR combo and that is NOT what im talking about/needing....

[BCDEDIT! ARRRGH!]

Well, I should not celebrate.. the last 3 commands didnt work.

Bcdedit –store c:\BCD –create {bootmgr} /d “Windows VISTA BootManager” /inherit {dbgsettings}

Bcdedit –store c:\BCD –set {bootmgr} timeout 30

Bcdedit –store c:\BCD –set displayorder {guid1} {guid2} ... ;

Freakin yippee... back to the &%^%#& drawing board.

why do you even have to edit the BCD?

"I have to create a BCD file for my PXE boot server"

[BCDEDIT! ARRRGH!]

I finally fingered it out.

I was using vista build 5744's bcdedit

In the WAIK guide everything turned out to be correct EXCEPT for a silly command

cd \temp\Windows\Boot\PXE

I dont know why that there....

once I created my own winpe2.0 BOOTABLE cd FROM the WAIK image wim everything worked.... it had a different Bcdedit.exe

And that bcdedit used a completely different set of commands.... thanks alot microsoft for telling me i could use my Vista OR winPE2.0.... that was simply NOT the case here.

I still havent tried to PXEboot the new BCD yet, so if I run into any more issues I'll just keep posting in this thread.

[BCDEDIT! ARRRGH!]

Hello friends,

I have to create a BCD file for my PXE boot server... but it isnt working.

This is a short part of info from the WAIK:

Bcdedit –createstore c:\BCD

This command doesnt work. I instead had to use

Bcdedit /createstore c:\BCD

C:\Windows\System32>Bcdedit /createstore c:\BCD

The operation completed successfully. neato.

Why did M$ put a -createstore when it should have been a /createstore ????

Now it gets worse:

Bcdedit –store C:\BCD –create {ramdiskoptions} /d “Ramdisk options”

I copy and paste that command into my console and this is the result:

C:\Windows\System32>Bcdedit -store C:\BCD -create {ramdiskoptions} /d "Ramdisk o

ptions"

The specified command line is not valid.

Run "bcdedit /?" for command line assistance.

C:\Windows\System32>Bcdedit -store C:\BCD -create {ramdiskoptions} /d "Ramdisk o

ptions"

The specified command line is not valid.

Run "bcdedit /?" for command line assistance.

OK wtf.

So I tried variations of this:

Bcdedit /create {ramdiskoptions} /d "Ramdisk options"

(the reason is because - seems to be / and the "Bcdedit -store C:\BCD" at the beginning seems to be more misguided junk

and I get:

C:\Windows\System32>Bcdedit /create {ramdiskoptions} /d "Ramdisk options"

An error occurred while attempting the specified create operation.

The specified entry already exists.

HOW does it already exist!!?? I didnt put that there!?? hahahah (I am going crazy!)

I didnt even get this far:

Bcdedit –store C:\BCD –set {ramdiskoptions} ramdisksdidevice boot

Bcdedit –store C:\BCD –set {ramdiskoptions} ramdisksdipath \boot\boot.sdi

Create the RAMDISK settings. For example,

Bcdedit –store C:\BCD –create {ramdiskoptions} /d “Ramdisk options”

Bcdedit –store C:\BCD –set {ramdiskoptions} ramdisksdidevice boot

Bcdedit –store C:\BCD –set {ramdiskoptions} ramdisksdipath \boot\boot.sdi

I have been at this for 5 days now, reading the WAIK, trying variations, pxebooting bunk BCD files that cant find "boot.ini"

I PMed kennedto because he got it to work... he said he made scripts and he will post them, but I cannot wait to get this working and ive been frustrating myself because I'm stubborn like that.

All I really want for Christmas is real instructions (yes with the REAL commands IN ORDER) on how to buid a BCD store for PXE booting winpe2.0. That is ALL I want for christmas... I know ive gone nuts.