similar to: Planning a 2.08 release

I am using PXELINUX, ISOLINUX, and memdisk in my project (http://unattended.sourceforge.net/). When memdisk gained support for compressed images, I started using it because it is cool. I used gzip to compress floppy.img to create floppy.imz, and all was good. But now my users are complaining that they cannot use WinImage (a Windows floppy image editing tool) to edit my floppy.imz files. I have

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

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 am planning to release SYSLINUX 2.08 in the next day or so; basically 2.08-pre9 without any further changes. So, I would appreciate any and all testers for this... -hpa

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

>+ booting floppy34.fs image from the CD works correctly (no ISOLinux, in >built BIOS emulates the floppy) Hi, have you tried the following (Isolinux direct emulation): KERNEL 34FS.IMG should function the same as if direct 1.44MB eltorito emulation was used. but using MEMDISK it fails? KERNEL MEMDISK APPEND INITRD=34FS.IMG that's all I can come up with .

This release includes Murali's menu positioning patch; it is otherwise identical to 2.09-pre13. I will release this as 2.09 on Sunday unless I hear objections. Note that I've effectively been out of the loop, moving houses, for almost a month, so if there is something I'm forgetting please tell me... -hpa

I'm trying to use this universal DOS TCP/IP boot disk available here: http://members.iinet.net.au/~bdriver/bootdisk/ It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image

Hello, Can I load setupldr.bin directly using isolinux without original CD boot sector? Thanks, Theewara

Hi there, I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... what is the problem can anybody tell me.. Regards, Yogesh

Dear Syslinux bootloader list, I'm running into a few issues concerning Syslinux modules here, hoping you can answer one or more of the following questions: * Where's "ifmemdsk.c32" ? 4.05, 4.06pre1 and latest 4.10pre seem to lack it. Only the "ifmemdsk.c" file, which is likely sourcecode. Not seeing any "ifmemdsk.cbt" legacy comboot module. * Do COM32

Good day to all, Gert Hulselmans requested a feature for MDISKCHK.COM that would function roughly like GETARGS.COM[1] by Murali Krishnan Ganapathy: DOS SET command output for MEMDISK kernel arguments passed by previous boot-loaders. He also needed to support the case for MEMDISK-in-a-MEMDISK type situations, where all MEMDISK kernel arguments could be gathered together and output as a list

Has anyone been able to boot a bartpe image successfully using pxelinux or does anyone know if this is impossible? For those who don't know, bartpe is a legitimate way to make a trimmed down installation of Windows XP or Server 2003 using your installation media. For more information on bartpe see: http://www.nu2.nu/pebuilder Basically the pebuilder gathers the minimum files needed to

This version adds Murali's "onerror" configuration directive. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Memdisk 2.08 cannot boot an XP boot floppy image (XP appears to use WinME boot files for its bootable floppy). For example: http://members.iinet.net.au/~bdriver/bootdisk/download.htm This disk will not boot with Memdisk (Memdisk starts to load the image and then hangs). I'm using Bart's tools to build a boot CD: http://www.nu2.nu/corpmodboot/ Which uses Isolinux and Memdisk.

Comments inline > -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Posted At: Thursday, November 14, 2002 1:40 AM > Posted To: Syslinux > Conversation: [syslinux] MSDOS not working: problem Solved > Subject: Re: [syslinux] MSDOS not working: problem Solved > > > G. Murali Krishnan wrote: > > > > In short: Is it possible to

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

Is there a method to reboot a memdisk (floppy) image? I'm working on a DOS-based installation floppy that needs to repartition the hard disk prior to proceeding. DOS will only recognize the updated partition table after a reboot, but I'd like to be able to save information to the currently loaded memdisk floppy disk and simply reboot the image. Possible? I haven't had any luck with

Is it possible to chain isolinux and memdisk over pxelinux? If it's possible, I'd like to boot a CD Image over the network. I've been using pxelinux to boot ltsp for years, and recently upgraded to take advantage of memdisk for booting a DOS hd-image. Ideally I'd be able to boot a CD-Image. Thoughts? -- <:3)~ Michael T. Garrison Stuber

Memdisk 2.08 does not appear to be able to boot an XP DOS image (it starts to boot and then hangs). XP DOS appears to be borrowed from WinME (v4.90.3000). I was trying to make a multiple boot CD with Bart's method: http://www.nu2.nu/bootcd/#multimemdisk but substituting Brads TCP boot disk instead of Barts: http://members.iinet.net.au/~bdriver/bootdisk/index.htm Brad uses XPs DOS as it