search for: zipdrives

-----BEGIN PGP SIGNED MESSAGE----- The autodetection routines for some linux modules can tie up the machine for several seconds at a time. By trying to open devices not present on the machine, a local user can disrupt service considerably. A very simple exploit is victim$ ls /dev/*/* repeatedly. A suggested fix is to remove or chmod 0 device nodes for hardware not installed on the

...t time for devices which are considered hard disks by the BIOS. Unfortunately, this is not possible for devices which are considered floppy disks, which includes zipdisks and LS-120 superfloppies. The -z option is useful for USB devices which are considered hard disks by some BIOSes and zipdrives by other BIOSes. $ ./syslinux-git/working-directory/linux/syslinux Usage: ../syslinux-git/working-directory/linux/syslinux [options] device --offset -t Offset of the file system on the device --directory -d Directory for installation target --install -i Install over the current bo...

I just released Syslinux 4.00-pre40. This is now a Release Candidate, meaning that it is on track to be released as it currently is unless I hear back about currently unexpected problems. If you have a chance, please pretty please test it. -hpa

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

On 04.08.2016 00:58, Erik Sandberg via Syslinux wrote: > 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

"use integer" limits integers to 2^31-1 on 32 bits, which makes imgsize to be -1 on DVD images Signed-off-by: Pascal Terjan <pterjan at mandriva.com> --- utils/isohybrid.in | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/utils/isohybrid.in b/utils/isohybrid.in index 4671036..e98c59f 100644 --- a/utils/isohybrid.in +++ b/utils/isohybrid.in @@ -17,7 +17,6

...000000 +0400 +++ syslinux-4.02/libinstaller/syslxopt.c 2010-08-17 22:37:24.955852630 +0400 @@ -125,5 +125,5 @@ void __attribute__ ((noreturn)) usage(in "\n" " The -z option is useful for USB devices which are considered\n" - " hard disks by some BIOSes and zipdrives by other BIOSes."); + " hard disks by some BIOSes and zipdrives by other BIOSes.\n"); exit(rv);

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.2016 00:58, Erik Sandberg via Syslinux wrote: >

Correct typos. Improve format for asciidoc-to-manpage conversion. Wrap text. Correct info. Help phase-out deprecated and/or conflicting options. diff U3 /syslinux-6.03/txt/syslinux.txt /wip/txt/syslinux.txt --- /syslinux-6.03/txt/syslinux.txt Mon Oct 06 16:27:44 2014 +++ /wip/txt/syslinux.txt Sat Dec 27 18:20:27 2014 @@ -30,9 +30,10 @@ unmounted file system. For the DOS/Win32/Win64 installers,

In other words: I'm suggesting to use WinImage as it also allows easy injection of new files *and* updating of already existing files. May I ask which vendor is distributing a DOS FW update that is 20MB? I'd like to see the files. Sometimes you just need the .bin/.rom and the actual FW update EXE and it would fit a 5MB FDD image. On Mon, Jun 18, 2018 at 2:03 PM, R S <rene.shuster at

...http://bootcd.narod.ru/images_e.htm (and I'd indeed recommend WinImage in its Pro-version for modifications like injecting files, as well as reading the Memdisk page in complete detail to get parameters right for use in Syslinux/Isolinux). Not sure if bootable images from exotic things like Zipdrives or LS-120/LS-240 drives exis (as non-harddisk image). Bernd

I've got a bootable USB pendrive with Syslinux 3.72, and while it usually works, there are a few computers, where I get the syslinux prompt, but it neither loads the configuration file, nor I'm able to boot anything. The only message I get on screen (apart from boot:) is "Could not find kernel image: linux". The configuration (and kernels) are in syslinux directory, but even

Allow the user to define the type of partition and its number from the command line. The following example creates partition numer 4 with type 1c (hidden FAT32 LBA): isohybrid -fstype=28 -pentry=4 hybrid.iso --- utils/isohybrid.in | 11 ++++++++--- 1 files changed, 8 insertions(+), 3 deletions(-) diff --git a/utils/isohybrid.in b/utils/isohybrid.in index 83f9dc0..d67a2b5 100644 ---

Hello Peter & Jeremy, I've found an ordinary desktop PC (with Phoenix Award BIOS 6.00PG) that won't boot off a USB stick created by livecd-tools-024 with syslinux (tested both versions 3.75 and 3.81). The boot process drops to the "boot:" prompt with an error message: could not find kernel image: linux The same USB stick boots fine on any other computer I could find.

Hi, I've created a rPath appliance which boots from a USB memory stick. Today I upgraded extlinux on my rPath appliance and the memory stick froze the system during POST. After a lot of trial and errors I found out this could be fixed by wiping the USB memory stick and reproduced it by writing extlinux (3.72) to the stick. I finally found out how to fix this issue, by entering the correct

...* MEMDISK: Give a way to query the boot loader type while running MEMDISK; see memdisk/memdisk.doc and sample/mdiskchk.c. * mkdiskimage: substantially improved mkdiskimage which, among other things, can now be used to initialize USB keys as zipdrives; see README.usbkey for more information. Begin3 Title: syslinux Version: 3.02 Entered-date: 2005-01-04 Description: SYSLINUX is a collection of boot loaders for the Linux operating system which operates off Linux ext2/3 filesystems, MS-DOS FA...

...ges_e.htm > > (and I'd indeed recommend WinImage in its Pro-version for modifications > like injecting files, as well as reading the Memdisk page in complete > detail to get parameters right for use in Syslinux/Isolinux). > > Not sure if bootable images from exotic things like Zipdrives or > LS-120/LS-240 drives exis (as non-harddisk image). > > Bernd > > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > -...

...* MEMDISK: Give a way to query the boot loader type while running MEMDISK; see memdisk/memdisk.doc and sample/mdiskchk.c. * mkdiskimage: substantially improved mkdiskimage which, among other things, can now be used to initialize USB keys as zipdrives; see README.usbkey for more information. Begin3 Title: syslinux Version: 3.01 Entered-date: 2005-01-03 Description: SYSLINUX is a collection of boot loaders for the Linux operating system which operates off Linux ext2/3 filesystems, MS-DOS FA...

LDLINUX.SYS uses a working directory. The documentation seems to improve if that fact is made explicit. So the working directory is added to the documentation (with a bit of vagueness and possibly not entirely correct, to keep it readable). Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- This is a result of today's discussion of a previous patch ("Describe the --directory

Op 2014-06-20 om 15:56 schreef Ady: > > The Perl variant, isohybrid.in, seems to be getting left behind > regarding several patches. I don't recall whether there is at least > some mention in the isohybrid docs about the existence of 2 variants > included in Syslinux (and that is in addition to other isohybrid > methods outside Syslinux). Is there any reference? >