Category : HD Utilities
Archive   : SFLOCK15.ZIP
Filename : SF15.DOC

Output of file : SF15.DOC contained in archive : SFLOCK15.ZIP



Release 1.5

(C) 1992 CEA Consulting Services

: Keep this documentation in a :
: place where it will be :
: accessible only to those :
: authorized to encipher or :
: decipher your protected data! :




CEA Consulting Services (CEACS) hereby disclaims all warranties
relating to SAFELOCK, whether express or implied, including
without limitation any implied warranties of merchantability or
fitness for a particular purpose. CEACS can not and will not
be liable for any special, incidental, consequential, indirect
or similar damages due to loss of data or any other reason, even
if CEACS or an authorized agent of CEACS has been advised of the
possibility of such damages. In no event shall the liability for
any damages ever exceed the price paid for the license to use
software, regardless of the form and/or the extent of the claim.
The user of SAFELOCK bears all risk as to the softwares' quality
and performance.


SAFELOCK is SHAREWARE. It is made available to the computer user
for evaluation. Users are licensed to use SAFELOCK for the
purpose of testing and evaluating for a limited trial period. It
is not possible to reasonably define any limits of a fair and
equitable time period for this evaluation; therefore, it is left
to the user's judgement as to the sensible time required in
making a decision to use it. Should the user decide that the
software is not sufficient to meet their requirements, the program
should be removed. In the event that the user decides the software
meets their needs, it should be registered with CEACS.

Registration requires payment of the registration fee to CEACS set
in the appendix of this documentation. Registration licenses the
user to continue using the software on a single computer for as
long as they choose. Site licensing is available for multiple
computers and the reduced fee is based upon the number of single
computers licensed for use.

SAFELOCK is the sole property of CEACS. It is a fully functional
software product distributed/marketed via the SHAREWARE method,
allowing potential buyers to thoroughly try the program prior to
purchase. It is NOT free, and is NOT in the public domain. The
SHAREWARE version may be freely copied and transferred to
individual parties for evaluation purposes. The SHAREWARE version
may be posted on bulletin boards (BBS) for file transfer as long as
no fee is charged for it's distribution (outside of any sub-
scription fee charged by the BBS for access). The shareware version
of SAFELOCK may not be distributed on diskette by any disk
distributor/vendor that charges more than $10.00 for the diskette
upon which the program and related files are recorded without
written consent from CEACS.




Introduction to CEA Consulting Services and Software Products

CEA Consulting Services (CEACS) is a consulting firm located in
Cicero, Illinois. Although we are primarily VAR (Value-Added-
Reseller) oriented, we often design specific programs for our
clients needs. Occasionally, when a product has been designed,
tested and implemented with more than two clients, we'll examine
the feasibility of it's modification for introduction to the

Once it's decided that the product will be made available as
shareware, it's modified for this purpose and placed on BBS's
and circulated through local user groups.

The SHAREWARE release is fully functional. The only difference
between this and the registered version is that we remove the
shareware notices from the displays and show a serial number
provided with the users registered copy.

The registered product provides the user with (1) a specified
time period of technical support based on the product purchased.
(2) The most recent release (if not already owned) of the product
purchased, (3) notification of upgrades and (4) substantially
reduced costs for upgrades of the specific software product.

We believe in a products proficiency. Should you have trouble
during a product evaluation, call our message center and leave
us a message including your name and phone number (the number
is listed in the appendix of this documentation).

After your purchase, if the product fails to meet your needs,
a refund can still be arranged by calling and discussing the
situation with a CEACS representative.

Thank you for evaluating this product, and we sincerely hope
it will meet your needs.


SafeLock Introduction

- What's SAFELOCK?

SAFELOCK is encryption software for floppy disks or hard drive

When it's necessary to secure data from prying eyes at the
office (or at home!), SAFELOCK may offer what you need to do the

- How does SAFELOCK work?

To be realistic, we can't reveal much about the process SAFELOCK
uses to encrypt and decrypt data; however, the steps used can be
discussed for general understanding.

