Using Access in an Obeyfile to Prevent Files Being OverWritten

[Richard Ashbery]

To prevent many files being overwritten I can select them and then set
Access > Protected using the filer.

Is it possible to do the same for multiple files using the Access
command in an Obeyfile? What is the syntax please?

Regards

Richard

[Tony Moore]

*Access

*Access changes the attributes of all objects matching the wildcard
specification. These attributes control whether you can run, read
from, write to and delete a file.

Attributes are:

L Lock object against deletion by any user
W Write permission for you
R Read permission for you
/ Separator between your permissions and the public‘s
W Write permission for the public (on a network)
R Read permission for the public (on a network)

Syntax: *Access <object_spec> [<attributes>]

Tony

[Richard Ashbery]

In article <45a59fef52.old_coaster@old_coaster.yahoo.co.uk>, Tony

Help Access has already given me that information but I need to know
how to apply lock (L) to a group of files. I can do it for a single
file with no problems (*Access <path of myfile> L). Imagine I have
twenty files all with different filenames and I want to prevent them
being deleted so my question is how do I write the command? I could
write the command twenty times but there must be a simpler way that
doesn't require a programming solution.

Help Access talks about objects matching the wildcard specification.
What does this mean?

Richard

[John Williams (News)]

In article <52efa3b3...@invalid.addr.uk>,

Richard Ashbery <bas...@invalid.addr.uk> wrote:

> Help Access talks about objects matching the wildcard specification.
> What does this mean?

Path to the directory followed by a .* to represent the filename(s).

John

--
John Williams, Brittany, Northern France - no attachments to these addresses!
Non-RISC OS posters change user to johnrwilliams or put 'risc' in subject!
Who is John Williams? http://petit.four.free.fr/picindex/author/

[Steve Fryatt]

On 16 Nov, Richard Ashbery wrote in message
<52efa3b3...@invalid.addr.uk>:

> Help Access has already given me that information but I need to know how
> to apply lock (L) to a group of files. I can do it for a single file with
> no problems (*Access <path of myfile> L). Imagine I have twenty files all
> with different filenames and I want to prevent them being deleted so my
> question is how do I write the command? I could write the command twenty
> times but there must be a simpler way that doesn't require a programming
> solution.

That will depend on what the filenames are.

> Help Access talks about objects matching the wildcard specification. What
> does this mean?

"*Access */zip L" would lock all of the files whose names end /zip in the
current folder.

"*Access * L" would do all of the files in a folder.

The exact form will depend on your files.

--
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/

[Richard Ashbery]

In article <mpro.mdlg2603...@stevefryatt.org.uk>, Steve

That's it - the secret is in the single * the wildcard symbol to
encompass all files. Thank you John and Steve for making this crystal
clear.

Richard

[Jeremy Nicoll - news posts]

Beware if you're using VRPC & HostFS. You can issue *Access commands, or
set Lock etc via the Filer, but HostFS does not implement the actual lock
flags. RO won't tell you that the file hasn't actually been locked, and it
will be accidentally deletable.

Unless VA have fixed this (which I doubt since there's been no announcement
of that) the only workaround as far as I know is to put files that must be
Locked etc onto an ADFS drive.

--
Jeremy C B Nicoll - my opinions are my own.

Email sent to my from-address will be deleted. Instead, please reply
to newsre...@wingsandbeaks.org.uk replacing "aaa" by "284".

[Tony Moore]

On 17 Nov 2012, Jeremy Nicoll - news posts

<jn.nntp....@wingsandbeaks.org.uk> wrote:
> Richard Ashbery <bas...@invalid.addr.uk> wrote:
>
> > To prevent many files being overwritten I can select them and then
> > set Access > Protected using the filer.
> >
> > Is it possible to do the same for multiple files using the Access
> > command in an Obeyfile? What is the syntax please?
>
> Beware if you're using VRPC & HostFS. You can issue *Access commands,
> or set Lock etc via the Filer, but HostFS does not implement the
> actual lock flags.

The same goes for RPCEmu 0.8.9, and HostFS.

Tony

[jgharston]

Steve Fryatt wrote:
> "*Access */zip L" would lock all of the files whose names end /zip in the
> current folder.

And would also remove any read access. That's ok if you really really
want to set the file to have absolutely no access at all, but if you
want
to be able to read them you need to include 'R', ie *Access */zip LR

JGH

[Russell Hafter News]

In article
<2c110ff052.old_coaster@old_coaster.yahoo.co.uk>, Tony

I found last week that to get Pluto working OK in RPCEmu and
Windows 7 I first had to set Windows permissions to all the
files in Pluto in Host FS to be completely free and open,
then start RPCEmu and look at the access to the files:
Nothing was set in either the locked or the unlocked
columns. Managed to to set everything to unlocked and I
could then repair/compact and get Pluto working.

None of this necessary on Win XP.

Have not used *Access since I sold my my BBC B.

--
Russell
http://www.russell-hafter-holidays.co.uk
Russell Hafter Holidays E-mail to enquiries at our domain
Need a hotel? <http://www.hrs.com/?client=en__blue&customerId=416873103>

[Harriet Bazley]

On 18 Nov 2012 as I do recall,

Otherwise you get errors every time you try to scan the directory with
Textseek, for example.... ask me how I know! The idea of a file locked
against accidental re-reading is fine in theory, but none too
convenient in practice.

--
Harriet Bazley == Loyaulte me lie ==

"An American is a man with two arms and four wheels".