Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-j.b-one.net (mx-j.one.com [91.198.169.57])
	by mail9.b-one.net (Postfix) with ESMTP id A8B6C400614
	for <info@awaresystems.be>; Wed,  1 Dec 2010 06:20:45 +0100 (CET)
Received: by mx-j.b-one.net (Postfix, from userid 106)
	id 9FD1410AA5E; Wed,  1 Dec 2010 06:20:45 +0100 (CET)
X-Virus-Scanned: by one.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=0 required=4 tests=[none]
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144]) by
 mx-j.b-one.net (Postfix) with ESMTP id 9253610AA5E for
 <info@awaresystems.be>; Wed,  1 Dec 2010 06:20:44 +0100 (CET)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by
 lists.maptools.org (Postfix) with ESMTP id B1B461D0E524D; Wed,  1 Dec 2010
 00:19:07 -0500 (EST)
Received: from blade.simplesystems.org (blade.simplesystems.org
 [65.66.246.74]) by lists.maptools.org (Postfix) with ESMTPS id 71DAD1D0E5248
 for <tiff@lists.maptools.org>; Wed,  1 Dec 2010 00:16:13 -0500 (EST)
Received: from freddy.simplesystems.org (freddy.simplesystems.org
 [65.66.246.65]) by blade.simplesystems.org (8.13.8+Sun/8.13.8) with ESMTP id
 oB15FtXV027626; Tue, 30 Nov 2010 23:16:06 -0600 (CST)
Date: Tue, 30 Nov 2010 23:15:55 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: Kevin Myers <KevinMyers@austin.rr.com>
In-Reply-To: <14DCF6D0C50244AE92D1B17BAECB6F5D@KAM6400>
Message-ID: <alpine.GSO.2.01.1011302310300.9713@freddy.simplesystems.org>
References: <76394064-A6C2-46E1-BC59-DB187EDDD275@tiscali.co.uk>
 <4CF55000.7000109@telegraphics.com.au>
 <14DCF6D0C50244AE92D1B17BAECB6F5D@KAM6400>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
 (blade.simplesystems.org [65.66.246.90]); Tue, 30 Nov 2010 23:16:06 -0600
 (CST)
Cc: tiff@lists.maptools.org
Subject: Re: [Tiff] Win32 ReadFile() / WriteFile() heads-up
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

On Tue, 30 Nov 2010, Kevin Myers wrote:

> I haven't looked into this very much *at all*, so what I am about to say
> could easily be *very* wrong.  That being said, wouldn't changing libtiff to
> use read() and write() break large file handling (greater than 4GB) under
> Win32?  If so, that would be a bad thing.

It is possible to use read() and write() with large files under 
Windows.  GraphicsMagick does so.  It works with Visual C++ but last 
time I tried with MinGW GCC it did not work because MinGW was not 
enabling the necessary APIs.

As far as libtiff using Windows file APIs goes, it can be "cured" by 
using TIFFClientOpen() to specify use of the desired file access APIs. 
This requires writing some tiny I/O wrapper functions.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
