home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Frozen Fish 2: PC
/
frozenfish_august_1995.bin
/
bbs
/
d07xx
/
d0798.lha
/
LockIt
/
LockIt.DOC
< prev
next >
Wrap
Text File
|
1993-01-10
|
14KB
|
358 lines
LOCK IT version 2.1. FREEWARE.
FREEWARE means: LockIt may only be distributed by Andreas Linnemann, Tom
Kuhlenkamp and Rainer Klinke. Written permissions for distribution can be
issued by these persons. This permission is hereby granted for Fred Fish's
"Amiga Lib Disk".
A simple data protection utility by Andreas Linnemann.
MANUAL
======
Contents
----------
1. General instructions
1.1 What can LockIt be used for?
1.2 System requirements
1.3 Hardware incompatibilities
1.4 Software incompatibilities
2. Installation
2.1 On Workbench
2.2 On CLI
3. Controls
3.1 Opening the Contol Window
3.2 The list of objects
3.3 Locking an object
3.4 Unlocking an object
3.5 Saving the list
3.6 Anything else?
1. General instructions
1.1 What can LockIt be used for?
Well, "lock" means closing something so that no one except the one who has
a "key" can access it. But what can be locked on a computer? Files, for
example, or drawers containing files.
The sense of this action is that there are definitely Amiga users who keep
files on their harddisk, which should not be accessible for any person
(e.g. children or friends who hang at your computer without your knowing
it). Conclusion: We simply LOCK these drawers. Finished. Everything ok.
The "key" consists of a password which ONLY YOU should know. It is indeed
quite difficult to use different keys except keyboard keys at PC's.
1.2 System requirements
As one requirement you first need an Amiga computer. Whether 500, 1000,
2000 or 3000 or anything else is not important. BUT:
----====****>>>> LOCKIT REQUIRES KICKSTART 2.0 OR HIGHER! <<<<****====----
The amount of memory is of less importance, as LockIt is quite short and
does not need a large amount of memory.
1.3 Hardware incompatibilities
Hardware Incompatibilities are not known (yet).
LockIt is being successfully used on the following systems:
A2000, 1MB Chip,CBM2630(4MB),Oktagon2008+ 105MB QuantumLPS,Flickerfixer
A500Plus, 1MB Chip,2MB Fast,GVP SerieII+52MB Quantum LPS
A500Plus, 2MB Chip,Oktagon500+FujitsuM2611S(42MB)
1.4 Software incompatibilities
Problems with any software are not known except of programs trying to
access locked dirs/files (e.g. Hard Disk backup systems).
2. Installation
2.1 On Workbench
First take care that LockIt is run at every system start. Simply copy the
program and its icon into your WBStartup drawer on your workbench
disk/partition. After that click onto its icon one time. Call
"Information..." from the Icon menu. You can use the following tool types:
DONOTWAIT --- Use this if you definitely use LockIt in "WBStartup"
(unless you want to use ONLYINSTALL=YES)
ONLYINSTALL --- LockIt only installs the protection for the objects in the
=<YES/NO> saved list and removes itself from memory after that. If
you start LockIt a second time, LockIt is installed in
memory like usual. This feature is only recommended for
users with lack of memory.
=== CAUTION!! === Never use both DONOTWAIT AND ONLYINSTALL=YES, as this
could cause system crashes!
EDITINIT=<type> --- Here you can specify the way to open the control
window.
<type>=APPICON - LockIt puts its own icon onto the Workbench. Double-
clicking opens the control window.
<type>=TOOLSENTRY - LockIt adds the entry "LockIt" in your Workbench
"Tools" menu. Selecting opens the control window.
<type>=BOTH - Both Icon and Tools-Entry are created.
<type>=NONE - Neither Icon or Tools-Entry is created.
ICON_X=<value> --- The horizontal position of the LockIt icon can be
specified here.
ICON_Y=<value> --- The vertical position of the LockIt icon.
If no values are specified here or if both values
are zero, the icon is put anywhere if there is enough
space, mostly at the left side.
SCREEN=<type> --- If <type> is equal to "WBENCH", the control window will
appear on the Workbench screen (or the current Public
Screen). If <type> is equal to "ACTIVE", the control
window will be opened on the currently active screen
(e.g. Deluxe Paint screen). Open any new screen and then
perform the LockIt key combination (e.g. Left-Amiga-L).
LockIt will open its window on this screen.
CAUTION: Don't close the screen before closing the
control window. If you do, you will definitely cause a
system crash!
CONFIG=<path> --- For <path> you can type the name of the LockIt config
file. Default path is "S:LockIt.config".
CX_POPUP --- If this tool type is set to "YES", LockIt will open its
=<YES/NO> control window at once if started.
CX_POPKEY=<key> --- For <key> you can enter the contol key sequence which
will cause LockIt's control window to be opened.
Default key is "LCommand l" (left Amiga key and "L" at
the same time). The expressions for all the key
combinations can be found in your Workbench manual.
Already noticed that LockIt is indeed a Commodity??
CX_PRIORITY=<value> --- <value> contains LockIt's Commodity priority. If
two commodities have the same HotKey, the one
with the higher priority will be preferred.
Default value is zero.
Instructions for entering tooltypes can be found in your Workbench manual.
2.2 On CLI
LockIt should be started from Startup-Sequence or User-Startup in the S-
Directory. As there is no icon, the tooltypes must follow the program call
as parameters. Try it, copy LockIt into the C-Directory and enter in CLI:
C:LockIt EDITINIT=APPICON ICON_X=60 ICON_Y=20 "CX_POPKEY=CONTROL F1"
This command will put the LockIt icon at (60/20) onto the workbench and
makes LockIt accessible by the key combination "CONTROL F1". Don't forget
the quotes! They are necessary, if a parameter contains white spaces, in
order to prevent misunderstandings.
Now edit your User-Startup (e.g. with MEMACS) and add a line calling
LockIt including its parameters
LockIt does not need "run", as it detaches from CLI automatically and
does not stop the CLI activities.
3. Controls
Normally, LockIt is mouse-controlled. Strings are self-evidently entered
by keyboard. The buttons can be clicked with keyboard commands, too. Press
the underlined letter in/beside the buttons on your keyboard. The cursor
keys (up & down) can be used for scrolling through the list entries.
3.1 Opening the control window
There are four possibilities for opening the control window:
1. Double-clicking the Application icon on the workbench
2. Selecting "LockIt" in the Tools-Menu
3. Performing "LCommand l" or the key combination specified in "CX_POPKEY"
4. Starting LockIt a second time. This function was built in because there
is no reason to start LockIt two times except editing the list.
According to EDITINIT, the number of possibilities can be reduced, but
Point 3 and 4 are always available.
3.2 The list of objects
There is a listin the upper region of the control window. The list is
divided into "Object" (name of the Object) and "Status" which can be
"locked" or "unlocked". You can scroll the list with the bar on the right
side or with the little arrows. The cursor keyss (up and down) are also
suitable for scrolling through the list.
3.3 Locking an object
To protect an object, press the "Add" button first. An entry is added in
the list and "Edit" is selected for this entry. The Edit window asks you
for the Object name. This name will be found in the list later on. After
that the object itself must be specified as a complete path onto a file or
a drawer. You can alternatively get your mouse and press "Select". An ASL-
Filerequester will appear and will allow you to select your object in a
comfortable way. If a file is selected and no Object name has been entered
yet, the file name will be copied to the Object name. Please ensure that
the COMPLETE path is entered (e.g. "DH1:Data/Beckertext/Letters" and not
only "Letters").
If you have successfully entered your object, you are to enter a password
now. Please do not mix up upper and lower case letters! Ensure that you
are alone. Do not forget the password! Write it down, but please do not
put the sheet beside your computer.
If a Lock can not be performed (e.g. wrongly written path), an error
message will appear. Leaving the Edit-Window with "OK" will not be
possible until the Lock can be performed. "Cancel" will always work.
PLEASE PAY ATTENTION: As LockIt is a Commodity, you can hide or kill it
with the Workbench-Tool "Exchange". Please do not hide/kill LockIt if the
Edit window is open. If you do, the window will be closed and the
modifications are LOST! Please leave the Edit window with "OK" and use
"Exchange" to your heart's content.
The protection itself can be activated now. Click on the Cycle-Gadget
next to "Status" or press "t" on your keyboard. The Cycle-Gadget and the
Status of the current object will change to "Locked". Try to open the
object, it is not possible any more.
To say it again: LockIt is very different to the Workbech-Command "Lock"!
LockIt does not only protect data of being deleted or written, it's a
read protect as well! Without LockIt the object is not accessible unless
a reset is performed. If LockIt is called after every System reset,
practically permanent (but NO absolute!!) protection is granted.
3.4 Unlocking an object
To unlock an object, select the object in the list at first, so that it
is visible below the list. Now switch the Status to "unlocked". LockIt
asks you to type the password now. After successfully entering the pass-
word, the object is really unlocked.
3.5 Saving the list
Never forget to save the list. The path given with "CONFIG" is used, or
if no path is specified, "S:LockIt.config". The Objectnames, paths,
passwords and states are saved. If you start LockIt the next time, the
file is read and the "locked" objects are locked indeed.
3.6 Anything else?
"Delete" deletes the current object, "Edit" makes it possible to change
the object name path and password after typing the old password.
At the bottom there are a few more buttons. "Hide" hides the control
window, "About" opens a small information requester. The close gadget
is the same as "Hide". "Quit" removes LockIt from memory, but locked
objects remain locked.
Consider the following: If a path is active to your object (e.g.
SYS:fonts/ to FONTS:), LockIt cannot install a protection. It is also
impossible if the object has been opened on the Workbench or if it is
somehow "in use". LockIt will tell you this with an error message.
LockIt is a Commodity. You can hide or kill or do anything with it with
the Workbench-Tool "Exchange". But condsider the warning in 3.3.
...and now a few MOST IMPORTANT things:
1. LockIt does NOT provide absolute protection against data misuse.
Professional users may be able to deactivate the protection. Most
critical data should therefore be copied to disks and deleted from
harddisk. The disks should be kept safe.
2. Although the passwords are encoded before being saved, please to not
use words which you use to use in Mailboxes or anywhere else because
it may be possible to decode the configuration file.
3. UNLOCK ALL objects before starting a harddisk-backup. ALFBackup
crashed when trying to access locked files/dirs.
So, that's it. If you have questions, bug reports or simply want to say
hello, please contact the author of the program or the author of this
manual (that's me). Please excuse my strange English as we use to speak
German in Germany.
LockIt 2.1. Finished in August, 1992.
Program-Author, Tests Manual, Icon, Tests
---------------------- ---------------------
Andreas Linnemann Tom Kuhlenkamp
Ringstra▀e 26 Ritzenberger Weg 18
W-2817 D÷rverden-Barme W-2811 Blender
Germany Germany
Phone (Ger) 04234/1294 Phone (Ger) 04233/448
Created for and sponsored by Rainer Klinke.
History
-------
V1.0 CLI-Tool without intuition surface, only one object, full of
errors, needed two programs ("LockIt" and "Unlock")
V1.1 Most bugs fixed, only for Kickstart 1.3
V2.0 More objects, difficult user surface, slow, still 2 programs
("LockItInstall" and "LockIt"), full of errors
V2.01- New surface, safe and (nearly) bug-free, application icon,
V2.08 tools-entry, commodity, ASL-Filerequester
V2.09 Quicker Window refresh, better Commodity-handling. Bug in string
gadgets and ASL-Requester fixed. Blocking of unused windows
V2.1a Auto-detach, CLI-Parameters, internal icon, better error-
handling. Window gets used to screenfont size
V2.1b Clean quitting in case of a program bug, bug in OnlyInstall-
routine fixed which was visible quite seldom. Repeatedly changed
the save format (sorry). Clean handling if started again. Real
version-handling added. Quicker (better Stack handling). Opening
window if started twice. Bug in window-blocking-routine fixed.
Checking for Lock already in Edit-Window. Bug at "Add" and
"Delete" fixed, memory was not freed.
V2.1 Minor bugs fixed, first publication
Neither the author nor anyone else takes guarantee for damages caused by
the usage of LockIt. If bugs should become visible which could not be
removed in spite of the long test phase, the author is grateful for any
bug reports. Please deliver an exact bug report and do not write something
like "LockIt seems to be so strangely slow" or something like this.
Thank you for using LockIt.
///
/// Only
///
/// A M I G A
///
\\\ /// makes it
\\\ ///
\\\ /// possible!
\\\///
\///