Due to the desire to get the 1.34 version of Am_Nix out, and the fact that I'm several weeks behind schedule... There was no time to revise the MAIN doc file. So... use this 'quickie' doc file in addition to the main file. The single most important feature of version 1.34 is a new time/cost accounting module. In honor of Mr. Peter Naleszkiewicz, the nice man at Telenet who watches over the PCP portion of Telenst's business, I have named this module.... The PETER METER!!! There is new gadget called 'Usage Summary' which is a toggle. Click on it to open/close the Peter Meter window. Besides the summary information you see in the PM window, a detail log of all PCP 'CONNECTS' is kept. Each entry in this log consists of the Date/Time of the 'CONNECT'(local from your Amiga, so keep your clock set accurately if you want accurate records), the city CONNECTed and total time of that 'CONNECT'(this info from the Network itself) and finally Date/Time of 'DISCONNECT'(also local from the Amiga). If at any time, you do not terminate Am_Nix normally(for example, you get a visit from the GURU)... Immediately turn off your modem. Then, re-boot your Amiga, SET THE DATE AND TIME, and immediately run Am_Nix. When you re-run Am_nix, it will notice that the detail file is incomplete, and will post the current Amiga time as the time of 'DISCONNECT' along with a notation that the session was aborted. If you follow this procedure, your local detail records will always be 'insync' with Telenet's within a tolerance of a minute or two. Also new to version 1.34, are modified routines to handle the aborting of calls to CITIES and/or BBS's. Normally, when you ask for an abort, it is desirable to delay the actual abort until the completion of the current iteration of the dialing cycle. The reason for this is so that Am_nix can receive and process *all* of the responses that the Network normally sends. In previous versions this was handled in various ways, none of which were all that great. (Version 1.22 and 1.23 had the 'Waiting 30 seconds...' countdown timer). With 1.34, there are two kinds of aborts called soft and hard. With a soft abort, Am_Nix waits for the completion of the current dialing cycle. Hard aborts are instantaneous. To do a soft abort, simply click the CLOSE gagdet in the dialing status window. The word 'Aborting...' will appear to indicate that an abort will occur as soon as the current dialing cycle is complete. If you do not wish to wait for the cycle to complete, click the CLOSE gadget *again* to effect a hard abort. Please be aware however, that if you do a hard abort too quickly, Am_Nix may get out of 'sync' with the Network. If that happens... Well.... don't say I didn't warn you!! I recommend a hard abort only when you are CERTAIN that the Network is really hung up. The third new feature in version 1.34 is user definable SET commands. The only comment I have to make about them is that I *strongly* recommend that you *not* remove the two lines of default SET's that I have defined. They are important to the proper operation of Am_Nix. In order to implement these changes, additional entrys to the main configuration file(amnix.config) were required. The new format of amnix.config is as follows(no change to the first five lines): LINE CONTENTS COMMENT 1. PCP12345,ABCD1234 *your* PCP account info. 2. comm Name of your terminal program. 3. LEVEL.ONE (or LEVEL.TWO) Type of interface to your term program. See main doc file. 4. df1:files/ Path where all the other Am_Nix configuration files may be found. See main doc file for important info regarding this line. 5. ATDT 353-1818 The command to be sent to *your* modem to dial your local PAD. 6. df1:files/detail Complete file spec for the file where your detail time accounting info will be stored. 7. df1:files/summary Complete file spec for the file where your summary time accounting info will be stored. 8. 1 The number of 30-hour blocks of connect time that you have purchased from Telenet. 9. 2 The number of *lines* of SET commands that you will include on the following lines. 10. SET? Line one of SET info. 11. SET? Line two of SET info. Please note that is is VERY important that you specify all SET commands with a question mark suffix. Also note that you should give careful consideration to the entrys on lines 6 and 7, particularly line 7. The file specification entry must be WRITE ENABLED and available to be written AT ALL TIMES. In fact, the summary file,(line 7) is actually written once every 60 seconds. The reason for this is that in the event of an abnormal termination(for example, a GURU meditation error), your summary information will be up to date within 60 seconds. If you don't wish to keep any detail or summary info, simply assign these two lines to RAM:file1 and RAM:file2. The file that is specified as the detail file contains the information that has been outlined above. It is updated every time you DISCONNECT from a city. The file that is specified as the summary file contains only the total number of MINUTES that have been accrued while CONNECTED since the last time the files were cleared. The data in the summary file plus the parameter from line 8 are used to display the information in the Peter Meter window. By the way, the next revision of Am_Nix will include the ability to clear these two files via a gadget. For the time being, it will be neccessary to clear them manually at the end of each month, by using the Amiga editor. I have included an example of what each file should contain in it's cleared condition. I suspect it would be wise to retain each months detail file for awhile, to use as reference in case any of Telenet's infamous billing SNAFU's occur!! Just rename it to the appropriate month.... For example, rename detail june.