similar to: Problems with PXE Booting

hpa etal, Im trying to get PIRT running on an SBC which has no CD-ROM drive. (an 8 MB ISO which demo's RTAI - RealTime Application Interface, on linux patched with Adeos) (BTW, PIRT uses isolinux) anyway, Im trying to use pxelinux to chainload / memdisk / mboot it, Im having no success. Ive also tried booting memtest86, which I can boot on my laptop using grub, ie title memtest

- 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

syslinux-3.0.7 Cannot boot memdisk+harddisk image. 1) mkdiskimage -d image.dsk 10 64 32 (I get a 10485888 bytes file) 2) start dosemu+freedos with image.dsk loaded as d: and do sys d: then copy some files to d: 3) reboot dosemu using image.dsk as c: to verify it's bootable, and it is C:\>ver FreeCom version 0.82 pl 3 XMS_Swap [Mar 06 2004 10:49:37] C:\> 4) isolinux.cfg: label 999

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

Im trying to boot memtest86 via pxelinux, memdisk, I found this advice on http://forum.x86-secret.com/viewtopic.php?t=2906 folks are making the image match a floppy size by one of the following: dd if=memtest86+-1.xx.bin of=memtest.img bs=360k count=1 conv=sync or dd bs=360k count=1 conv=sync if=memtest86+-1.xx.bin|gzip > memtest.gz I did the former, it did suppress the warning/errors I saw

Hi, I stumbled on a rather odd problem. A brand new HP Compaq dx2200 computer didn't want to boot up pxelinux+memdisk image. The computer just gave "Disk I/O error" and stopped there. Workaround was rather simple... Just attach regular floppy drive to the motherboard and everything started working fine. I tried with older 2.05 (pxelinux+memdisk) and newer 3.31. Both produced

My system is hanging up when attempting to boot a bootable floppy disk image Does the following info tell any story as to what's happening? Thanks. LABEL dosdiskimage KERNEL memdisk APPEND keeppxe initrd=dos.img floppy Loading dos.img ............. Ready. MEMDISK 3.11 2005-09-02 e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 2 e820: 00000000000e0000

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

My system is hanging up when attempting to boot a floppy disk image. Does the following info tell any story as to what's happening? Loading ghost.imz ............. Ready. MEMDISK 3.11 2005-09-02 e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 2 e820: 00000000000e0000 0000000000020000 2 e820: 0000000000100000 0000000009ef0000 1 e820: 0000000009ff0000

Hi there, while my memdisk setup works perfectly well an an Intel system it fails like this on a Via-C3 based Mini-ITX system (copied manualy, I hope I did not make a mistake): --cut-- Failed to Free base memory, sorry... MEMDISK 2.08 (Debian, 2003-12-22) Copyright 2001-2003 H. Peter Anvin e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 1 e820: 00000000000f0000

memdisk fails to boot HD image, if the system does not have an HD. Has any seen this? Is there a solution? memdisk output: Disk is hard disk, 9216 K, C/H/S = 9/64/32 Total size needed = 2063 bytes, allocating 3K Old dos memory at 0x9dc00 (map says 0x9dc00), loading at 0x9d000 INT 13 08: Failure, assuming this is the only driveold: int13 = f000799a int15 = f000f859 new: int13 = 9d000008 int15

Sorry for makeing a new post, but I already erased my old mails. In the following I describe my Server-Situation (Sorry for my bad english) * I have a eisfair server http://www.eisfair.org with version 1.6.1 (newest) * I have a ISC-DHCPD 3 Server running * I have a TFTP Server running http://www.kernel.org/pub/software/network/tftp/ * I have Samba installed and a DNS Server is running My

Hi everybody. Hardware: Several computers with Asus P/I-P55t2P4S motherboard, CPU Pentium MMX and K6-2/3, 128 to 384 MB RAM, Award 4.51PG Bios, Hard disks from 8 GB to 123.5 GB Realtek 8139D based NICs with PXE Boot-Proms PXELINUX 2.06 / MEMDISK 2.06: - fails to boot Compaq PC-DOS 3.31 PXELINUX 2.08 - succeeds to boot Compaq PC-DOS 3.31 with 0, 1, 2 and 3 hdds installed in

I am trying to acheve pxe booting of a image of barts boot disk (www.nu2.nu). I have managed to get LTSP booting via pxelinux, so I know my dhcp/tftp servers are ok. However when I try to boot memdisk with either a stock suselinux boot image file (taken from SuSE 9.1) or my dos disk (created by dd if=/dev/fd0 of=/imagefile) I get output like MEMDISK 2.08 command line : BOOT_IMAGE=memdisk

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

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

I am trying to PXE boot an ISO image using ISOLINUX. I am starting small just trying to get anything working but seem to be having problems. I followed the instructions on the isolinux page (http://syslinux.zytor.com/iso.php) but still cannot get it to work. I can get the ISO image to try to load but then it stops at the booting message. Any help would be greatly appreciated. Here is

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

Hi group, currently I try do make my own PXE bootscreen. There is one thing i dont like. When I use vesamenu.c32 there is always a table on the screen (I mean the border lines are visible) Is there any command i have to add to the default file that this border lines are unvisible ? Thanks in advance

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line: