
               RELEASE NOTES for OCTOPUS version 1.6



This release of Octopus includes executable code
that runs on Intel, Risc, Alpha, and PowerPC platforms.

The User Guide included in the package contains
the  necessary instructions for running Octopus and dealing
with common configuration issues.


Table of Contents

A.  Installing Octopus
B.  Uninstalling Octopus
C.  Octopus 1.6 Features





		A. INSTALLING OCTOPUS


" This note includes quick installation steps:  System
Guide has complete details on installation options. "


1. Place the Octopus diskette 1 in a drive.

2. Log on to Windows NT with Administrative privileges (local account),
 if you have not already done so.

3. Select Run from the Program Manager or File Manager File
Menu and type [drive]:SETUP in the Command Line box (where
[drive] represents the drive letter associated with the
floppy drive).  E.G. a: setup.

After initialization, the Setup program will prompt you
through the Octopus installation.

4. Once Setup has completed, a Windows NT Octopus program
group is created in the Program Manager containing the
Octopus control program.





         	B. UNINSTALLING OCTOPUS 


1. Place the Octopus diskette in a drive.

2. Log on to Windows NT with Administrative privileges, if
you have not already done so.

3. If Octopus is running, Uncheck Auto Start Service and EXIT Octopus completely.

4. Reboot the machine.

5. Select Run from the Program Manager or File Manager File
Menu and type [drive]:UNINSTAL in the Command Line box
(where [drive] represents the drive letter associated with
the floppy drive).  E.G. a: uninstal.

Uninstall will remove Octopus from your system.


	C.  Octopus 1.6 Features

 
1.	NIC Selectability	 
	Currently, Octopus does not necessarily use a specific NIC (Network Interface Card) for communication purposes
	 (presuming more than one NIC is installed).
	Modify Octopus to allow the user to specify a NIC to be used for forwarding of Octopus related data.  This will allow
	 the user additional flexibility for managing network load.

2.	Put Errors in the Event Log	 
	Currently, Octopus records all of its errors in its own error log which can only be viewed from within Octopus.  This
	 presents a problem for those users who are setup to inspect/monitor the NT Event Log for errors.
	Modify Octopus so that it will put its errors, warnings, and/or informational messages in the Event Log in addition
	 to the Octopus error log.  The user will be provided with the ability, via the Octopus Options menu, to select which
	 Octopus messages (i.e., error, warning and or informational), if any, to have put in the Event Log.
	Provide the user with the following additional buttons within the "Octopus - Message Log" window:
	View Error Messages-  displays all error messages contained in the log.
	View Error and Warning Messages-  displays all error and warning messages contained in the log.
	View All Messages-	 displays all messages contained in the log.

3.	Save Network Sites List		 
	Currently, Octopus only retains the list of network sites that was gotten as a result ofa "GetList" performed from
	 the Attach window, or a "Get Network Sites" performed from the Add Specification windowwhile the associated 
	window remains open.  Consequently, once the window is closed, the Get Sites function needs to be reinitiated to
	 get the network sites, resulting in the time duration required to get the site information.
	Modify Octopus to retain the site information gotten from a "GetList" or "Get Network Sites" function.  Therefore,
	 if the user performs another "Attach", the retained site information will be displayed in the "known sites" box.  
	Additionally, in the Add Specification window, the user will be able to click on the "selection arrow", associated with
	 the "target site" box, to display the retained site information.  Once a Get Sites function has been performed, the
	 "Get" and "GetList" buttons will be modified to say "Update", and the date and time of the last Get/Update will be
	 displayed adjacent to the "Update" button.

4.	Exclude Specific Type of File and/or Sub Tree	 
	The user will be able to exclude specific files like:
	*.tmp; *.bak 
	This option will be under ADD SPECIFICATION.

5.	Send MSG to ADM when the Target is Rebooting		 
	The target machine will send a msg to the admin. of the network advising that the target will rename and reboot.

6.	Circular Mirroring		 
	Octopus will be able to do circular mirroring, only one to one.

7.	Mirror Shares from File Manager 
	Octopus will mirror the shares from file manager.

8.	Incremental Synchronization
	Octopus will do incremental synchronization, only the files that have diferent date, time or size will be synchronized.  

9.	Disk Space Monitoring  
	Octopus will monitor the disk space under the OCTOPUS\DATA directory. The user will be able to specify when Octopus
	 should stop the mirroring. The specification will be done by disk space specification.



Release Notes   02/14/96
