If you are already running a V7 C-BBS then IGNORE THIS FILE. It describes changes that you must make to your system if you are still running a V6 C-BBS and are now converting to V7.20. Note that if this is the case you must also read the notes.72 file. Version 7.0 of the mailbox code now uses a new structure for the MAIL.DAT file. IF you are still running a V6 C-BBS then you must convert your mail.dat file to the new structure. Place MBCONV10 in the same directory as your messages. Then run the program and you will have a converted MAIL.DAT file located in your MB/BBS subdirectory. If you have your MAIL.DAT file in some other subdirectory you can use something like "MBCONV10 work:bbs" with command line arguments. That will place the mail file in the work:bbs subdirectory. Make sure you make a backup of your old mail file in case something goes wrong. This version of the C-BBS mailbox will only work with a converted mail file. It will halt operations if it sees the wrong mail file when it loads. Also the older versions of C-BBS will not load with the converted mail file. So make sure you have a backup of your old 'MB' and MAIL.DAT. If all else fails, you can use them to bring back up 6.7X C-BBS by just copying them back onto your system. Make sure you use the new MBRESTM as it is different from the old one. You MUST also add the number of days you want to keep BID's in the config file. If you forget, on the first BID compress cycle, you will lose all the current bids, and have them transferred to the BID.TMP file. If you do a bid compress again, then you will lose all your bids.. So make sure you add to the config file, the number of days you want to keep bids.. It is on the same line as (Max # of calls in of forwarding mail list) in the lower half of the config file. You must also ADD three lines to the config. These are for the Entering of the QTH by the user... So you add YES (Prompt QTH) and then later on in the config you add the "*** Please Enter NQ......" and " NOT your callsign......".. So you add three lines in the proper places and also add the number of days for BIDS... Compare your current config.mb file with the one supplied with this distribution to see where the changes have occurred. Some features: New Command "XB" puts the bbs back online after a manual forward. BULLETIN.MB is now changed to BULLETIN.A, BULLETIN.B, ETC. It is now related to the port that a user connects on. You can have the same or different files for each user port. (NOT in AMIGA ( A new log program is included.. MAKELOG by NK3T does a nicer job of ( sorting and listing information for the sysop. Sysop listing using the ';' will now show where you got the message and where it is forwarded to. Doing a LK ; will show more information about each message. "<TOBBS" FROMBBS is where the message came from; TOBBS is where you forwarded the message. When a user does a listing command, if there are more than 24 headers in the list, the user will get the pause line, and listing will be halted until the user answers, "Any key to continue, Q to quit". Only listing commands are checked for pauses. A New Command for users - "NP" toggles the pause on or off as they want. When a user reads a traffic message, he will be given the option after reading the message to either take the traffic or not. If the user answers "Y", the traffic message will be killed, and if enabled a Service message will be created. A new listing command for sysops and users. "LS WHAT" will scan the headers for a match and list them. The TO, FROM, BBS, BID, And TITLE fields are scanned. The BID.MB file is now compressed automatically when the mail file compress is done. The amount of days to keep bids is placed in the config.mb, and your BID file will be renamed to BID.TMP, and a new BID file created with bids no older that the number of days in the config.mb.. You can now cause other windows to do an "XI" from the SYSOP program. Doing an "AA" command in SYSOP will cause a "XI" to take place on the "A" port window. Doing a "A1" will cause a "X" on the "A" port window. So "AA" and "A1" will cause forwarding action on the "A" port. Doing "AB" or "A2" will do the same thing on the "B" port window, and so on with "AC" or "A3" for the "C" port, etc.. A powerful forwarding command using "XI BBS CALL" allows forwards to BBS with any match of CALL in the mail file. Meaning that if you want to forward a message, that is NOT in the list of calls for a bbs, you can do so with this command. OR if the band is weak and you wish to forward out a message first, you use the message bbs in CALL, and the mailbox will forward out this message first, before going thru the list of calls in the forward file. After the forward of any match to CALL, the normal list of calls in the forward file takes over, and forwards out what needs to be forwarded. The mailbox now prompts the user for his QTH.. The QTH is added to the user's record and you also have the ability of editing the user's QTH.. Also the QTH is added to the WP response. Another common problem was that the user could enter his own call for his home bbs. This is no longer permissible and the user will get prompted to enter the callsign of a full time bbs.. Adding the word HUSER to the hold section of the config will cause all local user entered bulletins to be placed on hold. Only local users who enter bulletins will be placed on hold. This hold is not visable to the user but will not allow the bulletin to be forwarded out, or be visable to other users, until the sysop manually changes the hold to normal. The "F" command now has a new option "I" which if NOT used will NOT put the internal headers of a message in the file. So using the "F" command for message to file will not include any internal headers unless you specify the "I" as an argument.