@ Tactical: I wanted it basic for many reasons. The more graphics the higher the file size. This one keygen was 18 mb until I made the BG a JPEG and lowered the quality of the music.
Quote:The author of a keygen typically uses a disassembler to look at the raw assembly code of the targeted program, checking either the software itself or the installer. Once access has been obtained to the program's code, the location of the subroutine(s) responsible for verifying that the key entered is valid are found. Using this knowledge, the algorithm may be reverse engineered to generate valid keys, which is then incorporated into the keygen.
With weaker serial protection schemes a complex reverse is not required as the key-checking code itself in the original application can be effectively copied and incorporated into a keygen. Weaker schemes sometimes internally generate a correct key inside the original application for comparison purposes (to determine whether the entered key is correct).
Some keygens use a brute force approach or brute force hybrid approach to creating valid keys. In these instances, rather than produce an exact reverse of the key check algorithm, the attacker uses a search technique, testing many possible combinations per second against the key validation check until a given combination produces a valid key.
Sometimes keygens have code incorporated into the keygen to change the written code of a program in order for the code that is given via the keygen to work, but this is not typically done for a keygen, as it is considered 'impure' when a crack must be used in conjunction with a keygen; true keygens are considered as such when they generate valid keys and do not require an additional 'crack' i.e. modification to the original application code for generated keys to be accepted.
The coding for the program takes a working key(s) and makes an algorithm. It then randmoizes the key so that it is an acceptable one for the program.