SAFELOCK has two executable files for protecting data. First, is
SFLOCKD.EXE, which locks floppy diskettes. The second is
SFLOCKF.EXE, which locks files on a hard drive or floppy diskette.

* SFLOCKD runs a sector by sector encryption technique which renders
the data on a diskette unusable once locked. This requires the
use of a second floppy drive (or hard drive) with SAFELOCK

* SFLOCKF encrypts files on a given drive (floppy or fixed) using
the standard DOS file specification. SAFELOCK encrypts the
specified file(s) and renames them to a locked file name.

These file names begin with an ASCII character that is not
normally present on the standard XT or AT type keyboard and
therefore makes it difficult to access the file without
knowing the key combination to type that character, or using
a DOS or window utility that allows file selection.

To further protect the selected file(s), their DOS storage
formats are altered as well. This helps make them difficult
to delete by the average user (by accident, or on purpose!).

* To summarize, SAFELOCK will:

1. Lock entire diskettes using sector encryption
2. Lock files on diskettes or selected subdirectories of
a hard drive by:

A. Encrypting the data in the file(s)
B. Renaming the file(s) with a special ASCII character
C. Change the files' storage formats

Page 1
SafeLock Introduction

- Is SAFELOCK "safe"?

As with all of CEACS software, SAFELOCK has undergone tests with
various file and disk types and has performed successfully on
most. The exceptions we have found are trapped by SAFELOCK, and
the user is prompted with a response to accept or reject these
conditions or in some cases, SAFELOCK will simply not perform
the lock.

Examples of a SAFELOCK rejection are the system files (in the
boot sector of a hard or floppy drive) and COMMAND.COM.

Examples of SAFELOCK user approval prompts are: .SYS files,
files already marked as READ-ONLY, and files marked as HIDDEN.

NOTE!!! ---------------------------------------------- NOTE!!!

When first using SAFELOCK, it may be a good idea to first make
back-up copies of the data files or diskette that you want to
encrypt, then run SAFELOCK against the BACK-UP copies, first
locking the diskette or files, then unlocking them.

When you have determined that SAFELOCK has successfully done
the job by using the diskette and/or files, then you can
continue using it as provided.

NOTE!!! ---------------------------------------------- NOTE!!!

If after performing the above steps, you find that SAFELOCK
did not perform properly, DO NOT use the product! Please
notify CEA Consulting Services by mail using the form provided
for this in the appendix.

- What about passwords?

SAFELOCK uses a password of up to 8 characters provided by
the user to lock their data. The password is input on an
"invisible" field, then verified on a second "invisible" field
to ensure that it was entered correctly.

Once data is encrypted, the user MUST remember the password
that they entered to unlock the data.

If a user forgets the password, there is a SAFELOCK file that
the user can send to CEACS by mail (or may be transmitted via
modem on a pre-arranged schedule). In most cases, CEACS will
be able to determine the password and notify the user.

NOTE! ------------------------------------------------------

Password determination is only available to REGISTERED users of
SAFELOCK without a fee!

Page 2
SafeLock Usage



: This portion of the documentation :
: contains instructions and information :
: on the use of SAFELOCK. To increase :
: security, the user may wish to remove :
: this section and place it in a secure :
: area. :

SafeLock Usage

- What you should know before using SAFELOCK.

The only real requirement as a user of SAFELOCK is a sound
knowledge of DOS. There are two times where this is necessarily

1. Setup and testing of SAFELOCK with your files.
2. Should you encounter problems or have questions and it
becomes necessary to call CEACS.

- Files included with SAFELOCK

The following should have been included in your SAFELOCK
archive.... DO NOT use SAFELOCK if ALL of the files are not
present, or if the file sizes and dates do not match.

Delete any other files that may be included in the archive.

This is SAFELOCK release 1.5

File Name File Size File Date
------------ ---------- ----------


Registered Files:

RFLOCKF.EXE..........75,362............Date of Registration
RFLOCKD.EXE..........48,032............Date of Registration

Call CEACS for a good copy of SAFELOCK if these files do not
have the correct size or date.

Page 3
SafeLock Installation

- What to do first

Now that you have SAFELOCK unarchived, it's time to decide where
you want it to reside. As a safety precaution, SAFELOCK hides
the directory in which it resides from DOS. Although this isn't
necessary, if you suspect security problems already, it IS

To install SAFELOCK in it's own directory and hide that
directory, switch to the directory where SAFELOCK now resides
and enter:


at the DOS prompt.

The install program will ask you for the drive and path in
which you want SAFELOCK to reside. If necessary, SAFELOCK will
create the subdirectory for you, copy the files and hide the

It would be a good idea to place SAFELOCK in a subdirectory
beneath a first-level subdirectory, if possible. For example,
if you had a first-level subdirectory of C:\DOS, then a good
place for SAFELOCK would be in C:\DOS\SLOCK. This way a normal
DOS utility program could not display it from the root directory.

Page 4
SafeLock Installation/

- Once SAFELOCK is "home"

SAFELOCK should be set up in your DOS PATH statement, so DOS can
find it when it's executed. Usually the PATH command is set up
in the AUTOEXEC.BAT file in the root directory of your hard
drive. An example of the PATH command with SAFELOCK added as
shown in our previous example might be like this:


If you're not familiar with the DOS PATH command, we recommend
that have someone you can trust help you with this setup.

- Testing SAFELOCK with your files

Although we've tested SAFELOCK with many different files, it
would be a good idea to test it with your files before actually
encrypting the files themselves.

We've placed this section on testing your files before the actual
command usage so you'll be sure to test SAFELOCK first. The
command usage instructions start on page 7.

The best way to make sure SAFELOCK will work properly with your
files is to make a copy of the files you want to lock. If they
are in another subdirectory, first make a second subdirectory
called "SFLOCKBAK", then copy the files from the original sub-
directory to that directory(*See note below).

For example.... let's say that your LOTUS 123 files are in


Switch to C:\LOTUS and create a directory called SFLOCKBAK...

COPY ..\DATA\*.*

Once the files are copied, switch back to \LOTUS\DATA and run

(*) See page 6 about copy-protected files before encrypting
.EXE or .COM files.
Page 5
SafeLock Installation/

- Testing SAFELOCK with your files (Cont'd)

Once the files are locked, rerun SAFELOCK with the "unlock"

When the unlock process is completed, run your application as
normal (in our example, we would start up lotus). If your
data files are in the proper condition, everything should
operate as usual. If so, you can delete the files in SFLOCKBAK
and remove the subdirectory.

If your application DID NOT access the data files as usual, then
change to your data directory and copy the files back from the
backup directory. For our example:


Once the files are copied back, you should be able to continue
as normal. You can now remove subdirectory \LOTUS\SFLOCKBAK.

If you have problems after the above procedure, call CEACS at
the tech support line listed in the appendix and leave your name
and a phone number where you can be contacted. We'll see what
we can do to help.

- Copy protected/read only files

Unfortunately, some developers find it necessary to "patch" their
executable programs and ensure copy-protection by locating that
patch on the physical sector of the disk.

Usually, when they do this, they make the file read-only, so it
cannot be overwritten or deleted. It also generally means that it
can't be copied to another source (this even includes backups,
which means your backup is useless if this file and/or subdirectory
is damaged!).

If you plan to encrypt .EXE or .COM files, you may want to confirm
that the developer has not employed this method of copy protection.

SAFELOCK informs you of read-only files and gives you the
opportunity to skip those files. If you elect NOT to skip them,
SAFELOCK will lock the file. This process remove the read-only
status before locking the file, and reset the new one when it's
unlocked. For this reason, if the file was "patched", it may
not execute when unlocked.

If there's any doubt about a read-only file, then elect to SKIP
that file when prompted.

Page 6
SafeLock Usage

- Command formats

*Locking diskettes with SFLOCKD


As mentioned earlier, you may want to test SAFELOCK by making
a copy of the diskette to be locked and then lock the diskette,
unlock it and view/use the contents.


