From: Martin Stromberg Message-Id: <200012101521.QAA13985@lws256.lu.erisoft.se> Subject: Re: Why are we using offset_t and not off64_t? To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii) Date: Sun, 10 Dec 2000 16:21:37 +0100 (MET) Cc: djgpp-workers AT delorie DOT com (DJGPP-WORKERS) In-Reply-To: from "Eli Zaretskii" at Dec 10, 2000 05:10:00 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Eli said: > On Sun, 10 Dec 2000, Martin Stromberg wrote: > > Hmm, perhaps somebody could try creating file bigger than 2^32 on a > > NTFS file system. > > Who says NTFS supports files larger than 2^32 natively? Does it? One source (at least): Microsoft WINDOWS 2000 Professional Resource Kit, ISBN 1-57231-808-2. Page 721, Table 17.5 NTFS Size Limits ------------------------------------------------------------------ Description Limit ------------------------------------------------------------------ Maximum file size 2^64 - 1 KB (Theoretical) 2^44 - 64 KB (Implementation) Maximum volume size 2^64 clusters (Theoretical) 2^32 clusters (Implementation) Files per volume 2^32 - 1 ------------------------------------------------------------------ > > I guess you can't through DOZE/DJGPP. > > Most definitelyly. The DOS calls simply don't have enough bits in the > registers to pass larger offsets. Yeah, But what happens if we write 2^32 + some bytes? Perhaps it'll just grow over the limit or perhaps not... Right, MartinS