.: U P D A T E D O C U M E N T A T I O N :. -------------------------------------------- Choose the version you want to review for Updates! (If this is the 1st time you read this Guide, then read them all to get all changes !) UPDATES IN V3.18 UPDATES IN V3.19 UPDATES IN V3.31 UPDATES IN V3.34 UPDATES IN V3.35 UPDATES IN V3.36 UPDATES IN V3.37 ------------------------------------ Documentation written by: Joseph Hodge LightSpeed Technologies Developement Updated by: The Outlaw /X WHQ RaJ-Ban Swedish /X-Dist Copyright (c) 1993-94 LightSpeed Technologies Inc. All Rights Reserved. Any copy or illegal distribution of this Documentation is prohibited. .: U P D A T E D O C U M E N T A T I O N :. The following is a list of changes to version 3.18 of AmiExpress. (01-Nov-93) CUSTOM COMMANDS MCI COMMANDS MESSAGE BASE ACCOUNT EDITOR ------------------------------------ Copyright (c) 1993 LightSpeed Technologies Inc. All Rights Reserved. Any copy or illegal distribution of this Documentation is prohibited. ========================================================================= We added a configuration option to the module icons called: PASS_PARAMETER=4 This option will tell AmiExpress to bypass checking the BBSCMD modules. This option was primarily introduced to allow a sysop to invoke an INTERNAL command from a ConfXCMD and forcing it to bypass checking the BBSCMD directory for the INTERNAL command. ========================================================================= Modified the following commands: ~SR - Show Random Files SYNTAX: ~SR_ ^ ^ ^ | | | | | ---------- pathname without security level and file | | extension | ------------- Command to show random file ------------------ Number of Random files IE: ~10SR_BBS:Logon This will look for a random file between 1-10, the syntax for the file to display is: SYNTAX: PathName.FileName[security level] IE: BBS:001.Logon200.txt This would be the first of ten files to create to be displayed by the random function, the '200' is the security level which is optional. ----------------------------------------------------------------------- ~SX - Show Sequentual Files SYNTAX: ~SX_ ^ ^ | | | ---------- pathname without security level and file | extension ------------- Command to show sequentual file IE: ~SX_BBS:Logon 1. This will look for a file called BBS:Logon which will store the last sequence of the that was displayed. If this file does not exist, the 'SX' command will create it. 2. Then it will construct a display file name based on the next sequence number as follows: SYNTAX: PathName.FileName 3. It will then look for the appropriate file to display. The actual ASCII file should contain the following information for the filename: SYNTAX: PathName.FileName[security level] IE: BBS:001.Logon200.txt --v BBS:001.Logon100.txt ----- notice the different security levels keeping in mind that they are optional. BBS:002.Logon200.txt ========================================================================= Following is a list of changes to the MessageBase system Due to popular demand we revamped the mailscan. Now AmiExpress will scan each conference for mail that pertains to the user that is online. While scanning, AmiExpress will store the msg numbers in memory until the end of the scan, at the end of the scan AmiExpress will proceed to show the user the originator of each message and then proceed to prompt the user if he/she wishes to read the mail. This method of scanning has 3 advantages: 1. The user will now know who left him/her mail prior to reading it. 2. The NewMail Scan pointer will not be updated until all the mail is read. So if the user has 2 messages '100' and '101' and he/she reads message 101 and not 100, then the next time the user logs on or does a mail scan, he/she will still be notified of message 100. 3. The NewMailScan will now remember the last valid message left to the user when the user losses carrier or logs off. ========================================================================= Following is a list of changes to the Account Editor A bug was introduced in version 3.17 of AmiExpress which was intended to allow the sysop to globally store a preset's ratio into all conferences for a given user. This change caused an error condition in that once the last conference was filled with a ratio, AmiExpress retained the last conference's attributes instead of the current conference. So this could have resulted in message base corruption in the last conference, especially if the current conference and last conference where not of the same message base type. This bug would only occur while validating users that are online or when validating a user from the message base. We have removed this bug and now everything should be fine. .: U P D A T E D O C U M E N T A T I O N :. The following is a list of changes to version 3.19 of AmiExpress. (12-Nov-93) MESSAGE BASE ACCOUNT EDITOR TIME ROUTINES SUGGESTIONS AND BUG REPORTS UPCOMING RELEASES DEVELOPEMENT ISSUES BETA TESTERS ------------------------------------ Copyright (c) 1993 LightSpeed Technologies Inc. All Rights Reserved. Any copy or illegal distribution of this Documentation is prohibited. ========================================================================= Following is a list of changes to the MessageBase system We removed the '...' which was being displayed during each conference new mail scan. Fixed a problem with deleting accounts from the message base. The previous version would not properly restore the current conference location after reseting the user's conference stats in each conference. This could have resulted in possible msgbase corruption. *REMARKS* A couple of releases ago we introduced a bug in AmiExpress which caused user's accounts to improperly reflect the number of messages the user has posted. Since the incorrect figures overwrote the user's original message posted stats, we had no way of correcting the damage that was already done, but in version 3.18 we introduced a conference maintenance function 'F5' which contains a new command option '6' which allows a sysop to reset the message posted field of the conf.db for each account for a given conference. So those who have experienced this problem, please proceed to CONFERENCE MAINTENANCE to reset the message posted field. ========================================================================= Following is a list of changes to the Account Editor Fixed the account editor so if user updates his own Time_Used using the '1' menu prompt command, the change will effect the daily time used and not only the session time used. ========================================================================= Following is a list of changes to the Time Routines Fixed the F2 and F3 online menu commands so that the user's time change will effect the daily time limits as well as the session time. ========================================================================= Following is a list of Suggestions and BugReports we would like to address. BUGREPORT: ------------------------------------------------------------------------- [11-12-93] CHB of Blizzard Hi, there is a nasty bug also in the /X 3.18 release! XPR uploads and downloads are not counted, so anyone who uses XPR protocolls can suck without end! Please remaove that bug quick! CHB of Blizzard COMMENTS FROM AUTHOR: We have researched this problem on more than one occassion and from our research have concluded that this problem is isolated to 1 zmodem xpr library which we feel is an error in the xpr library itself. If you experience this problem from more than 1 library please let us know the library names so that we may properly research the problem. ------------------------------------------------------------------------- [11-10-93] THE CHAMP /X 3.18 - MessageBase-Counters still destroyed... MCI-Command xxSR_" isn't working... only when entering values higher than 9... so that we use two numbers... the sec. level after the FileName isn't work, too COMMENTS FROM AUTHOR: Please read the *REMARKS* in the messagebase updates section of this guide to resolve the problem with your message posted values. If the problem still persists after that please inform us immediately. Please refer to the changes text in version 3.18 for the new file naming conventions for the SR and SX command. We will research this problem on our end as well. ------------------------------------------------------------------------- [11-08-93] Rad! Message base problems : The messages are again becoming blank on my bbs using 3.18 for the first conference and the first conference only??? Dunno what is causing this problem but no messages are able to be read, and I don't want to loose my message base... snief.. hehe - Rad! COMMENTS FROM AUTHOR: This problem is probably the direct result of deleting an account from the message base. This should be fixed in this release. ========================================================================= Following is a list of changes and additions to upcoming releases of AmiExpress. These changes may or may not come to pass but we would like to keep you informed. We are currently Testing a 32 node capable version of AmiExpress. This version is being developed along side the 9 node version '3.19'. The most important difference besides the 32 node capability is the fact that the 32 node version is 'pure' so that only one copy needs to be in memory at a time. During the process of making the 32 node version 'pure' we had to temoporarily disable the XPR interface capability which is what we are working on right now. The Assembly code for the XPR interface was not coded in a way that permits us to make it 'pure' so we are recoding it right now. We bring this information to you mainly because we want some feedback. If we release the 32 node version to the public there will more than likely be a revision fee. Those that maybe interested in testing the 32 node version should consult The primary support board for details on obtaining a copy. This will most likely me signing some agreements forms to include a non-disclosure form and an upgrade fee. Concerning all versions of AmiExpress: 1. We intend on providing more internal functions to the program, to include a built in last callers routine which will be configurable from MCI commands. 2. We plan on modifying the msgbase routines so that you can read a message and suppress the READ MESSAGE flag. This will be useful in instances where you read some mail and do not wish the orginator to know that you have read it yet. This is an important option to most sysops. ========================================================================= Those of you wishing to write modules or utilities for AmiExpress to obtain a profit, please consult the primary support board for information on obtaining licensing agreements and any associated fees. We will also be opening the 3 developer support Bulletin Boards in a couple of weeks. These boards will be devoted to providing the developer with any technical information at our disposal for assistance in developing and maintaining utilities and modules for AmiExpress. We will be charging an annual development fee to compensate for the time required to provide the information and assitance you may need. Those interested in becoming registered developers please consult the primary support board for further details. ========================================================================= The developement of any large scale program undoubtably requires the assistance of BetaTesters. AmiExpress is no exception (we all know that). Those interested in beta testing AmiExpress please consult the primary support board to obtain a non-disclosure form. .: U P D A T E D O C U M E N T A T I O N :. The following is a list of changes to version 3.31 of AmiExpress. (02-Jan-94) MULTICOMM PORT PROGRAM EXECUTION MCI COMMANDS INTERNAL ZMODEM PROTOCOL XPR PROTOCOLS CUSTOM COMMANDS MESSAGE BASE AMIXNET UPDATES ------------------------------------ Copyright (c) 1994 LightSpeed Technologies Inc. All Rights Reserved. Any copy or illegal distribution of this Documentation is prohibited. ========================================================================= Following is a list of changes to the MultiComm Port Since version 3.30 of AmiExpress we have increased the Maximum Number of Nodes that ACP can handle. ACP can now handle a maximum of 32 Nodes. This change involved changing the internal MultiComm structure to handle 32 nodes vs 9 nodes. This change means that the old NewChat and some of the older Online Message Send Modules may not work any longer. We have released an update to the NewChat door so that it will handle the 32 node configuration. ========================================================================= Since version 3.30 of AmiExpress you now have the ability to make AmiExpress resident. Doing this should speed up program execution and also conserve memory. Making AmiExpress resident: 1. change all nodestart tooltypes in the NODE icons to reflect the following: NODESTART=express 2. Update your s:user-startup script by adding the following after your BBS Assignment: RESIDENT EXPRESS BBS:EXPRESS ========================================================================= Following is a list of changes to the MCI Commands I have modified the ~CC command to allow the execution of MENU PROMPT commands. This will allow you to run the internal WHO command from any MCI text. Simply add this MCI command to your MCI Text File: ~CC_WHO NOTE: It is important to realise that most MENU COMMANDS should only be run from the MENU PROMPT. For Instance , forcing the READING of mail at the FRONTEND of express would not be wise because the BBS does not know who is logging onto the system. So use your own judgement on these matters. ========================================================================= Following is a list of changes to the Internal Zmodem Protocol I added the tooltype HDTRANSBUFFER, this tooltype is for the node icons. HDTRANSBUFFER allows you to change the buffer size from serial to harddisk. This option is a better alternative than using a RAMPEN because it works on a file by file basis, whereas the RAMPEN method has to wait until all uploads are complete. HDTRANSBUFFER has the following syntax: HDTRANSBUFFER= You may specifiy as many buffers as you like. The number of buffers default to 8 if this tooltype is not used. Here is a formula for determining how much memory will be allocated for transfers when the node is started: ((buffers+2)*1024)*2 ^--- This is required due to the double buffering. ie: HDTRANSBUFFER=20 would require 45,056 bytes of memory 1. ((20+2)*1024)*2 2. (22*1024)*2 3. (22528)*2 4. 45056 Version 3.30 a bug was introduced with this HDTRANSBUFFER addition. AmiExpress was not freeing the memory it allocated for the buffers. This is the primary reason for releasing this version. ========================================================================= Following is a list of changes to the XPR Protocols Interface: We have temporarily removed the XPR interface and placed it in a SYSCMD. We will most likely put this back into AmiExpress in a month or so. One of the important changes to AmiExpress besides this is now all batch Protocol Icons must contain the tooltype AE_BATCH instead of BATCH. ========================================================================= I added the tooltype 'QUICKMODE' for the module icons. This tooltype simply tells AmiExpress not to run the Module in question if the user has logged onto the sysop using the QUICK logon option. ========================================================================= Since Version 3.30 the message base has been modified to re-display the original message if a reply to a message was aborted. ========================================================================= Due to the expansion of the Net, including more sales and increased volume of mail, we realized the need for a more optimized method of packing netmail. AmiXnet currently recalculates the MailRoute for every net mail conference when it is packing mail and unpacking mail. This in itself is not efficient. Therefore I modified all of the NETMAIL utilities to recognize pre computed mailroutes, this greatly speeds up the mail packing process for those with only one Node Id. In order to invoke the optimized method of packing mail you will need to do the following: 1. Modify the scripts that run MRUPDATE with an additional commandline option 'AUTOUPDATE'. AUTOUPDATE should be the last commandline option to MRUPDATE. This will force MRUPDATE to create pre-calculated mailroutes when new maps come down the net. 2. Create a directory in BBS:AmiXnet named your node id. For instance I have a directory called: BBS:AmiXnet/703001 because 703001 is my nodeid. Once you have done the above, the next time mail is packed the netutils will create pre-computed route files and place them into the newly created directory. NOTE: ONLY DO THIS IF YOU HAVE ONLY 1 NODE ID. THERE IS A COUPLE OF BBSs WITH MULTIPLE NODE IDS, THIS OPTION WILL NOT WORK FOR THEM AT THE MOMENT. I HOPE IN THE NEAR FUTURE I WILL HAVE THIS SOLVED. .: U P D A T E D O C U M E N T A T I O N :. The following is a list of changes to version 3.34 of AmiExpress. (13-Feb-94) FOREWORD INTERNAL COMMANDS MULTINODE CHAT CONFERENCE TOOLTYPES CUSTOM COMMANDS DOORS FINAL WORDS ------------------------------------ Copyright (c) 1994 LightSpeed Technologies Inc. All Rights Reserved. Any copy or illegal distribution of this Documentation is prohibited. ========================================================================= First of all I think all of you guys, should tip your hat off to Joe this month for all the extra work he has done for this release. he has been putting in all his days and nights over the last few weekends to make all these changes. THANKS JOE. Personally I am very excited about the changes that are being incorp- orated into express and a lot more coming. ========================================================================= 1. There is a new command called 'CF'. This command will allow your users to set the way express handles conferences. From here they can set the 'NEW FILE SCAN', 'NEW MESSAGE SCAN', and turn 'OFF' and 'ON' what conferences they want to ZOOM mail from. In the Conference Maintainance option in the Account editor you can also Globaly set these options (F5). 2. In the 'W' option for users, is now the ability for the user to pick what kind of Zoom they want. They can pick QWK, or the old ascii zoom option. NOTE: You must first install some new Icons in the ZOOM dir, otherwise it wont work. Samples are included in the 'UPDATE.LHA' archive. Edit them to fit your needs ! ========================================================================= The second biggest feature is that /X now has 'MESSAGE QUE' capabilty for multinode chat. Remember when you would chat someone on another node, and they were busy doing something, and they would never get the message, well now when the user is done, they will receive the mesaage you sent them. There is a new 'NEWCHAT' door online to grab, that uses this new capability. (also included in the UPDATE.LHA package) ========================================================================= New options in the conf icons for you sysops: FORCE_NEWSCAN ------------- This will force your users to have a New Mail scan whether they have selected it or not. NO_NEWSCAN ---------- This will Force No New Mail scan whether a uers has turned it off or not. SHOW_NEW_FILES -------------- This is not a new command, but if used in the conf icon, will act like the above force command for messages IE: Force your users to get a new file scan whether they have chosen it or not. ========================================================================= Another new option is for your commands Dir. You can now make an icon called 'NODE#CMD' This is used like your CONF#CMD Option. Now your node can use it as well. ========================================================================= In this version there was also a BUG FID in the doors icons. PRIORITY= has now been fixed. If you use PRIORITY=SAME, it will use the same Priority that express uses. ========================================================================= Well I think that is all. If I have forgotten to tell you everything I will leave a message. Wow what a month. Ok enjoy the new express. Included in archieve, is also the icons needed to put in your zoom dir. For those of you useing utilities that delete everything in your Zoom directory, I advise you to stop useing them. It will delete these icons needed. Ok that's it for now. /LIGHTSPEED TECHNOLOGIES INC. .: U P D A T E D O C U M E N T A T I O N :. The following is a list of changes to version 3.35 of AmiExpress. (14-Feb-94) USER ACCESS ------------------------------------ Copyright (c) 1994 LightSpeed Technologies Inc. All Rights Reserved. Any copy or illegal distribution of this Documentation is prohibited. ========================================================================= Added a new tooltype For Access.info or /access/ACS.xxx.info ! ACS.CONFFLAGS ------------- This tooltype sets at what access a user can use the CF command. .: U P D A T E D O C U M E N T A T I O N :. The following is a list of changes to version 3.36 of AmiExpress. (14-Feb-94) BUG FIXES ------------------------------------ Copyright (c) 1994 LightSpeed Technologies Inc. All Rights Reserved. Any copy or illegal distribution of this Documentation is prohibited. ========================================================================= Found a bug in the way /X handled the PRIORITY=X In the doors icons. This has been fixed. Modified the 'CF' Command to display double lines if a user has access to more than 10 Conferences. .: U P D A T E D O C U M E N T A T I O N :. The following is a list of changes to version 3.37 of AmiExpress. (13-Mar-94) WHAT'S NEW BUG FIXES ------------------------------------ Copyright (c) 1994 LightSpeed Technologies Inc. All Rights Reserved. Any copy or illegal distribution of this Documentation is prohibited. ========================================================================= The release of 3.37 requires that a utility be run against the user.data file called 'CLEANDATA' this will insure that the obsolete areas in your user data are initialized for the use of the new 'MULTICHAT' fields and the new 'CREDIT MAINTAINENCE' fields. The syntax for running this utility is: CLEANDATA bbs:user.data This will create a backup of the user data prior to making any changes, into a file called bbs:user.data.old. ========================================================================= Added ACCOUNT CREDIT MAINTENANCE. This feature allows you to keep track of paying users, The assumption is that if a user pays, then they are paying for a DISABLED ratio. CREDIT MAINTENANCE will let you establish the number of days that the credit account is to be in effect. During this time period the user will be given an 'EFFECTIVE' DISABLED ratio. Their ratio does not actually change, but express will treat there account as a disabled ratio. So during the credit period an 'FS' command or 'S' command will reflect a DISABLED ratio. Once the credit account has expired, express will then use the ratio established for the user. There are 2 new tooltypes for the ACCESS icons, which help maintain CREDIT ACCOUNTS: ACS.SHOW_PAYMENTS = using this access, the user will be able to see when there credit account will expire via the 'S' command. ACS.CREDIT_ACCESS = this tooltype will allow a user (cosysop/sysop) to view CREDIT ACCOUNTS as long as they have ACCOUNT EDITING access. There is a new option which is not reflecting in the ACCOUNT MAINTENANCE screen, '!' , this will invoke the CREDIT MAINTENANCE screen for that particular account. NOTE: Only Sysops on the LOCAL side of the BBS will be allowed to SAVE any changes to CREDIT MAINTENANCE. Credit Maintenance will maintain a log called CREDITLOG in the BBS: directory. Modified Comsetics to CREDIT MAINTENANCE, and CONFERENCE MAINTENANCE and ACCOUNT MAINTENANCE. Modified CREDIT MAINTENANCE to allow you to turn on/off download/upload tracking for the account. ========================================================================= Modified express to not display negative numbers when showing the total time awarded for upload. ========================================================================= All OVERIDE tooltypes have been replaced with OVERRIDE, please make this change in all of your ACS icons and ACCESS icon. ========================================================================= Modified AmiExpress so that you can run a N S U or S door from the SYSCMD at logon. ========================================================================= Added new tooltype to the ACP icon 'LONG_WHO'. This tooltype will provide a seperater between each node listed in the WHO command. ========================================================================= Modified the cosmetics of the 'W' (User Account Edit) function. ========================================================================= Modified the who command to show if a user is available for chat or online messaging. ========================================================================= Added new tooltype to the node icons: 'COPYBUFFER' this allows you to specify the maximum amount of memory that you wish express to use when copying files from one partition to another. If you do not specify this, then express will try and allocate memory enough to copy the file with 1 WRITE. If course, if there is not enough memory, it will decrement by 8K blocks, until it can copy it, regardless of the COPYBUFFER. ie: COPYBUFFER=100000 ^---------100K copy buffer Added new tooltype to the node icon: 'MAX_MSG_QUE' this allows you to specify the maximum number of messages (olm/chat) that can be queued to that node. Anything that is sent after the maximum will be ignore. If this tooltype is not specified then express defaults to 5. ========================================================================= Credited a new tooltype for the Node icon called 'SCREENPENS' this tooltype is primarily there for testing the color configurations of the upload file requestor and overall screen color appearances, It is hard to explain how this works, but we have 12 color pens we can config that make up the look of the screen, and the best I can do for testing is to let you the sysop define what those 12 colors will be, so here is an example: SCREENPENS=101010110110 0 = BLACK 1 = WHITE 2 = GREEN 3 = YELLOW 4 = BLUE 5 = MAGENTA 6 = CYAN 7 = RED Now for a 1 bitplane screen (2 colors) you will use only 1 and 0, so you experiment with this, and see what you can come up with. ========================================================================= Added 'Time_Total' field to the account editor, this field keeps track of the actually maximum time the user has acrued for the day. This value has always been in the User.Data, but I decided to place it in the account editor so that the value can be manipulated. ========================================================================= Modified Logon routines so that you do not need a password to login locally, regardless of account. Modified express to update time used directly after the download is finished. Modified express to check time remaining after each file is downloaded in a batch transfer. If the time has expired, it will not allow the rest of the batch transfer to complete. ========================================================================= Modified AmiExpress to report 'WHO' to acp when running the internal who command. ========================================================================= Added ability to accept a module's name to display in the action window for a given node. Added #28 status code 'Online Message' to acp. ========================================================================= Added new tooltype to the node icons: DEF_SCREENS DEF_SCREENS tells AmiExpress to use non security screens before looking for security screens. ie: BULL30.TXT BULL.TXT In the above case, express would start it's search for screens with BULL.TXT, this can be a considerable time savings if the majority of your screens are not security oriented. Under this scheme, BULL0.TXT is now a valid security designator. As many of you know, AmiExpress searches for security oriented text in increments of 5 based on the user's password. So if a user has an access level of 255, and there is only a BULL30.TXT, then express would have to check for the existance of 88 screens prior to locking in on BULL30.TXT. By default express does this now. I am just saying, if you do not have security text or most of your texts aren't security oriented, then I recommend using the DEF_SCREENS. NOTE: if you use the DEF_SCREENS option but you have security oriented menus to display, then instead of having: BULL30.txt BULL.txt use: BULL30.txt BULL0.txt and simply do not have a BULL.TXT for that bulletin. ========================================================================= Modified express to use AmigaDos Time vs UnixTime routines. NOTE: Time is still recorded based on a UnixTimeBase. This should remove 95-99% of the ENV:TZ accesses. There may be some doors that use some of the old glue routines which may still use the unix time routines. ========================================================================= Changed the display of Chat_Left in the account editor to reflect Chat time used. Changed the WHO outline color from green to blue. Added new access tooltype 'ACS.HIDE_FILES'. This access will prevent the user from seeing which files are being transfered via the WHO command and 'NEWCHAT (who)'. ========================================================================= Added internal Online Message Sender. Introduces new Access tooltype 'ACS.OLM'. Added the ability to send OLM messages to ALL Nodes. Specify '*' when asked for the destination node. Added MultiNode Chat Time Limits to the Account Editor. These limits will be utilized by the 'NEWCHAT' door. Once we are comfortable that the 'NEWCHAT' door is streamlined we maybe hard coding it into express. Added new menu prompt option 'OLM' for online message sending. Online Messages will be queued at the destination node. The Online Messages sent to other nodes are Allocated by the originating Node, and deallocated by express at the destination Node. ========================================================================= Fixed bug with the awarding of time for uploads. If there is any other problems that you can spot with the awarding of time for uploads, please let me know. ========================================================================= There is an OLD tooltype in the node icons, called 'KEEP_UPLOAD_CREDIT' this tooltype can have 1 of 2 values '0' or '1'. There meaning is as follows: KEEP_UPLOAD_CREDIT=0 = Do not penalize a user 'time' for uploads. KEEP_UPLOAD_CREDIT=1 = Do not penalize a user 'time' for uploads and give them an additional %50 time increase to the remaining time online for ========================================================================= Fixed problem with ANSI stripper routines, when a double sequence was issued, the stripper would not strip right hehe. ========================================================================= Modified File Check routines, fixes a bug in the ERROR detection phase of the checking. ========================================================================= Fixed bug in OLM, that was created with the last version. I had a report that the time awarded actually displayed a negative, number, if this occurs, then in this version express will annotate it into the callerslog, so if you notice it, please let me know. ========================================================================= NewChat 3.37 Modified NewChat to not display a user as active 'CTRL-A' if the user has run out of time in the door. Added recognition of the 'Online Message' status. Added stat #28 'Online Message' status to express. Added new tooltype to the module icons: NAME=whatever The Module Name can be upto 15 characters in length, this name will be reported to the ACP window when the module is invoked, if you do not supply a name, AmiExpress will substitute it with the modules icon name. Modified the WHO command, to show the 'Online Message' status. Changed WHO colors from Green to Blue. Modified Paging Method, to allow the destination node of the page to deallocate the interport communications. This means that the NewChat door does not have to wait on a reply to the message from the destination node. Made some cosmetic changes. Fixed a problem with semaphore releasing in versions prior to 3.3 if a user ran out of time in the chat door and then re-entered the door then it would cause a multinode lockup. Changed WHO colors from Green to Blue. Modified Paging Method, to allow the destination node of the page to deallocate the interport communications. This means that the NewChat door does not have to wait on a reply to the message from the destination node. Made some cosmetic changes. Fixed a problem with semaphore releasing in versions prior to 3.3 if a user ran out of time in the chat door and then re-entered the door then it would cause a multinode lockup.