Maverick_V3_Instruction_Manual.pdf

PRESENTS

MAVERICK v3

FOR ALL AMIGA COMPUTERS

AN IMPORTANT NOTE

The Maverick is a very powerful and comprehensive utility system. We're

alwayshappy to providesupport toregistered Maverickowners, butwe can't

teach you over the phone what this manual is designed to teach you. Before

calling for technical support, please re-read the appropriate section of the

manual and check the trouble shootingsection. Your help in this allows us to

serve you better on those occassions when being able to reach our technical

staff is required. Thank you.

TABLE OF CONTENTS

IN THE BEGINNING

PARAMETERS? LONG TRACKS? CUSTOM COPIERS?

SYSTEM REQUIREMENTS

PACKAGE CONTENTS

UPGRADES & SUPPORT

GETTING STARTED

HARD DRIVE INSTALLATION

COMMAND SCREEN OVERVIEW

COPY IN PROGRESS SCREEN

USER CONTROL CENTER

EXPANSION MODULES

KillDFX

THE INSPECTOR

QUESTIONS & ANSWERS

BACKUP BUDDY INSTRUCTIONS

.21

CONCLUSION

LIMITED WARRANTY

CREDITS

BACKUP BUDDY ORDERING INFORMATION

AMIGA MAVERICK

IN THE BEGINNING

<> Remember back a few short years ago, when we all thought that "Pong" was the

hottest game ever produced for home use? The cartridge game machines appeared on

the scene and the personal computer was here and here to stay. Not long after, "IT1

arrived. "IT" was capable of not only playing games with its user, but also allowed its

user to develop his own programming. "IT" was the Commodore 64, and before long

it became the personal pet of millions of people wishing to join in the age of personal

computers. Commercially produced applications such as spreadsheets and word

processors started to show up in rudimentary form, and software copy protection was

soon to follow.

Software protection has come a long way since the inception of the Commodore

computer. Ever since the first commercial software was written for the Commodore,

programmers have been dreaming up newer and more potent protection schemes. The

purpose of copy protection was to prevent the software authors from becoming victims

of piracy. Although most well thought out protection schemes seemed to slow the

pirates down a bit, the protected software was eventually broken, and fell into their

hands like anotherstamp in a collection. The result was that most ofthe software pirates

still didn't purchase the software that they finally acquired anyway. The honest

consumer DID purchase his software, especially those programs that he decided were

a valuable addition to his library. It is this individual that has been the real victim ofthe

software protection wars. If he wanted a backup of his fragile treasured program disk,

he had to send extra money to the manufacturer of that product and wait for what

seemed like forever to receive his backup. The only alternative was to resort to a myriad

of copiers, hoping one of them would do the job at hand. As it turned out, it seemed

that the more valuable the program was to the consumer, the harder it was to backup.

For a time, it was a leap frog game between the copier programmers and the protection

programmers. Anew protection scheme was developed, and all the copier programmers

would scramble to be the first to develop a new patch in their copiercapable ofdealing

with that particular protection scheme. This leap frog game went on for a couple of

years before the inevitable happened. The protection programmers evolved to the stage

that they wereable to write protection thatjust couldn'tbe duplicated, at least with disk

drives availableto the end user, even with the most sophisticated nybblers. All purpose,

do it all copiers were dead in the water.

What to do? If the copier programmers couldn't write copiers to sense and copy a

particularprotectionschemethenonlyonesolutionremained.Breaktheprotectioncheck

code. It was early in this stage that Kracker Jax was born. KrackerJax allowed the user

to simply make a fast copy of the protected program and then run a custom parameter

over that copy to produce not only a copy of that program, but a copy devoid of

protection in most cases. The revolution had begun. Parameters proved to be the most

effective way to copy a protected program. Protection schemes that no nybbler could

AMIGA MAVERICK

touch could easily be archivedby the press ofa key. This went on for a couple ofyears,

and again the inevitable happened. Parameter-proofprotection. How, you ask? Read on.

Today's protection is made up ofthree classes ofdifficulty. 1. Afew programs are still

released using archaic protection that most modern nybblers can duplicate. Why bother

protecting?! 2. Many are still archivable using either a nybbler or fast copier in

conjunction with a parameter. 3. Finally, more and more programsare showing upwith

data written in formats that protects every byte of data on the disk. Ifthe data can't be

written out, then a parameter is useless. The Bull's Eye was our first effort at this third

level of copy protection. Soon after, the Shotgun II was developed to automate the

principals set forth in The Bull's Eye. These two programs have set the standard which

imitatorshavebeentryingunsuccessfully toduplicate.TherevolutionstartedbyKracker

Jax has paved the way for the Maverick, the next step in an evolutionary process. <>

Those of you who have been supporting us over the years will recognize the above

paragraphs as the introduction to Maverick for the Commodore 64. "So what11 you say,

"this is an Amiga product". Well, as a matter of fact, the methods used to copy protect

Amiga programs are VERY SIMILAR. Remember, just as the hardware evolved from

Commodore 64 to Amiga, so have the programmers and the protection schemes that

they use.

Rudimentary Amiga protection such as DOS Error checks and Index Sync format have

given way to the familiar signature tracks, long tracks, and custom formats. Our

methods todefeat theseschemeswillbe ourcustomary methods. Experienced computer

users learned long ago that backup products that promise to be 100% effective are

nothing more than false promises shrouded by ambiguous sales pitches. Nothing, not

even Maverick itself, willbackupeverything. WewillapproachAmigacopy protection

just as we did Commodore 64/128 copy protection - with long hours and hard work.

This resultsin thecreationof(patch) parameters and custom copiers thatworkandwork

well. These willbe offered in upgrades on a timely basis. See the Upgrades section in

this manual for more info.

PARAMETERS? LONG TRACKS? CUSTOM COPIERS?

Copy protection has come a long way from the days when a "do it all" nybbler could

either copy all protection on the market - or could be programmed to do so. Today's

copy protection usually demandsa tool wecalla parameter. "Whatisa parameter?" you

ask. For our purposes, a parameter is a program written by us that addresses the copy

protection ofa specific title (and possibly one ofmany protection versions ofthat same

title). Thus, even though a parameter may workin many different ways, the resultswill

be similar.

AMIGA MAVERICK

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika: