[syslinux] Buggy bios, boot of dos image hangs with syslinux, but not with isolinux

[Zipf Christian]

--------------------------------------------------------------------------------
BÖWE SYSTEC Mailroom Communication GmbH
Sitz der Gesellschaft: D-86159 Augsburg
Amtsgericht Augsburg HRB 17386
Geschäftsführer: Michael Meyer
---------------------------------------------------------------------------------
Diese E-Mail und die darin enthaltenen Informationen ist/sind ausschließlich für den/die oben bezeichneten Adressaten bestimmt. Sie können vertraulichen Charakter haben und/oder gesetzlich geschützt sein. Unberechtigter Gebrauch, Vervielfältigung oder Offenlegung sind untersagt und widerrechtlich. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, benachrichtigen Sie den Absender bitte per E-Mail, Telefon oder Telefax.

This communication and the information it contains is only intended for the addressee(s) named above and may be confidential, legally privileged and protected by law. Unauthorised use, copying or disclosure of any of it is restrained and may be unlawful. If you have received this communication in error, please contact us immediately by email, telephone or facsimile. 
-----Ursprüngliche Nachricht-----
Von: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] Im Auftrag von H. Peter Anvin
Gesendet: Dienstag, 5. August 2008 17:35
An: For discussion of SYSLINUX and tftp-hpa
Betreff: Re: [syslinux] Buggy bios, boot of dos image hangs with syslinux, but not with isolinux

Zipf Christian wrote:
> Here is the output:
> Ramdisk at 0xdbef0000, length 0x002d0000
> Disk is floppy 0, 2880K C/H/S = 80/2/36, EDD off
> Using raw access to high memory
> Total size needed = 2454 bytes, allocating 3K
> Old dos memory at 0x9d800 (map says 0x9d800), loading at 0x9cc00
> 1588: 0xffff  15E801: 0x3c00 0x7cbe
> INT13 08: Success, count = 0, BPT = 0000:0000
> old: int13 = e320aaef int15 = e3200fab
> new: int13 = 9cc0000a int15 = 9cc0037e
> Loading boot sector... booting...
> Starting MS-DOS
> 
> After that the computer completely freezes, and has to be powered down.
> 
> Does anybody know of a way around this?

Could you try 3.71?  This looks like it may be one of the machines which 
is helped by the new code.

	-hpa

_______________________________________________

I tried Version 3.71, 3.62, 3.55. Unfortunately it is the same behavior on all of them. But it is only memdisk that is affected by this. If I boot a mini linux distro like DSL or SLAX this works just fine from the usb stick. But than again the memdisk code works if booted from a cd with isolinux. Mighty strange.

Christian