WinTAR - TAR (Tape ARchive) for Windows Version 2.06
====================================================

Copyright (c) 1994-96 SpiralCom Communications Inc.
All Rights Reserved.

This README file provides up-to-date information regarding WinTAR
Version 2.06 that may not be included in the help file.  Please read
the help file for detailed information about WinTAR Version 2.06.

********** System Requirement **********

+ A 386 or above IBM compatible PC with at least 8MB RAM and 2 MB free hard
  disk space.

+ Windows 3.1 or Windows for Workgroup with Win32s 1.30A (*), Windows 95, 
  and Windows NT 3.5x or above.

+ Windows Sockets DLL (such as Trumpet Winsock or Microsoft TCP/IP)
  The Winsock DLL can be interfaced to an ethernet card or a modem (using SLIP,
  PPP, etc.) or whatever hardware interface that it supports.

+ For network backup/restore mode, UNIX workstations equipped with storage 
  devices such as tape drives and availability of services "remote exec" or 
  "remote shell".

********** File List **********

After unzipping this archive, you should receive the following files:

licence.txt
readme.txt
wintar.exe
wintar.hlp
wintar.inf
wintar.cnt
ctl3d32.dll
winnt\ctl3d32.dll
win32s\ctl3d32.dll

********** Installation for Windows 95 users **********

Follow the instructions below for software installation.

1) After unzipping wtar206u.zip to a temporary directory, use the Explorer
   to open up that directory.

2) Right-clicked on the WinTAR icon with the extension .inf (the icon has
   a yellow donut at the lower right hand corner.)

3) Select "Install".

4) Follow the instructions as displayed to locate your temporary unzipped
   folder.  Windows 95 may ask you if you want to restart the computer.
   Answer "Yes".

5) WinTAR will be installed under c:\Program Files\Spiralcm\WinTAR and
   a program group is created with the name "SpiralCom WinTAR".

********** Installation for Windows NT users **********

1) Create a destination directory for WinTAR, e.g. c:\WinTAR, and
   unzip all files into that directory.

2) Move winnt\ctl3d32.dll to your Windows installation directory under 
   system\, e.g. c:\windows\system.
   NOTE: You must remove ctl3d32.dll, winnt\ctl3d32.dll, and 
   win32s\ctl3d32.dll after the above step;  Otherwise, you may see
   "ctl3d32.dll is not properly installed" message.

3) Add wintar.exe to an existing program group or you can create a new
   program group for WinTAR.  Please make sure that the working directory
   is the same is the directory where WinTAR.exe is located or the program
   cannot start properly.

********** Installation for Win32s users **********

1) If your Win32s is not at least Version 1.30A, you should obtain the
   latest from one of Microsoft's distribution channel.  The upgrade is
   free of charge.  Please see the FAQ section in the WinTAR help on how
   to obtain your copy.

2) Create a destination directory for WinTAR, e.g. c:\WinTAR, and
   unzip all files into that directory.

3) Move win32s\ctl3d32.dll to your Windows installation directory under 
   system\, e.g. c:\windows\system.
   NOTE: You must remove ctl3d32.dll, winnt\ctl3d32.dll, and 
   win32s\ctl3d32.dll after the above step;  Otherwise, you may see
   "ctl3d32.dll is not properly installed" message.

4) Add wintar.exe to an existing program group or you can create a new
   program group for WinTAR.  Please make sure that the working directory
   is the same is the directory where WinTAR.exe is located or the program
   cannot start properly.

5) If you are using Windows 3.1x and NOT Windows for Workgroup, you must
   add the following line your config.sys if it is not already there.  Then,
   reboot your computer.

   install=c:\dos\share.exe

********** Known Bugs/Problems/Limitations **********

The following problems are not documented in the Help file.  For other
problems, please refer to the Trouble-shooting guide or the FAQ.  If those
documents cannot solve your problems, you can find more information from
our Web page located at http://www.spiralcomm.com.  For other problems,
please send a bug report to support@mail.spiralcomm.com.

