THINK C for A/UX?

[Matthew T. Russotto]

In article <1990Sep19.012057.5581 at bushido.uucp> mnowak%bushido.uucp at umich.edu (Michael A. Nowak) writes:
>I've started using A/UX 2.0 and have just started trying to work with THINK C
>in this environment (I've used THINK C extensively in the regular MacOS
>environment).  THINK C 4.0 exhibits some strange behavior under A/UX:
> 
>o  The debugger always complains that it is out of memory, despite changes in
>   the size of its Multifinder partition size.

That's better results than I have-- the debugger merely crashes.

>o  After running a project and returning to the THINK C environment, the whole
>   THINK C application just quits, with no explanation.  There's usually a
>   5 to 10 second period between returning from the run and the exit where
>   THINK C appears to run preoperly.

Is this with or without the debugger?  I've had no problems running without
the debugger.

--
Matthew T. Russotto	russotto at eng.umd.edu	russotto at wam.umd.edu
      .sig under construction, like the rest of this campus.