CXT105@PSUVM.BITNET (Christopher Tate) (11/06/89)
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...
When attempting to run THINK C 3.02 on an AppleShare network, it fails every
time a compilation is attempted. Regardless of the code being compiled, it
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.
Inspecting THINK C with ResEdit, I discovered that on the shared volume, the
"file protect" bit is set for every copy of the program. This is apparently
how the Center for Academic Computing prevents students from copying the
software available on the servers.
I'm looking for confirmation: is THINK C 3.02 unable to function properly
when the application itself is on a read-only volume *and* is protected?
Rich? The official word?
-------
Christopher Tate | "Voices leaking from a sad cafe....
| Smiling faces try to understand.
cxt105@psuvm.psu.edu | I saw a shadow touch a shadow's hand
{...}!psuvax1!psuvm.bitnet!cxt105 | On Bleeker Street."
cxt105@psuvm.bitnet | -- Simon & Garfunkleyahnke@vms.macc.wisc.edu (Ross Yahnke, MACC) (11/06/89)
In article <89309.142523CXT105@PSUVM.BITNET>, CXT105@PSUVM.BITNET (Christopher Tate) writes... -When attempting to run THINK C 3.02 on an AppleShare network, it fails every -time a compilation is attempted. Regardless of the code being compiled, it -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. Are you trying to include "MacHeaders" via a compiler option and is MacHeaders available, i.e., is it in the "Think C" folder? >>> Internet: yahnke@macc.wisc.edu <<< >>> Mille voix chuchottent <<c'est vrai>> <<<
siegel@endor.harvard.edu (Rich Siegel) (11/06/89)
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." ~~~~~~~~~~~~~~~