Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!midway!ellis.uchicago.edu!lrm3
From: lrm3@ellis.uchicago.edu (Lawrence Reed Miller)
Newsgroups: comp.sys.mac.comm
Subject: Re: AppleShare/File protect bit
Message-ID: <1991May8.165839.16719@midway.uchicago.edu>
Date: 8 May 91 16:58:39 GMT
References: <1991May8.134939.8041@cc.curtin.edu.au>
Sender: news@midway.uchicago.edu (NewsMistress)
Organization: University of Chicago
Lines: 34

In article <1991May8.134939.8041@cc.curtin.edu.au> chooper@cc.curtin.edu.au (Todd Hooper) writes:
>I'm trying to set the 'file protect' bits on some applications on a standard
>AppleShare file server, to stop people simply dragging copies onto their own
>floppy disks.
>
>However, ResEdit 2.1 (under SSW 6.0.7) just won't let me do this - the button
>is activated ok but no cross appears in the box. This is when I am logged into
>the server as 'Administrator'.
>
>Am I barking up the wrong tree here?  What do I need to do to achieve this? It
>was simpler with AlisaShare, where you just run a program called ASCP!
>

To set copy protect files under AppleShare, you need to run the Administration
program.  Assuming that you installed the program when you originally set up
your AppleShare server, if your AppleShare server is up & running, just select
Administration from the Server menu on the machine running AppleShare.  Enter
your Admin key, and you will then be in the Administration program.  Select
File & Folder Info from the Folders menu, pick the file you want to copy protect
and click Get Info.  Then Click the Copy-Protected box and then Save.  Ta dah.
This is covered in the AppleShare manual (page 151, in mine, under the heading
"Copy-protecting a file").

I don't think that ResEdit will set the copy protect bit at all any more; I
think that MacTools still will.  In any event, there is no way to set the
protect bit from any machine other than the server itself (i.e. you _can't_ do
it to a remotely mounted AppleShare volume).  The Administration program is
the best way to go, though.

Note that AppleShare copy protection is not very strong; it is pretty trivial
to get around the protect bit.

Hope this helps,
Lawrence Miller