overulehost said:
yeah...
i think you are saying stuff about debugging tools
There are cracked windows files on the internet. Back when Windows 98 was the norm someone hacked regedit.exe (the windows registry editor) to fix a memory a leak, and at least reduce the effects of the reg-file size bug (have you heard of it? google search it)... also found in Windows ME. There was a game that I wanted to play without having to insert my original CD... I hacked the exe by decompiling it and pushing the memory in real time, and dumping the result (cracked.exe). I didn't distribute it or anything, as that would be a "crack".
The program I used for that is called "OllyDbg". It's very easy and simple to use, however it doesn't do anything automatically. You have to know exactly what you're searching for, and a very basic understanding of the assembly language. All it does is decomile the program so you can edit in memory as it runs, and then writes the patched .exe file if you make changes to the program. It used to have a home page at
http://home.t-online.de/home/Ollydbg, but I guess you'll just have to google-search for it.
If I was so inclined I could probably easily crack shareware to make it full version, etc... I haven't tried. If something in a game or program annoys me, I know I can change it and that's all I care about. Heck I had one game I changed the registry address at where it saves... very similar to the original problem (changing a hard drive save directory). Get ollydbg.
For very simple resource-hacking get "Resource Hacker" - it may be able to solve these problems. But often you don't find these things in resource string tables, and instead they're buried deep within the program code, which is when you need ollydbg.
