Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <013c01c1ea22$4d0056a0$cd8a9dc0@uk.aonix.com> From: "Cliff Hones" To: , References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020422130402 DOT 05e18c48 AT lnxmain> Subject: Re: Incorrect file size reported .... Date: Mon, 22 Apr 2002 18:21:37 +0100 Organization: Aonix Europe Ltd. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Roland Glenn McIntosh wrote: > Are you sure you don't have some FAT corruption? (or ntfs corruption?) > Running Scandisk or defrag with the "check disk" option should tell you. Actually, this looks much more like the 32-bit file-size limit in Cygwin. 2,097,156KB is just over 2^31 (given 1K=1024 bytes). I expect large file support will be added to Cygwin one day, but it's not there yet, so there's no workaround (except of course that you are always free to use direct WinAPI calls within a Cygwin program). -- Cliff -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/