DeTransfer V3.27 RELEASE NOTES 
==============================

This document describes the changes and bugs fixed since v3.21.

For a description of this product and details on how to use it please refer
to the help file - DeTransfer.hlp.


Upgrading from previous versions
--------------------------------

Simply run the installation executable. It is not necessary to uninstall
previous versions or do any other specific preparation.

DeTransfer Change History
--------------------------

Version 3.27 - 19 October 2004
==============================

Bugs Fixed (since version 3.21)
-------------------------------

    * Fixed bug with the Unload function when unloading data from a DT800.
      Previously if a communications error occured during the unload then
      DeTrannsfer would start unloading the data from the beginning of the
      data store of the DT800 causing repeated data to occur in the unload
      file.

    * Fixed a bug in the creation of files for firmware upgrade by card that
      caused one of the files created on the card (loader.s) to have the 
      wrong extention (loader.dwn).

    * Fixed a bug that caused an error dialog to be shown when double-clicking
      on a command file (.dxc). You can now double-click on any .DXC file and
      it will start DeTransfer and load the .dxc file. See the note below on 
      changes to the way the detransfer.ini file is found when DeTransfer is
      started by openning an associated file (e.g. .dxc file).

    * Fixed a bug that stopped the detransfer.ini file from being saved when
      the user exited and was prompted to save the current settings. For 
      example this stopped the macro definitions from being saved if they were 
      changed and the user exited DeTransfer, was prompted to save the current 
      settings and clicked OK - nothing was actually saved!

    * Fixed a bug when sending large program files over TCP/IP (ethernet or 
      serial PPP) to DT800 that caused the send to stop for no good reason
      half way through.

    * Fixed a bug when attempting to connect to the logger with a TCP/IP
      connection and that connection cannot be established for some reason, 
      the CANCEL button and X button in the connect dialog did not do anything.
      The user was forced to wait the full timeout period.

    * Fixed a bug that sometimes caused DeTransfer to start up with the viewing 
      area of the display hidden and the only way you can see it is if you 
      maximise the screen.

Changes (since version 3.21)
----------------------------
    * Changed the connections interface to recognise all available com ports
      on a PC. Previously only COM1-COM4 were supported, unless you changed a
      registry setting. Now only the available COM ports are listed. This is
      particularly useful when using USB to RS232 adaptors.

    * Changed the DT800 firmware upgrade function to allow COM port numbers 
      above COM2. Also added support for automatic upgrade from V3.16 and 
      below to V4.00 and above (a two stage upgrade). Also changed some
      warning and information messages during the upgrade process to make 
      messages clearer.
      IMPORTANT: This changed functionality will not work if you have 
      DeLogger4V2R16 or earlier loaded as they share a common file to support
      the firmware upgrade process and the DeLogger version of the file will
      take precendence if both programs are installed. Go to the dataTaker
      web site www.datataker.com to get an updated version of DeLogger to fix
      this issue.

    * Changed the timeout for modem connections so that editing the registry
      is no longer necessary. As per Page 133 of the DT800 users manual.

    * Added extra timeout field for modem connections so that the user is not
      forced to edit the registry to set a extended timeouts when using modems.

    * The detransfer.ini file used by default is in the installation directory.
      In previous versions DeTransfer would use the detransfer.ini in the current
      directory. When DeTransfer is started by association (e.g. double-clicking 
      on a .dxc file to open it) the default detransfer.ini file in the 
      installation directory will alway be used, previously DeTransfer would have
      looked for detransfer.ini in the current directory of the file being openned.
      The only way, to use a detransfer.ini file different to the default, is to 
      explicitly specify it in the command line (using a shortcut).

New Features
------------

    * Added right mouse button click to send and receive windows to bring up 
      edit menu to allow undo, copy, cut, paste, clear, select line and select 
      all functions.


--End--