Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!purdue!mentor.cc.purdue.edu!nova.cc.purdue.edu!gerrit
From: gerrit@nova.cc.purdue.edu (Gerrit)
Newsgroups: comp.sys.next
Subject: Re: Hints for upgrading from 0.8 to 0.9
Message-ID: <2742@mentor.cc.purdue.edu>
Date: 18 May 89 02:17:27 GMT
References: <2705@mentor.cc.purdue.edu> <2726@mentor.cc.purdue.edu> <4905@umd5.umd.edu> <11570@polyslo.CalPoly.EDU>
Sender: news@mentor.cc.purdue.edu
Reply-To: gerrit@nova.cc.purdue.edu (Gerrit)
Organization: Purdue University
Lines: 41

In article <11570@polyslo.CalPoly.EDU> sstanfie@polyslo.CalPoly.EDU (skot) writes:
>feldman@umd5.umd.edu (Mark Feldman) writes:
>>>gerrit@nova.cc.purdue.edu (Gerrit) writes:
>>> [References to WriteNow version of upgrade 0.8 to 0.9 notes deleted]
>
>Hey Mark & Gerrit!
>
>Any way you guys can make those files  ASCII standard files?  See, I only
>have Write Now on the NeXT's and the only way to read those docs would
>be to ftp to my local site.  Well, I probably need those docs to get it
>up on the net.  See...endless loop.

Not really true - the documents can be read on (and printed from) the
NeXT with the 0.8 version of WriteNow - if you are running 0.8 you
should be able to read them (I've read the doc on a couple of our 0.8
systems before).

>So, if there is a way to save a *.wn file as an ascii text, I'd really
>appreciate getting a copy of it (throught ftp)

I took a look at a saved ASCII only copy, and it is much more difficult
to read.  Emphasis is removed, heading are difficult to distinguish
from short paragraphs and examples, etc.  If you really want an ASCII
copy, I can send you a copy, but I also recommend *strongly* that you
read this document and other printed NeXT documentation *before* taking
down your 0.8 system and wiping the disks.  We give you an idea of what
files to save and how to do your backups so that you can get back the
things that you need from your old system.

If people are interested, I can try to save a PostScript version.  I'd
prefer to have a single authoritative copy, but if a PostScript copy
is any better I'll try that.

BTW, there will probably be yet another new version available soon.  I
think I'm going to start incorporating version numbers.  The new one
will be Version 3 - watch the README file for info.

Gerrit Huizenga
NeXT Workstation Support
Purdue University Computing Center
gerrit@mentor.cc.purdue.edu