similar to: No subject

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

Hi, I looked at the web http://clic.mandrakesoft.com/documentation/pxe/ch06.html, and create a floppy boot image by : dd if=/dev/fd0 of=boot.img. I copied the boot.img to /tftpboot, and my /tftpboot/pxelinux.cfg/default is : default freedos display boot.msg label freedos KERNEL memdisk APPEND initrd=/boot.img When I boot up my client, it shows : could not find kernel image: memdisk What

Hello syslinuxers I'm stuck with a scientific problem which gives me headaches: I have a laptop (Gateway MX3410) which has a SD memory card reader. Recently an interesting thought crossed my mind: why don't I setup a 2GB SD card as a harddrive and put some rescue tools on it. So I dug on the net and I came across the idea of using memdisk to boot floppy images without the need of a

Helle, I'm facing a strange issue with memdisk The context : syslinux 3.75 gpxelinux.0 the gpxe stript called from a menu executed through menu.c32 : #!gpxe kernel /modules/memdisk initrd=/freedos initrd /freedos The output before the freeze : /boot.gpxe. ok /modules/memdisk. ok /freedos...... ok MEMDISK 3.75 3.75 Copyright 2001-2009 H. Peter Anvin et al e820: 0000000000000000

I'm trying to trace why launchers created by wine due to a program installation are not appearing in the menus on my system. The launchers appear to have the correct contents, but for some reason gnome-panel is not adding them to my menus. Does anyone know how to run the relavent gnome tools with options to see what's happening when gnome reads these launchers. Keep in mind that there

LDLINUX.SYS uses a working directory. The documentation seems to improve if that fact is made explicit. So the working directory is added to the documentation (with a bit of vagueness and possibly not entirely correct, to keep it readable). Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- This is a result of today's discussion of a previous patch ("Describe the --directory

Trying to be not long, on x86 I have 3 floppies images boot, root-1, root-2 Booting from boot image with no problem, I try reading root-1 and root-2 image in raw format. Reading root-1 and root-2 is made from boot init script, using klibc-1.5.9 or klibc-1.5.10 with debian insmod patch, and a vanilia linux-2.6.24.7 root-1 and 2 images are smaller than 1440 kB and are made the same way with cd

> On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao > Miller, Kenneth Davis, wrote: > > [...] > > Thank you all for your responses. You helped me solve my problem. For > anyone else that runs into similar trouble and finds this thread, here > follow summaries of what I've learned. > > To recap, our PXE server holds Dell BIOS updates in

It is now possible to build a bootable floppy image which contains HDT, with my patch applied to Erwans HDT branch: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=16b37fe2266c920087f88cdec94243b71218d871 Unpack the Syslinux archive and build whole Syslinux first, then cd to ./com32/hdt/ and make hdt.img $ make $ cd ./com32/hdt/ $ make hdt.img Now you have a 2.88 MB floppy image which

I downloaded the 'seatools for DOS' diskette creator on seagate website. it's a windows program that creates the diskette; so a floppy disk must be present in the drive. running the program is ok, but creating the diskette fails, it says "the current diskette format not valid". while the diskette is blank, vfat, mounted and linked to a: in wine; so everything seems to be ok.

On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao Miller, Kenneth Davis, wrote: > [...] Thank you all for your responses. You helped me solve my problem. For anyone else that runs into similar trouble and finds this thread, here follow summaries of what I've learned. To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy images booted via MEMDISK.

Is there any chance at someone looking at the gateway software between the forum<-->mailing list and seeing if it is possible to have it set the In-Reply-To header when sending a forum post to the mailing list in response to an email? Would make it much easier on those of us with mail clients that do threading based on this header. Btw, what's the software being used? mail2forum? --

Hi, I'm looking at adding support to vagrant-libvirt to add some additional XML to the network definitions it creates following https://libvirt.org/formatnetwork.html#general-metadata assuming the metadata element is to be treated the same as what is listed for domains https://libvirt.org/formatdomain.html#general-metadata (app metadata isn't explained What I was wondering is if there

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

Hi, I did found the problem, a combination of 2 factor. 1- I taught that I did install the latest syslinux, but in fact it was the 3.36 version. 2- Thank to kevin Connelly, he point me to a problem he got with mkdosfs command. The default FAT16 do not work, but the FAT12 do. By adding -F12 to the mkdosfs command fix the problem. The default F16 do seem to work for <8M floppy image. Thank you

Sorry for the delay, I should not send email on an holiday week-end. I'll try to answer all the questions by explaining what does work for me right now, and what I'd like to do. I have a script to create the a USB stick or an ISO image. The boot media contains many DOS images, and I use versamenu to select one of them. If my DOS image is smaller than 8megs, everything is working fine as

Hi I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy disk image 8440kB size. I've put FreeDOS kernel and bootsector into the floppy. Boot process goes fine with this command: isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy The problems begin when I try to run FreeDOS memory manager emm386 from the floppy image. my config.sys: ...

[Drive A] "Path" = "/mnt/floppy" "Type" = "floppy" "Label" = "Floppy" "Serial" = "87654321" "Device" = "/dev/fd0" I'm not sure whether /mnt/floppy should be mounted or not when trying to do this. I tried it both ways and got the same error message from rdisk.exe: "Repair Disk Utlity is

2018-06-26 2:10 GMT+08:00 H. Peter Anvin via Syslinux <syslinux at zytor.com>: > On 06/18/18 13:06, R S via Syslinux wrote: >> The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. >> >> If you are interested I could provide a 5MB FDD image template based on >> FreeDOS 2041 kernel (the latest available at that time in 2014) where you >>

Haven't yet had a need for 10MB FDD images. The biggest I had to create was 5MB (5760kb). At that time I had to use WinImage to create the FDD image and it took me a while to figure out the correct settings. My notes state: "I'm getting 'missing FAT' errors in WinImage, and 7-zip complains about 'unexpected end'. The fix is to increasing the FDD Heads from 2 to 4 and