Blaauw,Bernd B.
2004-Dec-10 04:24 UTC
EDD error RE: [syslinux] Re: SYSLINUX 2.12-pre7 released
>No, but you can write a comboot/com32 module to do it if you wish.I meant for syslinux.exe/com (the installer). that BIOS issue is now handled in the driver the author wrote. Unfortunately I can't find another cdrom which boots but lets me access A: to really demonstrate it's the BIOS which is doing this. Every non-emulation cdrom either uses isolinux (even ReactOS bootloader) or does not allow booting to diskette. thanks for the feedback anyway, and good luck releasing 2.12. Bernd ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing: http://www.fontys.nl/disclaimer The above disclaimer applies to this e-mail message. ----------------------------------------------------------------
H. Peter Anvin
2004-Dec-10 04:40 UTC
EDD error RE: [syslinux] Re: SYSLINUX 2.12-pre7 released
Blaauw,Bernd B. wrote:>>No, but you can write a comboot/com32 module to do it if you wish. > > I meant for syslinux.exe/com (the installer). >Oh, right... I forgot all about that. On that subject, how would you expect this to work when the bootsector is tied to a particular location of ldlinux.sys? (I'm not being negative, I am just trying to understand the requirement(s).)> that BIOS issue is now handled in the driver the author wrote. Unfortunately I can't find another cdrom which boots but lets me access A: to really demonstrate it's the BIOS which is doing this. > Every non-emulation cdrom either uses isolinux (even ReactOS bootloader) or does not allow booting to diskette. > > thanks for the feedback anyway, and good luck releasing 2.12.Thanks. -hpa