Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!nprdc!malloy
From: malloy@nprdc.arpa (Sean Malloy)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Wacky results from "dbwrendr"
Keywords: ray tmp2gif ng
Message-ID: <1492@skinner.nprdc.arpa>
Date: 17 Feb 89 14:49:55 GMT
References: <1575@leah.Albany.Edu>
Reply-To: malloy@nprdc.arpa (Sean Malloy)
Organization: Navy Personnel R&D Center, San Diego
Lines: 22

In article <1575@leah.Albany.Edu> rds95@leah.Albany.Edu (Robert Seals) writes:
>Well, I got the recently posted "dbwrendr" aka "ray" and "tmp2gif"
>and everything unpacked fine and stuff, and it runs... kinda.
>
>After computing around 200 scan lines, the program terminates, apparently
>normally. Then when using "tmp2gif" the bottom half of the picture is just
>a repeat of the last scan line; I presume this is because of the
>Amiga's 400 scan lines. So what's the scoop?

When in doubt, RTFM. The file TMP2GIF.MAN explicitly states that the
program converts a 320x400 .TMP file into a 320x200 GIF file by
throwing away alternate lines. With 100 lines to fill, and no new
lines to read, the program just repeats the last scan line. However,
if your input .TMP file is already 320x200, the manual says to use the
invocation 'TMP2GIF -2 <file>' which tells TMP2GIF that the input is
only 200 lines high, so don't drop alternate lines.


	Sean Malloy
	Navy Personnel Research & Development Center
	San Diego, CA 92152-6800
	malloy@nprdc.navy.mil