[softwarelist] Re: OPro error message
- From: Alan Adams <alan@xxxxxxxxxxxxxxxx>
- To: davidpilling@xxxxxxxxxxxxx
- Date: Wed, 16 Oct 2013 11:05:10 +0100
In message <539b736188Paul@xxxxxxxx>
Paul Sprangers <Paul@xxxxxxxx> wrote:
> In article <8f3c499b53.farmstay@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
> Bev & Ross McGuinness <farmstay@xxxxxxxxxxxxxxxx> wrote:
>> What would cause the the file to switch the setting to 'No' - there
>> are a dozen chapters, all being worked on concurrently, so why would
>> three of them suddenly become 'locked'? It attacks my sense of logic!
> ...as it attacks mine. I've never heard of such behaviour.
> Besides, as far as I know, setting filer access to 'No' doesn't necessarily
> mean that the file can't be opened, I think it just means that you won't be
> able to modify it.
> Anyhow, another cure may be more successful: save the file as DDL and load
> that file. You probably have to re-enter some settings in the view options,
> but in general this approach solves many problems - that's at least my
> experience.
> Kind regards,
> Paul Sprangers
I have some suspicions about what may be happening, but a quick test
here has proved inconclusive so far.
The files are stored on Windows, presumably accessed by LanMan98.
Windows permissions include an "owner" for a file, and sets of access
rules for the owner, for the Administrators group, for the user called
Administrator, and for SYSTEM. There may be others for other users,
and for the group called "authenticated users".
The access for each user is a combination of the access granted on the
file itself, and that on the parent directory.
When LanMan98 connects to a share it specifies a username and password
for the Windows user who is to be used for the connection. The access
granted is then determined by that for the user (including that for
any groups the user may belong to).
In my test, I connected using Alan as a username. Alan is a member of
the Administrators group. A file created on the Windows share gained
the ownership "administrators", i.e. the group. That group has full
control. "Users" and "Authenticated users" groups have modify.
Looking at the Access in RISC OS shows Owner read and write, public no
read and no write. Changes to these from RISC OS are ignored - i.e.
going back to the Access control shows the same public no access.
On Windows the permissions haven't changed. This may be because the
connection user already has full control.
To see the full story on Windows permissions you need to use the
Properties menu item on the file, then click security, which shows a
summary. Click the Advanced button. The Owner tab shows who the
Windows owner is, and the permissions tab shows the permissions for
each user, including the owner. Effective permissions will reveal just
how many items are rolled together to produce the summary. They fall
into a number of groups.
Some control access to a file. Some control access to a directory.
Some (applied to a directory) control the default permissions granted
to a file created within the directory. Others control the ability to
change the owner and permissions.
So, to go back to the original problem, my gut feeling is that some of
the files making up the document have different owners from others, or
different Windows permissions for the LanMan98 user making the
connection. I also suspect that for this to make a difference, the
username for LanMan98 will be different from the username logged into
Windows and opening the files using OproWin.
--
Alan Adams, from Northamptonshire
alan@xxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
To unsubscribe or subscribe goto: //www.freelists.org/list/davidpilling
Other related posts:
