Beijing Paradise BBS Backup

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

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

Wrap

Text File | 1997-03-27 | 66.0 KB | 1,397 lines

┌───┐┌─────┐┌─────┐ ┌─────┐┌───────┐┌───┐┌───────┐ │░▒▓││░▒▓┌─┘│░▒▓┌─┘ │░▒▓┌─┘│░▒▓┌┐░▒││░▒▓│└─┐░▒▓┌─┘ │▒▓█││▒▓█│ │▒▓█└┐ │▒▓█└┐ │▒▓█││▒▓││▒▓█│ │▒▓█│ │▓██││▓██│ │▓██┌┘ │▓██┌┘ │▓██││▓█││▓██│ │▓██│ │███││███└─┐│███└─┐ │███└─┐│███└┘██││███│ │███│ └───┘└─────┘└─────┘ └─────┘└───────┘└───┘ └───┘ Deluxe Fullscreen ANSI Message Editing Utility For RemoteAccess v2.xx, Telegard v3.0x, QuickBBS 2.8x, & Compatibles ───────────────────────────────────────────────────────────────────────────── IceEdit v2.35 - Copyright Jeremy Landvoigt, 1994-97 - IceEdit v2.35 ───────────────────────────────────────────────────────────────────────────── ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Important Note: Upgrading from v2.30 to v2.35 ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ If you are upgrading from v2.30 to v2.35, all you need to do is run EDITCFG before attempting to run the main executable. As of v1.60, the external version converter utility has been internally coded into the configuration program. Please note that the converter can not upgrade between more than one "generation" of the software, in other words if you skip a version you'll need to manually re-configure the software. ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Some Unique Features Of IceEdit v2.35 ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ ■ IceEdit has a built in Macro replacement feature that will replace keywords with other words. Eg "RA" -> "RemoteAccess" ■ IceEdit has a built message censoring feature to weed out inappropriate text. {+} ■ Character Color Configuration for individual letters such as Uppercase, lowercase, High Bit, numbers, and punctuation. ■ Tagline appending feature - IceEdit has THREE modes of tagline appending available! Mode 1 is single random tagline appending without user knowledge, Mode 2 is allow the user to select from a random pick list, and Mode 3 allows the user to completely scan the entire tagline database for the tagline they want! {+} ■ Easy to use control keys. ■ Color Code insert strings ■ SysOp defined function key macros ■ Quoted text re-formatting And much MORE! ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Copyright Notices & Program Disclaimer ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ The utility IceEdit, along with all its support files and documents, are Copyright (C) 1994-97 Jeremy Landvoigt. Distributing a version AFTER it has been registered is prohibited; distribution & execution of the original, unaltered version is permitted, indeed encouraged, as long as all support-files and documentation that accompany the program are included WITHOUT ALTERATION OF ANY SORT. None of the files included in the IceEdit archive may be modified in any way or distributed in any package without the express, written permission of Ice Technologies. Any type of cracking of either evaluation or registered versions of IceEdit including (but not limited to) hex-editing, reverse engineering, decompiling are strictly prohibited. The author can be quickly reached for information through the ICEUTILS or the RA_UTIL international FidoNET Conferences, 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: Jeremy Landvoigt 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: IceEdit - Copyright Jeremy Landvoigt FKFossil - Copyright Tim Strike and Forbidden Knights Systems RemoteAccess - Copyright Wantree Development & Andrew Milner Telegard - Copyright Tim Strike QuickBBS - Copyright Matrix Technologies & Benjamin Schollnick X00 - Copyright Raymond L. Gwinn BNU - Copyright David Nugent and Unique Computing Pty Limited 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 that this package is guaranteed to do is to 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 IceEdit 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 : Ian Thomsen Branislav Slantchev Glen Oliver Eric Staufer Kevin McKillop for all of their help. Couldn't have done it without them! Special thanks to James Goldbloom for writing the QBBS setup section, Andreas Magnusson for translating the language file to Swedish, and 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 IceEdit v2.35 are Copyright 1993-94 By Tim Strike and Forbidden Knights Systems. ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Registration ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ The development of IceEdit v2.35 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 expectations of a fullscreen editor,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 future versions with many more features. If you register, the Message Censoring & tagline features will become available. All "Unregistered" messages and almost inaudible beeps within the program will also 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 extract the ICEREG archive (which is the official Ice Tech registration kit) and 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 Europe ------ Register.Ger - Registration Form for Germany Register.Uk - Registration Form for the United Kingdom Far East -------- Register.Aus - Registration Form for Australasia 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 2 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 charge 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, understood and agree to these conditions. ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Archive Contents ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ IceEdit v2.35 has been compressed using RAR, and should be a self-extracting (SFX) archive. The archive should be approximately 190k 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 IceEdit archive should contain the following files : ICEEDIT .EXE - The main program EDITCFG .EXE - Use to configure the program LANGUAGE.EXE - Archive containing various language files ICEREG10.EXE - Registration kit (includes regforms and regdocs) CENSOR .CFG - Sample censor keyword file ICEEDIT .DOC - Program documentation ICEEDIT .LNG - IceEdit language file (English) WHATSNEW.235 - Changes in IceEdit since previous version HISTORY .DOC - Changes in IceEdit since it's creation FILE_ID .DIZ - General program description 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 IceEdit. It would be advised that you delete this copy, and get a clean copy of IceEdit from one of the BBS's listed at the end of the documentation. Newest Version of IceEdit can be F'REQed from Ice Technologies BBS under the magic name 'ICEEDIT' (Without the quotes). There is a second archive which you can probably find wherever you obtained this copy of IceEdit. The file is ICEDICT.EXE, which is an archive containing IceEdit's dictionary files. These files must be installed into the program directory for IceEdit to make use of the spell checker. Files IceEdit will create are : ICEEDIT.CFG - The configuration file. ICEEDIT.x - The temporary file which buffer text is stored in. [x] represents current node number. This file also indicates that the current node is in use. MACRO.CFG - The file containing replacement macros. MSGTMP. - Textfile containing message text which is read in by the BBS package. Files IceEdit can/will read are: CONFIG.RA - Read when IceEdit is first installed. It will CONFIG.TG attempt to determine if you are running RA/TG/QBBS QUICKCFG.DAT by use of Environment variable, and if it can find the configuration, it will read in some information from it. MESSAGES.RA - IceEdit will attempt to read this file if it can MSGCFG.DAT It uses this file to determine whether or not a message area is an echomail/netmail base. If it is, the Color Code feature will be temporarily disabled. DORINFO1.DEF - Drop file containing user information. MSGHDR.ANS - Definable ANSI screen which, if found, will replace the hardcoded screen header on the main editing screen. MSGINF. - File created by the BBS package containing message MSG.INF information such as Source User, Target User, message subject, & Message area. MSGTMP. - File created by the BBS package containing Quoted text. ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Program Information ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ IceEdit is a fullscreen ANSi message editor that was originally designed for use with RemoteAccess. Although it has been tested with TG 3.00, RA v2.xx, & QBBS v2.80 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. IceEdit has a special feature specifically for QBBS/RA/TG, which is Echobase checking. Do not enable this feature if you are not using RA, QBBS, or TG. Why was IceEdit created? .. Well, after I wrote my first major BBS utility, known as IceChat, I was really surprised by the response to my chat program and the number of registrations that came in for it. When I first created IceChat, I never expected it to have the impact that it obviously had. This encouraged me to start writing other BBS (specifically RemoteAccess) utilities. A number suggestions came in for utilities such as a User Editor, a TimeBank (both of which came into existance after IceEdit), but the most challenging one was to write a Fullscreen message editor, which I thought would be a really great idea. Not only for the challenge, but because right now I feel that there are very few message editors currently available. Of the ones that do exist, one or two of them tend to dominate the market, and they STILL didn't offer all the features that I would like to have in a fullscreen editor. Nevermind ridiculous registration fees. So, thus became the beginnings of IceEdit. ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ IceEdit's System Requirements ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ IceEdit requires the following to correctly operate on your system: ■ An IBM XT/AT/386/486/Pentium/P6+ or compatible ■ A modem, 300-115200 BPS ■ A FOSSIL communications driver (BNU/X00 or 100% compatible) ■ DOS 3.0+, OS/2 2.0+/Warp 3.0+, Win 3.0+, DV 2.0+, or Win '95 ■ DORINFO1.DEF (produced by your BBS program) (EXITINFO.BBS optional) ■ A terminal supporting ANSI emulation (user only) ■ 500k on your hard disk (plus space for dictionary & taglines) ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Program Configuration - Using EditCfg ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ Setting up IceEdit is quite easy. This section of the documentation will attempt to take you step by step on how to use the configuration utility EditCfg.Exe to set up IceEdit. Most of the options are self explanatory. You can use the local testmode feature at any time to test out how your current settings will affect IceEdit.Exe without having to save your settings or exit the configuration program. BEFORE YOU BEGIN: If you are using RemoteAccess, Telegard or QuickBBS it is recommended that you ensure that you've set your BBS package environment variable so that you can take advantage of the added features for these three BBS packages. FILE ------ ■ Save & Exit - This will save your current configuration to the IceEdit.Cfg file and will exit the program. ■ Save Without Exit - This will save your current configuration to the IceEdit.Cfg file and will allow you to continue modifying your setup. ■ Exit Without Save - This will abort the save procedure (just in case you somehow really messed up!) and will exit the program. ■ System Paths - ■ Censor file - textfile containing censor keywords, one word per line. If censoring is enabled, IceEdit will read in the file and scan the user's message for any matches of words within this file. If it finds any matches, it will strike out that particular word from the message. For example, if a censor word was "IDIOT", and the user had a sentence such as: "You are such an idiot!" After the scan was complete the word "IDIOT" would be wiped out and the result would be: "You are such an *****!". A sample CENSOR.CFG file is included. The format is very simple; use one word per line. IceEdit is not case sensitive to the particular censoring word that is being compared. Message censoring only takes place AFTER the user opts to save their message. This is a registered feature. {+} ■ Msg Header - a definable header which will be imported into the main text body upon program execution. ■ Macros - path and filename to macro database. ■ Chat Util - path and filename to external chat utility. This can be executed from within IceEdit using the ALT-C key. ■ Dictionary - path and filename to words added to dictionary by *sysop* -- this file must NOT be the same name as the dictionary files -- ■ Program Info - This will give you a little bit of information on the current version of IceEdit that you happen to be using. ■ Local Testmode - You can use this at anytime during configuration to view how your current configuration will affect IceEdit if you should choose to save. You can execute a local testmode from the dos prompt by running IceEdit like this: ICEEDIT.EXE /L MANAGER --------- ■ Tagline Setup - This is a submenu containing all most of the tagline setup. It can be accessed by unregistered users, however tagline functions are limited. TAGLINE SUBMENU ----------------- ■ Tagline Editor - Use this to edit all your compiled tagline files. You can edit, insert, and import new taglines into your compiled files. ■ Compile Taglines - This file contains taglines that can be appended to the ending of the users message if they opt to save their text. This is a textfile that you can create, although a sample is included called TagLines.Cfg. This file is encrypted, and MUST be compiled from a textfile containing taglines. Use EditCfg to compile. At this time there is not any considerable limitation on the number of taglines that the file may contain. However, the more that there are, the longer it will take EditCfg to read in the textfile and convert it to a structured datafile. IMPORTANT: The file extension of the compiled taglines file MUST be a number. If you are using RemoteAccess with different message GROUPS, it is possible to configure different tagline files for different groups. If you are aren't using groups, or only want one tagline file, it must be named in this format: ICETAG.0 It must have the .0 extension to indicate one file. If you create a file called ICETAG.2, if the message is being written in a conference which falls in GROUP 2, then this tagline file will be accessed. If IceNote can't find a corresponding tagline file, it will fall back on ICETAG.0, so it would be a good idea to have a 'default' tagline file. ■ Configure Toggles - This is another small submenu to toggle tagline configuration. It consists of three options: 1) Use Taglines 2) List Taglines 3) Scroll Taglines - If taglines aren't enabled, there will be no taglines (obviously :) - If only option (1) is enabled, a random tagline will be chosen for the user. - If options (1) and (2) are enabled, the user will be able to pick from a random list of taglines. - If all options are enabled, the user can browse the entire tagline database. ■ Compile Dictionary - Use this to compile a textfile with a list of words to a encrypted private dictionary file. This feature is used to add words to the dictionary database that you wouldn't usually find in an average English dictionary, Such as "RemoteAccess", "FrontDoor" etc.. or any other slang terms that might be commonly used. Any words that IceEdit finds in this file will not be treated as mis-spelled. Note, the textfile that contains the words MUST not be the same name as what the compiled file will be called. Eg, if you have 'ICEEDIT.PVT' as your Private dictionary name, make sure you do not name the textfile with this name before compilation. ■ Override Manager - Use this to define overrides for individual message areas. You can toggle Pipe Codes, Taglines, Censoring, and ANSi individually for every message base that your BBS has. This is for RA/QBBS/TG only. The settings defined will override the default configuration settings. ■ Display Manager - This is a submenu containing toggles to turn certain information fields ON or OFF on the main editing screen, as well as configure screen locations. Toggles --------- ■ View Macros YES/NO - Are users permitted to view the list of available macros from within IceEdit by using the CTRL-V key? ■ Create Macros YES/NO - Are users permitted to add to the list of available macros from within IceEdit by using the CTRL-V key? NOTE: View Macros MUST be enabled for this feature to work. ■ Censor Tagline YES/NO - If the user uses inappropriate text in their message and IceEdit is forced to censor the text, should a tagline be appended to the message to inform future message readers of that fact? Eg. "*** This message has been censored by IceEdit v2.35" ■ Imbedded Colors YES/NO - Should imbedded color codes be permitted? If YES, when the message is saved, all color strings will be replaced by ANSi escape sequences, thus putting colors into the message. Refer below in "Editing Your Message In IceEdit" for more information on Color Strings. ■ Convert Colors YES/NO - Should IceEdit convert colour pipecodes to ANSI? ■ Use Overrides YES/NO - Should IceEdit make use of the message override definitions located in the MANAGER section? ■ Confirm Abort YES/NO - Should IceEdit display a message to the user if they choose to abort a message either by '/A', 'CTRL-A' or by use of the help prompt which will ask them if they really want to abort their message? Enabling this feature can help prevent accidental message erasure. ■ Use Quote Color YES/NO - Should IceEdit use the quote color selected in EditCfg to make quoted text a specific color. If NO, all quoted text will have regular text coloration. ■ Filter ANSi YES/NO - Should IceEdit disrupt any ANSi that is read into IceEdit whether it be quoted text or manually imported text by the SysOP? If NO, all ANSi codes will be treated normally. ■ Use Soft C/Rs YES/NO - Should IceEdit use soft carriage returns in messages, or should all lines be followed by a hard return? ■ KBT hangup YES/NO - Should IceEdit terminate the connection when the keyboard timeout has elapsed? ■ Speller Prompt YES/NO - Should IceEdit prompt the user for spell checking when they save their message? ■ CTRL-Q Quote Key YES/NO - Should IceEdit open the quote window using CTRL-Q? If not, it will use CTRL-W. On some systems using OS/2, the operating system filters out the CTRL-Q before IceEdit can intercept it thereby making it impossible to quote from the main editing screen. ■ Suspend Time YES/NO - Should IceEdit suspend user time while they are editing their message? ■ Imbedded Files YES/NO - Should IceEdit process imbedded file names. If YES, IceEdit will read in the external file that is specified and add it to the message text. Eg: If the user put the following string on a line by itself .. %[MAIN.ANS]% If IceEdit can locate the file MAIN.ANS, it will import it into the message text. Any files that you want to have imported MUST be surrounded by the "%[" & "]%" brackets and should be placed on a single line without any other text. You should specify the full path and filename of the file to be imported. Please note, this function will PROPERLY import a file into the message text, but editing before saving is not possible, as all Imbedded files are processed when the user chooses to save. ■ Spell Checker YES/NO - Should users be permitted to make use of IceEdit's built in spell checking routines? If YES, users can access the spell checker from the status bar. Please note, the spell checker does take a little time, as it must cross reference every word with the dictionary. Also, words smaller than 3 letters will not be checked. ■ Quote Ratio YES/NO - Should IceEdit check to see if users have exceeded the permitted percentage of quoted text? ■ Enforced Quote Ratio YES/NO - If the Quote Ratio is active, should IceEdit enforce it? If YES, IceEdit will display a message telling the user the current ratio, and that they must cut down. If NO, IceEdit will mention the ratios and display them, and ask the user if they wish to re-edit the message before saving. ■ Upcase Ratio YES/NO - Should IceEdit check to see if users have exceeded the permitted percentage of Upcase text? ■ Enforce Upcase Ratio YES/NO - If the Upcase Ratio is active, should IceEdit enforce it? If YES, IceEdit will display a message telling the user the current ratio, and that they must cut down. If NO, IceEdit will mention the ratio and display it, and ask the user if they wish to re-edit the message before saving. ■ Allow Linedraw YES/NO - Should users be allowed to enable linedraw mode? ■ Message Censor YES/NO - Should IceEdit censor the message when the user opts to save? This is a registered only feature. {+} ■ Quote Format YES/NO - Should IceEdit reformat quoted text? Some editors (such as DOS EDIT) when used in conjunction with BlueWave cause messages to be afflicted with what is commonly known as the "Chainsaw Effect", caused by Hard Returns. IceEdit will now reformat quoted text to remove this annoying problem. ■ QBBS compatible YES/NO - Is the BBS package you're running QBBS compatible? (ie. QBBS, RA, TG as a few examples). Does your BBS package support kludgelines? If you can answer YES to either of these questions, turn compatibility ON! ■ Message Header YES/NO - Should IceEdit import the sysop defined message header upon execution? ■ Kludge filter YES/NO - If IceEdit finds *defined* kludgelines in the quoted text, should it filter them? ■ Errorlevels YES/NO - Should IceEdit exit using the standard QBBS compatible errorlevels? ■ Time Warning YES/NO - Should IceEdit warn the user when less than 5 minutes remain? Colors -------- ■ This section on color configuration is self explanatory. Simply select the type of character which you wish to color configure. Another box will appear that will show you the list of available colors. Type in the number of the color you want to use. ■ DEFAULT SETTINGS will restore all the colors to their original installation settings. Macro Setup ------------- ■ Macro Editor - This will allow you to define replacement macros that will be used within IceEdit. For example, if you defined a macro such as "RA" -> "RemoteAccess", when the user types "RA" while editing their message, IceEdit will replace it with "RemoteAccess". User Keywords are not case sensitive, so if the user was to type "RA" or "Ra" Or "rA" or "ra", each of these would still be replaced with "RemoteAccess". This function can be useful for correcting commonly misspelled words, replacing shortforms, or "weeding out" inappropriate text (refer to message censoring function aswell). The macrofile used in IceEdit is completely compatible with IceChat's macrofile, so you can interchange the macro files between both pieces of software. ■ MacroFile Sorter - This will allow you to sort the macrofile in alphabetical order by User Keyword. It will also strip the spaces between macros to eliminate gaps. ■ Macro Triggers - Which characters (when typed after a macro) should trigger the macro conversion? These characters usually consist of punctuation. Function Keys --------------- ■ This section is fairly simple. You can define different Function keys (F1,F2..etc) to insert text into the message body while you are editing your message. This is useful for greetings, goodbyes, and signatures that are commonly used. For example, I might configure my Fn Keys like this : F1 - Take Care, F2 - Later.. F3 - Jeremy F4 - SysOP, Ice Technologies F5 - .. Author Of IceEdit. etc.. etc.. If I hit one of my Fn Keys while in IceEdit, the appropriate text would be inserted at the current cursor position. Function keys can also be used to IMPORT files, such as multiline sigs. This is done by putting the prefix '@' before the path to the file name. ie: F1 - @SIG.TXT If the file can't be found, it will simply do nothing. Make sure you specify the full path for the file, or else IceEdit will assume the file should be in the current directory. If you wish to run an external utility from within IceEdit using the function keys, simply use the '#' prefix in from the the commandline, ie: F1 - #D:\BBS\ICECHAT\ICECHAT.EXE -D:D:\BBS\RA Assuming that the commandline is correct, the program will be executed. Other ------- ■ Strike Symbol [*] - What character should IceEdit use when striking out text that can be found in the Censor.Cfg file. Asterisk ("*") is the default. ■ SysOp Security - What is the SysOp security level to activate the dictionary 'word-adding' feature. ■ Quote Ratio % - Up to what percentage is Quoted text allowed in the message text. ■ Upcase Ratio % - Up to what percentage is upcase text allowed in the message text. ■ # Of Taglines - What number of taglines should a user be allowed to pick from when they have chosen to save their message? [1..10] (User makes use of light bar to select tagline) ■ Dropfile Type - Which type of dropfile should IceEdit use? (DORINFO1.DEF, DORINFOX.DEF, or DOOR.SYS) ■ Kludge Codes - IceEdit will filter kludges prefixed the the characters configured in this section. ■ Menu Brackets - Configure left and right menu brackets surrounding lightbar options, and some information fields. ■ Scroll Length - Configure total scroll length of main editing screen when the end of page is reached. ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Setting Up IceEdit.Exe With RemoteAccess ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ Please read the section of this document entitled 'Program Information - Using EditCfg' BEFORE attempting to install IceEdit into RA. Failure to setup IceEdit correctly before installing it into your bbs program will probably result in IceEdit failing to run or not running as expected. In order to run IceEdit.Exe with a user ONLINE, you must have a fossil driver active. A fossil driver such as BNU should work fine with IceEdit. 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 locally. **Note** : Do _NOT_ write protect _ANY_ Of the IceEdit files, if you do, IceEdit will ignore them, and therefore not run properly. We will now run through EVERYTHING you need to do in order to get IceEdit to run in your RemoteAccess setup. 1. Extract all the files in the distribution archive to a directory of your choice. C:\RA\ is recommended and is assumed to be the directory you are using from now on. 2. Run EditCfg.Exe and configure all of IceEdit's options as explained earlier in this document. You MUST configure IceEdit for it to work correctly! Refer to the section of this document for setting up IceEdit. 3. IceEdit needs to be setup in RACONFIG.EXE so that when the user attempts to write a message it calls up IceEdit and NOT the internal RemoteAccess line-by-line editor. Change to your RemoteAccess directory and run RACONFIG.EXE. Go to OPTIONS>MESSAGES>EXTERNAL EDITOR. Place the command- line to run IceEdit.Exe in this space. Eg. C:\RA\ICEEDIT.EXE *M If you wish, you can specify the path to the dropfiles read in by IceEdit (Dorinfo1.Def, MsgInf, and MsgTmp if it exists) by adding the following parameter to your commandline like this: ICEEDIT.EXE /D:[PATH TO DROPFILES] Eg: C:\RA\ICEEDIT.EXE /D:C:\RA Otherwise IceEdit will assume the dropfiles are located in the current directory (usually your BBS directory) If you are PLANNING TO RUN ICEEDIT FROM YOUR NEWUSER.Q-A, then you should use the following commandline in your RaConfig setup. C:\RA\ICEEDIT.EXE /B:*B /P:*P /T:*T *M *B - Passes the baudrate out to the commandline. *P - Passes the modem port out to the commandline. *N - Passes the nodenumber as read from the %TASK% environment variable out to the commandline. *M - Activate the MemorySwap feature. *T - Passes time limit out to the commandline. 4. When you run IceEdit, be sure that the IceEdit.Cfg file has been created. If it has not, then you MUST run EditCfg.Exe. If you don't, and attempt to run IceEdit.Exe directly, IceEdit will display an error message that IceEdit.Cfg doesn't exist. ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Setting Up IceEdit.Exe With QuickBBS ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ QuickBBS Version 2.80 is supported FULLY in this version of IceEdit, which includes automatic integration of your existing BBS message areas, as well as proper display of all message headers. IceEdit and QuickBBS work together offering your users a powerful option of a feature-laden full screen editor package compared to others which barely supported QuickBBS specific requirements in years past. The following documentation will help you, a QuickBBS SysOp, to successfully integrate IceEdit into your system, seamlessly... INSTALLING ICEEDIT VIA QCONFIG (FULL SCREEN EDITOR SETTINGS): ------------------------------------------------------------- Go into QCONFIG, and pull down these menus: MESSAGES -> EXTERNAL EDITOR Install accordingly, adjusting paths as necessary (example below): +------------------------External MessageEditor Setup----------------------+ | | | Message Reply Quoting String: @> Swap to Disk/EMS: Yes | | | | DOS Command String: | | c:\qbbs\editor\iceedit.exe /N:*N | +--------------------------------------------------------------------------+ (The above example assumes "c:\qbbs\editor\" is the path containing the IceEdit distribution files, please adjust accordingly for your platform.) Note for calling IceEdit as a DOOR from a menu: If you load IceEdit as a door, via a TYPE 7 command in a menu, issue the following command on the "optional data" line (example): *C /C *M d:\qbbs\editor\iceedit.exe /N:*N (Make sure the swap, *M, is there, and pass the node# to IceEdit as shown) CONFIGURATION INFORMATION: EDITCFG.EXE ====================================== New Users to IceEdit who run QuickBBS, please note: *Before* running EDITCFG.EXE, make sure your "QUICK" environment variable is set properly in your batch file(s) used to load the BBS, or autoexec.bat. This environment variable should already be enabled, according to the QuickBBS documentation. This variable, such as "SET QUICK=C:\QBBS", points to your main BBS path, where MSGCFG.DAT lives along with other BBS data files. EDITCFG.EXE looks for this environment variable the first time it is run, and if found it automatically configures sensible defaults, and enables the following integrated features: * IceEdit reads in your message areas directly, automatically! * IceEdit creates certain toggles and defaults which work well with QuickBBS! So make sure the "QUICK" environment variable is set, and active, when you run EDITCFG.EXE for the first time if it's not already. IMPORTANT CONFIGURATION CONCERNS WITHIN EDITCFG.EXE --------------------------------------------------- Did you know all your QuickBBS defined message areas are loaded by EDITCFG.EXE, and set to sensible defaults, automatically? Also, various sensible QuickBBS toggles and features are set: * By reading in your message areas, via EDITCFG.EXE, the following defaults are given to the message areas on your BBS, automatically (and can be easily overridden via "Area Manager" settings): * Private areas will have censorship options DISABLED * Networked ECHO areas will have PIPECODES and ANSI disabled * Kludge code of CONTROL-A (ASCII 1) is used * Proper errorlevels are issued for aborted messages under QuickBBS * SysOp security level and associated options should be set to 32000 or whatever YOUR access level is on your system if you need to overide. * DORINFO1.DEF, DOOR.SYS are both supported and either can be enabled under version 2.80 of QuickBBS. Version 2.76a users, opt for DORINFO1.DEF. * Since QuickBBS does not utilize "message number" fields in version 2.80, you can easily toggle this setting via "Display Manager" settings menu as well as the other header fields (both location and availability) if desired, but are set to work with QuickBBS's MSGTMP and MSG.INF files, automatically. * Under "Toggle 2", make sure "QBBS Compatible" is set to YES, which should be set as the default if the "QUICK" environment variable is set properly and active prior to the first time EDITCFG.EXE is run. * REMOTE file import mode for SysOps, initiated by CONTROL-F when entering a message, is now supported as requested by QuickBBS users. * LOCAL file import, ALT-F2, is supported also! SUPPORT FOR QUICKBBS: PLEASE NOTE... ==================================== All wish lists, bug reports, and incompatibility flaws as well as questions regarding integration are welcomed. The author will on occasion visit the QuickBBS support echo (zone 1, backbone) so feel free to post such requests and observations. Direct support requires assistance from concerned and helpful users. The author is dedicated to continued support for QuickBBS, whenever possible. Try the automatic setup, be sure to edit the message areas, and check out the toggles. And, of course, enjoy continued support and seamless integration of IceEdit and QuickBBS! ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Setting Up IceEdit.Exe With Telegard ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ Please read the section of this document entitled 'Program Information - Using EditCfg' BEFORE attempting to install IceEdit into TG. Failure to setup IceEdit correctly before installing it into your bbs program will probably result in IceEdit failing to run or not running as expected. In order to run IceEdit.Exe with a user ONLINE, you must have a fossil driver active. A fossil driver such as BNU or X00 should work fine with IceEdit. 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 locally. **Note** : Do _NOT_ write protect _ANY_ Of the IceEdit files, if you do, IceEdit will ignore them, and therefore not run properly. We will now run through EVERYTHING you need to do in order to get IceEdit to run in your Telegard setup. 1. Extract all the files in the distribution archive to a directory of your choice. C:\TG\ICEEDIT\ is recommended and is assumed to be the directory you are using from now on. 2. Run EditCfg.Exe and configure all of IceEdit's options as explained earlier in this document. You MUST configure IceEdit for it to work correctly! Refer to the section of this document for setting up IceEdit. 3. IceEdit needs to be setup in Telegard so that when the user has a choice to either use the internal line-by-line editor or using IceEdit. You can accomplish this by doing the following. Go to your Telegard directory, run Telegard.EXE. Go to "S"ystem Config -> "X"ternal Utilities -> "C" Full Screen Editor. Place the command-line to run IceEdit.Exe in this space. Eg. C:\TG\ICEEDIT\ICEEDIT.EXE 4. When you run IceEdit, be sure that the IceEdit.Cfg file has been created. If it has not, then you MUST run EditCfg.Exe. If you don't, and attempt to run IceEdit.Exe directly, IceEdit will display an error message that ICEEDIT.CFG doesn't exist. 5. Be sure to set the ICEEDIT (IEDIT, not ICEEDIT) environment variable for this above setup, if it is left out, you will recieve errors. There are many different ways of setting up IceEdit to work with Telegard. This above way is one way it will work, if you know another way that works then by all means, use it. This is meant for the first time beginner who does not know how to setup IceEdit with Telegard. ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Errorlevels Generated By IceEdit ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ Once IceEdit's execution has ended, it will generate one of two errorlevels under normal termination. 0 - If IceEdit terminates with errorlevel 0, it means that the message has been successfully saved, and should be processed by the BBS package. 1 - If IceEdit terminates with errorlevel 1, it means that the message has either been aborted; or, that the user attempted to save a blank message. In either case, the BBS package should treat the message as aborted, and NOT process the message. 2 - If IceEdit terminates with errorlevel 2, it means that the user's keyboard has been inactive for more than the maximum time allowed. The program has terminated, and may have saved the message body to the MSGTMP file (or equivalent) if autosaving is enabled. ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Files That Are Used By IceEdit ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ IceEdit will call upon a number of files during runtime. They are listed below along with a brief description. CENSOR.CFG - This is a textfile containing inappropriate words that IceEdit will strike out of the message text when they are encountered. {+} CONFIG.RA - This file is read ONCE only by EDITCFG when you first CONFIG.TG install IceEdit. It will only be read if EditCfg can find QUICKCFG.DAT the BBS environment variable. It is compatible with the RA 2.xx/TG 3.00/QBBS v2.80 configuration files only. It will not read the Ra 1.1x format. COL_HELP.ANS - This is an ANSi file that will be displayed that will replace the hardcoded colour help menu. You can create this with an ANSi editor such as TheDraw. DORINFO1.DEF - This is the dropfile that most BBS packages can create that holds important user profile information. EDITHDR.TXT - This file will be imported into the beginning of the message if it is enabled, and IceEdit can locate it. It should be in the main IceEdit directory. ICEEDIT.CFG - This is IceEdit's configuration file. It is absolutely necessary in order for IceEdit.Exe to function. ICEEDIT.DIC - This is the IceEdit dictionary that is used in conjunction with the spellcheck feature. It comes in a separate package from the main IceEdit program, due to its size. ICEEDIT.IDX - This is the IceEdit dictionary index file that comes with the dictionary. It is also located in the secondary package. ICEEDIT.MDX - This file is scanned by IceEdit if you are using RA, and have run EDITCFG.EXE INDEX. This file is an index that contains the current toggle settings for all message areas. Toggle settings include taglines, pipecodes, ANSi filtering, and message censoring. KEY_HELP.ANS - This is an ANSi file that will be displayed that will replace the hardcoded Userkey help menu. You can create this with an ANSi editor such as TheDraw. MACRO.CFG - This is the file that contains the replacement macros that can be used in IceEdit. It is compatible with the MACRO.CFG file that IceChat uses. This file must be edited using EDITCFG.EXE. MSGHDR.ANS - An ANSI screen which IceEdit will use instead of the default screen header on the message editing screen. MSGINF. - This file contains message writing information. MSG.INF MSGTMP. - This file can contain both quoted message text as well as the regular message text that will be read back in by the BBS package. ICETAG.### - This is a tagline database that IceEdit will use to pick a random tagline to be appended to the end of messages. {+} ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ IceEdit.Exe Commandline Parameters ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ Note: ALL Commandline parameters are optional, and do NOT have to be used unless you are trying something new and different with IceEdit =). Generally these parameters are only used with you are trying to run IceEdit without a DORINFO1.DEF file (such as an offline mail reader) /B:[BAUD] - Use this parameter to specify the baudrate. Eg. ICEEDIT.EXE /B:14400 /BW - Use this parameter to tell IceEdit that you are using an offline mail reader, such as BlueWave. If this is the case, your commandline generally will not use any of the other commandline parameters. /D:[PATH] - Use this parameter to specify the path ONLY to the dropfiles that are to be used by IceEdit (DORINFO1.DEF, MSGTMP, MSGINF) Eg. ICEEDIT.EXE /D:C:\RA\LINE2 /F:[FILENAME] - Use this parameter to change the default textfile name that message text will be stored in. (Default = "MSGTMP") This is useful for offline mail readers. Eg. ICEEDIT.EXE /F:MSGTEMP.BBS /FORCE - Use this parameter to make sure that the user can't abort the message they are writing. This is useful for NewUser Questionnaires, where you want to make sure the user actually writes an introductory comment. /K:[TIMEOUT] - Use this parameter to specify in SECONDS how long IceEdit will wait in keyboard inactivity before disconnecting. /L - Use this parameter to run IceEdit in local test mode. Eg. ICEEDIT.EXE /L /N:[NODE] - Use this parameter to specify the NODE that IceEdit is being run on. A MUST FOR MULTINODE SYSTEMS!!!!!! (Default = 1) /P:[COMPORT] - Use this parameter to specify comport to be used by IceEdit. If you port is com3, then this is the commandline: ICEEDIT.EXE /P:3 /T:[MINUTES] - Use this parameter to specify the amount of time remaining for the user. Eg. ICEEDIT.EXE /T:30 Please note: If you change any values above that correspond with values in the DORINFO1.DEF File, then the DORINFO1.DEF value will be ignored. There is one more parameter that was added in during the v1.60 betas. I had planned on removing it, however I've left it in for those who really need to fine-tune IceEdit to their system. This parameter controls how much timeslicing will occur in multitasking environments. The LARGER the value, the LESS slicing that occurs. IceEdit defaults to 20, which was the optimum value on all test systems. Following is a symptom/solution chart: Symptom: | Solution: ------------------------------------------------------------------------- IceEdit, when run in a | IceEdit is giving up TOO many timeslices multitasking environment is | in your multitasking environment. You really slow, although the | should INCREASE the value, so that IceEdit other windows run fine. | gives LESS timeslices. ------------------------------------------------------------------------- IceEdit runs absolutely | IceEdit 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 IceEdit is | IceEdit gives up time slices more running, my other windows | frequently. slow to a crawl. | ------------------------------------------------------------------------- The parameter to use to adjust IceEdit'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! *** ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Editing your message in IceEdit ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ Function Keys --------------- To make message editing go easier, there are a number of different keys that may be used by both the SysOP and the user. A list follows: UP ARROW - Moves the cursor up one line DOWN ARROW - Moves the cursor down one line LEFT ARROW - Moves the cursor to the left one space RIGHT ARROW - Moves the cursor to the right one space INSERT - Toggle the text insert/typeover mode DELETE - Delete the character currently under the cursor CTRL-A or /A - Abort message text & exit program CTRL-B - Restore line of text from buffer CTRL-C - Center the current line of text on the screen CTRL-D - Move cursor to the right one space CTRL-E - Move cursor up one line CTRL-F - Remotely import a file (SYSOP ONLY) CTRL-J - Left justify the current line of text on the screen CTRL-K - Toggle LineDraw mode ON or OFF, or select line style CTRL-L - List / edit available macros CTRL-P - Place cursor at the end of the line CTRL-Q or /Q - Quote window (Available only with message replies) CTRL-R - Redraw the editing screen CTRL-S - Move cursor to the left one space CTRL-T - Delete text from the cursor to the end of the line CTRL-U - Delete text from the cursor to the end of the current word CTRL-V - Toggle INSERT/TYPEOVER Modes CTRL-W or /Q - Quote window (Available only with message replies) CTRL-X - Move cursor down one line CTRL-Y - Erase current line of text CTRL-Z or /S - Save message text & exit program There are also SysOP only keys that may be used: F1.. 10 - Activate previously defined SysOp text macros ALT- F2 - Import a textfile into the message ALT- F3 - Export message contents to a file ALT- C - Invoke external chat utility ALT- H - Terminate Connection ALT- J - Shell to DOS ALT- = - Add one minute to user's time ALT- - - Subtract one minute from user's time Imbedded Replacement Strings ------------------------------ All replacement macros, taglines and SysOp function keys can make use of the following built in control strings (NOTE ** Some are repeated to ensure compatibility with ICECHAT replacement strings) : @A = SysOp name (Read From IceEdit Configuration) @B = BBS name (Read From IceEdit Configuration) @C = Receiving users full name @D = Date @H = Message subject @F = Receiving users first name @R = Receiving users first name @S = SysOp name (Read From IceEdit Configuration) @T = Time of day @U = Sending user's first name @V = Program version number The control strings can be used in the following manner. For Example, if you were configuring one of your macros to tell the current time & Date, you could put: "MTD" -> "This message was written at @T on @D." And then when IceEdit is run, if the user chooses to type in the "MTD" macro, the strings would be replaced and the result would be: "This message was written at 2:41p on 02/19/95." All the control strings can be used in a similar manner in all the other macros & taglines, and Fn keys. Imbedded Colors ----------------- With IceEdit, it is possible to use color codes into your Message text. This is very easily done. Wherever you would like to have a color change in your message, use one of the following colour combinations: 0 - Black 8 - DarkGray 1 - Blue 9 - LightBlue 2 - Green A - LightGreen 3 - Cyan B - LightCyan 4 - Red C - LightRed 5 - Magenta D - LightMagenta 6 - Brown E - Yellow 7 - LightGray F - White Combine these colour codes to create a foreground & background colour. ie. |4E would yield yellow foreground on red background The first value represents the background colour, the second value represents the foreground colour. So, If you had a line such as: "|15This is a |09test." The first three words "This is a" would be in White, and the rest, "Test." would be in LightBlue once the message has been saved. Please be aware of two important points. Firstly, IceEdit will NOT CHANGE the color WHILE YOU ARE EDITING the message. Color strings will be converted when the message is saved. Second, these codes are replaced with ANSi escape sequences (the same codes that are used in your ANSi screens). Many networks do not authorize ANSi escape codes in their echos. If you are going to make use of this feature, it is recommended that users are informed on the point that they should not use embedded color strings in echomail areas. If you are using RemoteAccess, it is possible to make IceEdit determine whether or not the message area is a local base. If it is NOT, IceEdit can automatically temporarily disable Imbedded colors in the message that the user is writing. Imbedded Files ---------------- With IceEdit, it is possible to have external filenames that will be later imported into into your Message text. This is very easily done. Wherever you would like to have a file imported into your message, use the following method. For Example, say you have a textfile with some type of header in it that you want to import into your message. The filename of the header is BBSHDR.ASC for our example. In your message you would put the following on a blank line of text: %[BBSHDR.ASC]% When your message is saved, IceEdit will seek out the filename between the two special brackets ( %[ and ]% ). You can specify the path of the file aswell, if the file is not located in your current directory, for example: %[C:\BBS\TXTFILES\BBSHDR.ASC]% When the message is saved, IceEdit will find this file, and import it into the body of the message text, so your message might end up looking like this: ▐██▌░▄█████▄ ▄██████░ ███████░▄██████░▄█████▄ ██░ ██░ ██░ ██░░░░░ ██▄▄▄▄░ ▐█▌░░░██▄▄▄▄░ ██░░░░░ ██▄▄▄██░ ██░ ██░ ██▀▀▀▀░ ▐█▌░ ██▀▀▀▀░ ██░ ██▀▀▀██░ ▐██▌░▀█████▀ ▀██████░ ▐█▌░ ▀██████░▀█████▀ ██░░░██░ ██░ ██░░░ ██░██░ ██░ ██░██░░ ██░░░ ██░ █▌░ ▐▌░ ▐▌░ ▐▌░▐▌░ ▐▌░ ▐▌░▐▌░ ▐▌░ ▐▌░ ▐░ ▌░ ▐░ ▌░ ▐░ ▌░ ▐░ ▐░ Please be aware of an important point. IceEdit will NOT IMPORT the file(s) WHILE YOU ARE EDITING the message. File(s) will only be imported when the message is saved. LineDraw Mode --------------- IceEdit has a "linedraw" mode. When the user activates this mode, it is possible to draw High-Bit ASCII lines on the screen by using the Cursor Keys (Left, Right, Up, Down). There are 3 line styles available: 1) ╔═╗ 2) ╒═╕ 3) ┌─┐ And that's all there is to it.. Hope you guys enjoy this thing, and it is my hope that IceEdit becomes the default editor used with your system =-) ┌────────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ 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, QBBS, and Telegard v3.0 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 - IceCBV is the sixth utility to become 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 Kevin Mckillop Dan Jones mckillop@rogerswave.ca dan.jones@ivsoft.com Website Manager American Registrations ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ Program Support - BBS Locations ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘ All Ice Technologies utilities are available from our homepage at: http://www.ionsys.com/~mckkev/icesoft.html IceEdit can be File Requested from any of the following BBS's under the magic name of ICEEDIT. Legend ────── S - Support Site B - Beta Site R - Registration Site D - Distrib. Site Ice Technologies SysOp Central Lateline BBS Ontario, Canada Chicago, USA Penshurst, Australia (905) 895-7775 (773) 583-0489 +61-2-9579-6564 FidoNET 1:2424/912 FidoNET 1:115/583 FidoNET 3:712/841 Max. Baud: 28800 Max. Baud: 33600 Max. Baud: 33600 Flags: S B R D Flags: S R D Flags: S R D B Beachcomber's Mailbox The Coracle BBS Lost Horizons BBS Langenloh, Germany United Kingdom Texas, USA +49-9827-4766 +44-1559-384404 (915) 757-1299 FidoNET 2:2490/8016 FidoNET 2:25/10 FidoNET 1:381/92 Max. Baud 28800 Max. Baud 28800 Max. Baud: 28800 Flags: S R D B Flags: S R D Flags: D RaLin Enterprises Battle Zone Systems E.L.F. BBS California, USA Ontario, Canada Ontario, Canada (510) 226-7731 (905) 715-7963 (416) 269-8733 FidoNET 1:215/710 FidoNET 1:2424/900 FidoNET 1:250/1001 Max. Baud: 14400 Max. Baud 28800 Max. Baud: 28800 Flags: D Flags: B D Flags: S B D Silicon Creations Texas, USA (915) 949-4798 FidoNET 1:383/47 Max. Baud: 28800 Flags: S B D ┌───────────────────────────────────────────────────────────────────────────┐ │░░░▒▒▒▓▓▓ End Of IceEdit Documentation ▓▓▓▒▒▒░░░│ └───────────────────────────────────────────────────────────────────────────┘