>Here's the scenario:
>
>- I create a folder
>- I copy an .exe and its .ini into it
>- Edit the .ini
>- Can't save it, access denied
>- Open the properties of the folder, add myself in the security tab and give myself full rights
>- Now I can save it OK.
>
>Why did the chicken cross the road? For security reasons.
>
>Why do I have to give myself the rights to a folder I just created, to edit a file I just copied into it?

I'd seen a similar weirdness under *nix -- and typically it's because something went wrong with the ownership (and typically the weirdness occurs when there's a problem with the group ownership rather than user -- using chown to change group ownership often quickly fixes the problem), or because of a problem in the umask, certain permission bits were forced to off upon creation (resulting situation where you were able to create it but you can't modify it afterwards). It could even more confusing if you're accessing this *nix machine from a Windows system through Samba -- the configuration through Windows may look OK, but a permission problem at the *nix level will cause a problem.