Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ucdavis!pollux!vmrad
From: vmrad@pollux (Bernard Littau)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Rich, please help!
Keywords: THINK C 4.0 problems
Message-ID: <6930@ucdavis.ucdavis.edu>
Date: 5 Mar 90 23:49:56 GMT
References: <371@fornax.UUCP> <1969@husc6.harvard.edu>
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: vmrad@pollux (Bernard Littau)
Distribution: na
Organization: University of California, Davis
Lines: 27

In article <1969@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes:
[lots of stuff deleted]
>>As well, THINK C has a high probability of causing an application lauch
>>immediately after THINK C has been quit, to crash.  This seems to happen
>>about 40% of the time.
>
>	Is this something recent, or has it been happening ever since you
>installed THINK C 4.0, or upgraded it? The only possiblilities I can think
>of are that your ImageWriter (I assume you're using an Image Writer) 
>driver is smashed, or that your copy of THINK C is smashed; restoring
>one or both from the distribution disk may clear up the problem...

I have had a similar problem.  I have traced it to some interaction
between On Cue 1.3 and Think C 4.0.  When I launch Think C 4.0 with On
Cue 1.3, and then do a run of a C program under multifinder, I often
crash.  Crash in this case is beep repeatedly until I get tired and
manually reboot.  

As a matter of habit I just avoid starting Think C 4.0 via On Cue, but
I would much rather have them work with each other.

Anyone have any thoughts of suggestions?

Bernard Littau    VM Radiological Sciences        Telephone: (916) 752-4014
                  School of Veterinary Medicine   Internet:  vmrad@ucdavis.edu
                  University of California        BITNET:    vmrad@ucdavis
                  Davis, CA 95616                 UUCP: ucbvax!ucdavis!vmrad