Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!midway!tartarus.uchicago.edu!tisue
From: tisue@tartarus.uchicago.edu (Seth Tisue)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Looking for XCMD/XCFN to eject disk and to shutdown
Message-ID: <1991Jan12.210640.2513@midway.uchicago.edu>
Date: 12 Jan 91 21:06:40 GMT
References: <2509@casbah.acns.nwu.edu> <47997@apple.Apple.COM>
Sender: news@midway.uchicago.edu (News Administrator)
Reply-To: tisue@tartarus.uchicago.edu (Seth Tisue)
Organization: U. Chicago Computer Science Dept.
Lines: 24

In article <47997@apple.Apple.COM> jkc@Apple.COM (John Kevin Calhoun) writes:
>
>In article <2509@casbah.acns.nwu.edu> matt@acns.nwu.edu (Matt Larson)
> writes:
>>               I would like to be able to shutdown the Mac from within
>>HyperCard.
>
>This is not a good thing to do.  Unfortunately, there's no way to guarantee,
>if you shut down the Macintosh from within HyperCard, that HyperCard will
>have written everything out to the disk that has to be written in order to
>keep the stack in a consistent state.  In other words, shutting down the
>Macintosh from within HyperCard is a common cause of stack corruption.

Comments:

1) Why couldn't a hypothetical ShutDown XCMD tell HyperCard that it needed
to finish cleaning house, so to speak?  i.e., have HC do whatever it does
before it quits to the Finder or opens another application.

2) I _have_ a ShutDown XCMD (which I got off one of the common library
stacks, don`t remember which) and have used it to shut off my Mac hundreds
of times and have never had any problem with stack corruption, which leads me
to believe that it does correctly take care of what needs taking care of.
Works in 2.0, too.