Help - Search - Members - Calendar
Full Version: NEED HELP: Booting VistaPE from USB with Syslinux
The CD Forum > The CD Forum > Windows PE
simon99
I've bought myself a brand new 16 GB USB-Flash device and want now to incoperate my Live-Linuxes and VistaPE on this one device using syslinux (or Grub4Dos - but don't know that good).

There are some manuals here describing the procedure for small USB-Flash using the FAT filesystem - of course I don't want to use FAT on this a large drive and formatted it using FAT32. All Linuxes boot fine but VistaPE will not boot. So far I've tried to extract the bootsector from my VistaPE USB-Flash device (4 GB - FAT32) using DD and MBR-Wizard and renamed it to pe.bss

LABEL VistaPE
KERNEL pe.bss
APPEND -

Any ideas anyone???
jaclaz
You might have better fortune with grub4dos.

If you can boot any linux, than you can also invoke grub4dos as a kernel, and in turn grub4dos can chainload directly Vista's bootmanager (bypassing the bootsector).

The problem with FAT32 and NT based OS systems bootsectors can be fixed by properly formatting the stick.

First thing to try is fuwi's batches:
http://www.911cd.net/forums//index.php?sho...c=21702&hl=

Or you need to post some more details on how the stick was partitioned/formatted (i.e. using which tool) ....

jaclaz
cdob
QUOTE (simon99 @ Dec 3 2008, 08:04 AM) *
VistaPE on this one device using syslinux


Use a current syslinux, v3.70 at last.
Chain.c32 does chainload NT bootloaders like ntldr, setupldr.bin and bootmgr.

CODE
LABEL /bootmgr
KERNEL chain.c32 hd0 1 ntldr=/bootmgr
simon99
@jaclaz & cdob

thanks for the information - I'll try and report what worked best...

@cdob

KERNEL chain.c32 hd0 1 ntldr=/bootmgr

You adress the harddisk as hd0 which I guess would be /dev/hda or /dev/sda - depending if you use IDE or SATA - how can I make sure the USB-Stick is always booted with this method?
cdob
@simon99

As for syslinux and grub4dos: there is neither /dev/hda nor /dev/sda.

hd0 refers to first BIOS device hard disk.
Windows boot from first BIOS device only.
Almost all BIOS does change device order virtually: USB boot device is mapped as first BIOS device hard disk, hence hd0.

Grub4dos can change device order too.
simon99
my results so far....

I couldn't get syslinux to work with chain.c32 as I always got a "unable to enumerate drives" error.

It works with Siblo using...

KERNEL ntloader /bootmgr

...however it can't boot the local harddisk the syslinux way - even if Siblo is a derivate. I also tried chain.c32 to boot the local disk but failed with "chainboot failed" error. If anyone knows how to boot a local disk using Siblo I'd be glad. I testet the Siblo bootloader with my two laptops (Dell D830 and Panasonic Toughbook WF-Z4)

Tomorrow I'll try with Grub4Dos.

Generally I've to say that - except for grub - the bootloaders a very poorly documented.... thumbdown.gif
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-2013 Invision Power Services, Inc.