Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!sparc1!rolf
From: rolf@sparc1
Newsgroups: comp.sys.mac.programmer
Subject: Re: Weird Think C problems
Message-ID: <1990Aug14.131735.21771@ux1.cso.uiuc.edu>
Date: 14 Aug 90 13:17:35 GMT
References: <1990Aug14.003350.2055@vaxa.cc.uwa.oz.au>
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 21

n_hays@vaxa.cc.uwa.oz.au writes:

>"4. Problem INITs

>Several INITs wreak havoc with the THINK Pascal debugging environment,
>usually because they bottleneck the Get
>in a non-standard fashion. INITs to avoid include Superclock, MacroMaker,
>Automac III, Masterstrokes, and TOM (Tear Off Menus). Also, if you are
>using a Radius TPD of FPD monitor, don't use the INIT software provided.
>The monitors work fine without the INITs and the INITs misbehave with
>THINK Pascal."

>As I said before this applies to Think Pascal, and I am only assuming that
>it may also apply to Think C. Also from my limited experience it is 

   I have a Radius FPD, and have never had any trouble with Think C 
(versions 3.0,3.02,3.04,4.0,4.2) using the inits that came with it.

--

Rolf Wilson   Illinois State Geological Survey   rolf@sparc1.isgs.uiuc.edu