Path: utzoo!attcan!uunet!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!cxt105
From: CXT105@PSUVM.BITNET (Christopher Tate)
Newsgroups: comp.sys.mac.programmer
Subject: Problems running THINK C 3.02 on a network
Message-ID: <89309.142523CXT105@PSUVM.BITNET>
Date: 5 Nov 89 19:25:23 GMT
Organization: Penn State University
Lines: 24

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 & Garfunkle