SFLOCKD must be run from a second diskette or a hard drive. It
WILL NOT lock a fixed disk or network drive. It WILL however,
lock any formatted diskette: 360k, 720k, 1.2m and 1.4m .

Since SAFELOCK does a sector-by-sector lock of the target diskette,
it's a slow process (depending on which option you use), but one
that renders the data on the diskette useless. One important note
about using SFLOCKD on a diskette:




If you open the diskette drive or shut off the PC while SFLOCKD
is locking a diskette, most or all of the data on the diskette
will be lost!

You may want to keep a backup of the diskette that you last
locked as a precaution. A locked diskette can be copied using
the DOS "DISKCOPY" command.

Depending on the level of security you need, there are two
switches used for SFLOCKD for locking diskettes. These are /S
and /L.

An example of running a "short" lock on a diskette would be:


SAFELOCK will ask you for the diskette drive where the target
diskette is inserted. Reply with the drive letter.

Page 7
SafeLock Usage

- Command formats (Cont'd)

*Locking diskettes with SFLOCKD (Cont'd)

"SHORT" Lock

The /S switch will perform a "short" lock on the diskette, which
only locks the first 25 sectors on the diskette. This generally
includes the boot sector and the disk file allocation table
(FAT), plus a few more sectors.

Without these sectors, the user is unable to view the contents of
the disk using the standard DOS commands.

"LONG" lock

The /L switch performs a "long" lock, encrypting every sector on
the diskette. This method earns it's name.... Depending on the
size of the diskette and the speed of the drive, this process
could take some time.

This long method of locking the diskette encrypts the entire
diskette, making the data useless even if viewed by special
software such as Norton Utility's disk editor or other such

Due to the length of time this process takes, it should only
be used when tight security is required and you suspect personnel
that have the knowledge to use a disk/diskette editor.

*Un-Locking diskettes with SFLOCKD

SFLOCKD encrypts and stores certain information about the locked
diskette when completed. To unlock a diskette, put the locked
diskette in the drive and execute SFLOCKD with the SAME switch as
was used to lock it.


SAFELOCK must be run from the same location as where it was
installed and where the diskette was locked in order to retrieve
the information it needs to identify the diskette and unlock it.

SAFELOCK will ask for the password and unlock the diskette once


Page 8
SafeLock Usage

- Command formats (Cont'd)

*Unlocking diskettes with SFLOCKD (Cont'd)

As is true with locking a diskette, if you open the diskette
drive or shut off the PC while SFLOCKD is unlocking a diskette,
most or all of the data on the diskette will be lost!

*Locking files with SFLOCKF

This method can also be used on diskettes, although using SFLOCKD
provides a bit tighter security when necessary.

There are two switches for use with SFLOCKF. These are /L and

The best way to use SFLOCKF to lock files in a given subdirectory
or on a diskette is to first switch to the directory or drive
where the files reside that are to be locked. Although SAFELOCK
will prompt you for the path of the files to be locked, it
always displays the current path by default.

*Selecting files/subdirectories to lock

Once the opening screen displays, you'll be given the opportunity
to select the default directory and "all files" by placing an "X"
by the default path, or to select an alternate path and file
name(s). If you want to use the current path, but do not want to
lock "all files", you still must select the alternate option.

To select the alternate option, press the "enter" or "return" key.
The cursor will move to the "Drive" selection.

To select a drive, just type the drive letter. The cursor will
automatically move to the "Path" field.

To enter the path, you should specify the complete subdirectory
name, for example:


DO NOT put the last back-slash in the path, and DO NOT put the
filespec you want to lock in this field. When the path is
correct, press "enter".

Page 9
SafeLock Usage

- Command formats (Cont'd)

*Selecting files/subdirectories to lock (Cont'd)

To enter the file specifications, use the DOS filespec options.
For example:


Our example tells SAFELOCK that we want to lock all the files
with an extension of .WK1.

SAFELOCK will ask you if everything is correct when all of the
information is provided. Take a final look, and if everything
is as you want it, reply "Y". An "N" response will start the

selection process over.

*Entering a password

When SAFELOCK has confirmed the path and files to be encrypted,
you will be prompted for a password to use for unlocking the


Use a password that should be easy for you to remember. If you
forget the password, you will have to contact CEACS to get
help with unlocking the files, and unregistered users will be
charged for the process.

The fields where you enter the password will not display as
typed. Therefore, you will be asked to verify the password in
another field. If the two do not match, you will be informed
and given another opportunity to enter the password.

Once the password is entered correctly, SAFELOCK will begin
locking the files. It will display the old file and the new
file names as they're locked.

*Locking a subdirectory

Once locked, if you are in a subdirectory of a hard drive or
diskette, SAFELOCK will ask if you want to lock the sub-
directory as well. When SAFELOCK locks a subdirectory, it
merely renames the subdirectory to a name beginning with the
special ascii character and makes the subdirectory read-only.
This makes it more difficult to switch to that subdirectory
or to delete it.

Page 10
SafeLock Usage

- Command formats (Cont'd)

*Locking a subdirectory

You may choose not to lock a subdirectory if you wish by selecting
"N" at the prompt.

Note: If you lock a subdirectory, SAFELOCK will not prompt you
for this, even if you lock other files later in that
subdirectory. You will not be prompted for this option
again for that specific subdirectory until that subdirectory
has been unlocked (see the next heading).

*Locking other files in the same subdirectory

When SAFELOCK has locked files in the subdirectory provided, it
renames the files to "!OCK.###". Where the "!" is, will be the
ASCII character used for locking files, and in place of the "###"
are sequential numbers as locked.

A log file would also be created using "!OCK###.LOG", where the
### represents a sequential number for logs. The log file is
used to store the information required to unlock the files that
were locked in one run of SAFELOCK.

*What happens

Assuming that we locked files "*.WK1", and there were 10 of those
files, they would look something like this:

!OCK.001 !OCK.002 !OCK.003 !OCK.004 !OCK.005
!OCK.006 !OCK.007 !OCK.008 !OCK.009 !OCK.010

If you later decided you wanted to lock files with a ".WK2" without
unlocking the other files, the log file and the files would
increment. Assuming there were 5 ".WK2" files, it would now look
something like this:

!OCK.001 !OCK.002 !OCK.003 !OCK.004 !OCK.005
!OCK.006 !OCK.007 !OCK.008 !OCK.009 !OCK.010
!OCK.011 !OCK.012 !OCK.013 !OCK.014 !OCK.015

The multiple log files are for SAFELOCK to determine which files
to unlock. You may use the same password or a different one to lock
other files in the same directory. You may want to keep a written
copy of what log files contain what files, especially if you're
going to use different passwords for different files!

Page 11
SafeLock Usage

- Command formats (Cont'd)

*What happens (Cont'd)

Note: If you LOCK a subdirectory, SAFELOCK stores the information
it needs in the active logfile. You can not unlock the sub-
directory until you unlock that particular log file!

*Unlocking files

If you elected NOT TO LOCK the subdirectory, then the easiest
way to begin the process is to first switch to the subdirectory
in which the locked files reside. Although SAFELOCK will give
you the opportunity to provide a path, it will default to the
current path.

*Selecting files to unlock

Once the opening screen displays, you'll be given the opportunity
to select the default directory by placing an "X" by the default
path, or to select an alternate path. If you want to use the
current path, just place an "X" for the default path.

To select the alternate option, press the "enter" or "return" key.
The cursor will move to the "Drive" selection.

To select a drive, just type the drive letter. The cursor will
automatically move to the "Path" field.

To enter the path, you should specify the complete subdirectory
name, for example:


DO NOT put the last back-slash in the path, and DO NOT put the
filespec you want to lock in this field. When the path is
correct, press "enter".

Note: If you've locked the subdirectory, go to page 13 to the
section: "Selecting files/subdirectories to unlock".

If there is only one log file in the subdirectory you've
selected, SAFELOCK will prompt you for the password to unlock
the files. If there is more than one, you will be shown a list
of log files to select from. To select the proper log, just enter
the number to the left of the log file name.

You're given three chances to get the right password before
SAFELOCK aborts, and you'll have to start again. Once you enter
the correct password, it will start displaying the file names
and unlock sequence.

Page 12
SafeLock Usage

- Command formats (Cont'd)

*Selecting files to unlock (Cont'd)

If this log was used when locking a subdirectory, SAFELOCK will
automatically unlock the subdirectory as well once all of the
files are unlocked.

*Selecting files/subdirectories to unlock

If you have locked the subdirectory, you will have to switch to
the subdirectory previous to that one to unlock the files in that
subdirectory. If we use our previous example our path may be:


Since the "!" represents a character that cannot normally be
typed from the keyboard, we'll have to rely on SAFELOCK to
access that subdirectory.

NOTE: In our example, we have locked the DATA subdirectory. If
we want LOTUS to access that subdirectory, and we've locked
more than one set of files, it will be necessary to unlock
the log file that contains the lock for the subdirectory!
(See page 10)

To unlock the files in the locked subdirectory in our example,
we would have to change to the \LOTUS subdirectory and start up
SFLOCKF as shown:


When SAFELOCK finds the locked subdirectory (or subdirectories),
it will display a selection list. Of course, if there is only
one, there will be just one displayed.

NOTE: If you want to unlock files in the current subdirectory,
and you're getting the display of locked subdirectories,
just hit "enter" to select the current directory.

When you select the locked subdirectory, SAFELOCK will search
the log files and find the password for that subdirectory (If
you don't unlock the log file that contains the password, the
subdirectory will not be unlocked!).

SAFELOCK will inform you that it's attempting to access the
subdirectory and prompt you for the password. Once properly
entered, SAFELOCK will display the list of log files or will
prompt for the password of the only log file in that subdirectory.

Page 13
SafeLock Usage

- Command formats (Cont'd)

*Selecting files/subdirectories to unlock (Cont'd)

If the log file you unlock is the one used to lock the
subdirectory, then the subdirectory will also be unlocked when
the process has completed.

Page 14
SafeLock Appendix A

- Error Messages

---- ------------------------------------------------------------

01 - User didn't specify the lock or unlock switch at execution.

! (See Page 7 of the documentation to correct this error)

02 - SAFELOCK couldn't find the subdirectory name provided for

! Check the spelling and "backslashes" (\) to make sure the
subdirectory is defined properly. Remember, the filespec
doesn't go on the same line as the path when locking files.

03 - In attempting to make a shareware copy of SAFELOCK, one or
more files were determined to be missing.

! The files that come with SAFELOCK are listed earlier in this
document. Be sure all of the files are present (unless your
your product is registered, you won't want to copy the RFLOCKF
or RFLOCKD files). You may have to retreive the missing files
from your original SAFELOCK archive.

04 - In attempting to make a shareware copy of SAFELOCK, the program
is alerting you of insufficient disk space for the copy.

! Delete enough files from the target disk to allow sufficient
space, or start with a clean formatted diskette for your copy.

05 - SAFELOCK had a problem trying to copy the shareware files to
the target diskette.

! Check the target diskette to make sure it's not write-protected
or damaged. Also make sure the SAFELOCK files do not already
exist on the target diskette and marked as read-onlt.

06 - The SFxx.DOC file is missing, where "xx" is the current version

! The files that come with SAFELOCK are listed earlier in this
document. Be sure all of the files are present (unless your
your product is registered, you won't want to copy the RFLOCK?.EXE
files). You may have to retreive the missing SFxx.DOC from
your original SAFELOCK archive.

07 - 08 Not used - reserved

Page 1
SafeLock Appendix A

- Error Messages (Cont'd)

---- ------------------------------------------------------------

09 - User provided filespec for files to be locked, but there were
no files in the current path meeting the criteria.

! Check the filespec spelling, and make sure you're in the right

10 - User specified "unlock" at execution, but there are no locked
files or subdirectories in the current path.

! Make sure you're in the right subdirectory. To unlock files
in a locked subdirectory, switch to the subdirectory before
it, and start up SAFELOCK with the "unlock" switch.

11 - User aborted SAFELOCK using the Esc key.

12 - 13 Not used - reserved

14 - Access failed due to 3 invalid attempts at entering a
password to unlock subdirectories/files.

! - Check the spelling and try again. If you determine that you
have forgotten or misspelled the password, you'll have to call
CEACS at their tech support line for assistance.

15 - 16 Not used - reserved

17 - Critical error.... an locked subdirectory was found, but
no log file was found in that level subdirectory. When a
log file can not be found, it will be difficult to determine
the password to unlock the subdirectory. There is also a
risk that the files within that subdirectory can not be
unlocked as well.

! Call CEACS at their tech support line (Number listed in
Appendix B.

18 - Critical error.... an locked subdirectory was found for
which there was no password within the specified subdirectory.

! Although it may not be as critical as error 17, you'll still
need to call CEACS at their tech support line to determine
how to unlock this subdirectory.

Page 2
SafeLock Appendix B

- Tech Support

Unregistered Users:

Unregistered users may call CEACS for general operational questions.

If a user has locked data and can not remember their password,
they may send a diskette with a copy of the log file that they can
not access to our address below. If the file is in a locked sub-
directory, they can call CEACS for help with accessing that sub-
directory from DOS.

Any services performed must be paid for in advance from an
unregistered user, unless the problem was caused by the software
itself. The actual problem determination will be performed by a
CEACS representative, and if determined to be caused by the
software, we will do what we can to correct the problem free of
charge (Please read the disclaimer in the front of this document).

Registered Users:

When a user registers their software, they receive the most recent
release of the product. Tech support will be provided free of charge
until such time as another release has been published, or a period
not to exceed 90 days from the date of purchase.

This includes free consultation on the use of the product and
problems arising from it's use (Please read the disclaimer in the
front of this document).

Any registered user that reports a legitimate "bug" in the program
that has not been previously reported will receive the next upgrade
of the product free of charge, to include the fix which they


For Technical Support:

Address: CEA Consulting Services
5827 W. Ogden Avenue
Cicero, IL 60650

Message Line: (708) 258-2157

To report a problem:

Either send your questions or comments to the address above or
call our message line, and include the following:

Your name, address, phone number, product name, release
number and your questions or comments.

Page 1
SafeLock Appendix C
Problem Report Form + CEA Consulting Services
-------------------------- + 5827 W. Ogden Avenue
+ Cicero, IL 60650
Product Name: SAFELOCK + (708) 258-2157
+ + + + + + + + + + + + + + + +
Release: 1.5

Nature of the problem: ________________________________________




If applicable, what were you doing when you first noticed
the problem?





What types of file(s) were being used when you noticed the
problem (i.e., Database files, Spreadsheet files, etc.).




What other information can you provide that you believe may help
with problem determination?





Your Name: _________________________________________

Address: _________________________________________


Phone: (____) ____ - _________

Best time to call: ______ AM ______ PM

Page 1
SafeLock Appendix D


Product Name: SAFELOCK Release: 1.5

YES! I want to register SAFELOCK! I am enclosing a check* or
money order in the amount of $30.00 made out to:


Please send me the latest release of SAFELOCK, along with printed
documentation! I understand I'll also get no less than 90 days
technical support. I further understand that I have a 30-day
satisfaction guarantee, during which I may return SAFELOCK, no
questions asked, for a complete refund.

Your Name: _________________________________________

Address: _________________________________________


Phone: (____) ____ - _________

SCODE: 023122378363-18104-C00

Send to:

5827 W. Ogden Avenue
Cicero, IL 60650

Attention: Phil Dornan

Thank you for registering SAFELOCK. We're sure you'll be
satisfied with the product.

Page 1

  3 Responses to “Category : HD Utilities
Archive   : SFLOCK15.ZIP
Filename : SF15.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: