Yes, OE = Operator Error. Using external disks without a fixed drive designation, not letting .PEK file creation finish, using unsuitable material, using media cache files on the wrong disk, using anti-something while editing, using a below spec disk setup, not turning off indexing, and a whole lot of other things, that an Operator should not do, so in my terminology that is OE.

I guess I have to start include a disclaimer with every single post or post reply I make: "Harm Millaard, please do not bother answering my questions or respond to anything I post in any way or manner"

You, sir, are alway condensending and never helpfull. Not a single time have you brought anything youseful into a single discussion I have ever been a part of. Do you not understand that you are not the only one who has ability to read the owner's manual or research on the internet? Do you not understand that one usually comes here aftert all other resorces to find the answer were explored? Do you not understand that one has the ability to run a search on adobe forums and one posts only after all other suggestions offered in the posts that were turned up by a search did not work?

Why do you have to fill adobe forums with a static? If you have nothing constructive to say about the post in question, please don't.

After doing some investigation and research it seems that the fault is not with Adobe Software (it still could be) but rather an OS and the way it handles permissions.

Windows 7, 64-bit seems to ignore any and all permissions and policies settings for the files and folders. It does it in a peculiar way. While it doesn't seem to prohibit writing to a folder that it marks as a read only (and won't let you change it) it makes it look as such to the apps that are trying to do this writing. Even as the new peak files are written the Adobe Premiere Pro does not seem to realize that.

Two things were done to remedy the situation:

Making Adobe Premiere Pro run as administrator (why on earth do I have explicitly make it so when my account is an Administrator account is beyond me);

Downloading and installing system registry record that allows one to take the ownership of a file or a folder (an option appears in the right-click context menu when you right click on a folder or a file) which allows one to remove "CREATOR OWNER" as a user name from the permissions in a security tab of the folder properties and also to actually enable full rights to one's user account that will not go away after clicking apply.

Problem is solved!

PS; have no idea how to fix similar problem people have on Mac Os, sorry.