Here's a list of changes for those who want to know:

v1.0 to version 2.07
~~~~~~~~~~~~~~~~~~~~

	My internal workings with the program. Basically got it up to where
 it is today. Days of debugging and tracking down problems. Addition of
 screens, windows, requestors, menus, opening title screen, last callers,
 system ID, message counter, calls counter, netmail ID'er, and almost
 everything else you see. You can even "1> version AeRTM full" from CLI
 and it will tell you it's version number and compilation date.

v2.08 - Apr 10, 1992
~~~~~~~~~~~~~~~~~~~~

	First public release. Seems to work fine!

v2.09 - Apr 22, 1992
~~~~~~~~~~~~~~~~~~~~

	Cosmetic change from "(1-9): View Node" to "(0-9): View node" since
 it is possible to use node #0. Also a small bug fix in the last 8 callers
 routines which gave unpredicatble errors when names were the same after
 2 calls in a row.

v2.10 - Apr 25, 1992
~~~~~~~~~~~~~~~~~~~~

	Heh, still had some of my debugging code in the program. Some users
 saw little comments flash upon their screens like "Gone to Printemup()!",
 or "Got into Part GetNodeID()" or whetever. These little "sayings" which I
 had put into the program to help me trace it's path have now been removed.
 Code size should be a little smaller, and a little faster.

	Definable peek time installed. Invoke your own delay on the command
 line, like this:

	1> AeRTM <time delay>

	Therefore, the command "1> AeRTM 6" would load up AeRTM and instruct
 it to update the information every six seconds. See "AeRTM.Doc" for more
 information on this command. Defaults to 3 sec.

	Removed a "safety option" I installed which did not let the program
 function past April 30, 1992, just in case an early version got out which
 I did not want to happen. It is now removed.

v2.11 - May 20, 1992
~~~~~~~~~~~~~~~~~~~~

	Changed the name of it from ARTM to "AeRTM" as to not get it confused
 another utility called 'Amiga Real Time Monitor" which some people have
 mistaken this program for. Hope you like it!

v2.12 - Aug 23, 1992
~~~~~~~~~~~~~~~~~~~~

	At the request of Brendan Faherty, I have made some small code
 changes. The refresh() routine had the possibility of infinite recursion
 which would lead to a stack overlow if the delay was set fast enough
 or the computer happened to be a stock (slow) machine with a slow HD.

                                    - Chris Kawchuk. [Sysop: Kickstart BBS]