====================================================================
Norton DiskLock for PCs    Version 3.0             May 01, 1994
====================================================================
Please refer to this document BEFORE installing and using the
product. This file contains the latest details regarding the current 
release of Norton DiskLock. The goal of this document is to inform 
you of the latest changes made and how to avoid known problem areas.

=============
New Features:  
=============
  
  1)  With Norton Administrator or Norton Console, Norton DiskLock can
      be distributed to workstations on a network.
  
  2)  The ability to turn off monitoring of Direct Disk Access for
      secondary users. 
      If the Prevent Direct Disk Access option is not selected, files 
      that are locked will be visible to secondary users.

  3)  The option to set passwords to be case sensitive or not.
  

===============
Items to avoid:
===============
1) Do not include accented characters in IDs or passwords.

===========================
To ensure a proper install:
===========================

  1) Set the number of available file handles to at least 20. This
     is accomplished by adding a FILES=20 statement to the
     CONFIG.SYS file.

  2) Remove any other security products, including previous versions
     of Disklock, from your machine (both hardware cards and software).

  3) Install Norton DiskLock only on a primary bootable hard disk drive,
     not on a non-bootable or removable drive.

  4) Run CHKDSK /F or Norton Disk Doctor and correct any errors detected.

  5) Run a hard disk optimizer such as Norton Speed Disk to defragment
     the hard disk, because it will increase DiskLock's performance.
                                                                 
  6) Run a virus scanner such as Norton AntiVirus to verify that no
     virus can interfere with the installation.

================
Memory Managers:
================

Quarterdeck's QEMM386 version 6.xx:

    Add EXCLUDE=8000-9FFF to your command line options.

Quarterdeck's QEMM386 version 7.xx:

   - Norton DiskLock prevents DOSDATA.SYS from executing to avoid
     unexpected results.  You will receive the message "Bad or
     missing DOSDATA.SYS".

   - Using LOADHI with the /SQF option with Norton DiskLock loaded in EMS 
     may cause the program being loaded to hang. If you experience problems
     remove the /SQF switch.

   - Using LOADHI, from QEMM versions from 7.00 through 7.02, on 
     COMMAND.COM will cause unexpected results.  QuarterDeck has 
     fixed this in version 7.03

Qualitas' 386MAX:

   - Norton DiskLock prevents EXTRADOS.MAX from executing to avoid
     unexpected results.  You will receive the message "Bad or
     missing EXTRADOS.MAX".

   - When loading Windows if you receive the error "386MAX VxD
     Error V1014: Disk Cache or Other File I/O Software Using
     EMS Memory" add the following line to your AUTOEXEC.BAT file:

          SET EMSCACHE=OK

   - When loading Windows if you receive the error "386MAX VxD
     Error V1018: NOLOW Option Required" add the following line
     to your AUTOEXEC.BAT file:

          SET NOLOW=IGNORE

     The first version of 386MAX to support SET NOLOW=IGNORE was
     6.02.  There are patches available through Qualitas to update
     6.xx to 6.02.

   - Using 386LOAD with the FLEXFRAME option with Norton DiskLock
     loaded in EMS may cause the program being loaded to hang.


All Memory Managers:

    - After changing the memory option for Norton DiskLock you
      should always reoptimize your memory configuration.

==============
Screen Locking
==============

When returning from screen locking in DOS, the screen is redisplayed
as it was when you first locked, even though processing continued in the
background.

When using the Norton Screen Saver and the Norton DiskLock Autolock
feature the timeout period for DiskLock's autolock should be set to a
smaller value than that for Screen Saver.  Otherwise DiskLock will
not lock the screen.

===========================
Windows For Workgroups 3.11  
===========================

32 bit file access won't work with DiskLock installed.  Windows
will revert to 16 bit access and display a message that IOS.386 is not
loading.  Windows will continue to function properly.

======================
Compression utilities:
======================

When installing DoubleSpace after DiskLock, DoubleSpace will prompt you
that you may be running software that is incompatible with the 
DoubleSpace install procedure.  DoubleSpace will install without
errors.  

====================
Other Items of Note:
====================

DISKLOCK -M will invoke Norton DiskLock in a monochrome mode.
This may be useful on laptops and other monochrome environments.

DRDOS 6 and Novell DOS 7, with KEYB.COM loaded, do not allow hot key 
locking with the default hot keys.  The user must switch KEYB.COM
to hardware default operation by using ALT-CTRL-F1.  Then use the 
DiskLock hot key sequence to lock the screen. To unlock, enter the 
user id and password and then use ALT-CTRL-F2 to switch back to 
locale specific keyboard operation.

Norton DiskLock captures CTRL-C sequences issued in DOS and DOS 
sessions under Windows to insure operating integrity.

With MS/PC DOS 6.x multiboot AUTOEXEC.BAT, install adds the DiskLock
program directory to all path statements found.  

If using NAVTSR on a Banyan Vines network with Norton DiskLock you must
load NAVTSR with the /NR- option before the network drivers are loaded.
After the network drivers are successfully loaded run NAVTSR again with
the /NR+ option.

The Novell Netware shell, NETX, has a known conflict with NDOS that may
be more evident after installing Norton DiskLock.  A temporary workaround
for this is to run COMMAND.COM as the primary shell with NDOS as a
secondary shell.

If you are using a disk cache program that loads from AUTOEXEC.BAT, 
we recommend placing it at the end of the file.  If you're using 
Norton Cache or Norton Speed Drive, this may also improve memory usage.
     
     
