
			FULL ARMOR Security Utility
			  Version 2.10  1/04/93
		  Copyright 1993  Micah Development Corp.  
			 Support: (617) 489-5854
			     FAX: (617) 489-5844

This file includes information not found in the User's Guide as
well as compatibility issues to keep in mind while using Full
Armor.  See Chapter 11 "Compatibility Issues" for additional
information.  Below is a list of covered topics:

      1.   Update/General Information about Full Armor
      2.   OEM Operating Systems and Partitioning Programs
      3.   Device Driver Programs
      4.   Multitasking Environments
      5.   Disk Utilities
      6.   Disk Caching Programs
      7.   Data Compression Software
      8.   Backup Software
      9.   Laptop Users
      10.  DOS CHKDSK
      11.  DOS FASTOPEN 
      12.  Networks
      13.  Ram/Vdisk Locking 
      14.  Hard Disks with >1024 Cylinders                       
      15.  IOMEGA Bernoulli Drives      
      16.  TANDY Computers
      17.  DOS 2.x Systems
	
1.   Update Information
-----------------------
Version 2.1 has three new features:

1)  Command Line/ARMX now allow you to lock/unlock files (as well as  
directories and hard drives) without having to go through the Full Armor 
menu system.

For instance, to lock a file named SALES.WK1 in the directory \LOTUS, 
you would type ARM /LD C:\LOTUS\SALES.WK1

Wildcards (*.*) are also accepted.


2)  The boot hard drive can be locked automatically by Full Armor.

To keep your hard drive protected at all times, select Hard Drive
Auto-Lock under the Option/Alter Configuration menu to YES, then 
lock the hard drive.

3)  Full Armor now includes an icon (SHIELD.ICO) to be used from Windows.

General Information
-------------------
Full Armor has been tested and found to be compatible with many
different software and hardware products.  However, we cannot
guarantee full compatibility with every system in the marketplace. 
As a result, back up your entire hard drive before locking any
data.  

When Full Armor locks data, the data is completely removed.  As a
result, the locked data cannot be backed up, viewed, opened,
changed, or altered.  In order to use the data, you must first
unlock it.

Before locking a hard drive, make sure that you are not running any
programs that would attempt to halt the process as this could cause
loss of data (i.e., Virus protection software).

We highly recommend assigning Volume Labels to your drives for the
following reason:

When a hard drive is locked and the computer reboots, DOS will not
know that the drive exists.  As a result, DOS will automatically
move subsequent drives up in drive letter accordingly.  For
instance, suppose you have a drive which is partitioned into
letters C, D, and E.  If you lock drive D, when you reboot, drive
E will be moved up by DOS and appear as drive D.  As a result,
commands in the AUTOEXEC.BAT as well as CONFIG.SYS files may be off
by a drive letter.

Check these files and their commands before locking a hard drive.

