permissions on files

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

I have 2 HDD's one is just for backup purposes (Z:)
Every now and then i copy files from Drive C: to Drive Z:
But... trying to overwrite some files on Z: is failing
if i pick a dir on Z: and look at properties the ReadOnly is shadowed and
checked. I have gone and set full control on all security parameters,
applied it to all child objects and on and on and on. No matter what
I do the attributes dont change. What is going on? Why do i have to
thrash so badly just to copy some files out to Z:
I can delete and even rename the files i cant overwrite! How do i fix this?
Its like having a "write once HDD"!
Thanks
Eric
 
pip22 said:
The 'properties' of folders (they are called folders in xp -- not
directories any more!) which you describe is normal, and is often
misunderstood. You cannot have 'read only' folders , and what you see
is actually the 'read only' option in it's disabled or unavailable form
where folders are concerned. There is a square block inside the 'read
only' option which means it's not available. You can put a tick in
there if you want, but if you close the properties box and then re-open
it, you'll see the option has been disabled again. 'Read Only' is for
files, not folders.

Are you sure the files you are trying to overwrite are not set to read
only?
Yes, the files are not marked RO but when i try to overwrite them with newer
versions i get access denied errors "you do not have permission to
overwrite file file55.txt" or something to that effect. I can rename it,
delete it etc but i cant copy-overwrite it. Does windows use the source
files owner to determine the permissions? Shouldnt an adminstrator on the
box have total rights? The files were created by cygwin originally (I'm
doing a backup of a bunch of things for safety to a separate HDD on the
same system)
Thanks,
Eric
 
Does windows use the source
files owner to determine the permissions?

No. Ownership and Security rights are different. But the owner usually has access else they wouldn't have been able to create it. Mostly security is inheirited from the folder or that folder's parent folder.

Shouldnt an adminstrator on the
box have total rights?

No. But the admin can take ownership (and thus leave an audit trail) and give themselves any permission they want.
 
David Candy said:
Does windows use the source
files owner to determine the permissions?

No. Ownership and Security rights are different. But the owner usually has
access else they wouldn't have been able to create it. Mostly security is
inheirited from the folder or that folder's parent folder.

Shouldnt an adminstrator on the
box have total rights?

No. But the admin can take ownership (and thus leave an audit trail) and
give themselves any permission they want.
I'm the only one on the box, why am i having such a hard time backing up
files to another HDD on the same system? What do i need to do to get
control? This is very annoying, I'm fighting with the system at every turn
trying to do something that should be easy.
Eric
 
Can you reformat the other drive. And don't change security on it. Thrashing is an interesting term - it conjours up images of faulty hard drives.

Is it always the same files.
 
David Candy said:
Can you reformat the other drive. And don't change security on it.
Thrashing is an interesting term - it conjours up images of faulty hard
drives.

Is it always the same files.
I probably could but I'd rather not. What i really need to do is to change
permissions on the entire system such that i can do what i want. I thought
being Administrator would do that but it doesnt.
Eric
 
There were 3 points in my post and you only addressed one.

1. Can you reformat the drive? You answered.
2. Thrashing is a term used to describe the sound of a faulty drive. You didn't address if you were using it in this context.
3. Is it always the same files.

The thread started off at Read Only which is irrelevent. I am still diagnosing and trying to confirm that permissions is your problem.

So describe what is happening, describe a specific instance.

From what you've said you've either configured permissions very precisely, which is rare and requires a user to decide to do that (and you'd remember). Or something else is happening.

It would be good if you can get a problem and keep that problem happening so tests can be run on that specific problem.
 
Back
Top