JON@wehi.dn.mu.oz (Jon Eaves) (08/09/90)
G'day Net,
Here's a beauty I had happen to me the other day. Using THINK C 3.01
upgraded to 3.02 using the updater for 6-8 months no problems. Yesterday
I went home, fired up the mac, started modifying a project by opening a new
file to enter functions. I typed in 10-12 small functions and used Check
Syntax to find my spelling mistakes :-). I get 'Syntax error' on line 1.
The line was; int PopUp_createMenu(p,l,t,r,b). Hmm, nothing looks to wierd
there. I changed this to abc(), and still got a 'Syntax error'.
Hmm, something funny is going on here. There are no include files so that
can be discounted. I chucked in CMarker to have a look at the function
names, more as a whim than anything else. The first function came up as
W`abc()
Very Unusual, no wonder there was a syntax error. I reinstalled Think C.
No fix. I reinstalled 6.04 -> No fix. I installed 6.03 that fixed it.
6.03 doesn't have the 6-7 DA's that I was using so that could be a problem.
The DA's have been in there for as long as I can remember with no problems.
Think C was creating windows with junks characters at the start of the window.
These characters were invisible and non-removeable. What's the answer
people?
My full config is: Platinum Mac Plus, 67Mb CMS drive, 2.5Mb RAM. A couple
of INIT's (SuperClock,Pyro!,OnCue, INIT CDev, all well behaved stuff)
I'm running UniFinder and System 6.04 (when the erros occurred) and now
have dropped back to 6.03.
I'm not planning to try anything until I've finished the contract I'm
currently working on. Everything is working fine now, but I have some nagging
doubts.
PS Everything is Virus free, I used Disinfectant to check my system and it
came up clean.
aTdHvAaNnKcSe
--
--------------------------------------------------------------------------------
Jon Eaves
"SAFE!!, obviously this is a strange new meaning of the
word safe that I was previously unaware of." Arthur Dent.
ACSnet ( jon@wehi.dn.mu.oz )
UUCP ( uunet!munnari!wehi.dn.mu.oz!jon )
Internet ( jon%wehi.dn.mu.oz@uunet.uu.net )
--------------------------------------------------------------------------------n_hays@vaxa.cc.uwa.oz.au (08/11/90)
In article <11088@wehi.dn.mu.oz>, JON@wehi.dn.mu.oz (Jon Eaves) writes > > My full config is: Platinum Mac Plus, 67Mb CMS drive, 2.5Mb RAM. A couple > of INIT's (SuperClock,Pyro!,OnCue, INIT CDev, all well behaved stuff) > I'm running UniFinder and System 6.04 (when the erros occurred) and now > have dropped back I don't know what Think C is like but the manual to Think Pascal 3.0 warns that Superclock "plays havoc" with the Think debugging environment.
oster@well.sf.ca.us (David Phillip Oster) (08/13/90)
>SuperClock plays hell with the debugging environment
My INIT Menu Clock, (which I wrote in '85!) still works with everything,
unless you color your menu bar to some color other than white, or are using a
24-bit per pixel display for your menu bar.
--
-- David Phillip Oster - Note new signature. Old one has gone Bye Bye.
-- oster@well.sf.ca.us = {backbone}!well!ostern_hays@vaxa.cc.uwa.oz.au (08/13/90)
>From: SMTP%"jackiw@cs.swarthmore.edu" >To: n_hays@vaxa.cc.uwa.oz.au >?CC: >Subj: Re: Weird THINK C problems >Date: Mon, 13 Aug 90 11:30:21 EDT >From: jackiw@cs.swarthmore.edu (Nick Jack: <9008131530.AA02707@swatsun.cs.swarthmore.edu> >To: n_hays@vaxa.cc.uwa.oz.au >Subject: Re: Weird THINK C problems >Newsgroups: comp.sys.mac.programmer,aus.mac >In-Reply-To: <1990Aug11.225521.2051@vaxa.cc.uwa.oz.au> >References: <11088@wehi.dn.mu.oz> >Organization: Visual Geometry Project, Swarthmore College, PA >Can you send a page reference to this warning about SuperClock in >the manual? I'm intrigued, but I can't finks. >-Nick Sorry my limited account doesn't let me send mail off campus so I have to reply by posting. Actually the warning about Superclock is not in the manual but in the release notes to Think Pascal 3. It took me a while to find it again. The warning in full reads: "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 evident that Superclock does not INVARIABcal. So it may be possible to operate for some time before hitting a situation in which an incompatibility becomes evident. Hope this helps, Neale Hays
rolf@sparc1 (08/14/90)
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