X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f Date: Thu, 24 Feb 2005 21:51:43 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp AT delorie DOT com Message-ID: <01c51aaa$Blat.v2.4$69a969c0@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 X-Mailer: emacs 22.0.50 (via feedmail 8 I) and Blat ver 2.4 In-reply-to: <14.3fb9cae4.2f4ed770@aol.com> (Sterten@aol.com) Subject: Re: files > 4GB There is always a solution References: <14 DOT 3fb9cae4 DOT 2f4ed770 AT aol DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: Sterten AT aol DOT com > Date: Thu, 24 Feb 2005 02:08:32 EST > > >From DOS-programming, I remember there were some interrupts with parameters. > Isn't it similar with NTFS ? > Shouldn't it be possible to just change some parameters to handle big files > correctly ? Why is it so difficult ? Because there's no way of calling the NTFS file I/O routines from a DOS program. Well, not a documented and well-known way, at least. > Well, with the new 64-bit processors it's quite natural to address the bytes > in a file >4GB. Will we be able to use 64-bit variables with gcc/djgpp > or will this never be supported ? DJGPP already supports 64-bit variables: there's the `long long' data type which is 64-bit wide. The problem is to use the 64-bit file I/O interface, which is something very different, as so many people tried to explain in this thread, from so many different angles.