search for: bootsecfile

...ms... If possible, I would like to have syslinux generate the .bss data as a file instead of writing to the partition. This will retain the existing Windows bootloader while allowing me to chain load the file generated. Looking at the online documentation, there is an optional value for the 'bootsecfile', but I can't get it to work. I have tried: syslinux[64].exe -i "/path/to/syslinux/file" c: bootsecfile.bss syslinux[64].exe -i "/path/to/syslinux/file" c:\bootsecfile.bss syslinux[64].exe -i "/" c: bootsecfile.bss syslinux[64].exe -i "/" c:\bootsec...

> On Sat, Jan 5, 2019 at 3:17 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > syslinux[64].exe -i -f c: bootsecfile.bss > > > > > > This should have been the form for your desire as specifying the > > > filename should have told it to create the BSS instead of writing it > > > to the VBR. Being the "fixed" HDD instead of a removable drive like a > > > USB s...

> syslinux[64].exe -i -f c: bootsecfile.bss > > This should have been the form for your desire as specifying the > filename should have told it to create the BSS instead of writing it > to the VBR. Being the "fixed" HDD instead of a removable drive like a > USB stick, "-f" is necessary. Hmm, instea...

...I would like to have syslinux generate the .bss data as a > file instead of writing to the partition. This will retain the > existing Windows bootloader while allowing me to chain load the file > generated. Looking at the online documentation, there is an optional > value for the 'bootsecfile', but I can't get it to work. I have > tried: > > syslinux[64].exe -i "/path/to/syslinux/file" c: bootsecfile.bss > syslinux[64].exe -i "/path/to/syslinux/file" c:\bootsecfile.bss > syslinux[64].exe -i "/" c: bootsecfile.bss > syslinux[64].ex...

On Sun, Jan 6, 2019 at 12:58 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Sat, Jan 5, 2019 at 3:17 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > syslinux[64].exe -i -f c: bootsecfile.bss > > > > > > > > This should have been the form for your desire as specifying the > > > > filename should have told it to create the BSS instead of writing it > > > > to the VBR. Being the "fixed" HDD instead of a removable drive like a...

On Sat, Jan 5, 2019 at 3:17 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > syslinux[64].exe -i -f c: bootsecfile.bss > > > > This should have been the form for your desire as specifying the > > filename should have told it to create the BSS instead of writing it > > to the VBR. Being the "fixed" HDD instead of a removable drive like a > > USB stick, "-f" is n...

Oh somehow I never noticed that "bootsecfile" option. That's probably what I need to use. I was looking at the source to see how the --mbr flag works and thought that there should be a way to do the same thing with the other mbr files. On Thu, Aug 4, 2016 at 2:41 AM poma <pomidorabelisima at gmail.com> wrote: > On 04.08.20...

Does anyone know how to install the gptmbr.bin onto a USB drive with Windows? I noticed that it would be really easy to modify the source of the installer to install gptmbr.bin instead of mbr.bin with the -m flag, but I'd like a solution that doesn't require me to maintain my own custom syslinux. I'm open to writing and submitting a patch to add a new flag (say -g) to install

...79 100644 --- a/doc/syslinux.txt +++ b/doc/syslinux.txt @@ -56,11 +56,11 @@ In order to create a bootable Linux floppy using SYSLINUX, prepare a normal MS-DOS formatted floppy. Copy one or more Linux kernel files to it, then execute the DOS command: - syslinux [-sfrma][-d directory] a: [bootsecfile] + syslinux [-sfrma][-d subdirectory] a: [bootsecfile] (or whichever drive letter is appropriate; the [] meaning optional.) -Use "syslinux.com" (in the dos subdirectory of the distribution) for +Use "syslinux.com" (in the DOS subdirectory of the distribution) for pl...

...39;s more like > running `cat gptmbr.bin > /dev/sdb` but on Windows. > > - Erik Sandberg > When you offer to patch, why not cover both - PE32 and ELF, MBR and GPT $ wine64 /usr/share/syslinux/syslinux64.exe /? Usage: Z:\usr\share\syslinux\syslinux64.exe [options] <drive>: [bootsecfile] --directory -d Directory for installation target --install -i Install over the current bootsector --update -U Update a previous installation --zip -z Force zipdrive geometry (-H 64 -S 32) --sectors=# -S Force the number of sectors per track --heads=# -H Force n...

...r your great util syslinux! It works fine for me. I discovered all web and package content, man's, but i didn't find info about what are -f and -r options are used for. When I start syslinux.exe in Windows, I get such help message: Usage: syslinux.exe [-sfmar][-d directory] <drive>: [bootsecfile] I know: -s safe, slow, stupid version of loader, for old BIOSes -m write MBR to device -a make partition boot flag active But -f and -r options are undocumented. Thank you, Ruslan from Russia.

...c193 100644 --- a/doc/syslinux.txt +++ b/doc/syslinux.txt @@ -56,7 +56,7 @@ In order to create a bootable Linux floppy using SYSLINUX, prepare a normal MS-DOS formatted floppy. Copy one or more Linux kernel files to it, then execute the DOS command: - syslinux [-sfrma][-d directory] a: [bootsecfile] + syslinux [-sfrma][-d subdirectory] a: [bootsecfile] (or whichever drive letter is appropriate; the [] meaning optional.) @@ -68,13 +68,15 @@ WinNT/2000/XP. Under Linux, execute the command: - syslinux [-sfr][-d directory][-o offset] /dev/fd0 + syslinux [-sfr][-d subdirectory][-o...

I intend to release SYSLINUX 3.73-pre7 as SYSLINUX 3.73 as soon as possible. Please let me know if there are any outstanding bugs with 3.73-pre7 that either haven't been reported or I have forgotten about... it's been a while. -hpa

...fset of the file system on the device (mtools installer) --directory -d Directory for installation target (mtools installer) - Gert Hulselmans $ wine ./syslinux-git/working-directory/win32/syslinux Usage: Z:\home\gert\syslinux-git\working-directory\win32\syslinux.exe [options] <drive>: [bootsecfile] --install -i Install over the current bootsector --update -U Update a previous EXTLINUX installation --zip -z Force zipdrive geometry (-H 64 -S 32) --sectors=# -S Force the number of sectors per track --heads=# -H Force number of heads --stupid -s Slow, safe...