Path: utzoo!utgpu!attcan!uunet!cs.utexas.edu!wuarchive!psuvax1!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problems running THINK C 3.02 on a network
Message-ID: <3072@husc6.harvard.edu>
Date: 6 Nov 89 15:33:40 GMT
References: <89309.142523CXT105@PSUVM.BITNET>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 35

In article <89309.142523CXT105@PSUVM.BITNET> CXT105@PSUVM.BITNET (Christopher Tate) writes:
>I think I've traced a problem we're having with running C over our AppleShare
>network here, but I'd like to know the official word...

	I'm assuming that you paid for an equivalent number of copies, 
otherwise you're in violation of the license agreement...

>gives the error "can't open #include'd file," and puts the cursor at the top
>line of the file.  It does this even if the source code contains *no*
>#include statements.

	It sounds like the project has "Use <MacHeaders>", and the
MacHeaders file isn't in the THINK C tree. (In other words,  not related
to running on the network.)

	THINK C was not intended for shared use; it does modify itself
(when the settings are save for "New Projects"), and whenever a project 
document is opened, it is modified. This means that projects should not
be on readonly volumes, and if THINK C itself is on a readonly volume,
the "New Projects" settings should not be changed.

R.


~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

"There is no personal problem which cannot be solved by sufficient
application of high explosives."

~~~~~~~~~~~~~~~