Return-Path: <harringf@yahoo.com>
Received: from localhost (ak4719.spb.edu [127.0.0.1])
	by ak4719.spb.edu (8.12.1/8.12.1/Debian -5) with ESMTP id h476deS3005018
	for <dron@localhost>; Wed, 7 May 2003 10:42:57 +0400
Received: from pop.in02.prd.whowhere.com [209.202.220.196]
	by localhost with POP3 (fetchmail-6.2.0)
	for dron@localhost (single-drop); Wed, 07 May 2003 10:42:57 +0400 (MSD)
Received: from gate7.olympiakos.com ([64.32.199.150]) by whowhere.com; Tue, 06 May 2003 15:30:02 -0000
X-Envelope-Sender: owner-tiff@olympiakos.com
Received: by gate7.olympiakos.com (Postfix, from userid 65534)
	id 1F60C110D8; Tue,  6 May 2003 11:29:46 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by gate7.olympiakos.com (Postfix) with SMTP
	id 038EF110D0; Tue,  6 May 2003 11:29:45 -0400 (EDT)
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Tue, 6 May 2003 11:29:25 -0400
Delivered-To: tiff-outgoing@gate7.olympiakos.com
Received: from web41004.mail.yahoo.com (web41004.mail.yahoo.com [66.218.93.3])
	by gate7.olympiakos.com (Postfix) with SMTP id A9BA6110A6
	for <tiff-outgoing@gate7.olympiakos.com>; Tue,  6 May 2003 11:29:24 -0400 (EDT)
Message-ID: <20030506152923.30518.qmail@web41004.mail.yahoo.com>
Received: from [12.8.123.244] by web41004.mail.yahoo.com via HTTP; Tue, 06 May 2003 08:29:23 PDT
Date: Tue, 6 May 2003 08:29:23 -0700 (PDT)
From: Harring Figueiredo <harringf@yahoo.com>
Subject: RE: Decode Message : Help ( SOLVED)
To: Carter John-jcarte01 <John.A.Carter@motorola.com>,
   tiff-outgoing@gate7.olympiakos.com
In-Reply-To: <496E31A690F7D311B93C0008C789494C0A1A35FE@zei02exm01.cork.cig.mot.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Precedence: bulk
Status: RO
Content-Length: 4081
Lines: 133



 John, 

 Thanks for the reply.

 I was looking at the image data itself using khexedit, and the original Strip
image begin with 00 00 ...

 When I was looking at mine, it was begining with II* (wich is the TIFF
signature), so from that point, I knew I had an offset screwed up. Sure enough,
I was not updating/setting the StripOffset Tag value when I was reading it from
 the original file; therefore, the offset value was 0 (zero) when I was copying
the strips (begining at zero offset) I was actually getting the entire heather
with it.-- What a nice bug.


  Thanks for the reply.



--- Carter John-jcarte01 <John.A.Carter@motorola.com> wrote:
> at a guess (seeing code word) I'd say there's a problem with LZW decoding.
> 55 =   00000110111   assuming 11 bit code
> 1864 = 11101001000
> 
> can you open the tiff file with something like hexedit and use 
> the scan offsets to confirm that the image file is ok.
> 
> how does it know what to expect
> 
> -----Original Message-----
> From: Harring Figueiredo [mailto:harringf@yahoo.com]
> Sent: 06 May 2003 15:55
> To: tiff-outgoing@gate7.olympiakos.com
> Subject: Decode Message : Help/
> 
> 
> 
> 
>  Folks,
>   I created a TIFF file using a java program that I wrote. The image I
> created
> is based on another TIFF file. 
>   When I try to load the image on gqview, I get the follwoing error. (Gimp
> also
> gives the same type of errors - see below)
> 
>  gqview Error Messages:
> Fax4Decode: har.tiff: Bad code word at scanline 1 (x 55).
> Fax4Decode: Warning, har.tiff: Premature EOL at scanline 1 (got 55, expected
> 1864).
> 
>  Gimp Error MEssages
> 
> gimp: har.tiff: Premature EOL at scanline 8 (got 1863, expected 1864)
> gimp: har.tiff: Line length mismatch at scanline 13 (got 1865, expected 1864)
> gimp: har.tiff: Bad code word at scanline 17 (x 1863)
> gimp: har.tiff: Premature EOL at scanline 17 (got 1863, expected 1864)
> gimp: har.tiff: Line length mismatch at scanline 20 (got 2265, expected 1864)
> gimp: har.tiff: Line length mismatch at scanline 21 (got 1870, expected 1864)
> ...... [ More messages imiliar to the above line ]...
> 
>   What does that mean ? ( I can load the original file OK. )
> 
>  NOTE: The original file is TIFF little endian, and the one I create is TIFF
> Big Endian. (Perhaps will help someone spot the problem)
> 
> 
> 
>    Here is a tiffdump of the Files:
> 
>    ORIGINAL FILE (Loads on on gqview)
> 
> Magic: 0x4949 <little-endian> Version: 0x2a
> Directory 0: offset 11552 (0x2d20) next 0 (0)
> ImageWidth (256) SHORT (3) 1<1864>
> ImageLength (257) SHORT (3) 1<728>
> Compression (259) SHORT (3) 1<4>
> Photometric (262) SHORT (3) 1<0>
> StripOffsets (273) LONG (4) 1<8>
> Orientation (274) SHORT (3) 1<1>
> RowsPerStrip (278) SHORT (3) 1<728>
> StripByteCounts (279) LONG (4) 1<11544>
> XResolution (282) RATIONAL (5) 1<200>
> YResolution (283) RATIONAL (5) 1<1>
> PlanarConfig (284) SHORT (3) 1<1>
> -----------------------------------------
> 
>   BAD IMAGE ( created by me)
> Magic: 0x4d4d <big-endian> Version: 0x2a
> Directory 0: offset 8 (0x8) next 0 (0)
> ImageWidth (256) SHORT (3) 1<1864>
> ImageLength (257) SHORT (3) 1<728>
> Compression (259) SHORT (3) 1<4>
> Photometric (262) SHORT (3) 1<0>
> StripOffsets (273) LONG (4) 1<146>
> Orientation (274) SHORT (3) 1<1>
> RowsPerStrip (278) SHORT (3) 1<728>
> StripByteCounts (279) LONG (4) 1<11544>
> XResolution (282) RATIONAL (5) 1<200>
> YResolution (283) RATIONAL (5) 1<1>
> PlanarConfig (284) SHORT (3) 1<1>
> 
> 
>   When I am copying the STRIPS (in this case, nly 1 (one), I basically do a
> mem
> copy from the original file to the file I am creating. ( I do not have to
> convert to Big endian, do I ? )
> 
>  I can send the images if anyone is interested.
> 
>  Thank you SO MUCH for any help.
> 
> Harring Figueiredo.
> 
> 
> 
> 
> 
> 
> 
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

