7 replies to this topic

[xorred]

I had an perfectly working WinPE (vista) image on a DVD, and a shell script that just made the usb bootable (once you copy all files from dvd to usb).

So... here's the thing: that script took care only of the boot sector, but seems the BCD data does not know that it's moved from DVD to USB.

So... whenever I try to boot, it gives me this /boot/bcd error that it cannot start the os. (0xc0000225).

I read here and there, that BCD needs to be updated, but have no freaking idea what needs to be done. Have a VM of xp and w7 here, so any commands that contain bcedit should work on the w7 vm...

On a second note:
folder BOOT structure:
isolinux
syslinux
dos
fonts
grub.exe
BCD
BOOT.SDI
chain.c32
BOOTSECT.EXE
ETFSBOOT.COM

I guess I need to edit that BCD or something else in the folder above (/)?

Here is my syslinux.cfg, which contains grub4dos entries as you will see:
LABEL vistape
MENU LABEL VistaPE
KERNEL /BOOT/grub.exe
APPEND --config-file="find --set-root /VISTAPE.WIM;chainloader /BOOTMGR"

[xorred]

I had an perfectly working WinPE (vista) image on a DVD, and a shell script that just made the usb bootable (once you copy all files from dvd to usb).

So... here's the thing: that script took care only of the boot sector, but seems the BCD data does not know that it's moved from DVD to USB.

So... whenever I try to boot, it gives me this /boot/bcd error that it cannot start the os. (0xc0000225).

I read here and there, that BCD needs to be updated, but have no freaking idea what needs to be done. Have a VM of xp and w7 here, so any commands that contain bcedit should work on the w7 vm...

On a second note:
folder BOOT structure:
isolinux
syslinux
dos
fonts
grub.exe
BCD
BOOT.SDI
chain.c32
BOOTSECT.EXE
ETFSBOOT.COM

I guess I need to edit that BCD or something else in the folder above (/)?

Here is my syslinux.cfg, which contains grub4dos entries as you will see:
LABEL vistape
MENU LABEL VistaPE
KERNEL /BOOT/grub.exe
APPEND --config-file="find --set-root /VISTAPE.WIM;chainloader /BOOTMGR"

[Icecube]

For your syslinux.cfg, the following should work too:

LABEL vistape

MENU LABEL VistaPE

COM32 /BOOT/chain.c32

APPEND ntldr=/BOOTMGR

[xorred]

For your syslinux.cfg, the following should work too:

LABEL vistape

MENU LABEL VistaPE

COM32 /BOOT/chain.c32

APPEND ntldr=/BOOTMGR

that one doesn't even try to load - I select, press enter - and stay in the menu, nothing happens...

[was_jaclaz]

that one doesn't even try to load - I select, press enter - and stay in the menu, nothing happens...

Where is chain.c32?
In root or in \BOOT\?
And BOOTMGR?

jaclaz

[xorred]

BOOTMGR is in /, 438 KB.
chain.c32 is in syslinux folder, isolinux folder, and in BOOT folder - from last syslinux build. the 2 folders (syslinux & isolinux) are in BOOT folder, which is in /.
/
- > BOOTMGR
- > BOOT
- - > syslinux - chain.c32
- - > isolinux - chain.c32
- - > chain.c32

The really interesting thing is, that it's just working on the DVD.... same file layout, same files....

[Icecube]

In that case, the following should work:

LABEL vistape

MENU LABEL VistaPE

COM32 chain.c32

APPEND ntldr=/BOOTMGR

I am not sure if Syslinux can find the /BOOT/syslinux directory correctly. I always use /boot/syslinux (but this may conflict with Windows booting ).

[xorred]

but it can find /BOOT/syslinux in the DVD and boot just fine from it? I'll rename and report.
Renamed to /boot/, same thing. All other things boot (I load bunch of isos from syslinux) fine, but the VistaPE does not even try to boot with the NEW chain.c32 config. Strange?

turned out I missed the c in c32. works as a charm now from usb.

Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!