vstrakh wrote on 2026-01-08, 10:24:
The Norton Disk Edit could only be used as a hex editor in this context.
So you'd guess if something is a cheat code, like maybe some text word standing out in the section clearly belonging to a code. Having experience with assembly you can see if something is a code or a data, even without disassembling it.
I used to just look for strange-looking words, without knowing if they were in a code or data section, for example "goobers" in Wolfenstein 3-D seems out-of-place. I'm not sure if I ever had success with that scheme though, given that often you need to hit some key sequence which isn't going to appear in ASCII.
Jonas-fr wrote on 2026-01-08, 09:11:
And while we're at it if anyone have info on how to discover cheats and make trainers for DOS games with the tools of the era just post there also, this is a general DOS/Win3x/Win9x cheat making/reverse engineering topic : )
I used to use "GAMETOOLS" ("G3X.EXE" might be a useful search term for it), which was basically a TSR debugger which included a feature where you could search memory for a byte or word that increased or decreased each time you popped the TSR up. If you were playing DOOM for example (not sure I ever actually used it on DOOM) you might pick up some bullets, tell the TSR that the value increased, then shoot, tell it the value decreased, etc. Each time you tell the TSR the value changed it, it will tell you how many locations in memory it narrowed the search down to. Sometimes it would say zero, and you'd have to try a different memory location size or something. Once you figure out where something is stored in memory, you could use the TSR to edit that location. Fortunately in DOS if you boot with the same configuration the same absolute memory addresses will normally be used every time you start the game.
It also comes with a program called "TSRCRACK", which I never tried using. It looks like a TSR which can be scripted to edit memory when certain conditions are true.