Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!think!ames!oliveb!felix!kehr
From: kehr@felix.UUCP (Shirley Kehr)
Newsgroups: comp.sys.mac
Subject: Re: Black Apple (problems installing systems)
Message-ID: <65200@felix.UUCP>
Date: 20 Oct 88 14:44:41 GMT
References: <1052@microsoft.UUCP> <9601@haddock.ima.isc.com>
Sender: daemon@felix.UUCP
Reply-To: kehr@felix.UUCP (Shirley Kehr)
Organization: FileNet Corp., Costa Mesa, CA
Lines: 50

In article <9601@haddock.ima.isc.com> suitti@haddock.ima.isc.com (Steve Uitti) writes:
>	About a month ago, I upgraded to system 6.0 on my Mac II.  A
>friend upgraded his SE to 6.0 at about the same time.  We both used to
>the installer to do the upgrade.
>	My friend found 6.0 so buggy that he reverted to 5.4 (or
>whatever his previous system was).  This was now newly just as buggy.
>He solved his problems by erasing his hard disk and installing 5.4
>from scratch.  (By doing selective restores, he cleaned up all sorts
>of cruft on his hard disk at the same time).
>
>	The moral of the story is that the installer is broken.  Damn
>shame.  It is very convenient.
>
Thanks for the information. That explains why I couldn't revert to System 5.0
at home (on an upgraded 512 that couldn't handle System 6.0).  But instead of
erasing the entire hard disk, I just trashed the hybrid system I got by
attempting to use System 5.0's installer on top of System 6.0.

I guess you programmers have a whole arsenal of tricks to find bugs us ordinary
users can't see (I'm not complaining!). I'm still using the original System 6.0
on a Mac II at work without problem one that I can attribute to the system.
(Now trying to run Word and Canvas together and moving lots of windows around
too fast is another story. My mini demos of multifinder's capabilities always
crash in front of prospective owners, but I attribute that to Word's inability
to deal outside the first megabyte of memory.)

>	MacroMaker is brain dead.  It breaks things, slows things down
>unbearably, and some macros only work until next reboot (like the
>trick for alphabetizing icons in a folder).  Maybe I'm missing
>something.  Having played with it, I've ditched it.

MacroMaker did not run one of my "creations" (can't remember what it was),
but I was super-impressed when I could combine QuickKeys definitions (menu
choices and aliases) into a longer string using MacroMaker. I used MacroMaker
to set up the nice quotes (which is the purpose of QuickKeys alias function,
but I just hadn't done it yet).

I used to put Word's TOC code in by pressing a function key that asked for the
name of the glossary item. Then I had to type the name (e.g., toc1, toc2, etc.)
and press Return. MacroMaker positions me at the beginning of the line, then 
uses the QuickKey that prompts for glossary name, and types the name for me.  Itwas a lot easier to just click "record" and do this sequence of events than to
figure out how to string together a bunch of QuickKey definitions into a string.

Maybe I just don't expect software to do as much as you do. It's all magic
to me and I'm delighted with what I can do today in comparison to the NBI
word processor I used to work with (8-inch single-sided floppies - not even
proportional spacing, let alone different font sizes and types, slow daisy
wheel printer, etc. - only about a year ago).

Shirley Kehr