2.   OEM Operating Systems and Partitioning Software 
----------------------------------------------------
Make sure that you do not lock the essential files that are needed
by the partitioning programs to boot (i.e., CONFIG.SYS or Disk
Manager's DMDRVR.BIN). 

Because of their unique partitioning schemes, Full Armor can lock
only one drive at a time with hard drives partitioned with the   
following software:
     
Everex Everdisk
Golden Bow VFeature Deluxe (not compatible with spanned drives)
NEC DOS Fdisk
Ontrack Disk Manager     
Storage Dimension Speedstor

Full Armor is not compatible with PC-MOS.

3.   Device Driver Programs
---------------------------
Full Armor can lock files and directories on drives which have 
been created using a device driver.  However, because these
drives do not have physical information, they cannot be locked 
as hard drives.

4.   Multitasking Environments
------------------------------
We STRONGLY RECOMMEND that you do not execute Full Armor from 
a multitasking environment.  Full Armor needs absolute control 
over writing to the drive.  

Full Armor detects when the following environments are active 
and will display a warning message:  
	  
	  Microsoft Windows 3.0/3.1 
	  MS-DOS 5 TaskSwapper
	  Quarterdeck DesqView 
	  PC Tools Task Switcher
	  Softlogic Solutions Software Carousel
	  Digital Research DR DOS 6.0 TaskMax

5.   Disk Utilities 
-------------------
Full Armor is compatible with popular utilities such as Norton and 
PC Tools.  However, before using Norton Disk Doctor (NDD) or PC Tools
DiskFix to repair drives, unlock all hard drives.
     
When a file or directory is locked, Full Armor places a message
'Files Locked' within the locked directory.  Norton Disk Doctor and
PC Tools DiskFix will report invalid files.  You can select to
remove the files or cancel.  This will not affect your locked data. 
See the "Alter Configuration/Remove 'Files Locked'" section in Chapter
6 for details.

Full Armor marks the locked data location as unavailable in order
that DOS does not overwrite the area.  As a result, unlock all data
before using programs or utilities that would mark unavailable
sectors as usable.  SpinRite II Depth 4 Pattern Testing and Norton
DiskTool are programs which can mark/unmark sectors.


6.  Disk Caching Programs
-------------------------
Full Armor is compatible with the most popular caches including 
PC-Kwik, Norton Cache, and PC-Cache.  However, if you are using a
delay-write cache, either disable the cache before locking a hard 
drive or turn off the delay-write option.

7.  Data Compression Software
-----------------------------
Unlock all data on a drive before compressing it with a compression
utility.  Full Armor can lock data on compressed drives in file and
directory mode.  However, because the drives created for the
compression are not true physical drives, they cannot be locked as
hard drives.  

STACKER - Stacker's SCHECK/CHECK utilities conflict with Full Armor.  
If you wish to check a Stacker drive, unlock all data on the drive 
before running SCHECK/CHECK.

SUPERSTOR - SuperStor's PREPARE and SSUTIL programs conflict with 
Full Armor.  Similarly, if using SuperStor with DR DOS 6.0, the DR DOS 
CHKDSK conflicts with Full Armor when checking a SuperStor drive.  
Unlock all data before using these programs.

When Stacker and SuperStor swap drive letters, the true physical drive 
is assigned another drive letter.  To lock the true physical hard drive,
select the drive letter that the compression program designated as the 
swap drive.  For instance, if you compress drive C: and it is swapped 
for drive D:, select to lock drive D:, which is really the primary drive.

If using Hard Drive Auto-Lock on a swapped C: drive, use the ARMX utility 
to create another AUTOARM.EXE file which reflects the change in the true
physical hard drive letter.  See Chapter 8 of the User's Guide for details
on how to create ARMX files.

8.  Backup Software
-------------------
When Full Armor locks data, the data is completely removed.  It
cannot be viewed, deleted, or altered.  Therefore, in order to back
up the data, unlock it, back it up, and re-lock it.  See Chapter 8
"The ARMX Utility and Batch Programming" to automate this process.

9.  Laptop Users
----------------
Full Armor automatically detects the type of video card and screen.
However, Screen D has been tailored for laptop screens.  Switch to
this screen by selecting "Change Colors" under the "Option/Alter 
Configuration" menu. 

Use INSTALL /MONO if you have difficulty viewing the screen during 
installation.

10.  DOS CHKDSK
---------------
When data is locked, the DOS CHKDSK program will show that there is
a large amount of sectors that are unavailable (or bad).  This is
OK, this is where the locked data is stored.  No repair action is
needed.

11.  DOS FASTOPEN.EXE
---------------------
Full Armor is not compatible with FASTOPEN when using the Delete
Directory Entry under the Option/Alter Configuration menu. 
Therefore, remove FASTOPEN from your AUTOEXEC.BAT or CONFIG.SYS
file before selecting this configuration. 

12.  Networks
-------------
Full Armor can be installed on the network server for all users to
access from their local machines.  See Chapter 9: "System Admin-
istration" to assign user access to Full Armor.  A network or site
license must be purchased to run Full Armor from a network.  Contact
Micah Development for details.

Note:  When Full Armor is installed on the server, users will only 
be able to lock data on their individual hard drives.  Full Armor 
will not affect data on the server.  

If you are on a peer-to-peer network such as Artisoft's LANtastic 
or Novell NetWare Lite, you must un-mount your drive before
locking and unlocking any data. 

13.  Ram/Vdisk Locking
----------------------
Full Armor supports RAM and VDISK's with Sector Sizes of 512 bytes
or larger.

14.  Hard Disks with more than 1024 Cylinders
---------------------------------------------
Full Armor is not compatible with hard disks with more than 1024
cylinders.

15.  IOMEGA Bernoulli Drives
----------------------------
Full Armor is compatible with Bernoulli drives (see 'Device Driver
Programs').  However, if your Bernoulli drive is your third 
(or greater) hard drive, remove the RCD.SYS line from your CONFIG.SYS 
file if you are unable to unlock a physical hard drive.

16.  TANDY Computers
--------------------
Tandy computers which give you the option to load from ROM 
(e.g. 1000 RL machines) or from DOS should be set to load from DOS.  
If you have already installed Full Armor and you are unable to 
retrieve drive C:, unlock the drive using Full Armor from the 
floppy. 

17.  DOS 2.x Systems
--------------------
If Hard Drive Auto-Lock is set to YES, you must change the statement
in the AUTOEXEC.BAT file.  Assuming that the ARM.EXE and ARMX.EXE 
files are in the \ARMOR directory, change the AUTOEXEC file to read
as follows:     CD\ARMOR
		AUTOARM.EXE
		CD\
		
