similar to: DOS Drive B: Hung

>that image under B: or X: or whatever. This will allow us to cross the >size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect >memdisk to mount it, just that set things up so that DOS mounts it there. I'm using a 5MB image which emulates floppydisk. label test kernel data/memdisk append initrd=data2/test.img c=80 h=8 s=18 floppy problems are

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

Thanks very much for syslinux and pxelinux,they bring me many conveniences.I have problem in some computers.My english is very poor,so i submit in chinese and poor english.First I say sorry! ????pxelinux???sis900??????????? ????????default???????menu.c32??vesamenu.c32????? ???default???????DEFAULT memdisk c=638 h=2 s=18 floppy append initrd=netboot.zip???????????????????????? ???3com?boot image

Dear friends: I decided to go out and buy the latest issue of Linux Format with the FreeBSD 6 CD. I am very glad I did. FreeBSD is tough to install, but after spending several hours I finally succeeded in doing a perfect installation. ONE BIG PROBLEM: When I removed the CD and rebooted, I got into my Windows XP (I have two separate disks, one for Windows, one of FreeBSD). There was no way to get

hi: i try to make some images for pxelinux+memdisk. the version i try is 2.0.6 and 2.0.7pre5 for 2.88M floppy image, first i make a 1.44M boot floopy, then use "winimage" to load the disk and transfer it to 2.88M format, then save the image. it seems a easy way to make a 2.88M boot image. for harddisk image, i use vmware to build a virtual machine with 20M harddisk, make it boot

When trying to boot a 2.88M syslinux 3.07 image from the boot area of a CD on an MSI Hermes 651, it says "SYSLINUX 3.07 2005-01-12 ", then hangs forever. On any other machine I've tried, the same CD displays my boot.msg after this message, and then boots the kernels listed in the configs. Any idea what's causing this, and how to fix/work around it? LLaP bero

>From the current pathbased branch, linux/syslinux.c, line 421, open() yields an error on a FAT floppy image, 2.88M standard size. At first, this was a floppy that did have a previous version of SYSLINUX installed. I saved that floppy image and tried deleting ldlinux.sys with the same results. I'm still trying to drill away and find more about its status and understand what is

HI list! We regularly experience kernel Ooops on our alpha SX164 with ext3 on md on ide controller: No modules loaded, lsmod empty, self compiled kernel ksymoops 2.4.5 on alpha 2.4.25. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.25/ (default) -m /boot/System.map-2.4.25 (default) Warning: You did not tell me where