+ The floppy disk access part of WinTAR Version 2.0 only works properly and
  flawlessly under Windows 95.  Under Win32s, it is not implemented yet, and
  hopefully, it is ready for the next release.  Under Windows NT, WinTAR may
  not be able to detect your 3.5" floppy disk drive.

+ Rarely, nothing happens when you try to access a remote device if you
  are running WinTAR under Win32s.  A workaround sometimes requires the user
  to reboot the machine and restarts Windows.

+ The REXEC protocol does not work properly if the source PC is not in the
  same domain as the destination workstation;  Use the RSH protocol instead
  if you are in this situation.  This is a limitation with the REXEC daemon.
  
********** Change Log **********
Version 2.06 - August 3, 1996
- When a large file is being backed up or restored, the WinTAR application
  does not appear to response to any mouse clicks.  This is fixed.
- If the "Do not read in Contents" entry is checked when a remote archive
  is open, WinTAR will not crash with a GPF if the "Extract" button is
  clicked.  This problem only occurs in the commercial version.
- If the RSH protocol is used repeatly, WinTAR will not complain about
  "Connection failed: address in use."
- If the REXEC protocol is used when the source PC and the destination
  workstation is not in the same domain, WinTAR does not hang anymore,
  but it will pop up a "Timed out." error message.
- If WinTAR is used in the Win32s environment, all file names are now
  lower case as in the 16-bit version of WinTAR since the 16-bit environment
  does not support long filenames.

Version 2.05 - June 22, 1996
- If there are more than 26 read permission errors, WinTAR now continues the
  backup process as opposed to stopping the process.
- For those files with the archive bit clear, WinTAR now shows them in the
  create archive dialog box.
- If the user presses the STOP button while WinTAR waits for input from 
  the remote workstation, WinTAR does not hang anymore.
- Windows 95 Help dialog box.
- An installation program for registered version of WinTAR.

Version 2.04 - March 15, 1996
- Fixed another GPF bug for those files whose modified dates are earlier than
  Jan 1, 1980.
- If there are more than 26 errors in reading files to be archived, WinTAR 
  now continues the backup process as opposed to stopping the process.
- If there are errors in a file during backing up, WinTAR now skips the
  file and continues the backup.
- Eliminated various annoying error messages popping up onto the screen.
  Those errors are now logged to a log file only.

Version 2.03 - December 26, 1995
- Fixed a GPF bug for those files whose modified dates are earlier than
  Jan 1, 1980.
- Fixed a bug in the Directory templates: when you try to modify the
  file listing for a template, the results are not saved in the registry.

Version 2.02 - December 6, 1995
- Added floppy disk support for Windows NT.  Requires at least NT 3.51.
- During archiving, when the user presses "Alt-F4", WinTAR now prompts the
  the user whether to stop the current operation or not.
- The drive names and the directory names are now properly separated and
  sorted in the list box where you select the directories/drives to be 
  archived.
- Fixed missing files and/or directories problem during full backup.
- Fixed template saving problems for the Login dialog box for Windows NT.

Version 2.01 - November 23, 1995
- Fixed a GPF bug when the path name is longer than 160 characters.

Version 2.0 - November 20, 1995
- First public release.

********** TODO List **********

+ A setup program for all platforms.
+ Windows 95 look-and-feel for user interface.
+ Add an option to allow the user to save the "table of contents" of the
  archive locally so that opening an archive would be fast.
+ Add the capability of appending files/directories to an archive.
+ Add multi-volume support that is compatiable with GNU tar.
+ Add a simple scheduler to schedule hard-disk backup time.
+ Add drag-and-drop support.
+ Allow the user to backup files selectively (archive bits, date range, etc.)
+ Command-line arguments for batch-mode processing
+ Access a local SCSI tape drive
+ Plus more...

