[syslinux] problem booting msdos with memdisk

behrad at rayavaran.com behrad at rayavaran.com
Thu Sep 28 12:31:12 PDT 2006


I have the same problem. I can not boot a floppy disk. Once I did it but no longer I can do this. I think there is some problem in the new versions of PXELinux. 

-----Original Message-----
From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On Behalf Of Quinn Plattel
Sent: Thursday, September 28, 2006 7:04 PM
To: syslinux at zytor.com
Subject: Re: [syslinux] problem booting msdos with memdisk

Try using grub4dos.  I have had exactly the same problem as you on all IBM Thinkpad machines with syslinux's memdisk - Dell machines work fine though.  I reported this problem almost 2 years ago but no solution was found then.

Use grub4dos v 0.4.1 - it is the most stable at the moment.  Here is an example syslinux.cfg:

default grub.exe --config-file="map --mem dosfloppy.gz (fd0); map --hook; chainloader (fd0)+1; rootnoverify (fd0); boot"

Good luck,
Quinn

On 8/28/06, Uli Raich <Uli.Raich at cern.ch> wrote:
> Hi all,
> I try to boot an msdos system using pxelinux and memdisk on my PC 
> engines Wrap-2.c card and I have problems with it This is what I see:
> PXELINUX 3.11 Debian-2006-03-16  Copyright (C) 1994-2005 H. Peter A
> boot: msdos
> Loading memdisk....
> Loading images/msdos/msd622bd.dosim.........................
> Ready.
> dp83815: Setting full-duplex based on negotiated link capability.
> MEMDISK 3.11   Copyright 2001-2005 H. Peter Anvin
> e820: 0000000000000000 00000000000a0000 1
> e820: 00000000000f0000 0000000000010000 2
> e820: 00000000fff00000 0000000000100000 2
> e820: 0000000000100000 0000000007f00000 1 Ramdisk at 0x07d61000, 
> length 0x00168000 command line: initrd=images/msdos/msd622bd.dosim 
> BOOT_IMAGE=memdisk Disk is floppy 0, 1440 K, C/H/S = 80/2/18 Total 
> size needed = 1899 bytes, allocating 2K Old dos memory at 0x9fc00 (map 
> says 0xa0000), loading at 0x9f400
> 1588: 0xffff  15E801: 0x3c00 0x06d6
> INT 13 08: Failure, assuming this is the only drive
> old: int13 = f000ac5e  int15 = f000a60a
> new: int13 = 9f400008  int15 = 9f400290 Loading boot sector... 
> booting...
>
> from then on nothing happens.
> Can this be a BIOS problem (PC engines uses its own TiniBios) or what else may I try?
> Thanks Uli
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.





More information about the Syslinux mailing list