Help - Search - Members - Calendar
Full Version: Read BCD options from within WinPE
The CD Forum > The CD Forum > Windows PE
gnulnulf
Is it possible to see bcd options within WinPE. I use the WinPE3 from the windows7 WAIK.
I can't find them in the registry or through wmic.

My example bcd is:
CODE
Windows Boot Loader
-------------------
identifier {a6d78231-90cc-11db-97db-001641238d0d}
device ramdisk=[boot]\winpe\x86_test\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path \windows\system32\boot\winload.exe
description WinPE x86 (TEST)
locale en-US
custom:12345678 bidie
inherit {bootloadersettings}
osdevice ramdisk=[boot]\winpe\x86_test\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot \windows
detecthal Yes
winpe Yes
ems Yes


I want to use one PE image and choose its behaviour during bcd boot menu.
jaclaz
QUOTE (gnulnulf @ Oct 14 2009, 02:31 PM) *
Is it possible to see bcd options within WinPE. I use the WinPE3 from the windows7 WAIK.
I can't find them in the registry or through wmic.


I am not sure what you are asking.

The BCD is a "Registry" type of file, but it is NOT part of the Registry.

Have you tried opening the BCD with rawreg:
http://www.boot-land.net/forums/?showtopic=4684

Or are you asking something else? unsure.gif

jaclaz
gnulnulf
QUOTE (jaclaz @ Oct 14 2009, 12:52 PM) *
I am not sure what you are asking.


I'll try to explain it by the procedure:
1. pxeboot
2. in the bcdboot menu choose one of the following options
- unattended firmware update
- start winpe
- autostart recovery application
3. start always the same boot.wim
4. after starting PE discover what menu option was used to start the image.
5. do as requested....

Do you understand my "wish" now?
jaclaz
So if I get it right, you are already past 1., 2. and 3.

And you presume that the chosen option in BCD is somehow "sticky" and detectable after PE has booted?

I don't think that it is "sticky". hmm.gif

There may be a workaround using different BOOTMGR's/BCD's and make the choice via grub4dos, with menu.lst entries that also log to a file (outside the .WIM). unsure.gif

jaclaz


gnulnulf
One workaround I could think of:

copy \windows\system32\boot\winload.exe to \windows\system32\boot\winload_auto.exe inside the wim.
and change a bcd path to "path \windows\system32\boot\winload_auto.exe"

Not so nice but it could work. Probably need to copy the winload.mui as well then.
jaclaz
QUOTE (gnulnulf @ Oct 14 2009, 04:38 PM) *
One workaround I could think of:

copy \windows\system32\boot\winload.exe to \windows\system32\boot\winload_auto.exe inside the wim.
and change a bcd path to "path \windows\system32\boot\winload_auto.exe"

Not so nice but it could work. Probably need to copy the winload.mui as well then.


But I don't see how that (the chosen option) would be "visible" once booted. unsure.gif

With grub4dos you could use several Vista boot floppy images:
http://www.multibooters.co.uk/floppy.html
one for each "choice", then either parse the grub4dos "default" file or use either grub4dos "dd" or "write" to change/write something to any file.

jaclaz
gnulnulf
QUOTE (jaclaz @ Oct 14 2009, 05:23 PM) *
With grub4dos you could use several Vista boot floppy images:

the chain would be: PXE -> memdisk -> grub4dos -> boot.wim

how would I load the network available boot.wim from a floppy?
jaclaz
QUOTE (gnulnulf @ Oct 15 2009, 09:18 AM) *
the chain would be: PXE -> memdisk -> grub4dos -> boot.wim

how would I load the network available boot.wim from a floppy?


Why not PXE->grub4dos>(directory or disk image containing)boot.wim ? unsure.gif
http://diddy.boot-land.net/grub4dos/files/pxe.htm

I don't think there is a specific guide around, the most "similar" is this one AFAIK:
http://sysadminman.net/blog/2007/pxe-boot-...he-pxe-server-8

You'll have to experiment a bit, but the (pd) device should be available and so it should be the .wim in it.

Or maybe adding grub4dos and the floppy images inside the .wim? unsure.gif


jaclaz

Ben_Mott
hello ,
in windows 7 PE made by going to systen and security in control pannel
and choosing make recovery CD from the left of that dialog box.

to get network ability
type
STARTNET
on the command line
this will run the winpeini
and get wired networking started.
also microsoft menu starts in a file called winpeshl.ini
in which one line refers to it
X:\sources\recovery\recenv.exe
this CD is also got a driver store folder which is only 22MB large

you can put Bbart menu(nu2mnu) in system32 after mounting it with imagex /mountRW
and build on that using waik tools

Ben
jaclaz
@Ben Mott
What has this to do with the thread? unsure.gif

jaclaz
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.