>Received: from belous by muhost.munic.msk.su id aa26121; 18 Sep 2002 19:25 MSD
To: opendos AT delorie DOT com
X-Comment-To: shadow AT krypton DOT rain DOT com
References: <20020918 DOT 024024 DOT 6U9 DOT rnr DOT w165w AT krypton DOT rain DOT com>
Message-Id: <2.7.9.ONXH.H2N37O@belous.munic.msk.su>
From: "Arkady V.Belousov" <ark AT belous DOT munic DOT msk DOT su>
Date: Wed, 18 Sep 2002 19:04:36 +0400 (MSD)
Organization: Locus
X-Mailer: dMail [Demos Mail for DOS v2.7.9]
Subject: Re: HIMEM.SYS and DOS 8
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
X-MIME-Autoconverted: from 8bit to quoted-printable by postbox.mos.ru id g8IFQdC29723
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g8IFQql02977
Reply-To: opendos AT delorie DOT com

X-Comment-To: shadow AT krypton DOT rain DOT com

Hi!

18-σΕΞ-2002 02:40 shadow AT krypton DOT rain DOT com (shadow AT krypton DOT rain DOT com) wrote to
opendos AT delorie DOT com:

>> when you try to access disk above 8Gb under noncompliant systems you
>> simply destroy data.
src> That sounds like a BIOS issue,

     This is application issue. Unlike old 512Mb limit, which may and should
solved on the BIOS level, 8Gb limit requires new API and requires adoption
this API in all "low level" programs (at least, OS).

src> not anything to do with FAT-32.

     Yes. FAT32 is an another issue.

src> The 8 gig limit is found in the BIOS on a lot of older systems.

     8Gb limit "is found" in _all_ BIOSes. Again: it may be "fixed" only
through new (BIOS) API (to be precise: see INT 13/41, EDD specification).