Somehow, some users are ending up with a single rogue 001_KSPe.dll in their installations, this DLLs freaks out because it can't find its companions and freeze.
I just don't know why this thing is being left alone - I coded 000_KSPe.dll exactly to prevent this from happening. You remove the 000_KSPe directory, it assumes the user wants a deinstal and gets rid of 001_KSPe.dll and from itself in the process.
So the only (known) way for this to happen is to
- Someone manually installs
001_KSPe.dll and not anything else
- Frankly? This would be nuts. Why someone/something would do that?
- Someone is manually deleting
000_KSPe and 000_KSPe.dll, but lefting 001_KSPe.dll
- Again, why someone/something would do that? Anyone willing to get rid of KSPe would delete all DLLs, right?
So I'm in the dark about this problem. It's a use case I didn't had foreseen? It's something the user is doing that I just can't fathom?
Last occurrence: #17 (comment)
Player log: Player.log
Somehow, some users are ending up with a single rogue
001_KSPe.dllin their installations, this DLLs freaks out because it can't find its companions and freeze.I just don't know why this thing is being left alone - I coded
000_KSPe.dllexactly to prevent this from happening. You remove the000_KSPedirectory, it assumes the user wants a deinstal and gets rid of001_KSPe.dlland from itself in the process.So the only (known) way for this to happen is to
001_KSPe.dlland not anything else000_KSPeand000_KSPe.dll, but lefting001_KSPe.dllSo I'm in the dark about this problem. It's a use case I didn't had foreseen? It's something the user is doing that I just can't fathom?
Last occurrence: #17 (comment)
Player log: Player.log