@database 01dd5d10-0 @master ram:apps.guide @$VER: 3.1 @author "Dave Humphreys" @(c) "" @wordwrap @remark Created with Heddley v1.1 (c) Edd Dumbill 1994 @node "Main" "Main Page" Amiga Password Protection System 3.1 August 11th 1997 Written By Dave Humphreys Please select an Item from the Menu @{"  Introduction " link "Intro" 0} @{"  Requirements " link "Req" 0} @{"     Usage     " link "Usage" 0} @{"    History    " link "History" 0} @{"      Bugs     " link "Bugs" 0} @{"    APPsetup   " link "appsetup" 0} @{"Future Features" link "Future" 0} @{" PRO Version   " link "PRO" 0} @endnode @node "Intro" "Introduction" Amiga Password Protection System or APPS is a multi-user password system. It uses a user-file system that stores the information for each user in a file. APPS allows the user to have thier own start up sequence and (in the case of the pro version) their own hard drive partition. APPS also comes with some eatra utilties not least of which is APPSetup. This is the setup program for APPS which sets up the user id andd passwords. It uses a similar interface as APPS so users of apps will feel at home. APPS come in two versions. Standard and Pro version. The programs are almost identical except the Pro version allow the user to setup their own partition as well as their own startup-sequence. I hope you find using APPS useful, and watch out for future releases and updates. @endnode @node "Req" "Requirements" APPS requires the following: Kickstart 2.04+ About 512k of Mem. Not my eh!. APPS and APPSetup were written on the following setup. Amiga 1200, Magnum 25mhz 68040, 8mb Fast RAM, Seagate 520Mb Hard drive, EIDE 8x CD-ROM DRIVE written using Blitz Basic 2.1 @endnode @node "Usage" "Usage" Installing apps is pretty simple. You can either use the supplied installer program(does not use commodore installer yet) or do it manually. Pro version users should check the PRO Version DOC. Stanadard version users continue reading. To install APPS manually follow these steps by steps instructions. 1. Make a directory called logonfiles in your sys: directory. 2. Copy the apps to the c: directory 3. copy the files APPSetup and APPSetup.info to the prefs draw of your sys: device. 4. copy all files in the images draw to the s: directory. 5. rename your s:startup-sequence as s:startup-sequence2 or any name of your choice. but remember what you called it. 6. Type ed s:startup-sequence into a shell window and type the following: Setpatch >NIL: Assign >NIL: ENV: RAM: run >NIL: c:apps endcli the hit esc x to save. (DO NOT RESET! DO NOT RESET!) 7. Run APPSetup. Type in a user id and password. Fill in the other details (name, aka). Stanadard users don't have to enter anything into the mount device string as it is not used by APPS standard any way. When you get to startup-sequence type in s:startup-sequence2 or what ever you called yours The hit save. 8. Reset and if all has been followed correctly the apps program will boot up and all you have to do is type in your user id and password. It doesn't matter about case because in apps everything is converted to lower-case anyway. @endnode @node "Bugs" "Bugs" There are only a few bugs in apps which will hopefully be sorted with version 3.2 The bugs that i have found are as follows. 1. After program has been run mouse stays on amigados screen until mouse button is clicked 2. Program requests the ENV: directory when run menaing that the amigados screen is opened rather than the usual and better black screen. 3. The password string is not disguised so the password is still visible to preying eyes. 4. When using more than 4 colours the menus go all pear shaped in the colour department. This can be fixed using magic menus but this only really works with APPSetup. Could be a bug in Blitz @endnode @node "History" "History" Version 3.1 (7/8/97) Public Release Changed text mode for Transparent text background Included Logo Used include file for graphics functions changed info window system to use a scrollable window changed about window system to use a scrollable window removed unused code and text optimised code for smaller file. Pro Plus version dropped Updated LogOFF User Info for Workbench Program written and included Version 3.0 (14/6/97) Internal Revision Revamped interface. Designed new code system Redesigned APPSetup Included backdrop file and Amiga logo. Removed Window Tile Border Added Menus Added Access Denied window added System lock up after 3 tries removed. Pro version and Pro Plus versions created Entire startup-sequence added internally to Pro Plus version. Porgress Indictaor added to Pro plus version. Version 2.2 (10/3/97) Internal Revision Internal changes Fixed Access denied bug which caused a crash Version 2.1 (5/3/97) Internal Revision Internal changes Updated Logoff and add confirmation requester and ability to run APPSetup. Version 2.0 (1/2/97) Internal Revision Redesign of User Interface. Use Gadtools gadgets. Included APPSetup 2.0 Created "Logoff" program for Workbench. Changed password system to file based one. No longer needed Blitz Basic compiler to setup user id's and passwords. Version 1.2 (15/11/96) Internal Revision Began working on APPsetup began work on file system Internal changes Removed clock Version 1.1 (10/10/96) Internal Revision Internal Changes Included a logo on window Version 1.0 (5/6/96) Internal Revision First Working version Stored user id's, password and startup-sequences in code and had to be compiled by each user Locked up after 3 tries Added a clock to window added normal or Picture bootup depending on a certain picture file being in the s: directory Missing in action due to colledge and hard drive failure. Needed to recreate whole system with limited knowlodge of computer programming. Version 0.1 - 0.9 (2/1/94-3/4/94) Internal Revision Transitional period after converting from AMOS @endnode @node "appsetup" "APPSetup" APPSetup is the program that is ued to setup each users user id's and passwords and the other details reuired by APPS. It uses the same Inteface file as APPS so they both have the same look and feel. You use the same version of APPSetup for both the standard and Pro version of APPS the standard version innores the etra code any way. Here is a description of strings in APPSetup. User Id - This is the users identity code it can be anything upto 8 charcters long. It is also used for as the suffix for the user logon file. Password - This is the users own password. This to can be upto 8 charcters but best to use either letters or number. User Name - This is the users real name. It used by the User Information program. Not implemented yet in this version. User AKA - This is the users AKA, Alias, Nickname, Handle. (Also not implemtented) Mount device - This is the name of the device assigned to each user. This is only found in the pro version as it requires a lot of setimg up. Startup-sequence - This is the file which stores ech users boot of script. This can be any file anywhere. The stanadard startup-sequence is copied, renamed and replaced during installation but can be used here. The Buttons are as Follows: New - Clears all string gadgets and starts from new Load - Reads the user Id String and load the file accordingly Save - Reads the all strings gadgets, adds the extra code and saves the file using the user id string as the suffix for the users file. Help - Opens a scrollable help window with a quick description of the string gadgets Quit - Ends the Program REMEMBER - The load function needs the users id to be input into the user id string gadget @endnode @node "Future" "Future Features" Here is a list of futrue features to be added or updated in next versions of APPS Fix Mouse Bug Fix Env Bug Fix Password String BUg Fix Menu Bug Create APPS own font Add Screen saver that uses anims and mods Add Prefs for APPS interface Update coding system and psoibly move all file into one big one. Add encryption to files Add prefs file to APPSetup for selecting screen, windows positions etc. Implement Name Function Implement AKA Function Update User Info Program Update Logo Change background to a more Newicon type Allow users to select their own backgroun(would probably mean including a palette file) @endnode @node "PRO" "Pro Version Doc" The PRO version of APPS requires more setup than the standard version as it reuires hard drives to partitioned and mountlists to be created. This not a task for the faint hearted. Users can do this the easiest way they an but waht they need to do is to : a. Partition their hard drive to give each users their own drive. They then need to install workbench and any and all programs that the requires. b. The mountfile on the needs to be editied to include all the drive information for each partition. This really needs to be there or APPS chuccks a mental. c. depeneding on your trust of the user then you need to edit their startup-sequence to do the following. 1. Move system assigns to their drive including fonts,s,libs etc. 2. use the assign command to dismount the boot device and remove it from the amigados volumes list. This will stop the user from accessing your drive and mountlist. If you trsut yours users not to mess around with your drive then the abouve is not needed. The best option is to create a small boot device of about 10mb and install only Workbench and APPS on it and use your own partiton in the same way. The above maybe added to futre version of APPS Pro depending on the complexity and whether i keep Pro working in the same way. Note! There is a Porgram called "MoveSys" which moves all the sys: assigns to the selected drive. You Might find this useful. @endnode