<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This should be downloadable, but perhaps not printed out line<br>for line. If you really want a disassembler, you'll also probably want
<br>an analyzer, </blockquote><div><br>How about this one?<br><a href="http://www.cybertech.net/~sh0ksh0k/projects_small/tDisasm.zip">http://www.cybertech.net/~sh0ksh0k/projects_small/tDisasm.zip</a><br><br>The instruction analysis and code tracing is pretty extensive (especially in this newer version) as demonstrated by (and the hooking code below):
<br><a href="http://www.cybertech.net/~sh0ksh0k/projects_small/tCodeTrace.zip">http://www.cybertech.net/~sh0ksh0k/projects_small/tCodeTrace.zip</a><br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">and you'll want do to something cool with your analyzer<br>in order to make your hooks "future-proof".
</blockquote><div><br>How about this one?<br>
<a href="http://www.cybertech.net/~sh0ksh0k/projects_small/Hooking.zip">http://www.cybertech.net/~sh0ksh0k/projects_small/Hooking.zip</a> <br><br>Give 'em a try.. these days I haven't had much time to extensively regress test, so treat these as "snapshots"... but I believe these versions to be pretty stable. Sending me an email is always the quickest way to get an updated/stable version. Reporting any bugs is always appreciated
<br><br></div></div>