@DATABASE "enLOCK Hard Drive Protection Docs" @AUTHOR "Mike Carter" @$VER: "enLOCK Docs v3.0 (29/06/96)" @(c) "©1995/96 NFA Productions" @FONT topaz.font 8 @INDEX INDEX @HELP HELP @SMARTWRAP @REM = nOTE ================================== @REM version number update in nodes: @REM MAIN, READ, INSTALLING, HISTORY, FEATURES @REM ========================================= @NODE MAIN "Welcome" @NEXT CONTENTS @TOC CONTENTS ____ . __________________| \ .____: __________ ______________/¡ _______ / __________ \ \| ¡ / ___ \ / ._______ |/ _/ _/ ____)_ / \ \ \ |___/_ |\ \/ | _____ \ _/ _/ \ | \/ \ / | \ |/ / |/ \/ \_ \ ______/ |\_____/|_____ /_________/ \___________/ \______/ -\____|----\______|-------------\___/------------------------\______|---[ß] v3.0 · The Most Excellent Hard Drive Protection Program Available? · » CREDITS « Original Idea & Concept - Mike Carter @{"cODED bY ßudda/NFA" LINK BUDDA} @{"Additional Stuff By" LINK CONTENTS}@{" Møz " LINK MOZ}@{"&" LINK CONTENTS}@{" Tøølbox " LINK TOOLBOX} @{" Contents " LINK CONTENTS} @ENDNODE @NODE TOOLBOX "About Tøølbox" @TOC CONTENTS ----------------------------------------------------------------------------- Real Name: Andrew Ballard Handle: Tøølbox/iNDi Age: 17 Occupation: Student Work included in "enLOCK": Bug Fix Suggestions & Example Code Beta Testing Ballard Quote 'Got any warez for me?' ----------------------------------------------------------------------------- @ENDNODE @NODE MOZ "About Møz" @TOC CONTENTS ----------------------------------------------------------------------------- Real Name: Jamie Morris Handle: Møz/iNDi Age: 18 Occupation: Student Work included in "enLOCK": Speech Styles - 'Robocop' and 'Devonshire' Installer Speech - All of it! Cracking of registration Beta Testing Morris Quote 'I want my name in the credits.' ----------------------------------------------------------------------------- @ENDNODE @NODE BUDDA "About ßudda" @TOC CONTENTS ----------------------------------------------------------------------------- Real Name: Mike Carter Handle: ßudda/NFA Age: 17 Occupation: Student Work included in "enLOCK": All Programming All Graphics Some Sound Effects Installer Script Instruction Guide Carter Quote 'Sorted. Got any clipart?' ----------------------------------------------------------------------------- @ENDNODE @NODE CONTENTS "Contents" @PREV MAIN @TOC CONTENTS __________ ____________ ____________ ____________ ____________ ___/ \_/@{" Read Me " LINK READ}\_/@{" Shareware " LINK SHAREWARE}\_/@{" Features " LINK FEATURES}\_/@{" Bugs " LINK PROBLEMS}\__ __/ @{b}CONTENTS@{ub} \_____________________________________________________________ .______________. @{" Read This First " LINK READ} @{"Full Index " LINK INDEX} @{fg shine}<@{fg text} | | @{" Shareware Info " LINK SHAREWARE} @{"System Requirements" LINK REQUIRE} @{fg shine}<@{fg text} | fILE: enLOCK | @{" About Program " LINK ABOUT} @{"Problem Solving " LINK FAQ} @{fg shine}<@{fg text} | | @{" Features " LINK FEATURES} @{fg shine}<@{fg text} )>------------<( @{" Installing " LINK INSTALL} @{fg shine}<@{fg text} | wRITTEN bY | @{" UnInstalling " LINK UNINSTALL} @{fg shine}<@{fg text} | | @{" Preferences " LINK PREFS} @{fg shine}<@{fg text} | @{"ßudda/NFA" LINK BUDDA} | @{" Bugs " LINK PROBLEMS} @{fg shine}<@{fg text} )>------------<( @{" Controlling Access " LINK ACCESS} @{fg shine}<@{fg text} | | @{" enLOCK Toolz " LINK TOOLZ} @{fg shine}<@{fg text} | ©1996 NFA | @{" N·F·A! " LINK NFA} @{fg shine}<@{fg text} `--------------' @{" Other Programs " LINK OTHERHDPROGS} @{fg shine}<@{fg text} @{" History " LINK HISTORY} @{fg shine}<@{fg text} `---------------------------------------------------------------------------' @ENDNODE @NODE READ "Important - Read Me" @TOC CONTENTS ___________ ___________ ____________ ____________ ____________ ___/@{" Contents " LINK CONTENTS}\_/ \_/@{" Shareware " LINK SHAREWARE}\_/@{" Features " LINK FEATURES}\_/@{" Bugs " LINK PROBLEMS}\__ ________________/ @{b}READ ME@{ub} \______________________________________________ WHAT IS enLOCK? ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ A program to protect your hard drive to a 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!! hehe). IMPORTANT NOTE ¯¯¯¯¯¯¯¯¯¯¯¯¯¯ 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 similar) 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. @{" " LINK FEATURES} enLOCK V3.0 Feature List @{" " LINK REQUIRE} System Requirements @{" " LINK INSTALL 42} Another Important Point! ***************************************************************************** LOOK! enLOCK (unregistered) CAN NOW BE FREELY INCLUDED ON ANY CD-ROMS! ***************************************************************************** `---------------------------------------------------------------------------' @ENDNODE @NODE REQUIRE "System Requirements" @TOC CONTENTS ----------------------------------------------------------------------------- enLOCK was designed and coded on an A1200 so it should work on all A1200's !! HD Space = 0.5 Mb Memory = 2 Mb Chip CPU = 68000 Basically it's created for an A1200 but *should* work on an A4000 too. Please mail me if it does!! @{" " LINK PROBLEMS 55} - Tested machines ----------------------------------------------------------------------------- @ENDNODE @NODE INSTALL "Installing enLOCK" @TOC CONTENTS ----------------------------------------------------------------------------- INSTALLING ¯¯¯¯¯¯¯¯¯¯ An install script has been provided for use with the new "Amiga Technologies Installer" utility. You will require the program to be already installed on your hard drive and available in the current search path (i.e. in your 'C:' or 'Utilities/' directory) To begin the installation choose @{fg shine}'Complete Installation'@{fg text} from the installer menu. 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/scripts. @{b}THIS IS AN IMPORTANT POINT!@{ub} 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 by chosing 'Alter Preferences' from the installer menu. 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. Make sure you boot up from the disk you want to install it onto and ensure that the "Commodore Installer" utility is available on the disk too! The installer script is 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 installer script to change the @{"preferences" LINK PREFS} or @{"un-install" LINK UNINSTALL} "enLOCK" straight from the installation floppy disk. ***************************************************************************** ** ** ** If you are a previous user of enLOCK (<3.0) then PLEASE make sure you ** ** UN-INSTALL the old version completly using the OLD un-installer ** ** or else this new version may not be completely ** ** installed correctly! This is not my fault but more of the new ** ** installer script. Is it my fault then?? ** ** ** ***************************************************************************** ----------------------------------------------------------------------------- @ENDNODE @NODE UNINSTALL "Un-Installing enLOCK" @TOC CONTENTS ----------------------------------------------------------------------------- UN-INSTALLING ¯¯¯¯¯¯¯¯¯¯¯¯¯ If you wish to remove enLOCK at any time simply click on the "enLOCK" install icon and select the @{fg shine}'Complete Un-Installation'@{fg text} choice from the installer menu. 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 @{b}since@{ub} you installed "enLOCK" then make sure you @{b}SKIP@{ub} the un-install section which alters your "S:Startup-Sequence" file and do the following steps instead by hand (mouse?): 1) Start an ASCII text editor ( ED, CygnusED, GoldED etc... ) 2) Load up "S:Startup-Sequence" 3) Remove the first line 'SYS:System/enLOCK' 4) Save the new "S:Startup-Sequence" over the old one These steps will prevent you from loosing your current setup. If you get in a pickle and can't boot from your hard drive to un-install "enLOCK" you can use the emergancy un-installer by booting from the "enLOCK" disk and clicking the mouse at the prompts. You will be required to show the un-installer which partition you boot from so that the script can move the system assigns to your hard drive in order to operate correctly. ----------------------------------------------------------------------------- @ENDNODE @NODE ACCESS "Controlling Computer Access" @TOC CONTENTS ----------------------------------------------------------------------------- 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: @{fg shine}password@{fg text} So to access the set-up menu enter the user name as '@{fg shine}enlock@{fg text}' and the password as '@{fg shine}password@{fg text}'. 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" LINK SETUPPASSWORD}. ----------------------------------------------------------------------------- @ENDNODE @NODE ADDNEWUSER "enLOCK Setup - Add New User" @TOC CONTENTS ----------------------------------------------------------------------------- ADD NEW USER ¯¯¯¯¯¯¯¯¯¯¯¯ If more than just yourself need access to the machine which has enLOCK installed on then 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 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" @TOC CONTENTS ----------------------------------------------------------------------------- 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! You will be asked for verification before any deleting commences :-) 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" @TOC CONTENTS ----------------------------------------------------------------------------- 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 this document!! 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" @TOC CONTENTS ----------------------------------------------------------------------------- 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. ----------------------------------------------------------------------------- @ENDNODE @NODE PREFS "Preferences" @TOC CONTENTS ----------------------------------------------------------------------------- PREFERENCES ¯¯¯¯¯¯¯¯¯¯¯ The "enLOCK" system can be configured to your personal taste. Several options are provided which will give you extra features on top of 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 selecting the @{fg shine}'Alter Preferences'@{fg text} choice from the "enLOCK" installer menu. supplied. @{"SOUND EFFECTS " LINK SNDFX} @{"MEMORY VECTOR CHECK" LINK MEMVECT} @{"MAKE ACCESS LOG " LINK ACCLOG} @{"DISABLE MENU " LINK DISMENU} @{"SPEED UP LOG-ON " LINK SPEON} @{"GREETINGS " LINK GREETINGS} ----------------------------------------------------------------------------- @ENDNODE @NODE SNDFX "Preferences - Sound Effects" @TOC CONTENTS ----------------------------------------------------------------------------- SOUND EFFECTS - Will give you @{"speech" LINK SPEECH} and sound effects which make an excellent atmosphere! Once the PROCEED button is clicked a selection of different sound types to choose from appear. Each type is a different backing sound so you can select the one to fit with your room's atmosphere! hehe. The selection is: Metallic Thump [oRIGINAL] Distant Grown Echo Belly Electrical Pulse ----------------------------------------------------------------------------- @ENDNODE @NODE SPEECH "Preferences - Speech Style" @TOC CONTENTS ----------------------------------------------------------------------------- If you choose to turn sound effects ON then you will also be able to select the 'style' of speech to be used in enLOCK after you have selected the @{"backing sound effect" LINK SNDFX}. Currently, and due to disk space, there are only the following styles: Woman [oRIGINAL] Devonshire Robocop The "Woman" style has only support for the original speech and does not support any GREETINGS if set in your preferences. Both the "Devonshire" and "Robocop" styles have full sampled speech and support all chances of talking in "enLOCK". Future releases of enLOCK may possibly provide more on a seperate 'Extras' disk. ----------------------------------------------------------------------------- @ENDNODE @NODE MEMVECT "Preferences - Memory Vector Check" @TOC CONTENTS ----------------------------------------------------------------------------- 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. ----------------------------------------------------------------------------- @ENDNODE @NODE ACCLOG "Preferences - Make Access Log" @TOC CONTENTS ----------------------------------------------------------------------------- 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. Click @{"HERE" LINK LOGFILE} for an example logfile & explination of it. ----------------------------------------------------------------------------- @ENDNODE @NODE LOGFILE "Log File Explination" @TOC CONTENTS enLOCK 3.0 · Log File Record +-------------------------+-------------------------+-------+----------+---+ ¦ USeR NaMe ¦ ATTeMPTeD PaSSWoRD ¦ TiMe ¦ DaTe ¦ ? ¦ +-------------------------+-------------------------+-------+----------+---+ ¦ mike ¦ wert ¦ 04:00 ¦ 28.04.96 ¦ N ¦ ¦ mike ¦ XXXXXXXXXXXXXXXXXXXXXXX ¦ 04:02 ¦ 28.04.96 ¦ Y ¦ ¦ mike ¦ XXXXXXXXXXXXXXXXXXXXXXX ¦ 04:10 ¦ 28.04.96 ¦ Y ¦ ¦ mike ¦ XXXXXXXXXXXXXXXXXXXXXXX ¦ 12:48 ¦ 28.04.96 ¦ Y ¦ ¦ mike ¦ XXXXXXXXXXXXXXXXXXXXXXX ¦ 14:57 ¦ 28.04.96 ¦ Y ¦ ¦ mike ¦ XXXXXXXXXXXXXXXXXXXXXXX ¦ 16:29 ¦ 28.04.96 ¦ Y ¦ ¦ mike ¦ XXXXXXXXXXXXXXXXXXXXXXX ¦ 22:02 ¦ 29.04.96 ¦ Y ¦ ¦ mike ¦ XXXXXXXXXXXXXXXXXXXXXXX ¦ 22:19 ¦ 29.04.96 ¦ Y ¦ ¦ dazza ¦ XXXXXXXXXXXXXXXXXXXXXXX ¦ 19:13 ¦ 30.04.96 ¦ N ¦ ¦ mike ¦ XXXXXXXXXXXXXXXXXXXXXXX ¦ 19:28 ¦ 30.04.96 ¦ Y ¦ ¦ mike ¦ XXXXXXXXXXXXXXXXXXXXXXX ¦ 19:29 ¦ 30.04.96 ¦ Y ¦ A explination of the logfile header: USeR NaMe - The userID entered in enLOCK ATTeMPTeD PaSSWoRD - The text entered in the password entry. If 23 X's appear (as above) then the password @{b}was valid@{ub} to enLOCK. TiMe - The time a log-on was attempted. DaTe - As above, but the date! ? - Was the user successful at logging on? flag. If password was valid and time was valid then this will be a @{fg shine}Y@{fg text}. If password was valid but user was out of the time band then this column will be a @{fg shine}N@{fg text}. Examples: @{fg fill}Mike@{fg text} attempted to log on with the password @{fg fill}wert@{fg text} at @{fg fill}4:00am@{fg text} on @{fg fill}28th April@{fg text} (I was still programming "enLOCK"!). The password, however was incorrect and so the success flag was set to @{fg fill}N@{fg text} and I wasn't allowed to log on. @{fg fill}Dazza@{fg text} attempted to log onto my machine at @{fg fill}19:13@{fg text} on @{fg shine}30th April@{fg text}. He got his password correct but wasn't allowed to log onto my machine, hence the nasty @{fg fill}N@{fg text}. Why? - well he was outside his @{"timeband" LINK USERTIMEBAND} which had been set by me :-) @ENDNODE @NODE DISMENU "Preferences - Disable Menu" @TOC CONTENTS ----------------------------------------------------------------------------- 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. ----------------------------------------------------------------------------- @ENDNODE @NODE SPEON "Preferences - Speed Up Log-On" ----------------------------------------------------------------------------- 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 GREETINGS "Preferences - Greetings" @TOC CONTENTS ----------------------------------------------------------------------------- Once "enLOCK" has 'connected' to your system you can be welcomed by "enLOCK" in the @{"style of speech" LINK SPEECH} you select. The greeting adjusts itself throughout the day depending on the time of your battery backed clock. Because of the need for a clock it is useless to non owners of a clock! ----------------------------------------------------------------------------- @ENDNODE @NODE STARTUP "User Startup-Sequences" @TOC CONTENTS ----------------------------------------------------------------------------- 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:System/enLOCK > 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" @TOC CONTENTS ___________ ____________ ___________ ____________ ____________ ___/@{" Contents " LINK CONTENTS}\_/@{" Read Me " LINK READ}\_/ \_/@{" Features " LINK FEATURES}\_/@{" Bugs " LINK PROBLEMS}\__ _______________________________/ @{b}SHAREWARE@{ub} \_______________________________ 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 will annoy users into registering with me; not nice but it gotta be done! 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 @{b}only@{ub} 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! I except cheques, postal orders or cash (British Only). Make anything payable to Mike Carter. 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 to 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 who wants one. If you want to get the latest update of enLOCK then you will need to write to me. Enclose a short letter, a disk and a return stamp (25p). ßudda/NFA "Bradda" Crowborough Road Georgeham North Devon EX33 1JZ All disks (with stamps) will be returned *hopefully* the same day. Please allow at least 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!). * Disk-Key as an alternative to a user name & password! * Disable HD partitions not available to certain users (it's still here!) * Utility to install "Startup.User" scripts via a nice interface * More functions on the 'Toolz' bar such as "Windoze 95" style 'Shut-Down' * Iron out any bugs reported by YOU and add any ideas by YOU! * Leave email for other users allowed on system * null-modem/network support (I need a small network for testing on!!) 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 * 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" @TOC CONTENTS ----------------------------------------------------------------------------- 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 @{b}own@{ub} work and send with an intro letter to this address:- Freak/NFA P.O Box 42 Grimsby South Humberside DN33 1RY Don't forget that you can pick up all the latest NFA productions/updates as well as the other latest PD 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)1162 661610 « .___________________) (______________________________) [ß] PLEASE NOTE: This is a @{b}LEGAL@{ub} bulletin board and piracy is not welcome! Do not upload illegal software be it commercial or hacked shareware a sit gives the group a bad name. See CU Amiga March 1996!! ----------------------------------------------------------------------------- @ENDNODE @NODE PROBLEMS "Bugs, Problems, Limitations" @TOC CONTENTS ___________ ____________ ____________ ____________ ___________ ___/@{" Contents " LINK CONTENTS}\_/@{" Read Me " LINK READ}\_/@{" Shareware " LINK SHAREWARE}\_/@{" Features " LINK FEATURES}\_/ \__ _____________________________________________________________/ @{b}BUGS@{ub} \_ ODD (small) BUGS ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ enLOCK bombs out if your harddrive is not validated leaving an open CLI for any hackers. Luckily if you have been using the Toolz bar to reset your machine all will be okay as you can't do much from the CLI! When un-installing enLOCK from Workbench the "enLOCK_Users" directory doesn't get removed although it's contents do (except the current Users directory who logged on. To get around this you may use the emergancy un-installer by booting from the enLOCK disk and clicking the mouse twice at the prompts. DISK EXPANDER & EPU STACKER ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ 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. EXTERNAL CLOCK MODULES ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ Bit of a silly bug this but it was reported by a user. Actually it's not a bug, just an inconvenience. Some of the idiots (yes that's right) that have bought a clock module which plugs into the disk drive port will not be able to use the USER TIME BAND feature. This is because enLOCK is started as the first program in the Startup-Sequence and to use the external clock module a patch has to be started first. If you want to use the USER TIME BAND function then simply edit your S:Startup-Sequence file and put the clock module patch as the very first line, BEFORE the enLOCK line. TESTING ¯¯¯¯¯¯¯ Amiga 1200 - 4Mb · 260Mb HD · 2 external floppies Amiga 1200 - Standard · 0Mb HD(!!) Amiga 1200 - 120Mb HD · 1 external · Disk Expander Software X Amiga 600 - 1Mb · 40Mb HD Amiga 1200 - 2Mb · 1.2GIG HD Amiga 1200 - 6Mb · 420Mb HD · 28Mhz FPU Setups marked with an 'X' didn't work. Thanks To The Following For Testing/Bug Reports & Help: Mon-PD, Darran Wilks, Andrew Ballard, John Pexman and Jamie Morris. And thanks to @{fg fill}Roberta Smith DTP@{fg text} for getting it reviewed in the mags! `---------------------------------------------------------------------------' @ENDNODE @NODE HISTORY "Version History" @TOC CONTENTS ----------------------------------------------------------------------------- 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 adjusted. 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 user list 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! v3.0ß(27/04/96) - Oh dear, oh dear! The last version was a complete muck up. It locked people out of their Amigas!! Big error with cruncher? All Fixed, okay! --- NEW STUFF STARTS HERE --- Choice of backing sound. Improved Installer! Larger program size 157k -> 191k! Updated docs. All listed bugs killed!!!!! Kewl? Added 'Blips' sound in SETUP menu. Installer now does everything no seperate prefs ed & un-installer scripts. Selection of different speech styles! Optional greetings when you log-on! Updated version of WB for all enLOCK users! Brilliant little enLOCK Toolz Bar on WB screen. v3.0 (12/05/96) - Removed corrupt sound bug whish caused enLOCK to crash on some machines! Installers un-install option fixed. enLOCK Toolz Bar can now be hidden if needed and doesn't duff up your HD's hash table! Added a new sound effect for the sake of it. Even larger program size 191k -> 210k! ----------------------------------------------------------------------------- @ENDNODE @NODE ABOUT "About The Program" @TOC CONTENTS ----------------------------------------------------------------------------- THE PROGRAM ¯¯¯¯¯¯¯¯¯¯¯ Originally it was a mate who cried at all the hard drive protection programs I sold him from my PD CD 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 items from the 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 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 learnt a nice lesson from this though: protect your executables because they can be easily changed with "File X" or a similar program!! Recently my key-file got copied by accident for Møz (BIG OOps!) but great news was that he could NOT alter it however hard he tried! Brilliant! So everything is protected now. :-) 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. ----------------------------------------------------------------------------- @ENDNODE @NODE USERAREA "The USER: Area" @TOC CONTENTS ----------------------------------------------------------------------------- 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 seperetly can be placed in this area. Just select USER: from the a file reguseter or type it at the CLI prompt. 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. Please note however that the data stored here is not safe from others as it only stores it in a directory under the users name. It is merely for keeping different users files stored neatly. ----------------------------------------------------------------------------- @ENDNODE @NODE FEATURES "Overall Feature List Of enLOCK" @TOC CONTENTS ___________ ____________ ____________ ___________ ____________ ___/@{" Contents " LINK CONTENTS}\_/@{" Read Me " LINK READ}\_/@{" Shareware " LINK SHAREWARE}\_/ \_/@{" Bugs " LINK PROBLEMS}\__ ______________________________________________/ @{b}FEATURES@{ub} \________________ @{"o" LINK ADDNEWUSER} Unlimited Users @{"o" LINK ADDNEWUSER 13} 23 Character long user names/passwords o Impressive User Interface @{"o" LINK SNDFX} Adjustable Backing Sound Effects @{"o" LINK MEMVECT} Memory Vector Checker (Simple Virus Checker & Killer) @{"o" LINK SPEON} Optional Speed-Up For Impatient Users @{"o" LINK USERAREA} Individual USER: areas @{"o" LINK ASIF} Unique Designed Protection @{"o" LINK STARTUP} Individual User Startup-Sequences @{"o" LINK ACCLOG} Log-File Recording Of EVERY Attempted Access @{"o" LINK USERTIMEBAND} Time Band For Each User To Log-on In @{"o" LINK ABOUT 28} Un-crackable Program Code To Prevent Illegal Versions @{"o" LINK PREFS} Adjustable Preferences @{"o" LINK INSTALL} HD Installer, Un-installer & Prefs Ed o Encrypted Password/Stats Files @{"o" LINK SPEECH} Choice Of Sampled Speech Style @{"o" LINK WB} Updates your Workbench to V42 @{"o" LINK TOOLZ} Toolbar on Workbench screen `---------------------------------------------------------------------------' @ENDNODE @NODE TOOLZ "enLOCK Toolz Bar v1.1" @TOC CONTENTS ----------------------------------------------------------------------------- WHAT IS IT? ¯¯¯¯¯¯¯¯¯¯¯ Once a successful log-on is achieved and Workbench has loaded you will notice a small icon bar in the (by default) top right corner of the screen. This 'Toolz' bar gives the user 3 options. Going from left to right the icons are as follows: @{fg shine}PADLOCK@{fg text}: temporarly re-lock the machine. Useful if you have to leave the computer to go for a dump, answer the door etc. You don't have to reset the machine either! As a saftey precaution always save work before leaving your machine as you never know what might happen!! If you enter a different login name and password the user will be changed on the system as if you had logged on as that user in the first place. @{fg shine}'I'@{fg text}: gives information about the current user in a requester. Details are time and date when user logged on and the name/identity of user. @{fg shine}PLUG@{fg text}: end session/log off/reboot machine (whatever you want to call it!). This will pop up a requester for verification and then another requester to remind you to save all work. It will then reset all enLOCK protection (unlike the older versions which never put it back again! oops!). A cold reboot is performed. Currently this bypasses programs such as "Multireset" so I may look into another way of rebooting the machine so that you can use the utils such as "Multireset" to create a cooler operating system. CONFIGURATION ¯¯¯¯¯¯¯¯¯¯¯¯¯ Unlike the main "enLOCK" program the preferences for "enLOCK_Toolz" have to be set manually by adjusting the tooltypes held within the "enLOCK_Toolz" icon found in the 'WBStartup' drawer of your hard drive boot partition. To change these click on the icon using the mouse and select ICONS/INFORMATION from the pull-down menus. There are two settings to be adjusted: BARX - the x position of the top left corner of the toolz bar. BARY - the y position of the top left corner of the toolz bar. Use the screen co-ordinates to change the position of the bar. If no parameters are set (default) then the bar automatically opens in the top right corner just below the screen depth gadget, just where @{b}I@{ub} like it :-) You will need to reset to make any changes to the toolz position active. Once the toolz bar has opened you cannot move it. oOo enLOCK Tool Bar is a commodity (although a little bit rough) and may be controlled using the 'Exchange' program found in the Tools/Commodities drawer of your 'Workbench' disk/partition. This will enbable you to Show/Hide the interface when needed so that screenmodes can be altered. You cannot quit enLOCK Toolz Bar and when the interface is hidden it still consumes memory! ----------------------------------------------------------------------------- @ENDNODE @NODE WB "Updated Workbench" @TOC CONTENTS ----------------------------------------------------------------------------- C/LoadWB C/LoadWB NAME LoadWB -- start Workbench. (V42) SYNOPSIS LoadWB [-DEBUG] [DELAY] [CLEANUP] [NEWPATH] [HIDE] TEMPLATE LoadWB "DEBUG=-DEBUG/S,DELAY/S,CLEANUP/S,NEWPATH/S,HIDE/S" FUNCTION This command will try to load and start Workbench. If Workbench was already running, it will do nothing (unless NEWPATH option was used). If NEWPATH option was used, LoadWB will make Workbench path a copy of current Shell path. INPUTS -DEBUG - adds 'Debug' menu to the Workbench menus. There are two items under this menu: 'ROMWack' starts internal ROM debugger, which requires a terminal to be connected to the Amiga internal serial port. 'Flushlibs' removes all libraries, devices and fonts currently not in use thus freeing some memory. DELAY - forces LoadWB command not to return until Workbench is completely initialized (i.e. all disk icons are loaded and all WBStartup programs are started). If DELAY option does not appear, LoadWB command will return as soon as Workbench is started. CLEANUP - forces Workbench to execute 'Clean Up' function for main Workbench window after starting. NEWPATH - lets you change current Workbench path. Normally, Workbench remembers path of the Shell that started Workbench. This path is inherited by all programs strated from Workbench. To change path of already running Workbench, you must use NEWPATH option. If Warkbench was already running, this option is ignored. HIDE - Workbench has a habit of putting 'NDOS:???' icons for all unrecognized disks. This is very annoying for users of CrossDOS and DiskSpare disks. HIDE will force Workbench to hide all those 'NDOS:???' icons, including the ones for unformatted disks. HIDE also implies DELAY. RESULT RETURN_FAIL - if 'dos.library' or 'workbench.library' couldn't be opened or command line arguments couldn't be processed. RETURN_ERROR - NEWPATH option was given but copy of current path couldn't be made (due to lack of memory). RETURN_WARN - Workbench was already running and NEWPATH option was not given. EXAMPLE LoadWB HIDE ; Load Workbench, hide all 'NDOS:???' icons. Command will not ; return until Workbench is completely initialized. LoadWB DEBUG CLEANUP ; Start Workbench with 'Debug' menu, move all icons after ; starting. LoadWB NEWPATH ; Set path of already running Workbench or just start it. NOTES To hide those 'NDOS:???' icons all DOS devices are removed before starting Workbench and restored afterwards. This mght affect multitasking! MakeLink is pure and can be made resident. BUGS LoadWB NEWPATH sometimes hangs for a few seconds. This bug also appears in LoadWB 38.9 command. oOo To use any of the new features of v42 of LoadWB simply adjust your S:Startup-sequence. When you un-install "enLOCK" the new version will be installed onto your harddrive so you can continue using it. Edit your S:Startup-sequence before installing "enLOCK" to keep any changes to LoadWB. ----------------------------------------------------------------------------- @ENDNODE @NODE ASIF "Unique DesignedProtection" @TOC CONTENTS ----------------------------------------------------------------------------- As if I would tell you how it was done! ----------------------------------------------------------------------------- @ENDNODE @NODE OTHERHDPROGS "Other HD Protection Programs" @TOC CONTENTS ----------------------------------------------------------------------------- Not to make you think "enLOCK" is the be-all and end-all of harddrive protection programs I've compiled a (currently) small run down of some other programs available on the Aminet in util/boot/ directory. @{b}oOo@{ub} @{fg shine}Superpass v2.0b@{fg text} - Freeware Author: woytek@henry.ece.cmu.edu (Jonathan Woytek/WWCS) SuperPass 2.0b is the wide-distribution BETA version of a new passwording system for Amiga computers. This passwording system probably makes its best impression by being completely FREE! NOTHING is disabled! SuperPass installs itself in your user-startup (if you use the provided installer script). Upon boot, it will read in the password file you specify, along with the number of tries you specify, and it will prompt for the password BEFORE the WB (or anything useful) boots. If a CTRL-C or other break signal is sent to the program, it will automatically reboot the entire machine, preventing access. Passwords are user-definable. Being that this is a BETA release, please email the author with any and all problems encountered. Please read the README.FIRST inside the archive. @{b}oOo@{ub} @{fg shine}BootController v2.0@{fg text} - Shareware Author: se2dp@dmu.ac.uk (Derek Piper) Features BootController 2.0 Protected password entry (ie. '*' characters instead of letters) Adjustable timeout (0-255 seconds) Encrypted password file Encrypted user file (registered version) Vector Checking (registered version) Last Alert display (registered version) Failed Attempts log file (registered version) Keyboard shortcuts 12 / 24 Hour Clock Two date display formats Memory display Attractive GadTools GUI As you can see this program has quite a lot of features. First of all I have to say that although this program is very difficult to break, it is possible to remove the protection it provides without too much hassle (if you know what you are doing) but it keeps prying eyes from accessing your data too easily. If you use it you are advised to lock away all bootable disks as they can provide an easy means of getting into your system. ----------------------------------------------------------------------------- @ENDNODE @NODE INDEX "enLOCK Index" @TOC CONTENTS @{u}INDEX@{uu} @{"About " LINK ABOUT} - Info on program development @{"Access Log " LINK ACCLOG} - Explination of preference setting @{"Add New User " LINK ADDNEWUSER} - How to add a user to the enLOCK system @{"BBS " LINK NFA 17} - The NFA BBS @{"Budda " LINK BUDDA} - About ßudda/NFA @{"Bugs " LINK PROBLEMS} - Bugs in this version of enLOCK @{"Contact Address " LINK SHAREWARE 60} - My address, incase you need it @{"Contents " LINK CONTENTS} - The clicky tab experience @{"Controlling Access " LINK ACCESS} - How to setup the enLOCK system @{"Disable Menu " LINK DISMENU} - Explination of preference setting @{"Greetings " LINK GREETINGS} - Explination of preference setting @{"Amiga Guide Help " LINK HELP} - Help on using Amigaguide® fully @{"Installing " LINK INSTALL} - How To Install enLOCK @{"Kill User " LINK KILLUSER} - How to kill a user & files from enLOCK system @{"LoadWB " LINK WB} - Info on replacement Workbench @{"Log File " LINK LOGFILE} - Explination of log file @{"Memory Vectors " LINK MEMVECT} - Explination of preference setting @{"Moz " LINK MOZ} - About Møz/iNDi @{"NFA " LINK NFA} - Info & how to contact the group @{"Read Me " LINK READ} - Description Of Program & Important Info @{"Registration " LINK SHAREWARE 22} - Details of how to do it @{"Preferences " LINK PREFS} - What preferences are available @{"Problem Solving " LINK FAQ} - Answers to some questions @{"Setup Password " LINK SETUPPASSWORD} - Protecting the setup menu @{"Setup Tip " LINK ACCESS 43} - Tip for accessing enLOCK setup menu @{"Shareware " LINK SHAREWARE} - Shareware information @{"Sound Effects " LINK SNDFX} - Explination of preference setting @{"Speech Style " LINK SPEECH} - Explination of preference setting @{"Speed Up " LINK SPEON} - Explination of preference setting @{"System Requirements" LINK REQUIRE} - What is needed to run enLOCK @{"Tested Amiga Setups" LINK PROBLEMS 47} - Amigas enLOCK Runs On @{"Toolbox " LINK TOOLBOX} - About Tøølbox/iNDi @{"Toolz Bar " LINK TOOLZ} - A tool bar for controlling enLOCK @{"Un-installing " LINK UNINSTALL} - How to wipe enLOCK from your hard drive @{"User Startups " LINK STARTUP} - How to use them @{"User Time Band " LINK USERTIMEBAND} - Setting a time band for a user @ENDNODE @NODE HELP "AmigaGuide® Help" @PREV CONTENTS @NEXT MAIN_2 @TOC MAIN_2 Using the mouse ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ For mouse use, note the following conventions: "click" = move the mouse until the mouse pointer is over the desired area, then press and release the left mouse button quickly "drag" = as "click", but press and hold the left mouse button down and move the mouse Documents are split up into subject areas known as "topics". Topics are chosen simply by clicking on any text which is surrounded by a box. It is unlikely that the whole of a topic will be able to fit on the screen at the same time. The amount of the topic which is currently on the screen is shown by the white rectangular "scroll bar" on the far right of the screen. You can reveal more of the topic either by dragging this scroll bar or by clicking the up and down arrows below the scroll bar (try it now!). Above the topic's text are six "buttons" which perform various functions when clicked. These functions are: Contents - Selects the contents page. (Index - Unused by any documents on this disk) Help - Selects these help pages. Retrace - Selects the topic previously chosen. Repeated clicking of this button "retraces" the topics you have chosen so far. Browse - These two buttons select the previous and next topic in the document you are reading respectively. When any of these buttons appear checkered, they cannot be selected. (This checkering is known as "ghosting"). Using the keyboard ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ This section describes the keyboard equivalents to the mouse operations described above. It is likely that you'll wish to mix mouse and keyboard use when using a document, for maximum speed. In this list: , , and refer to respective arrow keys; and (for example) "Shift - " means hold down the Shift key and press the up arrow key. Return Selects the topic highlighted in blue. (Shift)-Tab Cycles through each topic box currently on the screen, highlighting them in blue. or Scrolls the topic upwards or downwards. Shift - Moves the topic a page upwards. Shift - Moves the topic a page downwards. Alt - Moves the topic to the very top. Alt - Moves the topic to the very bottom. Space bar Scroll forwards Backspace Scroll backwards Holding down any of these keys listed above repeats the function continuously. Alternatively, the various numeric keypad keys (A600 excluded) - Home, End, Pg Up, Pg Dn, the arrows - can be used to move around a topic. Note that the six buttons at the top of the screen can be activated from the keyboard by pressing the key underlined on the gadget. For example, to select "Retrace", press the R key; to select "Browse >", press the ">" key. * For a more detailed "reference manual" of Amiga Guide (prepared by Commodore themselves), click the Browse > button. @ENDNODE @node MAIN_2 @title "AmigaGuide® Help" @TOC MAIN_2 A M I G A G U I D E H E L P (1) @{" Buttons " link HELP_BUTTONS} (2) @{" Menus " link HELP_MENUS} (3) @{" Keystrokes " link HELP_KEYSTROKES} (4) @{" Mouse " link HELP_MOUSE} (5) @{" Arrow Keys " link HELP_ARROWS} (6) @{" Function Keys " link HELP_FUNCTION} Use The "RETRACE" Button To Return TO This Menu Click On Contents To Return To The "enLOCK" Guide @endnode @node HELP_BUTTONS "AmigaGuide® Help: Buttons" @TOC MAIN_2 Contents - Display the Table of Contents document for the current database. Index - Display the index document for the current database. Help - Display the help document for the current database. If the database doesn't have a Help document of its own, then the global Help database will be used instead. Retrace - Go back to the previous node. Browse - Step through the documents in sequential order, in the order they appear in the database. @endnode @node HELP_MENUS "AmigaGuide® Help: Menus" @TOC MAIN_2 Project ------- Print - Print the current document to the current print device. Close Window - Close the active document window. Quit - Close all windows for the current database, and exit. Edit ---- Mark - Start marking a block of text for copying to the clipboard. Copy - Copy the current document to the clipboard. Select All - Select all the lines of the current document. Clear Selected - Unselect all the lines of the current document. Print Selected - Print the selected lines to the current print device. Navigation ---------- Find Document... - Locate a document. Find Text... - Locate all occurrences of text within the current document. Find Next - Show the Find Text document. Set Bookmark - Save the current location to the bookmark file. Go To Bookmark - Go to the location indicated by the bookmark file. @endnode @node HELP_KEYSTROKES "AmigaGuide® Help: Keystrokes" @TOC MAIN_2 TAB - Cycle forward through the buttons. Shift-TAB - Cycle backwards through the buttons. HELP - Display this document in its own window. ESC - Close the active AmigaGuide® window. Backspace - Scroll backwards a page. RETURN - Activate the default button (the highlighted one). Shift-RETURN - Activate the default button (the highlighted one). If it is a document, then load it in a new window. SPACE - Scroll forwards a page. > - Go to the end of the current document. < - Go to the beginning of the current document. @endnode @node HELP_ARROWS "AmigaGuide® Help: Arrow Keys" @TOC MAIN_2 Up - Scroll up through the document. Down - Scroll down through the document. Shift-Up - Go up a page in the document. Shift-Down - Go down a page in the document. Alt-Up - Go to the beginning of the document. Alt-Down - Go to the end of the document. Left - Scroll left through the document. Right - Scroll right through the document. Shift-Left - Scroll left one window-full through the document. Shift-Right - Scroll right one window-full through the document. Alt-Left - Go to the extreme left of the document. Alt-Right - Go to the extreme right of the document. @endnode @node HELP_FUNCTION "AmigaGuide® Help: Function Keys" @TOC MAIN_2 F9 - Activate Next Window. F10 - Cycle active AmigaGuide® window front to back. @endnode @node HELP_MOUSE "AmigaGuide® Help: Mouse" @TOC MAIN_2 Select - Over a node, will activate the node. Shift-Select - Over a node, will activate the node. If it is a document, then load the document in a new window. @endnode @NODE FAQ "Problem Solving" @TOC CONTENTS ----------------------------------------------------------------------------- (1) @{"When I've entered my User ID and Password into enLOCK a small dialog box" LINK ANS1} @{"opens saying `File Not Found'." LINK ANS1} (2) @{"When I rebooted my machine after installing enLOCK I was told that" LINK ANS2} @{"`SYS:System/enLOCK' didn't exist." LINK ANS2} (3) @{"When enLOCK starts a requester opens saying `Sample Bank Not Found'." LINK ANS3} (4) @{"When I try to relock my system using the Toolz bar it doesn't start but" LINK ANS4} @{"instead flashes the screen black quickly and returns to Workbench." LINK ANS4} (5) @{"When I un-install enLOCK the `enLOCK_Users' directory is still present." LINK ANS5} If you have any other questions which would be useful if answered here then let me know. Write to me via @{"snail mail" LINK SHAREWARE 60}. ----------------------------------------------------------------------------- @ENDNODE @NODE ANS1 "Answer To Question 1" @TOC FAQ (1) When I've entered my User ID and Password into enLOCK a small dialog box opens saying 'File Not Found'. ... This is caused due to enLOCK not finding correct directories of files on your hard drive. When reseting enLOCK with `enLOCK Toolz Bar' v1.0 it caused this error due to a bug in Blitz Basic v2.1!! I've fixed this so this message should be rare. To fix it a re-installation may be needed (or use SnoopDOS?) @ENDNODE @NODE ANS2 "Answer To Question 2" @TOC FAQ (2) When I rebooted my machine after installing enLOCK I was told that "SYS:System/enLOCK" didn't exist. ... The installation did not go to plan. This can be caused by a number of things: Your hard drive partition didn't have enough free space and the installer will not tell you because it installs the executables via an external unpacker (UnLZX) which doesn't output to the display any errors that might have occured. Free 1 Mb of HD space and re-install. Since installing you may by accident have deleted an important file that enLOCK requires. Reset the preferences via the Prefs bit in the installer script (selectable at the start) which will copy all required files back onto your hard drive. @ENDNODE @NODE ANS3 "Answer To Question 3" @TOC FAQ (3) When enLOCK starts a requester opens saying "Sample Bank Not Found". ... The installation did not go to plan. This can be caused by a number of things: Your hard drive partition didn't have enough free space and the installer will not tell you because it installs the executables via an external unpacker (UnLZX) which doesn't output to the display any errors that might have occured. Free 1 Mb of HD space and re-install. Since installing you may by accident have deleted an important file that enLOCK requires. Reset the preferences via the Prefs bit in the installer script (selectable at the start) which will copy all required files back onto your hard drive. @ENDNODE @NODE ANS4 "Answer To Question 4" @TOC FAQ (4) When I try to relock my system using the Toolz bar it doesn't start but instead flashes the screen black quickly and returns to Workbench. ... this is due to a lack of memory, especially CHIP memory which enLOCK requires to store it's sound and graphics in. Close some programs to free memory if you need to lock your system. I am unsure of the exact requirements of memory enLOCK requests. @ENDNODE @NODE ANS5 "Answer To Question 5" @TOC FAQ (5) When I un-install enLOCK the "enLOCK_Users" directory is still present. ... the USER: assign didn't REMOVE correctly so the directory was still locked preventing the DELETE command from removing it. Delete it by hand? @ENDNODE