NT UNIX Password Cracker Documentation
--------------------------------------

Software and documentation written by: The Hurtmaster

System requirements:

	Windows 32 bit compatible operating system.
		-> Preferably Windows NT.
		-> Windows 95 is ok, but not quite the same speed.
	Pentium processor
		-> Tested on 90, 120, 150, 166 (but not the PRO yet)


The main menu is pretty straight forward:

1)  Get Cracking; move to the password cracking screen.
2)  Results; this screen allows viewing of passwords that have been found.
3)  Auto resume; not yet available - but will come if there is any demand.
4)  About; program, version, author information.
5)  Exit; enough for today.

The password cracking screen requires several fields to be entered before
starting. Once everything is entered, just press the Start button to begin.
Afterwards (during the cracking process) you can press the Stop button to
halt (or pause).

The password cracking screen has the following subtleties:

a) If you leave the Word List blank, then the Brute Force method will be used.
	-> Brute force reads all of the custom password criteria.
	-> Word list cracks will only read the minimum word length.
b) If you leave the Password blank;
	-> Entire word list will be used.
	-> Brute force will start according to your criteria. (ex: AAA)
c) If you enter a word into the Password field, and there is a Word List
   selected, then the Password must exist in the word list for things to
   continue.
d) Turning off Fast Update will update the screen every 1000 passwords.
e) The password list that you select will be sorted to take advantage of
   similar salts.  With large password files ( > 30000 accounts) this can take
   a few minutes.  Keep in mind however that with more accounts, you
   have a better encrypt/attempt ratio - so it's worth the extra time.  Very
   small password lists may not make any difference either way.
f) Because the password list is stored completely in RAM it is possible that
   you might run out of memory while loading.  I've tried a mock password file
   containing 50000 accounts, and everything went well.  If you run out of
   physical memory and it starts to swap, your performance will probably
   decrease dramatically.  I would suggest cutting up the password file
   into smaller pieces - although I haven't seen a case for this yet.


That's it - have fun.
If you have any bug reports, comments, suggestions, or otherwise you can
reach me (indirectly, although I'll get it eventually) at:
    
    Email: aq783@freenet.carleton.ca
