[rsaxvc]

Everyone else has mentioned the easy part - replacing the function entry with "return not money"

The hard part is finding where that is. One approach is to start with the error string - find it in the file and put a memory-read breakpoint on it in the debugger. Trigger the error and capture the call stack - start working up the chain until you identify why that text was read, either the failure directly or a message passed to that thread - if it's a message, find what sent it and why.

[Double_a_92]

> start with the error string - find it in the file

This has never ever worked for me, unless it was some prepared example. There just never are any meaningful strings in the EXE.

[flatiron]

did you check DLLs?

[ottello]

I'm trying to disassemble photoshop CS4 wish me good luck because it seems they pretty hide it