2 replies to this topic

[JohnyGezony]

•  
• 0 warning points

Sent Today, 04:41 PM

Good Morning. I saw in previous threads that you preferred to be messaged directly regarding specific issues.


Ill start,


currently running windows 10.

Game is from retail DVD.

Currently patched to 1.9 across all attempts

 

Command and Conquer 3 w/o KW
 

 

Error log is as follows 

 C&C:Online Launcher Start -----
Game: C&C3
C&C3 Install Path: C:\Program Files (x86)\Electronic Arts\Command & Conquer 3\
Started game with: "CNC3.exe "
Caught CREATE_PROCESS_DEBUG_EVENT from C&C3. Detaching...
Found game.dat process. PID 8480
*** Starting CA public key patching routine ***
ERROR: Reading process memory failed. Error: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.

ERROR: Reading process memory failed. Error: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.

ERROR: CA public key differs from expected value. Not patching.

Initially upon install, I actually was

able to play several games without any bugs. No problems until I experienced connection trouble and then a crash that caused windows defender firewall to pop up. Unfortunately I didn't write down exactly what is said, but I opened it and made sure that it was allowing CNC3 and CNConline complete access.

This did not solved the problem.


So, I uninstalled everything. CNC3, CNConline. Reinstalled. Patched. Try to boot through launcher and received messages stating that the OS is not compatible with the game. Ok. so I go and try running game in compatibility mode (and launcher eventually). No avail. Tried all of the XP options, vista, and windows 7 and 8. Still same error message about needing 98se, windows 2000, or better.


Thank you for your time.

 

Edited by JohnyGezony, 15 March 2018 - 04:26 PM.

[JohnyGezony]

Also I just caught this error message,  CA public key matching routine failed

[ToxicShock]

OH.     Contrary to what I said in our PM conversation, I have sent you a PM with a solution which we're testing. If anyone else wants that solution to try, please make your own topic and post your error log.