▄▓██ ▄ ▄▄▄▄ ▄▄ ▀ ▄▄▄ ▄▄▄ ▀ ▄▄▄ ▀ ▄ ▄ ▄▓▄ ▄██▄▓▄▄
▀██▄█▀ ▄▄ ██▄▓████ ▀▀▀▀ ▀▀▀█▓████ ▓███▓▄█▓▓▄ ▓██▄▓▓██▄ ▓█▄ ██▄▄▀ ▄▓▓ ▄▄ ▀▀▓▄█
█▀▀▀▀▐▓██ ▀▀▀▀ ▄▄▄▄▄███████▄▄▄▀▀▓█▄▀▀▀ ▀▀▀▀ ▄▄▄▄▄▄▄▄▄▄ ▀▀▀ ▀▀▀▀▓ ▀ ▄█████▄ ██▓
▄▓██▄███████▄▄▄▄ ▀▓▓███▀▀▀▓▓███▄▄▀▐█▄█████ ▀████▀▀▓████▄▀████▄ ▄██▐█████ ▀
▄▄▄▄ ████▀▀▀▀██████▄▐███▌ ▀█████▄████▀ ████ ▐████▀███▌▀█▓▓█ █████▌▄██▄
▀▓█▀▐████ ▄ ▀████████▌ ▄▄ ▐██▓▓▄███▌ ▄████▄▄▄▄████▓████ ▀█ ▐█████ ▀█▓▀
▓██▌▐████ ▀▓▀ ▄█████▀██▄▄▄▄████▀▀▐██████▓ ▐███▓▀▀▀▀████▐████▌ █████▌▓█▄▄
▀▀ ███▓▓▄▄▄▄██████▀████▀▀▀▀▄▓██▀ ▓███▓ ▄████▌ ▐███▌ ▀▀▒▀ ▐████▓ ▀▀▀
████████████▓▀▀▀▐▄▓███▌ ▓████▄▐███████████████ ██████▓ ▀▀▓▀ ████████▓▒░
▓▄▄▄ ▄▄ ▄▄▄▄▄▄▄▄▄███▄██▄▄▄▄█▄▄▄ ▀▓█▄█▄█▀ ▄▄▄▄▄▄▄ ▓█▄▄ ▄ ▄█████▄ ▄▄ ▄▄▄
▀▀ ██▓▓ ███▄█▀▀▀███████▀▀▀▓▓▄█████████▌▀▀▀▀▀▀▀███▄▀████▄▄ ▄█▀▐█████ █▓▓ ▀▓▓▌
▀ ▄▄▀▀ ▄▐████▌ ███████ ▄████ ▓██▓ ▄███▀▀▓█████████▓▀█▓▓▀ █████▌ ▓▀ ▄▓▄
███▓▄█▌▓▀▀▀▄▄▓▐██████▌ ▓████▌ ▄█▀▀ ▓██▓▌ ▓████ ▓████ ▀ ▐█████ ▀▀▀▄ ▀ ▄
▄ █▀█▀▀██▀ ▀▀▀ ▐██████▌ ▐███▓▓ ▀ ▀▓▓█████ ▐████▌ ▓███▌ █████▌ ▓█▓▄ █▓
▓████ ▄▄ ▀ ▒▓████████▓▀█████████████▄█▓▓▀▀▀▓██████▓ ▓███ ▓▄▄▄▄▄▄▄▄████▀▄▄ ▀
▄ ▀▀ ▓▓██ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▓▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█▓░ olli^cro ▓▓██
▀▓▀ ▀ ▀▀ ▀▀
┌───────────────────────────────────────────────────────────────────────┐
│║ [■] Armadillo v3.60 DR Professional (Public) [■] ║│
│║ ─────────────────────────────────────────────────────────────────── ║│
│║ cracker....: dREAM TEAM date.........: 01/26/2004 ║│
│║ supplier...: dREAM TEAM type.........: Uncrackable Stuff ║│
│║ tester.....: dREAM TEAM developer....: SRT Lamers / DR ║│
│║ packager...: dREAM TEAM protection...: Armadillo v3.60 ║│
│║ system.....: WinAll size.........: 01 x 2.88 mb ║│
│║ ─────────────────────────────────────────────────────────────────── ║│
│║ ║│
│║┌─[ r e l a s e n o t e s ]───────────────────────────────────────┐║│
│║│ │║│
│║│ armadillo is a powerful license manager and software protection │║│
│║│ system. it wraps around your program like an armored shell, │║│
│║│ defending your work from pirates and program crackers while │║│
│║│ enforcing your license agreement. it allows you to add a complete │║│
│║│ ready-made registration-key and software protection system to │║│
│║│ your existing programs in five minutes or less -- source code is │║│
│║│ not required! it works with almost any 32-bit windows exe, dll, │║│
│║│ ocx, or screen saver file, regardless of the language it was │║│
│║│ written in. │║│
│║│ │║│
│║│ the power and flexibility of armadillo come from its license │║│
│║│ management model. you decide, when you release your program, how │║│
│║│ it will be licensed -- armadillo offers a number of options, │║│
│║│ including unlimited licenses, time-limited licenses (which expire │║│
│║│ a certain number of days after the user first runs them), │║│
│║│ date-limited licenses (which expire on a certain date, the date │║│
│║│ can be either hard-coded into the program or placed in the key), │║│
│║│ and usage-limited licenses (which expire after a certain number │║│
│║│ of runs or after using some function a certain number of times). │║│
│║│ │║│
│║│ the program's license certificates are embedded in the program │║│
│║│ itself when armadillo encrypts it. they can only be decrypted │║│
│║│ using the keys you select, by means of an encryption template (a │║│
│║│ word or phrase that you keep secret) -- no information built into │║│
│║│ the program can decrypt a license file without the proper key. │║│
│║│ and if anyone tries to patch the armadillo code to bypass the │║│
│║│ license-check, the program can't be decrypted -- it requires │║│
│║│ information stored in the license certificate. │║│
│║│ │║│
│║│ armadillo supports several different kinds of licenses, including │║│
│║│ temporary (time-limited) and demonstration/limited usage. each │║│
│║│ kind of license requires a different key to decrypt, meaning that │║│
│║│ even if someone were able to crack the protection scheme, they │║│
│║│ would still be unable to forge a permanent license key without │║│
│║│ first buying your program. and they can't get away with buying a │║│
│║│ key and then immediately getting their money back, either; when a │║│
│║│ user first purchases the program, you can send them a temporary │║│
│║│ key which will only work for a limited time (such as the │║│
│║│ charge-back period for credit card purchases or the time it takes │║│
│║│ for their check to clear). if the check doesn't clear, or they │║│
│║│ demand their money back within that time period, the key will │║│
│║│ expire and they'll be no better off than they were. if all goes │║│
│║│ well, you send them a permanent key after you've safely gotten │║│
│║│ your money. │║│
│║│ │║│
│║│ your program can be released on cd-rom, disk, via the internet, │║│
│║│ or any other way you wish. you will only need one version of your │║│
│║│ program to handle all of the different license models! when a │║│
│║│ user pays for your software, you only need to give him a key │║│
│║│ (something like "a1b2-c3d4-e5f6-7890"), which you can generate │║│
│║│ either by hand (using armadillo) or by program (using the │║│
│║│ codegen.dll supplied with it). because of its format, keys can be │║│
│║│ given easily by telephone, fax, or e-mail. you can also set up │║│
│║│ your program so it doesn't need a key to get a trial version, by │║│
│║│ using a default key which armadillo checks for if it can't find │║│
│║│ another one, so your user doesn't even have to worry about │║│
│║│ getting or entering a key until he decides to purchase your │║│
│║│ program. │║│
│║│ │║│
│║│ setting up armadillo is a snap! a dialog-based system allows you │║│
│║│ to change any of its settings, no messy text configuration files │║│
│║│ involved. guided examples show you the most common features of │║│
│║│ armadillo and how to use them; you can have your armadillo system │║│
│║│ ready to run in as little as five minutes. once it's set up, a │║│
│║│ single command (which can be given using the graphical interface │║│
│║│ or by the command line) will protect your software. │║│
│║│ │║│
│║│ armadillo will work with or without support by your program. if │║│
│║│ you use a third-party program to create yours (such as an e-book │║│
│║│ program, a screen-saver toolkit, or a music system), armadillo │║│
│║│ can handle all the license-management details without the actual │║│
│║│ program knowing anything about it. or, if you prefer, you can │║│
│║│ integrate armadillo's licensing into your program and handle │║│
│║│ everything yourself. │║│
│║│ │║│
│║│ armadillo's keys are based on a word or phrase that you select │║│
│║│ (known as an "encryption template"). this secret word or phrase │║│
│║│ is what makes armadillo's licenses secure -- without it, no one │║│
│║│ (including us!) can access the details of your license, or your │║│
│║│ program. │║│
│║│ │║│
│║│ armadillo keys can be generated by most of the online │║│
│║│ software-purchase systems with little or no effort. if your │║│
│║│ favorite system does not support armadillo yet, please ask them │║│
│║│ to contact us, and we will provide them with the necessary files │║│
│║│ free of charge. │║│
│║│ │║│
│║│ whats new in v3 series │║│
│║│ ---------------------- │║│
│║│ . added five new levels of signed v3 keys │║│
│║│ . added network card mac address and physical memory size to the │║│
│║│ list of options for the hardware fingerprint │║│
│║│ . extended the extra info field to 16 bits for unsigned keys and │║│
│║│ older expire-by-uses signed keys with the expiration data in │║│
│║│ the certificate, and 32 bits for all others (it was previously │║│
│║│ fifteen bits for all keys) │║│
│║│ . added user-defined bit labels. the labels can be different for │║│
│║│ each certificate │║│
│║│ . added an option to disable the register command-line parameter, │║│
│║│ for customers who want to force people to use their own enter │║│
│║│ key dialogs instead of armadillo's default one │║│
│║│ . added up to five secondary files-to-protect. secondary files │║│
│║│ are only supported for protection; all other functions will │║│
│║│ ignore them. armadillo supported secondary files before, but it │║│
│║│ wasn't official or documented │║│
│║│ . changed the *.arm project file format. the project files now │║│
│║│ use the standard windows ini format, and can be modified easily │║│
│║│ by external programs. all previous *.arm files can still be │║│
│║│ read, but only the new format will be written; armadillo will │║│
│║│ ask permission to make a backup of your old file before │║│
│║│ converting it to the new format. please note: armadillo does │║│
│║│ not attempt to check the validity of the options in the file. │║│
│║│ . added the option to compress resources (in the professional │║│
│║│ edition only) │║│
│║│ . enhanced the relative sizes display, to display the resource │║│
│║│ and data-after-program portions separately, and changed the │║│
│║│ color scheme so that colors shown on the uncompressed bar are │║│
│║│ now also used on the compressed one for the same data │║│
│║│ . permanently fixed the "limited accounts" problem under windows │║│
│║│ nt4/2000/xp by requiring write-access to the new main registry │║│
│║│ key. if the user doesn't have permission to set write-access on │║│
│║│ it, your program will ask him to run it from the administrator │║│
│║│ account to set it up (this is only required the first time an │║│
│║│ armadillov3-protected program is run, after that the access │║│
│║│ will be available to all armadillo-protected programs). │║│
│║│ . you can now store the number of copies (either in the key or in │║│
│║│ the certificate) and use the don't-check-copies-on-startup │║│
│║│ option at the same time, as requested by several customers │║│
│║│ . added the setuserstring, getuserstring, and vbgetuserstring │║│
│║│ functions to armaccess.dll (professional edition only). these │║│
│║│ functions allow your program to store and retrieve up to eight │║│
│║│ strings of 255 characters each, which will stay on the machine │║│
│║│ between runs, securely stored against user-tampering along with │║│
│║│ armadillo's own key-code information │║│
│║│ . added multiple language capability for the expiration, │║│
│║│ reminder, and limit install time messages, by request. when you │║│
│║│ change the language for a project, you can now specify a │║│
│║│ different set of messages for each of these. this feature is │║│
│║│ meant to be used with the command-line language override │║│
│║│ (/language=) added in 2.85 │║│
│║│ . the nanomites option is now visible in public builds. the code │║│
│║│ to support it will still only be available in custom builds │║│
│║│ . you can now tell your protected programs the name and key to │║│
│║│ register on the command line, via the register command. just │║│
│║│ use it like so: "yourprogram.exe register " │║│
│║│ (without the quotation marks). do not use quotation marks │║│
│║│ around the name or key either; armadillo will take care of it │║│
│║│ │║│
│║│ whats new in v3.60 │║│
│║│ ------------------ │║│
│║│ since the beta-1 version, the only changes are some minor │║│
│║│ bug-fixes and security changes, and the addition of a new │║│
│║│ environment variable, totaluses. since the 3.50 version, the │║│
│║│ major new features are: │║│
│║│ │║│
│║│ . added a new anti-dumping defense, import table elimination, │║│
│║│ another defense that does not require the debugger blocker │║│
│║│ setting │║│
│║│ . the reminder, expiration, and warning messages can now all be │║│
│║│ set to use a plain-text message, an html message, or a bitmap │║│
│║│ . in addition, the expiration and warning messages now have a │║│
│║│ visit website/buy now button, if you've defined a website in │║│
│║│ your project for the current certificate │║│
│║│ . you can now store multiple armadillo languages in a single exe │║│
│║│ file, by request │║│
│║│ . added the firstrun environment variable, by request │║│
│║│ . the splash screen bitmap is no longer shown when quietregister │║│
│║│ is used, by request │║│
│║│ . added a new api function, showremindermessage, by request │║│
│║│ . we've also continued our improvements to the security code │║│
│║│ │║│
│║│ │║│
│║│ for more info visit http://www.siliconrealms.com/armadillo.htm │║│
│║│ │║│
│║└───────────────────────────────────────────────────────────────────┘║│
│║ ║│
│║┌─[ i n s t a l l n o t e s ]─────────────────────────────────────┐║│
│║│ │║│
│║│ 1. run setup.exe to install the main program │║│
│║│ │║│
│║│ 2. run keygen.exe to generate your registration info │║│
│║│ │║│
│║│ 3. start main program and finish the registration process │║│
│║│ │║│
│║│ │║│
│║│ there are two versions of this product, public and customer ones. │║│
│║│ there's no support of nanomites and other stuff in public version │║│
│║│ available free from author's www. │║│
│║│ │║│
│║│ │║│
│║│ *** OPEN MESSAGE TO SRT PROGRAMMERS *** │║│
│║│ │║│
│║│ girls, i dont wanna race you with any new arma crapy version. its │║│
│║│ more than year and half when i released first armadillo keygen. │║│
│║│ so try use a brain, read some books and code *really* powerfull │║│
│║│ one! │║│
│║│ │║│
│║│ dont waste your time with making rumors like we use 300 computers │║│
│║│ on university to bruteforce armadillo and few others. yours │║│
│║│ customers arent dickheads so dont use lies and try to stop me. i │║│
│║│ do a favour to you by testing your protector..so stop bitchin and │║│
│║│ start work! │║│
│║│ │║│
│║│ hm..maybe your idea isnt code good protector.. │║│
│║│ │║│
│║│ more keygens -> more lies -> more sell updates -> more dollars │║│
│║│ │║│
│║│ ..so girls, fuck you!! │║│
│║│ │║│
│║│ -skamer delebre │║│
│║│ │║│
│║└───────────────────────────────────────────────────────────────────┘║│
│║ ║│
│║┌─[ a b o u t u s ]───────────────────────────────────────────────┐║│
│║│ │║│
│║│ we arent absolutely not a new group. we have been around way │║│
│║│ before your mother had sexual intercourse with your father (or │║│
│║│ was it the dog next door?). │║│
│║│ │║│
│║│ we know everything about you being a little jerk sitting in a │║│
│║│ front of your computer (your mom spent the money on) doing │║│
│║│ nothing but idling on irc (nice logs we have from you by the │║│
│║│ way), and boasting how cool trader you are naming yourself dark │║│
│║│ dork or something as stupid as you really are. │║│
│║│ │║│
│║│ we are watching you and everybody you talk to via the school link │║│
│║│ you think is so-so safe. we have logs of everything you have │║│
│║│ said or done on the net. we have roots on all the machines you │║│
│║│ think you rule according that cws mag we actually release too. │║│
│║│ │║│
│║│ we know which porn site you attend while jerking. we have given │║│
│║│ you that old bitch you plan to spend your dad's money on to lose │║│
│║│ your virginity with. we know everything. you apparently know │║│
│║│ nothing. │║│
│║│ │║│
│║│ we releases stuff. it is going to be spread worldwide. it │║│
│║│ contains viruses and trojans we coded to trace it all the way │║│
│║│ down to your very site or shell. you know, we want more roots as │║│
│║│ well as we want to bust your tiny ass. if you see this nfo on │║│
│║│ your site, you know we gotcha. smile! you're being photographed. │║│
│║│ │║│
│║│ ───────────────────────────────────────────────────────────────── │║│
│║│ │║│
│║│ *** MESSAGE FROM OUR SPONSOR *** │║│
│║│ │║│
│║│ "dREAM TEAM seems to be one angry guy with delusions of adequacy, │║│
│║│ trying to make himself look big by calling himself a group." │║│
│║│ │║│
│║│ Chad Nelson (Armadillo Lead Developer) │║│
│║│ │║│
│║│ ───────────────────────────────────────────────────────────────── │║│
│║│ │║│
│║│ - SHOUT OUT - │║│
│║│ │║│
│║│ .: UNPACKING GODS :: dREAM TEAM :: PDX :: RENEGADE :: CORE :. │║│
│║│ │║│
│║│───────────────────────────────────────────────────────────────────│║│
│║│ │║│
│║│ . we dont send any cracks/keyfiles/serials and other stuff │║│
│║│ . we dont support any unsecured web sites and other public crap │║│
│║│ . we aren't technical support, so fuck off with stupid questions │║│
│║│ │║│
│ └───────────────────────────────────────────────────────────────────┘ │
└───────────────────────[dREAM TEAM 2000-2003]──────────────────────────┘
dT-CRC:2003-12AA!