Combat Arms -Bad image.exe

Alright guys, i think that older hacks that are patched and use a different structure method will result in bad widows image file. Atm this crypter only works with Flameswor10's hack. If you get a bad image file error the most likely result is that the hack is patched in CA since my encryption is built to work with the most recent hack structure of hooking CA. That being said if you get a bad windows image file with Flameswor10's hack then contact me. Also, Engine.exe is the one outputting the error, not windows. How do i know this? My Build 3 encrypted dlls would not run with Engine due to a bad windows image error everytime it was injected, the test dll i was using worked fine in my d3d test environment but wouldn't work in CA due to a bad image file, so the dll files work it's just engine.exe blocks them if it picks up a certain structure or something

- Open PerX Injector.
- In the 'What to Inject' bar, type in the process name (Engine.exe).
- Click on 'Automatically' for 'How to Inject'.
- Click 'Browse' to select the .dll file that's wanted to be injected.
- Run Combat Arms, and PerX should inject Automatically.
* Before you download PerX, turn off your Firewall/Anti-Virus Programs.
* If on Vista, run PerX 'as admin'.