BACK                                                                                         CRACKS FAQs

 

What Exactly IS a "Crack"?

 

In the simplest terms, a Crack refers to anything that allows a software user to defeat a program's shareware-related limitations. A Crack may be an

executable file, an encrypted key file, a Windows Registry file, or even a simple text file containing a serial number or user instructions. Admittedly, this

definition is too broad to be of much enlightenment to a newcomer. In order to elucidate the defining characteristics of a "crack" (the hunter), one must

first aquaint him/herself with the animal known to us as "shareware" (the hunted). So read on, and happy hunting!

 

 

 How Do Cracks Work to Defeat Shareware Protection?

 

The mechanism by which a crack brings about changes in program functioning depends largely on what type of crack it is. It's often useful to categorize cracks into two main groups, based on how they function. There are cracks that that work WITH the program's protection schemes, and there are other cracks that work AGAINST the program's protection schemes. A patcher is a (typically) small executable file that changes a specific number of bytes at one or more specific locations within one or more targeted program files. Crack patchers target areas that control functioning of the program's protection mechanisms, and in altering these areas they effectively bypass or inactivate the protection. Because patches must operate with great specificity in order to avoid disruption of program functioning, they are usually effective ONLY for one particular version, release, or build of a program. The user of a patch must therefore always pay close attention to version information and never use a patch on a program that has a different version number. Doing so will almost always elicit an error message, create a corrupt file, or lock up your system. Patches have extensions of either EXE or COM. Almost always you'll need to move the patch to the program's main directory prior to running it. You "run" a patch by double clicking on it from Windows, or by typing it on the command line from DOS mode or a windowed DOS session. Almost all patches are DOS executables that can effectively be run in a Windows environment. Running a patch will usually elicit a new DOS window that echoes its activity to the screen. The average patch requires less than 2 seconds to complete it's routine, and will automatically terminate the DOS session when it finishes. However the DOS window usually remains on screen so that you can read any confirmations, further instructions, or error messages concerning the patch.
Remember too that running the patch may be just the first step of a multi-sequence crack procedure. Again, you should be able to learn this from the NFO file or other ASCII (text) formatted documentation that accompanies the patch inside the compressed archive. Sometimes you'll need to type specific numbers into a registration screen, other times you may need to execute a Windows .REG file, sometimes you may need to do both. Given the fact that there are countless ways to protect a program, it stands to reason that there will also be countless methods of "cracking" these schemes. Every patch is different so never assume that you know how to use it correctly. Always read the documentation that comes with a patch before you execute the patch.

 

How Do Cracks Work to Defeat Shareware Protection?

 

 

The mechanism by which a crack brings about changes in program functioning depends largely on what type of crack it is. It's often useful to categorize cracks into two main groups, based on how they function. There are cracks that that work WITH the program's protection schemes, and there are other cracks that work AGAINST the program's protection schemes. A patcher is a (typically) small executable file that changes a specific number of bytes at one or more specific locations within one or more targeted program files. Crack patchers target areas that control functioning of the program's protection mechanisms, and in altering these areas they effectively bypass or inactivate the protection. Because patches must operate with great specificity in order to avoid disruption of program functioning, they are usually effective ONLY for one particular version, release, or build of a program. The user of a patch must therefore always pay close attention to version information and never use a patch on a program that has a different version number. Doing so will almost always elicit an error message, create a corrupt file, or lock up your system. Patches have extensions of either EXE or COM. Almost always you'll need to move the patch to the program's main directory prior to running it. You "run" a patch by double clicking on it from Windows, or by typing it on the command line from DOS mode or a windowed DOS session. Almost all patches are DOS executables that can effectively be run in a Windows environment. Running a patch will usually elicit a new DOS window that echoes its activity to the screen. The average patch requires less than 2 seconds to complete it's routine, and will automatically terminate the DOS session when it finishes. However the DOS window usually remains on screen so that you can read any confirmations, further instructions, or error messages concerning the patch.

Remember too that running the patch may be just the first step of a multi-sequence crack procedure. Again, you should be able to learn this from the NFO file or other ASCII (text) formatted documentation that accompanies the patch inside the compressed archive. Sometimes you'll need to type specific numbers into a registration screen, other times you may need to execute a Windows .REG file, sometimes you may need to do both. Given the fact that there are countless ways to protect a program, it stands to reason that there will also be countless methods of "cracking" these schemes. Every patch is different so never assume that you know how to use it correctly. Always read the documentation that comes with a patch before you execute the patch.
 

1

 

 

 

 

 

 

 

CopyrightİFoOsi 2002 -Last updated 02.10.2002        Created  at 13.03.1999                                                                                                            Contact me : [email protected] 

 

1

Hosted by www.Geocities.ws

1