@DATABASE "enLOCK Hard Drive Protection Docs" @AUTHOR Mike Carter @$VER: v1.3 (29/01/96) @(c) "İ1995/96 NFA Productions" @FONT topaz.font 8 @NODE MAIN "Welcome" ____ . __________________| \ .____: __________ ______________/Ħ _______ / __________ \ \| Ħ / ___ \ / ._______ |/ _/ _/ ____)_ / \ \ \ |___/_ |\ \/ | _____ \ _/ _/ \ | \/ \ / | \ |/ / |/ \/ \_ \ ______/ |\_____/|_____ /_________/ \___________/ \______/ -\____|----\______|-------------\___/------------------------\______|---[ß] v2.3 · The Most Excellent Hard Drive Protection Program Available? · ğ CREDITS Ğ Original Idea & Concept - Mike Carter cODED bY ßudda/NFA gRAFIX bY ßudda/NFA sOUND eFFECTS fROM Public Domain iNSTALLER sPEECH bY Mĝz bETA tESTING & gENERAL hELP bY Mĝz @{" Contents " LINK CONTENTS} @ENDNODE @NODE CONTENTS "Contents" @{bg fill} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} e n L O C K S Y S T E M M E N U @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{" " LINK STUFF_MENU} : Stuff To Read @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{" " LINK SETUP_MENU} : Getting enLOCK Going @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{" " LINK NFA} : NFA Gubbins @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg fill} @{bg back} @{bg text} @{bg back} @{bg fill} @{fc text}@{bg back} @ENDNODE @NODE STUFF_MENU "`Stuff' Contents" @{bg shine} @{bg back} @{bg shine} @{bg text} @{bg shine} @{bg back} @{bg shine} @{bg text} @{bg back} e n L O C K S T U F F M E N U @{bg text} @{bg shine} @{bg back} @{bg shine} @{bg text} @{bg back} @{bg text} @{bg shine} @{bg back} @{bg shine} @{bg text} @{bg back} @{bg text} @{bg shine} @{bg back} @{bg shine} @{bg text} @{bg back} @{" " LINK READ} : Important - Read Me @{bg text} @{bg shine} @{bg text} @{bg back} @{bg shine} @{bg text} @{bg back} @{" " LINK SHAREWARE} : Shareware Information @{bg text} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg back} @{bg shine} @{bg text} @{bg back} @{" " LINK FEATURES} : enLOCK Features @{bg text} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg back} @{bg shine} @{bg text} @{bg back} @{" " LINK PROBLEMS} : Bugs, Problems, Limitations @{bg text} @{bg shine} @{bg fill} @{bg back} @{bg shine} @{bg text} @{bg back} @{" " LINK HISTORY} : Version History @{bg text} @{bg shine} @{bg fill} @{bg back} @{bg shine} @{bg text} @{bg back} @{" " LINK ABOUT} : The Author & The Program @{bg text} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg back} @{bg shine} @{bg text} @{bg back} @{bg text} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg back} @{bg shine} @{bg text} @{bg back} @{bg text} @{bg shine} @{bg text} @{bg back} @{bg shine} @{bg text} @{bg shine} @{bg back} @{bg shine} @{fc text}@{bg back} @ENDNODE @NODE SETUP_MENU "Setup Contents" @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} @{" " LINK INSTALL} : Installing enLOCK @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{" " LINK UNINSTALL} : Un-Installing enLOCK @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{" " LINK ACCESS} : Controlling Computer Access @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{" " LINK PREFS} : Preference Setting @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg back} @{bg fill} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg back} @{bg shine} @{bg back} @{bg text} @{bg fill} @{bg back} @{bg fill} @{bg text} @{bg fill} @{bg shine} @{bg fill} @{bg back} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg back} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg shine} @{bg back} @{bg fill} @{bg back} @{bg shine} @{bg fill} @{bg back} @{bg fill} @{bg shine} @{bg fill} @{bg text} @{bg shine} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg shine} @{bg text} @{bg shine} @{bg fill} @{bg text} @{bg back} @{bg shine} @{bg text} @{bg fill} @{bg shine} @{bg fill} @{bg back} @{bg fill} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg back} @{bg fill} @{bg text} @{bg fill} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg shine} @{bg back} @{bg shine} @{bg fill} @{bg shine} @{bg back} @{bg shine} @{bg fill} @{bg text} @{bg shine} @{bg back} @{bg shine} @{bg fill} @{bg text} @{bg back} @{bg shine} @{bg fill} @{bg text} @{bg back} @{bg fill} @{bg shine} @{bg text} @{bg shine} @{bg text} @{bg back} @{bg fill} @{bg text} @{bg shine} @{bg text} @{bg fill} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg back} @{bg fill} @{bg shine} @{bg fill} @{bg shine} @{bg fill} @{bg text} @{bg fill} @{bg back} @{bg fill} @{bg text} @{bg fill} @{bg back} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg fill} @{bg text} @{bg back} @{bg text} @{bg back} @{bg text} @{bg back} @{bg text} @{fc text}@{bg back} @ENDNODE @NODE READ "Important - Read Me" ---------------------------------------------------------------------------- IMPORTANT - READ ME ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ I've spent a while now developing enLOCK and improving it bit by bit. The time thats been used to produce enLOCK could have been used doing other projects which I've got 'half-done' but I decided to stick it out with enLOCK because it was a program which the PD was lacking a decent version of. For this reason I'm releasing it as @{"shareware" LINK SHAREWARE}. You may freely distribute the complete disk either as a standard copy or a DMS (or simular) file. The registered key-files may NOT be distributed to/by ANYONE for ANY reason. Doing so is against the copyright law! All registered key-files must be obtained from me only at the address in the @{"shareware section" LINK SHAREWARE}. PD libraries may sell enLOCK for no more than a fee of £1.25 (or foreign equivalant) to cover the cost of a disk, copying and postage/packaging. WHAT IS enLOCK? ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ A program to protect your hard drive to certain degree from other computer users. It will not allow anybody to pass unless a correct name and password have been entered. The level of protection is better than anything currently available but it is NOT amazing and any knowledgable Amiga user could get past it. However parents, brothers/sisters, friends etc., will all be stuffed when trying (unless they know about Amiga stuff!!). I've had some people saying "oh it's crap, the protection is really stupid." well I say "It only looks stupid to YOU because you can see how really good it is compared to anything you could have thought of." ...in other words ... "Your jealous!" (help my head is swelling!!). @{" " LINK FEATURES} enLOCK V2.3 Feature List **************************************************************************** LOOK! enLOCK (unregistered) CAN NOW BE FREELY INCLUDED ON ANY CD-ROMS! **************************************************************************** ---------------------------------------------------------------------------- @ENDNODE @NODE INSTALL "Installing enLOCK" ---------------------------------------------------------------------------- INSTALLING ŻŻŻŻŻŻŻŻŻŻ An install script has been provided for use with the Commodore Installer utility. This will setup your system for enLOCK to operate in when you next reboot. The installer will require a hardware device to install too. This will probably be one of your hard drive partitions. i.e. DH0:, DH1:, Work: etc. Make sure the device you choose IS available when the machine is turned on and NOT when it has been mounted/installed by software. THIS IS AN IMPORTANT POINT! The installer will alter your "S:Startup-Sequence" too. Virus Checkers may consider this to be a sign of a virus. Don't worry! Just ignore it. The original "S:Startup-Sequence" file is backed up under the name "S:Startup-Sequence.enbak". Only the top line of your "S:Startup-Sequence" file is changed so don't worry about loosing setups etc. The installer will also allow you to setup your preferences for enLOCK to use. These settings may be altered at a later time using the seperate @{"Preferences Editor" LINK PREFS}. Make use of the installers HELP button whenever possible as it provides useful information about the operation you are about to do. NOTE: It is completely STUPID to install enLOCK to floppy disk! Although it WILL FIT it will slow down the log-on and will mean that the disk must be kept write enabled at all times. However you could install to floppy as a test to see what enLOCK is like. The install, un-install and The Preference Editor are NOT installed onto your hard drive. This is to prevent un-wanted people un-installing enLOCK from your system and changing the setup. You may run the un-install script and Preferences Editor straight from the installation floppy disk. **************************************************************************** ** ** ** If you are a previous user of enLOCK (<2.0) then PLEASE make sure you ** ** UN-INSTALL the old version completly using the OLD un-installer ** ** (enLOCK_Destroyer.exe)or else this new version may not be completely ** ** installed correctly! This is not my fault but more of the new ** ** installer script. ** ** ** **************************************************************************** ---------------------------------------------------------------------------- @ENDNODE @NODE UNINSTALL "Un-Installing enLOCK" ---------------------------------------------------------------------------- UN-INSTALLING ŻŻŻŻŻŻŻŻŻŻŻŻŻ If you wish to remove enLOCK at any time an install (or should that be un-install?!) script has been provided. It's seperate from the install script but uses the same Commodore Installer program. All you have to do is confirm the un-installation of certain files and it will do it in an instant. Your "S:Startup-Sequence" will be restored to the original one which was backed up when you installed enLOCK. If you have altered you current "S:Startup-Sequence" file since you installed enLOCK then make sure you SKIP the un-install section which alters your "S:Startup-Sequence" file and do the following steps instead: 1) Start an ASCII text editor 2) Load up "S:Startup-Sequence" 3) Remove the first line 'SYS:Utilities/enLOCK.exe' 4) Save "S:Startup-Sequence" over the old one These steps will prevent you from loosing your current setup. ---------------------------------------------------------------------------- @ENDNODE @NODE ACCESS "Controlling Computer Access" ---------------------------------------------------------------------------- CONTROLLING COMPUTER ACCESS ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ enLOCK allows you to set up an infinte list of users that can access your machine. No limits are put onto you, only that of storage space for each user. enLOCK generates a drawer and a small data filefor each user which is required to allow access for the user. To access the set-up menu of enLOCK you need to know the password. When you first install enLOCK onto your hard drive the default password has to be used. THE DEFAULT PASSWORD IS: password So to access the set-up menu enter the user name as 'enlock' and the password as 'password'. You will now be presented with a menu. The following options are available: @{"ADD NEW USER" LINK ADDNEWUSER} @{"KILL USER" LINK KILLUSER} @{"SETUP PASSWORD" LINK SETUPPASSWORD} RESET COMPUTER @{"USER TIME BAND" LINK USERTIMEBAND} EXIT To select an option use the up/down cursor keys to move the cursor on the left of the menu. Press return/space to select the option. @{"ADD NEW USER" LINK ADDNEWUSER} - To allow a new person to access your machine they will need to be setup on the system. @{"KILL USER" LINK KILLUSER} - If an existing user is no longer allowed access to the machine he/she may be removed. However you will need to know the password of the user before removal can be performed. @{"SETUP PASSWORD" LINK SETUPPASSWORD} - To access the setup menu you require a password. RESET COMPUTER - If for some reason you wish to restart your machine? @{"USER TIME BAND" LINK USERTIMEBAND} - Specifiy the times between which an individual user may log-on. EXIT - Return to the log-on screen. All changes are effective immedietly! TIP: To save typing 'enlock' every time to enter the 'setup' menu you may press F1 and the user name 'enlock' will be automatically entered for you and all that is needed is your access password. ---------------------------------------------------------------------------- @ENDNODE @NODE ADDNEWUSER "enLOCK Setup - Add New User" ---------------------------------------------------------------------------- If more than just yourself need access to the machine which has enLOCK installed on them multiple users may be added. Each user requires two things; a user name/identity and a password. When adding a new user you will be prompted for the name of the new user. Then you will be required to enter the password (The keys pressed will be represented as X's on screen for security). Once the password has been entered you will be asked to repeat it for verification, just incase you typed it wrong the first time! A maximum of 23 characters can be used for both the user name and the password. This is not a limit of enLOCK's system but more of the screen font! I like to blame things on anything but myself! The limit to the total users is, err, unlimited! It works by storing each user as a seperate directory on your hard drive so only your hard drive space limits enLOCK! All files are stored individually to avoid confusion. ---------------------------------------------------------------------------- @ENDNODE @NODE KILLUSER "enLOCK Setup - Kill User" ---------------------------------------------------------------------------- If an existing user is no longer allowed access to the machine he/she may be removed from the system. Simply select the desired user name from the scrolling menu and hit return! When the user next attempts to log-on enLOCK will refuse access and explode! If a user is killed it is instant. Everything is removed including any saved files in the users directory! Please make sure anything important has been backed up FROM the @{"USER: area" LINK USERAREA}. ---------------------------------------------------------------------------- @ENDNODE @NODE SETUPPASSWORD "enLOCK Setup - Setup Password" ---------------------------------------------------------------------------- To access the setup menu when enLOCK was first installed you have to use 'password' as the password. However 'password' is known by everybody as it is in these documents!! This option allows you to alter the password; and functions just like entering a password for a new user. The password will have to be repeated for verification. ---------------------------------------------------------------------------- @ENDNODE @NODE USERTIMEBAND "enLOCK Setup - User Time Band" ---------------------------------------------------------------------------- Selecting this option will present you with a scrolling lister in which you can specify the user yo wish to edit. Simply use the cursor keys to select the user and then hit return/space to edit his/her time band. You will now be presented with a screen to adjust the earliest time at which the user can log-on. ** PLEASE NOTE THAT THE TIME IS IN 24 HOUR FORMAT! ** Instructions on how to adjust the time setting are on the screen but for information they are as follows: · Left/Right cursor keys will swap between the hours and minutes. Which ever part of the time is currently selected will be enclosed in a white box. HH MM · Up/Down cursor keys will increase/decrease number inside the highlight box. Once you have adjusted the earliest time setting the screen will be presented for you to adjust the latest time you may log-on. Please note that this is the latest time you can log-on through enLOCK and not the latest time you can use your computer untill. If you are already logged on just before the latest set time nothing will happen if you are still on after the set time and you may continue to use the computer. If you set the earliest and latest log-on times to 0000 then the user will be able to log-on at ANY time which is the default setting when a @{"new user" LINK ADDNEWUSER} is added to the system. This function has a minor @{"bug" LINK PROBLEMS}! ---------------------------------------------------------------------------- @ENDNODE @NODE PREFS "Preferences" ---------------------------------------------------------------------------- PREFERENCES ŻŻŻŻŻŻŻŻŻŻŻ The enLOCK system can be configured to your personal taste. Several options are provided which will give you extra features for the standard log-on. These preferences can be set first of all during the installation of enLOCK. They can then be later altered by using the seperate Preferences Editor supplied. To make changing the preferences by somebody else harder the Preferences Editor is NOT installed along with the rest of the enLOCK system. The editor will remain and work straight from the installation floppy disk. SOUND EFFECTS - Will give you speech and sound effects which make an excellent atmosphere! MEMORY VECTOR CHECK - Provides a simple virus checker that will scan the memory vectors for anything abnormal. If something is found you are given the option of destroying it with a cold reboot. MAKE ACCESS LOG - Records every user which attempts to log on to your computer. It creates a log file in the S: directory called 'enLOCK_aCCESS.Log'. This provides information on the user name used, attempted password, time and date. If the person logs on succesfully then the password is replaced with a line of X's to hide the valid password. DISABLE SETUP MENU - Once you have configured enLOCK with the users you may disable the internal setup menu from everybody. This is an extra security just incase somebody gets hold of the setup password before you can change it. SPEED UP LOG ON - If you want the hard drive protection but not the fancy effects this option will skip them and get down to the actual logging on. ---------------------------------------------------------------------------- @ENDNODE @NODE STARTUP "User Startup-Sequences" ---------------------------------------------------------------------------- USER STARTUP-SEQUENCES ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ NOTE: A good knowledge of AmigaDOS is required to use this function properly Once a new user has been added to enLOCK it is possible to give the user his/her own startup-sequence which will be executed after access has been granted. Creating an individual startup-sequence is exact the same as doing a standard one. Load up your favourite text editor and write out a script file which can be executed at boot-up. In this alternative startup-sequence make sure you include any assigns which will be required. Once you have created your own startup-sequence for a user put it into the USER: area under the file name "Startup.User". You will find the @{"USER:" LINK USERAREA} assignment will be created after a sucessful log-on. Alternatively you may save the "Startup.User" direct into the directory. To do this locate the DEVICE on which you installed the enLOCK data files on. In the ROOT directory enter the "enLOCK_Users" directory and select the users directory inside this. Now save the file as normal. enLOCK always executes a "Startup.User" script before the program quits so the script will be performed BEFORE the start of the "startup-sequence". This is why it is important to make sure you make any assigns etc. in your OWN "User.Startup". It would be sensible to copy the standard "startup-sequence" into a different place, or simply rename it. Then replace the current "startup-sequence" with just: > SYS:Utilities/enLOCK.exe > EndCLI This will run enLOCK then do nothing. If a user is validated they can ALL have their own startup-sequences ("User.Startup") which can do different things. e.g. Your brother/sister could have a menu automatically loaded up with access to just your hard drive installed games; or your Dad could have a wordprocessor loaded up automatically! The possabilities are endless!! If you wanted a standard log-on you could make a small "User.Startup" which simply said something like: > Execute S: > EndCLI And that would run the original [renamed] startup-sequence as if it was a normal bootup for just one user. oOo All the above *may* sound complicated. Maybe it's just I'm no good at explaining the feature but there's so much I could say about it. Just practice with the feature you should be able to find some use for it as there are no restrictions. ---------------------------------------------------------------------------- @ENDNODE @NODE SHAREWARE "Shareware Information" ---------------------------------------------------------------------------- SHAREWARE ŻŻŻŻŻŻŻŻŻ enLOCK is NOT Public Domain. It's Shareware, that is you can use it for a month and then either REGISTER your version or @{"REMOVE" LINK UNINSTALL} enLOCK from your hard drive. The choice is yours. I leave my trust in you to follow this rule. The unregistered version of enLOCK has a couple of requesters. When enLOCK is started a requester will pop-up telling you that the program is un-registered. Then once a user has logged on a different requester will pop up which has a timer bar on it. You will then have to wait 30 seconds until the computer will continue to boot-up. When you enter the setup menu and then exit it you will also have to wait 30 seconds. Hopefully this annoy users into registering with me. A valid key-file will remove the requesters and enLOCK will work without hinder. This unregistered version doesn't lack any features as I wanted you all to use them and see the FULL program without any crippled bits. REGISTERING ŻŻŻŻŻŻŻŻŻŻŻ From version 2.0 enLOCK operates with a Key-File system. enLOCK will only operate without delays when you have your own 'key-file' in the L: directory of your hard drive. To obtain a personalised key-file for use ONLY by you, registration is required. I charge £5 to allow you to use enLOCK fully. Thie registration fee will keep me happy and push me on to adding more to enLOCK for future versions. Each key-file has your own name and postcode encrypted into it. Altering or fiddling with the file via a binary editor (e.g. FileX) will corrupt it as there are quite a few checksums built in to make the key-file extra safe. This is not a reason to give you crackers a challenge; just don't do it! Please, please withhold from distributing your own key-file. If you do so, even by accident then I will make sure something happens :-) !!! If you want to support enLOCK then do so nicely, try registering or suggesting improvements! UPDATES ŻŻŻŻŻŻŻ When new versions of enLOCK are released I will distribute them in the public domain and try to get them spread on various BBS's. Everybody may distribute the enLOCK archive as long as it is either a DMS (or similar file) or the unpacked disk. Please feel free to upload it onto the Aminet ,as I'm unable to, and also as many BBS's as possible. I will put adverts in NFA's disk magazine "The Word" when new versions of enLOCK have been released. This way you will know by just getting hold of the latest issue of "The Word" from any good PD Library. It will save me a lot of money (which I don't have) and also make it easier to get updates to everyone. If you want to get the latest update of enLOCK (Britain Only! Sorry) then you will need to write to me. Enclose a short letter, a disk and a return stamp. ßudda/NFA "Bradda" Crowborough Road Georgeham North Devon EX33 1JZ All disks (with stamps) will be returned *hopefully* the same day. Please allow upto three days though, you never know what might happen :-) But updates wont just happen! I need input from the users to give you what you want (within reason). IMPROVEMENTS ŻŻŻŻŻŻŻŻŻŻŻŻ Yep that's right, I want new suggestions for enLOCK. Where should I go next with it? Here's my personal list of goals for the future of enLOCK. Some are more realistic than others but are good ideas (I think!). * Disable HD partitions not available to certain users (not sure how to do this yet!! but it would be excellent) * Utility to install "Startup.User" scripts via a nice interface * Welcome speech for different times of day (using your built in clock!) * Adjustable sounds, a choice of different types. * Iron out any bugs reported by YOU! Please feel free to send your ideas to me. Best to send them along with your registration fee so that I will be able to respond to them when sending your key-file. Everything will be read; although immediate replies will not be possible as I've got college work 'n' stuff to do at the same time now! RE-CAP ŻŻŻŻŻŻ So registering gets you:- * Personalised Key-File * Free updates for future versions (with proof of already registered) * Disk containing latest version of enLOCK & key-file * Help when ever you need it; via snail mail only at the moment :-( ---------------------------------------------------------------------------- @ENDNODE @NODE NFA "NFA Gubbins" ---------------------------------------------------------------------------- NFA GUBBINS ŻŻŻŻŻŻŻŻŻŻŻ Okay NFA are still a sniffin' for good gfx artists and musicans aswell as totty coders in any language (even AMOS and Blitz if you can get good things from them!). If you wish to attempt to gain membership then you just stuff a disk or two with some of your own work and send with an intro letter to this address:- NFA P.O Box 42 Grimsby South Humberside DN33 1RY Don't forget that you can pick up all the latest NFA productions/updates aswell as the other latest scene warez from this NFA birdy: .______________________________________. .____________( )____________. .____( Ż Ż )____. | Ż Ż | | iT suRE wOZ hERE sOME tIME iN itS tRAVelS...nOW yOu cAN geT heRE tO! | | _____ __ _____ __ __ ______ _____ ______ | | -ThE-/. \--/. \-/. \-----/. \/. \-/. \-/. \--/. \-- | (_ ....// / _/.// /// / /....// // /_\\_/ /// / _/.// / /.. _) _) :::/ \:/ // /__/::::/ __ // // \:/ / /::: (_ ( / / // // / /Ż / / // / // / // / / ) | --\______/-\__/-\______/----\__/\__/-\______/-\__/\__/-\______/-ONE- | | | | Sysop : Deck The Ripper/NFA · A4000 · 030 CPU · 50Mhz FPU · 34Mb RAM | |_. 2 CD-ROM's On-Line · 2.9 Gig HD · 14,440 Speedz · Open 8pm - 8am ._| | | (___________________. ğ +44 (0)1530 260160 Ğ .___________________) (______________________________) [ß] ---------------------------------------------------------------------------- @ENDNODE @NODE PROBLEMS "Bugs, Problems, Limitations" ---------------------------------------------------------------------------- BUGS ŻŻŻŻ The user time band function will not work correctly if you set the latest time after midnight (0000 hrs) as this is the next day. Your latest time setting MUST be greater than your earliest time setting or else enLOCK will not see it logically. At the moment I haven't got round to fiddling with it but if you keep away from stupid times (i.e. 0930 until 0230) then enLOCK will function perfect with this feature. Also remember that people without a battery backed clock should not use this feature! When selecting a time avoid using the number 59 for minutes as this corrupts the time bands when saved and will generally lock you out of your pooter the next time you attempt to log in!! DISK EXPANDER ŻŻŻŻŻŻŻŻŻŻŻŻŻ This can present a BIG problem. enLOCK is run before anything else in the startup-sequence so, you guessed it, Disk Expander isn't running and so any files cannot be unpacked. enLOCK requires access to a number of data files to operate. If the files are crunched when it tries to access them it will probably present you with an error or just a simple crash out. To fix the problem you can do one of two things when installing enLOCK on your system. (1) Install the 'enLOCK_Users' data directory on a HD partition that doesn't have Disk Expander installed on it. (2) Install enLOCK on the HD and then alter the startup-sequence by hand and place the DExpander line before the enLOCK line. This will start Disk Expander first and then enLOCK straight after. Like anything else there's bound to be some new bugs that have appeared as I've added more features. To keep the bugs at bay and to kick them as soon as possible PLEASE report them when ever possible. TESTING ŻŻŻŻŻŻŻ Amiga 1200 - 4Mb Fast RAM · 260Mb HD · 2 externals · CD-ROM Amiga 1200 - Standard Amiga 1200 - 120Mb HD · 1 external · Disk Expander Software Amiga 1200 - 1.2GIG HD Amiga 1200 - 0Mb HD(!!) [floppy disk] Thanks To The Following For Testing/Bug Reports & Help: John Pexman, Gavin Lilley, Ralph & His Mate and Jamie Morris. ---------------------------------------------------------------------------- @ENDNODE @NODE HISTORY "Version History" ---------------------------------------------------------------------------- HISTORY ŻŻŻŻŻŻŻ v1.0 (11/06/95) - First release to beta tester boy. v1.1 (12/06/95) - Bug fixes. Improved installer. v1.2 (13/06/95) - Major installer change. Protection improved. A new sound sample added when access denied. Another few bug fixes. v1.3 (14/06/95) - They Don`t Stop! Another bug fix with cursor. This version is sent to some people including 17-Bit Software. OOOps! v1.4 (24/06/95) - Arrrggg! Silly mess-up with enLOCK set-up access; linked to above cursor thing! A small bug when removing enLOCK from your HD fixed too! v1.5 (31/07/95) - More features added from suggestions. To remove enLOCK a seperate program is now used. Each user can have an individual startup- sequence if required. Fuzz added to terminal if left on for a minute. Installer is tidyed up and adjusted for new protection enhancments. More sound added (siren). Docs adjustment. v1.6 (16/09/95) - NEVER RELEASED. Docs update. Visual tidy up and additional graphical effects added. v2.0 (01/10/95) - Recoded registration (added Key-file). Completely re-written HD Installer. New preferences editor for 5 new preferences (which can be changed at any time) Brand new docs in AmigaGuide. v2.1 (02/11/95) - Code made less crackable! New GFX effects added & Sound effect. Protection improved once more! Fixed installation bug with "S:Startup-Sequence". v2.2 (29/01/96) - Speech added to installer. Code made even less crackable! Prefs Ed & Installers Improved too. Compiled code size has shrunk!! New time band selector so no mouse required! v2.3 (02/02/96) - Slight program version mix-up fixed! So far code is un-crackable! - At long last! ---------------------------------------------------------------------------- @ENDNODE @NODE ABOUT "The Author & The Program" ---------------------------------------------------------------------------- THE AUTHOR ŻŻŻŻŻŻŻŻŻŻ I coded it aswell as drawing the small amount of graphics. Me, who am I? Well I'm Mike [ßudda/NFA] and have been plodding around in AMOS Pro for about nearly three years now (I think). I'm half way through my first year on a course at College. BTEC National Diploma in Information Technology (no crap A-Level stuff for me!!) if you really wanted to know. I'm seventeen too and I'll be eighteen (logically) next. I spend most of my life at my pooter coming up with little creations what have been 'wished' as it were by others. Which is just how this whole enLOCK project began... THE PROGRAM ŻŻŻŻŻŻŻŻŻŻŻ Originally it was a (sort of) mate who cried at all the hard drive protection programs I sold him from my PD collection. They were 'shit' he said and not much use as they were easy to get past and looked really CRAP. So I though about it for a week and then declared I would try to make something better. After spending a few nights sleeping on ideas of how I could make the protection better; it started. enLOCK began as just a standard interface which looked nice and not much else. I then added the new form of protection which actually involved removing a certain program from your HD to stop it from working unless you entered a correct password. Then as the versions progressed I got some feedback saying it was 'the best available' and 'looked really kewl'. This got me chuffed so I made it better again by improving the protection. Soon a few people registered and that is where it stopped ... for a while. Then after getting into college and all that hassle and shit put out of the way I started up again with enLOCK. The idea of preferences had been swilling around for a while so in September I put it into reality. I then spent a while trying to write a decent installer using the Commodore utility. Now that it's all done, the project has arrived in a new form. Complete with an optional registered key-file involving complex check-sums to help protect it against being hacked (well only in theory!). Later on, November I think, a wee lad came along to have a bash at hacking enLOCK. Because I knew the munchkin I didn't mind and was intrested to see if he could do it. He started hacking at v2.0 of enLOCK and after 2 hours he had made the program ignore the registered key-file completely, turning it into the registered version! Well I wasn't going ot stand for that so I set to work attempting to make it harder - encrypion of the important strings inside the programs executable file was the only way to do it. After this was done I gave the new version to him. Within 15 minutes he had kicked it in again!! This dongle man was a pro or summin'! I was quite chuffed when a really good program arrived which claimed to be able to password protect a crunched executable file. This was wetting my @{fg shine}pants@{fg text} (hi Mĝz!) and I was eager to give it a go. I crunched my AMOS compiled executable file and then password protected it. I ran the new protected executable and, er, it worked ... sometimes. But there must have been some sort of problem because it kept crashing once it returned to DOS. So this util was thrown out the window (maybe it is just a problem with AMOS stuff??). What next? I called in the next level of security - even more encryption, and just to confuse him I rearranged the internal program structure so that the executable wouldn't look the same as the old (cracked) one... ...the damn good news is: at the current time he has been unable to hack it!! I've succeeded at last. I've learent a nice lesson from this though: protect your executables because they can be easily changed with "File X" or a similar program!! enLOCK was coded in AMOS Pro v2.0, using the help of some extension commands although not sure which extensions they came from! All graphics and the font were drawn in Deluxe Paint 5 and the sounds were collected from places of which I can't remember; Alien Breed SE is one :-) . They were on my HD already okay! ---------------------------------------------------------------------------- @ENDNODE @NODE USERAREA "The USER: Area" ---------------------------------------------------------------------------- When a user logs on sucessfully a new assign is set up which points to a special area reserved for that user ONLY. Any files that need to be stored safely and seperetly can be placed in this area. Just select USER: from the directory. The assign will ALWAYS be present after a sucessful log-on so you can setup software i.e. to save documents from a wordprocessor to the USER: drive as default. ---------------------------------------------------------------------------- @ENDNODE @NODE FEATURES "Overall Feature List Of enLOCK" ---------------------------------------------------------------------------- @{fg shine}enLOCK V2.3 Features:@{fg text} @{"o" LINK ADDNEWUSER} Unlimited Users o 23 Character long user names/passwords o Impressive User Interface @{"o" LINK PREFS} Sampled Speech And Sound Effects @{"o" LINK PREFS} Memory Vector Checker (Simple Virus Checker & Killer) @{"o" LINK PREFS} Optional Speed-Up For Impatient Users @{"o" LINK USERAREA} Individual USER: areas o Unique Designed Protection @{"o" LINK STARTUP} Individual User Startup-Sequences @{"o" LINK PREFS} Log-File Recording Of EVERY Attempted Access @{"o" LINK USERTIMEBAND} Time Band For Each User To Log-on In o Un-crackable Program Code To Prevent Illegal Versions @{"o" LINK PREFS} Adjustable Preferences @{"o" LINK INSTALL} HD Installer/Un-Installer o Encrypted Password/Stats Files ---------------------------------------------------------------------------- @ENDNODE