Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!web-3g.berkeley.edu!labc-4dc
From: labc-4dc@web-3g.berkeley.edu (Erik Talvola)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Wacky results from "dbwrendr"
Keywords: ray tmp2gif ng
Message-ID: <20483@agate.BERKELEY.EDU>
Date: 16 Feb 89 23:26:10 GMT
References: <1575@leah.Albany.Edu>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
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?



If you look in the documentation concerning TMP2GIF, you will find that it
normally expects a 320x400 line image.  It then skips every other line to
get the final 320x200 GIF picture.  All of the sample files on the disk are
set up to be 320x200 resolution originally however.  If you run TMP2GIF with
a "-2" option (I think), it won't skip the lines and you will have the full
image.

--
Erik Talvola               | "It's just what we need... a colossal negative 
labc-4dc@web.berkeley.edu  | space wedgie of great power coming right at us
c164-2bf@bard.berkeley.edu | at warp speed." -- Star Drek