ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ READROOM ³ ³ Online Publication Viewing Door ³ ³ (C) Exhibit A Communications, 1992-1993 ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Upgrading from version 3.1 to 3.2 No changes need to be made if you are already running version 3.1. See below for changes to make if you are jumping from 3.0 directly to 3.2. Upgrading from version 3.0 to 3.1 1) Replace your RR-Sx.BAT files with the enclosed SEND.BAT file. If you are using protocols other than those offered by DSZ, you will need to make the appropriate changes. Please note that the SEND.BAT file is fully commented to allow you to modify it to suit your needs. 2) change your PROTO.DAT file (if you are offering users the ability to d/l files from within the door). Then new format is as follows: Ú[PROTO.DAT FILE]ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³; 1st parameter is the letter for the protocol ³ ³; 2nd parameter indicates whether or not it is a batch protocol³ ³; 3rd is th name of the protocol ³ ³Z YES Zmodem ³ ³Y YES Ymodem ³ ³G YES Ymodem-g ³ ³X NO Xmodem ³ ³C NO XmodemCRC ³ ³1 NO Xmodem-1k ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Comment lines begin with a semi-colon (;). 1) The first letter on the line should be the identifier used to select this protocol. This letter will be used on select protocol screen as well as the proper section of the download batch file (SEND.BAT). You will want to adjust this file to reflect the protocols you are offering and then del all the RR-S*.BAT files. 2) The second parameter on the line is a YES or NO. YES indicates that it is a batch protocol and NO indicates that it is NOT a batch protocol. 3) The last parameter is a short description of the protocol. It is used in the line "Please begin your xxxxxx download now". For example, the first protocol listed in the above file is Zmodem which is a batch file. The SEND.BAT file would use the section labeled Zmodem. Upgrading from version 2.x to 3.0 1) The configuration file format has changed to make room for DigiBoard support information as well as the color scheme definition lines. PLEASE read the READROOM.DOC for details. Upgrading from version 2.0 to 2.1 1) You may now keep your publication configuration information seperate from your node configurations. Simply copy the lines 10 through end of file from a configuration file to a publication list. You may call it anything you'd like, although I would suggest something like PUBS.DAT. Then, replace line number 10 in each node configuration file with the @ symbol, followed immediately by the full drive\path\filename of the publication list. On my board line 10 of each nodes' configuration file looks like this: @H:\READROOM\PUBS.DAT If you wish each node to have a different configuration file, you must use the old, node by node configuration style. See READROOM.DOC for more details. Upgrading from version 1.x to 2.0 1) New registration numbers are required. Registered users may obtain them from Exhibit A Communications. 2) Please update your .CNF files to match the format shown in READROOM.DOC. There are two new lines before the publication section as well as an additional Advanced Feature that needs to be defined for each publication. 3) PLEASE read the documentation for more information about these changes.