RighTime v2.58a                                 Copyright 1991-93, GTBecker
Released August 26, 1993                                All Rights Reserved


                   What's new in RighTime Version 2.58a?

Version 2.58a corrects unpredictable DTR behavior on /Mport while in Microsoft
Windows' 386 Enhanced mode.  This should have been included in v2.58, but
wasn't.

     On a related matter: since DTR still can still contain short glitches
     while multitasking in Windows 386 Enhanced mode, we suggest that you add
     S25=100 to your modem's active profile.  This decreases the sensitivity
     to changes on DTR.

Version 2.58 solves a long-standing difficulty with communications, provides
automatic disabling of both 0.01 DOS clock resolution and learning when
Windows in 386 Enhanced mode is resident, starts balky CMOS RTCs, and improves
stability.

     Some machines experienced serial port errors, usually showing up as file
     transfer resends or noisy faxes.  The trouble was long thought to be
     something elusive in RighTime itself, but was finally located in the
     BIOS interrupt handler.  Because of this, RighTime must be inoperative
     during critical serial port use since it must use the interrupts that
     are at the core of the errors.  Two new techniques are available in
     v2.58 to determine serial port activity - one senses DCD (Carrier
     Detect) differently than v2.53 and v2.54 did (/Mport), and a new method
     senses IRQ activity (/MIport) - and a new dormant mode is automatically
     controlled by them.

     Version 2.58 also uses a different process to start the CMOS RTC; some
     machines refused to start properly, causing a failed selftest and
     subsequent program load abort.

     If RighTime is running in its high resolution (0.01 second) mode, and
     Windows is in 386 Enhanced mode, the clock in DOS sessions behaves
     poorly.  This is due to the non-preemptive multitasking technique used
     in Windows which cannot guarantee prompt interrupt response.  RighTime
     v2.58 senses this condition and automatically disables high resolution
     mode while Windows in 386 Enhanced mode is present, essentially an
     automatic /TH.

     If the time is set from within Windows in 386 Enhanced mode, the time
     will be set late and the resulting false error will improperly affect
     the correction values.  By default, learning is now disabled for time
     sets from within Windows 386 Enhanced mode, as well as the first set
     that follows any such sets.  If the user insists, a switch (/LW) enables
     learning under these conditions.  All other RighTime functions operate
     normally, but the user is still cautioned to not trust that the time
     indicated while in Windows 386 Enhanced mode is correct.  The Windows
     clock is usually a second or two late without RighTime or less than one
     second late with RighTime, and it does not increment smoothly.

     Several internal improvements have increased the timing stability; 
     TestTime now usually shows measurement-to-measurement variations on the
     order of tenths of milliseconds.  TestTime and TestIncr are improved and
     RighTLog and SetupRT2 match RighTime's changes.

Version 2.54 added two new switches, /I"name" and /#.  These ease the handling
of unexpected or unwanted date and time sets, and allow the system date and
time to be protected from inadvertent or unauthorized changes.  Internal
improvements were implemented to reduce DOS clock jitter to below one
millisecond.

Version 2.53 was the first release since v1.1 (v2.00 to v2.52 either never
left the shop or went only to beta testers over an 18-month development
period).  From version 1.1, there were many improvements.  If you are a v1.1
user, you'll need to read the document, RighTime.TXT, to catch up.

Changes in RighTime.TXT are indicated by asterisks on the left margin.