COPY PROTECTION ================= Copy protection is a method of storing information on disks using a non-standard format. This makes information on the disk hard to copy and modify. Although protection is legal, it is often unfair to the person who buys the program. Because of this problem, when a normal program tries to read the program, it can't understand it, and usually gives you some kind of an error. Companies (and writers) will copy protect data to make sure that people buy the programs. Without copy protection, anyone who bought a program could freely distribute it, robbing the author and publisher of sales. The problem with copy protection is that the resulting program is non-modifiable. For instance, many business programs (ranging in price from $75-$1000) are protected. If you buy one of these programs, you cannot customize it to fit your individual needs and uses. The second problem sprouts directly from a program being protected. If you ever happen to destroy your disk, you have no other copies. Disks are easy to destroy, and may range in cost from 5 to 20 dollars to replace. If you aren't familiar with software laws, it is perfectly legal to make copies of a program for yourself. For these reasons, it was felt that a program was needed to allow the backup and maybe modification of programs. The result is dedicated copying software. e.g. MARAUDER, MIRROR, HACKERS PACKAGE. The topic of disk "Copy-Protection" is now a very complex one compared to a few years ago. To give you an idea how far it's come, let me give you an example. When MARAUDER was first released it had only a handful of algorithms (copy formulas). Now, programs like MIRROR 1.5 have not only more complex algorithms, but many more of them. And still it won't copy everything without heavy user intervention in many cases. Meaning, you may need some in depth computer savvy to use it to its ultimate. Most copy programs do just that, they make duplicate copies of protected software that will hopefully work. But what if you want to modify the protected program? Sorry Charlie, but its locked up. Unfair I say! You paid for the right to use the program, and should be able to change it according to your individual needs. The HACKERS PACKAGE was born out of this need. It's main function is to "BREAK" the copy protection system of the protected disk itself, as well as pulling data off a damaged, standard Dos disk. Recovering data from a damaged disk may save you many hours of re-entering data. So now you say, shouldn't the unprotected version I've created work just like the original. Maybe and maybe not. Back in early to mid 1986 you could say yes. 90% of them, or better, will work fine without doing anything else to them. However, the newer protection systems don't just protect the disk, they protect the program as well. This is where the snag comes in. The copied program, just removed from the copy protected disk, may check itself while it's booting, to see if it is on its own original disk. Of course, now it isn't. So while you now have an unprotected version of a program, it may not run simply because of this. Now you must look at the program itself, and determine what sort of protection scheme(s) it uses. There isn't a program in the world that will do that for you. You must have some programming fundamentals under you belt. The HACKERS PACKAGE has a text file on its disk with a listing of some changes to varying programs, most of which break the disk and/or the program protection scheme. The only problem with this is you're not learning, you're just punching in numbers that don't mean anything, all you know is that it works. But learning Assembler language to pick these schemes is a whole new kettle of fish, lets not get into that. There are many, and varied, forms of copy protection schemes, ranging from the most simple (e.g. changing the sync words to a non standard format), to the most sophisticated (e.g. program protection - long track gap length). No protection scheme is invincible, after all the disk must be read by the computer. Seeking, and identifying, the type and form of protection is the hard part. Once this has been done, it's only a matter of formality to either alter, or discard, the part of code which does its self checking. I personally use THE MIRROR HACKERS PACKAGE, and once mastered it can not only allow you to alter protected software, but very quickly teach you the basics of disk format construction. I've heard that many people find it hard to use this package. Pity because it is a good piece of software. Maybe, if MEGADISC receives enough feedback they will consider allowing me to write a tutorial article for its use, and helpful hints. (Just heard on the grapevine that MARAUDER are also bringing out a hackers package). IS THERE AN ANSWER ? I was prompted to write this article to show my feeling about the Protector/Pirates merry-go-round. With the high shelf price of software here in OZ its not surprising illegal copying is rife. Will cheaper or more affordable software reduce it? Will deprotected software reduce it? Will heavier penalties for breaching the copy-right law reduce the incidence of copying ? Will even more sophisticated protection schemes reduce it ? I don't know the answer but, who's going to be the first one to jump off the merry-go-round ? The result of the introduction of copy programs such as MIRROR 1.5 and MARAUDER II has been to "force the hand" of the software vendors. The initial response was to develop new protection schemes that defeated these programs. If the present trend continues, it is very likely that protection schemes will evolve to a point where automated techniques cannot be used to defeat them. Is this really in every one's interest ? I for one, would buy more software if it were reasonably priced and non-protected. I don't think I'm Robinson Crusoe with this view. Till next time.............STEVE WRIGHT. END OF PROTECTION (what?) | | V