search for: zipdriv

-----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

...ine ./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 and stupid mode --raid -r Fall back to the next device on boot failure --once=... -o Execute a command once upon boot --clear-once...

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

.../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 number of heads --stupid -s Slow, safe and stupid mode --raid -r Fall back to the next device on boot failure --once=... -o Execute a command once upon boot --clear-once...

...s/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 @@ # use bytes; -use integer; use Fcntl; # Use this fake geometry (zipdrive-style...) @@ -92,7 +91,7 @@ $cylsize = $h*$s*512; $frac = $imgsize % $cylsize; $padding = ($frac > 0) ? $cylsize - $frac : 0; $imgsize += $padding; -$c = $imgsize/$cylsize; +$c = int($imgsize/$cylsize); if ($c > 1024) { print STDERR "Warning: more than 1024 cylinders ($c).\n&qu...

...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);

.../? > 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 number of heads > --stupid -s Slow, safe and stupid mode > --raid -r Fall back to the next device on boot failure > --once=... -o Execute a command once...

...failure mode. *-t*, *--offset* 'offset':: (Linux syslinux/syslinux-mtools ONLY) Indicates that the filesystem is -at an offset from the base of the device or file. +at an offset from the base of the device or file. Some older versions +did not accept the short format, *-t*. *-z*, *--zipdrive* Assume zipdrive geometry ('--heads 64 --sectors 32'). See also *--head* @@ -195,7 +195,7 @@ iflag=fullblock conv=notrunc of=/dev/sda + Note: using 'cat' for writing the MBR can under some circumstances cause -data loss or overwritting. For this reason, using 'dd'...

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

...19,6 +19,13 @@ use bytes; use Fcntl; +# Use Linux as default partition type (any better ideas?) +# e.g.: -fstype=28 (hidden FAT32 LBA) +our $fstype ||= 0x83; +# Use first partition slot +# e.g.: -pentry=4 (4th partition, as in original Zip discs) +our $pentry ||= 1; + # Use this fake geometry (zipdrive-style...) $h = 64; $s = 32; @@ -135,8 +142,6 @@ $bcyl = 0; $ehead = $h-1; $esect = $s + ((($cc-1) & 0x300) >> 2); $ecyl = ($cc-1) & 0xff; -$fstype = 0x83; # Linux (any better ideas?) -$pentry = 1; # First partition slot for ( $i = 1 ; $i <= 4 ; $i++ ) {...

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...

...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...

...irectory on the device). +specified name (relative to the root directory on the device). ldlinux.sys +will then use this subdirectory as its working directory. .TP \fB\-t\fP, \fB\-\-offset\fP \fIoffset\fP Indicates that the filesystem is at an offset from the base of the @@ -88,7 +88,7 @@ Assume zipdrive geometry (\fI\-\-heads 64 \-\-sectors 32). All the configurable defaults in \s-1SYSLINUX\s+1 can be changed by putting a file called .B syslinux.cfg -in the install directory of the boot disk. This +in the ldlinux.sys working directory. This is a text file in either UNIX or DOS format, contain...

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? >