similar to: memdisk - reboot loaded image

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

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

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

Hi I am using PXELinux to boot BartPE and some other application and it works fine. There are some other Boot application which I am using 3COM MBAUTIL PXE.mnu and floppy images. I have problem chaining from pxelinux.0 to 3com pxe.0 (pxe.mnu). Consider: BIOS->(DHCP-TFTP)->pxelinux.0 works fine. BIOS->(DHCP-TFTP)->3COM pxe.mnu works fine, the menu appears and I can choose a floppy

On Thu, Feb 17, 2005 at 16:09:50 -0800, Mikey Sklar wrote > > I use 8MB DOS images with pxelinux to load firmware. Which platform > would you like them for (I have many). I just saw your post and I would definitely be interested in an 8 MB DOS images to work with pxelinux. I have tried the method described in http://people.cs.uchicago.edu/~gmurali/gui/downloads.html but I keep getting

Is it possible to have a isolinux based boot CD, where one of the options is to boot off the network. This would mean, 1. The kernel that one boots into is on the network and not on the CD. So easy to make changes. 2. One does not need a 'PXE enabled' network card. - Murali

Since lot of people want this thing, I will try to take a stab at it. For now, I will hard code the menu in the code, and then somebody else can remove that restriction. May be we can add some kind of keyword to the config file which syslinux ignores and the comboot menu does something with it. I have one question about comboot: If I write a DOS program using C (compiled using watcom -3 -mt -osx

HPA, I believe that support to boot windows CD bootsectors was broken in 3.05. I have tested 2.13, 3.00, 3.02, 3.05, 3.06, 3.08, 3.11, and 3.20pre6. All versions >= 3.05 are broken. All versions <= 3.02 work fine with the same config. The error message I get is: ================================================================ IOSLINUX 3.20 3.20-pre6 Copyright (C) 1994-2005 H. Peter Anvin

SYSLINUX is certainly useful. I currently start Debian from their standard boot floppy, which uses SYSLINUX. I found it very easy to edit syslinux.cfg for ide-scsi setup. Surely the future lies with bootable CDs and floppy images specifically designed for them. Maybe there should be a combined SYSLINUX / ISOLINUX package which allows you to specify Floppy Emulation or not. But if you invent a

I have released SYSLINUX 2.10-pre2. I *really* would like testing reports for this one, especially ISOLINUX, since I've included Knut Petersen's fix for Award BIOSes... Changes in 2.10: * MEMDISK: Handle images compressed with zip as well as with gzip. Some Windows-based image tools apparently generate these kinds of images by default. Patch by Patrick

Hello all, I plan to make an (emergency) multi OS bootable CD which contain: - Win98 boot floppy (create from Win 98 control panel, add remove program) - WinME boot floppy (create from Win 98 control panel, add remove program) - Linux boot disk - Win NT boot disk - Win 2000 recovery console - Win XP recovery console - Winternal Administrative Pak (ERD Commander etc) I am new to Linux and feel

Can someone address the boot once option. Is it to hard for syslinux to write a flag file to file system or the blank space after the mbr? .conf bootonce Lable /boot/flagfile or .conf bootonce Lable1 /boot/flagfileLable1 bootonce Lable2 /boot/flagFileLable2 bootonce Lable2 /boot/flagFileLable2 skip the default option if the flag file is 0 size. Write something to the

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'd like to add a user-friendly menuing system to pxelinux replacing/enhancing the default on the pxelinux.cfg/default Where can I find instructions on how to get started? Regards, Conrad Lawes Sr. Technical Analyst Argon Technology

Does the COMBOOT stuff with 2.04 work correctly with function calls? or does one need to write it as one huge function? If memory serves me correctly, there was some problem if hello.c was modified to include additional functions, in an earlier version. - Murali

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a project that uses syslinux to load the kernels from the CD to create disk and/or partition images. The process works great, but as I have been building newer kernel images with new disk and nic drivers, I have had users run into problems. Example: one users machine would fail at hotplug detection, creating a kernel with this feature off

But the win wks on the other subnet is configured to use my SAMBASERVER as its WINS SERVER, and it is configured using the IP Adress of the SAMBASERVER and not the name. Shouldn't this do the trick? win wks is on a wireless subnet and hence runs at 11 MBPS, while the SAMBASERVER is on a wired subnet. I read somewhere that windows does some kind of "optimization" with slow networks.

Hi all, I have released SYSLINUX 2.09; it is the same as 2.09-pre15 except for the version number. Changes in 2.09: * SYSLINUX: Remove residual setuid crap from syslinux-nomtools. * Handle video pages correctly when using the API functions. * Handle compiling on an x86-64 platform correctly. * Menu system from Murali Krishnan Ganapathy; see the

I guess this really isnt the right place to be posting this it's probably the best place for me to find the answer. I would like to know if any of you are doing windows 2000/2003 installs over PXE and if so how you had it setup. I've done some searching on google and mostly found info about somthing called RIS or RAS or whatever.... it required a windows box and thats not a option.. I