similar to: SYSLINUX 2.01 released

Displaying 20 results from an estimated 6000 matches similar to: "SYSLINUX 2.01 released"

2002 Oct 29
2
SYSLINUX 2.01-pre1 released
This isn't strictly speaking a SYSLINUX release, it's a change to MEMDISK and mkdiskimage to allow the creation of hard disk images with DOSEMU headers. This should make it easier to create bootable DOS hard disk images under DOSEMU. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa
2002 Oct 25
3
Here we go - SYSLINUX 2.00 released
Can't hold it off any longer... here it is :) Changes in 2.00: * ALL: Add support for "COM32" (32-bit COMBOOT) images. * ALL: Add an API for COMBOOT/COM32 images. See comboot.doc for details. There is a C development environment for COM32 being created; it should be ready at some point in the future. * Fix mbr.asm so that it
2007 Feb 06
0
Broken file reading for fat16 with 3.35+?
Hello, I noticed after upgrading from 3.20, I haven't been able to get syslinux to boot properly with menu.c32 or mboot.c32 from a USB key. I get an error saying invalid kernel when its trying to load menu.c32 or mboot.c32 (or any other kernel for that matter). I tried 3.35 and 3.36-pre5. Same exact behaviour. I'm using the following to compile: gcc version 3.2.3 20030502 (Red Hat Linux
2007 Nov 15
3
3.53-pre5 released - release candidate
Hi all, I have received a fair number of bug reports over the last few weeks -- even days -- and I am therefore declaring 3.53-pre5 a release candidate for a 3.53 bug fix release. This 3.53 will not contain either of the two major features under development -- client side state (including boot-once) and gPXE integration -- since I want to avoid destabilizing the code base beyond the bug
2007 Feb 06
3
Syslinux: Broken file reading for fat16 with 3.35+?
Hello, I noticed after upgrading from 3.20, I haven't been able to get syslinux to boot properly with menu.c32 or mboot.c32 from a USB key. I get an error saying invalid kernel when its trying to load menu.c32 or mboot.c32 (or any other kernel for that matter). I tried 3.35 and 3.36-pre5. Same exact behaviour. I'm using the following to compile: gcc version 3.2.3 20030502 (Red Hat Linux
2005 Jan 05
2
SYSLINUX-3.02 released
Tying up lose ends, and adding the ethersel module for the Etherboot folks. -hpa Changes in 3.02: * SYSLINUX: The "unix" installer now sets the MS-DOS attributes (hidden, system, readonly.) * COM32 library: build the .lnx (test modules for running under Linux) as architecture native modules, in case i386 devel libraries aren't
2005 Feb 21
2
memdisk: regression: 2.11 -> 2.12 (up to 3.07)
- mkdiskimage -d image.dsk 2 64 32 - load it in dosemu and make it bootable with sys - isolinux: label 999 kernel memdisk append initrd=image.dsk harddisk c=2 h=63 s=32 results: memdisk 2.11 -> boots memdisk > 2.11 (up to 3.07) -> hangs The following message is printed in the boot messages > 2.11: MEMDISK: image has a fractional end sector The complete error message
2005 Jan 03
1
SYSLINUX 3.01 released
Some people have reported portability problems with SYSLINUX 3.00, mostly due to the use of HDIO_GETGEO_BIG, which is deprecated; additionally, the advanced menu system wouldn't build for everyone due to a spurious reference to %ebp. This release fixes these things, plus makes the extlinux installer default to zipdisk geometry (64 heads, 32 sectors) if it can't guess anything else.
2005 Feb 17
0
memdisk: image has a fractional end sector -> hangs
syslinux-3.0.7 Cannot boot memdisk+harddisk image. 1) mkdiskimage -d image.dsk 10 64 32 (I get a 10485888 bytes file) 2) start dosemu+freedos with image.dsk loaded as d: and do sys d: then copy some files to d: 3) reboot dosemu using image.dsk as c: to verify it's bootable, and it is C:\>ver FreeCom version 0.82 pl 3 XMS_Swap [Mar 06 2004 10:49:37] C:\> 4) isolinux.cfg: label 999
2005 Oct 04
3
Boot DOS through Pxelinux
Hello list, My set up is almost complete in booting DOS through PXELinux, but I need to create a DOS boot image from (2 )DOS floppies. I've search the archives and google but didn't find any relavant info... My current set up now works with the standard setup (with one DOS floppy): kernel: memdisk append: initrd=floppy.img ramdisk=10000 My goal to is create a floppy.img from 2 DOS
2005 Aug 24
1
SYSLINUX 3.10 released
Changes in 3.10: * gcc 4.0.1 compilation fixes. * Add support for querying the PCI BIOS in libcom32 (used by ethersel et al.) * Fix PCI handing (ethersel etc) on several old chipsets (and VMWare.) * Try to deal with systems with broken EBIOS. * New API call to do "localboot". * New API call to query features.
2016 Mar 05
2
build problems with 6.04-pre1
hello everybody, apologies if I'm missing something here Just tried to build 6.04-pre1 test version with: make bios installer and found some problems all (seemingly) related to inaccurate paths in various Makefiles. I enclose a complete patch at the end of this email, which details the problems I found and how they got fixed for me. As an example, this is the first error I got:
2003 Feb 07
1
Security issues with SYSLINUX 2.01
I have just received some audit info on the SYSLINUX 2.01 installer running setuid. There seems to be some issues, and although I can fix them easily enough I'm somewhat questioning the whole approach. The other alternative would be to make the syslinux installer a wrapper around mtools, and use mtools for the filesystem access. Since this would be done entirely in userspace, as a normal
2005 Sep 03
0
SYSLINUX 3.11 released
Changes in 3.11: * MEMDISK: Fix bug by which accessing the real floppy disk as B: in MS-DOS was broken. * Simple menu system: allow tweaking of the screen layout. * Simple menu system: better command-line editing, correctly handle command lines above 256 characters. * PXELINUX: revert memory allocation change that caused problems
2004 Jun 30
1
mkdiskimage question (another one?)
Hi, I am trying for quite some time to create a bootable hd disk image with mkdiskimage (included in the syslinux distribution) and the combination isolinux/memdisk. It just won't work:-} I have done the following: [snip] # ./mkdiskimage -d -o disk 256 32 1 640 # losetup -o 640 /dev/loop3 disk # mount /dev/loop3 /mnt/3 # mount | grep loop3 /dev/loop3 on /mnt/3 type vfat (rw) :: copy
2008 Oct 17
1
possible build problem with syslinux-3.72
Howdy, I just did a build on my CentOS 5.2 (x86_64) system and noticed the following error msg. I don't think this is a problem for me but I wanted the developers to be aware of it. Regards, and thanks for your time, George... make[1]: Leaving directory `/tools/pxelinux/syslinux-3.72/utils' ls -l version.gen version.h version.mk mbr/mbr.bin mbr/gptmbr.bin core/pxelinux.0
2012 Nov 01
1
Syslinux 4.06 and 5.00-pre9 Binary Sizes
This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25
2003 Nov 23
0
SYSLINUX 2.07 released
After all the bug fixes over the last few weeks I thought it was high time to release 2.07. It certainly doesn't fix everything, but it fixes several important problems people have reported. Changes in 2.07: * MEMDISK: Workaround for BIOSes which go into a snit when they get a RESET command for the floppy system when there is no floppy in the system.
2014 Jan 30
2
[PATCH 04/05] utils/mkdiskimage.in: New option -S to sync zeroizing after each cylinder and to issue pacifier messages
utils/mkdiskimage.in: New option -S to sync zeroizing after each cylinder and to issue pacifier messages. --- utils/mkdiskimage_patched_03.in 2014-01-30 20:54:27.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:59:19.000000000 +0100 @@ -139,6 +139,7 @@ if ( $file eq '' || $c < 1 || $h < 1 || print STDERR " -4 use partition entry 4 (standard for
2003 Jul 02
6
help: booting dos from syslinux/memdisk
Thanks for Remko for his help to solve the fractional cylinder problem. But there is the second problem, the boot disk failure (see below << [B]) ... command line: initrd=disk.img harddisk c=2 h=256 s=63 BOOT_IMAGE=memdisk Disk is hard disk, 16128K CHS=2/256/63 <<<< [A] ... Loading boot sector... booting... SYSLINUX 2.04 welcome! boot: 1 [single dot]