Newsgroups: rec.arts.int-fiction
Path: gmd.de!jvnc.net!yale.edu!news.yale.edu!yar.trincoll.edu!downes1-101.dynamic.trincoll.edu!rbryan
From: Russell L. Bryan <rbryan@Mail.trincoll.edu>
Subject: Re: IBM to Mac porting information for TADS authors
Message-ID: <1992Nov24.200503.20446@starbase.trincoll.edu>
X-Xxmessage-Id: <A737F5D60C013165@downes1-101.dynamic.trincoll.edu>
X-Xxdate: Tue, 24 Nov 92 20:08:06 GMT
Sender: usenet@starbase.trincoll.edu (SACM Usenet News)
Organization: Starving Writers of America (sole member)
X-Useragent: Nuntius v1.1.1d12
References: <1992Nov24.004310.9875@starbase.trincoll.edu>
Date: Tue, 24 Nov 1992 20:05:03 GMT
Lines: 41

In article <neilg.722628370@sfu.ca> Neil K. Guy, neilg@fraser.sfu.ca
writes:
> When you say that the 2.0 compiler has been crashing when you launch
>it... Do you mean that you double-click a TADS file from the Finder,
>or that you explicitly launch TADS Compiler 2.0 by double-clicking it?
>If the former it's possible that TADS 1.2 is actually being launched,
>and it's trying to open a file created with 2.0. If this is the case
>try making a backup of 1.2 onto a floppy and then trash any copies of
>it from your hard drive.

What happens is this :

With the compiler, I may try to compile something, and have the
compilation fail (usually because I forget to set version 1.2 compile
options).  So I'll set the options and then try to compile again. 
Usually, it will immediately crash, leaving me no way to shut down (or
reboot) short of manually shutting off the Macintosh.  Often, if I hit
the reset key to reboot, a portion of the program must STILL be in
memory, because it will crash before the finder comes up.  A truly cold
start is required.

With the Run-Time system, if I leave it idle for over an hour, I can
usually count on returning to either find myself unable to restore or
quit (and don't even TRY to save, because it will save OVER the .gam file
you are using at the time), or the computer will have dropped into
Macsbug while it was idle.  If everything goes fine with EITHER the
compiler or the run-time, I will often get a crash later for no apparent
reason, and this ONLY happens when I have used the aforementioned
applications.

I'm not entirely mac illiterate.  My guess is that there is a large
portion of memory which is not being deallocated when the programs are
through with them.  Either that, or it's running in memory which is best
left alone.

Of course, I could have a virus, as well -- lately the memory taken up by
the finder has been approaching 2.5 megs for no apparent reason.  I'm
going to check for this possibility before I go bothering Mike about it
-- I've been bugging him too much lately as it is.

-- Russ
