>>>Explicitly give yourself the rights, even if you're already the owner. Works elsewhere, dunno about the parts of disk owned by m$.
>>
>>Perfect idea to undermine system security.
>
>System? It's the effing windowses we're talking about.
>
>> Never do that.
>
>What, open the folder properties dialog, add yourself as a user, give yourself full rights? That's not hacking, that's widely open to the user. C'mon, the so-called system allows you to give yourself the rights manually through the dialog, but doesn't give them automagically when you, logged in as yourself, create the folder. I guess about 2% of the cost of Windowses goes to the heavy security cost, which is fully awake 24/7, watching that no bit of logic sneaks in.
>
>>Solve the problem.
>
>I did. Switched to Linux five years ago :).
>
>> It's solvable the right way since, what, W2K? 21 odd years?
>
>If so, how do you explain that the solution is not widely known, but instead, among the 60 of us regulars here, the question occurs 3-4 times a year? Even better, if there's a solution since 20 years ago, why is the problem still there in each new version, and solution is not?
>
>Just for curiosity's sake, what's the right way, why is it right, and why is the above wrong?
Come on. if you work in Linux like that, you open up so many problems, you wouldn't talk about.
To many people, old school as the common VFP guy, simple install aside the normal file structure. Because it's more simple. M$ at those days where unable to do the right steps in the early 20s (ok, it was visible late 90s) Like the just-copy-dll-next-to-the-exe installation style.
This is so wrong all the time. We left DOS ages ago. It was wrong in Win95 and it still is. Anybody insisting in it has slept the last two decades on basic OS requirements.
All I say is, do it right, not kludgey.
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord
Weeks of programming can save you hours of planning.
OffThere is no place like [::1]