Hex codes from ToolBoks

[fys]

Any clue why hex-editing anything in the .exe would show a 0xc0000142 error? Is it possible that the .exe checks it's own hash at startup or something?

 

I've never hex-edited anything in the exe so far. The best alternative besides a modpatcher is using ResEdit and insert your DefaultGameCore.ini and DefaultLoadouts.ini content in XComGame.exe.

 

DGC.ini goes to 10\1020. Right-click on 1020 and open with plain text. Then you should see the familiar lines of the DGC.ini. Delete anything and copy your own DGC content there.

DL.ini goes to 10\1040. Same procedure.

Save and have fun!

Edited August 30, 2013 by fys

[ShEsHy]

I've never hex-edited anything in the exe so far. The best alternative besides a modpatcher is using ResEdit and insert your DefaultGameCore.ini and DefaultLoadouts.ini content in XComGame.exe.

 

DGC.ini goes to 10\1020. Right-click on 1020 and open with plain text. Then you should see the familiar lines of the DGC.ini. Delete anything and copy your own DGC content there.

DL.ini goes to 10\1040. Same procedure.

Save and have fun!

 

I'm trying to use these techniques: http://wiki.tesnexus.com/index.php/DefaultGameCore.ini_settings_-_XCOM:EU_2012#Recent_Discoveries (Disabling hash checks and Enabling INI loading), so I can bypass large edits to the .exe, but even the smallest edit (hex or otherwise, anything that changes the .exe in any way) causes the 0xc0000142 error upon launch.

And just to clarify, if I use my backup original .exe, the game launches and works.

Edited August 30, 2013 by ShEsHy

[Krazyguy75]

Are adding extra bytes or just replacing existing values?

[ShEsHy]

Replacing (mainly the "x" in xcom with "c").

[dubiousintent]

Have you followed the guidance in 'Installing Games on Windows Vista+' and 'Steam and Mods'? Did you include the 'RunAs Administrator' option when using the hex editor? (Some people has had this error when using ToolBoks on the game EXE without that.)

 

If it's none of the above, then we need something else in the way of detail to go on. Have you checked the Windows Event Viewer 'Applications log' to see which is the 'faulting module', as a for instance? What OS version, where is Steam located, what patch level is the game at, etc.

 

-Dubious-

[ShEsHy]

I never installed games under Program Files in the first place, so that's not an issue (always use D:\ partition, installed Steam & Origin there aswell).

Event Viewer listed nothing under the Application (or any other) log, but under System I found: "Application popup: XComGame.exe - Application Error : The application was unable to start correctly (0xc0000142). Click OK to close the application."

Win7 Ultimate SP1 x64, Steam is installed on D:\, game is up to date (update 4 IIRC), reason for modding .exe is trying to manually add Warspace Extension 1.75 (heavily modded by myself)

 

I didn't consider that the hex editor (HxD Hex Editor) could be at fault, will give that a try and edit this post wen I get the results.

 

*edit*

Tried running HxD as admin and got the same result when running the .exe.

 

Close to giving up now, will probably wait for EW and an then try again :(.

Edited August 30, 2013 by ShEsHy

[dubiousintent]

Still sounds like either the hash check or 'phone home' ( i.e. the 'hosts' file hack is absent or not functional) is causing the modified EXE to be detected as 'corrupt'. If the game is installed outside of the 'Program Files' tree, then the OS won't be trying to protect itself from changes, which again suggests it's Steam or internal EXE checks complaining.

 

You might try applying the second 'difference' patch (dated 20130815 in the filename) from EXEPatcher to a vanilla EXE and see if that will enable it to launch. Shouldn't be doing anything different than what you are attempting, but since that isn't working any alternative is worth a try. There is always the possibility that you are mistakenly modifying the wrong location.

 

Get the basic 'ini loading' and 'disable hash checks' hacks functioning and the game still launching first. Then progress to adding mods. Don't try to do everything at once, especially with your own tweaks to a mod by someone else. One mistake can crash the game with no clue as to why.

 

-Dubious-

[ShEsHy]

Tried it while offline completely and still got the error. Tried EXEPatcher, same result.

That's how I've been trying it for this whole time; first remove the checks and enable loading the.ini, then mod the game. So I actually haven't even gotten to modding the game yet, since I have to edit the .exe first.

[dubiousintent]

Whelp, I'm stumped. We know you can mod the EXE and still get the game to launch, if you have it prevented from checking the file integrity back with Steam. Other than that, the only known reason for it to assume the file is corrupt is because of a bad hex change which does make it corrupt. So, absent any other information, I can only think to suggest a complete removal and re-install of XCOM from Steam. But that is pure desperation.

 

Sorry not to be of more help.

 

-Dubious-

[ShEsHy]

Well, guess I'll just wait for EW and try again then (hopefully it'll make some changes to the .exe), don't really have the will to reinstall, not after all that it's put me through.

I don't know how much more help you could've offered (thank you very much for that, by the way), so no need to apologise.