Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!apple!Apple.COM!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac
Subject: Re: SuitCase II disables Tappy Type
Message-ID: <6292@internal.Apple.COM>
Date: 22 Jan 90 18:45:06 GMT
References: <2851@cerberus.oakhill.UUCP>
Sender: usenet@Apple.COM
Organization: Objects-R-Us,  Apple Computer, Inc.
Lines: 33

In article <2851@cerberus.oakhill.UUCP> hunter@oakhill.UUCP (Hunter 
Scales) writes:
>         Suitcase II installed, Tappy Type wont work.  Has anybody else
>         noticed this?

There's some chance that Suitcase isn't the culprit.  I've noticed that 
there are INITs that call PBHGetVol & PBHSetVol to save and restore the 
current directory, which is a bad thing to do (according to Tech Note 140).

What happens is that INIT "A" call PBHGetVol & PBHSetVol.  This sets the 
current volume to refer to an explicit dirID.  

Then Suitcase (or some other INIT) calls GetVol and since the system can't 
return an explicit dirID, it returns just the volume refnum.  

When Suitcase restores the current volume with a call to SetVol, the 
current directory is set to the root of the volume.  The system code that 
searches for INIT files then start looking at the root of the volume.  
Since it won't normally find any INITs there, and INITs that are after 
Suitcase in alphabetical order won't run.

You can see if this is the case by testing whether *ANY* init that follows 
Suitcase alphabetically is run.  (For example rename another INIT to 
follow Suitcase and see if it is also disabled.)

If this is the problem, then you can figure out which INIT is calling 
PBHSetVol using Macsbug.

Larry Rosenstein, Apple Computer, Inc.
Object Specialist

Internet: lsr@Apple.com   UUCP: {nsc, sun}!apple!lsr
AppleLink: Rosenstein1