Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!ut-sally!ut-ngp!cgeiger
From: cgeiger@ut-ngp.UUCP (charles s. geiger, esq.)
Newsgroups: comp.sys.mac
Subject: Re: multifinder won't boot
Message-ID: <6873@ut-ngp.UUCP>
Date: Wed, 18-Nov-87 18:12:15 EST
Article-I.D.: ut-ngp.6873
Posted: Wed Nov 18 18:12:15 1987
Date-Received: Sat, 21-Nov-87 10:51:40 EST
References: <513@lsrhs.UUCP> <3543@uwmcsd1.UUCP>
Organization: UTexas Computation Center, Austin, Texas
Lines: 22
Summary: my pop-keys work just fine

In article <3543@uwmcsd1.UUCP>, hammen@csd4.milw.wisc.edu (Robert Joseph Hammen) writes:
> Here lies your problem, I believe. The Pop-Keys INIT was reported to
> be incompatible with MultiFinder. The last version of the Pop-Keys
> INIT that I had (the one that came with the FKEY Manager 3.0) bombed
> when put in my System Folder.

I have FKEY Manager 2.5 and presumably have the compatible version
of Pop-Keys.  It works just fine on my Mac+ with Multifinder and
loads of other inits.

Someone awhile back posted a suggestion as to how to fix someone
else's problem with Suitcase--pull out the battery, thereby erasing
the PRAM, and then restart.  This worked for me, and I'm wondering
if this couldn't be a solution to try with Pop-Keys as well (unless
2.5 is compatible and 3.0 isn't).

cheers, from
charles s. geiger
ARPA:  cgeiger@ngp.cc.utexas.edu       cgeiger@ut-ngp.ARPA
UUCP:  ihnp4!ut-ngp!cgeiger     allegra!ut-ngp!cgeiger
       gatech!ut-ngp!cgeiger    seismo!ut-sally!ut-ngp!cgeiger
       harvard!ut-sally!ut-ngp!cgeiger