Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!mailrus!cornell!uw-beaver!tektronix!tekig5!tekig4!brianr
From: brianr@tekig4.TEK.COM (Brian Rhodefer)
Newsgroups: comp.sys.amiga
Subject: FFS problems
Keywords: workbench 1.3 lockup
Message-ID: <3354@tekig4.TEK.COM>
Date: 25 Oct 88 08:01:29 GMT
Organization: Tektronix Inc., Beaverton, Or.
Lines: 57

Unlike the jubilant Chris Barrett, my experience with 1.3 and its
many wonders has not been effortless.  I won't dwell on the many
different ways I managed, even though incessantly and intensely
reading the documentation, to screw things up while arriving at
a working set of startup scripts.  I will say that along the way
I got to see a whole bunch of new Amiga behaviors, and each one seemed
almost as miraculous and unlikely as `Useful operation'.

I won't dwell on them, because in yielding to solution in only 20 hours
of trial-and-error, they proved themselves to be trivial and uninteresting.

The Fast File System, though, seems to be an impressive enough problem
to seek help with.   Can any of you experts out there divine anything
from the following symptoms:  (not necessarily a complete list - just all
I've noticed) ?

1) I'm not sure when this started happening, but I've noticed that some
   features of Manx'  `z' text editor no longer work.  For example, I can
   use the editor to create a file in RAM:, using Insert mode, write it out
   to storage, and exit the editor with no ill effect.  The `jump to next
   word' command, though, (`w'), which I use a lot, doesn't work.  It'll
   either toggle the cursor onto a different line, or cause the machine
   to hang up badly enough to freeze the mouse pointer, depending on its mood.

   This happens if z is run from a FFS-formatted partition, or an AmigaDOS
   formatted one, and whether or not the FastFonts (FF) program is `ON'.

1a) Thinking that my attempt to save my files' contents by FFSing only
    one partition at a time and doing `copy xx0: xx1: clone all' to preserve
    my command files had somehow corrupted the `z' program, I pulled it back
    off the backup I'd made just prior to installing 1.3, and stuck the
    recovered file in an AmigaDOS partition for good measure.
    Still misbehaved in the same way.

2) Still needing to edit a file, I gave Commodore's `MEmacs' a try.
   It had similar difficulties navigating the cursor around, and also
   locked the machine up (though this time I think it was on exit from
   the editor).

3) `Ed' seems to work OK.

4) The non-FFS partition isn't yet mounted by my startup sequence, so
   I'm mounting it manually.  After so doing, I find I can't do a `dir'
   on it.   Well, I can try, but what comes out is the contents of my FFS
   partition, NOT the AmigaDOS partition.



If anyone out there can suggest an cure for these problems, I'll be
very grateful.  It would sure be nice to have the amiga working again,
though, since the Bridgeboard didn't get upgraded too, IT still works, and
I can still get the useful stuff done.


Bewildered again,

Brian Rhodefer   ...!tektronix!tekig4!brianr