similar to: SYSLINUX 2.08 released

Hi,, I wud just like to inform that the previous issue of memdisk not booting compressed images still persists !! The release 2.05 that was supposed to fix this issue dint yet solve the problem !! Please, let me know if more info on the problem is required !! Bye, Jassi >From: syslinux-request at zytor.com >Reply-To: syslinux at zytor.com >To: syslinux at zytor.com >Subject:

Goodness, how many prereleases has there been in the last week... have lost count... Anyway, I have implemented the already-promised chainbooting API, and have included a sample program to chainboot floppies (it works for harddisks too, but only for the MBR.) As a bonus, in the process I actually discovered that booting .bs/.bss images under SYSLINUX was actually broken... that has been

Hello everyone, I have just released SYSLINUX 3.70, which is the first version which includes gPXE for support of non-TFTP network scripts, as well as a large number of other enhancments. gPXE support is still somewhat experimental - in particular it still doesn't support chaining other NBPs. Very special thanks to: - rPath, Inc, my employer, for the uncountable hours I've spent

I have released SYSLINUX 2.04, mostly to address the 2.03 MEMDISK bug. At the same time I'm getting the PXELINUX blksize and SYSLINUX installer changes out there, which hopefully is a good thing. New release mostly to address the MEMDISK corruption issue. Changes in 2.04: * ALL: Reclaim even more low memory by observing that comboot_seg == real_mode_seg is perfectly fine,

As far as I know the only thing close to that, is to boot DOS from a floppy image (stored on the CD). The floppy image will contain the CD drivers and hence you can use DOS to access the contents of the CD. The floppy image is usually stored in the "boot sector" of the CD, or if you are using utilities like ISOLINUX, then they can be stored on the CD, and ISOLINUX/memdisk can boot

Greetings, I have released SYSLINUX 2.05. It is almost identical to 2.05-pre4. I'm about to leave for a trip, so if there are any issues please let me know, but don't expect a response any time soon. -hpa 2.05 is mostly a bug fix/maintenance release. Changes in 2.05: * PXELINUX: Add a default query based on the hardware address of the boot device. This is in lower

Hi all, I have released SYSLINUX 2.11. It's basically -pre3 with a few last-minute fixes. 2.11: Bug fix release. Changes in 2.11: * ALL: Add an API call to get the configuration file name. * SYSLINUX: Fix bug in 2.10 that prevented it from working correctly for a lot of people. * SYSLINUX: In the installer, make mtools a bit less fussy. * Make

Working on fixing lower-priority bugs that I didn't want to risk destabilizing the 2.07 release for: Changes in 2.08: * Add "timeoutcmd" to allow timeout to have a different action than just pressing Enter. * Fix bugs in the COMBOOT/COM32 command-line parsing. APPEND now works with COMBOOT/COM32 images.

I just found a rather embarrassing bug in PXELINUX -- and what's worse -- I wrote an email about it and killed it off accidentally :-/ It appears PXELINUX doesn't free its internal socket buffers (it has 32 of them) when it gets an error reply from the server, including "file not found." This means it will eventually run out of sockets and "go deaf." This

It seems that quite a bit of stuff built up very quickly after the 2.07 release: Changes from 2.07 to 2.08-pre6: * Add new configuration command "ontimeout" to allow timeout to have a different action than just pressing Enter. * Add new configuration command "onerror" to allow a custom command to be executed in case the kernel image is

Hi... I'm Jaspreet. I've been having the memdisk memory overlapping problems since 2.04 Its always seen in the compressed images whereas the uncompressed images works just fine !!! It just stops at the error "Ran out of input data".. Even the memdisk 2.05 dint solve my problem !!! maybe there r still some bugs remaining. !! My motherboard is Intel 845GEBV2 and i've got

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.

I have released SYSLINUX 2.06; it's basically identical to 2.06-pre4. I'm doing this now because the bug fixes are so major and because I am not sure I'll be around next week. -hpa 2.06 is a bug fix release. Changes in 2.06: * ALL: Fix problem that would occationally cause a boot failure, depending on the length of the kernel. * ISOLINUX: Fix problem

HAS_LOCALBOOT is set unconditionally in config.inc. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/core/comboot.inc b/core/comboot.inc index 59db7ec..d6f670c 100644 --- a/core/comboot.inc +++ b/core/comboot.inc @@ -723,13 +723,9 @@ comapi_idle: ; ; INT 22h AX=0014h Local boot ; -%if HAS_LOCALBOOT comapi_localboot: mov ax,P_DX jmp local_boot -%else

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

Program your locked ADSI phone not by unlocking it but by using the feature slot FDN download descriptors of ADSI SEC security code telco provider lock number key from database list. ch33s3 First reset phone. Set clock to Jan 1 12:00AM (options-2?). exit to main screen. press options, (mute/flash/speaker/?) until you see firmware version. press # to reset. google more info, bam ch33s3d ;

Hi All, I sent the patch to allow blktap to be able to booted as system bolume for PV-on-HVM. However, there was a problem that hdN and xvdN were not able to be specified at the same time. I made the patch to correct it as follows. - Whether hdN is defined first is checked. - If hdN is defined, xvdN is not replaced with hdN. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>

Do=F0ru se=E7imi yap=FDn Bazen, bir i=FEe giri=FEmeye ve farkl=FD bir =FEeyler yapmaya karar vermek = =E7ok kolay olmayabilir. Ortalama k=FC=E7=FCk =F6l=E7ekli bir i=FEletme kurma maliyetinin =E7ok paha= l=FD oldu=F0unu ve bu i=FEletmelerin bir=E7o=F0unun ilk y=FDllar=FDnda kapa= nmak zorunda kald=FD=F0=FDn=FD biliyor muydunuz? Herbalite ile kendi i=FEin= izi y=FCr=FCtme zorlu=F0unun =F6n=FCne

Do=F0ru se=E7imi yap=FDn Bazen, bir i=FEe giri=FEmeye ve farkl=FD bir =FEeyler yapmaya karar vermek = =E7ok kolay olmayabilir. Ortalama k=FC=E7=FCk =F6l=E7ekli bir i=FEletme kurma maliyetinin =E7ok paha= l=FD oldu=F0unu ve bu i=FEletmelerin bir=E7o=F0unun ilk y=FDllar=FDnda kapa= nmak zorunda kald=FD=F0=FDn=FD biliyor muydunuz? Herbalite ile kendi i=FEin= izi y=FCr=FCtme zorlu=F0unun =F6n=FCne

Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==