Beijing Paradise BBS Backup

home *** CD-ROM | disk | FTP | other *** search

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / ICHAT440.EXE / ICECHAT.DOC < prev next >

Wrap

Text File | 1997-02-08 | 74.7 KB | 1,733 lines

┌───┐┌─────┐┌─────┐ ┌─────┐┌───┐┌──┐┌───────┐┌───────┐ │░▒▓││░▒▓┌─┘│░▒▓┌─┘ │░▒▓┌─┘│░▒▓││░▒││░▒▓┌┐░▒│└─┐░▒▓┌─┘ │▒▓█││▒▓█│ │▒▓█└┐ │▒▓█│ │▒▓█└┘▒▓││▒▓█││▒▓│ │▒▓█│ │▓██││▓██│ │▓██┌┘ │▓██│ │▓██┌┐▓█││▓██└┘▓█│ │▓██│ │███││███└─┐│███└─┐ │███└─┐│███││██││███┌┐██│ │███│ └───┘└─────┘└─────┘ └─────┘└───┘└──┘└───┘└──┘ └───┘ Deluxe Splitscreen ANSI/ASCII Chat Utility For RemoteAccess v2.xx, ProBoard v2.xx Dorinfo1.Def & Door.Sys Compatibles v4.40 Release Date: 02/08/97 ────────────────────────────────────────────────────────────────────────────── IceChat v4.40 - Copyright Jeremy Landvoigt, 1993-97 - IceChat v4.40 ────────────────────────────────────────────────────────────────────────────── ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Some Of IceChat's Features ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ {+} Indicates registered only. * IceChat is a split screen chat utility for RemoteAccess/ProBoard BBS packages. It can be used with many other BBS types as long as they support Dorinfo1.Def/Door.Sys type Doors. * IceChat support 10, that's TEN different TOTALLY configurable chat screens! * IceChat has a special chatmode for ASCII users. * IceChat has file transfer support! {+} IceChat allows the users to post a comment in the area of the SysOps Choice. It requires an external message editor for this purpose. This function requires the Hudson or Jambase message Base type to work. * If the SysOp doesn't answer the page, and you are using RA/PB IceChat will update the [Wants Chat] flag causing it to be activated on the SysOps status line, and the users total number of pages for the call will be incremented. This is ONLY possible when using RA, generic Dorinfo1.Def systems are not supported by this feature. * Configurable Emergency page option, password protected. This is activated when a user has paged outside of paging hours. If they chose to emergency page, they must enter a password. This can be disabled by leaving password blank when configuring IceChat. It can also be configured so that only users ABOVE a set security level will be asked for the emergency page password. * IceChat v4.40 will seek out Remoteaccess 2.xx and read in crucial information from the BBS configuration to make IceChat v4.40 even easier to install than it already is. * A configurable page tune for those users that are in your VIP.CTL Textfile * IceChat is Easily configured, unlike many programs SysOp's have to deal with. * Online User Editor : IceChat has an Online User Editor Built in so that the SysOp can edit the users Profile without having to exit back to the BBS. (RA/PB Compatible) * Can play random page tunes * Defined Macro Listing in Chat * And MUCH MORE!! ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Setting Up IceChat Using ChatCfg.Exe ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ To Setup IceChat, please read this section thoroughly! Then also read the section of these documents that apply to the Installation of IceChat into the particular type of BBS system you are running (i.e. RA, TG etc) Note: Menu items that are followed by '{+}' are REGISTERED ONLY features, and will not be active until you have registered IceChat and obtained a valid key. When you run CHATCFG.EXE, you will be presented with a series of pulldown menus. In this section we will step through each menu in turn and explain in some detail what you need to enter in order that IceChat will be configured correctly. The cursor keys are used to move around the configuration program, left and right will move between the various pulldown menus, and the up and down keys will step through the items on each menu or submenu. SYSTEM -------- · Save & Exit - Selecting this option will save any changes you have made and exit to Dos. · Exit Without Save - Exit ChatCfg, but DO NOT save any changes made. · Operator Names - · BBS Name - Enter the name of your BBS system. · SysOp Real Name - The name of the System operator. If you are a registered user of IceChat, this name MUST be exactly the same as the name that appears in the registration key. · SysOp Alias - System operators Alias (if used). If this is enabled, IceChat will use the Users alias aswell. · CoSysOp 1-3 Names - Enter up to 3 Co-SysOps in these fields. To select a CoSysop for Chat, run IceChat with a parameter ranging from A-C, or you may select the CoSysOp for chat from within IceChat while the pagetune is playing. i.e. IceChat.Exe /A - would cause IceChat to use the #1 Co-Sysops name instead of the SysOp's name. OR You may press 1,2 or 3 while the page is playing to select a CoSysOp for chat. · External Filenames - · MsgBase Path {+} - Path to your message base, i.e. C:\RA\MSGBASE NOTE TO RA SYSOPS: IceChat DOES support the JAM message base at this time. The area selected for IceChat to post messages into MUST be specifically configured to be either a HUDSON base OR a JAM Base. · Chat Log Path - The path and filename of the chat conversation log, if enabled. · Logfile Path - The path and filename of the logfile IceChat should use. This can either be a seperate logfile, or IceChat can append to your BBS logfile if you so choose. · External Editor {+} - The full path and command line of the external message editor you want to use such as IceEdit. This will be called whenever a user leaves a message to the SysOp when a page has not been answered. Please refer to the documentation for the message editor of your choice for details of the required command line. · External DOS Util - When shelling to DOS using the Alt-J function within IceChat, you have the ability to call up a program automatically by enabling this option. If you enter the path and filename of a DOS utility, when you shell to DOS IceChat will ask if you want to invoke your Dos program - You can then select 'Y' to run it, or 'N' to go straight to Dos. If you leave this field blank IceChat will just shell to Dos as normal, you will NOT be asked to press Y/N. · Regular Pagetune - The path and filename the 'Normal' pagetune to be used by IceChat (i.e. C:\ra\Icechat\Page.Ice). · VIP Pagetune - The path and filename of the 'VIP' pagetune to be used by IceChat (i.e. C:\ra\icechat\Vip.Ice). This tune is used for VIP users who's names are stored in an ASCII control file called VIP.CTL. See the section of these docs about the Files Used and Created by IceChat for more info on this file. · Transfer Protocols - · Protocol - Enter the name of the external protocol you are using. · Send - Enter the path and filename of batchfile or external program which will be used to send user files. · Recieve - Enter the path and filename of batchfile or external program which will be used to recieve incoming files. · Trigger - Enter the code or string that IceChat should interpret as a remote protocol attempt to transfer files. · Auto Upload YES/NO - Should IceChat automatically activate the inbound commandline when trigger is detected. · Confirm YES/NO - If Auto upload is activated, should IceChat quickly prompt SysOp for confirmation. · ANSI bulletins · Page Header - File displayed to user when IceChat is first activated. · Not Available - File displayed to user when SysOp doesn't answer the page. · Out Of Hours - File displayed to user when they have paged outside of scheduled paging hours. · Page Exceeded - File displayed to user when they have paged too many times. · Page Warning - File displayed to user when they are about to exceed maximum number of pages. · Page Hangup - File displayed to user when they are going to be hung up on for paging excessively. · Finished Chat - File displayed to user when they have completed a chat session. · Language Editor NOTE: IceChat now has the ability to use a number of macro characters that will be translated when it is run. These can be used in the various 'Strings' that can be displayed to the user. See the seperate section of these docs for more info on the macros and their usage. · Greetings String - String displayed to users when the SysOp first enters chat. This string will only be shown once per program execution. Leave blank to disable. · User Editor String - String displayed to users when the user record is being altered, by using the built in user editor in IceChat (RA/PB only). · ASCII Dump String - String displayed to users when SysOp is preparing to view an ASCII file. · Drop To Dos String - String to be displayed to users when the SysOp Drops To DOS. · SysOp Help String - String displayed to users when SysOp is viewing local help window by pressing F1 (Function key F1) when in Chat. · Page SysOp String - Enter the string displayed to users when paging the sysop. · Page Reason Header - Reason for page header. i.e. "Why do you want to chat with Jeremy?" · Message String - The string to be displayed when IceChat asks if the user wants to enter a message to the SysOp if the chat request is unanswered. If you are unregistered, make this a statement such as "Why Not Leave The SysOp A Message?". If you are registered, make this a question such as "Would You Like To Leave The SysOp A Message? ". · "Not Here" String - The String to be displayed when either 1) The page expires when the SysOp doesn't answer it. 2) The SysOp has defined the user as a "quiet user". · "Page Time" String - The string to be displayed when the user pages outside of scheduled hours, before a time slot later in the day. · "Tomorrow" String - The string to be displayed when there are no more page slots left in the day. · Template Manager - With IceChat, it is possible to define up to 10 COMPLETELY CONFIGURABLE chat screens. Use the template manager to define window dimensions and clock locations. When in IceChat, you can call up each of these screens with the ALT-Fx keys. The corresponding Template ANSi will be displayed. This chart is the Template Manager. Use it to configure all of the above fields. Screen File - Full path and filename to the ANSI template file. Clock Type - Choose between DISABLED, 12 HOUR, and 24 HOUR clocks. - Position - Choose clock X,Y co-ordinates - Colours - Choose clock foreground,background colours Date Type - Choose between DISABLED, and 4 different date formats. - Position - Choose date X,Y co-ordinates - Colours - Choose date foreground,background colours Timer - Choose either DISABLED, or ENABLED toggles. - Position - Choose timer X,Y co-ordinates - Colours - Choose timer foreground,background colours Window 1 + 2 Setup - - Boundaries - Select top-right corner of window, and then bottom left corner of window. Leave a minimum of 4 LINES in window. - Name Position - Where should the sysop/user name be displayed? Leave as 0,0 to have the name centred on the top border of the window. - Max. Name Length - Enter maximum name length. Any names which exceed this value will be truncated. - Colours - Configure name and window background colour. Additionally, it is possible to alter a template record WITHOUT using the template manager. In order to create a screen layout, it is usually necessary to either create the screen, and record the necessary location values to be later entered into the manager, OR create the screen in the manager FIRST, and then design your custom ANSI after. It is now possible to combine the two steps. If you create an ANSI with special SCREEN LOCATION CODES, IceChat will automatically import the cursor locations into the template manager, leaving only simple preferences such as colour configuration for you to deal with. The following are screen location codes which IceChat will import, if configured to do so. ^R1 Sysop Window X1,Y1 location (top left) ^R2 Sysop Window X2,Y2 location (bottom right) ^R3 Sysop name location (X,Y) ^R4 User Window X1,Y1 location (top left) ^R5 User Window X2,Y2 location (bottom right) ^R6 User name location (X,Y) ^R7 Clock location (X,Y) ^R8 Date location (X,Y) ^R9 Timer location (X,Y) · Program Info - Gives detail of the current version of IceChat including release date and any crucial fixes. TOGGLES --------- · Alias Usage - Should IceChat use the SysOp's & User's alias as defined above? Yes/No · Force Greeting - Should IceChat use the 'Greeting' string when a 'Forced' chat is initiated by the SysOp. · Suspend Time - Should IceChat freeze the users time whilst in chat. · Allow Remote Exit - Are users allowed to terminate a chat? If set to NO, only the Sysop will be able to stop the chat by pressing [Esc] or Alt-X. · Allow CTRL-G beep - Should users be allowed to beep with CTRL-G. · Chat Logging Enabled - Should the conversational log be activated when chat is initiated. · Use 24 Hour Clock - Should IceChat use the 24h clock in it's string translations? COLOURS --------- Here you can define what colours IceChat should use for various types of text. You can select the colour you prefer for any of the following : · .SYS represents the SYSOP window text colour configuration .USR represents the USER window text colour configuration · Punctuation · Numbers · Capital Letters · High Bit ASCII · Reason Bar · SysOp Name · User Name · Time Clock · Chat Timer · Status Line · Default Settings - Selecting this option will restore IceChat's 'Default' colours. Select the colour you prefer by entering the number indicated in ChatCfg.Exe. IceChat will then use these colours when in chat. PAGE SETUP ------------ · Page Hours - The page hour setup in IceChat has been greatly improved since v3.60. In previous versions, you could only have one time slot per day ranging from an earlier hour to a later hour. Hours couldn't extend past midnight. This was very inconvenient to those SysOps who are 'Nighthawks'. So, as of v4.40 a new system is in place. If you refer to the chart above, you can see that the days of the week are listed at the left, and each hour of the day across the top. Every square on the grid represents an hour of the day. The two blocks within each square represents an half-hour slot. For Example: ╔══╤══╤ ║00│01│ <-- Hour of the Day, Starting at midnight ╔══╬══╪══╪ Day Of Week --> ║Su║■■│■■ ╚══╩══╧ ^----- Represents 1:30a to 2:00a. ^----- Represents 1:00a to 1:29a. By toggling these little blocks on or off, you can configure as many half- hour paging slots a day as you want, at whatever time is convenient for you. · Page Duration - How long (in seconds) IceChat should page the sysop. · Maximum Pages - How many times a user may page in one session. This feature can only be used if RA is the BBS package. · Page Reason Length - The minimum number of characters a user MUST enter as a page reason. If the user enters LESS than this amount IceChat will exit and inform him/her that the reason is too short. · Password required to page the sysop outside normal paging times. The user will need to enter this password BEFORE IceChat will call the SysOp, in this way regular or trusted users can page you at any time. They MUST also have a security level ABOVE the level set in 'Emergency Security' for this feature to be used. · Emergency Security - The MINIMUM security needed by a user before they will be given the option to FORCE an 'Emergency Page' outside normal paging hours. Users with a security BELOW this level will NOT be given the option to page outside the normal hours. See also 'Emergency Password', the two emergency options (Password and Security) work in combination with each other. · Configure Display - · Reason Bar Colour - Colour of the page reason brackets · Elapsed Character - The character which fills in time already elapsed in the countdown bar. · Elapsed Colour - The colour of the elapsed character. · Remaining Character - The character which fill in the time which is left in the countdown bar. · Remaining Colour - The colour of the remaining character. · Configure Toggles - · User Page Warning - Should IceChat warning user when they are paging excessively. · Exceeded; Hangup - Should IceChat hangup on user when they have paged excessively. · Exceeded; Twitlist - Should IceChat add user to the twitlist when they have paged excessively. · Beep Remotely - Should IceChat beep remotely while paging. · Use Countdown Bar - Should IceChat use the countdown bar while paging. · Fake Page - Should IceChat fake the page when twit users run IceChat. MACRO SETUP ------------- · Macro Editor - This menu option will bring up a submenu that will ask for a 'Keyword' and a 'Macro' that will be used in place of the 'Keyword' as explained below. You can also configure the colour that will be used when these macros are displayed. There are five pages available for you to enter macros. They are explained below. Pages #2-#5 are ONLY available to registered users of IceChat, unregistered users are limited to one page. - User Keyword - The word to be translated by IceChat, i.e. RA - Macro - The replacement to be used by IceChat, i.e. RemoteAccess IceChat has the ability to translate Macros when in Chat mode, here you can enter the macro and what IceChat should convert it to. i.e. RA = RemoteAccess. You will be asked for the original word and then for the replacement, enter "RA" (as the original) and RemoteAccess (as the replacement) then whenever you type "RA" when in chat mode, IceChat will convert it to "RemoteAccess" (without Quotes). You have two pages in which you can enter any macros you wish. It is useful to also place common mistyped words here too, i.e TAHT (User Keyword) - THAT (Macro) then every time you accidentally type 'Taht', IceChat will convert it to 'That'. Control strings may also be used in macros. For Example, if your key word is "HT!" and the Macro is "Hi There @F!", when "HT!" is typed in chat, it will be replaced with "Hi There Jeremy!" For example. Available control strings are listed in a seperate section of these documents. With IceChat, it is possible to use color codes into your macros. This is very easily done. Wherever you would like to have a colour change in your message, type one of the following codes: |00 - Black |01 - Blue |02 - Green |03 - Cyan |04 - Red |05 - Magenta |06 - Brown |07 - LightGray |08 - DarkGray |09 - LightBlue |10 - LightGreen |11 - LightCyan |12 - LightRed |13 - LightMagenta |14 - Yellow |15 - White - Colour Once you have entered a "User Keyword" and it's accompanying "Macro" IceChat will ask for a colour. This is the colour that the Macro will be displayed in when in chat. An Asterisk (*) will show the colour you have selected. · MacroFile Sorter - Allows you to sort macrofile in alphabetical order by User Keyword, and will close any gaps in the macrofile. · Macro Triggers - Configure punctuation which will trigger macros. · Macro Toggles - · View Macros YES/NO - Should users be able to list macros which are available? · Create Macros YES/NO - Should users be able to create their own macros? · SysOp Window YES/NO - Should macro translation be active in the Sysop window? · User Window YES/NO - Should macro translation be active in the user window? MESSAGES ---------- · Board Number {+} - The number of the message board as defined in your BBS config. This only applies if you are using the HUDSON style message base. If you are using JAMBASE, make sure you specify the full path and filename of the JAMbase in the files setup. · Message Flags {+} - Message Type - Private, Public, Or Both - Select the message attribute. If set to 'Private/Public' IceChat will ask if the message is Public or Private before it is saved. · Area Name {+} - Name of the message area used to post messages into if the sysop does not respond to a chat request (or if he/she manually aborts the request) · Memo Comment - The string to be appended to messages left for the sysop. · Conditions - · Out Of Hours YES/NO - Should users be allowed to leave comments when they page out of hours. · No Answer YES/NO - Should users be allowed to leave comments if the sysop doesn't answer. · Excessive Page YES/NO - Should users be allowed to leave comments if they have paged excessively. · Failed Password YES/NO- Should users be allowed to leave comments if they've failed the emergency page password? · Twit Page YES/NO - Should twits be allowed to leave comments? · SysOp Abort YES/NO - Should users be allowed to leave comments if the SysOp aborts the page? · User Abort YES/NO - Should users be allowed to leave comments if they abort the page? OTHER ------- · Chat Border Type - Choose one out of a selection of three different types of chat windows borders that you would like to use while chatting with the user. · BBS Type - Select the BBS software you are using. This is essential for the correct operation of IceChat. - RA v2.xx/PB v2.xx If you are using either RemoteAccess or ProBoard, this option should be selected to give the most that IceChat has to offer. - Dorinfo1.Def Compatible If you are not using RA, IceChat can still use the generic Dorinfo1.Def file which is generated by *most* BBS packages. Check your BBS documentation to see if it can generate a Dorinfo1.Def file. - Door.Sys Compatible If you are not using RA, IceChat can still use the generic Door.Sys file which is generated by *most* BBS packages. Check your BBS documentation to see if it can generate a Door.Sys file. · Name Brackets - Select the brackets ( {([ ) that will be used when displaying the SysOp's or Users name in IceChat. Please note that the configuration file is not a text file, so you MUST use CHATCFG.EXE to configure the program, and the configuration file must be named ICECHAT.CFG. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Upgrading From v4.35 to v4.40 ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ This couldn't be easier! Simply copy the files from the v4.40 distribution archive into the directory you have IceChat installed and run CHATCFG.EXE. This will upgrade all of the previous version's configuration to the format needed by v4.40. Please Note! Failure to upgrade your previous configuration files will result in an error message being displayed if you attempt to run ChatCfg.Exe or IceChat.Exe. You should also step through each of the pulldown menus in CHATCFG to ensure your setup is correct. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Installing IceChat Into RA v2.xx Systems ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ Please read the section of this document entitled 'Setting Up IceChat Using ChatCfg.Exe' BEFORE attempting to install IceChat into RA. Failure to setup IceChat correctly before installing it into your bbs program will probably result in IceChat failing to run or not running as expected. If you are using RemoteAccess or ProBoard, and you wish to take advantage of the added features for these BBS Packages, you MUST be running RemoteAccess v2.xx, ProBoard v2.xx or above. IceChat's added features will not work properly with older versions of these software packages. In order to run IceChat.Exe, you must have a fossil driver active. A fossil driver such as BNU should work fine with IceChat. If you don't have a fossil driver installed, a simple error message will be displayed, and the program will stop. A fossil is not required when running in local mode. We will now run through EVERYTHING you need to do in order to get IceChat to run in your RemoteAccess setup. 1. Extract all the files in the distribution archive to a directory of your choice. C:\RA\ICECHAT is recommended and is assumed to be the directory you are using from now on. 2. To help IceChat find it's configuration files, you need to define an environment variable for it in this manner in your AutoExec.Bat : SET ICHAT={PATH TO ICECHAT DIRECTORY} PLEASE NOTE, THE ENVIRONMENT VARIABLE NAME IS ICHAT - NOT ICECHAT !! The environment variable is used by IceChat to find its system files and configuration. Failure to setup the environment variable can result in IceChat failing to run correctly - YOU HAVE BEEN WARNED! Please see your DOS manual for more information on environment variables. NOTE: You will need to reboot your machine after entering the environment variable for it to take effect. 3. Run ChatCfg.Exe and configure all of IceChat's options as explained earlier in this document. You MUST configure IceChat for it to work correctly! Refer to the section of this document for setting up IceChat. 4. You will now need to edit your .MNU files to include IceChat so that when a user pages you it will execute IceChat instead of the internal chat routine built into RemoteAccess. IceChat can be run using either a type 7 or a type 15 menu command. A type 15 menu will require a batch file that is called to execute IceChat, a type 7 menu only needs to have the command line to execute IceChat on the Optional data line of the menu. See your BBS manual for more information on type 7 and type 15 menus... Decide which type of menu command (Type 7 or type 15) you wish to use and then do ONE of the following depending on which menu type you have chosen to use: Type 7 Menu Command: Optional Data: <command line> [control codes] Description: This function will run an external program, or door in a shell while the user is on-line. Example command lines for Type 7 usage: Calling IceChat in either a single line or multiline system you would use: Single Line: C:\RA\ICECHAT\IceChat.Exe -d:C:\ra *! *M Multi Line : C:\RA\ICECHAT\IceChat.Exe -d:C:\ra\line*N *! *M In a single line system, calling CoSysOp #1 (NOT the sysop) you may use... C:\RA\ICECHAT\IceChat.Exe -A *! *M The following RA parameters are used in the above examples: *M Activate the MemorySwap feature. RemoteAccess attempts to swap itself and all the memory it occupies to XMS and EMS memory (if available) or to disk, leaving only 3KB resident. This is ideal when running memory-hungry programs but takes a few seconds longer in order to perform the swap. If the swap cannot be accomplished, RemoteAccess will attempt to load the program in a normal shell. *N The current node number, as specified by the -N command line parameter when RemoteAccess was loaded. *! Freeze the system timer for the duration of the shell. Type 15 Menu Command: Exit to DOS with errorlevel Optional data: <errorlevel> Description: This function causes RemoteAccess to exit to DOS completely, returning an errorlevel to your BBS batch file. The optional data field should contain the errorlevel that you wish to pass to the batch file. The batch file should trap the errorlevel and act accordingly. If you use this exit while the user is still on- line, the user may be logged back into RemoteAccess using the command line parameter -R. This forces RemoteAccess to read the EXITINFO.BBS file that was written at the time of the exit so that it can restore system and user information, presenting the user with the TOP menu. NOTE: Errorlevels 0 through 5 are reserved for internal use by RemoteAccess. For a complete description of these internal errorlevels and how they are used, see the Errorlevels section of the Reference chapter. If you decide to use a Type 15 menu to call IceChat you will need to add IceChat into your BBS batchfile and call IceChat with the errorlevel you have chosen. :START IF ERRORLEVEL 10 GOTO ICECHAT IF ERRORLEVEL 5 GOTO NET&ECHO IF ERRORLEVEL 4 GOTO ECHOMAIL IF ERRORLEVEL 3 GOTO NETMAIL IF ERRORLEVEL 0 GOTO START_UP GOTO START_UP :ICECHAT CD\RA\ICECHAT ICECHAT.EXE <Don't forget IceChat's Parameters!> RA -R GOTO AFTER_BBS In this example, a TYPE 15 menu command with an Errorlevel of 10 will make the batch file execute the command following the :ICECHAT label. Include the line "RA -R" to return to the board after the external programs have been executed. NOTE: DO NOT FORGET to include the correct command line switches for IceChat in your batchfile. Failure to do so will result in IceChat not functioning as it is intended. See the section of this doc file for more info on IceChats parameters. 5. Make sure you have changed ALL of the menus you wish to call IceChat from and that you have saved the changes. 6. IceChat also needs to be setup in RACONFIG.EXE so that when you break in to chat with a user it calls up IceChat and NOT the internal RemoteAccess chat. Change to your RemoteAccess directory and run RACONFIG.EXE 7. What you do next depends on wether you have registered RA.... If you HAVE registered, Goto OPTIONS, PAGING and then to 'External'. Enter the following command line: C:\RA\ICECHAT\IceChat.Exe -F *E *M *! If you are NOT running a registered version of RA you will need to setup IceChat so that it is called from a Function key, as the above example will ONLY work if you have a registered copy of RA. Instead you will need to do the following. Goto MANAGER, AltFn Key, and choose a blank entry to install IceChat into. We will assume entry 1. Enter the following command line: C:\RA\ICECHAT\IceChat.Exe -F *E *M *! If you are running an UNREGISTERED copy of RA, and have chosen this second example, you will need to call IceChat by pressing Alt-F1 instead of the Alt-C command which would be used when it is installed in a REGISTERED version. These are only an example to get you going... Please refer to the section of these docs about 'parameters' to ensure you have the correct command line to execute IceChat. 8. Please make sure that there is a Page.Ice in your BBS System Directory, or in your IceChat Directory. IceChat requires this as your page tune. A selection of sample page tunes has been included, just rename the tune of your choice to Page.Ice. 9. When you run IceChat, be sure that the IceChat.Cfg file has been created. If it has not, then you MUST run ChatCfg.Exe. If you don't, and attempt to run IceChat.Exe directly, IceChat will display an error message that IceChat.Cfg doesn't exist. That's all there is to it.... Please make sure that there is a Page.Ice in your BBS System Directory, or in your IceChat Directory. IceChat requires this as your page tune. A selection of sample page tunes has been included, just rename the tune of your choice to Page.Ice. If you have enabled a seperate tune for VIP users the tune you wish to use should be named Vip.Ice and this should also be placed in either your system or IceChat directory. BOTH tunes must exist for this feature to work, if the Vip.Ice tune does not exist, or cannot be located by IceChat the default Page.Ice file will be used instead. When you run IceChat, be sure that the IceChat.Cfg file has been created. If it has not, then you MUST run ChatCfg.Exe. If you don't, and attempt to run IceChat.Exe directly, IceChat will display an error message that IceChat.Cfg doesn't exist. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Installing IceChat Into Dorinfo1.Def/Door.Sys Systems ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ Please read the section of this document entitled 'Setting Up IceChat Using ChatCfg.Exe' BEFORE attempting to install IceChat into your Dorinfo1.Def/ Door.Sys compatible system. Your BBS MUST be capable of producing a Dorinfo1.Def/Door.Sys drop file for IceChat to run correctly. If IceChat fails to find this file it will abort with an error message! Because of the number of slight differences between various BBS systems it is impossible to give a detailed explanation of EXACTLY how to install IceChat into any Non RemoteAccess system. However, if you follow the basic ideas outlined in the sections of this document about installing IceChat into RemoteAccess it should give you the general layout of what is necessary. Please refer also to the documents for your particular BBS system for any differences in layout or command line parameters. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Sysop and User Function Keys ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ Easy To Use SysOp function keys : F1 : Display Help Status Pop Up Menu PGUP : Initiate file transfer to remote user ALT-Fx : Toggle Chat Template (1..10) ALT-B : Blacklist User (Security Lockout) [RA/PB Compatible] ALT-E : User Editor [RA/PB Compatible] ALT-H : Hang Up ALT-J : Drop To DOS ALT-L : Line Noise Key ALT-T : ASCII TextFile Dump to modem & screen ALT-X : Force Program Exit Easy To Use User Keys : CTRL-L : List/Add to available Macros (if enabled) CTRL-W : Clear Window CTRL-R : Redraw Screen ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Substitution Strings In Commandlines ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ The following codes can be used in any external filename that IceChat calls upon. These codes are based on the same ones that are used by RemoteAccess. *C - replaced with COMSPEC environment variable. *M - swap to external program. Not necessary in IceChat as IceChat auto attempts to swap to memory or disk. *N - node number that IceChat is being executed under. *B - User's current connection rate. *P - Current port that is being used by IceChat. *T - User's Timeleft. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Control Codes Used In TextFiles ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ IceChat now has the ability to interpret and convert control codes which are imbedded in textfiles that IceChat displays to the user. The following are valid codes that IceChat can use. This information (referring to available ^F and ^K codes) can also be found in your RemoteAccess documentation. Control Code Information Displayed ──────────────────────────────────────────────────────────── ^K1 Number of the current template message area. ^KA Total system calls. ^KB Name of last caller (any node). ^KF Number of times user has paged the Sysop during this session. ^KI Time in 24-hour format. ^KJ Today's date. ^KL Seconds connected (always returns zero). ^KM Minutes used today. ^KN Seconds used today (always returns zero). ^KO Minutes remaining today. ^KP Seconds remaining today (always returns zero). ^KQ Daily time limit. ^KR Connect speed. ^KT Daily download limit (in Kb). ^KW Node number (as set on command line). ^KX Terminates the current call. ^K/ Clear to end of the current line. Control Code Information Displayed ──────────────────────────────────────────────────────────── ^F! User's default protocol setting. ^F# User's current file group. ^F$ User's address line 1. ^F% User's address line 2. ^F& User's address line 3. ^F' User's sex (Male/Female). ^F* Current file group number. ^F+ Current message group number. ^F[ User's download limit. ^F3 User's handle. ^F4 Date of user's first call to the system. ^F5 User's date of birth. ^F6 Subscription expiration date. ^FA User's full name. ^FB User's location. ^FD Business/Data telephone number. ^FE Voice/Home telephone number. ^FF Date of last call. ^FG Time of last call. ^FH A Flags setting. ^FI B Flags setting. ^FJ C Flags setting. ^FK D Flags setting. ^FL Credits remaining (cents). ^FM Total messages posted. ^FN Last message read. ^FO Security level. ^FP Total calls to the BBS. ^FQ Number of files uploaded. ^FR Kilobytes uploaded. ^FS Number of files downloaded. ^FT Kilobytes downloaded. ^FU Minutes used today. ^FV Current screen length setting. ^FW User's first name only. Control Code Information Displayed ──────────────────────────────────────────────────────────── ^RA Sysopname as defined in ChatCfg. ^RB BBSName as defined in ChatCfg. ^RC Co-SysOp name #1. ^RD Co-SysOp name #2. ^RE Co-SysOp name #3. ^RF Full name of user. ^RG Area name in which comments to SysOp are posted. ^RH Beginning time of next page slot. ^RI Ending time of next page slot. ^RJ Time elapsed within chat. ^RK Time of day. ^RL Today's date. ^RM User's security level. ^RN User's location. ^RO User's first name. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Macros In IceChat Configuration ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ ** NOTE : All MACROS and the following strings and headers (UserEditor, ASCII, Drop To DOS, SysOp Help, Page Reason String, and Paging Header) can all make use of built in control strings: @1 = CoSysOp name #1 @2 = CoSysOp name #2 @3 = CoSysOp name #3 @A = SysOp alias @B = BBS name @C = Chat duration @D = Date @F = User's first name or alias @S = SysOp name (Read From IceChat Configuration) @T = Time of day @V = Program version number @Y = Next pageslot begin time @Z = Next pageslot end time The control strings can be used in the following manner. For Example, if you were configuring your Page Reason String to ask the user why they are paging, you could put: @F, Why Would You Like To Chat With The SysOp? And then when IceChat is run, and asks the user who is "John Smith" in this example to enter a page reason, the @F will be replaced, and the string will appear to the user as: John, Why Would You Like To Chat With The SysOp? All the control strings can be used in a similar manner in all the other Strings & Headers, as well as macros. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Errorlevels used by IceChat ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ IceChat will terminate on different errorlevels depending on what conditions IceChat encounters during runtime. Here is a list of hardcoded errorlevels which IceChat uses. Errorlevel Definition ------------------------------------------------------------------------------ 0 No error has occured, normal exit. 1 Error initializing fossil driver. 2 Configuration file can not be found. 3 Version conflict has occured, try upgrade util. 4 Configuration error has occured, make sure settings are correct. 5 Dropfiles (Exitinfo.bbs, Dorinfo1.Def or Door.Sys) Can't be found 6 User posted a comment to the SysOp. 7 Carrier was lost! 8 A file is corrupted. 9 User daily time limit has expired. 10 User paged, but not answered. Did not post a comment. 11 User exceeded pages per session limit. 12 The users page reason was not long enough. 13 The user paged the SysOp out of defined hours. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ BBS System Files Used By IceChat ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ See also the section on 'Files Created & Used By IceChat' later in these docs. When executed, IceChat calls upon the following Files from your BBS System: ExitInfo.Bbs - Read/Write To Exitinfo.BBS, to adjust time limit, read in the User's Name, Location, baudrate etc.. and to indicate the [Wants Chat] at the bottom of the SysOp's screen after exiting IceChat. Also accessed by IceChat's User Editor. Dorinfo1.Def - Read in user Information When using RemoteAccess, IceChat also calls upon the following files as well as those above : Ra.Log - IceChat writes out to this file to indicate the User's Paging reason (If you set your Logname to your Ra.Log) PageStat.Ra - IceChat uses this to determine whether or not The SysOp has disabled the paging by using ALT-O in RemoteAccess. If Paging is set to [OFF] Then no page tune will be heard on the Sysops end when the user pages This file is only used if it can be found in the System directory defined in ChatCfg. If you have registered your copy of IceChat, it will also read and/or write to the various BBS message base files if you have allowed the user to post a message to the SysOp if the chat request is not answered. If you are not using RemoteAccess, the only file that is read from is the Dorinfo1.Def or Door.Sys BBS drop file. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Parameters Used When Executing IceChat ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ There are many parameters that can be used for IceChat. They are : -D:[PATH] This will cause IceChat to use the specified [PATH] to locate the dropfiles that IceChat will read in. This is a change since the previous versions, which had a limit of ten paths in the configuration program. This new change will allow for more than 10 paths. -F This will cause IceChat to abort the page reason prompt and jump directly into chat mode. This would normally be used when the SysOp instigates a chat with a user, OR if you do not want IceChat to ask for a reason when paging. -L This will cause IceChat to run in local/testing mode so that the SysOp is able to test it out. -N:[NODE] This will cause IceChat to acknowledge what node of the BBS that it is being executed on. -RANDOM[#] This will cause IceChat to load a chat template randomly within the range of 1 to [#]. -TP:[#] This will cause IceChat to load up the template which corresponds to [NUMBER] when chat mode is entered. -A/B/C This will cause IceChat to change the SysOp name to either CoSysOp #1,#2, or #3. Co-SysOps names are defined in ChatCfg. IceChat.Exe This will cause IceChat To wait for the user to enter a page reason. If they are outside of paging hours, a message to that effect will be displayed, and they will return to the BBS. These parameters may be used in almost any combination when executing IceChat, It is IMPORTANT that you select the right parameters for IceChat to run correctly, so please read this section carefully and refer to the various examples given for setting up your particular BBS in the relevant section of these documents. There is one more parameter that was added in during the v4.20 betas. I had planned on removing it, however I've left it in for those who really need to finetune IceChat to their system. This parameter controls how much timeslicing will occur in multitasking environments. The LARGER the value, the LESS slicing that occurs. IceChat defaults to 20, which is the optimum value on all test systems. Following is a symptom/solution chart: Symptom: | Solution: ------------------------------------------------------------------------- IceChat, when run in a | IceChat is giving up TOO many timeslices multitasking environment is | in your multitasking environment. You really slow, although the | should INCREASE the value, so that IceChat other windows run fine. | gives LESS timeslices. ------------------------------------------------------------------------- IceChat runs absolutely | IceChat is "hogging the CPU" (it's not great in my environment, | giving up enough timeslices). Correct for with no lag or delays. | this by DECREASING the value, so that However, while IceChat is | IceChat gives up time slices more running, my other windows | frequently. slow to a crawl. | ------------------------------------------------------------------------- The parameter to use to adjust IceChat's slicing is: /S:[value] - [value] represents the slice value, as outlined above. We recommend you play with this only if *** YOU REALLY KNOW WHAT YOU'RE DOING! *** ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Files Created & Used by IceChat ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ IceChat creates a number of files for it's own use, these include it's main configuration file and macro file etc. There are also a number of ANSI files that you can create yourself using an ansi editor (such as TheDraw). These ANSI files will be used by IceChat during its operation. See the following list for a full rundown on the files that are created and/or used by IceChat. !! ALL of these files MUST reside in the same directory as IceChat.Exe !! ─────────── ICECHAT.CFG ─────────── This files stores IceChat's main configuration. It is created by ChatCfg.Exe and MUST be present for IceChat to run. ─────────── MACRO.CFG ─────────── Macro.Ice file is an encoded file that you MUST use ChatCfg to edit. Do NOT use a standard text editor. It contains words that will be replaced in chat with new words. For Example, if you type "BBS" in chat, it will replace it with "Bulletin Board System". These are all SysOp Defined. ──────────── NOPAGE.CTL ──────────── NoPage.Ice file is an textfile that you can use any text editor To edit. It contains any names of users that you feel shouldn't be allowed to page. When the user enters the page reason, it will appear that the music is playing from the remote end, but no page music will be heard on the Sysop's end. You do not HAVE to use a NoPage.Cfg, but it is always handy to prevent yourself from being annoyed by the constantly paging user that every BBS has. ──────────── RANDOM.CFG ──────────── Random.Cfg file is a text file that you can create. It contains any page tunes that you would like to have randomly selected and played everytime a user pages. When the user pages, IceChat will read in all of the page tunes listed in this file, and will randomly select one to be played. Please note, if this file exists, the VIP page tune will not be played for VIP users. The Format is simple : Page.Ice Dallas.Ice Dance.Ice Axel_F.Ice That is a simple example. You do not have to use these particular tunes, just replace these names with the page tunes you prefer. These tunes must be in your IceChat directory. If it can't find the random pagetune that it selects, it will default to page.Ice. A file containing various page tunes is included in the release archive. ──────────────────── PAGE.ICE & VIP.ICE ──────────────────── These are standard RemoteAccess page tunes that IceChat will play while paging. Page.Ice is used for normal users, and Vip.Ice is used for VIP users. These files must be located in either the IceChat directory or the main BBS System directory. These files will not be used if the Random page tune function is active. ─────────── VIP.CTL ─────────── Very Important Person TEXTFILE - use a different tune for these Users. This file is a simple ascii text file which contains a list of user names that will use the Vip.Ice pagetune when they page the SysOp. It's format is simple, just enter each user that you wish to use the Vip.Ice pagetune, ONE name per line as follows: Jeremy Landvoigt Vince Maggio Dave Carter Michael Huggins ────────────── NOTAVAIL.A** ────────────── This is an ANSI/ASCII file that can be displayed if the SysOp is unable to (or chooses to abort) the users page. You can create this file using any standard ANSI/ASCII editor. ────────────── OUTHOURS.A** ────────────── This is an ANSI/ASCII file that can be displayed if the user pages outside of the SysOp's paging hours. You can create this file using any standard ANSI/ASCII editor. This file is ONLY Displayed when user pages out of hours and there is NOT a defined emergency password. ────────────── TEMPLATE.x ────────────── Any TEMPLATE.x file that you use MUST be in 24x79 format, and they MUST be saved in ANIMATED mode in TheDraw. If you dont save them like this, it is possible for them to scroll off the bottom of the screen by one line, and thus mess up the display. YOU MUST SAVE THEM IN THIS FORMAT TO WORK !!! The "x" represents the template number. 1 & 2 are hardcoded, but 3 - 10 can be defined using ChatCfg. If you create this file, it will be used by IceChat to replace the default chat modes (Horiz/Vert). This file is NOT necessary, but is included so that you can make IceChat look like the rest of your BBS setup should you wish to. Simply create an ANSI screen using an ansi editor (TheDraw) And name it TEMPLATE.x. This file MUST be in the same directory as IceChat.Exe. ────────────── MACROHDR.ANS ────────────── Included in the release archive is an ANSI screen named SAMPLE3.ANS, It is used to replace the header at the top of the macro listing feature. the screen has to be renamed to MACROHDR.ANS to become active. If this screen is not available in your chat directory IceChat will use its built in screens. {+} ───────────── PAGEHDR.ANS ───────────── It is used to replace the header at the top of the main paging screen. The screen must be renamed to PAGEHDR.ANS to become active. If this screen is not available in your chat directory IceChat will use its built in screen. This file can only be 7x79 characters in size. {+} ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Frequently Asked Questions ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ Q: Is it possible to run Icechat from RA's external chat feature? I have the path and filename set correctly, but RA's default chat mode always comes up. A: This is most likely because your copy of RA is Unregistered. This RA feature is only available in the registered version. Change from using RA's external chat routine and use a Function key instead. This is explained in the section of these docs about installing IceChat into RA. -- Q: IceChat is ignoring the necessary configuration files that it requires at startup. What is wrong? A: There are two possible solutions. 1st: Make sure that none of the IceChat files are WRITE-PROTECTED. If they are, IceChat will simply ignore them. 2nd : Make sure that you have set up an icechat environment variable. ie. SET ICHAT=C:\bbs\doors\chat This will allow IceChat to find its configuration files no matter where IceChat is run on the System. Otherwise, it will be necessary to run IceChat from a batchfile that will CD into Icechats home directory. EG: @Echo OFF Cd \BBS\DOORS\CHAT ICECHAT.EXE Cd \BBS\Ra -- Q: When I try to run IceChat, it gives me a conversion error similar to "Invalid IceChat.Cfg : Please run v4.35 -> v4.40 converter". What is wrong? A: This is most likely because you have just recently upgraded to a newer version of IceChat and not run the conversion utility. The solution would be to run the Conversion program (CHATCFG), or to delete your IceChat.Cfg file and start the installation from scratch. -- Q: When I try to run GEdit with the registered copy of IceChat, GEdit always runs thinking that it is in LOCAL mode. A: When you install GEdit into IceChat, make sure that you use the following commandline: [Path]\Gedit.Exe *P *B *T <kbt> <kbt> represents the keyboard timeout value in seconds. -- Q: I am running a registered copy of IceChat, and have configured my external editor correctly in ChatCfg. However when the page is not answered and a user attempts to leave a comment IceChat says "Swapping Out For External Editor.." and then freezes. What is wrong? A: This is a known bug, which only affects some systems. If you are encountering this bug, it is most likely because you have a *M on your external editor commandline. Remove this *M, because IceChat will automatically attempt to swap out when loading the editor. -- Q: When a user pages, it ALWAYS pages no matter what the hour is, or it does the exact opposite and either A) never emits any sound or, B) tells the user that I'm unavailable even during page hours. What is wrong? A: There are two possibilities here. The first possibility is that you have your RemoteAccess override engaged. When you are logged onto RemoteAccess, try hitting ALT-O. If it is set for always ON or always OFF, IceChat will respect this setting and abide by it, regardless of page hours setup. The other possibility is that you have your scroll lock key engaged. If scroll lock is ON, IceChat paging is OFF. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Registration ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ The Development of IceChat v4.40 took many long hours, and a lot of time and effort not to mention money. This program is NOT FREEWARE. If this program satisfies your expections of a chat utility, if not MORE, then you are expected to register it after an evaluation period of 30 days or sooner. By doing this you can be sure of continued development of the software. Thanks for your support. This Program may be freely distributed but DO NOT under any circumstances change any of the executables or alter any files that come in the original distribution archive. I urge you to register as soon as you can! The more registrations that I have will show the interest of people in the program, and I will release a newer version with many more features. If you register, the IceChat built in message editor will be available and the extra Macro editing screens. Also, all "Unregistered" messages and almost inaudible beeps within the program will be removed. Please note that the status of features (whether they are available or not to unregistered users) may be changed without further warning in later versions of the software; but this does not mean that they will be changed. If you wish to register, please fill out the registration form : North America ------------- Register.Can - Registration Form For Canadian Users Register.Usa - For the U.S.A, and for all other Registrations Australia --------- Register.Aus - Registration Form For Australia Please at this time send ALL registrations to the address listed in the correct registration form. Thank you for your support. Any Registration forms that have invalid or missing information may be considered void and not be processed, depending on the extent of the errors. Due to recent events, I have changed my policy on personal cheques that are sent in to pay for registration. I will continue to honour them, however as of this release, there will be a 3 week hold placed on the cheque to ENSURE that it does NOT go N.S.F. Although most people are honest about this, lately too many people have sent in N.S.F. cheques, and when contacted about them, show little or no concern about them or the financial difficulties they may have caused. Additionally, a service of $15 will be levied against any N.S.F. cheques. Until both the full payment, and the service charge is recieved in the form of a MONEY ORDER, the registration will not be processed. In conclusion to the above information, to ensure a speedy turnaround time it is recommended you send your registration in the form of a money order (or direct deposit for Canadian residents) If you do choose to send in a personal cheque, it means that you have read and understood these conditions. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Archive Contents ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ IceChat v4.40 has been compressed using RAR, and should be a self-extracting (SFX) archive. The archive should be approximately 207k in size. This archive should have an authenticity verification seal by Jeremy Landvoigt. If this archive is not in RAR/EXE format, or if the seal has been broken, it is may be advisable to get a new archive from one of the support sites listed at the end of the documentation. The IceChat archive should contain the following files : ICECHAT .EXE - The Main Program CHATCFG .EXE - Use to configure the program ICEPLAY .EXE - PageTune Player PAGES .EXE - Archive containing sample pagetunes ICECHAT .DOC - Program Documentation HISTORY .DOC - Feature addition history ICEBETA .APP - Support site application form WHATSNEW.440 - Changes (Additions/Deletions) in IceChat v4.40 REGISTER.USA - Generic Registration Form REGISTER.CAN - Canadian Registration Form REGISTER.AUS - Australian Registration Form XFER-S .BAT - Batchfile used for file transfers to user XFER-R .BAT - Batchfile used for file transfer from user PAGE .ICE - Page Tune FILE_ID .DIZ - General Program Description SAMPLE1 .ANS - Sample Horizontal ANSI screen (rename to Template.1 to use it). See Template.X in the section of these docs on 'Files Used & Created by IceChat' for more info. SAMPLE2 .ANS - Sample Vertical ANSI screen (rename to template.2 to use it). See Template.X in the section of these docs on 'Files Used & Created by IceChat for more info. SAMPLE3 .ANS - Sample Macro Header ANSI screen (must be renamed to MacroHdr.Ans to be used). See MacroHdr.Ans in the 'Files Used & Created by IceChat' section for more info. If one or any combination of these files are missing, or files have been ADDED, then you are using a possibly modified or altered copy of ICECHAT. It would be advised that you delete this copy, and get a clean copy of ICECHAT from one of the BBS's listed at the end of the documentation. Newest Version of IceChat can be F'REQed from Ice Technologies BBS under the magic name 'ICECHAT' (without the quotes) Files IceChat will create are : ICECHAT.CFG - The configuration file MACRO.CFG - Encrypted Macro File NOPAGE.CTL - List of TWIT users who may not page ICECHAT.LOG - Usage Log (Can be configured to be appended to your BBS system log) ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Copyright Notices & Program Disclaimer ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ The door IceChat, along with all its support files and documents, are Copyright (C) 1993-97 Jeremy Landvoigt. Distributing a version AFTER it has been registered is prohibited; distribution of the original, unaltered evaluation version is permitted, indeed encouraged, as long as all support-files and documentation accompany the program are included WITHOUT ALTERATION OF ANY SORT. None of the files included in the IceChat archive may be modified in any way or distributed in any package without the expressed permission of Ice Technologies. Any type of cracking of either evaluation or registered versions of IceChat including (but not limited to) hex-editing, reverse engineering, decompiling are strictly prohibited. The author can be quickly reached for information through the RA_UTIL international FidoNET Conference, or at InterNET e-mail address: jlandvoigt@interhop.net Or, If you wish to trust comments/complaints/suggestions to the Post Office, you can send them to: P.O. Box 93044 1111 Davis Drive Newmarket, Ontario Canada L3Y 8K3 The following programs mentioned in this documentation are Copyright of their respective authors. They are listed in no particular order: IceChat - Copyright Jeremy Landvoigt RemoteAccess - Copyright Wantree Development & Andrew Milner ProBoard - Copyright Philippe Leybaert QuickBBS - Copyright Benjamin Schollnick X00 - Copyright Raymond L. Gwinn BNU - Copyright David Nugent and Unique Computing Pty Limited FKFossil - Copyright Tim Strike and Forbidden Knights Systems Turbo Pascal - Copyright Borland International THE USUAL LEGALITIES I (Jeremy Landvoigt) make no warranty of any kind, expressed or implied, including without limitation any warranties of merchantability and/or fitness for a particular purpose. I shall not be held liable for any damages, whether direct, indirect, special or consequential arising from the failure of this program to operate in the manner desired by the user. I shall not be held liable for any damage to data or property which may be caused directly or indirectly by the use of this program. In no event will I be held liable for any damages, including (but not limited to) any lost profits, lost savings, or other incidental or consequential damages arising out of the use -- or the inability to use -- this program, or for any claim by any other party. The only thing this package is guaranteed to do is take up space on your hard drive. Making use of this software is acknowledgement that you have read, understand, and fully agree to the license and disclaimer agreement. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Credits ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ There are a few people who helped with the development of IceChat that although they weren't involved in the creation or writing of the program, their suggestions, Bug reports, and lengthy ßeta testing have been an enormous asset. I would like to thank in no particular order : Kevin Mckillop, Eric Staufer, Glen Oliver, Branislav Slantchev and for all of their help. Couldn't have done it without them! Special thanks to Kevin McKillop for creating and maintaining our homepage on the internet! (http://www.ionsys.com/~mckkev/icesoft.html) Also, portions of the Fossil Routines used in IceChat v4.40 are Copyright 1993-94 By Tim Strike and Forbidden Knights Systems. ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Other Ice Technologies Utilities ▓▓▓▒▒▒░░░│ └────────────────────────────────────────────────────────────────────────────┘ Here is a list of all the Ice Technologies utilities that were available at the time of release of this archive. If you enjoy using this Ice utility, you may want to check some of these out! :) · IceChat - IceChat is a split screen chat utility for RemoteAccess/ProBoard BBS packages. It can be used with many other BBS types as long as they support Dorinfo1.Def/Door.Sys type Doors. · IceEdit - IceEdit is a fullscreen ANSi message editor that was originally designed for use with RemoteAccess. Although it has been tested with RA v2.xx, PB v2.xx, and TeleGard v2.99 it should be compatible with any other BBS that uses the QuickBBS style dropfiles that contain the message writing information. These files are MSGTMP & MSGINF. You should check your BBS documentation to see if your software supports this system. IceEdit also calls on the Dorinfo1.Def file to read in necessary information about the user profile. · IceMGR - The very newest Ice Technologies utility. Unlike the other programs, this program is run offline as a bulletins generator, message poster, nightly maintenance utility. · IceNote - IceNote is the third Ice Technologies door to become available. It is a message to all users type door with many neat features. It has been tested with both RemoteAccess v2.xx, and the latest release of Renegade, and should work with any other Dorinfo1.Def compatible BBS Packages. · IceBank - IceBank is the fourth utility to become available. It is a fully functional, fully configurable timebank system for RA v2.xx/PB v2.xx. It has many cool features, including InterBBS transactions. · IceUser - This is the fifth utility to become available. It is a fully functional online user editor for RemoteAccess v2.xx. Very secure. · IceCBV - The very newest Ice Technologies door available! Took awhile to finally get it released, but you won't be disappointed. Full featured callback verification system for RemoteAccess and ProBoard. Many unique features! Look forward to even more features in the next version! ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Program Support - Internet Email Addresses ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ Following is a list of support/distribution/registration sites which currently have Internet email addresses. Please contact any of these sites via email for assistance with any Ice Technologies product. Jeremy Landvoigt John Piper jlandvoigt@interhop.net japp@mpx.com.au Canadian Registrations Australian Registrations Eric Staufer Kevin Mckillop estaufer@irwin.vetrol.com mckillop@rogerswave.ca American Support Site Website Manager Dan Jones dan.jones@ivsoft.com American/Worldwide Registrations ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Program Support - BBS Locations ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ All Ice Technologies utilities are available from our homepage at: http://www.ionsys.com/~mckkev/icesoft.html IceChat can be File Requested from any of the following BBS's under the magic name of ICECHAT. Legend ────── S - Support Site B - Beta Site R - Registration Site D - Distrib. Site Ice Technologies SysOp Central Concession Stand Ontario, Canada Chicago, USA Florida, USA (905) 895-7775 (773) 583-0489 (561) 569-6568 FidoNET 1:2424/912 FidoNET 1:115/583 FidoNET 1:374/6568 Max. Baud: 28800 Max. Baud: 33600 Max. Baud: 33600 Flags: S B R D Flags: S R D Flags: S B D Battle Zone Systems StoneKeep Lost Horizons BBS Ontario, Canada Florida, USA Texas, USA (905) 715-7963 (407) 380-9529 (915) 757-1299 FidoNET 1:2424/900 FidoNET 1:363/321 FidoNET 1:381/92 Max. Baud 28800 Max. Baud: 33600 Max. Baud: 28800 Flags: B D Flags: D Flags: D RaLin Enterprises Lateline BBS Slash BBS California, USA Penshurst, Australia Venray, The Netherlands (510) 226-7731 +61-2-9579-6564 +31-478-550103 FidoNET 1:215/710 FidoNET 3:712/841 Fidonet 2:512/5 Max. Baud: 14400 Max. Baud: 33600 Max. Baud 33600 Flags: D Flags: S R D Flags: S D Silicon Creations E.L.F. BBS Texas, USA Ontario, Canada (915) 949-4798 (416) 269-8733 FidoNET 1:383/47 FidoNET 1:250/1001 Max. Baud: 28800 Max. Baud: 28800 Flags: S B D Flags: S B D ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ End Of IceChat Documentation ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