You are not allowed to sell this program, not even for a minimum fee for costs which consist of copying or postage and/or packing! Copy it, but don`t sell it! N O W A Y ! I dont want ANYBODY making money with my work! DONT SPREAD IT COMMERCIAL! DONT PUT IT ON A CD-ROM, ANY LIBRARY OR ANY OTHER DISK! KEEP THIS UTIL GOING THROUGH THE MUCH TOO LESS LEFT BOARDS IN GERMANY! PUTTING THIS TOOL ON A DISK IS A VIOLATION OF LAW! now let`s begin: -______________________________________-__________________________________- Okay. Fuck the lame utils going round these days. Disclaimer: ~~~~~~~~~~~ I`m not responsible for your mistakes, your mishandlings on your systems or any braindamage you have through the use of my software! You can either use it or let it be. To make it clear again: I`m not responsible in any way! Everybody is shocked about the busts. But is there a 100% protection? You need protection. Here it is: What`s it: ~~~~~~~~~~ This tool works very simple: it codes the rdb (Rigid-Disk-Block) of your harddisk(s) in a few milli-seconds. This means: You cannot boot from your harddisk anylonger or read any data from it. Rigid-Disk-Block is needed for the computer to know the size of your partitions and so on. Without this block you have NO access to your HD! (NDOS-disk) If you once have booted your computer you don`t need these informations. You only need these informations when you startup your computer. This is what it`s all about: If you started your computer with a correct RDB you can work with your computer. If you then code the RDB you still can work with your computer. If your computer crashes or if you make a reset you have to restore the RDB to boot again from your HD(s). You can either restore the RDB BEFORE you make a reset, or what is also possible: AFTER you made a reset, but due to the fact that you can`t reach your HD`s any more you have to restore them from floppy drive. This is how it looks in schematic-system: No Protection: 1. RDB okay. You can work with your computer, startup your HD`s etc. Do several resets. Protection: 2. RDB coded: / \ / \ / \ before after bootin`: bootin`: Nobody has You can work with your Computer+HD(s) as normal! access to There is no patch, no loss of time or any other your data`s strange thing with your computer. Not even me! BUT: if you make a reset your HD wont boot (NDOS-Disk) The principle is easy: We think that those people who are really interested in your datas, don`t take the time to look on your HD immediately. They will take the computer with them and figure it out later. So, if they disconnect it from the power-supply and the RDB is coded, they won`t be able to boot again from the HD and they can`t have access to the media by another way, either. Now this is the easy principle. History & advantages compared to other tools: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There are other tools (or at least ONE), which works the same way like my tool. I don`t wanna tell you that I was the first one, who made it this way. Nobody would believe me anyway. I coded the first version of this tool in 1992. There`s another tool from a group called remedy, which made a total hardcore-coding routine. You need a patch and quite a lot of time for reading and writing. And though remedy might not believe it: their protection is not 100% sure. And what is even worse: It takes a lot of time. But what`s worst about the tool is: if you enter a wrong PW your HD fucks up and will never return to you. Why in heavens sake haven`t you created a little checksum for the pw and compare this one with the pw? You think you are smart?! Jesus, eat my shorts. If you enter ONE wrong key your harddisk is GONE! Very nice. This tool also works on an Amiga 1000 (do you remember?)!! Hardware-protections: Is the best solve, though not every controller has one. I don`t have such protection. This tool is a nice software variant. Are you real sure that the controller-pw is 100% sure?! I can`t tell... There`s also another util which delete`s the RDB after copying it on a disk. This is ofcoz a very safe method. I`ll try to implement such option in the next version. But I think it`s a disadvantage to have the rdb`s on a disk. Well, let`s wait and see.. I`ll give you the option to kill and restore the rdb in the next version and then you can decide. You need at least two utils then: one for restoring and one for cleaning the RDB. My tool simply codes your RDB with a PW. It works as a principle known as the "alberti"-concept, which means: fast and uncrackable. You can try your luck, but you`ll fail. You only need ONE tool to code and decode your HD`s. If your HD is coded then it get`s decoded and vice versa. How to install: ~~~~~~~~~~~~~~~ copy "coder" to "dh0:c/coder" or "hd0:c/coder" (on your boot-HD) copy "libs/trashcan.library" to "dh0:libs/trashcan.library" or "hd0:libs/trashcan.library" (on your boot-HD) That`s it. You don`t need no patch or other crap. Take a look at the trashcan.library. It`s NOT a library, but it`s a simple text-file in ascii-format. It might look like this: scsi.device myfuckingpwtralala 0 scsi.device = your device from your controller... if you have OS 2.04 you can start the "dirinfo"-command in this archiv, which is gonna tell you the name of your Controller-device. typical are: gvpscsi.device scsi.device alfscsi.device etc.. if you are running under 1.0, 1.1, 1.2 or 1.3 then you have to figure it out on your own what`s the name of your controller-device. myfuckingpwtralala = is the pw, which is need to code the rdb of this HD 0 = device unit. If you are using more than one hd on one controller then you can decide what HD you wanna protect. _____________________________________________________________________________ ATTENTION: THE RDB CODES A WHOLE HARD-DISK! NOT A PARTITION!! _____________________________________________________________________________ If you want more than one HD to be coded then simply add the lines below each other, so that trashcan.library looks like this: scsi.device myfuckingpwtralala 0 scsi.device anotherpwforhd2 1 scsi.device youknowthepw! 2 With these lines there are THREE Harddisks running on one controller. They get coded/decoded in less than a second. If you have multi-controllers in your system then do the following: alfscsi.device myfuckingpwtralala 0 gvpscsi.device anotherpwforhd2 0 gvpscsi.device anotherpwforhd2 1 maxxon.device youknowthepw! 0 this assumes that you have Three controllers and Four HD`s! I think you got it... It`s easy.. Effectivity: ~~~~~~~~~~~~ IF you want 100% security read these advices: 1. Divide your HD up in multiple partitions (they will ALL become coded). Not in fifty-fifty-partitions, but in 40% 60% partitions, coz if the size of the partitions is unknown there is no chance to get your data. So you better don`t format a GB-HD with one partition, coz this would be too easy to find out. Professional Tools like quarterback tools can not restore any datas from your hd if it doesn`t know the exact size of your partitions!! 2. Bind in the "coder"-command in your startup-sequence as FIRST command. This makes sure: 1. if somebody breaks your startup-sequence your HD(s) are coded. 2. You can sleep tight. 3. Create such a nice Startup-sequence: c:makedir ram:T ram:Clipboards ram:env ram:env/sys c:assign ENV: ram:env c:run >nil: nil: c:endcli If you protect your s:real-startup-sequence with a PW your system is invulnerable. 4. The RDB is 100% coded. You cant decode it. Normal use: ~~~~~~~~~~~ Start up your computer, start "Coder" it will tell you whether your HD`s are coded or decoded. If they are coded then you can`t boot them again. If it says: decoded you can reset your computer and boot again (if you want to). You can also stay it "coded" and "decode" it later from floppy- disks. You have to create your own "libs:trashcan.library" with PW`s, device-names etc. and what is MOST important ofcoz a disk (installed please) with "coder" on it and a directory named "libs" and the "trashcan.library" in it ofcoz. You need this disk if your computer got switched off, while your HD`s are coded or you by mistake made a mistake before decoding your HD`s. You should keep this disk to a VERY safe place. ATTENTION AGAIN: you have to use the same pw`s ofcoz on your disk than you use on your HD! the best would be to copy the trashcan.library to the disk and make NO change to it. You can protect the "coder" on the disk with a Password if you want to. Simply use Powerpacker in encrypt mode! It`s absolutely safe! This makes sure, nobody starts the programm without knowing the password and by this: nobody can decode your HD except you or the person who knows the PW of the coder. ______________________ ATTENTION: ________________________ some lame controllers don`t work without the RDB! This means if your HD is coded and you want to decode it with the "coder" on disk, then it might happen that it won`t recognize your controller-device. this depends on your controller!!! I tested it on many controllers. And it worked with MANY controllers. If it works with yours? I can`t tell. Find out. btw: it works 100% with gvp-controllers and all other GOOD ones... ___________________________________________________________________________ Check it out... signed the programmer of this tool: cedrix of latex: . . _____________________________.______:_ . : / . \___ ____/ ____/ | /| : |___/ | \| | ___) \_ | _/ | _/ \ \_ \ | \ \/ \_ \ _ | \\ | \ | \ | \ / |_________/__! \____:_________/____| \\hH! --------------------------:______/----.--------------:______/-------------- call +49(0)2594-80017, 24h, 14.4.... for bug-reports, questions, etc. please dont call if you crashed up with your HD. I can`t help you.