EDD error RE: [syslinux] Re: SYSLINUX 2.12-pre7 released

[H. Peter Anvin]

Blaauw,Bernd B. wrote:
>>information a bit closer; it'd find that it's marked accordingly.
> 
> 
> UDMA2.SYS author now worked around it, it seems you do something with "DPTE" in isolinux.asm but not using it (probably for memdisk or direct floppy/harddisk emulation?).
> 
> also something about EDD v1.1 and v3.0 specifications and setting bits to 1.
> Anyway, the driver works now on:
> BIOS -> cdrom -> Isolinux -> A: -> MSDOS -> UDMA2.SYS -> COMMAND.COM -> command prompt.
> 
> I don't have the sourcecode of this latest work-around version available, so can't let you have a look at it.
> Any possibility for the 'write to bootsectorfile' in a 2.13 series SYSLINUX?
> 

No, but you can write a comboot/com32 module to do it if you wish.

> Bernd
> 
> here's a part of the mail:
> 
> "
> hard-disks (item C above), I believe the Isolinux bootloader may
> NOT be setting the DPTE pointer to all-ones if DPTE data in fact
> IS NOT present, i.e. for the CD-ROM!   In his first E-Mail, your
> friend says "examine the data more closely" which makes me think
> the Isolinux bootloader denotes a non-ATA unit ONLY through data
> available in "new" V3.0 EDD BIOS fields!!   He MUST ALSO set the
> DPTE pointer to all-ones for non-ATA units, or in my opinion the
> Isolinux bootloader is VIOLATING both the V1.1 and V3.0 EDD BIOS
> specification!   How else, for BOTH an old OR a new EDD BIOS, is
> one to know a particular BIOS "disk unit" is NOT REALLY A DISK??
> If your friend insists he has NOT violated the specs (as I think
> he HAS!), then there is only one answer:  Our drivers must FIRST
> check for a NEW V3.0 EDD BIOS (74 bytes of returned "parameters"
> not just 40), then check the NEW data fields for a non-ATA disk." 
> 

He's completely confused.  I'm not doing ANYTHING with this stuff, it's 
the system BIOS that's doing it, not ISOLINUX.

	-hpa