I have some basic knowledge, I even found those strings in the debugger, but I am not sure on what to do logically then.
I assume I have to break where the game uses them, but what I do from there? MrMedic?
Thats exactly where I've gotten. I've found the strings for AcceptedKey (Among others which sound suspicious), and Medic just told me to get a better hex editor. So now I have the full version of hiew, but thats all. I really just need to know which byte to change in the AcceptedKey string. If its more complicated then that, at least let me know so I dont stare at the value thinking "...It could be any of these bytes. Any.. single... one."
edited out i posted the solution but then i thought about it ..lets see if they can come up with it themselves..
Maybe instead of stick-and-carroting us newbies around and always reminding us you have the answers we need, you could provide a step-by-step guide to the solution, complete with explainations of every step not so much to prevent mistakes, but to provide learning.
Rather like a teacher does in the classroom. For instance.
The byte 74 needs to be change to <this>. Why? Well, previously, byte 74 conducted <this action/mechanism>, and by changing it to <this>, we see that the executable instead activates <this>. This is called <insert term here>. You can find other examples of this at <insert link to information on the method used, maybe even a wikipedia entry on hexidecimal values>.
It's one thing to sit around and ask for a release without doing any work yourself, however, I'm more than willing to "do-it-myself", if I had the slightest idea of what I was doing. Reading up on executable/hex hacking isnt going to help me hack this particular executable. Maybe compile a key or index of the various values in arma.exe and put it in a .txt file for us newbies to use? That way we know exactly what we are looking for, and can experiment with the values to get varying results.