Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <000601beb984$cf9e43f0$29acdfd0@InspirePharm.Com> From: "Suhaib M. Siddiqi" To: "Ulrich Koehler" , References: <376A37B8 DOT A5863A50 AT mvt DOT tu-clausthal DOT de> Subject: Re: Problems with libtiff! Date: Fri, 18 Jun 1999 08:19:26 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 > Hello, > > I browsed through the archives and there should be > no problems at all, but... > > libtiff v3.4beta037 + cygwin B20.1 > > % sh configure --target=i586 > % make > > compiles without any errors on Win95b, AMD-K6-2. Yes, it compiles without errors. > > execution problems: > > tools/tiffdump.exe - works ok > tools/tiff2ps.exe - does not work, probs with strip-size > tools/thumbnail.exe - does not work, > the thumbnail image is 8 byte in size (just the header) > I guess libtiff is unable to read my greyscale image > which I created with libtiff on a UNIX-system. > (the images is ok, a hex-dump shows this) > and so on... that is where the problem is, at least i noticed. if you unmount the disk then binary mount it umount / mount -b c: / Now your tiff images created on UNIX can be read, also tiff images created under Cygwin will not have header problems and can be opened with Photoshop and/or MS Wang Image Editor. That's what I meant that someone needs to port Tiff properly the precompiled binaries available from Cygwin users have the above mentioned problems. I have tried almost all the precompiled Tiff binaries available on net from different porters and all of them have this problem. --Suhaib > > If I save images with my own program via libtiff > (on UNIX everything works well) the TIFF-images > are corrupt. The hex dump of the image shows: > - byte ordering and the first 4 bytes (0..3) of the header > seem to be ok. > - the pointer to the first IFD (Byte 4..7) misses the real IFD > by one byte. If I fix this manually the image is recognized > by other programs (type, size etc. are correct) but the data > is still corrupt. > ??? > > Does anybody got a _working_ libtiff on Win95? > > Bye > Ulrich Koehler > > -- > Want to unsubscribe from this list? > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com > > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com