Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!xylogics!transfer!lectroid!jjmhome!m2c!umvlsi!dime!dime.cs.umass.edu!nayeri From: nayeri@takahe.cs.umass.edu (Farshad Nayeri) Newsgroups: comp.sys.mac.hypercard Subject: Re: Self-Starting Demos Message-ID: Date: 8 Mar 90 00:57:28 GMT References: <16578@oregon.uoregon.edu> <14145@phoenix.Princeton.EDU> <10850@bsu-cs.bsu.edu> Sender: news@dime.cs.umass.edu Reply-To: Nayeri@cs.umass.edu Organization: Dept of Comp and Info Sci, Univ of Mass (Amherst) Lines: 26 In-reply-to: mithomas@bsu-cs.bsu.edu's message of 28 Feb 90 20:55:35 GMT With the original HyperCard, you could do this: Create a disk with just the System file, HyperCard, the Home stack, and the stack that you want to run. When the system starts up, it will open HyperCard and the Home stack. Now, go into the on openStack handler in the Home stack and have it go to your stack. As far as I could remember, you have to modify a resource in the System file to tell it that your startup appliaction is not Finder, but HyperCard. I did a stack that had to be standalone once, and to solve this problem, we did things a more tricky way (we were under time pressure.) System will run any file which has the name "Finder" in the same folder. So just rename HyperCard to "Finder" and put it in the same folder as the Home stack and the System file, and reboot. I think that the original hypercard disks worked the way they did because the System was modified. Anyone knows how to tell the system to look for a file different than the finder? -- Farshad Nayeri Graduate Student COINS Department University of Massachusetts