[syslinux] Isolinux bug: CD bootsector support broken

Michael_E_Brown at Dell.com Michael_E_Brown at Dell.com
Thu Feb 9 20:52:36 PST 2006

	Any idea on my original error?

	Thinking about it a bit, I realized I might have not been clear. The isolinux-debug.bin output I sent in the prior mail (http://syslinux.zytor.com/archives/2006-February/006529.html), is output from when isolinux is configured to boot the WINDOWS cd boot sector, not isolinux. :-)  Even though the debug output _looks_ like I may have configured isolinux to try to boot isolinux, I have, in fact, configured it for windows cd boot sector boot. Clear? I think my "random additional comment" may have made it sound like the debug output was from trying to boot isolinux from isolinux, but I can assure you that this was not the case.

	Doing absolutely nothing to the CD image except replacing isolinux.bin with 3.02 (and rerunning mkisofs, etc) will fix this. My isolinux.cfg is:
label winpe
  kernel lhpe32.bin

default winpe
prompt 1
timeout 100


-----Original Message-----
From: H. Peter Anvin [mailto:hpa at zytor.com]
Sent: Wednesday, February 08, 2006 11:23 AM
To: Brown, Michael E
Cc: gmurali at cs.uchicago.edu; syslinux at zytor.com
Subject: Re: [syslinux] Isolinux bug: CD bootsector support broken

Michael_E_Brown at Dell.com wrote:
> Random additional comment:
> 	I would have thought that you could use this feature to 
> chainload isolinux from isolinux, but after trying this, it doesn't
> work. The new version fails. (I thought it might save time to burn
> an image with 3.02 and have chainload menus for every intermediate
> version to check, rather than having to reburn my cdrw with every 
> new version.

Well, it would work, but only if you could get mkisofs to update the 
metadata written into the alternate isolinux.bin files.  In fact, if you 
could do that, you could also get it to use an alternate root directory.


More information about the Syslinux mailing list