These pages are kept because they are part of hashcat's history and because links to them exist all over the internet. Do not follow their advice. Each one says at the top what to read instead.

A page lands here for one of three reasons. It describes a program that no longer exists. It describes a feature that was removed. Or it still works, but there is a better way now, and sending somebody down the old road when a shorter one exists is not help.

• Archived FAQ - driver error messages from the fglrx, Catalyst, ADL and ForceWare era, moved out of the FAQ. The error codes are still searchable, so the answers are kept, but none of them apply to a current machine.

hashcat, hashcat-legacy, oclHashcat, oclHashcat-plus and oclHashcat-lite used to be separate programs. They were merged into one hashcat in 2015. Everything here describes one of the old ones.

• oclHashcat - read hashcat instead
• oclHashcat-plus - read hashcat instead
• oclHashcat-lite - read hashcat instead
• oclHashcat-old - read hashcat instead
• hashcat-legacy - the CPU-only program. Modern hashcat does CPU and GPU in one binary
• md5stress - the repository is gone. Use hashcat -b to load a card
• Supported PSA and the original - generic sha1(pass.salt) support was dropped. See example hashes
• Feature requests and the original - these live on GitHub now

• Catalyst and ForceWare - both driver families are long gone
• Upgrading AMD drivers on Windows and the original
• Changing fan speed of ATI under Linux and the original
• Ubuntu Server + AMD Catalyst HOWTO - built around Ubuntu 14.04, which is long out of support
• VCL Cluster HOWTO and the original - VCL is dead. See Distributing work
• Making your cat lose weight - hashcat compiles only the kernels it needs, so there is nothing to trim

• Cracking SL3 - the SL3 algorithm is no longer supported
• hccap format - the modes that read it are deprecated. See Cracking WPA/WPA2
• hccapx format - same. Convert your capture and use -m 22000
• WPA clean and convert script - written for Backtrack, and current advice is the opposite: do not clean a capture file, it throws away frames hashcat needs

• Using rules to emulate a hybrid attack - attack mode 12 does this directly. You write one mask and put ?w where the word goes
• Using maskprocessor to emulate brute-force and the original - built into hashcat now
• Using maskprocessor to emulate a mask attack - built in now, see Mask attack
• Distributing workload in oclHashcat and the original - see Distributing work
• Distributing workload in oclHashcat-lite and the original - -s and -l do this, see Distributing work

Several pages here have a twin whose name ends in _original. When somebody added a deprecation notice to a page, they kept the untouched text under that name. They are the same material twice and are archived together.