From: Martin Stromberg <Martin DOT Stromberg AT lu DOT erisoft DOT se>
Message-Id: <199908050948.LAA28512@propus.lu.erisoft.se>
Subject: FAT32 support
To: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
Date: Thu, 5 Aug 1999 11:48:45 +0200 (MET DST)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

According to <http://support.microsoft.com/support/kb/articles/q193/6/56.asp>:
"On computers using the FAT32 file system, the maximum file size is 4
GB minus 2 bytes".

Hence making llseek() return a long long and treating the return value
from lseek() (which has the return value from INT 21 call in dx:ax
IIRC) as unsigned, with special handling the return value 0xffffffff
to map it to -1, would resolve the llseek() problem.

Actually calling "lseek(fd, -3, SEEK_SET); write(fd, "?", 1)" might
produce a nearly 2GB file. I haven't tested that yet.


Right,

							MartinS