3 ms·
Correct way to solve that would be adding a new privileged Windows API call which ignores file locks and lies to other applications.
by anticensor 8y ago
Correct way to solve that would be adding a new privileged Windows API call which ignores file locks and lies to other applications.
- acdha 8y agoIt’s been awhile but I thought that would complicate the way they load DLLs, not to mention the potential impact on legacy code which was doing something unsafe but would no doubt be spun as Microsoft unfairly breaking someone’s security kludge or dubious extension. Not something which can’t be handled but increasing the cost/risk perception. The big thing, though, is that they had a lost decade or so where the stack-ranking system heavily favored new features over improving existing code. Unless this was such a problem that it became a senior management priority I doubt anyone was jumping at touching it.