AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

1998.04.06 18:42 "libtiff isn't closing all of the file handles on NT ?", by Chris Griffin
1998.04.06 23:24 "Re: libtiff isn't closing all of the file handles on NT ?", by Masanori Kanda
1998.04.07 00:44 "RE: libtiff isn't closing all of the file handles on NT ?", by Dean Grimm
1998.04.07 13:41 "Re: libtiff isn't closing all of the file handles on NT ?", by Jim White
1998.04.07 15:40 "Re: libtiff isn't closing all of the file handles on NT ?", by Rex Jolliff
1998.04.07 17:13 "RE: libtiff isn't closing all of the file handles on NT ?", by Gerben Vos

1998.04.06 23:24 "Re: libtiff isn't closing all of the file handles on NT ?", by Masanori Kanda

I am using LIBTIFF from within a DLL to read and write TIFF images on a Windows NT machine. I am finding that after I read a file, I can no longer write to that file, and I also cannot delete it at the OS level until my application has exited.

I became the phenomenon which was the same, too. Such a problem disapeared by changing the option in the call of the function ( TIFFOpen() ) as follows in the case of me.

TIFFOpen( lpfilename, "ru" );

The "u" option indicates the access which doesn't mapped file forcibly. And, When it is written, the "u" option is not necessary.

--------------------------------------------------------------
 Masanori Kanda
 Youth Engineering Co.Ltd.
mailto:mkanda@taurus.bekkoame.or.jp, PAH03156@niftyserve.or.jp
 http://www.bekkoame.or.jp/~mkanda/
--------------------------------------------------------------