similar to: memdisk problem?

hi there. I'm trying to boot several OSes floppy images from a cdrom via memdisk. Actually, Linux and FreeBSD boots fine, but, while i'm using the same method, I couldn't get into booting netbsd nor openbsd. The boot process seems to hang up, in those two cases, when the second stage native bootloader try to load the kernel (i'm not absolutely sure about this). The native first

I had posted the problem described below about two weeks ago, and I would like to add some odd behaviour even on machines where the zip image is loaded correctly (without divide by zero). If I call DOS fdisk, when booted from the image, fdisks asks if it should enable the large disk support and the returns immediately to the command prompt. regards -- Bernhard Treutwein

I'm trying to switch from a standard floppy emulation rescue disk (PQ-Magic & Ghost) to a no emulation large floppy using isolinux & memdisk. I finally got the CD booting on two systems (see below) but on a third system I get a divide by zero message and/or other error from DOS, which is starting to boot correctly. It appears to happen during loading the drivers in config.sys. It is an

Hi Peter, I'm using isolinux and memdisk to create a multiboot rescue cd for personal use as described on Bart's page (www.nu2.nu). One boot item is to boot DOS 7.1 from Win98SE with a lot of other staff for emergencies. This DOS bootimage puts all necessary stuff into it's own ramdisk (XMSDSK). Some progs on the ramdisk needs access to floppy drive A: and unfortunately I've no

Hi... I'm Jaspreet. I've been having the memdisk memory overlapping problems since 2.04 Its always seen in the compressed images whereas the uncompressed images works just fine !!! It just stops at the error "Ran out of input data".. Even the memdisk 2.05 dint solve my problem !!! maybe there r still some bugs remaining. !! My motherboard is Intel 845GEBV2 and i've got

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

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

Hello, I seemed to have encountered a problem with memdisk that I have seen before when I was playing around with USB device booting at one time. Here's the scenario: Take fx a image of a PC DOS bootable diskette. Boot the image via memdisk. This should boot fine if you use the built-in motherboard ide controllers (ide0,ide1). Now install a PCI IDE controller and put one IDE disk on the

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

Hi, I'd just want to express my gratitude for the recent versions of pxelinux and memdisk. They allowed me not only to install Linux, but also to boot those darn rescue Floppys on my IBM ThinkPad X22, which comes without Floppy or CDDROM drive, but a built-in Ethernet card which supports PXE. I also had a look at other projects, like bpbatch, but none were so easy to use and functional as

Hi community, since more than one week I try now to boot my client via PXE. More informations about my equipment: Client: Board ASUS K8V-X SE Amibios with BIOS Revision 1501 (newest) Intel UNDI, PXE-2.0 (build 082) Server: Tyan Tomcat K7M Board with Eisfair 1.6.1 (www.eisfair.org) With exactly the same hardware unattended boots where working for more than one year perfectly without any

Hi guys, I'm trying boot a floppy basead netbootdisk solution ( http://www.netbootdisk.com/) using grub and memdisk. This is a Floppy 1.44 Mb with TCP/IP and Ethernet Drivers for DOS. This image doesn't has a command.com. This file is unzipped on boot. Using a floppy, the machine boots, but when I trying to use a image from floppy which memdisk, the boots hangs. The image can found at

I've been trying to use memdisk with grub2 to boot some iso images -( I've done this without any problem with pxe ) There is a memdisk.mod in /boot/grub/ and I've seen some material talking about this, but no example of a menu. After trying countless permutations - Right now I have : menuentry "Memtest-Plus 4.2" { echo `hello` insmod lvm

- mkdiskimage -d image.dsk 2 64 32 - load it in dosemu and make it bootable with sys - isolinux: label 999 kernel memdisk append initrd=image.dsk harddisk c=2 h=63 s=32 results: memdisk 2.11 -> boots memdisk > 2.11 (up to 3.07) -> hangs The following message is printed in the boot messages > 2.11: MEMDISK: image has a fractional end sector The complete error message

I have been using memdisk (version 3.82) with no problem. I use it to boot my x86 computer with a compressed image I created/modified from an original DOS floppy bootable diskette. The original size of the image is 2.44 MB. I tried memdisk (version 3.83) and the bootable image gets uncompressed, bu the computer locks up and the las two lines in my screen are: Loading Boot Sector... Booting...

For the boot floppy at http://superkeen.com/peacecorpsfiles/FUZOMA14.IMG using memdisk from syslinux version 3.72 boots correctly, but for memdisk versions newer than 3.72 (I tested 3.73, 3.75, 3.85, and 3.86) all hang at boot with the following message: Loading boot sector... booting FreeDOS kernel - SVN (build 2039 OEM:0xfd [compiled Oct 2 2009]) Kernel compatibility 6.22 - BORLANDC ... XMGR,

We are working on a prototype for an installation system, and it would be very useful if we could load two memdisk images, having one pretend to be normal A: drive, and another as B: drive. I have read through the docs as well as done some google searches, and haven't seen such a thing described. We have one person who has asm programming experience, and we were wondering if we could get

Hello everybody, I want to boot my HP x86 PCs with a Norton Ghost 12 boot disk image via PXE. I followed all the steps but I have still the same message and the booted computer hangs always. 0- I created the boot image. 1- A folder named tftpboot and tpftpboot\pxelinux.cfg created. 2- The pxelinux.0 copied in tftpboot folder. 3- memdisk copied in tftpboot folder. 4- the image file (norton.iso)

I know there's a module to check which syslinux bootloader was used, but is there also a module for detecting MEMDISK? Basicly I want to use the same isolinux.cfg for a CD which boots an ISO. Issue is that the inner ISO also uses same Isolinux (+ menu), which isn't very user-friendly. So: CD --> ISOLINUX (menu) --> MEMDISK CDROM.ISO --> ISOLINUX (menu) --> diskette

<..trying again after changing outgoing e-mail options to avoid bad headers...> I'm trying to use syslinux 3.08-pre11 on a Gateway E4000 with the (sample) config file below, and the ramdisk images fail to boot if selected as a menu option, but do boot if I press ESC and type the command line manually. The two options are for the same floppy image, but the first is compressed, the