How may we contact you?
Comments, questions, and suggestions are welcome. Please send them as e-mail to: email@example.com
Questions regarding on how to use my software.
Occasionally I receive communications along the idea of: "Can I use your software to crack X?" (As if I had the means to enforce whatever answer I gave.) My response would be to follow the Golden Rule and not this. Less occasionally I receive: "Your software was really helpful to me and I would like to pay you." To these I say: "Donate your money to a useful cause or, better yet, pay it forward and provide something of value to those that follow". I have stood on the shoulders of giants while creating my tools and I am hoping that I am also "paying it forward".
How often are your programs updated?
This depends on where my attention and interest is focused. I use my utilities as part of my daily activities. If an idea strikes me or something just does not seem to work correctly, I often interrupt my work to enhance my stuff and then return to the interrupted work to see if the enhancement or new feature works. My software is very much a representation of how I work and what similar programs should offer.
Are you supporting/updating the 32-bit versions of your utilities anymore?
The 32-bit programs, PEBrowse Professional, PEBrowse Professional Interactive, TopToBottomNT, etc. have been embalmed. These programs were written mostly in an early version of Delphi, Embarcadero's (formerly Borland) Object Pascal language. I waited many years for a 64-bit version to appear, before giving up and switching to Microsoft's language tools. The newer, 64-bit versions of PEBrowse64 and PEBrowseDbg64 have been totally rewritten in managed C++ and support 32-bit programs running on 64-bit Windows. And, no, the Delphi sourcecode is not available for distribution, should anyone ask.
Why don't you supply more program documentation?
I don't supply program documentation because it is a PITA and often a permanent crutch. My software should encourage one to explore and experiment with the many configuration options and the rich context-sensitive menu structure. If it does not, I have missed my target. Much of what you see here is not meant for "beginners"; but since we were all beginners at one point, I hope that by using my programs, one will have help in moving past the beginner phase.
Why are there so many PEBrowse programs, and which one should I be using?
The three PEBrowse programs share large amounts of code, but perform distinct activities. PEBrowse Professional, the static analyzer and eldest, allows you to examine any Windows Portable Executable file (including system drivers) offline and not in the middle of some debugging session. That domain is reserved for the PEBrowse Professional Interactive debugger, which contains most (but not all) of features found in the PeBrowse Professional disassembler but brings powerful additions to the analysis and debugging of an active program. The latest addition to the PEBrowse family, PEBrowse Crash-Dump Analyzer, in many ways acts and feels like the debugger, but instead of a live target examines information collected in a mini-dump or crash-dump file from a dead process.
What is a "Smidgeon"?
Smidgeon was my dear puppy-dog (a Sheltie) that passed away in 2001. She will always remain "my poopee" in my heart and memory and will be immortalized by her presence on the web.