Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!bionet!ames!amdcad!sun!pitstop!sundc!seismo!uunet!mcvax!hp4nl!nikhefk!petec
From: petec@nikhefk.UUCP (Pete Countryman)
Newsgroups: comp.sys.mac
Subject: Re: Why can't I use FKEY 0 on a Mac II
Summary: FKEY 0 may bomb in Finder if bad Desktop
Keywords: FKEY, Finder, Desktop
Message-ID: <494@nikhefk.UUCP>
Date: 3 Feb 89 13:07:44 GMT
References: <198@Portia.Stanford.EDU>
Reply-To: petec@nikhefk.UUCP (Pete Countryman)
Organization: Nikhef-K, Amsterdam (the Netherlands).
Lines: 12

I once had a problem with FKEY 0 bombing, and it happened only 
when I was in the Finder.  It turned out that a Shareware application 
on my disk had the Creator signature set to FKEY.  This put a 
resource of type FKEY into the Desktop file on the disk, with ID=0.
The Desktop file is always open when you're in the Finder.
Since the Desktop file was opened _after_ the System file, this
meant that pressing cmd-shft-0 made the Mac try to execute the 
contents of the bogus FKEY resource.  Re-building the Desktop 
obviously doesn't fix this.  You should a) trash the offending 
application; b) change the Creator type of the application or
c) turn off the BNDL bit for the application.  Then re-build the 
Desktop file.