Path: utzoo!attcan!uunet!husc6!bloom-beacon!bu-cs!dartvax!eleazar.dartmouth.edu!ack
From: ack@eleazar.dartmouth.edu (Andy J. Williams)
Newsgroups: comp.sys.mac
Subject: Re: I just thrashed my Hard Disk!
Message-ID: <8939@dartvax.Dartmouth.EDU>
Date: 17 Jun 88 14:57:38 GMT
References: <3599@okstate.UUCP> <8890@dartvax.Dartmouth.EDU> <6549@cup.portal.com>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: ack@eleazar.dartmouth.edu (Andy J. Williams)
Distribution: na
Organization: Kiewit Computation Center, Dartmouth College
Lines: 25

In article <6549@cup.portal.com> Tim_M_Dierks@cup.portal.com writes:

>I was under the impression that it was [ok, well, not impossible, but difficult]
>to corrupt your project or Lightspeed C while your program is running, because
>neither one of them is resident in memory at the time- your program gets
>compiled,
>and the _Launch trap is used to run it.  Because it gets sublaunched, it returns
>to Lightspeed C when it's done.

>back out, it should be really hard to corrupt your code for a second run.
>(Blowing
>the system away is an entirely different matter.)

That is what I meant... I didn't mean corrupting the code, I have never seen
that, I meant corrupting the RAM, the system... all the fun stuff that keeps
your mac up and running without a glich.  Corrupt it, and who knows what
it'll do... usually system error/macsbugs.  But every so often...

-ajw


Andy J. Williams '90   |Ack Systems: ack@eleazar.dartmouth.edu|   _   /|
Software Development   +--------------------------------------+   \`o_O' ACK!
Kiewit Computation Ctr |Hello. Set $NAME='Iinigo Montoya' You |     ( )  /
Dartmouth College      |kill -9 my process.  Prepare to vi.   |      U