how to install syslinux on hard disk? like grub4dos?

Edited by ignored, 08 October 2012 - 01:53 PM.

if i'm guessing right, i've to use this on cmd.exe along with some parameters which will create ldlinux.sys on hard disk and it will change mbr.

your first link shows "The Syslinux Project covers lightweight bootloaders for MS-DOS FAT filesystems (SYSLINUX)" but i have NTFS everywhere. Wikipedia says NTFS is supported since 4.06 version

ntfs(since 4.06), ?

Edited by ignored, 08 October 2012 - 04:13 PM.

i created a virtualbox machine,
next created 1 vhd file mounted it on imdisk, added syslinux.exe (5.00 pre7) and unmounted
next attached it to vbox which already has another vhd attached, so total 2 vhds attached

next i booted to liveXP, tried syslinux.exe --install c:

but now it says feature not implemented to non removable disk

syslinux.exe --force --directory /boot/syslinux/ --install C:

is there any other test build that allows installing on harddisk and supports NTFS? or do i have to create ext3/4 file system and use extlinux? which is another jungle?

??? Wonko, have you ever tried other builds or stable build on hard disk? anyway to chainload syslinux from grub4dos?

try the -fma switches?

syslinux.exe -f X: X:syslinux.bin

title Load syslinux menu

chainloader /syslinux.bin

title x86 OS above 4GB RAM

find --set-root /x.vhd.lzo

map --mem-min=4G

map --mem /x.vhd.lzo (hd0)

map --hook

root (hd0,0)

chainloader /ntldr

title Only map mem min to 4G and start syslinux

map --mem-min=4G

root (hd0,0)chainloader /syslinux.bin

Edited by ignored, 10 October 2012 - 06:38 PM.

title x86 OS above 4GB RAM

find --set-root /x.vhd.lzo

map --mem-min=4G

map --mem /x.vhd.lzo (hd0)

map --hook

root (hd0,0)

chainloader /ntldr

...

syslinux.exe -f X: X:syslinux.bin

...

title x86 OS above 4GB RAM

find --set-root /x.vhd.lzo

map --mem-min=4G

map --mem /x.vhd.lzo (hd0)

map --hook

root (hd0,0)

chainloader /ntldr

LABEL x

    KERNEL /path/to/memdisk

    INITRD /path/to/x.vhd.gz

does --mem-min=4G work on syslinux config or there is a different command?

Also, if syslinux.exe -m not specified, does it install on pbr by default?

is there any chance the following can work?
first grub4dos starts and performs the following

title Only map mem min to 4G and start syslinux

map --mem-min=4G

root (hd0,0)

chainloader /syslinux.bin

then syslinux starts and performs the following
APPEND --config-file="map --mem /x.vhd.lzo (hd0);map --hook;root (hd0,0);chainloader /ntldr"

Edited by ignored, 11 October 2012 - 07:01 AM.

This doesn't make sense.

What you are asking for makes no sense.

All that you are going to receive by way of responses are bodges that attempt to do the nonsensical task that you have set, from people who are either making wild guesses as to what you are actually trying to achieve, or who don't understand enough about the tool that you have chosen to know that what you are asking makes no sense. In both cases, that isn't going to help you.

State the actual thing that you are trying to achieve. State what your actual problem is. Stop focussing on the minutiae of a particular solution. Stop forcing people to guess what it is that you are actually trying to do.

Forcing people to guess is wasting your time. More importantly, it is wasting their time. Many people will choose not to waste their time on you.

label xxxxxx

menu label xxxxx

MENU INDENT 1

KERNEL /grub.exe

APPEND --config-file=/your-grub4dos.lst



your-grub4dos.lst



title x86 OS above 4GB RAM

find --set-root /x.vhd.lzo

map --mem-min=4G

map --mem /x.vhd.lzo (0xff)

map --hook

root (0xff)

chainloader (0xff)/NTLDR || chainloader (0xff)

 

Edited by Damnation, 11 October 2012 - 01:03 PM.

Edited by ignored, 11 October 2012 - 08:07 PM.

If I use syslinux, i loose the ability to map x86 OS above 4gb ram

Edited by Damnation, 11 October 2012 - 08:21 PM.

sooo there is no memdisk command that makes use of PAE like grub4dos does, right?

Sha0: Sooo, you're telling me

winvblock or firadisk does not support memdisk created by syslinux?

because obviously i intended to use one of these
...

No. But let's think about this... What is inside this x.vhd.lzo? An operating system? If so, which one? If so, is it 32-bit or 64-bit? If 32-bit, does it support PAE access to the RAM > 4 GiB? If it does, what RAM disk driver are you using that will use the RAM disk > 4 GiB?

Edited by ignored, 15 October 2012 - 09:36 AM.