I have come across several folders on different drives that have a Padlock symbol on the folder, I have tried unsuccessfully to remove this and allow all users on the network to view or alter the contents within. Any help or suggestions to remedy this would be most appreciated.
P.S. This is an I7 chipped motherboard with Windows 7 Ultimate.
Some of these folders are system locks and cannot be removed. Interestingly enough, the documents folder is one of those, however, you'll also find
that there is another one that allows access to it anyway.
I'm assuming that you are familiar with setting up file shares. You'll also need to set up the permissions tab too or network users will not have any joy. Especially if they are not using W7.
A useful tool that works on some files is take ownership, if it's just locked by an unruly program or another user it works quite well. It also adds to the right click menu so you don't have to look for it. Read the blurb before you download, just so you understand what it does, and how.
That's the best way. But, there's an easier one, if it still works...
Create a random directory, somewhere (Desktop?) and copy the files to that directory.
Move them back to where they were (Confirm overwrite) and you'll find that the padlock has vanished...
Dear Forum, Many thanks for your excellent suggestions, I have tried both of these and they both work and has cured my problem. Saved these for future
Pleased to hear that we haven't lost "it". Our expertise is less called upon these days.
In the recent past I attempted to read up on why in Windows Explorer a few select folders had a padlock symbol next to the folder name.
As a non-tech home user, I will NOT attempt to explain the function/purpose/etc. of Placeholders, but they are a deliberate effort by MS to protect the OS from inadvertent, etc., damage. The padlock, even when the end user has his folder files options set to "show hidden files/folders/drives" were deliberately created to prevent access.
My view is that an attempt to defeat the purpose of a padlocked file/folder/drive is playing with fire re the negative consequences unless the end user has a considerable degree of geek skill sets.
Typically, you are correct, Jack, the problem often is that Windoze decides that a folder needs to be "protected" for it's own nefarious purposes even when it's your own documents.
A Google type search will turn up a HUGE amount of hits re the word "placeholders"; many, if not most of the hits, will contain, in part, a
description of what their purpose is. One of the most common SINGLE words to describe placeholders is "alias". I must admit to having considerable
difficulty in envisioning (comprehending) the word 'alias' as describing an OS function, and apparently a VERY important one. One minor piece of
information is that the use of placeholders goes all the way back to UNIX systems decades ago (at this point). Windows, speaking of bastardized
metaphors, is a child (perhaps stepchild) of UNIX.
Perhaps there is someone among the forum members who have a great command of the language who can attempt to articulate, I. e., explain placeholders for the benefit of the rest of the forum members (perhaps a NEW topic should be created for anyone who attempts that). Please this this reply an invitation for someone to do so.
On the good old Amiga, you could make assigns, to point to all sorts of places.
If you had a directory that you used a lot, you could assign a name to it.
For example, if you had a directory called "Stuff", on your DH1: drive, inside a subdirectory named "Docs", you could set up an assign, so that it was easier to access.
Assign Stuff: DH1: Docs/stuff. (Damn those smiley codes)
You can do something similar with Windoze, except for the fact that you can't use words, for drives.
For instance, I access AppData, quite a bit, to remove crap that uninstallers leave behind. (You'd be surprised how much they leave, both there and in ProgramData).
So, I have an autoexec.bat which has this line:
subst.exe X: "C:UsersKatAppData"
To access the directory, I just need to access drive X:.
On the Amiga, an alias was a way to shorten commands, for use in DOS. If you wanted to use "del", instead of "delete", for example, you could set the alias, thus:
Alias Del Delete
But, I digress...
I recall reading here that Karl loved his Amiga, back in the day.
I had a couple of Atari's
I use an Amiga emulator, now. If I want to do anything DOS, it's better than using MSDOS, in many ways.
I was playing with DOS in a virtualbox only on the weekend but could not seem to convince it that I needed access to a physical device to actually get
something to load! (I wanted to return to my dBase roots) In the end it was easier to set up DOS on a memory stick and just boot into that! I, then,
found how much I'd forgotten!
I was intending to write a quick and dirty database but realised that it would require more time to re-learn the command syntaxes than it would to make my excel spreadsheet work the way I wanted. I also experimented with MySQL, and gave up for similar reasons. Instead, the spreadsheet now sports a few UDFs that perform the task. Still a few bugs to iron out, but 'tis getting there.