Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rice!sun-spots-request
From: adm@apollo.drexel.edu (Administration)
Newsgroups: comp.sys.sun
Subject: imagetool under SunOS 4.0.3
Keywords: Miscellaneous
Message-ID: <2293@brazos.Rice.edu>
Date: 20 Oct 89 14:09:12 GMT
Sender: news@rice.edu
Organization: Sun-Spots
Lines: 35
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 167, message 16 of 17

We have a system consisting of 3 Sun-3's and 2 SPARCstation-1's, all
running SunOS 4.0.3.   When we obtained the SPARCstations, we copied over
the source code for imagetool and compiled it using the Sun-4 option.
When imagetool was then executed, some problems arose.  Specifically, when
an image was initially read in it would be displayed distorted (appearing
as though, perhaps, the dimensions had not been specified properly).  If
the image was then magnified using 'zoom', the expanded display was
correct, except for a white diagonal stripe or two that would appear
across the image.  We obtained the latest version of the source code from
NCSA, and it turned out to be identical to the source we already had.
There is no special option for compiling on a SPARCstation, so we thought
perhaps that the Sun-4 compilation was not correct for these machines.  To
check it, we recompiled the Sun-3 version of imagetool.  The result: when
imagetool was recompiled on the Sun-3, the same problem occurred.  We have
therefore concluded that this is a problem with compiling imagetool under
the new operating system and is not a machine related problem.  When we
use the old binary for imagetool on the Sun-3's, which was compiled under
SunOS 3.x (probably 3.5, but possibly earlier), everything is fine.  When
we use the new binary, imagetool cannot read images properly.

We have now re-installed the old binary on the Sun-3's, and imagetool is
working fine on these systems, but we cannot use imagetool on the
SPARCstations.

We know that there are changes in the new OS in the way libraries are
linked and in the way sunview is implemented.  The dynamically linked
libraries give a much smaller binary file, but could they also be
responsible for the problem we are seeing?  Sunview might be to blame, of
course, but it really looks like the problem is in reading and/or
manipulating the data from the image file, and not in the graphics
interface.

Does anybody know of a workaround for this problem?  Are there any ideas
as to either the cause or the solution?  Respond in Sun-Spots, or directly
to me and I'll summarize the responses.  Thanks in advance.