Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!rutgers!elbereth.rutgers.edu!rgonzal From: rgonzal@elbereth.rutgers.edu (Ralph Gonzalez) Newsgroups: comp.sys.mac.hypercard Subject: Re: Hypercard 2 problem with "on openstack" Keywords: hypercard 2 Message-ID: Date: 7 Feb 91 13:59:45 GMT References: Distribution: na Organization: Rutgers Univ., New Brunswick, N.J. Lines: 18 In fact, it wasn't a buggy HyperCard or Home stack, but an init conflict which was giving me problems. Here's as near as I can pin it down: If you have the Gatekeeper Aid init installed AND you're using HyperCard 2.0 AND you start HyperCard by double-clicking on a (non-Home) stack which has it's own resource fork (due to a snd, ICN, XCMD, etc.) then this stack's "on openstack" handler may not be executed. The problem seems to arise in the Home stack's "on startup" handler which calls a handler which calls the FontExists XCMD. You will hear a "beep" if you have this problem. It only happens with some versions of the Home stack, depending on at what point the XCMD is called. This is the second conflict in one week I've had with Gatekeeper Aid, so I'm removing it and going with Disinfectant init... -Ralph