similar to: Still blocked with chain.c32

I'd like to use chain.c32 to allow the computer boot from HARDDISK if needed. If I use isolinux and boot from CD, the following works OK: chain.c32 hd0 But if I boot from USB Flash Key, it sometimes work and sometimes it doesn't and I have to use chain.c32 hd1 (it seems BIOS assigns hd0 to the flash key sometimes, so the real harddisk is hd1 in that case). Is there any way to tell

2013/8/7 Jonas Keidel <jonas at jonas-keidel.de> > > > 2013/8/6 H. Peter Anvin <hpa at zytor.com> > >> On 08/05/2013 11:29 PM, Jonas Keidel wrote: >> > 2013/8/6 H. Peter Anvin <hpa at zytor.com> >> > >> >> What about "chain.c32 hd1" or "chain.c32 hd1 swap"? >> >> >> > >> >

Code doesn't just write itself... Jonas Keidel <jonas at jonas-keidel.de> wrote: >I like to reactivate this topic because i don't see any changes at the >last >time... >So what about the topic? > > >2013/8/9 Jonas Keidel <jonas at jonas-keidel.de> > >> 2013/8/7 Jonas Keidel <jonas at jonas-keidel.de> >> >>> >>>

On 2019-4-10 1:20, Ady Ady via Syslinux wrote: >>> Test #2: if you unplug the USB and reboot the system, can you >>> successfully boot directly to the HDD's OS? >>> >> Yes. The only HDD, NTFS, WindowsXP native boot loader ntldr. > > > Let me rephrase my question. It was/is clear that you used to be able > to boot Windows when the first boot

Dear All: I am having trouble trying to dual-boot VMware and Linux, and I tried everything I could come up with. The situation is that /dev/sda is fully used by VMware and /dev/sdb is used by Linux. VMware uses Syslinux, so I thought this would be simple... However, it is not. The bootable FAT partition is too smal to have kernels in it. As a fallback I tried to chain-load GRUB, but that did not

On 2019-4-5 11:28, Ady Ady via Syslinux wrote: >> >> #This item fails >> label normal >> menu default >> menu label Boot from ^hard disk >> com32 chain.c32 hd1 > > >>From the Syslinux boot menu, press [Esc] in order to get to the boot prompt. At > the boot prompt, type in: > > normal > > and press [Enter]. > > Is there

Lu Wei, What Hard drive are you also trying to boot? The first and only fixed drive inside a computer? If so would the line to boot a local HD not be: LABEL LOCAL MENU LABEL Local operating system in harddrive (if available) kernel chain.c32 append hd0 -Adan On Thu, Apr 4, 2019 at 8:56 AM Adan Calderon <adancalderon at gmail.com> wrote: > > Lu Wei, > > For the DOS portion

Hi, I'm new to the list. I've replaced grub by extlinux to multi boot my system. Now, I can't manage to boot one of my systems. I have 5 hard drives, 3 of them being part of a raid0 array, and one of them being here for backup purposes (can be removed). So the total 'logical' drives number is 2. First drive: - primary partition holding a rescue Windows XP system (ntfs) -

With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). An example of this is whichsys.c32, which uses this. E.g., using an example from the wiki page - whichsys.c32 -iso- chain.c32 hd0 -sys- chain.c32 hd1 swap - results in a loop back to the isolinux menu as chain.c32 receives no parameters. Similarly, using -iso- memdisk

On 08/05/2013 11:29 PM, Jonas Keidel wrote: > 2013/8/6 H. Peter Anvin <hpa at zytor.com> > >> What about "chain.c32 hd1" or "chain.c32 hd1 swap"? >> > > That's right, but due to our pxe environment we need a static entry which > handles both, booting from first and second hdd if one fails. localboot > does so. > Actually this does

Hi, My problem is I have a particular system which has Linux (LFS) and Windows XP on one drive and Windows 10 on a second drive. I use extlinux to boot my systems and all three systems boot as expected, however in use I have found unsatisfactory interactions between the Windows XP and the Windows 10 systems. My question is: Is it possible on booting one of the Windows systems to hide

Hi, I am using syslinux-4.00-pre24, -pre27 and -pre31. chain.c32 fails for pre27 and pre31 for particular configs ... shown below. 1) works on pre24, fails with error message "Chainboot failed!" for pre27 and pre31 LABEL local MENU DEFAULT MENU LABEL Local Boot ... (skip PXE boot) KERNEL chain.c32 APPEND hd0 0 2) works on all three. LABEL local

I am trying to use chain.c32 to boot windows xp from a hard disk. In my pxelinux.cfg file I have the following: Prompt 1 Default menu1 Timeout 2 Label menu1 Kernel chain.c32 hd0 1 When my system boots it gives me the following usage error Usage: chain.c32 (hd|fd)# [partition] Boot: If I type chain.c32 hd0 1 at the boot prompt the system boots windows ok. Any help would be

Hi. I prefer using the syslinux boot loader and recently undertook a project of creating a multiboot USB drive that boots using syslinux. The aim is to create a medium from which various live linux environments can be run for things like system maintenance, installation, and perhaps demonstration. I anticipate using this multiboot USB drive on mostly legacy, BIOS systems, if that matters. As

Hello all. Here[1] is a branch where chain.c32 can chain-boot a partition on a GPT disk when given the partition index. boot: chain hd1 84 (For example.) - Shao Miller [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ chain_gpt

I was seeing if I could use chain.c32 to boot windows off of a second drive. I'm pretty sure I'm using it right. Could it be because these are sata drives? I installed FC5 on a second sata drive I had in my new machine. Of course Grub didn't work as I wanted so I decided to try extlinux and if I can get it to work I might switch to syslinux so that I can edit the boot info in windows

Hi! Can extlinux boot Linux kernel from the second drive? I want to leave Windows XP on the first IDE drive and put Linux to the first partition (ext2/ext3) on the second IDE drive. I am allowed to change MBR on the first drive. Will the following configuration work? /dev/hda1 - Windows /dev/hdb1 - Linux root (/, /boot, ...) /dev/hda - extlinux in MBR /boot/vmlinuz extlinux /boot

Greetings, I encounter a problem that should be basic, but I can't get a clue. I have 8G USB disk formatted as FAT32. I run (syslinux -i -s -r -m H:) to make it bootable, and write syslinux.cfg according to the documents, but it will not boot some items. Syslinux is 6.03, bios files used. The whole syslinux.cfg file:

I wrote a new module "whichsys.c32" which detemines which command to execute, based on the Syslinux bootloader variant. In the near future it should/can be replaced by a lua script. But for people who want small binaries: whichsys.c32 is +/- eighty times smaller than lua.c32, atm. Usage: whichsys.c32 [-iso- command] [-pxe- command] [-sys- command] Examples: whichsys.c32 -iso-

> More context to this: syslinux_run_command calls into load_kernel(), and somewhere behind load_kernel things break. This is also broken at the boot: console prompt. Any commands executed at the boot: prompt also lose all parameters. > > > With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). > > An