Alshiva wrote:
I prevented all of the .lock files from spawning, that is for sure. I created gimmick files replicating the name (just a random patch from here), and had Redaxle's petite patch in the data folder, named patch-A.MPQ. Still same error, however.
What I immediately noticed:
If there is a .lock file existing BEFORE WoW is launched, WoW will delete that file and replace it with the Blizzard .lock file. So if copied patch-A in this case and renamed it art.MPQ.lock, it would be deleted and replaced. The only reason I noticed this is because the file size went from 17.8 MB to 0 MB.
To prevent this, you can change permissions of who can access the file. I had SYSTEM set to Deny full control, and myself deny all but Modify and Full Control. This prevented the .lock files from being replaced.
I replaced ALL of the .lock files in the Data folder. Upon trying this, I started up WoW, could delete and move whatever I desired with my created files, suggesting they did not get loaded up by WoW. However, this also yielded the same result of the move before pointer error thing.
TL;DR
It didn't work.
That makes me want to believe that the issue(s) lie within the models themselves. I am starting to think that it is no longer an issue of "access denied," but more of an update they made to the models or the files themselves.
After all, the "file pointer" error message does not sound anything like "access denied." But then again someone can argue that it doesn't have to sound like it's not an access issue when it could be.
_________________
