by the way, i noticed something. the list of names of the processes in taskmanager isn't always the same as the window name. sometimes, the window name may change during game play (!) and then a trainer based simply on the window name it is running in would not be helpful. however the name of the process in windows task manager stays constant. so the window name and the process name are two different things. i think the task manager approach would be necessary in those instances where the window name might possibly change during game play or be different each time you load the game. however, for 90% of games (a guess), the window for the .exe is probably static (i.e. the name of it doesn't change) so then tracer's simpler version would apply. i was curious how many api calls are in tracer's code (i am being to lazy to check each statement) and could you quickly generate a .decls file for it (userlib)? i can probably make the trainer using tracer's method for the specific game i have in mind, but being able to select the process using the task manager method would be nice to know since the name of the window could potentially be different when the trainer is engaged. i hope you guys will continue to work on this. thanks a bunch, i know it took a little time to do this for me- these are great forums.
best,
mike
best,
mike