🚀 go-pugleaf

From article <46100230@uxe.cso.uiuc.edu>, by hirchert@uxe.cso.uiuc.edu:
> My upgrade to Suitcase II finally arrived.  After installing it and booting
> with Multifinder, I find that when I try to access the Control Panel, I get
> a message about a needed resource being missing.  Once that happens, I can't
> access any DAs (they all just beep).  If I reboot without Multifinder or go
> back to Suitcase I, everything works fine.  Does anyone have an idea about
> what's going wrong here and how I fix it?
> 
> Kurt W. Hirchert     hirchert@ncsa.uiuc.edu
> National Center for Supercomputing Applications

One of the things I missed on my first installation of Suitcase II caused
symptoms very similar to the ones you describe.  After installation of 
Suitcase II, you reboot, and THEN you open each suitcase containing DAs and
Fonts you wish to use manually with Suitcase II.  You do this before doing
anything else.  This is a one-time step, because Suitcase II no longer looks
in the System Folder for a Font/DA Folder so that it can automatically open
everything in it.  Having opened all DA and Font suitcases manually, Suitcase
II will now open each of these whenever it is activated on a reboot or
startup.  Fifth Generation says this in their documentation, but old habits
from using Suitcase 1.2 are hard to break, I guess.  Hope this helps your
situation.

On the more general issue of Suitcase II and MacOS 6.0 et seq, I have run
into some interference between Suitcase II and disketter initialization.
With Suitcase II installed and active on a Mac II, an attempt to erase or
initialize a diskette results in a slightly malformed diskette directory/
desktop.  The symptoms are that after initialization, verification, and
directory creation a dialog box appears stating that the diskette is partially
damaged and asking if you wish it repaired.  Selecting OK repairs the
damage.  Subsequent insertions of the diskette after repair find it intact.
But this behaviour causes backup programs, such as DiskFit, to barf when
trying to extend the backup set to a new diskette.  This seems to me to be
a fundamental level of interference which should not occur.  Fifth Generation
tech support believes the problem doesn't exist because it doesn't happen on
their stripped down Mac II.  I've checked the problem on a plain MacOS 6.0
running only Finder and no inits or cdevs.  I've done the same for 6.0.2.
Running MultiFinder has no affect one way or the other.  All I have to do to
remove the problem is to substitute Suitcase 1.2 for Suitcase II (leaving
Pyro 3.0 in place) and the problem disappears.  Anybody have any thoughts as
to what the problem is or how to 'fix' it?

TJ {With Amazing Grace} The Piper
aka Ted Jardine  CFI-ASME/I
Usenet:		...uw-beaver!ssc-vax!ted
Internet:	ted@boeing.com
-- 
TJ {With Amazing Grace} The Piper
aka Ted Jardine  CFI-ASME/I
Usenet:		...uw-beaver!ssc-vax!ted
Internet:	ted@boeing.com