oldStatesman
Cybernaut
I'm not sure I understand you - are you saying the ~e0005.exe is part of the issues or not? Thanks for the clarification.Harkonnen said:There is one more thing to blame - that ~e0005.exe process. Macrovision say about some memory protection in their recent Safedisk release, so that no "hacked" can read the code... Probably it's theirs memory works (BTW I found NOCD solution the same night the game arrived to me, 27th october). Wrote nothing, just searched the web... so Macrovision probably provides more trouble than does any really working protection. At best it doesn't affect anything, at worst it is the fragmenter.
Also, when I VirtualAlloc'ed too much for my own needs, DirectX renderer failed during initialization like in those ATi drivers issue.
BTW, I just posted a thread asking for feedback from the Beta testers on this part at almost the same time you posted this - I had Deja-vu when I read your post...we are reading minds!
http://forums.civfanatics.com/showthread.php?t=139346
I hope that the Beta Testers can provide insight - if the game worked with no CTD's or excessive fragmentation on the last Beta build without the cp, then the cp scheme may be a big suspect in hunting down the issue.