Received: from [207.176.88.85] by phillip.cerious.com (NTMail 3.03.0017/7.aaxh) with ESMTP id pcrews for <pcrews@cerious.com>; Fri, 19 Nov 1999 12:47:47 -0500
Received: from localhost (daemon@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) with SMTP id OAA02605;
	Fri, 19 Nov 1999 14:07:08 -0500
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Fri, 19 Nov 1999 14:01:45 -0500
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) id OAA02483
	for tiff-outgoing; Fri, 19 Nov 1999 14:01:44 -0500
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from relay.EECS.Berkeley.EDU (relay.EECS.Berkeley.EDU [169.229.34.228])
	by gate7.olympiakos.com (8.9.3/8.9.3) with ESMTP id OAA02480
	for <tiff@olympiakos.com>; Fri, 19 Nov 1999 14:01:42 -0500
Received: from cs.berkeley.edu (windsome.CS.Berkeley.EDU [128.32.131.134])
	by relay.EECS.Berkeley.EDU (8.9.3/8.9.3) with ESMTP id JAA27139;
	Fri, 19 Nov 1999 09:00:48 -0800 (PST)
Message-ID: <38357E7A.F4DB7451@cs.berkeley.edu>
Date: Fri, 19 Nov 1999 08:44:42 -0800
From: Richard Fateman <fateman@cs.berkeley.edu>
Organization: University of California, Berkeley
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: tiff@olympiakos.com
Subject: tiffclose on windows leaves files open?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-tiff@olympiakos.com

 If I tiffopen a file in mode "r"
process it (or not) and then
tiffclose the file descriptor,
that file cannot be deleted in my Windows (NT) system.
At least not while the program is running.

I have to open it in mode "ru" or "rm"
if I want to delete it.

I think this is a bug in tiffclose that doesn't unmap
the file properly.
Maybe no one else noticed it because people tend
to not read and delete tif files in the same running
program?

For what it's worth, I've linked the tiff library
into a lisp system; the lisp system is running a
server which takes a (b&w) 1-page tiff image. 
  Right now it sucks up the file
you specify and tries to compute a "skew" angle
for the page. 
Our next step is to offer to send you back your
deskewed page.
We're trying to figure out how to integrate
the rest of the system (an OCR system written
in Lisp) to the server. And yes, the server too
is written in Lisp.

  http://windsome.cs.berkeley.edu:8010/ocrme

Feel free to try it.  Don't be surprised if
it is not up. If you try it and it fails in some
way that you'd like to report, please say so.
(fateman@cs.berkeley.edu)
