Log In Log Version 1.00 beta revision 18 Upgrading from a previous revision. Upgrading instructions Upgrading an old revision of Log In Log requires the following steps. i) Back-up your old Log In Log directory, for safety. ii) Extract all files in the archive to your Log In Log directory, overwriting any old files. iii) Create a new configuration file, if you wish to make use of the new automatic disconnection feature. iv) It is advisable to back-up your log file & start a new one, in order for the statistics calculations to work properly. It is possible that some of the entries made by old versions will not be read in properly when calculating statistics. v) If you are using Trumpet Winsock TCP Manager, reinstall Log In Log into the script files using the facility provided in the Set Scripts section of the Create Configuration dialogue of Log In Log or by manually editing the login.cmd and bye,cmd files. Don't forget to install into both these files. or i) Create a new directory. ii) Extract all files in the archive to the new directory. iii) Follow the onscreen instructions to create a new configuration file and install Log In Log into Trumpet Winsock script files (if using Trumpet). The following is important to those upgrading from a previous version/revision of Log In Log to the current one. 1) It is necessary to change the line in the Trumpet '.cmd' scripts to reflect the current executionable file name, as each revision uses a different filename for the executionable file. Upgrading necessitates running the Install In Scripts routine, from the Create a Configuration dialogue, for each script file, which will automatically upgrade the lines in the scripts. The scripts can, of course, be manually edited, instead. 2) Some old revisions of Log In Log corrupted the log file. Please, check that the header for the file consists of three lines, each separated by a blank line as between the dotted lines below:- ..........Start of lines........ Log In Log - copyright 1995 Goahead Imagination n.b. The accuracy of these figures is not guaranteed Online Session Log ..........End of lines....... Also, each entry must be separated by a blank line. Full details of the construction of log files, so that they can be manually edited, in case of corruption or if they become too long, are given in the file 'liltips.txt'.