32BOBO32 Schreef:
-------------------------------------------------------
> OT: ZaZ any plan for CSM 2.0 release? :P
Plan, yes
Short term, no
On topic:
I'm surprised I don't see more reports on this. There are some flaws in the CSM system which can cause corruption if certain scenarios are met.
If you run Windows Defender (which runs by default from Vista and up), it's possible that Defender locks files.
CSM does check whether it can open a file for write access and from that moment, it assumes it can write.
It does catch errors and bails out when an error occurs so it can try again next time.
Defender can cause such error by locking file access suddenly and CSM bails out but that part of the code wasn't written with much attention as we were in XP era
There are 3 systems for file access in CSM: Swapping, Patching and Wadding
With the flaws in the design of the system in CSM, it's possible that the restore of a patch fails, but the restore of the swap continues and then the restore of the patch tries again, resulting in one big mess.
Real solution is me fixing the source and offer a new binary.
Temporary solution is setting your gp4 folder to an exclusion list of your AV or disabling the AV (such as Defender)
I'll see what I can do in the next few weeks (don't have much time)
I'd rather have a bottle in front of me than a frontal lobotomy