14 replies to this topic

[delicatepc]

Hi Folks,

Is anyone having BOOTMGR issues with Syslinux 4.01?

I am doing the following to chainload it:

LABEL -

MENU LABEL BOOTMGR

	COM32 /boot/syslinux/chain.c32

	APPEND boot ntldr=/BOOTMGR

My file directory looks like so:

C:\TESTING
| BOOTMGR
+---BOOT
| | BCD
| | boot.sdi
| | bootsect.exe
| | ETFSBOOT.COM
| | memtest.exe
| |
| +---en-us
| | bootsect.exe.mui
| |
| +---fonts
| | chs_boot.ttf
| | cht_boot.ttf
| | jpn_boot.ttf
| | kor_boot.ttf
| | wgl4_boot.ttf
| +---isolinux
| | isolinux.bin
| | isolinux.cfg
| |
| \---syslinux
| chain.c32
| econfig.c32
| hdt.c32
| ldlinux.sys
| mbr.bin
| memdisk
| memtest
| menu.c32
| reboot.c32
| syslinux.cfg
| vesamenu.c32
|
+---EFI
| \---microsoft
| \---boot
| | bcd
| |
| \---fonts
| chs_boot.ttf
| cht_boot.ttf
| jpn_boot.ttf
| kor_boot.ttf
| wgl4_boot.ttf
|
+---SOURCES
| boot.wim
|
\---ubcd
|
+---menus
| \---syslinux
| main.cfg

Its seems BOOTMGR chainloads normally but then it conks out and gives an error:

File: \Boot\BCD
Status: 0xc0000225
Info: An error occured while attempting to read the boot configuration data.

If I format the drive to just FAT32 and transfer files to the usb drive (so we are using FAT32's inherent programming telling it to boot NTLDR or BOOTMGR) the drive boots successfully (get a listing of available options from the BCD store). I have several different BCD files and I have even tried copied everything from a working syslinux 3.8x USB stick that has BOOTMGR loading however it still doesnt seem to work.

I have tested on a Lenovo W500 and Dell E4300 with same result. I am using Windows 7 RTM to build the stick. I have tried a few sources of the BOOTMGR/etc files and not much luck yet...

Anyone have BOOTMGR issues with syslinux 4.01? The chainloading seems fine but I was wondering if anyone could shed some light on why its having a hard time accessing the boot configuration data...

thank you,
dpc

[Icecube]

Can you try this?

LABEL bootmgr

MENU LABEL BOOTMGR

	COM32 /boot/syslinux/chain.c32

	APPEND fs ntldr=/BOOTMGR

[delicatepc]

Can you try this?

LABEL bootmgr

MENU LABEL BOOTMGR

	COM32 /boot/syslinux/chain.c32

	APPEND fs ntldr=/BOOTMGR

IT WORKS!

What happened? A change in chain.c32?

Thank you,

[Icecube]

From syslinux-3.85, chain.c32 will load the boot sector of the partition too, when booting a file with ntldr=. In earlier versions this was not done.
It is possible that it only works completely correct from syslinux-4.00-pre39 (set-hidden option fix: http://git.zytor.com...83d9e0c15ead03).

So now you need to specify the partition number too (and not only the drive number).
When you want to boot Windows from the same partition as the one where you installed SYSLINUX, you can use 'fs'. 'fs' will pass the boot drive and partition number of the syslinux partition to the booted file (NTLDR, BOOTMGR, SETUPLDR.BIN, ...).

[delicatepc]

Sounds good!

Thank you IceCube!,
dpc

[delicatepc]

Since the chainloading has changed in syntax slightly would the following still be proper:

LABEL -
MENU LABEL Boot Partition 2 of USB Drive
COM32 /boot/syslinux/chain.c32
APPEND hd0 2

LABEL -
MENU LABEL Boot Partition 3 of USB Drive
COM32 /boot/syslinux/chain.c32
APPEND hd0 3

LABEL -
MENU LABEL Boot Partition 4 of USB Drive
COM32 /boot/syslinux/chain.c32
APPEND hd0 4

LABEL -
MENU LABEL Boot next device
COM32 /boot/syslinux/chain.c32
APPEND hd1 swap

These are all for loading partitions off the same usb drive running syslinux (in order to get around a setup.exe limitation in Vista and later).

Thank you,
dpc

[Icecube]

Since the chainloading has changed in syntax slightly would the following still be proper:

Yes.

LABEL -

MENU LABEL Boot Partition 2 of USB Drive

COM32 /boot/syslinux/chain.c32

APPEND hd0 2

Even better, use "," instead of " " for avoiding ambiguities:

LABEL -

MENU LABEL Boot Partition 2 of USB Drive

COM32 /boot/syslinux/chain.c32

APPEND hd0,2

You can also use "boot" in combination with a partition number:

LABEL -

MENU LABEL Boot Partition 2 of USB Drive

COM32 /boot/syslinux/chain.c32

APPEND boot,2

[delicatepc]

Got it. Many thanks IceCube!

~
dpc

[ghjm]

This solved my problem also.

Unfortunately I grew old and grey while trying to find it.

What will the girls think of me now?

[Wonko the Sane]

What will the girls think of me now?

The plain truth: you are a geek, and you can do nothing about it.


Wonko

[c400]

very helpful!!!! thx

[deckoff]

The plain truth: you are a geek, and you can do nothing about it.


Wonko

Honestly, for some 30 minutes of fun time girls can seriously spoil and steal the other 23:30 hours of good geek time

[Wonko the Sane]

Honestly, for some 30 minutes of fun time girls can seriously spoil and steal the other 23:30 hours of good geek time

But, on the other hand, I know a lot of geeks wanting to get that "half hour of fun" and very few "normal" people wanting to have "23:30 hours of geekitude"....


Wonko

[protools23]

my preference 23:55 of geekness and 5 minutes with mis. right hand lol

[zzx]

Can you try this?

LABEL bootmgr

MENU LABEL BOOTMGR

	COM32 /boot/syslinux/chain.c32

	APPEND fs ntldr=/BOOTMGR

I have issue with this.

1. Win 7 boots and works. And I want to have syslinux to chose what to boot. So
2. syslinux -m X: (where X: boot partition, FAT32)
after that
if any of these :
APPEND fs ntldr=/BOOTMGR
APPEND boot 1 ntldr=/BOOTMGR (or might be any partition set except 0)
then syslinux report "Requested partition not found!"
if
APPEND boot 0 ntldr=/BOOTMGR
then bootloader seems to be found and has passed control to it , but says :
File: BootBCD
Status: 0xc0000225
Info: An error occured while attempting to read the boot configuration data.

If I want to boot to windows again just need boorrec /fixboot from Win PE.

syslinux ver 4.04 and 4.05 ... same thing.

Please point out what I'm missing.... tx.

Edited by zzx, 07 March 2012 - 10:33 AM.