similar to: syslinux / antique computers

MEMDISK included in the freshly released Syslinux v3.10 is unfortunately broken. v3.09 works properly. Scenario: Isolinux --> MEMDISK --> FDBOOT.IMG (FreeDOS 360KB diskette image). Then try to access drive B: , which normally is your first diskette drive with driveletter A:. However, in this case MEMDISK occupies A:, and real diskdrive becomes B: Bug: when accessing B:, you're asked

rename the VMlinuz*.* to file 'vmlinuz' (no quotes ofcourse). a bootfloppy leaves me enough diskspace, not 860KB. format as FAT12 (ofcourse), install Syslinux (I do this on Win2K with syslinux.exe A:, win9x: syslinux.com A:) my example: http://www.fdos.org/ripcord/beta9rc4/fdboot.img unfortunately no Linux involved. If I could only show a Knoppix bootfloppy (but it's part of a

Hallo, I try to boot the windows 98 bootdisk via memdisk. It doesn't work completely. Booting a freedos FD image works, booting the windows 98 image works too. But the windows 98 boot disk then should extract the file "ebd.cab" with the file "extract.com", and that step fails. Is that a syslinux problem or a windows problem? Viele Gruesse! Helmut

perhaps the boot-from-cdrom code in Smart Boot Manager? Bernd >>> No, since booting from CD-ROM requires that the El Torito part of the BIOS is activated, which it won't be if it didn't boot from CD-ROM in the first place. ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing:

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > 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.. > please read Syslinux and Memdisk

Hello all, I've been following this project with interest, and have had great fun implementing Isolinux within the FreeDOS cdrom distribution. Since I'm not that an expert at Linux, I would like to know how I can *succesfully* generate a bootable image from a partition. Situation is like this: (640MB RAM on system) 60GB IDE harddisk, primary partition 1 win98 500MB extended partition

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

I have an application/program which shows 'bios EDD error' when using Isolinux (with either loading an image directly through MEMDISK, or booting to A:), and not when using a bootdisk directly or booting a bootdisk directly which has SYSLINUX on it. configuration: bootable cdrom with Isolinux 2.11/2.12pre9 as bootloader. 1.44MB bootdisk with MSDOS.SYS/IO.SYS and the UDMA2 dos driver,

Hello all. I am pretty new to this list but I have looked through the archives and did not see any reference to this problem. I have an MS-DOS boot floppy image that I am trying to load using MEMDISK. The disk is simply a boot floppy made using XPSP2. I have tried it on 4 different machines, all Dells. PowerEdge 2650 Server, Latitude D610 Notebook, Optiplex GX280 Desktop and Optiplex GX520

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes

Just for the record, I want to let the list know that I succeeded in booting a modified Universal TCP/IP Network Bootdisk floppy from http://members.iinet.net.au/~bdriver/bootdisk/ I started with a Win98 Bootfloppy from http://www.tobs.uku.co.uk. Then I made a disk image from this, using dd.exe from cygwin. Then I converted this disk image from 1.44MB to 2.88MB with winimage. Then I copied

HPA, is it possible to add GZ support in syslinux itself? Some standalone software compresses very well, but is not compressed. Example is the Memtest86+ binary (90KB uncompressed --> 35KB gzip'd) and maybe Smart Boot Manager (gzip'd COM32 binary instead of normal COM32 binary?). I'm using both on a simple bootdisk, and all space savings are welcome. a workaround could ofcourse

I've recently returned to working on FreeDOS again after quite some time, and read about an unmerged MEMDISK branch that allows to boot DOS-based ISOs. This seemed quite usefull to me as it allows for faster modifications to my code/scripts/disklayout. The general idea was to install Syslinux 3.83 to harddisk, then add the modified Memdisk from that boot-land forum, as well as my ISO. In

Hello HPA, I think on harddisks, Syslinux is going to lose somehow from other bootloaders like LILO, Grub and others. However, SYSLINUX is still VERY usefull for removable media like diskettes, Zipdisks, USB Flash keys, etc.. I don't know if the fact that Syslinux is now installed using blockmapping is really breaking the usefullness for harddisks. You already mentioned system attribute

Does SYSLINUX have any idea which DOS driveletter would be assigned to the disk it is booting from? At www.veder.com someone is trying to build a USB flash drive. However, FreeDOS does not seem to boot correctly from it (bootsector trouble maybe, or kernel itself is confusing drives), thus we're thinking of using Syslinux + Memdisk + bootimage, but somehow we want to be able to also access the

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 ALL, I've got a diskless server working (under Gentoo), booting on it works. (a linux session start with no problem.) My Big problem, is to get Memdisk to boot with PXE. In fact memdisk is loaded, but it cannot find the img file. I've tried a lot of thing, but nothing works... tftp use : /diskless the config file for PXE in then in : /diskless/pxelinux.cfg/ the root for the

hm, nice algorythm thingie. I'm not a programmer, so here goes: currently: F1 helpfile.txt probably results in DISPLAY helpfile.txt perhaps extend this option: F1 arg1 arg2 arg3 argX if arg1 does not exist, abort (currently also done?) if arg1 ends in COM extension, execute it and pass the optional arg2/3/X parameters if arg1 ends in C32 extension, same thing. else DISPLAY arg1 // arg1

HPA, is it possible to add a parameter/argument to syslinux.com/syslinux.exe to specify a file? currently it's something like SYSLINUX A: I'd like the following also to be possible: SYSLINUX A: A:\SYSLINUX.BIN It still copies LDLINUX.BIN to A:, but writes the generated bootsector intended for drive A: to a 512byte user-specified file Perhaps to allow both at the same time even SYSLINUX

My question is the following: I need to "syslinux" a harddisk(partition-type is FAT16, size is about 100mb). I created a Dos-Bootdisk with WindowsXP and removed everything except command.com, io.sys and msdos.sys. Then I copied syslinux.com (and even ldlinux.sys) to the disk but nothing seems to help, I always get the "SYSLINUX: Cannot read ldlinux.sys"-error. Should I use