BUGHUNTER Frequently Asked Questions (FAQs). 

Q: What does BugHunter really detect?
A: See PARTLIST.TXT for a more specific idea.

Q: How does BugHunter actually work?
A: BugHunter uses a customized CheckSumming engine that first examines
   files for a length hit before going any further; This results in a
   much faster more reasonable scantime. If a length hit is made, then
   a checksum is done on the file, and looked up in whichever database
   segment BugHunter is presently using. If a hit is found, the record
   id is looked up. If a matching description for the record id is found
   BugHunter will display it, otherwise it will display "Full Match!" on
   the screen and in the logfile.

Q: Why does BugHunter detect so few compared to others?
A: BugHunter *only* detects executables, and various vb, htm files.
   it doesn't detect registry keys, subkeys, cookies or urls stored
   in your favorites folder. As such, the amount of items BugHunter does
   detect is very small in comparison.

Q: Where can I find the BartPE disc you talk about?
A: http://www.nu2.nu/pebuilder/

Q: How often do you release new signature files?
A: As time allows for the capture and analysis of malware samples.
   Just check the website often. As I find bugs and or add new features
   to the executable, it will be updated as well. New signature releases
   will always involve downloading the BUGHUNXX.ZIP file.
   This assures your using the latest public build executable
   and signature files. Delete your old copy, download and unzip to update.

Q: Can we submit files we believe to be malware?
A: Yes! In fact, I encourage you to do so. See the file MALWARE.TXT
   for instructions.

Q: This Bart disc seems complex, can you send it?
A: You will have to acquire the BartDisk yourselves. Due to licensing
   restrictions, I am unable to provide you (..) a copy.

Q: I'm the author of a program that your BugHunter detects and I am not
   at all happy with that because I feel that my program isn't malware.
   How can this be remedied?
A: Send me a sample of the file in question. If it is a false alarm, I will
   remove it from BugHunter with the next signature update.

Q: I think I found a bug in your program. What should I do?
A: Please contact me. I'll need to know what you were doing at the time
   and I'll need a copy of the bughunt.log file.

Q: Windows says it cannot execute BugHunter. What do I do?
A: This sometimes occurs if you have the BugHunter program placed
   in a folder with a long name. It's recommended to just place Bughunter
   and it's associated files in a directory called \BUGHUNT

Q: Windows is saying something about CONFIG.NT and or AUTOEXEC.NT
A: You either don't have them, or they are corrupt. Very simple
   versions can be found in the NTFILES.ZIP file.

Q: I thought of another question for this FAQ, how can it be added?
A: Contact me. :)