Xref: utzoo alt.sys.sun:1665 comp.windows.news:2360
Path: utzoo!utgpu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!husc6!lange!bochner
From: bochner@lange.harvard.EDU (Harry Bochner)
Newsgroups: alt.sys.sun,comp.windows.news
Subject: SunWrite under SunOS 4.1?
Message-ID: <4410@husc6.harvard.edu>
Date: 12 Oct 90 18:06:08 GMT
Sender: news@husc6.harvard.edu
Reply-To: bochner@lange.harvard.EDU (Harry Bochner)
Organization: Aiken Computation Laboratory, Harvard University
Lines: 31

Yes, I know that SunWrite is no longer marketed as such, that the rights have
been sold back to Island Graphics. But under our site license agreement
with Sun
we have access to SunWrite version 1.1; we haven't established contact with
Island Graphics yet, and I'm not sure who (if anyone) is supposed to provide
support ...

So here's the problem: we installed SunWrite about a year ago, and it works
fine under SunOS 4.0.3. Since then we've upgraded almost all our machines to
SunOS 4.1; we haven't been using SunWrite, but now one of our users wants to
use it (on an SLC they acquired for the purpose).

Under 4.1 here's what I observe:
SunWrite starts up fine, allows basic editing, etc.  When you save the file, it
seems to go smoothly. But it doesn't reopen the file correctly: it apparently
misunderstands it's native format. That is, the file format begins with
a header
(in ascii) of global formatting information.  When you try to reopen the file,
_part_ of that formatting information shows up as text in the file. Saving as
this point and reopening results in doubling the about of formatting
information
that creeps in.

I've tried this on an SLC, a SS1 and a 3/60: same results. The files that won't
reopen under 4.1 _will_ reopen on one of the few machines still running 4.0.3.

Any ideas what the problem is?
Thanks for any suggestions.

Harry Bochner
bochner@das.harvard.edu