IHLP1
+¬╣Help Index≥&BIF Logon ScreensMBIF Message ScreenlBIF Notes▀qCopyright/License£äWelcome to Intellicomm9ïNew User Introductionî¡Learning Intellicomm╞User-Supported?3σHelp on Help▐⌠Printing Problemsj∙Help Linkç·Using the Menus╡Intellicomm OverviewFeature SummaryLACommon Questions & AnswersKhORDERING INFORMATION╣kCredit Card OrdersDirect Mail Order∞âRegistration Benefits4ƒDistribution Sites¼TECHNICAL SUPPORT8╔Intellicomm Files█Deleting Icom Files÷DocumentationTⁿSearching HelpText Editor Menu)File Viewer MenuúUpgrader Introduction( Intellicomm Setup≥%User Settings.Debugging Log SettingsM?General SettingsToFilenames and Paths≡îScreen/Color SettingsxÖTerminal Settingsú┼Dialer SettingséΦFile Transfer Settings░External Protocols¥ProtocolsEExternal Protocol IntroductionRrComm Port Settings+ÇHost Mode Settingsⁿ│File Tagger SettingsΓSysop Settingsa⌡Tagger Keywordsv·Load a New Setup FileⁿExit SetupK■Message DirectoriesäPTR UploadsdMail Reader~Hotkey MenuìMain MenuN.Exit Intellicomm╨2Job DirectoryLJob Editor╛XSet job starting day/time%fBank WithdrawalhSend message replies+iGet all new mailykGet new files listPpUpload tagged filesqDownload tagged filesεqBank Deposit╨rGet personal mail onlyuChange BBS/File AreasSearch BBS for filesæüCustom Command/Run scriptæDOS Command/Run a programîôGo to terminal modeûCapture on/offûùRepeat job6ÖExit to DOSΦ¢Job Editor IntroductionºBBS Directory╔┴Select a BIF├BIF Editorî╥BIF Response┴πBIF Setup TipsH
BIF General Settings¬)BIF Bank/List ScreenïJCOUNT File Areas≡NBBS File List DetailsΘbBIF File ScreenMëBIF Extras Screendû_Edit File DescriptioníƒExport D/L's to TEXT FILE»úBIF Format for Exportí«_Tag Uploadsò▓DOS Shelln├Screen Blanker╤TerminaloΣTerminal MenuaScrollback BufferKPort SettingsΘChat Mode,'Host Modeó5Host Menu6=Dialer╝CKeystroke BufferkFCapture√LUsage LogûTFile Picker╦WDownload DirectoryæYUpload Directory▀[Screen Capture≤]File ManagerKäFile ViewerÅêFile TaggerEªTagger Sort Order≈¬Tagger Column 2U¼File Tagger Introduction╪┘Tagger Edit Mode╩εTagger Tools
√Tagger Import/Export▀Automatic Browse Mode╟Text EditorΣEditor Cursor KeyΣEditor Cursor Keys¡Working with Blocks█Edit File)Job Pause Menut"Exit BIF Editor╙$New Files ImportsÖ>Keyword TipsüPStrip Comment KeywordsS[Replace KeywordsLiExclude File Keywords¼nNote File KeywordsEwICOMAUTO Easy SetupsxëLearn ModesñïBIF LearnG▓BIF Overviewε╦_BIF Learn - Main Menu╤╨_BIF Learn - Main Menu [BBS Recognized]T┘BIF Learn Online MenuX▌BIF Learn - Message/Reply TransfersqBIF Learn - New Files Collection╫BIF Learn - File Downloads
&BIF Learn - Time Bank Transactions06Finishing up after BIF Learn┴D_ICOMAUTO Error½JInput TextèPTroubleshooting!UDebugging Log±nAutomation in GeneraluèAutomation in Detail9«Automation in Detail Continued¥╒Automated Logons.┘Automated Mail Runsu▌Automated DownloadsyΦAutomated Uploads°Automated Bank Transactions>√BIF Logons⌠	Enter Phone Numberµ
	Setup Problems┬1	Command Line OptionsoD	CatalogsK	Optimizing Intellicommñr	_Run Script\t	_Run JobKx	SND/GET Lists9ô	Long Distance ServicesΣñ	Control Menu,«	_Message Packet Filename¼░	Transfer Prioritiesç╘	Transfer Dayƒ╫	Packing on Exit├┘	Archive Viewerí▄	PKZIP7
To use the index, select a help link from the list below.  For more
information on selecting help links, press the [F1] key.

For problem-solving see Troubleshooting and TECHNICAL SUPPORT.


	Welcome to Intellicomm		Intellicomm Overview
	Learning Intellicomm		Using the Menus
	New User Introduction		Upgrader Introduction
	Copyright/License
	───────────────────────────────────────────────────────────
	Common Questions & Answers	Setup Problems
	Troubleshooting			Documentation
	TECHNICAL SUPPORT			Help on Help
	Search Results  (results of last search with [Ctrl-F1])
	───────────────────────────────────────────────────────────
	Command Line Options		Intellicomm Setup
	───────────────────────────────────────────────────────────
	User-Supported?			ORDERING INFORMATION
	Intellicomm Files			Deleting Icom Files
	───────────────────────────────────────────────────────────
	BIF Learn 				BIF Setup Tips
	Automation in General		Automation in Detail
	Automated Logons			Automated Mail Runs
	Automated Downloads 		Automated Uploads
	Automated Bank Transactions	ICOMAUTO Easy Setups
	───────────────────────────────────────────────────────────
	Hotkey Menu				Main Menu
	Job Directory				Job Editor
	BBS Directory				BIF Editor
	Dialer					Long Distance Services
	Terminal					Host Mode
	───────────────────────────────────────────────────────────
	File Tagger				SND/GET Lists
	───────────────────────────────────────────────────────────
	File Manager				Text Editor
	File Viewer				DOS Shell
	Screen Blanker 			Packing on Exit
	───────────────────────────────────────────────────────────
	Script Manager 			Script Learn
	Script Language			Script Debugging
	SCRIPT.DOC				SCRTUTOR.DOC
	ASCII Codes				Extended ASCII Codes
	Keyboard Codes 			Color Codes
	───────────────────────────────────────────────────────────
	Intellicomm Add-ons 		Mail Reader
	Archive Viewer 			PKZIP
	Multitasking Intellicomm 	Optimizing Intellicomm

──────────────────────────────────────────────────────────────────────────
Remember that you can perform a search for specific text on all help
topics, building a custom "index" of all the topics containing a specific
topic you are interested in.	Use the index above to browse around, but
when you have a specific topic/subject in mind just press [Ctrl-F1] and
enter the subject you're interested in ("BIF", "download", "Tagger",
"script", etc).  Please see Searching Help for tips.
──────────────────────────────────────────────────────────────────────────
&See BIF Editor for general information on using the BIF Editor.

The information defined on the BIF "Logon" screen is what Intellicomm uses
to automatically log you on (right to the BBS Main Menu) either during
automated jobs, or after connecting when using "Dial" from the BBS
Directory.

IMPORTANT: The "Password Answer" item determines whether Icom tries to
auto-logon after using "Dial".  If no password is defined, auto-logons are
NOT attempted, nor can you use the BIF for automated jobs.	If a password
IS defined, this tells Intellicomm that you have the "Logon" screen set up
properly, and it's okay to attempt automated logons.

The "Password", "Pause" and "More" slots (see below) are used GLOBALLY
throughout automated BBS sessions: unless you OVERRIDE these prompts (where
possible) on another BIF screen.  If the BBS uses the same Pause/More
prompts globally (in the mail system, file system, etc.) then you need only
define the prompts here on the Logon screen, and you can leave the
Pause/More prompts BLANK on other BIF screens.

NOTE: All prompts defined in the right column below (as well as the Message
Menu, Bank Menu and File Menu prompts) *and* the four "External Extra"
prompts on the "Extras" screen, are tracked AT ONCE during auto-logons.  So
it doesn't matter in which order the questions are asked by the BBS . . . 
Further you needn't use these logon prompts SPECIFICALLY for the purpose
outlined below.  For example, you could answer some miscellaneous prompt
using the "Confirm" slot, if the BBS doesn't confirm your name entry.

Logon/Global Commands and Prompts
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

 ───────────────────────────────────   ───────────────────────────────────
 [Escape] Answer: The answer to the    [Escape] Prompt: For use on BBS's
 [Escape] Prompt --> in the next	    that force you to press the [Esc]
 column.	Normally ~^[~^[ which	    key once or twice to enter the BBS,
 means pause 1 second, send [Esc],     this is the PROMPT that tells you
 pause 1 second, send another [Esc].   to press [Esc].

 ───────────────────────────────────   ───────────────────────────────────
 Your Logon Name: The response to	    Name: The BBS logon prompt that
 the Name prompt --> in the next	    asks for your name.
 column.	This is the name you use
 on the BBS.  If both your first and
 last name can be sent to the Name
 prompt enter as Firstname Lastname. 
 If names must be entered
 separately, enter your name as
 Firstname^M~Lastname (^M =
 [Enter]).

 ───────────────────────────────────   ───────────────────────────────────
 Password Answer: The response to	    Password: The BBS prompt that asks
 the Password prompt --> in the next   for your password.  This prompt is
 column.	See the notes at the top     tracked during the logon, AND when
 of this help screen, regarding use    accessing and leaving bbs
 of the Password Answer item. 	    doors/sub-menus (the Message Menu,
							    for example).  Some BBS's ask you
							    to enter your password again after
							    leaving doors.

 ───────────────────────────────────   ───────────────────────────────────
 Mode/Language: Response to the	    Mode/Language: The BBS logon prompt
 Mode/Language prompt --> defined in   (if any) that asks you to select a
 the next column.  This is a *very*    language.
 important item for BBS's that use
 multiple languages.  If multiple
 languages are available, look for a
 language called "Standard BBS
 Prompts", or "Script Prompts" or
 the like.  If available, this
 language will use all the STANDARD
 BBS prompts (as opposed to Sysop-
 customized prompts) which should
 match Icom's BIF template data
 exactly.  If no Standard Prompts
 language is available, AND if the
 BBS uses Sysop-customized prompts,
 you might want to ask your Sysop to
 set up a Standard Prompts language. 
 In most cases it can be done in
 less than 5 minutes... and it'll
 save *all* automated callers from
 modifying their scripts or BIFs.

 ───────────────────────────────────   ───────────────────────────────────
 Confirm Answer: The response to the   Confirm: The BBS logon prompt (if
 Confirm prompt --> defined in the     any) that confirms your name entry. 
 next column.					    I.e. after the "Name" prompt above
							    is answered, some BBS's will ask:
							    Firstname Lastname from City?

 ───────────────────────────────────   ───────────────────────────────────
 Graphics Answer: The response to	    Graphics: The BBS logon prompt (if
 the Graphics prompt --> defined in    any) that asks you whether to use
 the next column.  It makes no	    ANSI Graphics, or ANSI Color, etc.
 difference to Icom whether you use
 ANSI graphics or not; it ignores
 ANSI codes when tracking BBS
 prompts.

 ───────────────────────────────────   ───────────────────────────────────
 Scan Answer: The response to the	    Scan messages: The BBS logon prompt
 Scan prompt --> defined in the next   (if any) that asks whether to scan
 column.	Normally you WON'T want to   the message base for new mail,
 scan the message base; it's		    since your last logon.
 preferable to use an automated job
 to pick up your new mail.

 ───────────────────────────────────   ───────────────────────────────────
 Pause Answer: The response to the     Pause: The prompt that pauses BBS
 Pause prompt --> defined in the	    output, asking you to press [Enter]
 next column.	IMPORTANT: If you	    (or some other key) to continue. 
 have "CR w/Commands?" set to YES on   Normally you cannot STOP further
 the BIF General Settings screen do    text from being displayed at the
 NOT define ^M ([Enter]) here.	    Pause prompt: the "More" prompt
 Define a single SPACE, since Icom     (below) is the prompt that lets you
 will ADD ^M automatically.		    stop text.

 ───────────────────────────────────   ───────────────────────────────────
 No More: The response to the More     More: The prompt that pauses BBS
 prompt --> defined in the next	    output, AND allows you to send a
 column: tells the BBS *not* to	    response ([N]o More, etc) to STOP
 display any further text (makes for   further text from being displayed. 
 faster logons and automated
 sessions in general).

 ───────────────────────────────────   ───────────────────────────────────
 Birth Date: The response to the	    Enter Birth Date: The BBS prompt
 Enter Birth Date prompt --> defined   (if any) that confirms your date of
 in the next column.  Enter it here    birth from time to time, during
 JUST as you'd enter it online.	    logons.  Why the world needs this
 I.e. do not use MM/DD/YY unless you   prompt is a mystery (BBS's do not
 must actually enter the date 	    hold national secrets worthy of
 separator (/) yourself online.  The   such "security" in most cases), but
 BBS may *display* MM/DD/YY, but you   for those that do... Icom can
 rarely have to actually enter the     handle it for you automatically.
 date separators and you'll just
 define MMDDYY (or DDMMYY, etc) here
 in those cases.
 ───────────────────────────────────   ───────────────────────────────────
 Home Phone: The response to the	    Enter Home Phone: The BBS prompt
 Enter Home Phone prompt --> defined   (if any) that asks for your VOICE
 in the next column.  Enter your	    or Home phone number from time to
 phone number JUST as you'd enter it   time, during logons.  Similar to
 online.	I.e. do not use (555) 555-   the above... it's used on BBS's
 5555 (punctuation/spaces) unless	    that hold national secrets (?), to
 you must actually enter 		    prevent foreign spies from using
 punctuation/spaces online.  The BBS   your valuable BBS account.  Your
 may *display* (555) 555-1234, but     logon password 'should' be
 you rarely have to actually enter     sufficient though, considering the 
 the punctuation and you'll just	    level of "top-secret" information
 define 5555551234 here in most	    from one BBS to the next.   Sysops
 cases.						    get entirely too impressed with
							    their BBS's sometimes, don't they?

 ───────────────────────────────────   ───────────────────────────────────
 Startup Command: For convenience,     Main Menu A: The BBS's "Main Menu"
 this command is sent as soon as	    prompt.  Sometimes BBS's use a
 Icom finds either of the Main Menu    different prompt at the "Main
 prompts defined in the next column.   Conference" (as opposed to when
 Use it to [J]oin your favorite	    you're in conference 2, etc), and
 conference, or to turn [X]pert mode   this is why Icom allows TWO Main
 on... etc.  Or just leave it blank;   Menu prompts.  This prompt does NOT
 it's up to you what you do with it.   have to actually be on the BBS's
							    command line.  See BIF Setup Tips
							    for more tips and information.

 ───────────────────────────────────   ───────────────────────────────────
 Logoff: The command Icom will send    Main Menu B: See above.  An
 to the BBS when it's finished all     alternate "Main Menu" prompt for
 automated jobs and is ready to	    BBS's that display the main menu
 disconnect.  Note that this		    differently, depending on the
 "Logoff" prompt is used at *all*	    conference you're in.
 BBS menus and sub-menus, UNLESS you
 override it by adding a different
 logoff command ("Logoff Msg Menu",
 etc) on one of the other BIF
 screens.

 ───────────────────────────────────   ───────────────────────────────────
 Exit Command: A response (or 	    Logged Off: Some text the BBS sends
 @SCRIPT) Icom sends once it finds     when it's time to hangup (or when
 the "Logged Off" prompt --> defined   it's time to run the @PCP-OFF.SCR,
 in the next column.  If blank, Icom   etc to logoff from PC Pursuit). 
 issues a HANGUP command (same as	    Usually something like "Thanks for
 pressing [Alt-H]). 			    calling" or the like.


See also:
	BIF Setup Tips
	Finishing up after BIF Learn
ôSee BIF Editor for general information on using the BIF Editor.

Message Commands and Prompts
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This BIF screen is used by Intellicomm during automated message runs. 
During reply uploads, all of the prompts related to REPLIES are tracked at
once.  During message downloads, all of the prompts related to MESSAGES are
tracked at once.  I.e., it matters not in which order the prompts on this
screen are received.

TIP: Message uploads and downloads are performed using the 'Send Mail' and
'Receive Mail' protocols, which are defined on the BIF General Settings
screen.  If you define 'ASCII' as the 'Receive Mail' protocol, a simple
text CAPTURE is performed to the filename defined below in the 'Msg
Filename' setting.


 ───────────────────────────────────   ───────────────────────────────────
 Access Msg Menu: The command (if	    Message Menu: BBS text Intellicomm
 any) Intellicomm must send from the   watches for (if any) to determine
 BBS MAIN MENU, to access the 	    when it's at the BBS Message Menu. 
 message door or sub-menu.  Leave	    Leave blank if the BBS has no
 blank if the BBS has no message	    message sub-menu/door.
 menu.
 ───────────────────────────────────   ───────────────────────────────────
 Send Replies: If a 'Send Message	    Send Replies Now: BBS text
 Replies' task is defined in an	    Intellicomm watches for to
 automated job, and Intellicomm	    determine when to actually start
 locates the 'Reply Filename' 	    the upload.  The 'Send Replies'
 defined below, it sends this 	    command is sent, then it watches
 command to the Message Menu to	    for this text: when found, the
 ready the BBS to accept a reply	    actual upload is started.  NOTE: If
 packet.						    no 'Send Replies Now' prompt is
							    defined, Intellicomm begins the
							    upload immediately after sending
							    the 'Send Replies' command (if any)
							    to the BBS.

 ───────────────────────────────────   ───────────────────────────────────
 Reply Filename: This is the file	    Replies Accepted: Tells Intellicomm
 Intellicomm will upload to the BBS    that the reply file was success-
 when the 'Send Replies Now' prompt    fully uploaded.  If defined and not
 is found.					    received, Intellicomm tries to send
							    the reply packet again (two times
							    total).  If blank, Icom assumes
							    that the upload was successful as
							    long as the upload protocol doesn't
							    abort.

 ───────────────────────────────────   ───────────────────────────────────
 Confirm Answer: The response to the   Confirm Receive: If the BBS mail
 'Confirm Receive' prompt --> 	    systems asks you a question similar
 defined in the next column (if	    to 'Do you want to receive your
 any).						    mail now (Y/N)' or the like, define
							    the prompt here.
 ───────────────────────────────────   ───────────────────────────────────
 General Read: The command		    Receive Messages: BBS text that
 Intellicomm sends to the mail	    tells Intellicomm to begin the
 system when a 'Get all new		    download, after sending either the
 messages' task is defined in a job.   'General Read' or 'Personal Read'
							    command.  NOTE: If no 'Receive
							    Messages' prompt is defined,
							    Intellicomm begins the download
							    immediately after sending the
							    'General Read' or 'Personal Read'
							    command (if any) to the BBS.

 ───────────────────────────────────   ───────────────────────────────────
 Personal Read: The command		    Receive Success: Tells Intellicomm
 Intellicomm sends to the mail	    that the message file was success-
 system when a 'Get personal mail	    fully downloaded.  If defined and
 only' task is defined in a job.	    not received, Intellicomm tries to 
							    download the mail packet again (two
							    times total).  If blank, Icom
							    assumes that the download was
							    successful as long as the download
							    protocol doesn't abort.


 ───────────────────────────────────   ───────────────────────────────────
 Msg Filename: The filename		    More Mail Found: If this BBS text
 Intellicomm renumbers prior to	    is found during a message download,
 message downloads, and the filename   Intellicomm sets a flag and
 it attempts to extract a new files    performs ANOTHER message download
 list from, if an 'Extract Newfiles'   when the first completes.  Used for
 filename is defined below.		    message systems which limite the
							    number of messages you can download
							    per message packet.
 ───────────────────────────────────   ───────────────────────────────────
 Extract Newfiles: The filename (if    No Mail Found: BBS text signifying
 any) of the NEW FILES LIST included   that no new mail exists since your
 in the mail packet.  If defined,	    last message download (if found,
 Icom attempts to extract this file    Icom cancels the message download).
 from the 'Msg Filename' defined
 above, and imports the new files
 list into the File Tagger.

							    ───────────────────────────────────
							    No Time Left: BBS text signifying
							    that new mail was available for
							    download, but there wasn't enough
							    online time remaining to download
							    it (if found, Icom cancels the
							    message download).. 

 ───────────────────────────────────   ───────────────────────────────────
 More Answer: Overrides the usual	    Message More: The format of the
 answer to the 'More' prompt while     'More' prompt while in the message
 in the message menu.  For certain     menu.  If blank, Intellicomm
 message transfers (ASCII captures)    assumes the 'More' prompt defined
 you may want to define the BBS	    on the BIF Logon Screen.
 'Display all messages Non-Stop'
 command here.  If blank, Icom
 assumes the 'No More' command
 defined on the BIF Logon Screen.
 ───────────────────────────────────   ───────────────────────────────────
 Leave Msg Menu: BBS command(s)	    Message Pause: The format of the
 needed to exit the Message Menu (if   'Pause' prompt while in the message
 any) and return to the BBS Main	    menu.  If blank, Intellicomm
 Menu.  For message DOORS, this may    assumes the 'Pause' prompt defined
 be a [Q]uit Mail Door command.  For   on the BIF Logon Screen.	The
 simple message sub-menus, a simple    RESPONSE to this prompt is always
 [Enter] (^M) may exit the Message     the 'Pause Answer' command, defined
 Menu back to the BBS Main Menu.	    on the BIF Logon Screen.	Use a
							    'Message Extra' prompt if you must
							    send a different response to the
							    Message Pause prompt.

 ───────────────────────────────────   ───────────────────────────────────
 Logoff Message Menu: BBS command(s)   Enter Protocol: Message system
 needed to logoff directly from the    prompt which asks you to enter a
 Message Menu (if any).	If no	    transfer protocol (send mail or get
 command is defined (i.e. if the	    mail).  The responses to this
 mail system doesn't support direct    prompt are defined in the 'BBS
 logoffs) Icom first sents the	    Letter' items under the Send Mail /
 'Leave Msg Menu' command (if any)     Receive Mail protocols, defined on
 then logs off from the BBS Main	    the BIF General Settings screen.
 Menu.

 ───────────────────────────────────
 Reply Dir: Overrides the usual
 'Reply Dir' defined on the Icom
 main setup Filenames and Paths
 screen.	Define only to override
 the main setup directory for a
 particular BBS.
 ───────────────────────────────────
 Message Dir: Overrides the usual
 'Message Dir' defined on the Icom
 main setup Filenames and Paths
 screen.	Define only to override
 the main setup directory for a
 particular BBS.


See also:
	BIF Setup Tips
	Finishing up after BIF Learn
╒See BIF Editor for general information on using the BIF Editor.

Notes can be attached to any BBS Information File (BIF) by entering the
BIF Editor, Editing the BIF, and selecting "Notes" from the bottom menu.
Once a note is attached to a BIF, it can be read while in Terminal mode
(i.e. while connected to the BBS) by pressing [Alt-Y].  Use the Terminal's
[Alt-Z] menu if you forget the [Alt-Y] key.

BIF Notes are quite flexible and can be used for a variety of purposes. 
The most common is to keep track of important BBS information, such as
special setup needed for automation, or the name of the Sysop, or the hours
of the BBS, etc.

Some uncommon uses include storing complicated BBS commands in the BBS
Notes, then using Icom's "Block to Keyboard Buffer  [Alt-K]" option in the
Editor to paste the command into the Keystroke Buffer.  The command(s) can
then be sent to the BBS with just a couple of keystrokes.

If you're a BBS System Operator, and are planning to pre-configure a BIF
for your users and post an ICOMAUTO.ZIP for downloading (please see
ICOMAUTO Easy Setups for information), the BIF Notes are a good place to
put important information such as the BBS rules, subscription fees, Sysop
name(s), special file areas/organization of the BBS, etc.  When Icom users
download the ICOMAUTO.ZIP and sit back for an easy setup, the notes will be
automatically displayed!  It's a sure-fire way to ensure that important
information isn't missed.

See also:
	Text Editor
╗ACKNOWLEDGEMENTS

Special thanks to everyone who has been involved with Intellicomm up to
this point.  Listing all the people would be fruitless, so please accept
this group THANK YOU!

Intellicomm uses the SPAWNO routines by Ralf Brown to minimize memory use
while shelling to DOS and running other programs.

COPYRIGHT AND TRADEMARK NOTICE

Intellicomm is not public domain software.  All files that accompany
Intellicomm, including this documentation, are Copyright 1991-1994
Liberation Enterprises.	Intellicomm is a Trademark of Liberation
Enterprises.  Various other products mentioned in the documentation are
trademarks of other companies/developers.

DISCLAIMER

Intellicomm contains hundreds of user-configurable settings and can run
into even more variables in equipment and at the BBS's it calls.  Though
the product has been tested as thoroughly as possible, please be aware that
there may still be combinations of settings/events that may uncover new
problems.

Thus, Intellicomm and its documentation are distributed and sold AS IS,
without warranty of any kind as to performance of merchantability, fitness
for a particular purpose, or any other warranties, either express or
implied.	Neither Liberation Enterprises nor its dealers or distributors
shall be liable to the user/purchaser or any other person or entity with
respect to any liability, loss, or damage caused or alleged to be caused
directly or indirectly by the software or its documentation.

LICENSE

Intellicomm is not free software.	It is a copyrighted commercial product
and is simply marketed using an alternative marketing technique called
user-supported or 'shareware' marketing.  Under this marketing concept you
may use evaluation ('unregistered'; not paid for) copies of Intellicomm
before you pay any money, to determine whether the program suits your
needs.  If you find that Intellicomm doesn't suit your needs you're out no
money and you can simply delete it with no worries as to whether it's
"returnable" or not, and with no "re-stocking" charges as is often the case
with retail software.  You may also distribute evaluation (unregistered)
copies to others, as long as you follow the conditions below.

You are licensed to use evaluation copies of Intellicomm at no charge for a
limited evaluation period.  Once you are satisfied that the program is
useful to you, after a reasonable evaluation period of 30 days or less, you
must either purchase your copy or discontinue use and delete all files.  To
purchase your copy follow the instructions in the ORDERING INFORMATION help
link.  Under NO circumstances may Intellicomm be used in a commercial or
institutional environment, without purchase, past a 30 day evaluation
period.  Re-distribution of Intellicomm is encouraged but must comply with
the following:

1.	The serialized 'key' file ICOM.REG (purchased copies only) must never
	be re-distributed.	This one file is the only difference between the
	'registered' and evaluation versions of Intellicomm.  You may lose
	your registered status making you ineligible for no-cost or low-cost
	upgrades, and could even be sued for damages if the file is
	distributed inadvertently so please BE CAREFUL with this file.  A
	unique serial number is encoded in each ICOM.REG file, and illegally
	distributed files can be traced directly back to the purchaser.

2.	No charges other than reasonable overhead/copying fees ($10 or less)
	may be levied for distribution of an unregistered evaluation copy.

3.	The program files, documentation, and online help files must remain
	absolutely unmodified, and the package must be distributed in its
	entirety.  Intellicomm is only to be re-distributed if ALL files are
	included (with the exception of the ICOM.REG file mentioned above). 
	Please see Intellicomm Files for a list.

Any re-distribution of Intellicomm that violates these conditions is
prohibited.

Registered (purchased) copies of Intellicomm are no different than retail
software or any other copyrighted work, in that you cannot re-distribute
the commercial portion of the program (specifically the ICOM.REG file
supplied to you when you purchase Intellicomm), and you may only copy the
commercial portion (ICOM.REG) for the purposes of backup.  The ICOM.REG key
file must be treated like a book in that the same ICOM.REG key file may not
be used on more than one computer at the same time, just as a book may not
be read by more than one person at the same time (without making an illegal
copy).  You cannot, for example, copy an ICOM.REG file that your employer
purchased, and take it home for your personal use, or vice versa.  If
registered copies of Intellicomm are used on a network, one copy must be
purchased for each terminal on the network that has access to ICOM.EXE and
ICOM.REG.
¢Welcome and thank you for your interest in Intellicomm v2.0!

Before we begin, let's first quickly get the help system (what you're in
right now) introduction out of the way.  When using Intellicomm, you can
obtain instant context-sensitive help on whatever it is you're working on
by simply pressing the [F1] key.  Don't forget to use the [F1] key
frequently whenever you enter an unfamiliar area: the online help is where
all the tips, tricks, and other little tidbits are.  If you are unfamiliar
with online help systems, and don't know how to select a Help Link to get
information on another topic, please press the [F1] key now for more
information.

Several help links have been designed to introduce you to Intellicomm v2,
be you a new user or an Intellicomm v1.00 upgrader.  Before we jump off
into another topic though be sure you understand the information and keys
listed on the bottom line of the help window.  Remember, [Alt-F1] brings
you back to the previous topic after selecting a Help Link, and [Shift-F1]
(Index) will show you all of the major help topics allowing you to browse
around quickly.  If you lose your place or simply want to look around,
press [Shift-F1] to pop up the index.  Everything you'd ever want to know
about Intellicomm is documented in the online help, and can be quickly
accessed via the help index.

Next up for new users:
	Copyright/License		Important!  Please read.
	Intellicomm Overview	Why Intellicomm?
	Feature Summary		Interesting concept, tell me more!
	New User Introduction	I'm in, let's get started.

And for veterans:
	Copyright/License		Important!  Please read.
	Upgrader Introduction	What's new in Icom v2?

Have fun!
Q"NEW USER INTRODUCTION
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Step one on the road to automated bliss is to activate 'BIF Learn' and
follow the on-screen instructions.

BIF is short for 'BBS Information File', which is a file that Intellicomm
uses (at least one BIF per BBS) to automate BBS calls.  The BIF holds the
BBS name, telephone numbers, and all the BBS 'prompts' (What is your name?,
Enter Filename to Download, etc) that Intellicomm watches for during
automated calls.  To help you to understand what BIF Learn does, below is a
sample of the BIF 'Logon' section.  The RESPONSES Intellicomm sends to BBS
prompts are on the left, and the BBS PROMPTS Icom watches for are on the
right.  For example, 'Wayne Duff' is the response Intellicomm would send
when it found the text 'st name? ' from the BBS during an auto-logon:

 ╔═╡ Logon/Global Commands ╞═════════╡ Logon/Global Prompts ╞═════════════╗
 ║ [Escape] Answer				  [Escape] Prompt				    ║
 ║ Your Logon Name	Wayne Duff	  Name . . . . . . st name? « 	    ║
 ║ Password Answer	<Confidential>   Password . . . . echo)? «		    ║
 ║ Mode/Language	3			  Mode/Language  . ter)=no change? «   ║
 ║ Confirm Answer . Y			  Confirm  . . . . Correct? « 	    ║
 ║ Graphics Answer	N Q			  Graphics . . . . phics (Enter)=no? « ║
 ║ Scan Answer  . . N			  Scan Messages  . Read' (Enter)=yes? «║
 ║ Pause Answer . . 			  Pause  . . . . . er) to continue«    ║
 ║ No More  . . . . N			  More . . . . . . More? «		    ║
 ║ Birth Date . . . 			  Enter Birth Date				    ║
 ║ Home Phone . . . 			  Enter Home Phone				    ║
 ║ Startup Command	X ON 		  Main Menu A	. . Board Command? «    ║
 ║ Logoff . . . . . G			  Main Menu B	. . rence Command? «    ║
 ...

As you can see above, the BIF Logon Screen has slots for all of the common
BBS logon questions.  By simply placing various BBS prompts and responses
into a BIF, Icom can automate logons to any BBS; and using other BIF
screens (Message, Bank, New Files List, File) it can automate other tasks,
such as message transfers, new files list collection, uploads and
downloads, on any BBS.  There is also a BIF 'Extras' screen which contains
four general purpose prompt and response slots (for non-standard prompts)
EACH for logons, message runs, and file-related activities.  When you can't
find a BIF slot to use, just use an 'Extra' slot.

The purpose of BIF LEARN is to GET the proper BBS prompts and responses
into the BIF -- in the proper BIF slot.  If all BBS's worked in the same
way, and used the same prompts, BIFs would not be necessary.  But until
that day comes, if ever, and we have some 'standard' ways of doing things
at BBS's, you can use BIFs to tell Intellicomm HOW to automate various
tasks at a given BBS.

BIF Learn not only helps you to create BIFs, but also optionally creates a
few 'jobs' which you can Run from Icom's Job Directory, to place automated
calls to BBS's.  The process goes like this (no need to take notes... this
is just an outline to give you an idea what will be happening):

  ■	Activate BIF Learn and select "Create a new BIF" to create a BIF for a
	particular BBS.  This is usually done once and ONLY once, per BBS.

  ■	Enter the information you are asked for, such as the BBS name and
	telephone numbers.	If you need help with a question, press [F1].

  ■	BIF Learn then dials the BBS.  When it connects one of two things will
	happen:

	(1) The BBS software type (PCBoard, Wildcat, RBBS, etc) WILL be
	recognized and BIF Learn will load proper BIF information (the prompts
	to watch for, and the commands to send) for that particular BBS type. 
	Icom knows the standard prompts and commands for many BBS types, and
	if the BBS type *is* recognized you will be asked for your Logon FIRST
	NAME, LAST NAME, and PASSWORD, and BIF Learn will then attempt to
	AUTOMATICALLY logon to the BBS.  At this point you'll be set up for
	complete automation, unless the Sysop customized one or more BBS
	prompts.	It can't get much easier than that!

	(2) The BBS software type will NOT be recognized (less likely, but
	possible) and BIF Learn will just let you logon manually, creating a
	BIF as you go along.

	In either case, if BIF Learn does not answer a logon prompt, WAIT a
	second or two before answering the prompt manually (type in the proper
	response on the keyboard).  Once you answer, BIF Learn will then
	display a menu, asking you which prompt you answered.	This
	information is needed to place the BBS prompt (captured from the
	screen by BIF Learn) and response (captured from your keyboard
	response) into the proper BIF information slot as outlined above in
	the BIF Logon screen.  For example, if the BBS asks "What is your
	name?" and BIF Learn does not respond within a second or two, enter
	your usual logon name, then select "Logon Name" when you see this BIF
	Learn menu:

	╔═╡ BIF Learn ╞════════════════════╗
	║							║
	║ Which BBS prompt did you answer? ║
	║							║
	║	Press [Escape] 			║
	║	BBS Mode/Language			║
	║	Logon Name				║ ── BIF 'Logon Name' slot
	║	Logon Password 			║
	║	Confirm Logon Name			║
	║	ANSI Graphics/Color 		║
	║	Scan Message Base			║
	║	Birth Date				║
	║	Phone Number				║
	║	Pause					║
	║	More 					║
	║	Extra A					║ ─── Use the 'Extras' if you
	║	Extra B					║	  don't see a suitable
	║	Extra C					║	  BIF slot.
	║	Extra D					║
	║──────────────────────────────────║
	║	Not yet, I'm not finished!	║ ─── For MULTIPLE commands/1 slot
	║	eXit [ignore this command]	║ ─── Do not include the response
	║							║	  in the BIF
	╚══════════════════════════════════╝

	[If the menu pops up before you're finished entering the proper
	response, pick "Not yet, I'm not finished!" from the menu.	If
	something unusual happens (you get a weird prompt that you've never
	seen before and aren't likely to see again), pick "eXit [ignore this
	command]" and BIF Learn will ignore the response.]

	Once you selected 'Logon Name' BIF Learn would then insert the BBS
	Prompt (captured from the screen) and the response you entered into
	the appropriate BIF slot, on the BIF LOGON SCREEN which was shown in
	the example above:

 ║ Your Logon Name	Wayne Duff	  Name . . . . . . your first name?« ║

	KNOWING which BBS prompt is which allows Intellicomm to perform	more
	reliable error-handling than scripts are capable of performing. 
	Scripts, unless you're very proficient at writing them, have NO idea
	what they're actually doing at any given time.  Icom, on the other
	hand, knows exactly what it's doing at ALL times, and it also knows
	what the BBS is doing to it.	Further, by using BIFs Intellicomm can
	also watch for MULTIPLE BBS prompts at the same time (all the Logon
	prompts, and the 4 Logon Extra prompts, are watched for at once during
	automated logons for example), which allows more flexibility since the
	BBS prompts NEEDN'T SHOW UP IN ANY SPECIFIC ORDER.  Understanding the
	BIF concept is the key to successful automation with Intellicomm, so
	when you have time will be very worthwhile to pop up the Help Index
	([Shift-F1] ... not now, later) and browse all the topics having to do
	with BIFs and Automation (BIF Overview, Automation in General, etc).

  ■	Further instructions will be displayed once the logon is complete and
	you reach the BBS main menu.	If instructions are NOT displayed when
	you reach the BBS main menu, press [Alt-G] to tell BIF Learn that the
	logon is complete (a reminder to this effect is displayed on the
	screen as you're logging on.	You needn't memorize the [Alt-G] key).

Using BIF Learn you'll be able to automate any of these tasks, on virtually
any BBS type, with no script programming of any sort, even if the BBS type
is unknown to Intellicomm:

  ■	Logons.
  ■	Message transfers. 
  ■	New files list collection and imports to the File Tagger.
  ■	File downloads.
  ■	Time bank transactions (if a time bank is available at the BBS).

If you need help while using BIF Learn, remember to press the [F1] help
key.

HOW TO BEGIN
▀▀▀▀▀▀▀▀▀▀▀▀
[Esc], [Q], [B], [C] will take you to BIF Learn:

  ■	[Esc] to exit the help system.  This will leave you at the Intellicomm
	Main Menu.

  ■	Press [Q] (or [Alt-Q]) and you'll then see the Learn Modes menu.

  ■	From there, press [B] (or [Enter]) to select 'BIF Learn'.

  ■	Press [C] to create a new BIF.

[Yes we could have done this automatically for you....  But then you'd have
no idea how to start BIF Learn again in the future to automate calls to
another BBS!  ]

One more time, and remember this since you may have to use it several times
to automate calls to various BBS's: "Learn Modes" from the Main Menu, "BIF
Learn" from the Learn Modes menu, then "Create a new BIF" from there.  Then
just follow the bouncing ball, and press [F1] for help again if you get
stuck.

Press [Esc] now to exit the help system.
rLearning Intellicomm is a systematic process of choosing the areas you're
interested in.  The program is divided up into several (largely) separate
areas combined into one complete system.  You needn't learn all areas of
the program, and by viewing the table below you can quickly see which areas
to concentrate on.	If a HOTKEY is specified next to the AREA below, it
means that you can press that key (hold down the [Alt] key and tap the
letter) from any other major area, to change locations.

 AREA			HOTKEY				 PURPOSE
───────────────────────────────────────────────────────────────────────────
 Main Menu		[Alt-M]	Provides access to all of the major areas of
						Intellicomm listed below.  Pressing the [Alt-
						M] key (and also usually the [Esc] key, or
						selecting eXit) from any other major area
						returns you to the Main Menu.
 Intellicomm Setup			Accessed from the Main Menu, the Job
						Directory "Tools" menu, or the Terminal
						"Tools" menu, the Icom Main Setup is where
						you configure all of the global Icom settings
						(settings not oriented to a specific BBS). 
						Set the screen colors, menu style, program
						startup area (to start at the Terminal
						instead of the Main Menu for example),
						terminal and dialer settings, and so forth.
 Job Directory 	[Alt-R]	Is where you set up (Edit and Create) and
						execute (Run) automated jobs.  The routines
						necessary to carry out automated jobs are
						built in to ICOM.EXE and can perform
						automated mail transfers, file uploads and
						downloads, time bank transactions, and
						various custom tasks using the "Custom
						Command" and other job options, on virtually
						any BBS or host system.	Automated jobs
						require one or more BBS Information Files
						(BIFs) to execute.
 BBS Directory 	[Alt-D]	Is where you set up (Create and Edit) BBS
						Information Files (BIFs) for use by the
						automated routines.  BIFs hold settings
						specific to one BBS.  This is also where the
						Dialer is accessed from, which allows you to
						dial and connect to BBS's for manual online
						sessions.  BIFs needn't be set up fully to be
						used and you can define just the BBS/Host
						Name and phone numbers if you like (for
						dialing/manual sessions), or can set up only
						the BIF 'Logon' options to have Icom perform
						automated logons... or can go further and set
						up the BIF 'Message' section for automated
						mail runs, etc.  BIF sections (screens) are
						largely independent of one another.
 Terminal 		[Alt-T]	Provides direct access to your modem (offline
						or online), displays all incoming text from
						the BBS when connected, sends your keystrokes
						to the modem, provides access to the file
						transfer Protocols, etc.  All the handy-dandy
						features you need to work with a BBS.  You
						are automatically switched to the Terminal
						when you connect to a BBS from the Dialer or
						automated job.
 File Tagger				Accessed from the Main Menu or the Job
						Directory's "Tools" menu, the File Tagger is
						where you go to browse BBS new files lists
						and to Tag files for automated download and
						upload.  A very powerful and useful aspect of
						Intellicomm.
 Script Manager	[Alt-U]	This is where you set up (Create and Edit)
						execute (Run) and otherwise maintain Icom
						scripts.	Scripts are peripheral to
						Intellicomm and have nothing to do with its
						internal automated jobs.  But they CAN be
						integrated with automated jobs to perform
						just about any customized task you can
						imagine.	While Icom's internal automation
						routines serve a specific purpose (auto-file
						uploads/downloads and mail transfers mainly)
						scripts can do anything.  Scripts are covered
						in SCRTUTOR.DOC and SCRIPT.DOC and are
						absolutely and positively worth a look, but
						in most cases you WON'T get into them right
						away.  They're something to look forward to
						after you're comfortable with the other areas
						of Intellicomm.
 Host Mode		[Alt-G]	Turns your computer into a mini-BBS, allowing
						people to call into your system and transfer
						files, chat, etc.
 File Manager		[Alt-F]	Provides complete menu-driven access to any
						file or directory on any disk.  Copy,
						Rename/Move, Delete, Edit/Run, View files, or
						search an entire disk for a given filespec. 
						If you "Edit" or "View" an archived file
						(.ZIP, .ARC, .LZH, etc) the File Manager
						calls your external Archiver as defined in
						the Intellicomm Setup, to allow handling of
						compressed files.

There are other areas of the program to explore (the internal
Text Editor, File Viewer, and more terminal menus and features), but the
above are the 'major' areas of Intellicomm.	Where you spend most of your
time in Intellicomm depends entirely on your wants and needs.  If your only
priority is automated jobs, the Job Directory and BBS Directory (BIFs) are
the areas to concentrate on.	If you're interested in manual communications
(using Icom as a general/manual comm. package), the BBS Directory and
Terminal will be your main focus.	If you're interested in scripts... the
Script Manager may be your most frequented area.	Once you find yourself
constantly switching to another area of Icom from the Main Menu at startup,
you should re-define the "Base and Startup Area" in the Intellicomm Setup
(General Settings screen) to have Icom start there.

Searching the Help System
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Also, don't forget that the help system is capable of searching *all*
topics for specific text, then displaying a list of all the topics (help
links) that contained the text.  Thus, if you want to learn about BIFs,
enter the help system, press [Ctrl-F1], and enter "BIF" (no quotes) when
asked what to search for.  A list of all the topics containing the word BIF
will then be displayed.	To learn about automated downloads, perform a
search on the word "download".  To learn about the File Tagger, perform a
search on the word "Tagger", and so forth.  You should be able to quickly
locate any and all information you require, on any topic, in this manner.
1Even though evaluation versions of this program are distributed freely,
Intellicomm is a copyrighted work and is not free software.  It is simply
marketed using an alternative marketing concept known as the User-Supported
or Shareware marketing method.  User-supported marketing is a better
alternative to retail marketing, and it provides many advantages to both
software end-users and software developers, such as:

■ Advantage #1 -- Try BEFORE you Buy:  User-supported software is fully (or
mostly) operational software that you can install and evaluate for a
limited evaluation period.  Instead of paying first and trying later as
with retail software, you try the software first and pay ONLY if you like
the product and use it.

How many times have you read a software advertisement, or the box of the
package, purchased it based on that ... then discovered that it wasn't at
all what you were looking for after you used it a few times?  Most computer
users have several such packages sitting on their shelves collecting dust;
while their money sits in a retail software developer's bank account, and
in a retail software vendor's bank account.	Very few computer users have
recently purchased user-supported software packages sitting around
collecting dust, however, since they've already tried the software out, and
they KNOW that it's what they were looking for.  There's no chance to
'mislead' you into buying the product, there's no hype -- you know exactly
what you're getting BEFORE you lay your money down.

■ Advantage #2 -- No Misleading Advertisements:  Unlike retail marketing,
user-supported software does not get your attention by putting flashy full-
page advertisements in magazines or newspapers.  It advertises itself on
the idea that the best possible advertisement for a product is the PRODUCT
ITSELF, and the happy users of the product giving word-of-mouth
recommendations.  Thus, there is no chance that you will be mislead (or
possibly even outright lied to) as is sometimes the case with retail
marketing and advertising.  A product released under the user-supported
concept means that the developer has CONFIDENCE in the product and is
willing to let it do its OWN talking.

■ Advantage #3 -- You pay LESS:  Due to the benefits listed above, user-
supported software is also usually much less expensive than the retail
counterparts.	Advertising is very expensive, and when you buy retail
software you're giving a very large chunk of your money to the advertisers
and other "middle-men" who cash in BIG, at YOUR expense.  When a retail
software developer takes out advertisements in computer magazines, the cost
of every advertisement, perhaps in the tens of millions of dollars, is
added to the price of the software.  It's all paid for with YOUR hard-
earned money, and you get absolutely nothing in return for this extra money
you're charged -- advertising benefits the developer, marketers, and
magazines, not you.

■ Advantage #4 -- Hassle-free "shopping":  User-supported software means
easy shopping via BBS file listings.  Instead of fighting traffic and
crowds to shop in a software store, you simply pick up the phone (or have
Icom do it for you) and have the software delivered right to your hard
drive -- free.  In most cases you'll have several user-supported products
to choose from as well, and many will be as good as (or sometimes even
superior to) their retail counterparts.  In many cases you will not be able
to find a retail counterpart at ANY price.  It just isn't feasible to
market most of the smaller shareware programs in retail channels.

■ Advantage #5 -- Easy returns.  If you don't like a user-supported
product, you simply delete it from your disk or pass the evaluation version
of the program along to a friend, and you're done with it.	If a retail
software package doesn't meet your needs, you may have to fight traffic and
crowds again to return the software to the retailer, usually paying a "re-
stocking" fee for your trouble (if it's even returnable).

■ Advantage #6 -- Easy upgrades/FAIR upgrades.  Instead of receiving yet
another flashy advertisement in the mail when an upgrade is released
(another expense to be added to the purchase price of the upgrade)
shareware upgrades simply show up at your local BBS or shareware mail-order
outlet ready for installation, often at no cost to you whatsoever. 
Intellicomm uses a "key file" method, and when you make the purchase you
are sent a special file encoded with your registration number.  When you
install future evaluation/shareware releases downloaded right from your
local BBS, and the key file is found, the new release will automatically
register itself, enable all the registered user bonus features, and bypass
the registration reminders!  In comparison, think about your experiences
with retail software upgrades.

The advantages listed above are in YOUR best interests, as you can plainly
see.  There are advantages to the software manufacturer as well, but MOST
of the advantages of user-supported software go to the users.  With retail
software it's the exact opposite: the software manufacturer holds the
cards, and there's no advantage to you at all -- every single 'advantage'
retail developers have over shareware developers, such as telephone
technical support, is simply due to lack of funding.  If you pay for
shareware products, we'll be able to offer EVERYTHING that the retail
developers offer, MAINTAINING the advantages listed above.

What do Developers do with the money?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
When you send your financial support to a user-supported software developer
you do all of the following:

■ Encourage the developer to continue development and improvement of the
products you enjoy -- and to continue MARKETING future updates using the
'try before you buy' concept.

■ Enable the developer to purchase higher quality development equipment and
tools: Expensive development tools are often the only difference between a
high quality product and a low quality product, or a high quality product
that takes a year to develop, and a high quality product that takes half
that time to develop.  But high quality equipment and development tools are
expensive.  Give a developer the means to purchase a Turbo XT with
monochrome monitor and a copy of QuickBASIC with no add-on libraries, and
the results are predictable.	Give the same developer, with the same ideas
and skills, the means to buy a fast computer with VGA monitor and
professional development tools and add-on libraries, and the results are
also predictable: BETTER products that take less time to develop, and that
have fewer bugs.  Today, in computer programming, the only difference
between a "state-of-the-art" high quality program, and a clunker, is in the
TOOLS used to program the software.  Better development tools won't make a
poor developer a good one: The idea is to support the shareware you DO
enjoy -- products where you see potential -- enabling the developer to do
an even better job next time.

■ Better support.  Most of the differences between retail and user-
supported software, such as telephone technical support, printed
documentation, multi-line support BBS's, etc., are often simply due to lack
of funds (or lack of time, due to a lack of funds to hire people to help
out).  With financial support, you again enable the developer to enhance
his or her service to YOU ... and the benefits will be yours to enjoy.

■ Ultimately, if you not only send your support but also help to encourage
OTHERS to do the same, you'll enable the developer to hire people to help
out... speeding up future development, technical support, documentation,
order processing, and everything else.

Given all of the above, most of which are benefits which will directly
affect your own enjoyment of software that you use, the real question is
why NOT to support shareware products that you use.  Not supporting the
work does the exact opposite of the above.
⌐Context-sensitive help with whatever you're working on is available by
pressing the [F1] key.  By using help links, and the search features of
both the help system and File Viewer, you should be able to find any
information you need, lickety split.

Once in the help system use your mouse or the special keys listed below to
browse the help text.

Browsing Topics
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Press [], [], [PgUp], [PgDn], [Home], or [End] to browse through the text
for the current topic.  If using a mouse, click on the SCROLLBAR that runs
from top to bottom on the right edge of the screen.  Clicking on the 
moves up one line, clicking on the  moves down one line, clicking between
the ■ and the top arrow moves up a page, and clicking between the ■ and the
bottom arrow moves down a page.  If you try to go up or down and can't,
you're either at the top or end of the text for the current topic.

Using Help Links
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
When you see bold text such as this: Help Link, you can obtain further
information on that topic by selecting the bold text.	If the help link is
a filename, such as SCRIPT.DOC, the help system will look in the \ICOM
directory for the file, and will load it for viewing if found.  So you not
only have access to online help, but also have online access to all the
extra documentation!

To select a help link with the keyboard, press the [Tab] key (usually
located just above [Caps Lock]) until the bold text turns to a different
color, then press the [Enter] key.  You may also press [Shift-Tab] (hold
down the [Shift] key then tap [Tab]) to select the previous help link, if
you go too far.  [TIP: press [Shift-Tab] first to immediately select the
bottom-most link].	To select a link with your mouse, just move the mouse
cursor over it, and click.

When you're finished reading the help link, press [Alt-F1], or click the
[Alt-F1] at the bottom of the screen to return to the topic you were
reading previously.

[Alt-F1] Back (Return to Previous Topic)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
When you select a Help Link or this 'Help on Help' topic, you can return to
the previous topic at any time by pressing the [Alt-F1] key, or clicking on
the [Alt-F1] at the bottom of the screen with your mouse (Hint: 'click on'
means to move the mouse cursor to the text and click the left mouse
button).

[Ctrl-F1] Search (Searching the Help System for information)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
You can perform two kinds of searches in the help system: [Ctrl-F1]
searches the text of every help topic then displays a list of all the
topics/links that contained the text you were looking for.	See the
Searching Help link for more information on that method.  You can also
perform a regular text search on the topic you are currently viewing by
pressing [Alt-F] (F for Find, so it's easy to remember).  See the
File Viewer Menu link for more help on using that method.

[Shift-F1] The Help Index
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The index is a convenient way to view any of the major topics in the help
system.  To view the help index, press [Shift-F1] or simply click on the
[Shift-F1] at the bottom of the screen with your mouse.

The Help Menu (Miscellaneous Functions)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Press [Alt-Z], or click your RIGHT mouse button to call up the help menu. 
Since the help system uses Icom's internal File Viewer to display the help
text, it's actually not called the "Help Menu", but rather is called the
File Viewer Menu.  Access that help link for more information.

Printing a Topic
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
To print the current help topic, turn on your printer then press [Alt-P] (P
for Print).  Print is also available via the Help Menu, discussed above. 
If nothing is printed it's most likely just a simple setup problem.  See
Printing Problems for information.  Further if you do not have a printer or
simply wish to edit text before printing it, you can do so by following the
tips in the Printing Problems link.
èIf you have problems printing text from within the Help System or File
Viewer the problem almost certainly lies in the Intellicomm Setup on the
"Filenames and Paths" screen:

 ║ Printer  . . PRN 									║

Icom defaults to using PRN as the printer, but you can change this to COM1
or any other device name (or even a filename; see the TIP below) by
selecting "Intellicomm Setup" from the Main Menu or Job Directory/Terminal
"Tools" menu, selecting the "File/Path" screen, then entering the proper
device name in the "Printer" item at the bottom of the box.  Then press
[Esc] to exit, save your changes to disk by pressing [Enter] when asked for
a main setup filename, and you should be all set.

TIP:  If you don't have a printer, or simply wish to edit text before
printing it, you can enter a FILENAME as the "Printer" device name. 
Example:

 ║ Printer  . . C:\TEMP\ICOM.PRN							║

Icom would then 'print' to the file C:\TEMP\ICOM.PRN.	Note that if you
enter a device name such as COM1 or COM2 or LPT2, etc., do NOT include a
colon after the device name.	Just type it in like this:

 ║ Printer  . . COM1									║

or this:

 ║ Printer  . . LPT2									║
"Help Links" allow you obtain information on an unfamiliar topic, very
quickly.

If this was a real help link, you'd now be viewing help on the topic you
selected.  Press [Alt-F1] or click with your mouse on the [Alt-F1] at the
bottom of the screen to go back to the previous topic.
,Intellicomm's menus come in various shapes and sizes, but they're all used
in basically the same way.

"Box menus" are menus with items stacked on top of one another in a box,
with each item on the menu containing a 'bold' character.

"Combination menus" are menus that employ both a box menu (sometimes with
more than one column of items in the box, such as in the Job Directory)
along with a bar menu along the bottom of the screen, with several items
running from left to right; each with a bold character.  Both are described
below.

Box Menus
▀▀▀▀▀▀▀▀▀
To select an item from a box menu with your keyboard just press the [],
[] cursor keys to move the hilight bar, then press the [Enter] key to
select the item.  Alternatively, you can select an item without moving the
hilight bar by pressing the corresponding bold character on your keyboard. 
If a "hotkey" is listed to the right of the item (e.g. [Alt-A]), this means
that you can select this item WITHOUT first calling up the box menu, by
just holding down the [Alt] key then tapping the letter.

To select a box menu item with your mouse, just move the mouse cursor
anywhere within the box border on the line of the item, then click with
your left mouse button (or right mouse button if Lefthanded mouse is turned
on; see the "Mouse Settings" in the Intellicomm Setup to set up a
Lefthanded mouse).

Combination Menus - Keyboard
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
These menus have the "commands" running from left to right, usually at the
bottom of the screen, in combination with a larger display/menu in a box
above (such as in the Job Directory).  Use of these menus depends on the
setting of the "Tab Keys" item in the Intellicomm Setup.  If Tab Keys is
set to "Bottom Menu", then you use [Tab] and [Shift-Tab] to move the bottom
hilight bar, while the [], [], [], [] cursor keys move the hilight bar
up/down, left/right in the large menu in a box above.	If "Tab Keys" is set
to "Top Menu" then you use [], [] to move the bottom hilight bar, and
[], [], [Tab], [Shift-Tab] to move the top hilight up/down, left/right. 
In either case the bold characters on the bottom menu can be used to
immediately select commands, without moving the hilight bar.

Some people prefer to use the [Tab] key to move the top hilight bar, while
others prefer to use the [], [] keys, while just using the bold
characters to select commands.  Use whichever method you prefer.  To change
this setting, select "Intellicomm Setup" from the Main Menu, select the
"General" settings screen, then change the "TAB / Shift-TAB moves" item on
the 1st setup screen.

Combination Menus - Mouse
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
To use a combination menu with your mouse, you normally first select the
item you want to work with in the top box by moving the mouse cursor over
the item and clicking.  If you click again (and if the item is "Taggable",
the item is Tagged for a group operation.  If you click again the item is
untagged.  Once the item(s) you want to work with are selected, move the
mouse cursor to the command you want to execute on the bottom bar menu, and
click.
JThis topic is mainly for those who are not familiar with the benefits of
automated/unattended BBS calls.  If you already use scripts or another
automation system, skip to the Feature Summary.

The Intellicomm Advantage
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Calling BBS's can be frustrating at times.  Often the phone lines are busy
and it takes several minutes (or even hours) to get connected.  Once you
get connected, you must go through a tedious "logon" process, every time,
entering basically the same information each time.  And even after the
logon, most people tend to do basically the same things from one session to
the next: you either check the new files listing and possibly download
(get) some files, or upload (send) some files to the BBS, or access an
offline mail system such as Qmail or Tomcat or the like, to download the
mail for reading.  Or you may do all of the above.

The disadvantages of manual BBSing are many, and are not always apparent
until you're given an alternative.  Most people tend to call BBS's in the
evening and unless you have a separate data line for your modem, you'll tie
up your phone possibly missing an important call (or causing a family
member to miss an important call, which may make your hobby rather
unpopular in the household).	Further, if you call one or more BBS's long
distance you'll pay more during the daytime/evening than you would if you
could carry out your sessions while you sleep, when long distance rates are
the cheapest.	And unless you're an expert with the BBS commands and are a
touch typist, you also probably waste a lot of your online time fumbling
with cryptic BBS commands, filenames, conferences, and browsing the BBS
online help.  And of course, carrying out routine repetitive tasks on BBS's
isn't exactly exciting; the information/data ON the BBS is exciting -- not
the process of obtaining that information.

Wouldn't it be nice to be able to just press a key or two and have
everything taken care of unattended, with full error-handling while you do
something more interesting or sleep?

Yes most communications programs come with script languages which
'theoretically' allow you to automate entire BBS sessions.	But unless you
have lots of time and energy to get everything working, this route is not
very practical.  Many communications programs come with script "learn"
modes (as does Intellicomm) that watch what you do and create a script for
you -- but the resulting scripts are mindless and will fail if anything
unexpected happens at the BBS, or the connection is lost.  You can't have
peace of mind leaving a mindless script to carry out your BBS sessions
unattended while you're sleeping, especially if long distance fees are
involved.

So what's the solution?	How about a pre-programmed script with error
handling of some sort that was designed by someone who KNOWS how to write
reliable scripts to automate BBS tasks?  It sounds like a good idea, and it
is if you have no better alternative, but unfortunately no single script
can automate all tasks on all BBS's, since all BBS's do things differently. 
If the script isn't designed specifically for the BBS you call, you could
end up back where you started, either having to modify the script (which
will be very difficult if an 'expert' wrote the script) or program your
own.

Well, all of the above is precisely why Intellicomm was developed!  Icom
knows how to automate logons, uploads, downloads, mail transfers, time bank
transactions and can handle many custom tasks -- with full error handling,
that we can all but guarantee is more reliable than ANY script or
automation system on the market.  And not just on one BBS type, or two BBS
types, but on virtually *any* BBS in the world!  And you don't have to
fumble with script programming to get even the most complex tasks automated
-- and that cannot be said of any other communications program in the world
today!

It sounds too good to be true: but that's why Intellicomm is released under
the shareware marketing concept.  If you don't believe it can possibly live
up to its claims, just TRY Intellicomm for yourself for two weeks, just as
hundreds of our satisfied customers did.  Once you get the hang of it, and
experience the concepts involved first-hand, you'll never go back to your
old general communications package and scripts, and you'll pity those who
are using anything else to call a BBS!

Next up:	Feature Summary
I)If you've heard enough about features for the time being and are anxious to
get started, skip to the New User Introduction.

Intellicomm Feature Summary:

■ Automate your sessions on virtually ANY BBS, without script programming,
and with error handling that rivals even what you might be able to do
manually yourself!	Give Intellicomm's learn mode a BBS name and the phone
numbers, and you'll be automating logons, mail runs, downloads, new files
list collection, and even time bank transactions in minutes!  Your online
sessions will be carried out completely unattended, expertly at lightening-
fast speed -- and that speed allows you to get more done each day with your
limited online time, and/or reduces your connect times.

■ Browse BBS new files listings OFFLINE with the File Tagger, which
converts virtually any type of BBS file listing into indexed dBASE-
compatible databases, which can be sorted instantly forwards or backwards
in any of three ways.  Sort by filename, or file size, or location; instead
of having to view the files rigidly the way the BBS sorts them.	Omit files
you aren't interested in using a list of user-defined keywords; if you
aren't interested in .GIF pictures, you don't have to waste your time
weeding them out.  Eliminate duplicate files, and set "download priorities"
which tell the Tagger the most desirable location to download a file from,
if two or more BBS's contain the same new file.  Replace annoying or
offensive file comments automatically with the Replace Keywords.  Have the
types of files you are most interested in automatically POINTED OUT TO YOU. 
And you can even turn on the "auto-browse" mode and just sit back while the
Tagger displays each new file to you, without even pressing a key!  And of
course, since Icom's File Tagger Catalogs are stored in dBASE format you
can also use any of the thousands of dBASE compatible utilities available
to manipulate and maintain your catalogs if you have something special in
mind that the File Tagger doesn't currently support (though it does support
just about everything you can imagine... including automatic database
MAINTENANCE)!

■ Select files to upload or download with ONE key press or mouse click!
Intellicomm does the dialing, logon, enters the filenames (and file
descriptions on uploads), transfers the files you have time for, saves the
ones you don't have time for until next time, and disconnects from the BBS
completely unattended.  If your BBS has a Time Bank, Icom will even get
some time out prior to the transfer, and deposit your unused time before it
logs off!  Once offline, Intellicomm will even automatically virus check
the new downloads!

■ Automatically transfer messages in any of a staggering number of BBS
message systems.  Intellicomm integrates with your Mail Reader to
completely automate your message reading and your reply uploading.  The
Mail Reader ISN'T built-in: you're able to select the reader that suits
your needs best.

■ Carry out custom tasks using the automated job "Custom Commands" and
other custom features.  Open new capture files, change BBS menus/areas,
send commands to the BBS, wait for BBS menus, search the BBS for files,
deposit and withdraw time (and download bytes where available) in BBS time
banks, have Icom page you then switch to manual terminal mode, pause jobs
until specific a specific day and time, run other programs or .BAT files...
all using the built-in automated routines, and a quick and simple menu-
driven setup, without script programming!

■ Add to that sophisticated, user-configurable error-handling that can be
changed with just a keystroke or two from BBS to BBS!	During automated
jobs, if the connection is lost Intellicomm will call back (up to three
times total) and continue the failed job exactly where it left off.  If the
automated job is using internal Protocols or External Protocols capable of
crash recovery, and the connection is lost in the middle of a file
transfer, Icom calls back and re-starts the file transfer exactly where it
left off -- even for automated BATCH downloads!  If the BBS goes out to
lunch Icom will send a user-configurable command to the BBS (normally a
couple of Ctrl-K's followed by a Carriage Return) after a user-configurable
"timeout" period.  If Icom can't locate its position on the BBS after a
specific number of timeouts (also user-configurable, for each BBS) it hangs
up and calls back, up to three times total.	If you have a very critical
job to carry out, you can even run Intellicomm from your AUTOEXEC.BAT file;
enabling it to recover an automated BBS session after a power outage!

Programming this type of error-handling with the script languages in other
communications programs would take you weeks if it was possible at all, and
you still wouldn't be sure whether the routines WORKED until a problem
occurred.  Icom has it all built in, it's all easily configurable from one
BBS to the next, and it's all been tested by hundreds of users over
thousands of BBS sessions, on dozens of different BBS types.  You simply
can't get anywhere near this type of error-handling through auto-learned
scripts available in general communications programs.

■ While Icom's forte is automation, it is by no means limited to automation
only.  Intellicomm has a Dialer and Terminal for manual sessions which
rival the counterparts in most general communications programs.	Complete
with all the popular BBS file transfer Protocols, including internal Zmodem
with SMART crash recovery, plus support for up to eight External Protocols
(including special HS/Link support) a powerful Scrollback Buffer, a
Keystroke Buffer, Chat Mode, Host Mode, and easy menu-driven access to all
of the above.	There's no need to keep a general communications program on-
disk for manual BBS calls, and you may soon discover that Intellicomm has
more features for periodic *manual* BBS calls than most popular general
communications packages do.  You give up nothing, and gain everything.

■ With a built-in Text Editor, File Viewer, and File Manager, plus
integrated access to external programs such as your Archive Viewer and
Mail Reader, user-configurable hotkeys to run any two external programs,
and a DOS Shell feature (with swapping!), you have everything you need
right at your fingertips.  And, yes, Intellicomm does come complete with a
very powerful Script Language with over *200* commands, 100 plus system
variables, user-defined variables, global array variables, access to all
main setup and BBS information, advanced video and MENU handling that
allows you to quickly define sophisticated user interfaces for your
scripts, direct File Tagger Catalog/database access, file I/O, an
integrated script debugger, online script writing help, and script tutorial
to get you started!  Even though Intellicomm doesn't require scripts to
automate most BBS tasks, it STILL has one of the most powerful and flexible
script languages ever produced for a communications program!  Yet it
remains very simple to use and can be picked up quickly by novices, with no
prior knowledge of programming.  Imagine a script language more powerful
than Telix's SALT language, but as easy to use as Qmodem's simple script
language, and you've got Icom's script language in a nutshell.  If you've
used Qmodem, ProComm, or Robocomm scripts, you'll be very comfortable with
Icom's script language... and you'll be able to get MORE done with LESS
work.

■ The registered version of Intellicomm adds to that a very handy
Script Learn mode that watches what you do and creates scripts for you, for
those little 'custom' tasks you want to automate!  You don't HAVE to use
scripts, and you can even perform many custom jobs with Icom using the
custom job features listed earlier, without getting into scripts at all. 
But the capability to automate whatever you can dream up is certainly there
with the script language if and when it is needed.  Scripts can also be
*integrated* with Icom's internal automated jobs, anywhere in the job, with
just a couple of keystrokes.	They can also interact with the user via
menus (with full mouse support) and other easy-to-use input functions,
providing a limitless number of options.  When you put everything above
together in one package, you have

■ Intellicomm is even DESQview, OS/2 and Windows aware!  One BBS Sysop who
recently switched to OS/2 told us that Intellicomm was the ONLY DOS
communications package he was able to get to operate properly under OS/2. 
The same can be said of many Windows users.

You'll truly get the best of all worlds with Intellicomm.  Automation is
easy to set up, extremely easy to use, is MORE reliable than the more
difficult methods of automating tasks with other communications programs,
and it all works on MULTIPLE BBS types with interactive learn modes to get
you set up quickly and easily, enabling you to automate complex tasks
virtually anywhere.  And if you do run into a task on a certain BBS that
Icom's internal automated routines can't handle, or just have something
special in mind, you STILL have at your disposal a powerful and easy-to-use
script language complete with debugger and auto-learn capabilities!  Add to
that Icom's full-featured terminal with internal and external protocol
support, its dialer that is capable of logging you through PC-Pursuit and
iNet 2000 ... and you may end up dropping your general communications
package rather quickly!	Compare Intellicomm's features and low price with
ANY other comm. package in the world today, and we think you'll agree that
there's simply no contest.  Visit our BBS or support conferences and ask
our users what they think of Intellicomm -- the glowing testimonials you'll
receive may astound you!  They certainly astound us at any rate.  <grin> 
You'll meet former ProComm Plus users, former ProComm for Windows users,
former Qmodem users, former Telix users, former Robocomm uers, former Boyan
users, former Telemate users, former Crosstalk/Mirror users -- BBS users
and Sysops who've tried everything on the market, shareware and retail, and
were STILL completely astounded by Intellicomm!  It's everything a BBS user
ever dreamed of, and then some.

So why are you still reading this!?  Let's get going and put this exciting
package to use.  If you're new to Intellicomm, the New User Introduction
will get you up and running very quickly.  If you're a veteran Intellicomm
user, the Upgrader Introduction will point out all the new features in this
major upgrade.

Happy BBSing!
²&Q.	Intellicomm has too many options: I'm overwhelmed!  Where do I start?
A.	You're probably trying to view the program as a whole, and get
	everything straight all at once... but that's not how the program is
	meant to be used.  Icom is designed to give you plenty of room to grow
	in the future, and it does have quite a few areas and options, but you
	DON'T have to learn them all at once (in fact, many areas you don't
	have to learn at all, unless you have a specific need).  Please see
	Learning Intellicomm to find the area(s) you should be concentrating
	on.
							  
Q.	How do I change the screen colors?
A.	Select "Intellicomm Setup" from the Main Menu, pick "Screen/Color
	Settings", then pick "Menu Style/Colors" to access the color
	configuration menu.
							  
Q.	I'd rather have Icom start at the Job Directory (or BBS Directory, or
	Script Manager, or Terminal) instead of the Main Menu.  How do I do
	this?
A.	Select "Intellicomm Setup" from the Main Menu, pick "General
	Settings", then hilight the "Base and Startup Area" and press [Enter]
	to select a new startup area.
							  
Q.	Whenever I run an automated job or BIF Learn, Icom says "Already
	connected..." but I'm *not* connected.	Why is this happening?
A.	Your modem is forcing the carrier detect on.  To remedy the situation
	on a 2400 baud or faster modem add an &C1 command to the "Initialize
	Modem String" on the Icom main setup/Terminal screen:

	║ Initialize Modem String > AT&C1 &D2 E1 Q0 V1 X4 			  ║
							─── 
	&D2 is also handy and tells 2400 baud/faster modems to watch the 'Data
	Terminal Ready' (DTR) line on the COM port and to hangup if it goes
	low.  Icom first tries dropping the DTR line to get the modem to
	hangup, when necessary.

	On 1200 baud modems the problem is usually remedied by finding the
	small bank of switches that configure the modem (sometimes they're
	inside, sometimes they stick out the back, etc) then changing switch
	#6 to its opposite position.	Turn the modem off before you do this,
	exit Intellicomm, change the switch, then power on the modem and start
	Intellicomm.  If switch #6 doesn't work either find your modem manual
	and look for the 'Carrier Detect' switch, or simply repeat the above
	process for all switches, returning the switch to its previous
	position if it doesn't work.
							  
Q.	Icom's Dialer isn't working at all.  It seems to send a command to the
	modem, but the modem doesn't dial.  What's wrong?
A.	You most likely are telling the modem to dial in "touch tone" mode on
	a line that is not equipped for touch tone.	Enter the Icom main
	setup, switch to the "Dialing" screen, then change dial prefix 1 from
	ATDT to ATDP (T for Tone, P for Pulse).  If this isn't the problem
	check all your cables and make sure your interface cards (and
	telephone line) are properly plugged in.  Also see Setup Problems.
							  
Q.	A BBS I call requires [Esc] to be pressed twice upon connecting.  How
	can I handle this?
A.	Each BIF has options on the Logon screen called '[Escape] Answer' and
	'[Escape] Prompt':

	║ [Escape] Answer ~^[~^[ 	   [Escape] Prompt	Press <ESC>«	   ║

	Simply fill in the prompt the BBS uses on the right side (there are
	various prompts for this, and the default of 'Press Escape Twice' may
	not match what your BBS sends).  Control characters such as ESC are
	listed in the ASCII Codes link, and they must be preceded by a caret
	(^[ is ESC).  The tilde (~) causes a one second pause, which is often
	necessary or the ESC characters are sent too rapidly.
Q.	Every time I download mail from Qmail (or Rosemail/Tomcat),
	Intellicomm uploads a .PTR file.  Why is it doing this and how do I
	stop it?
A.	Please see PTR Uploads.
							  
Q.	How do I get Intellicomm to automatically extract the new files list
	from my mail packet?
A.	Edit your BIF, switch to the "Message" screen, and plug the filename
	of the new files list (normally NEWFILES.DAT) in the "Extract
	Newfiles" slot.
							  
Q.	Why do some of my jobs and/or BIFs have brackets around them in the
	Job/BBS Directory?
A.	You have inadvertently pressed 'D' or selected "Delete" to flag it as
	deleted.	No harm is done as yet though, and you can UNdelete the job
	or BIF by simply hilighting the entry and selecting "Delete" again
	(it's a toggle).  Had you selected "Pack" from the Exit Intellicomm
	menu, the deleted jobs/BIFs would have been permanently removed.
							  
Q.	I use an external protocol to transfer my mail and/or files, but the
	files end up in the wrong directory.  Why?
A.	Please see the notes on HS/Link below.
							  
Q.	I want to use the external HS/Link protocol for bi-directional
	mail/reply transfers.  How do I set this up?
A.	Please view the file HSLINK.BAT included with Intellicomm.	It
	contains remarks on proper Intellicomm setup (as do DSZ-?.BAT for
	using the DSZ or GSZ external protocol program).	Also be aware that
	if using HS/Link you should NOT define a "download directory" in the
	HS/Link configuration program.  Icom performs a CHDIR command to
	change to the proper directory (for either mail or files, as defined
	in the Icom setup/BIFs) so ALL external protocols should simply be set
	up to place files in the current directory.	If you must define a
	download directory with an external protocol, use "." (a period) which
	means "current directory" to DOS.
							  
Q.	I read in the introduction that Icom can automatically re-format file
	descriptions and can strip/replace certain word and files and
	automatically point out interesting files to me.	WHERE do I set this
	up?
A.	Whenever you're looking for a setting that ISN'T specific to a BBS,
	you'll find it in the main setup (while settings specific to a BBS are
	configured in the BBS Information Files or BIFs).  Select "Intellicomm
	Setup" from the Main Menu, then browse through the screens to get an
	idea what settings are available.	The File Tagger items are on the
	"File Tagger" screen, and the various types of keywords to re-
	format/clean up file descriptions are on the "Tagger Keywords" screen. 
	Hilight the keyword type of interest and press ENTER to add new
	keywords.  See the online help while on the File Tagger Settings
	screen or when editing a set of keywords for detailed information.
							  
Q.	I call several BBS's regularly and duplicate files are eliminated by
	the File Tagger, but Icom doesn't always download files from the BBS I
	want.  How do I tell Intellicomm the most desirable BBS to download
	files from?
A.	Since this item is specific to a BBS, it is set up in the BBS
	Information File (BIF) rather than the main setup (press [Alt-D],
	hilight the BIF, select "Edit" to change BIF data).  Items relevant to
	File Tagger and new files imports are on the "Bank/List" ("/List"
	meaning BBS file listings).  In this case you want the "D/L Priority"
	(Download Priority):

	║ D/L Priority   > 1			   Date separator . -		    ║
	  ────────────────── 

	New BIFs always default to priority 0 (no priority... all are equal). 
	Set priority 1 on the most desirable BBS (where you have the most
	online time/download bytes), but don't use priority 2 for the next-
	most desirable.  Use Priority 1, 10, then 20, etc., so that you can
	later add new BIFs into the structure without having to renumber the
	priorities in all your BIFs.	Priorities can go from 0 to over 65000. 
	0 is the lowest (no priority at all), 1 is the highest (as in priority
	one), 2 is the next-highest, etc.
							  
Q.	I call several BBS's and want to keep SEPARATE File Tagger Catalogs
	instead of having all new files go into the NEWFILES catalog.  How do
	I do this?
A.	This is set up just above the "D/L Priority" mentioned above.  Simply
	enter the new catalog name (regular DOS filename; 8 letters or less)
	and the Tagger will create the catalog and will automatically import
	to it, and will also scan it for tagged files when you request an
	auto-download.  See New Files Imports for more details/tips.  You must
	be using a registered copy of Intellicomm to use this feature;
	multiple catalogs are a registered user bonus feature and are not
	supported in the evaluation version.
							  
Q.	The File Tagger isn't showing me any files, but I KNOW there are files
	in the catalog.  What's going on?
A.	The Tagger "View Date" is most likely filtering them all out.  Please
	see File Tagger Introduction for more details.  If this isn't the
	problem your indexes may be damaged.  Use the File Manager to view the
	\ICOM\DBF directory, then look for the .NDX files that use the same
	base name as the catalog (e.g. NEWFILET.NDX, NEWFILEC.NDX
	NEWFILEF.NDX).  There are three NDX files per catalog.  "Tag" the
	three .NDX files, then select "Delete" to delete them.  Then enter the
	Tagger and "Load" the catalog if necessary.	It will automatically re-
	build new NDX files when it loads the catalog.
							  
Q.	How do I find the answer to a problem that isn't covered here?
A.	Remember that the online help changes according to what you're doing.  
	Experimenting, and using [F1] for more information when you're in the
	MIDDLE of something is the best way to get information.  You can
	always back out of something by pressing the [Esc] key if it wasn't
	what you wanted.  The Help Index ([Shift-F1]) is also very useful in
	finding specific information, as it lists every major topic in the
	help system, grouped according to the topic.  If you can't find the
	topic you're looking for in the index, press [Ctrl-F1] while in the
	help system to search the entire help file for topics containing a
	specific keyword.  For example you might enter the search string
	"keyword" if were looking for information on Tagger keywords, or "BIF"
	if looking for information on BIFs, etc.  All help topics (links)
	containing the word are then displayed, and you can view any/all of
	them.

See also:
	Setup Problems
	Troubleshooting
	Debugging Log
	BIF Setup Tips
	TECHNICAL SUPPORT
lStand up and support the most comprehensive program for BBS communications
in the world today!  Save time, effort, frustration, and long distance fees
day in day out, support the shareware concept and Intellicomm's continued
development, AND take advantage of the registered user bonus features for
just $39.95!

Intellicomm operates on a "key file" method, in that when you place your
order you are sent a special file which (once installed in the \ICOM
directory) causes regular evaluation copies to bypass the registration
reminders AND to enable all the registered user bonus features (see
Registration Benefits for details).  This way you are able to upgrade to
new minor releases at no charge, with no hassles.

Which would you like (press [F1] for help if you do not know how to select
a Help Link):

	Credit Card Order
	Direct Mail Order
	Distribution Sites
aOrder Intellicomm with your credit card and receive your key file
immediately!  No waiting for the mail, no check or money order to fill in,
no postage stamps, no trips to the mailbox -- just make a phone call with
Intellicomm and receive your key file on the spot!

Two order sites are available.  One for U.S. and international orders, and
one for Canadian residents:

 Sound Advice BBS  K.C., MISSOURI, U.S.A	INTERNATIONAL AND U.S. ORDERS;
									AMEX, Discover, MasterCard,
									VISA.
 Synapse BBS	    Gatineau, PQ, CANADA 	CANADIAN ORDERS ONLY;
									MasterCard, VISA.

Please select the BBS you wish to call (press the [Tab] key just above
[Caps Lock] to hilight one of the above sites, then press [Enter]). 
Intellicomm will then display the telephone number allowing you to edit it
to either remove the area code (if you live in the local area) or insert
the long-distance prefix (1- if dialing within North America, or the
country code if dialing from overseas).  You'll then be logged on and
placed in the credit card ordering system where you will MANUALLY enter and
confirm your ordering information.  Once you confirm your order a unique
key file will be created for you, your registered user kit (about 2 Kbytes;
a very quick transfer) will be uploaded to you, your name and address will
be added to our customer list making you eligible for future upgrade
notices and discounts, and you'll be all set!

IF YOU PREFER TO LOG ON MANUALLY
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
To enter the order system manually, dial with Icom's "Manual" BBS Directory
option:

Outside Canada (Sound Advice) : 816-436-4516
Canadian Orders ONLY (Synapse): 819-561-4321

Log on using the name "ORDER ICOM" (no quotes) and the password "ICOM" (no
quotes).	Once at the PCBoard Main Menu type "ICOMREG" (no quotes) to enter
the ordering system.  Everything is self-expanatory from there.
╬To order Intellicomm by direct mail, please print this help screen and the
order form that follows by setting up your printer then pressing [Alt-P].
If you do not have a printer, just view the order form below and be sure to
include all the necessary information in writing on a piece of paper so
that we can process your order quickly.  If you run into a problem
printing, see Printing Problems.  Once you fill out the order form, enclose
it in an envelope with your check or money order in either Canadian or U.S.
dollars OR Pounds Sterling (see note below), payable to Liberation
Enterprises.  See the order form below for pricing, applicable taxes
(Canadian residents only) and shipping charges.  Mail your order to:

	Liberation Enterprises
	3091 Eglinton Ave. E., Suite 602
	Scarborough, Ont., CANADA  M1J 2G1  (Check your postage.)

NOTE TO AMERICAN CUSTOMERS: Letter postage from the U.S. to Canada was
$0.40 U.S. (40 cents) at the time this was written.  If you're ordering
from the States please double-check your postage.  Also note that you
needn't have anything special done to your cheque or money order if paying
in U.S. dollars.  Just make it out as usual, as if you were paying a
company in the States.

Thank you for supporting Intellicomm!

──────────────────────────────────────────────────────────────────────────
				    PAYING IN POUNDS STERLING 					
──────────────────────────────────────────────────────────────────────────
Orders from outside the U.S. and Canada may also be paid by personal
cheque, money order or bank draft, made out in an equivalent amount in
pounds sterling, just as you'd pay a company in the U.K.  Just check the
exchange rate for dollars at the time of your purchase, then simply adjust
your payment accordingly.  For example, if at the time of your order the
exchange rate was 1.75 dollars per pound (U.S. dollars are the easiest to
get an exchange rate on, but you can use Canadian $ as well), you would
divide the TOTAL DOLLAR AMOUNT of your order by 1.75, then pay the result,
IN POUNDS, on your cheque or money order.  Please do your work on the order
form in DOLLARS.  Only your cheque/money order should be made out in
pounds.  The cheque needn't be certified, nor have anything "weird" done to
it by your bank.  Just make it out, as usual, as if you were paying a
company in the U.K.

   Intellicomm v2.0 Order Form							   C-9403

					    PLEASE PRINT CLEARLY.

   Name: ________________________________________________________

   Company: ________________________________________________________
		  [Only if you require an Invoice in the Company's name.]

   Address: ________________________________________________________

	 City: _____________________________ Prov/State: ______________

   Country: _____________________________ ZIP/Postal: ______________

   Day Phone: ___________________	 Evng Phone: ____________________
			  [If we have a question about your order.]

   -----------------------------------------------------------------
		  Quantity		  Price  [Canadian or U.S. dollars]
   -----------------------------------------------------------------
		   1 -   9		 $39.95  Compare to the competition!
		  10 -  19		  35.95  (10% off)
		  20 -  49		  33.95  (15% off)
		  50 -  99		  31.95  (20% off)
		 100 - 199		  27.95  (30% off)
		 200 - 999		  23.95  (40% off)
		   1000+			  19.95  (50% off)

   Please rush  __________ copies of Intellicomm at  $_____________

					per copy for a subtotal of  $_____________

			Ontario Residents, please add 8% PST  $_____________

			  Canadian Orders, please add 7% GST  $_____________
			  [Apply GST to the SUBTOTAL]
						  Shipping & Handling* $_____________
						  <------------------
    *If ordering multiple copies and you need only a
    'Master' disk, DO NOT add Shipping. Otherwise:
	 $2	per disk within North America 	TOTAL  $_____________
		 ($20 max)
	 $3	per disk for outside North America
		 ($24 max) 

		PLEASE INDICATE DISKETTE SIZE AND FORMAT.
	  [	  ] 3.5"	disks.   [    ] High Density Okay.
	  [	  ] 5.25" disks.   [    ] Low Density Required.

   Comments/Instructions: _________________________________________

   ________________________________________________________________

   ________________________________________________________________
FIn appreciation for your financial support, as a paying customer you will
gain the following benefits:

■ Make use of the Script Learn mode to have Icom create scripts to automate
most any custom task you can imagine.  Learned scripts can be attached to
function keys to carry out automated tasks at the press of a key, or can be
run as stand-alone scripts, or can even be plugged into automated jobs and
BIFs.  Scripts are not necessary for regular automation but if you have a
special job you want to automate the Script Learn mode will create the
script for you, by just watching what you do!

■ Set your BBS Information Files up to use MULTIPLE File Tagger Catalogs,
instead of having all new files go into the NEWFILES catalog.  For example,
you could have files from different BBS file areas (perhaps a "general"
file area, and an "adult" file area) stored in separate Catalogs, or could
keep separate catalogs for different BBS's, or both.

■ Registration gets rid of all payment reminders, and the random keystroke
at program startup and when you finish running a job.	Instead of
displaying "Copy NOT paid for" at the Main Menu, Job/BBS Directory menus,
your registration number is proudly displayed, which will invariably give
you a good feeling when using the program.

■ Since the registration reminders/random keystrokes are bypassed after
purchase, you can use your registered copy of Intellicomm for *totally*
unattended operation via the /Run: or /Scr: command line options (see
Command Line Options for more details).  For example, you could use a
program launcher to start Intellicomm at certain times on certain days and
perform whatever unattended jobs you wanted, without ever entering a
keystroke -- and without keeping Icom in memory all the time as is the case
with regular job pauses/repeats.  Similarly, many registrants use the /Run:
switch with their favorite menu programs (or DESQview/Windows), and simply
select a menu option such as "Get E-Mail" or "Download Files" to run
Intellicomm in the background, and pick up their mail and/or files with one
keystroke or mouse click!  You can also make effective use of the "Repeat
job" task to execute one or more automated jobs each day at a specific time
(while you're on vacation, etc) without your having to be around to press a
key at the end of each day's run.

■ Registered users can define a new "Base and Startup" area in the main
setup, to have Intellicomm start at a location other than the Main Menu.
The Job Directory, BBS Directory, Script Manager or Terminal can be used as
the startup area if desired.

■ Intellicomm uses a key file method to bypass registration reminders (and
to enable the bonus features), so you don't have to go through us to get
minor upgrades.  Once you have your key file, you can simply obtain the
latest shareware (unregistered) version from your usual source, or from one
of our Distribution Sites, and install it.  When the upgrade finds your
ICOM.REG key file it will automatically register itself!  No hassles, and
no charge.  Note that MAJOR upgrades, from v2.xx to v3.00, for example, may
require a new key file and a small upgrade fee.  More details follow.

■ Direct Mail Order registration gets you a copy of the latest version of
Intellicomm for the release you register.  For example, if you register
v2.00 you will receive the newest v2.xx release, which may contain fixes
and new features which were not available in the release you're using.  Of
course, the key file you're sent with the latest version WILL work with the
exact release you registered as well, so even if you don't like some of the
new features in the version you're sent, and prefer to use the release you
registered, you can do that too.

■ Registration of Icom v2 makes you eligible for an upgrade to the upcoming
Intellicomm for Windows for *$15* or less.  Icom for Windows will most
likely be sold for $40-$50, and this special $15 upgrade will NOT be
available once the Windows version has been released (a similar deal exists
for a future OS/2 version, which I hope to release at the same time as the
Windows version if I can afford the proper development tools).  By
registering the DOS version today you support the development of Icom for
Windows (and Icom for OS/2), and will ensure your entitlement to what is
probably the cheapest upgrade price EVER for a Windows or OS/2
communications program: $15 or less.  The combined price of Icom for DOS,
plus this special $15 upgrade offer means you'll get both Icom v2.xx for
DOS and Icom for Windows or OS/2 -- for less than what you'll pay just for
the *DOS* versions of most other comm. packages!

■ By making the purchase, you're sending a very clear message encouraging
continued development of Intellicomm, as a low-priced shareware product. 
Intellicomm is nowhere near where I want it yet, and I have enough ideas on
paper to keep this product far ahead of the pack for many years to come. 
With your support, your BBSing and the things you do before and after your
BBSing, will become even easier, even more convenient, and even more
enjoyable as each idea is turned into a working Intellicomm feature in
upcoming releases.	Your wildest dreams will come true, if you participate
and register in your financial vote of support.  If not... well, there's
always Qmodem.  (Kidding!)
  
■ Registration also allows you to legally continue using Intellicomm past
the 30-day evaluation period specified in the license.  Though 'legal'
issues should be the least concern when purchasing Intellicomm, or any
shareware product you enjoy.	There are so many other benefits to the user-
supported software concept that I hope you'll make the purchase because you
like the idea, and WANT to support it to ensure that Intellicomm, and the
try-before-you-buy marketing concept it currently uses, continues.

MAJOR UPGRADES:  Major releases (when the number to the left of the decimal
changes from v2.xx to v3.00, and/or when a Windows or OS/2 version is
released) may require an upgrade fee; though that is not always the case,
and v2 was a free major upgrade.  Upgrade fees will typically be in the
$10-$15 range while unregistered users will pay full price.  Major releases
requiring an upgrade fee will only occur when a major re-write of the
program is completed, and significant features are introduced.  All
registered users will receive notification via mail or e-mail when upgrade
fees are involved.	In the case of free upgrades, you can update yourself
by just downloading a regular evaluation copy and installing your key file
as mentioned above, and update notices are not mailed out (though release
notices for all Intellicomm releases are posted on the major BBS message
networks).

Support Intellicomm's continued development, vote for continued use of the
user-supported marketing concept, and receive all the bonus features by
placing your order today!  Please see ORDERING INFORMATION for details.
╠Looking for the latest release of Intellicomm?  We keep all of the
following BBS's up-to-date with the latest releases, for your convenience. 
The files are posted as ICOMxxx?.ZIP (xxx being the version number, and ?
being archives 'A', 'B', 'C', etc.  If the BBS allows batch transfers, just
try to download ICOM*.ZIP or ICOM????.ZIP to find the latest version).  
All sites offer v.32bis (14.4K BPS) or better and all are No Parity, 8 data
bits, 1 stop bit.

NOTE: This list is subject to change without notice.  Please call the Icom
Online Service at 416-261-9583 for an up-to-date list of distribution sites
if you have problems contacting a site listed below.

─────────────────────────────────────────────────────────────────────────
LOCATION	 BBS (*=Free Access)	Phone Number	Operator/Procedure
─────────────────────────────────────────────────────────────────────────
	B.C.  *Virtual Insanity BBS	604-842-6634	Brad Reddekopp
CALIFORNIA *Prime Connection		909-274-9634	Karen Davis
   DENVER  *System Support BBS	303-469-9359	Barry Young/Enter ICOM
							303-469-9389	VISITOR as your name,
							303-469-0978	ICOM as your password.
NOVA SCOTIA *VE1EI BBS			902-868-2475
							902-868-2527
HAMILTON	 *Mohawk College BBS	905-575-2129	Anthony Tekatch
    K.C.	 Sound Advice			816-436-4516	Roy Timberman
 MEMPHIS	 *Don't Panic BBS		901-756-5812	Michel Behna
NEW YORK	 *DaTaNeT 			607-433-6610	Chris Chase
		 SOM Premium			516-536-8723
   PARIS	 *mAIDay			(+1) 44.49.90.07	Len Conrad
  QUEBEC	 Synapse BBS			819-561-4321	Daniel Coulombe
 SEATTLE	 *French Connection 	206-745-3445
ST. LOUIS  *Support U.			314-227-6746	Patrick Grote
 TORONTO	 CRS Online			416-213-6002	Join conference 2 (IBM).
		 *Karico				416-502-3611	Kari Suomela
		 *WESTONIA BBS 		416-241-1981	Dave Smith/Enter ICOM
										VISITOR as your name,
										ICOM as your password.
─────────────────────────────────────────────────────────────────────────
We're looking for more distribution sites outside North America, anywhere
and everywhere: Australia, Africa, Asia/Pacific Rim/Russia, Central
America, Europe, Scandinavia, South America, U.K. ... Bora Bora? 
Distribution sites are automatically kept up-to-date with all GENERAL/non-
beta releases of Intellicomm.  If you run (or know of) a good stable BBS in
a fairly large population center in any of the above areas, please outline
the BBS including the following information:

■ How long the BBS has been operating. IMPORTANT!
■ The phone numbers/area code.
■ The number (quantity-wise) of public access telephone lines.
■ The type and speed of the modem(s) on the public access lines/subscriber
  lines.
■ Whether the Intellicomm files can be made available for 1st time download
  to the general public.  If not possible, outline what the procedure
  would be for the general public to access the files. If your BBS is
  subscription only, please specify the number of active members.
■ The BBS's mailing address, if possible.

Drop the information off in a [C]omment at the Icom Online Service (modem):

 416-261-9583

or to WAYNE DUFF in one of the network conferences listed in
TECHNICAL SUPPORT.	Or mail to:

 Liberation Enterprises
 3091 Eglinton Ave. E., Suite 602
 Scarborough, Ont. CANADA  M1J 2G1

Remember to check your postage.
4Intellicomm technical support is available to both registered and
unregistered users, and is currently done via electronic mail and BBS ONLY. 
We will not answer questions via regular mail (paper), nor is voice
telephone support available as yet.  Use e-mail or drop a message on the
support BBS.  No paper please.

BEFORE using Icom technical support, please:

■ Press [Ctrl-F1] to search the online help for the information you
require.	You'll get much more detailed help here in the online help than
can possibly be provided through technical support.

■ Also see: Troubleshooting, a list of all the introductory/troubleshooting
help topics.  If you have a problem with an automated call, please see the
Debugging Log (in Extensive mode preferably).  The Debugging Log will show
you why any given job task was cancelled, and in Extensive mode it'll also
show you all the BBS prompts that Icom was watching for, as well as any
prompt MATCHES it received from the BBS.  The most common automation
problem is a mismatched BBS prompt (the BIF doesn't match what the BBS is
sending), and the second-most common is an INADVERTENT PROMPT MATCH (a
prompt in the BIF it too vague, and some extranneous text on the BBS caused
Icom to think it had found a certain prompt).  Including punctuation in the
BIF prompt (trailing colons, question marks, etc., that show up in the BBS
prompt but do not show up in the extranneous BBS text) and/or setting CASE
SENSITIVE prompts in the BIF (set "Case-sensitive" on the 1st BIF screen to
YES) will often eliminate an INADVERTENT PROMPT MATCH.  But until you look
at the Debugging Log in extensive mode, you likely won't know what the
problem is (nor will we in most cases, since we can't see the BBS, your
Debugging Log, or your BIF unless you post the capture log, your BIF, and
the ICOM.DBG log in your message).

■ Attempt to recall any unusual changes you made either in the INTELLICOMM
MAIN SETUP, or in your BIF (if having an online problem).  Try changing any
items you DID change back to their default values where possible, and see
if it has any effect.  There's no sense in wasting time and network disk
space asking "where your downloads went" if you turned on "Move old
downloads?" in the main setup and forgot.

■ Recall any unusual hardware you installed recently.	If you use unusual
hardware (a sound card, video adaptor, CD-ROM, etc., not designed for your
computer or one known to have compatibility problems), you can experience
'unusual' problems with software: particularly communications software,
since it must plug itself right into your computer's interrupt structure,
unlike most other software.  Un-install the hardware temporarily, and see
if the problem goes away.  If it does, please contact the manufacturer of
the hardware for possible solutions.

■ Attempt to recall any MEMORY RESIDENT SOFTWARE OR DEVICE DRIVERS you
installed recently, such as a screen blanker, a disk cache, a new mouse
driver, etc.  To eliminate the possibility of a conflict with memory
resident software, and/or to find out which (if any) piece of software is
incompatible: Boot your computer with a plain vanilla DOS boot disk.	You
can create a bootable disk by typing "FORMAT A: /S" (no quotes) from the
DOS prompt.  Then create a CONFIG.SYS file on the disk that contains only a
"FILES=45" statement (no quotes), and an AUTOEXEC.BAT that contains only
your usual PROMPT and PATH statements.	No device drivers or memory-
resident programs should be loaded.  If the problem goes away, you can
start adding in device drivers and memory resident programs back in a
couple at a time.  Eventually, you'll locate the exact piece of software
that is causing (or helping to cause) the problem, and then you can take a
closer look at the way in which you are loading/using that software.	You
may be using an improper or 'risky' command line switch, etc. (such as
QEMM's "stealth" mode, which can cause lockups with some software on some
machines), or an out-dated version of the memory resident software that
isn't compatible with your DOS version or equipment, etc.  But unless you
do the above and identify WHICH piece of software is incompatible with Icom
(or vice versa), we may be completely unable to help you... since we will
in all likelihood be unable to reproduce the problem you're having.

■ For a quick reply, be sure to put the problem into context explaining all
the steps necessary to REPRODUCE the problem, if possible.	If it's an
automation problem, posting a clip from the ICOM.CAP, ICOM.USE and/or
ICOM.DBG files in your message will make for a swifter answer (these files
can be found in the \ICOM\CAP directory or by accessing "Review Session
Captures" from the Icom main menu).  A "picture" (which is what the above
files provide us with) is often worth a thousand words.  Without detailed
information as to how you ARRIVED at the problem, it can be extremely
difficult to provide answers given the number of user-configurable settings
as Intellicomm has, and the number of different ways it can be (and is!)
used.

CONTACTING TECH. SUPPORT
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Network mail should be addressed to WAYNE DUFF:

	Internet: wayne.duff@westonia.com
	FidoNet : 1:250/636
	BBS	   : 416-261-9583

There are also Intellicomm technical support conferences on the following
BBS message networks (please read on if you don't have access to these
networks):

	EchoNet
	GlobalLink
	NorthAmeriNet/NA-net
	RelayNet/RIME
	SmartNet
	U'NI-net

TIP: If you are not familiar with BBS message networks, please see the "BBS
MESSAGES/MESSAGE NETWORKS" section in the document BBSTUTOR.DOC, included
with Intellicomm.  It will get you up to speed with network mail quickly.

Note that the conference/forum might also be called "Liberator", or
"Liberator Tech. Support" (a previous product ... If you get a chance,
please ask your Sysop to change the conference name to "Intellicomm
Support" if it's called "Liberator".  The conferences were officially
renamed over a year ago).

IMPORTANT: It's possible, if not likely, that your Sysop does pick up one
of the above message NETWORKS, but does not pick up the Liberator/
Intellicomm CONFERENCE as yet.  This is quite common, and most BBS
operators do not pick up a conference they're unfamiliar with unless
someone on the BBS requests it.  If this is the case just leave a [C]omment
to your Sysop asking him or her to pick up the Icom conference for you. 
IT'S NOT UNUSUAL AT ALL TO MAKE SUCH A REQUEST, it's the ONLY way to get
the conference, and it'll only take your Sysop a minute to add it for the
next mail run.

If you can't gain access to an Intellicomm conference, locate a BBS that
carries any of the following message networks:

	EchoNet
	FidoNet
	GlobalLink
	ILink
	Intelec
	NorthAmeri-Net
	RelayNet/RIME
	SmartNet
	UN'I-net

You should be able to find a BBS carrying one of these networks, just about
anywhere.  You must make sure you post your message in a conference/forum
that I monitor though: I don't monitor all conferences.  First look for an
Intellicomm conference (one may have been added since this help topic was
prepared) then look for the Communications or Shareware conference
(available on all networks above) if you can't find anything else.  I
monitor every conference I'm likely to get mail in (communications and
shareware-related) on all of the above networks.	Please make sure you
spell my name correctly (Wayne Duff) or I'll likely miss your message.
▌The following files/directories make up Intellicomm.  Files preceded by
three letters and a backslash (\) signify an \ICOM subdirectory (e.g.
BIF\*.BIF means \ICOM\BIF\*.BIF). Files marked with ≡ are created by the
program as needed:

ICOM.EXE		The executable.
IN-PIF.DVP	This file contains all the proper settings needed to use
			Intellicomm with DESQview (can be deleted if you don't use
			DESQview).  See DESQview for details.
ICOM.PIF		Program Information File for Windows; contains all the
			proper settings needed to use Intellicomm with Windows 3.1
			(can be deleted if you don't use Windows).
ICOM.REG		[Registered users only.]  This file contains your
			registration number, and causes regular evaluation copies of
			Intellicomm to bypass the registration reminders/random
			keystrokes at program startup and after automated jobs, and
			also enables the registered user bonus features (see
			Registration Benefits for details).  This file must NEVER be
			re-distributed to others.  The serial number in the file is
			connected to the purchaser's name/address and can be traced
			directly back to the purchaser if found to be illegally
			distributed, so please BE CAREFUL with this file.
ICOM.HLP		The main online help file.
SCRIPT.HLP	Online help with scripts.
ADDON.HLP 	Multitasking Intellicomm topics, and useful add-ons.
ICOM.INI≡ 	Holds the main setup information.
ICOM.BDX≡ 	BBS (BIF) Directory index.
ICOM.PWD≡ 	Holds your BIF passwords (encrypted).
ICOM.JDX≡ 	Job Directory index.
ICOM.DAT≡ 	Job data file.
ICOM.STA≡ 	Statistics file, holds # times connected, total online time,
			the average speed of your file transfers (for use in the
			File Tagger to estimate transfer times offline), and all the
			stats you see at the Main Menu.  If you delete this file,
			all the stats are reset to 0.
BBSTYPES.DAT	Used by BIF Learn this text file holds BBS software
			identification strings (e.g. PCBoard (R) v15), followed by
			the filename of the BIF template (e.g. PCB150) that holds
			the default prompts and responses for that BBS type.  If you
			create new BIF templates yourself, you can add support for
			these new BBS types to BIF Learn by editing BBSTYPES.DAT and
			adding the new template name.  See the comments in
			BBSTYPES.DAT for details.
DSZ-D.BAT 	Batch files to interface Chuck Forsberg's "DSZ" 
DSZ-U.BAT 	protocol program (external X/Y/Zmodem) with Icom.  See the
			REMarks in DSZ-D.BAT for instructions.
HSLINK.BAT	Batch file to interface Sam Smith's "HS/Link" bi-directional
			protocol program with Icom (upload and download at the same
			time).  See the REMarks in HSLINK.BAT for instructions.
POST*.BAT 	Optional "post-job" batch files.  Please see 
			Automation in Detail, and the REMarks in the POST*.BAT files
			for details.
*.KWD≡		These files hold the various Tagger Keywords you define. 
			REPLACE.KWD (fix up file comments) and STRIP.KWD (strip
			garbage from file comments) are included with Intellicomm. 
			You can modify these files, and/or create other types of
			keyword files, using the Tagger Keywords main setup screen.
HELP.BBS		online help for REMOTE users of Host Mode.
BIF\*.BIF 	BBS Information Files and BIF templates (the "BBS/Host Name"
			item is enclosed in square brackets, if the BIF is a
			template).  These are the BBS systems displayed to you when
			you enter the BBS Directory in Intellicomm.
BIF\*.BTF 	BBS Time Bank systems known to Icom (Bank Templates).	These
			are the various message systems displayed to you when you
			select "Message Type" in the BIF Editor (also used by
			BIF Learn) to set Icom up for automated mail runs.
BIF\*.MTF 	BBS Message systems known to Icom (Message Templates). 
			These are the various bank systems displayed to you when you
			select "Bank Type" in the BIF Editor (also used by
			BIF Learn) to set Icom up for automated time bank
			transactions.
CAP\*.CAP≡	Captured data from online sessions.
CAP\*.DBG≡	The Debugging Log and backups.
CAP\ICOM.USE≡	The Usage Log.
DBF\*.*≡		File Tagger Catalogs (dBASE databases).  Each catalog has a
			.DBF (database file) .DBT (memo file holds extended file
			descriptions) and three .NDX (index) files.
DOC\*.DOC 	Please see Documentation.
GET\*.*≡		The Download Directory (contains files you download manually
			and automatically).
LST\*.NEW 	Captured/extracted BBS new files listings.
SCR\*.SCR 	Pre-programmed scripts.
SND\*.*≡		The Upload Directory (where Icom looks for files when you
			perform an upload).

See also:
	Deleting Icom Files
÷You 'can' delete the following files and still run Intellicomm.	But you
should keep a backup of any files you delete in case you change your mind
and want to bring a connected feature back at some point in the future.

INSTALL.EXE	Needed only for the initial installation.  Can be deleted
			immediately after the installation is performed.
README.1ST	Installation/introductory information.	Can be deleted
			immediately after the installation is performed.
FILE_ID.DIZ	Contains a description of Intellicomm (may or may not have
			been included in the Icom archives).  BBS's look for
			FILE_ID.DIZ and use the description inside, if the file is
			included in distribution archives.
IN-PIF.DVP	Contains all the proper settings needed to use Intellicomm
			with DESQview (can be deleted if you don't use DESQview).
ICOM.PIF		Program Information File for Windows; contains all the
			proper settings needed to use Intellicomm with Windows 3.1
			(can be deleted if you don't use Windows).
ICOM.HLP		Registered users only: ICOM.HLP can be deleted when you
			become an expert and no longer need this online help system. 
			If you delete this file (which contains the ordering
			information) in the UNREGISTERED version, Icom will not run.
SCRIPT.HLP	online script and Script Learn help can be deleted if you
			are not interested in scripts.
ADDON.HLP 	holds the Multitasking Intellicomm topics, as well as a list
			of useful add-ons.	Even if you don't use a multi-tasker
			(Windows, etc) at present, you may in the future.  If you
			delete this file, you should keep a backup on floppy.
DSZ-D.BAT 	Batch files to interface Chuck Forsberg's "DSZ" 
DSZ-U.BAT 	protocol program (external X/Y/Zmodem) with Icom.  Can be
			archived to floppy if you don't use DSZ (you may want to in
			the future, so keep these files handy).
HSLINK.BAT	Batch file to interface Sam Smith's "HS/Link" bi-directional
			protocol program with Icom (upload and download at the same
			time).  Can be archived to floppy if you don't use HS/Link
			(you may want to in the future, so keep this file handy).
POST*.BAT 	Optional "post-job" batch files.  Please see
			Automation in Detail, and the REMarks in the POST*.BAT files
			for details.  All of these files "can" be deleted, but you
			should know what they can do for you before you delete them.
BIF\*.BIF 	This directory holds all your BIFs, PLUS several BIF
			"templates" which Icom uses to create a new BIF for various
			BBS types.  Use the File Manager and File Viewer to look at
			the .BIF files and delete any BIF templates that you don't
			currently need.  The templates can be identified by looking
			at the second line of the BIF file:
					desc="[PCBoard v14.5]"
			Any BIFs with a description in square brackets is a TEMPLATE
			and can be deleted if you don't call that type of BBS. 
			Further, Intellicom does not use the templates AFTER you
			have set your BIFs up: it uses them only for the initial BIF
			setup (a starting point for a new BIF).
BIF\*.BTF 	Similar to the above, you can delete any bank
BIF\*.MTF 	or message template files (BTF's/MTF's) you don't anticipate
			needing.	The only consequence is that when you select "Bank
			Type" or "Message Type" in the BIF Editor (or BIF Learn),
			you'll have fewer systems to choose from.  Note that these
			files are not needed AFTER you set your BIFs up.	If you
			only have a few BIFs, you can first set up the proper
			Bank/Message systems (which will import the MTF or BTF
			settings into the BIF itself), and then can delete all the
			BTF/MTF files with no ill effects as far as automation goes.
CAP\*.CAP 	Capture files are for your information only and are not
			needed by Icom.  You can limit the number of backup capture
			files Icom keeps on-hand in the main setup, using the
			"Capture File Max" item.   You can also prevent Icom from
			opening the capture file automatically in the main setup,
			via the "Open Capture on Connect?" option (General Settings
			screen).	NOTE: The capture file is often the only way to
			diagnose an automation problem, and it is not recommended
			that you shut off the auto-open on connect if you carry out
			unattended online sessions.
CAP\*.USE 	The Usage Log is for your information only, and can be
			deleted if you don't need it.  If you don't want a Usage Log
			kept, set "Auto-Open Usage Log" to NO in the main setup
			(General Settings screen).
DBF\*.*		These are the File Tagger Catalogs (databases).  Each
			catalog is made up of 5 files: the DBF (database), DBT (memo
			file, holds extended file comments), and three NDX files
			(allows re-sorting, and are also used by Icom for various
			purposes).  If they get too big and you want to free up some
			disk space, but still want to keep SOME of the newer files
			around, enter the Tagger, select "Tools" then "Purge". 
			Follow the bouncing ball to delete whatever records you see
			fit, then use "Pack/Rebuild" to actually free up the disk
			space.  Note that packing can temporarily INCREASE the size
			of the database, since a new database (minus the deleted
			records) is created to pack the files.	If you're
			desperately short on disk space, the Tagger won't be able to
			complete the pack, since it won't have room to create the
			new database.	You can also delete the databases, and the
			Tagger will create them again if/when necessary.	If you
			don't want databases kept at all, enter the Icom main setup,
			change to the "File Tagger" screen, and set "Auto Import New
			Files" and "Keep an Upload Catalog" both to NO.
DOC\*.DOC 	None of these files are "required".  If you keep them on-
			disk in the \ICOM directory, you can view them online
			through the help system or File Viewer whenever needed. 
			They're handy to have around, but if you're short on disk
			space you can archive them to a floppy.
LST\*.NEW 	These are BBS new files listings that have been either
			captured or extracted from mail packets.  The File Tagger
			normally imports these files when found then deletes them. 
			But if you don't use Auto Import New Files, discussed above,
			they'll just sit there and accumulate (the assumption is
			that you're using something else to handle the new files). 
			If you don't want these files extracted from your mail
			packets, enter the Icom Setup, switch to the "Screen/File
			Transfer" screen, and set "Extract NEWFILES in .QWK" to NO.
SCR\*.SCR 	Most of the pre-programmed scripts are included for
			instructional purposes and can be deleted if you don't need
			them.  The exceptions are the *-ON.SCR *-OFF.SCR scripts. 
			These are logon/logoff scripts for Long Distance Services
			(PC Pursuit, and Inet) and if you use long distance
			services, you must keep either PCP-ON.SCR/PCP-OFF.SCR (PC
			Pursuit) or INET-ON.SCR/INET-OFF.SCR (iNet) around.

See also:
	Intellicomm Files
CMost of the documentation for Intellicomm is supplied in the *.HLP (online
help) files.  The advantage of online help over printed manuals is that
Intellicomm can flip you to the right "page" in the manual, as you move
around the program and do things.	When you want information, just press
the [F1] key and the relevant documentation will be displayed.  A further
advantage is the Help Link concept, which allows you to quickly look up
information on a given topic, without losing your current page (just press
[Alt-F1] to go back to where you were before reading the link) and without
having to look up page numbers in a manual index.

Some of the documentation, however, is provided in *.DOC files, pre-
formatted and ready for printing and/or viewing through the File Manager or
this help link (if the files are installed in the \ICOM directory you can
simply select the document filename as a Help Link below):

AUTOICOM.DOC	Detailed information regarding Intellicomm "auto-BIFs".
BBSTUTOR.DOC	BBS tutorial.
HOST.DOC		Host Mode documentation.
ORDER.DOC 	Intellicomm ordering information and order form.
SCRIPT.DOC	Script language documentation.
SCRTUTOR.DOC	Script language introduction/tutorial.
UPGRADE.DOC	Information for those who upgraded from Intellicomm v1.00 or
			v0.9x.

To print a .DOC file, simply ready your printer then "COPY" the file to
your printer with the command:

 COPY DOCFILE.DOC PRN

[DOCFILE.DOC being the .DOC file you wish to print.]

See also:
	Intellicomm Files
	Deleting Icom Files
	Help on Help  (reading a .DOC file from the help system)
╞This online help system allows you to search the complete help system (all
.HLP files) for specific information.  To use Search, just press [Ctrl-F1],
or click on the [Ctrl-F1] at the bottom of the screen with your mouse, then
enter one or more keywords (or portions of keywords) you want to search
for.

All help topics will be searched for the text you enter, and those topics
that contained the text will then be displayed.  Case is not significant in
the search string (bif, BIF, and Bif are considered the same).

If you wish to search for a specific word, precede and follow the search
string with spaces.  E.g. " PUT " (without the quotes... just enter the
spaces) would match only the word PUT and not the words PUTS, COMPUTER,
etc. (which do contain the letters PUT).  If you don't enter spaces, any
word in the help system containing the *portion* of the string you enter
causes a match.  This is useful in many cases, since it allows you to
search for both singular and plural cases of a given word.	For example, if
you enter "BIFs" when asked what to search for, only plural cases cause a
match.  Normally you'll just use the singular case of the word (BIF) so
you'll get a match for both single and plural occurrences of the word.

Lines are searched across as well, so if the help file displays "BBS
Information File" (with the text broken onto two lines), you'll still get a
match assuming you entered "BBS Information File" as the search string.

TIP:  To access the last search results at any time, press [Shift-F1] to
display the help index (assuming you're in the help system; if not you must
first press [F1]), then select Search Results from the index.  Search
results are saved on-disk in the file \ICOM\SEARCH.HLP, so the previous
results are saved from one Intellicomm session to the next, which
effectively gives you your own custom help "index" to use.	To clear the
search index, either perform another search with [Ctrl-F1] or delete the
file \ICOM\SEARCH.HLP.
The Text Editor Menu is accessed by pressing [Alt-Z] or by clicking your
mouse on the status line at (where it displays "Alt-Z for Menu") while
viewing a file.  To operate the Text Editor Menu, press the left/right
arrow keys (or the bold hotkey) to access the sub-menu of interest (File,
Search, Keyboard Buffer, Options, or eXit), then use up/down arrow (or the
bold hotkey) to select an action from the sub-menu.  Press [Esc] or click
your right mouse button to close the Text Editor menu.

You'll also notice "hotkeys" listed next to each item, which can be used to
select the item directly without calling up the menu.	For example, to save
the current file to disk just press [Alt-F].

File
▀▀▀▀
New/Clear 	clears the current contents of the editor.  If the current
			file has changed since it was last saved to disk, you are
			given the option to save it before clearing.

DOS/Open		accesses the File Manager, allowing the usual DOS-related
			options (copy, ren/move, delete files, etc).  To load a file
			into the Text Editor, hilight the file and select "Edit".

Save 		saves the current file using the same filename.

Save as		saves the current file using a different filename.  NOTE: If
			you mark a block (see Edit below) before selecting "Save
			as", only the block is saved to disk.

Print		is used to print the current file.  Turn your printer on
			BEFORE selecting this item.  [Alt-P] can be used to Print
			without going through the menu.  See Printing Problems if
			you have any problems getting a printout.  NOTE: If you mark
			a block (see Edit below) before selecting "Print", only the
			block is printed.


Jump to DOS Shell  temporarily go to the DOS command prompt.

Exit Editor	exit the editor.  If the current file has changed since it
			was last saved to disk, you are given the option to save it
			before exiting.

Edit
▀▀▀▀
Undo 		restores the last block that was deleted with the Edit|Clear
			or Edit|Delete (see below).

Mark Block	an alternate way of marking blocks.  The usual way to mark a
			block is to hold down a [Shift] key while pressing a cursor
			key (up, down, left, right, PgUp, PgDn, etc).  If you find
			this to be awkward, you can also mark blocks by selecting
			"Mark Block" (press [Alt-B]), then moving the cursor to mark
			the block without holding down a [Shift] key.

Cut Block 	saves the currently marked block to an internal editor
			clipboard, then deletes the block.

Copy Block	saves the currently marked block to an internal editor
			clipboard WITHOUT deleting the block.

Paste Block	inserts the contents of the internal editor clipboard (Cut
			Block/Copy Block) at the current cursor position.

Delete Block	deletes the currently marked block (end-of-line characters
			are also deleted).

Clear Block	clears the currently marked block (end-of-line characters
			are not deleted).

Search
▀▀▀▀▀▀
Find 		is used to search from the current cursor position either in
			an upward direction towards the top of the text, or a
			downward direction towards the end of the text.  After
			selecting "Find" enter the text you want to search for, then
			select Upwards or Downwards to search in the direction you
			desire.  If the string is found, the editor automatically
			positions the cursor to the located text.

Find again	is used to continue searching for the same string you
			entered in the last "Find", in the same direction.  Press
			[Alt-A] (A for Again) to select Find Again without going
			through the menu.

Goto line 	positions the cursor to a specific line number in the
			current text file.

Keyboard Buffer
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
BLOCK to Key Buffer - Add SPACE  copies the currently marked block (first
			line only) to the Keystroke Buffer, and adds a space
			character after the text.  This item is intended to be used
			in the Scrollback Buffer to mark filenames and paste them in
			the Keystroke Buffer for later use in downloading files.  

BLOCK to Key Buffer - Add CR	copies the currently marked block (first
			line only) to the Keystroke Buffer, and adds a carriage
			return character after the text.  This item is intended to
			be used in the Scrollback Buffer to mark filenames and paste
			them in the Keystroke Buffer for later use in downloading
			files.  

Options
▀▀▀▀▀▀▀
Insert		toggles Insert/Typeover mode.

Line wrap 	toggles line wrap mode.

Tabs 		sets the editor [Tab] positions.

eXit
▀▀▀▀
Back to document  exits the Text Editor Menu.

Exit editor	exit the editor.  If the current file has changed since it
			was last saved to disk, you are given the option to save it
			before exiting.
xThe File Viewer Menu is accessed by pressing [Alt-Z] or by clicking your
mouse on the status line at (where it displays "Alt-Z for Menu") while
viewing a file.  When the menu pops up, you'll notice "hotkeys" listed next
to each item, which can be used to select the item directly without calling
up the menu.  For example, to search the current file for specific text
just press [Alt-F].

Find 		is used to search from the current line (top of screen),
			either in an upward direction towards the top of the text,
			or a downward direction towards the end of the text.  After
			selecting "Find" enter the text you want to search for, then
			select Upwards or Downwards to search in the direction you
			desire.  If the string is found, the viewer automatically
			positions the line where the text was found at the top of
			the screen (unless the text is on the last screen; in which
			case it may end up further down).

Find Again	is used to continue searching for the same string you
			entered in the last "Find", in the same direction.  Press
			[Alt-A] (A for Again) to select Find Again without going
			through the menu.

Print		is used to print the current contents of the Text Viewer. 
			Turn your printer on BEFORE selecting this item.	[Alt-P]
			can be used to Print without going through the menu.  See
			Printing Problems if you have any problems getting a
			printout.

Ruler		displays a numeric ruler at the top of the screen.  This is
			mainly of use when viewing BBS .NEW File Listings (normally
			captured to the \ICOM\LST directory).  Intellicomm BBS
			Information Files (BIFs) require the positions of various
			items in BBS files listings, such as where the filename
			starts, where the date starts, etc., so that the
			File Tagger can import these lists properly.  Use the ruler
			to obtain the proper positions whenever necessary.  To turn
			the ruler off, just select Ruler again from the menu; [Alt-
			R] can also be used to toggle the ruler on and off.

Exit Viewer	exits the Text Viewer (or help system; the online help also
			uses the Text Viewer to display help text).	You can also
			exit by pressing the [Esc] key.
âDue to the large number of new features introduced, it wasn't feasible to
place the upgrade information for v2.0 in this online help file.  All the
details are included in a separate file: UPGRADE.DOC (you can select this
help link now to read it, if the file is installed in the \ICOM directory).

As a separate document, this also allows you to DELETE the file after
you've read it.
╚The main setup allows you to customize nearly every aspect of Intellicomm
to suit your equipment and your personal preferences.	Setup is accessed
via the Main Menu, the Job Directory Tools menu, or the Terminal Menu Tools
menu.

Once in the main setup, you'll be presented with a box menu containing the
options listed below:

	User Settings
	General Settings
	Filenames and Paths
	Screen/Color Settings
	Debugging Log Settings
	Sysop Settings
    ────────────────────────
	Terminal Settings
	Dialer Settings
	File Transfer Settings
	External Protocols
	Comm Port Settings
    ────────────────────────
	File Tagger Settings
	Tagger Keywords
    ────────────────────────
	Load a New Setup File
	Exit Setup

To access a setup screen, simply hilight it and press [Enter], or move the
mouse cursor and click.	When you're finished on a particular settings
screen, press [Esc] (or click the right mouse button) to return to the main
setup menu: Any changes you made on the screen will be preserved.  Note
that NOTHING you do while in the main setup is actually saved to disk. 
Only when you select eXit the Intellicomm Setup menu do you have the option
of saving your changes to disk.  So you're free to play around and do
whatever you like in the setup menus...  If you press [Esc] when asked for
a filename to save to on eXit, any changes you made will be discarded, and
your original settings will be restored the next time you start
Intellicomm.

The User Settings allow you to define common personal information, for
later use when (a) setting up new BIFs, (b) signing on to a new BBS. 
Intellicomm "Auto-BIFs" (see ICOMAUTO Easy Setups for information) will
prompt for your logon name, sometimes your date of birth, etc.  And if
you've defined this information here in the User Settings, Icom will be
able to offer you the proper default.  You can also have Icom send any of
the user settings to the BBS when online, by pressing [Alt-1] through [Alt-
0] (means hold down the [Alt] key, and tap key [1] through [0] on the top
row of the keyboard).

Note that the actual format you use when entering these items depends
largely upon the TYPE of BBS you call most frequently.  You should enter
the data here in the User Settings exactly as you'd enter it if you were
online at a BBS (noting that ^M signifies [Enter], ^[ signifies [Esc], and
~ causes a 1 second delay.  You can have multiple commands sent with a
single User Setting by using ^M).

All of the items on this setup screen are self-explanatory, except perhaps
the "BBS Password", and the two "General Use" slots.

You'll note that you cannot enter a BBS Password on the User Settings
screen, and this is because it is good practice to use a DIFFERENT password
for every BBS you call.	Thus, instead of defining a 'global' password to
be used everywhere, you instead should define separate passwords in each
BIF (on the Logon screen).  Once you've enter a password in a BIF, Icom
will attempt to perform an auto-logon for you, after using the Dialer (for
a manual online session), and later during your online session if you are
asked to enter your password again, you can simply press [Alt-2].

The two "General Use" slots can be used to store any information you find
yourself entering over and over manually at BBS's.  They could be used to
store a credit card number and expiry date (be careful with this if others
have access to your machine though!), or even just some tedious BBS
commands you must enter frequently at your favorite BBS.
JSee Debugging Log for general information regarding the log.

Debugging Level
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
When set to 'Normal with Immediate Disk Writes' (the default) status and
error messages are stamped in the log (including file transfer protocol
status and error messages) as well as general information regarding
automated jobs.  This debugging level is mainly used to aid us in
TECHNICAL SUPPORT as it presents a fairly good overview of what took place
without us having to ask myriad questions.  'Normal' level can also help
you to diagnose problems yourself: particularly regarding job tasks that
you REQUEST but that are not carried out by Intellicomm when online: the
reason Icom cancelled the job task will be shown in the log.

If set to 'Extensive' (either with or without buffered disk writes)
information regarding BIF prompts Intellicomm was watching for, as well as
responses it sent to the BBS as well as all menu items selected, are
written to the log.  This level is not meant to be used regularly as it
will slow down your online jobs with many disk writes: it is meant to be
used when you have an automated job problem of some sort (which is almost
always due to BIF setup error and one or more prompt mismatches) that you
cannot solve.

A common problem with BIFs, and a problem that can be difficult to solve,
is one of extraneous BBS text matching a BIF prompt, and causing
Intellicomm to perform some action or response due to the (seeming) prompt
match.  For example, if the word "Password" showed up in the BBS logon
news, and all you had defined as the Password prompt in the BIF was this:

 ║ Password Answer> <Confidential>    Password . . . . Password« 	   ║
											────────
then Intellicomm would RESPOND to any appearances of the word 'Password' in
the logon bulletin, and indeed throughout the automated session.   By
setting the debugging log to 'Extensive' whenever you run into any oddity
during an automated job, you can quickly see exactly which BIF prompts Icom
was watching for at a given time, and also which prompts MATCHED any BBS
text that came in.	Using the 'Password' example above, you could quickly
see from looking at the debugging log that Intellicomm had matched on the
word 'Password' in the logon news... and could correct the situation by
defining more UNIQUE text in your BIF such as 'Password:' (using
punctuation).

Extensive with Buffered Disk Writes
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Enables the Extensive logging level and allocates a 4 Kilobyte memory
buffer for the disk log: information is not written to disk until the log
is closed (you exit Intellicomm or access the File Manager) or the memory
buffer fills up.  It is meant to be used when you are not running into a
lockup or other external problem that might cause a portion of the log to
be lost.	Buffering will speed up Extensive debugging log writes
substantially, but will be of no use if you're running into a lockup, as
you may lose up to 4 Kilobytes worth of log information.

Debugging Log Filename
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If blank, the debugging log is disabled entirely.  If only a filename is
specified (no D:\PATH\) then the same D:\PATH\ used by the "Capture Log" is
assumed (see the main setup Filenames and Paths screen).  The Capture Log
is normally kept in the \ICOM\CAP\ directory, so if only ICOM.DBG is
specified as the filename, the debugging log uses \ICOM\CAP\ICOM.DBG.  If
you specify a full D:\PATH\FILENAME.EXT the file will be placed in the
drive/directory you specify: make sure you create the directory if it
doesn't exist: it will not be created for you.

Log Renumber Total
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Controls both whether you want Debugging Log maintenance performed at all
(set to 0 for no maintenance and the Log will be appended to) and if so,
how many backup Logs you want to keep around.  Debugging Log Maintenance is
performed only when ICOM.EXE is started and thus a single ICOM.DBG file
shows everything ICOM.EXE did from start to finish.  It is done this way
mainly to aid in technical support: Often if problems do occur, they ONLY
occur after a certain series of events have taken place.  And while you may
overlook this series of events when reporting the problem,	the debugging
log, when in 'Extensive' mode, overlooks very little.	Thus you may be
asked to post an Extensive-mode copy of the relevant ICOM.DBG log in a
message if/when you require technical support.
0Password Access Key
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If you enter a password here, Intellicomm does not let you "Edit" (look at
or change) any of the passwords defined in your BIF unless you enter the
proper Password Access Key.  Note that the Password Access Key is only
prompted for ONCE per Intellicomm session.  So if you're in the habit of
leaving Icom in memory all the time, you'll gain little protection by
defining a Password Access Key, since it won't be asked for again after you
enter it the first time.  The solution: exit Intellicomm when you're
finished with it (or have your job Exit to DOS automatically).

Base and Startup Area
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This allows you to define a new startup area for Intellicomm.  By default,
Icom starts at the Main Menu, but if you find yourself constantly switching
to another area at program startup, such as the Job Directory,
BBS Directory, Terminal, or Script Manager, you should change this setting
and have Icom start there instead.  Note that this also serves as your
"base" area, which is where Intellicomm returns after automated jobs and
various other tasks.

TAB / Shift-TAB moves the
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
At a menu with multiple hilight bars and multiple columns (such as the
Job Directory, BBS Directory, Script Manager, etc), by default, the [Tab]
and [Shift-Tab] keys move the bottom hilight bar, and the [Left] and
[Right] arrow cursor keys move the top hilight bar in the large window.  If
you'd rather switch it around, and have [Left] / [Right] move the BOTTOM
hilight, and [Tab] / [Shift-Tab] move the TOP hilight, set this item to
"Top Hilight".

Put Overlays in XMS/EMS
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Controls where Intellicomm attempts to put its most frequently-used
overlays.  Overlays are parts of Intellicomm that are swapped in and out of
memory (to reduce overall memory usage) as they are needed.  The
Main Menu is an overlay, and actually most all areas of Intellicomm (except
the Terminal) are stored in overlay format... and are not loaded into
memory unless needed.  You should leave this set to "Either" (use either
XMS or EMS memory... whatever is available, if any), unless you experience
problems.  If you do not have enough EMS or XMS memory available for
loading the overlays, Intellicomm will run much slower than it would
otherwise.

Enable Swapping
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This controls what Intellicomm does with itself (if anything) when
accessing external programs such as your Mail Reader, Archive Viewer, or
the PRE/POST job batch (.BAT) files, or when performing a DOS Shell.
"Swapping" means that before accessing the external program, Intellicomm
can swap itself OUT of base memory, to either EMS/XMS 'high' memory, or to
disk, leaving the external process with all available memory (minus just
about 200 bytes, which Icom keeps resident to swap itself back IN, when the
external process completes).	Please see DOS Shell for a complete
explanation of the options available for this setting.

Release Time Slices
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If set to "Yes", and if either DESQview, OS/2, or Windows is detected at
program startup, Icom will release idle time back to the operating system. 
"Idle time" means that no COM port input/output, keystrokes, or mouse
clicks are pending.  A "time slice" is a period of time the operating
system gives to each open application.	The period of time given to each
open application is fixed, and unless the slice is 'released' by
Intellicomm, the entire period of fixed time allotted in the slice is used
up whether anything is happening or not.  The advantage of setting this to
"Yes" is that Icom, while running in the background, will allow your
foreground applications to execute more smoothly if nothing is happening. 
The disadvantage is that multitasking operating systems do not tell
Intellicomm about "pending" (buffered) COM port activity, sometimes leading
Icom to believe that there's nothing to do (releasing its time slice) when
in fact there may be much to do.

If set to "No", idle time is not released back to the operating system
while Intellicomm is online, eliminating the possible disadvantage
mentioned above.  But idle time will still be released while Intellicomm is
offline.

If you use DESQview, OS/2 or Windows and you experience problems online
(either when Icom is in the foreground or the background), such as missing
characters in terminal mode, or excessive file transfer errors, you should
set this item to "No" as your first attempt to eliminate the problem.  If
that doesn't work, see Multitasking Intellicomm for more help.

Drop RTS on Disk I/O
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If Yes, and if Hardware Flow Control on the Terminal Settings screen is set
to CTS/RTS, this causes Intellicomm to re-vector interrupt 13h (disk
input/output) to an Icom routine that lowers the Request To Send (RTS) line
during disk activity, when the COM port is in use.  Lowering RTS causes
modems that use CTS/RTS flow control to stop sending data to the COM port. 
If this is not done data can be lost during disk activity; particularly if
a disk cache is in use.	Interrupt 13h is re-vectored to ensure that disk
writes by caches (DOS's SMARTDRV, etc) which use DELAYED disk writes, are
intercepted.

If you encounter lost characters from BBS's in terminal mode, and/or
excessive protocol errors during downloads, try turning this option ON to
see if it solves the problem.  If you encounter lockups (even AFTER running
Intellicomm) after turning it on, turn this item back OFF, then re-
configure your disk cache and disable the 'write behind' buffer.  Example
for SMARTDRV:

rem ICOM-S.BAT
SMARTDRV C
ICOM.EXE %1 %2 %3 %4
SMARTDRV C+

With DOS's SMARTDRV disk cache, if you specify a drive letter but do NOT
follow it with a plus sign (+) read caching is still enabled (which rarely
causes communications problems, and increases disk performance
significantly) but WRITE CACHING (which does cause communications problems,
and introduces many other potential problems system-wide) is DISABLED.  If
you follow the drive letter with a plus sign, both read and write caching
are enabled.

Mouse Settings
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
When selected, this option gives you the mouse settings menu, which allows
you to define the Mouse Mode and mouse cursor speed (relative to actual
mouse movement).  If the Mouse Mode is set to "None", then Intellicomm
mouse support is completely disabled.  If set to "Lefthanded", everywhere
you'd normally press the "Left" mouse button, you'll instead press the
"Right" mouse button, and vice versa.  It assumes that the mouse is on the
left side of the keyboard (your left hand), and that you'll use your left
index finger on the right mouse button for most of the clicking.

The mouse speed allows you to either speed up, or slow down the movement of
the mouse cursor (on-screen) relative to mouse movement (on-desk).  If you
find that you run out of desktop space before getting the cursor where it's
going, then you'll want to DECREASE both the Up/Down and Left/Right numbers
(thus speeding up the mouse cursor).  If you find that you move the mouse
an eighth of an inch and the cursor goes flying right across the screen,
you'll want to INCREASE the Up/Down and Left/Right numbers (thus slowing
down the mouse cursor, relative to movement).  Experimentation is the only
way to get the "right" settings for your particular mouse and mouse driver.

Use PATH to Locate Files
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
When looking for a file (usually in the case of a file upload), Icom
normally does not search the DOS PATH, since it can sometimes take a fair
bit of time to do so... and since it can sometimes lead to finding a
PRIVATE file that you never intended to be uploaded in the first place. 
However, if you do want Icom to search the DOS PATH when it can't find a
file its looking for, set this item to "Yes".

File Renumber Mode
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines what method Icom uses to renumber both the capture file
(\ICOM\CAP\ICOM.CAP) and Message/Reply packets.  "Renumbering" allows you
to keep a few backup files on-hand (defined below), and it simply renames
the existing file, putting numbers in either the filename or extension to
rename it.  If you elect to place the numbers in the "Filename", ICOM.CAP
becomes ICOM01.CAP when the capture file maintenance is performed.  If you
elect to place the numbers in the "Extension", ICOM.CAP becomes ICOM.C01. 
The same applies to Message and Reply packets, when their maintenance is
done.

Usage Log Renumber Total
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Controls both whether you want Usage Log maintenance performed at all (set
to 0 for no maintenance and the Log will be appended to), and if so, how
many backup Logs you want to keep around.  Usage Log Maintenance is done
with the Capture Log Maintenance, when "Dial" is selected from the
BBS Directory (in manual mode), and during the pre-job setup (in automated
mode, after you select "Run").

Capture Renumber Total
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Same as the Usage Log setting above, but for the default Capture Log.

Message Renumber Total
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Controls how many (if any) backup mail packets you want to keep handy. 
Message Packet Maintenance is done each time you execute an automated job
to pick up a NEW mail packet.  If set to 0, Icom deletes the existing
message packet just before requesting the new mail at the BBS.

Reply Renumber Total
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Controls how many backup message reply packets you want to keep handy.  You
must keep at least 1 (though you're free to delete it with POSTJOB.BAT or
POSTJOB.SCR if you like).  Reply Packet Maintenance is performed after the
reply packet is successfully uploaded to the BBS message system.  I.e.  the
"Replies Accepted" prompt (defined on the BIF "Message" screen) must be
received from the BBS message system, and it must match what you've defined
in the BIF.

Auto-Open Usage Log
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If set to "Yes", Icom automatically "opens" the Usage Log at program
startup.	If the Usage Log is closed, no usage data is written to the file. 
If you set this item to "No", you'll have to manually open the Usage Log
via the Terminal Menu, when you want usage stats kept.

Open Capture on Connect
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines whether Icom opens the Capture log when it connects to a BBS. 
You can later pause or close Capture with the [Alt-L] hotkey or via the
Terminal Menu.  It's best to leave this setting turned on: By default, Icom
will limit the size of the file (via Capture File Maintenance described
above) so you don't end up with a massive capture log on-disk.

Stamp Date/Time Cap Open
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If turned on, Icom automatically stamps a line such as this whenever it
opens the Capture log:

==<< YY-MM-DD HH:MM:SS BIFID - BBS/Host Name >>=========================

This is sort of a "Usage Log" and capture file all in one, showing you the
date, time, and location of the connection.

Sound
▀▀▀▀▀
If off, neither the pager (below) nor [Ctrl-G] (BELL characters from the
BBS) are active.  In short, Icom won't make a peep if Sound is turned off.

Pager
▀▀▀▀▀
Used only during manual mode, this setting determines whether Icom sounds
the pager both when it connects to a BBS, and after file transfers -- in
MANUAL mode only.  In Auto mode, since there's no reason to "page" you, the
pager is not sounded after connecting or completing file transfers.

Date Format
▀▀▀▀▀▀▀▀▀▀▀
The date format you prefer.  Note that the Usage Log uses a standard format
called the "Call Data Standard" (CDS) format, and this standard mandates a
date in the form of YY-MM-DD, and a time format of HH:MM:SS, so don't
expect this setting to change the way your Usage Log (or the "Capture
Stamp" mentioned above) looks.  It applies only to date displays for your
own consumption, such as at the Main Menu.

Date Separator
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The date separator character you prefer.  Note that the Usage Log will use
"-" as the Date Separator regardless of what you define here.  Other places
in Icom where the date is displayed (the Main Menu, for example) will use
the Date Separator you define here.

Time Format
▀▀▀▀▀▀▀▀▀▀▀
As above, but for the time of day.

Time Separator
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
As above, but for the time of day.
ÜNote that for all "DOS commands" defined on this screen, which call an
external program or .BAT file, you can precede the command with SW: to have
Icom swap itself out of memory (see DOS Shell for details) before executing
the external program.  You can also precede the command with NS: (No Swap)
to perform a faster shell, and have Icom leave itself in memory while the
external program runs.  Note that if SW: is used (Swap), the "Enable
Swapping" setting on the General Settings screen still applies, and Icom
will not swap itself out if it's connected and Enable Swapping is set to
"When not connected".

Mail Reader
▀▀▀▀▀▀▀▀▀▀▀
If you're in the habit of reading BBS mail offline, you can integrate your
external Mail Reader with Intellicomm by entering the command you'd
normally use to start your reader from DOS (C>) here.	If you normally use
a .BAT file to start your reader (to perform a CHDIR command or the like
before entering the reader... this is quite necessary with Sparkware
products), use the .BAT file name here.  You almost certainly will want to
precede the reader command with SW: to force Icom to swap itself out of
memory.  Examples:

SW:C:\BAT\DELUXE.BAT
SW:C:\MEGA\MEGAREAD.EXE

Reply Dir
▀▀▀▀▀▀▀▀▀
Every offline Mail Reader worth its salt saves your replies in a single
file, compresses the file, and places it in a user-configurable directory
where your comm. program can easily find it when uploading it to the BBS
message system.  Before automated programs like Icom came along, most
people had their readers create the reply packet in their comm. program's
"Upload Directory", to avoid having to specify a directory name when
uploading the file.  Nowadays, with things such as Icom lurking about, the
mail readers assume that the comm. program will conform to the reader...
and they usually create a reply directory somewhere in or around the mail
reader itself, instead of using the comm. program's upload directory.  Icom
cares not which is the case.	You can make your reader conform to
Intellicomm, or you can make Intellicomm conform to your reader.  Whichever
is the case, as long as both programs agree that reply packets should be
placed in a SINGLE directory, everyone will be happy.	Note that you can
override this directory for a particular BBS, if necessary, by defining a
"Reply Dir" in the BIF itself, on the "Message" screen.

Message Dir
▀▀▀▀▀▀▀▀▀▀▀
Basically the same as above, but in this case, Icom places newly downloaded
mail in this "Message Directory".	As long as both your reader and
Intellicomm agree on the same directory, it matters not where they go.
Note that you can override this directory for a particular BBS, if
necessary, by defining a "Message Dir" in the BIF itself, on the "Message"
screen.

Main Unpack
▀▀▀▀▀▀▀▀▀▀▀
Ideally, this item will hold the name of a program that is capable of
uncompressing ANY type of archive, and is also capable of auto-detecting
the archive type without using the filename (for .QWK mail packets) as a
guide.  But until we, or someone else, produces this "wonder unpacker",
we're stuck with PKUNZIP (or equivalent).  Icom uses this command to
extract the NEWFILES.DAT (new files list) from newly downloaded .QWK mail
packets, and also uses it to uncompress new ICOMAUTO.ZIP auto-BIFs.  If
this command fails (i.e. if the archive was not a "ZIP") ... we fall below
to the next command.

2nd	Unpack
▀▀▀▀▀▀▀▀▀▀▀
This command is the last line of defense when the command above fails to
produce the expected result (either a NEWFILES.DAT from a .QWK, or a .BIF
from an ICOMAUTO).	It needn't be PKUNPAK (the old .ARC type format).  It
can be LHA e, ARJ x, etc.  Whatever type of archive you're most likely to
run into in your area, on the BBS's you call.

Arc. Viewer
▀▀▀▀▀▀▀▀▀▀▀
If you attempt to "View" or "Edit" a known archive type (.ZIP, .ARC, .ARJ,
.LHA, .ZOO, etc.) in the File Manager, or in the File Tagger when browsing
the FILELIST catalog (files that were auto-downloaded) your external
Archive Viewer is automatically called to view the archive, if you define
the command here.  Enter it just as you would from the DOS command prompt.
Note that you may have to precede this command with SW: (SWap) to have Icom
swap itself out of memory before loading the Archive Viewer.  Example:
SW:SHEZ.EXE

File Viewer
▀▀▀▀▀▀▀▀▀▀▀
Can be used to substitute Icom's internal File Viewer with a more advanced
external file viewer such as Buerg's "LIST" program.  If you define a File
Viewer here, Icom uses the external viewer in place of its internal viewer.

Extnl Editor
▀▀▀▀▀▀▀▀▀▀▀▀
Same as above, but this option allows you to substitute Icom's internal
Text Editor with a more advanced external editor.

Alt-N Hotkey / Description
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
A general purpose command you can use from just about anywhere in
Intellicomm, by just pressing [Alt-N].	The actual command to execute/send
to DOS goes on the upper line (beside "Alt-N Hotkey") while a "Description"
of the command (shown at various Icom menus beside [Alt-N]) can be placed
below.

Alt-O Hotkey / Description
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
As above, but for the [Alt-O] hotkey.

BIF Dir
▀▀▀▀▀▀▀
The drive/directory where BIFs, BIF templates, .MTF (Message Template
Files), and .BTF (Bank Template Files) are stored.  C:\ICOM\BIF\ by
default.

Catalog Dir
▀▀▀▀▀▀▀▀▀▀▀
The drive/directory where File Tagger Catalogs are stored.	C:\ICOM\DBF\ by
default.

Filelist Dir
▀▀▀▀▀▀▀▀▀▀▀▀
The drive/directory where BBS new files lists (*.NEW) are captured to, and
also where Icom looks for SND/GET Lists.  C:\ICOM\LST\ by default.

Upload PATH
▀▀▀▀▀▀▀▀▀▀▀
A list of drives/directories (each separated by a semicolon, with NO spaces
from one end to other) Icom should search when looking for a particular
filename to upload.  C:\ICOM\SND;C:\ICOM\GET by default.  Not applicable to
reply packet uploads.... see "Reply Dir" above for that.

Download Dir
▀▀▀▀▀▀▀▀▀▀▀▀
Where newly downloaded files (aside from auto-downloaded mail) is placed.
C:\ICOM\GET\ by default.  This drive/directory can be overridden in a
particular BIF in the "Download Dir" item on the "File" screen, if need be.

Script Dir
▀▀▀▀▀▀▀▀▀▀
The directory the Script Manager displays, and also the ONLY directory from
which you can execute an Intellicomm script.  C:\ICOM\SCR\ by default.

Usage Log
▀▀▀▀▀▀▀▀▀
The path/filename of the Usage Log.  C:\ICOM\CAP\ICOM.USE by default.

Capture File
▀▀▀▀▀▀▀▀▀▀▀▀
The path/filename of the Capture log.  C:\ICOM\CAP\ICOM.CAP by default.

Screen Cap
▀▀▀▀▀▀▀▀▀▀
The path/filename of the Screen Capture log. C:\ICOM\CAP\SCREEN.CAP by
default.

Swap Dir
▀▀▀▀▀▀▀▀
When Icom swaps itself out for a DOS Shell, or to run an external program
listed above, if not enough EMS or XMS is available for the swap, Icom
swaps itself to disk by creating a temporary file and writing its current
memory image into this file.	By default this file will be placed in the
\ICOM directory, but if you have a large RAMDisk installed, you can write
the swap file there instead.	Note that if this is the case... hopefully
you have a good reason for using the RAMDisk, since it's a much less
effective use of memory to use a RAMDisk as opposed to just making some EMS
or XMS available for programs to use.  RAMDisks should only be used when
you have no alternative.

Printer
▀▀▀▀▀▀▀
If you want to print this help screen by pressing [Alt-P] (or print from
the File Viewer or Text Editor), you'll have to make sure you define the
proper printer device here (if not PRN) or the printing isn't going to
work.
åMenu Style/Colors
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This screen is self-explanatory if you pay attention and experiment for a
second (just hilight the item[s] of interest, and press [Enter]).  By the
time you read a detailed account as to "how" to use the color menu, you'll
already have figured it out by just playing around a bit.

If you mess up and don't want to keep the changes you made, just keep
pressing [Esc] until you exit the color menu (and all the way back to Icom,
if you like).	If you find a nicer combination of menus/colors and you want
to keep things that way for a while, make sure you pick "Preserve and exit"
to exit the color menu (this does NOT save anything to disk; you still must
re-save your setup when you exit to save the changes permanently).  If you
use [Esc] to exit, you'll get your old colors/menu style back.

Default Screen Size
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
A picture is worth a thousand words.  Try changing it and see what
happens...  If nothing happens, your video adaptor doesn't support extended
screen line mode.  If you don't like what you see, change back to your
original video mode.  If you like what you see, keep it set that way.  Note
that the File Tagger also has its own "Screen Size" setting, allowing you
to use 25-line mode for Icom itself (and calls to BBS's), while using an
extended line mode for the File Tagger (to display more files on the screen
at once, and also to increase the number of lines you use in the "Split
Screen" report, showing more of the file description).

Screen Write Mode
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This should only be changed from "Direct writes" if you have a good reason
for doing so.	If your hardware isn't 100% IBM-compatible, and you're
having problems with the video, using BIOS writes may solve the problem. 
If you're still using a CGA adaptor that produces "snow" when the screen
scrolls... you can either spend $10 on a newer CGA adaptor (or $20 for an
EGA adaptor ... or $30 for a VGA adaptor), or can turn on "Direct writes
with snow elimination".

Blank Screen # Seconds
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Has the power and ability to either disable the Screen Blanker (set to 0 to
disable), or to change the interval of "inactivity" (in seconds) after
which the screen is blanked.

Status Window Delay
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
You really should pay attention to, and use this setting.  Of all the
settings on this screen, this one is probably the most useful.  It allows
you to tell Icom how fast a reader you are...  The delay defined here (in
TENTHS of a second) is how long Icom will pause, when displaying status
messages, warnings, etc., for every 40 characters of text.	If the status
message/warning is less than 40 characters, the delay is adjusted downwards
accordingly.  If the status message/warning is longer than 40 characters,
the delay is adjusted upwards accordingly.  Thus, define here however long
it takes you to read 40 characters of text, plus perhaps a second or two
(add 10 or 20 tenths) to get your head/eyes pointing in the right
direction.  "This is a forty character status message."  Time yourself, add
10 or 20, plug the proper number in, and you'll never be unable to read the
full message in an Icom status message box again.
),Default Comm. Port
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The COM port your modem is connected to.  Note that only COM1 and COM4 are
defined in a default Icom setup.  COM5 through COM8 must be defined (as the
I/O interface card documents outline) on the Comm Port Settings screen
before you attempt to use them.  Everything above COM4 points to COM1 by
default.

Default Port Settings
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The speed your modem manual recommends that you set your "Terminal" or
communications program at.  Unless you're in the habit of connecting to
BBS's that are not run on PC's (IBM-compatible or otherwise), you'll want
the Parity set to "None", the Data Bits set to "8", and the "Stop Bits" set
to "1".

Software Flow Control
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If your modem doesn't have automatic error detection/correction (MNP, LAP-
M, or a V. standard), you'll want to use "Software Flow Control".  Software
flow control (XON/XOFF) is clumsy, not very reliable, and should be avoided
where possible.  See "Flow Control" in your modem manual if you're not sure
what to use.  Note that on most 1200 and 2400 baud modems, you must use
Software Flow Control and you CANNOT use Hardware Flow Control (though
there are some exceptions; such as the ATI 2400etc, which does support
hardware flow control).	On most all (if not all) modems that run above
2400 baud, you should use Hardware Flow Control, and should shut this
Software Flow Control off.

Hardware Flow Control
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If your modem has automatic error detection/correction (MNP/LAP-M/PEP or a
V. standard), it most likely supports CTS/RTS hardware flow control as
well, though you may be required to flip a DIP switch or include a specific
command in the "Initialize Modem" string (see below).	If in doubt, see
your modem manual.	Unfortunately there are no standards for such things,
and setup techniques vary from modem to modem.

Initialize Modem String
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
In the old days, modems were incapable of storing their settings once the
power was turned off ... and you had to "re-initialize" the modem (get it
back to the proper settings, instead of using the screwed up factory
defaults) before you used it.  But nowadays, most all modems allow you to
enter your settings (using the Terminal mode of any communications
program), then enter a special command such as AT&W or the like to "Write"
the settings into battery powered memory in the modem.  Where this is the
case, the only thing you need as an Initialization String is "ATZ" (which
resets the modem).	If you're using an older modem that is incapable of
saving its settings, you'll have to enter the proper set of commands here
to get all the settings into the right state for use with an IBM PC (the
settings are the exact same from one DOS comm. program to another). 
Basically you want the modem to do the following:

	    Function			  "Hayes compatible" command
──────────────────────────────────────────────────────────────────────────
SET ECHO ON						E1
MODEM RETURNS RESULT CODES			Q0
DISPLAY RESULT CODES AS WORDS 		V1
		or in VERBOSE FORM					 
ENABLE BUSY SIGNAL DETECTION			X4
		The best policy is to set 'X' to the highest number available. 
		If X4 (or higher) is not supported, Intellicomm will not be able
		to tell when the line is busy when dialing.
ENABLE CARRIER DETECT				&C1
		Very important, but may also be set by a switch.	If your modem
		is 1200 baud you can't use &C1, and should instead find the
		switch for carrier detect enable (normally switch 6 on Hayes
		compatibles).	If Carrier detect enable is not set up properly,
		Intellicomm will be told that it is connected at all times, and
		this will cause it to malfunction.
RECOGNIZE CHANGE IN DATA TERMINAL READY &D2
		Must be removed if 1200 baud.  & commands are only supported by
		2400 baud modems and higher.	This causes the modem to hang up if
		DTR changes (see DTR/Hangup below).
TURN AUTO ANSWER OFF				S0
ALLOW COMMUNICATIONS PROGRAM TO
		HANDLE TIMEOUT WHEN DIALING	S7=255

Modem Hangup String
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If Icom cannot get the modem to disconnect by dropping the DTR line (see
below), it then sends this command to the modem.	The command should (a)
put the modem into "command state" (as opposed to letting your keystrokes
go through to the BBS); typing +++ does this on most modems; (b) tell the
modem to hangup.  ATH0 (put the phone "On-Hook") is usually the proper
command.	The ~ and ^M in the default denote a one second pause (~), and
(^M	= [Ctrl-M]) the same as pressing [Enter].

Confirm Hangup?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If "Yes", you are asked to confirm a hangup when the [Alt-H] hotkey is
pressed, or when "Hangup" is selected from the Terminal Menu.

Drop DTR to Hangup?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If your modem is even remotely intelligent, it will not allow a connection
to continue if the DTR line (Data Terminal Ready ... a line in the COM port
that tells the modem whether or not there's a comm. program "awake" and
receiving data in the computer) goes low.  Icom raises the DTR line when it
starts up, and it lowers it when it exits (unless you elect to stay
connected after exiting), and most modems will drop the connection
immediately if the DTR line goes low.  Thus, a handy (and reliable) way for
a comm. program to GET the modem to hang up is to temporarily "play dead"
by dropping the DTR line.

HANGUP NOTE: Unless the modem reports the state of the connection properly
(most modems don't from the factory), Icom will have no choice but to
report "Hangup Failed".	Please see Common Questions & Answers (and
"Initialize Modem String" above) for a fix.

Init Modem at Startup?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines whether Icom initializes your modem at program startup, or
leaves it until just before dialing.  If you run into problems with
dialing, try having Icom initialize your modem at program startup.

Init Modem if Connected?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If set to "No", and the modem is connected when Icom first starts up, the
Initialize Modem String (see above) is NOT sent to the modem.  On some
modems, until the initialization string IS sent to the modem (the &C1
command), the modem does not report the connect status properly.  On such
modems, you should set this item to "Yes".

Status Bar
▀▀▀▀▀▀▀▀▀▀
Determines whether a status bar is displayed in Terminal mode.  The status
bar shows the name of the BBS you're currently connected to, how long
you've been online, the state of Intellicomm (Auto|Script|Learn| Manual),
the COM port settings, the state (and filename, if open) of the Capture
log, and a reminder as to how to pop up the Terminal Menu.

Status Bar Displays
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This setting determines what is displayed on the Terminal status line,
here  ─────────────────────────────┐
							│
BBS Name		 HH:MM │ Manual │ XXXXXΘN81 │ ...

If set to "Port Speed", the speed the COM port is operating at is displayed
here.  If set to "Modem-to-Modem speed", the speed reported by the modem
CONNECT message is displayed.  If you have "Auto Baud Adjustment" turned
on, on the Dialer Settings screen, then this setting is irrelevant since
the port speed and the modem-to-modem speed will be identical.  If you use
an error-correcting modem, however, and have Auto Baud Adjustment turned
OFF (i.e. the port speed is locked), then the CONNECT speed and the port
speed are usually different.	Note that some modems do not report the
modem-to-modem speed after the CONNECT message, and instead report the
speed in another message such as a CARRIER message (CARRIER 9600, etc).  If
this is the case with your modem, simply change the "Dial Connected"
message on the Dialer Settings screen:

║ Dial Connected		 > CARRIER					    ║

The Dialer will then be able to determine the modem-to-modem speed
properly.

Scrollback Size [Kbytes]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The size of the Scrollback Buffer, in kilobytes.	The larger the Scrollback
Size, the more data you can review in the Scrollback Buffer, and the more
memory Intellicomm uses.  Set this item to 0 to disable the scrollback
buffer, if you don't need it (it'll increase the speed of the terminal
slightly to do so).

Receive Buffer Size [K]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Please see Optimizing Intellicomm for a detailed description.

Transmit Buffer Size [K]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This is where data is stored while Icom is waiting for the modem to "empty"
the last character placed in the transmitter end of the COM port.  Icom
keeps filling up the Transmit Buffer (until full), whether the modem is
actually sending anything or not.	As the modem has time to send the data
over the phone line, it'll empty the character sitting in the COM port, and
Icom's interrupt handler will get another character (if any) from the
Transmit Buffer and stick it in the COM port, again to wait for the modem. 
The bigger the Transmit Buffer, the less chance there is that Icom will
have to sit around waiting for the COM port.  But note that the total size
of the "Receive Buffer" (see above), PLUS the size of this "Transmit
Buffer" must be 32 kilobytes (or less) in length.  You 'can' get away with
defining more than 32K in total here, but Icom will adjust the combined
Transmit/Receive Buffer lengths to no more than 32K when the memory is
allocated.

Echo
▀▀▀▀
If you see something like "HHeelloo" when you type commands, you've got
this option turned on when it needn't be.  If you see absolutely nothing
when you type, you don't have this option turned on when it should be.  All
but the most archaic modems will "echo" the characters you type, so in most
all cases, Echo will be OFF in Intellicomm.

Add Line Feeds
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If each new line from a BBS overwrites the previous line, this option is
off when it should be on.  If lines from the BBS are double-spaced, this
item is on when it should be off.

Backspace Destructive?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If "Yes", backspace characters received from the BBS actually "erase" the
character to the left of the current cursor position.	If "No", the cursor
moves one position left, but doesn't erase the character on-screen.

Send DEL as Backspace?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Causes the Backspace key to send DEL (ASCII 127). If you need it, you'll
know what it's for.  Note that [Ctrl-BS] can also be used send DEL.

Enable 16550 if Found?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Please see Optimizing Intellicomm for a detailed description.

16550 Receive Trigger
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Please see Optimizing Intellicomm for a detailed description.

16550 Transmit Trigger
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines how many characters (bytes) Icom gives to the 16550 UART on each
"Ready to Transmit" interrupt.  16 is the maximum, but the UART (16550 or
otherwise) does NOT observe flow control, so you can cause an overrun at
the BBS (a "Bad CRC" error, on their download/your upload) by loading the
16550 up on transmit interrupts.

ENQ Response/@SCRIPT
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The response Intellicomm sends if an ENQuiry (Control-E, ASCII 5) is
received from the BBS (normally nothing is required, and an improperly
defined ENQ string could interfere with proper operation of Intellicomm). 
You may also call a script when ENQ's are received, which may be useful in
calling external protocols.  Compuserve uses ENQ to signify the start of a
CIS QuickB transfer.
▌"Dial Prefix 1
▀▀▀▀▀▀▀▀▀▀▀▀▀
This is the command your modem requires to dial a telephone number.  On
Hayes compatibles, the correct commands are ATDT for touch tone dialing,
and ATDP for pulse dialing (no carriage returns should be entered in the
prefix... Icom APPENDS the number it is dialing directly to these prefixes. 
E.g. <Prefix><Number><Suffix>.  The <Suffix> [below] is usually a carriage
return to [Enter] the command).

Dial Prefix 1 is what all BIF templates default to.  I.e. you must change
the prefix in your BIF after you create it, if you wish to use prefix 2 or
3 below.

You can, if necessary, send multiple commands to the modem by adding to the
default dialing prefix ("AT S0=0 X6 T" [touch tone] or "AT S0=0 X6 P"
[pulse] are legal dialing prefixes).  By defining multiple dialing prefixes
with customized modem commands in each prefix (error-correction on, error-
correction off, etc.) you can set your modem up differently depending upon
the BBS you're calling.

Dial Prefix 2
▀▀▀▀▀▀▀▀▀▀▀▀▀
Same as above, but this is an alternate (and optional) prefix you can
define for convenience.	To use this prefix, just enter 2 in the "Dial
Prefix" item on the 1st BIF screen.

Dial Prefix 3
▀▀▀▀▀▀▀▀▀▀▀▀▀
Same as above, but this is an alternate (and optional) prefix you can
define for convenience.	To use this prefix, just enter 3 in the "Dial
Prefix" item on the 1st BIF screen.

! Dial Code
▀▀▀▀▀▀▀▀▀▀▀
All of these codes (!, @, $) are optional, and they are provided as a
convenience.  They can be used much like the "Dial Prefixes" above (to send
custom commands to the BBS, or just to enter any sequence of characters in
a telephone number).  But these Dial Codes are usually place right in the
BIF where you define your telephone numbers.  If you frequently dial a
specific area/country code when dialing, you can save keystrokes by
defining the repetitive characters here in one of the "Dial Codes".  If you
defined:

1-416-

As the ! Dial Code, you could then use !555-1234 in your BIFs to dial 1-
416-555-1234.	Please see Enter Phone Number for more information.

@ Dial Code
▀▀▀▀▀▀▀▀▀▀▀
As above, but this code uses the '@' character.

$ Dial Code
▀▀▀▀▀▀▀▀▀▀▀
As above, but this code uses the '$' character.

Dial Suffix
▀▀▀▀▀▀▀▀▀▀▀
This command (normally just ^M; a Carriage Return or [Enter]) is added just
after the telephone number Icom is about to dial.  Again, the format is:

 <Prefix><Number><Suffix>

The whole thing, prefix, number (with !, @ and $ codes expanded), and
suffix, is sent as one command to the modem.

Dial Connected
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If your modem is set up properly, it will return WORDS to the computer to
communicate the results of dialing.  "Dial Connected" is the word the modem
returns to signify a connection.  CONNECT is the usual word used, but in
order to use either the Minimum Connect Speed or Auto Baud Adjustment
(below), the modem must return the actual modem connect speed immediately
following this "Dial Connected" word.  Most modems will do something this:

CONNECT 9600

But some modems do this:

CONNECT 9600
CARRIER 2400

Reporting the port speed in the top line, and the actual modem speed (which
is what is relevant for the next two settings below) after the word
CARRIER.	If this is the case on your modem, simply use the word CARRIER as
your "Dial Connected" string.

Minimum Connect Speed
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The lowest speed you want Icom to connect at, or 300 to disable speed
checking.  If a connection is made at a speed slower than the speed defined
here, Icom gives you 15 seconds to proceed with the call at the lower
speed.  If you don't return to your computer and press a key, Icom hangs up
and redials (up to the "Max. Redials" defined in the BIF).

Auto Baud Adjustment
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This setting is becoming irrelevant on modems these days.  With older
modems, the COM port speed had to be set to the same speed as the modem
connect speed (the speed the two modems are communicating at, as opposed to
the speed your modem and the computer are communicating at).  So if you had
a 2400 baud modem, and you connected at 1200 baud, the terminal (COM port)
would have to drop down to 1200 baud or you'd just get garbage on your
screen.  Today, most modems use a "locked" terminal speed.	 That is, you
do not want Intellicomm to adjust the COM port speed regardless of the
actual speed that the two modems are communicating at.  Auto Baud
Adjustment "On" means that you DO want Icom to watch the "CONNECT 2400"
(etc) message, and to set the COM port speed to the same speed that the
modems are communicating at.	Auto Baud Adjustment "Off" means that you
want Icom to keep the port speed fixed at the speed defined in the BIF
"Port Settings", regardless of the actual modem connect speed.  Your modem
manual will tell you which you should use.

Dial Busy/Retry 1
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Is your modem capable of detecting busy signals, and telling the computer
about the busy signal via a WORD?	If so, this is where you should define
the word your modem returns to signify "line busy".  Normally the word is
"BUSY".  If Icom's Dialer receives this word after sending a dial command
to the modem, it cycles to the next number to dial (if any) immediately,
and it leaves the current number in the dial queue to be tried again later.

Note that most modems require that you use an X4 (or higher) command in the
Initialize Modem String, before busy signal detection is enabled.

Dial Busy/Retry 2
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Optional.  Another word the modem returns where you'd like Icom's Dialer to
cycle to the next number, and to leave the current number in the dialing
queue (try again later).

Dial Busy/Retry 3
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
See above.

Exclude Dialing 1
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Optional.  If this word is returned from the modem after a dial command is
sent, the Dialer immediately cycles to the next number to dial (if any),
but it REMOVES the current number from the dialing queue.  I.e. it will not
be dialed again.  This is useful for cases where the number is out of
service, or the BBS telephone number changes without your noticing, and
some poor soul gets the old BBS telephone number at a later date (a VOICE
return code).	It prevents the Dialer from making a pest of itself, and
dialing a non-functioning number over, and over, and over, and over... as
most comm. programs do.

Exclude Dialing 2
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Optional.  Another word the modem returns where you'd like Icom's Dialer to
cycle to the next number, and to remove the current number from the dialing
queue (don't try again later).

Exclude Dialing 3
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
See above.

Dial Timeout
▀▀▀▀▀▀▀▀▀▀▀▀
If the modem returns nothing at all (or just keeps returning RING over and
over again), this timeout, in seconds, cause the dialer to give up.  The
timer is started as soon as the dial command is sent to the modem.  If the
timeout period elapses, the Dialer immediately cycles to the next number
(if any), and leaves the current number in the queue.	Don't forget that
you can also define a "Max. Dial Attempts" in each BIF ... telling the
Dialer to give up if it can't connect after a given number of total dials
to a given BBS.

Stop Dialing
▀▀▀▀▀▀▀▀▀▀▀▀
If you press the [Esc] key to cancel dialing in the Dialer, Icom has to
have some way to tell the modem about it, and to get it to stop dialing. 
This command is what Icom sends if you press [Esc] (it's sent twice,
actually, just to make sure).  Normally just a carriage return (^M) gets
the job done.

Pause Between Dials
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Is your modem connected to your usual voice line?  If so, you might want to
increase the pause between dials to let voice calls through while Icom is
dialing.	With a pause of just 1 second (the default), it only gives the
telephone company just long enough to reset its circuits before Icom sends
another number.  If someone was trying to get through to your voice line at
the time, they'd most likely get a non-stop busy signal.  If you do
increase the pause between dials to 10 seconds or so, AND if someone does
phone you during that 10 second pause, make sure you select "Hold" from the
Dialer menu to pause Icom's dialing while you're talking on the phone.

Attempts per BIF/Cycle
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
There are 5 telephone numbers (maximum) in each BIF.  Normally, the Dialer
dials each number in the BIF once, then it cycles to the next tagged BIF
(if any)... and this is due to the fact that this item is set to 1 by
default.	If you increase it to 2, then the Dialer will dial each number in
each BIF twice before cycling to the next tagged BIF, and so forth.

LD Service Phone Num
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This is the number Intellicomm dials if you have an "LD Service"
long distance service defined on BIF screen 1.  It should be either your PC
Pursuit or iNet 2000 local access number.  See Long Distance Services for
more details.
,POSTFILE.SCR Settings
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
When you select this option Intellicomm executes the POSTFILE.SCR main
setup program: \ICOM\SCR\POSTINI.SCR.  More help is available once
POSTINI.SCR starts, through POSTINI.SCR itself.

Move Old Downloads?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If set to "Yes", Icom moves any files in the default Download Directory
(\ICOM\GET), to the first directory on the default Upload PATH (\ICOM\SND),
just before running any job that has a "Download tagged files" task in it. 
The purpose of it is to clean out the Download Directory so that after the
next job finishes, ONLY newly downloaded files will exist in the Download
Directory.  A note of warning though: if a file transfer aborted
previously, and you didn't allow Icom to automatically recover the
transfer, the existing (aborted) portion of the file will be moved if this
setting is on, thwarting Zmodem or external protocol crash recovery.

Cancel D/L on No Time/Bytes?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This setting is only checked during Automated Downloads, when Intellicomm
is tracking the No Time/No Bytes prompts on the BIF "File" screen:

║ Files per U/L  .				No Time  . . . . Sorry,« 		   ║
║ Files per D/L  .				No Bytes . . . . Insufficient«	   ║
							──────────────────────────────
If either of the above prompts are found during filename entry on an
automated download, and "Cancel D/L on No Time/Bytes" is set to Yes, then
no more filenames will be entered for download, even if more files remain
tagged.  Usually this setting will remain turned off, since it only takes a
Intellicomm a few seconds to enter a dozen or so filenames, and it doesn't
hurt anything if you don't have enough time/download bytes to transfer any
of the files (they're simply saved for the next session).  And often, a
smaller file will be found further along, and it WILL be transferred even
though some larger file couldn't be transferred due to lack of time or
download bytes.  But, if you don't want Icom to keep trying after it gets
the first No Time/Bytes message from the BBS, just turn this item off.

Auto Zmodem Receive
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If a Zmodem auto-download sequence is detected in Manual terminal mode, and
if this option is on, the Zmodem download begins (using the protocol
defined below) without your having to press [PgDn] to initiate a download.

Auto Zmodem Protocol
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This is the protocol Icom calls when an auto-Zmodem download sequence is
detected.  See above.

Zmodem Crash Recovery
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The type of crash recovery (if any) Icom's internal Zmodem uses to recover
from aborted file transfers.	Zmodem has the ability to ADD to the end of
an existing file, if it already exists on-disk (most likely due to a
previously aborted file transfer).  If Crash Recovery is set to "Regular",
Zmodem simply checks the filesize to determine whether it should add to
existing file on-disk: the incoming file must be LARGER than the existing
file.  If Crash Recovery is set to "Smart", Zmodem does both a filesize and
CRC check.  CRC stands for Cyclic Redundancy Check, and it's a very
accurate way to check a chunk of computer data (a file in this case).  The
CRC check opens the existing file on your disk, loads each byte of the
file, and runs it through a complicated formula to arrive at an "end
result" (a number).  Meanwhile, Zmodem at the BBS is doing the same thing
to the same portion of the file (according to the filesize, on your disk,
which Icom's Zmodem communicates) on the BBS.  If both Icom's Zmodem, and
the BBS's Zmodem come up with the same "end result" (the CRC value), then
it's about 99.99998% certain that both the BBS file, and the file on your
disk are the exact same file... and Zmodem then commences to add to it. 
The purpose of all this is to avoid wrecking an existing archive that just
happened to use the same filename (such as an old mail packet).

Filename Conversion
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This allows you to tell Icom's internal protocols what to do with the
filenames it sends and receives.  It can convert them to uppercase,
lowercase, or leave them alone.  This is mostly a cosmetic issue when
transferring from one DOS machine to another, but if you're sending files
to a UNIX box or the like, you might want filenames to be converted to
lowercase.


Manage Duplicate Files
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines what internal Ymodem (or Zmodem, if crash recovery is turned
off) does if an incoming file exists on-disk already.	If Manage Duplicate
Files is set to "Yes", the incoming file is given a new name, by placing
numbers in the filename (starting with the last character... FILE.EXT
becomes FILE.EX0).	If set to "No", the transfer aborts (Ymodem) or the
file is skipped (Zmodem).

Delete Aborted Transfers
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If on, internal X/Y/Zmodem will delete the portion of the file that exists
on-disk, if the transfer aborts.  I.e. no crash recovery is implemented at
all.

Disk Buffer Size
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
In order to transfer a file, all internal protocols must "open" the file
either to read it (uploading) or write to it (downloading).  This setting
determines the size of the memory buffer used (in kilobytes) to buffer
these disk read/writes.	Only once the buffer fills up, is the disk
accessed, and there is but one advantage to this: by increasing the disk
buffer size, it saves turning your disk drive motor on/off a few times. 
There can be a very real DISadvantage to increasing this disk buffer size
though: The larger the buffer, the longer it takes to read from/write to
disk.  And while the disk is being accessed, you can lose incoming data
(downloads only) coming in the COM port.  If you increase the size of this
buffer, IMMEDIATELY go and test a few high-speed downloads.  If you run
into lots of Bad CRC errors, put this buffer back to 1 Kilobyte
immediately.

ASCII Transfers
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Line Pacing/Delay:	How long the ASCII protocol waits (in tenths of a
				second) after sending a line feed from a text file. 
				This "pacing" allows the BBS to catch up... since in
				the cases you'll use ASCII uploads for most often --
				uploading pre-typed messages -- the BBS isn't expecting
				the "typing" to be going quite as fast as the ASCII
				protocol sends.  You can slow things down by increasing
				this delay, if you get a mess.  [Applies only to ASCII
				uploads.]
Char Pacing/Delay:	This delay allows you even more control, and lets you
				tell the ASCII protocol to delay for a given amount of
				time (in tenths of a second) after sending each
				character.  [Applies only to ASCII Uploads.]
Receive Timeout:	To perform regular Message "Captures", Icom uses an
				ASCII download... which simply has the effect of
				capturing the messages to a specific text file (the
				name you plug in the BIF).  However, a regular ASCII
				download ends only when (a) the user presses [Esc] to
				end it manually, or (b) one or more Control-Z (end of
				file) characters are found.  Neither are suitable for
				automated message captures... and this is where this
				Receive Timeout comes in.  It ends an ASCII download as
				soon as a period of inactivity (in seconds) is detected
				at the BBS.
δIf you've never set up an external protocol, or are unfamiliar with DOS
BATCH FILES please see External Protocol Introduction before continuing.

If you're planning to use the bi-directional HS/Link external protocol,
please VIEW the comments in HSLINK.BAT, included with Intellicomm.

Quick Setup (Experienced Users)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Set up two DOS batch files to interface with the external protocol program,
passing it the necessary command line options.  Icom passes the current COM
port speed to the .BAT files as parameter 1 (%1) and the current COM port
number (1-8) as parameter 2 (%2).	Examples for DSZ:

rem DSZ-D.BAT (download)
DSZ.COM port %2 speed %1 ha on rz -mrr

rem DSZ-U.BAT (upload)
DSZ.COM port %2 speed %1 ha on sz -m %4 %5 %6 %7 %8 %9

The command line parameters Icom passes are:

Parameter 1:	The current COM port speed (300-115200).
Parameter 2:	The current COM port (1-8).
Parameter 3:	The string "-CDSC:\ICOM\CAP\ICOM.USE" (no quotes).  Icom
			uses the Call Data Standard usage log format, and any
			external protocol which supports this standard will be
			looking for the -CDS switch on its command line.	Unless the
			protocol uses the CDS usage log format, and specifically
			tells you to include a -CDS switch on the command line, you
			will not use parameter 3 in your BAT files.
Parameter 4:	The filename to download (if "Ask for Filename on D/L?" is
			set to "Yes" ... see below), or the first filespec to
			upload.
Parameter 5:	Parameters 5 and onward will only contain values if multiple
			filenames were specified in the "Enter filenames" upload
			box.  If you use the Icom "File Picker" and tag several
			files for upload, Icom creates a text file containing all
			the tagged filenames, and passes the name of the text file
			as Parameter 4 (e.g. @C:\ICOM\ICOM.UL).  Most all external
			protocols support this use of a text file, and use the @
			character to signify that a list of filenames is to be used. 
			Thus, where the external protocol expects filenames to be
			for an upload, you should specify "%4 %5 %6 %7 %8 %9" (no
			quotes).	This will either be replaced by the filenames you
			entered in the "Enter filenames" upload box, or by
			@C:\ICOM\ICOM.UL if you used the File Picker.

Note that Intellicomm passes the COM port and speed in the same order as
most other comm. programs do, so if you already have .BAT files set up for
another comm. program (Telix, etc) you can probably just copy them to your
\ICOM directory (or put them on your PATH so all programs can use them). 
However, make sure you remove %3 (the -CDS switch) if the external protocol
doesn't support the CDS Usage Log format.

Once you have the .BAT files created and installed in the \ICOM directory
(or in a directory on your DOS PATH), just plug them in an empty slot on
the Icom main setup / External Protocols screen:

│												Ask for File  │
│	 Name/Description  Hotkey  Receive Cmd.    Send Cmd.	name on D/L?  │
│														    │
│ 1.  DSZ-Zmodem		 D	  DSZ-D.BAT	   DSZ-U.BAT	    No	    │
						  ═════════	   ═════════
"Name/Description" is simply the text that will be display on the protocol
menu, 'Hotkey' is the hotkey you'll use to select the protocol from the
protocol menu, 'Receive Cmd.' is the batch file Icom executes (and passes
the command line parameters to) on downloads, 'Send Cmd.' is the batch file
Icom executes on uploads.

'Ask for Filename on D/L?' determines whether Icom asks for/passes a
filename to the protocol on a download.  All but ancient protocols will
pass the filename over the telephone line just before the file data...
instead of wasting the receiving user's time by prompting for the
information.  The sending protocol already knows the filenames or it
wouldn't have been able to start the transfer... and in most cases the
sending protocol simply passes the proper filename(s).  But, with old
Xmodem (and some others), no one had thought of this as yet.  So you have
to enter the same filenames at *both* ends of the connection.  If this is
the case with the external protocol you plan to use, set 'Ask for Filename
on D/L?' to "Yes" and, if in manual mode, Icom will ask you to enter the
filename to receive -- and it'll pass this filename to the external
protocol 'Receive Cmd.' (.BAT file) as command line parameter 4.  During
Automated Downloads, Icom already knows the filenames, and it'll simply
pass them to the protocol without prompting you for them.  If you must set
this option to "Yes", you really should consider finding another (better)
external protocol to use.
a.What is a "Protocol?"
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
A protocol, in the context of computer communications, is a program you use
to transfer important data from one computer to another.  If line noise
hits when you're reading a bulletin online, you see some garbage on your
screen and that's the worst of it.  However if the same happens when
transferring a computer program, and line noise or other communications
problems distort the machine code of the program... virtually anything
could happen when you ran the program: and probably nothing pleasant.  Thus
when transferring important data from one computer to another over possibly
noisy telephone lines, it's essential that all the data transferred is
double-checked to ensure that it arrived intact.	This is the purpose
transfer protocols serve: to double-check important data transfers.

However, it would make no sense to transfer the entire file before double-
checking the data; since if an error was detected... the ENTIRE file would
then have to be re-transferred.  So transfer protocols break data down into
"blocks" (pieces), transfer one block, check one block, and so on.  If an
error is detected all the protocol must do is re-transfer is a small block
of data, and not the entire file.	One of the differences between the
various protocols is in the block size used: some use 512 byte blocks, some
use 1024, some use even larger blocks.	Smarter protocols like Zmodem use
variable sized blocks according to the quality of the line (the number of
transfer errors; if there are lots, a smaller block size is used so that
less information has to be re-transmitted for each error).

How do Protocols check for errors?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This is another of the major differences between protocols: the method used
for error-detection and error-correction.  The SENDING protocol performs a
check on each block of data before it sends it, and it passes the result of
this check (just after each block of data) to the receiving protocol.  The
receiving protocol then performs the same check on the data, compares its
result to the result the sending protocol sent... and if they both came up
with the same result in the cross-check, the data is assumed to have
arrived intact.  If there's a mismatch in the cross-check, the receiving
protocol throws away the data block and asks the sender to re-send the
block.

This is important to understand, as whenever you see 'errors' occurring
during a file transfer it means that the protocol IS working and has
detected (and is correcting) an error of some sort.  You never have to do
anything about errors you get when transferring files (unless the transfer
aborts, and even then if you use Icom for auto file transfers IT will worry
about what to do to correct the situation, not you).  You don't even have
to understand what the errors mean; the information is only displayed to
show you that something went wrong, and that the transmission might take a
little longer due to the fact that one or more blocks had to be re-
transmitted.

Checksum vs. CRC
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Early protocols (Xmodem) use a method called "Checksum" to detect errors. 
A checksum is simply the sum of all the byte values in a data packet (a
block)... and it's not very reliable.  Another error-detection method,
called a Cyclic Redundancy Check (CRC) puts each byte in each block through
a much more complex mathematical formula.  The longer the formula (CRC-32
means a 32 bit formula result, CRC-16 means a 16 bit formula result) the
less likely it is that an error will slip by undetected.

It's virtually impossible to come up with the same CRC value at both the
sending and receiving end if even the slightest (or strangest) error
occurred during data transmission.  The same cannot be said of the Checksum
method.  For example, if line noise hits and changes one byte from, say a
value of 46 to a value of 48 ... and changes another byte in the SAME block
of data from a value of 200 to 198, the SUM of all the bytes will be the
same: since line noise dropped 2 off one byte, and added 2 to another byte,
the end-result is the same SUM.  So simply summing up all the bytes in a
block of data is an unreliable way to check for errors.  This is the main
reason the CRC method was introduced, since it isn't fooled by such flukes.

Some protocols (such as Ymodem-G) have the ability to DETECT transfer
errors, but have no ability to CORRECT transfer errors, and such protocols
are only of use when you have an error-free link such as when two error-
correcting (MNP, v.32, etc) modems are in use, or when two computers are
linked together via cable.  NOTE: Even when error-correcting modems are in
use, and the modem-to-modem link is error free, it still doesn't guarantee
that the data will arrive to the protocol program error-free.  Bytes go
through quite a gauntlet from the modem: first to the COM port (via cable
from your modem), from the COM port to the "interrupt service routine"
(part of Intellicomm), into the Receive Buffer, and finally to the protocol
itself (where a further error-check is performed).  Due to various problems
(outlined in Optimizing Intellicomm) you CAN get transfer errors even when
using error-correcting modems, and thus it's best NOT to use a protocol
that cannot recover from errors (Xmodem-1K-G and Ymodem-G) when using
Intellicomm for UNATTENDED communications.

Fascinating, but which protocol is the BEST?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Internal to Intellicomm, Zmodem is the best, hands down, by several miles,
and you should use it whenever you can (whenever you're using a BBS or mail
system that also supports Zmodem).  External to Intellicomm, HS/Link is a
very good choice since it offers all of the BBS-related advantages of the
latest Zmodem (intelligence, crash recovery, very efficient throughput and
reliability), and can ALSO upload and download at the same time.  HS/Link
is shareware produced by Sam Smith, and is available for download on most
all BBS's.  Intellicomm includes special support for HS/Link, documented in
the included HSLINK.BAT file.

Intellicomm's Internal Protocols
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

ASCII
─────
Only of use when transferring text files; no error checking is performed. 
By setting Icom up to use ASCII as the "Receive Mail" protocol, and setting
the BIF "Msg Filename" to the name of a text file, you can use the ASCII
protocol to 'capture' text-based mail to a specific file, using
Intellicomm's normal "Get all new mail" automated job task.

Xmodem
──────
An ancient protocol, included for compatibility's sake.  128 byte block
length and either Checksum or CRC-16 error checking (if the sender uses
Checksum, Icom uses Checksum; if CRC-16, Icom uses that).  Further, this
protocol does not pass filename, date/time or filesize information and thus
when downloading manually you must input the filename, making "batch"
transfers (transferring multiple files, one after the other) impossible.

Xmodem is considered inefficient due to its short block length (regardless
of the quality of the line and the lack of transfer errors) and due to the
fact that it waits for an Acknowledgment from the receiver after each
block.  Xmodem is also considered to be unreliable due to the fact that it
uses very simple (and unprotected) one-byte supervisory codes to
acknowledge blocks received intact, and blocks with errors.  If line noise
changes a NAK (Ctrl-U, negative block acknowledgement; a transfer error) to
an ACK (Ctrl-F, positive block acknowledgement; no errors), the sending
protocol will happily continue along, and won't re-send the erroneous
block.

Relaxed Xmodem
──────────────
The same as Xmodem, but uses longer 'timeouts'.	If you experience aborted
Xmodem transfers due to timeouts, use Relaxed Xmodem.	Again, batch
transfers are not possible with this protocol.

Xmodem-1K
─────────
Similar to Xmodem, but uses 1024 byte (1K) block lengths and CRC-16 error
checking.  One-byte, unprotected supervisory codes are used as with Xmodem,
and the protocol is still inefficient since it waits for an ACKnowledgement
from the receiver between each data block.  Filename, date/time, filesize
are not passed (no batch transfers) as with Xmodem.

Xmodem-1K-G
───────────
Identical to Xmodem-1K but this version assumes that an error-free link is
in use, and thus doesn't wait for an ACKnowledgement from the receiver
between each block.  CRC-16 error checking is performed, but since the
sender is not watching for acknowledgement (or negative acknowledgement)
after each block, there is no way to have a block RE-transmitted if an
error is detected.	Thus if an error is detected during an Xmodem-1K-G
transfer there is nothing that can be done about it other than to abort the
file transfer (which is what is done).	Identical to Xmodem-1K in every
other respect (no batch transfers, etc).

Ymodem
──────
A Ymodem transfer is similar to an Xmodem-1K transfer, except that Ymodem
passes the filename, date/time and size to the receiver eliminating the
need to input filenames manually, and allowing batch file transfers. 
Identical to Xmodem-1K in every other respect.

Ymodem-G
────────
A Ymodem-G transfer is similar to an Xmodem-1K-G, except that Ymodem-G
passes the filename, date/time and size to the receiver eliminating the
need to input filenames manually, and allowing batch file transfers. 
Identical to Xmodem-1K-G in every other respect.

Zmodem
──────
Zmodem eliminates the shortcomings in all the protocols mentioned above,
and is like night and day compared with the X/Ymodem breed.  Many pages
would be required to explain even half of the features in Zmodem, but
here's a quick summary:

■ The block size is automatically adjusted according to transfer speed and
line quality, from 1024 bytes (as Xmodem-1K/Ymodem) down to as low as 32
bytes.  If many transfer errors occur it is more efficient to use SMALL
block lengths; if few errors occur it is more efficient to use LARGE block
lengths.	Zmodem does this dynamically, monitoring the transfer as a whole
whereas X/Ymodem focus only on one block at a time, with no idea of the
overall transfer progress.

■ Adaptive error-checking techniques.  If line quality is good, Zmodem
behaves the same as Ymodem-G, sending block after block without waiting for
an acknowledgement from the receiver between each block.  If line quality
is poor, Zmodem adapts its error-checking techniques and may begin to wait
for acknowledgement after sending each block.  Further, Zmodem has the
ability to re-transmit from any position in the file whereas X/Ymodem can
only re-transmit the LAST block received (eliminating the 'getting out of
sync' problem mentioned above with Xmodem).	If X/Ymodem get out of sync,
the transfer aborts.  Zmodem can re-synchronize to any position in the file
-- Zmodem at the receiving end, after detecting an error 'tells' the sender
exactly what it needs to correct the situation.

■ Detailed supervisory information (reliable communication of errors and
the file position at which the error occurred) protected with CRC-16 error
checking whereas X/Ymodem use single byte supervisory information with no
protection.  If line noise distorts a Zmodem 'ACK' or 'NAK', the CRC
doesn't match and the other end thus knows it received a trashed
supervisory code and requests a re-send.

■ Batch transfers, and batch transfer information is available (total batch
length, number of files in the batch).

■ Crash recovery allows Zmodem to pick up an aborted download right where
it left off, whereas X/Ymodem must re-transmit the entire file.	"Smart"
crash recovery even runs a CRC-check on the existing portion of the file,
comparing CRC's with the sender, to ensure that the existing file portion
is identical.

In short, if you can use Zmodem -- do so.  Particularly for unattended file
transfers.
P-What is an external protocol?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
External protocols can seem quite mysterious to the uninitiated.  Which
external protocols will work with Intellicomm?  How do they work with
Intellicomm?  How does Intellicomm work with the external protocols?	The
answer to all these questions can be found by first understanding that
external protocols are completely self-contained "communications programs". 
They know nothing about the communications program that called them (they
don't have to, and actually they don't even need a communications program
at all in many cases) and the communications program usually has no idea
'which' external protocol it's calling.  The interaction between the
communications program and the protocol amounts to the following, which is
all passed to the external protocol's .COM or .EXE file on the DOS command
line, via a batch file:

 1.	Telling the external protocol which COM port to use.
 2.	Telling the external protocol what speed we're connected at.
 3.	On an upload, telling the external protocols which file(s) to
	transfer.  [On a download, most protocols pass the filename just
	before the file data itself, so they're not needed on the command
	line.]

With most external protocols, that's the extent of interaction between the
comm. program and the external protocol itself: COM port, speed, and files
to transfer on an upload.  External protocols need to know nothing else
about Intellicomm or any communications program.

The external protocol program then simply accesses the proper COM port when
it starts, and starts transferring the file completely on its own with no
interaction between it and Intellicomm for the duration of the transfer
(Icom isn't even running while the external protocol runs; it's "suspended"
and is totally out of the picture until the external protocol program ends
and returns control of the computer to Intellicomm).

Due to the way protocols work, whether internal or external, the BBS
doesn't start sending any real data until the RECEIVING protocol tells it
to do so.  So it matters not how long the external protocol takes to load:
Until the receiving end is ready, the "begin transfer" protocol signal will
not be sent to the BBS.	Only when the external protocol is ready to
receive (or send) does it tell the BBS to start the transfer (and vice
versa... many BBS's use external protocols as well).  There's nothing
mysterious about it, and it's no different than using an "external cup" at
a soda pop machine.  Until you press the lever, by putting the cup into
position, no soda pop comes out.  Protocols work the same way, whether
internal to the comm. program, or external in another .COM or .EXE file.  

Which external protocols does Intellicomm work with?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If you understood the above, you'll realize that Intellicomm (and any comm.
program) can work with ANY external protocol.  The comm. program is
irrelevant, and you don't even need a communications program to transfer a
file with an external protocol.  All Icom is doing is making the
connection, letting you enter a few commands to the BBS (or doing that
itself in automated mode), then calling the external protocol .COM or .EXE
either when you press [PgUp] / [PgDn], or when the "Begin your transfer"
message is received from the BBS.	For convenience, Icom passes the current
COM port and speed on the command line when it calls the external protocol. 
From there on out, until the transfer ends, Icom has nothing to do with
anything and the external protocol has complete control of the computer. 
The external protocol doesn't know that "Intellicomm" started it, and it
could even have been started by you from the DOS C> command prompt for all
it knows.  You CAN execute any external protocol from the command prompt
manually, and it may help you to better understand how to set up an
external protocol to actually run the protocol from the command line... 
All you have to do is make sure you pass the proper command line options
(COM port, and speed) to the external protocol program.  DSZ, the standard
X/Y/Zmodem external protocol program by Chuck Forsberg (inventor of Zmodem)
uses the following command line to receive a file using Zmodem:

DSZ.COM port 1 speed 19200 rz

This tells it: COM1, 19200 baud, and "rz" is just the way DSZ's developer
chose to specify 'r'eceive 'z'modem, just as ICOM.EXE has its own format
for its own Command Line Options.	Most other external protocols will only
support one transfer protocol in the .COM/.EXE (unlike DSZ.COM which
contains X/Y/Zmodem in a single file) and you won't have to use "rz" to
specify Zmodem.  You may have to specify "send" (upload) or "receive"
(download) though.	Further, 'port' and 'speed' and 'rz' are simply the way
DSZ's developer chose to specify those options.  Another external protocol
might require:

PROTOCOL.EXE baud19200 com1 /download

The only way to determine which command line format the external protocol
uses, is to read its documentation.  Each external protocol developer can
(and usually does) use different ways of specifying the port, speed, flow
control settings, and whether to upload or download, on the command line. 

The Interface
▀▀▀▀▀▀▀▀▀▀▀▀▀
Of course, you don't want to have to enter any of the tedious commands
above every time you transfer a file using the external protocol, so what
we do is to create DOS batch (.BAT) files that Icom can call when it needs
to access the protocol.	The batch files serve the purpose of running the
proper external protocol program (.COM or .EXE), entering the proper
command line parameters, for a particular external protocol, in the proper
order -- and that's all.  But instead of forcing you to 'hardcode' the
actual COM port and speed into the batch files, Icom instead passes the
current COM port and speed to the .BAT file when it runs the external
protocol program.  "Passes?", you say.	How does it pass this information? 
Read on.

Batch file tutorial
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If you somehow missed the chapter on batch files in the DOS manual
(intentionally or otherwise... <grin>) you'll have to understand one
concept before continuing below.  Note that this is standard batch file
stuff and it applies to any batch file, and has nothing to do with Icom or
external protocols specifically.

Most everyone knows that you can pass 'command line options' to .COM and
.EXE programs when you run them.	For example, Icom lets you run specific
jobs by typing something like this when you run ICOM.EXE:

	ICOM.EXE /run:"Send/Get Mail"

But did you know that you could pass command line parameters to batch
files?  If not, it's extremely relevant to using external protocols...
since Icom "communicates" with external protocols by passing command line
options to it, via batch files.  What does it communicate?	The current COM
port and baud rate being used (which the external protocol must know, or
they'll either open the wrong port or open it at the wrong speed), and on
uploads, the filenames to send.

To illustrate this "communication" between Icom and the external protocol,
let's say Icom typed this for you at the DOS command prompt:

C:>TEST.BAT 9600 1 FILENAME.EXT

Assuming TEST.BAT could be found by DOS (i.e. it was on the PATH or in the
current directory), DOS would execute it and would pass it three command
line parameters: the baud rate, current port number and a filename.

To access command line parameter 1, you use %1 in the batch file, %2 to
access the second command line parameter, %3 for the third, etc.  So if you
created a file called TEST.BAT and it contained the following:

	echo 1st: %1  2nd: %2  3rd: %3  4th: %4  5th: %5

And you (or Icom) ran TEST.BAT with the command line shown just above, it
would print the following to the screen:

	1st: 9600  2nd: 1  3rd: FILENAME.EXT  4th:  5th:

Get it?  DOS replaces the %1 in the .BAT file itself with the 1st command
line parameter you (or Icom) type on the command line, %2 with the second,
%3 with the 3rd, %4 with nothing (since no 4th parameter was specified) and
%5 with nothing (since no 5th parameter was specified).  If you don't
understand, just do what is outlined above and actually create TEST.BAT
(use Icom's Text Editor or DOS's EDIT.COM, etc).	Then, from the DOS
prompt, type in the command line illustrated above to run it.  You'll
quickly see what this is all about, and you'll also have gained some very
useful knowledge, since this applies to *all* DOS batch files making them
much more flexible.

Below are the two example commands we used to start the external protocol
programs earlier, followed by the proper .BAT file equivalents which use
the parameters (current port and speed) passed by Intellicomm, instead of
"hardcoding" the information right into the .BAT (remembering that the 1st
parameter Icom passes is the port speed/baud rate and the second is the COM
port Icom is using):

DSZ.COM port 1 speed 19200 rz
DSZ.COM port %2 speed %1 rz

PROTOCOL.EXE  baud19200 com1
PROTOCOL.EXE  baud%1 com%2

In both cases, the %1 is replaced (by DOS when it runs the batch file) by
the 1st parameter Icom passed (the proper port speed to use) and %2 is
replaced with the 2nd parameter Icom passed (the COM port Icom is using).

Also note above that the BAT file itself, simply due to the way batch files
work, is simply re-typing the commands for you no different than if you
typed them yourself at the DOS prompt.	And unless you place the external
protocol .COM or .EXE (the program itself; DSZ.COM and PROTOCOL.EXE above)
in a directory on your DOS PATH, you'll just get a "Bad command or
filename" error when the .BAT file attempts to run the external protocol
program.	If this happens, either copy the external protocol .COM or .EXE
into a directory on the PATH (type PATH alone at the DOS prompt to see the
directories on the path), or precede the command with the proper
drive/directory when you define the command in your BAT files:

C:\UTIL\DSZ.COM port %2 speed %1 rz

So where do the .BAT files go?  And How does Icom know which ones to use?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
You can either put the .BAT files that interface with the external protocol
in any directory on the DOS PATH, and Icom will find it there (DOS will
actually, when Icom tries to run the .BAT file).	Or, you can place the
.BAT files in the Icom home directory (where ICOM.EXE is).	Icom looks in
the home directory for the .BAT file first, and if it finds it there, it
sends the command:

	C:\ICOM\PROTOCOL.BAT <speed> <port> ...

instead of sending the command:

	PROTOCOL.BAT <speed> <port> ...

to DOS.  The first allows PROTOCOL.BAT to execute properly no matter which
directory DOS is currently in, since Icom has told DOS where PROTOCOL.BAT
is.	The second, with no directory at all specified, causes DOS to search
the current directory, then all the directories on the PATH (standard DOS
stuff, just as from the command line.  Icom calls COMMAND.COM to execute
the .BAT files, so the same rules apply as if you were sitting at the C>
prompt).

As to how Icom knows which .BAT files to use, this is the purpose the
External Protocol setup in the Icom main setup serves.  Please refer back
to External Protocols for the details.	And if you're still confused about
batch files, DOS prompts, paths, or anything else above, please refer to
your DOS manual or any good book on DOS basics.  You can find much more
detailed explanations and examples there that will benefit you in many
aspects of your computer use.
╫
The Comm Port Settings screen allows you to define the Base Address and IRQ
(Interrupt ReQuest line) for up to eight different communications ports. 
The Base Address and IRQ line of the port are what let Intellicomm access a
communications port on your computer.  The actual NAME of the comm-
unications port (COM1, COM2, etc.) is irrelevant: you can set COM1 to point
to COM4, COM2 to point to COM8; all Icom needs to access any port is the
Base Address and IRQ of the port.	By default, COM5 through COM8 point to
COM1: these are 'extra' slots that you can use as you see fit, if you have
the hardware to make use of them.

Where do you get the proper Base Address and IRQ settings?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The Base Address and IRQ information for your hardware can be found in the
technical manuals (or perhaps just on a single page stuffed into your
motherboard manual) that you got with your computer.  The COM ports are on
the circuit board known as the "Multi I/O Card".	Or, if you use an
INTERNAL modem, the Base Address(es) and IRQ(s) will be documented in your
modem manual.	Without the proper documentation, you cannot change the Base
Address or IRQ of the hardware, and you'll thus never need to use this Icom
setup screen.	Changing settings on this screen doesn't change your
hardware at all: you must change the hardware first (configure switches or
jumpers, as instructed in the documentation for your modem or Multi I/O
card) and THEN come to this screen to tell Icom about the changes you made.

Why would you want to change the Base Address or IRQ?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Changes can be made to the Base Address and IRQ settings of a given port to
avoid conflicts with other pieces of hardware.  Most Multi I/O cards and
internal modems allow you to change small switches or jumpers on the card,
to allow the COM port(s) to use different Base Addresses and IRQ lines. 
There are a limited number of IRQ lines in a PC computer and things such as
SoundBlaster cards, your mouse, and your modem must all use DIFFERENT IRQ
lines.  If you have two devices using the same IRQ line: one device will
always "steal" the IRQ line, leaving the other device with no access into
your computer.  This is a common occurrence with internal modems, since (by
design specification of PC hardware) COM1 and COM3 use the same IRQ line
(IRQ 4) and COM2 and COM4 use the same IRQ line (IRQ 3).  Thus, if you have
a mouse on COM1, a printer on COM2, and you try to configure your internal
modem to use COM3 -- your modem won't work, since COM1 and COM3 both use
IRQ 4, and your mouse (on COM1) is already using IRQ 4.

The solution is to get out your modem manual or Multi I/O documentation,
and configure COM3 to use a different IRQ line (or simply to use COM4 if
that option is available; it's okay to use a printer on COM2 and a modem on
COM4, since most times a printer doesn't actually "steal" the IRQ line that
it's connected to, unless something is being printed).  For example, you
might change COM3 to use IRQ 5 ... and then you can tell Icom about the
change you made by typing 5 in the COM3 IRQ setting.

IMPORTANT NOTE
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Both the Base Address and the IRQ must be entered in HEXADECIMAL.  The
documentation for your Multi I/O Card or internal modem should list the
available Base Address and IRQ values in hexadecimal only, or in both
hexadecimal and decimal.  Hexadecimal numbers use the letters a through f
(3f8, 2e8, etc), so they should be easy to spot.
╧3The Host Mode settings screen allows you to configure Intellicomm's
Host Mode to suit your needs.  Please see HOST.DOC for detailed information
on Intellicomm's Host Mode.

Sysop Name
▀▀▀▀▀▀▀▀▀▀
The name displayed to users when referring to the System Operator (Sysop)
of Intellicomm Host.  For example, if the user attempts to [C]hat with you
and you are not available, Host will display the message:

Sorry, the Sysop is not available.   OR...
Sorry, Joe is not available.		  OR...
Sorry, Joe Smith is not available.

You can define your first name, your first name and last name, or leave it
at Sysop.

Host Download Dir
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This is the D:\PATH that Level 1 callers are limited to for the Host
'[L]ist Files', '[F]ind a File', '[V]iew File', and '[D]ownload' commands. 
No other drives or directories are available to Level 1 callers.  Level 2
callers can access files on any drive in any directory.

Host Upload Dir
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The D:\PATH that all user uploads are placed in (Level 1 and Level 2
callers).

IMPORTANT: Some external protocols contain features which knowledgeable
callers could use to BREECH security Level 1 of your Host.	Please see
"Level 1 EXTERNAL Protocols?" below.

Level 1 Password
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The security 'Level 1' password.  To gain access to Intellicomm Host, all
users are prompted for a password.  If the Level 1 Password is entered, the
user will have access ONLY to files that are located in the 'Host Download
Dir' defined above.

To illustrate: When Host asks a Level 1 user for a filename to [V]iew,
[F]ind, or [D]ownload, any D:\PATH that the user precedes the filename with
is STRIPPED, and the 'Host Download Dir' is automatically inserted. 
Further, when '[L]ist Files' is selected, ONLY the files in the Host
Download Dir are displayed.  The Level 1 user is forced to deal with files
in the Host Download Directory, even if he or she knows the proper
D:\PATH\FILENAME.EXT for a file in another directory.

Level 2 Password
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The security 'Level 2' password.  If you define a password here, make sure
that it's a good long one, preferably made up of random characters, digits
and symbols so that no one will be able to guess it (or don't define a
Level 2 password at all, which disables Level 2 access remotely).  Level 2
users have access to every file on your computer: all drives and all
directories.  When a Level 2 user is asked for a filename to [V]iew or
[D]ownload, or is prompted for a filespec for the '[L]ist Files' command,
he may enter a full D:\PATH\FILENAME.EXT allowing access to all files on
the system.  Further, the '[F]ind a File' option allows Level 2 users to
search directories other than the Host Download Dir, and even allows
complete disk searches.

If you don't need this kind of remote access to your computer, don't define
a Level 2 Password at all, and remote Level 2 access will be disabled.

DOS Shell Password
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Even more critical than the security level 2 password is the DOS Shell
Password.  This password is prompted for if the user attempts to use the
'[E]nter DOS Command', '[S]hell to DOS', or '[N]ew Directory' commands.  If
the correct password is entered, the user effectively gains access to all
files on your computer ([S]hell to DOS, then COPY files from any D:\PATH
into the Host Download Dir), not to mention access to FORMAT, DEL *.*,
etc., etc., from the DOS prompt.  Even if you remove FORMAT.EXE and other
destructive programs, all the user has to do is [U]pload FORMAT.EXE, then
[S]hell to DOS and execute it.

The DOS Shell Password should ONLY be defined if you need remote DOS prompt
access to your computer, and again make sure you define a good password
that isn't easy to guess.  If you leave it blank and the user attempts to
access one of the DOS options mentioned above, he receives the message
"Sorry, DOS functions are disabled on this Host." and that's as far as he
gets.

Abort Host Password
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This password is prompted for when the '[A]bort Host' option is selected,
or when [A]bort is selected from the '[C]ontinue, [G]oodbye, or [A]bort'
prompt just before a file transfer begins.  Abort isn't terribly crucial:
all it does is cause the Host to abort itself when the user logs off. 
Abort is handy when someone accesses your computer late at night, or when
you're on your way out, and you don't plan to be around to shut the Host
down when the user finishes.	In such as case you can simply give the user
the Abort Host Password, and she'll be able to select [A]bort Host to shut
the Host down when she's finished.

Modem Init Host Command
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This command is sent to your modem after each caller disconnects, and also
to put your modem back on-hook (see next setting).

Modem Offhook Command
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This command (if any) is sent to your modem to take it "off-hook".  It is
used when you select an option such as 'DOS Shell' from the Waiting for
Caller menu, so that anyone who calls while you're shelled out will get a
busy signal.  When you return from the shell, the 'Modem Init Host Command'
is sent to the modem to put it back on-hook.

NOTE: According to the documentation for TriBBS, the telephone equipment at
some phone companies will flag your telephone line as OUT OF SERVICE if a
busy signal is detected for an extended period of time.  I.e. if you were
at the Waiting for Caller screen and picked "Shell to DOS" (takes the modem
off-hook), then something came up and you forgot to return to the Host...
your phone line may be out of service when you return and exit back to the
Host.  I have no idea where this is the case, since it didn't say in the
TriBBS docs; but if this troubles you, just remove the "Modem Offhook
Command" and your modem will remain on-hook while you're shelled out (i.e.
users who call will get a ring-no-answer instead of a busy signal).

Modem Answer Command
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This command is sent to the modem when the 'Modem RING Message' is
received.   ATA is the normal command, but if your modem uses something
different you can define the proper command here.  Then again, if your
modem uses ATA, you can leave it as is. ()

Modem OK Message
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The string that your modems returns when a valid command is entered.	"OK"
is the usual message.

Modem RING Message
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The string that your modem returns when it detects an incoming call.	RING
is the usual message, but if your modem returns something different
(DINGALING?) enter the proper response here.

Answer on Ring #
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Tells Intellicomm Host how many 'Modem RING Message' strings to wait for
before telling the modem to answer the call.  If you use your regular voice
line for Host calls, you could set this to 10 rings or the like, and
instruct people who call via modem to wait for at least 10 rings.  People
calling by voice normally won't wait for 10 rings... and thus they won't
get a modem screaming in their ear.  You can keep Intellicomm Host active
24 hours a day using this technique.

Main Setup File for Host
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This option allows you to use a customized main setup file for Intellicomm
Host.  This allows you to define custom External Protocols for use with
Host Mode (see "Level 1 External Protocols?" below; you may not want to
make certain external protocols available), or to shut off Zmodem crash
recovery, or to set "Delete Aborted Transfers?" to YES (File Transfer
Settings screen), or to define custom Filenames and Paths (i.e. a different
Capture Filename, or Usage Log filename, etc), or to shut off "Open Capture
on Connect", etc., etc.

Defining a Custom Main Setup File
─────────────────────────────────
To create a custom main setup file for Host Mode:

1. Enter the Intellicomm Setup, access the 'Host Mode Settings' screen and
enter "HOST" (no quotes) here in the 'Main Setup File for Host' option. 
Don't bother changing any of the other host settings since henceforth the
HOST main setup file (which you'll create in step 2) will be used for host
settings: not ICOM.INI.	Save your setup and exit Intellicomm Setup.

2. Access Intellicomm Setup again, and this time set everything as you want
it during Host Mode execution.  Then press [Esc] until you get to the 'Save
Setup' screen.  Instead of pressing [Enter] on ICOM (.INI), enter the
filename HOST to save the settings in HOST.INI.  Then, go back into the
Intellicomm Setup, select "Load a Setup File", and re-load your original
ICOM setup (or exit Intellicomm and re-start).

Henceforth, when Host Mode starts it will automatically load the settings
defined in HOST.INI, and will re-load the previous main setup file
(ICOM.INI) when Host Mode finishes.

Level 1 can OVERWRITE?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines what action Intellicomm Host takes when a Level 1 user attempts
to upload a file that already exists in the Host Upload Directory.  If
'Level 1 can OVERWRITE' is set to YES, the following menu is presented:

File already exists.
[D]elete file, [L]eave file (crash recover), [C]ancel:

I.e. the user is given the option to delete the existing file (overwrite it
with the new upload), leave the existing file for the protocol to sort out
(Zmodem or HS/Link crash recover, etc.) or cancel uploading that particular
file.

If 'Level 1 can OVERWRITE' is set to NO, the message 'File already exists.'
is displayed, no menu is presented, and the file is not accepted.

NOTE: Level 2 users are always given the option to [D]elete or [L]eave
existing files when uploading.

Level 1 EXTERNAL Protocols?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If set to YES, Intellicomm Host allows Level 1 callers to use all external
protocols defined on the main setup External Protocols screen (see 'Main
Setup File for Host' above to define custom external protocols for use with
Host Mode).  If set to NO, only Intellicomm's internal protocols are made
available to Level 1 callers.  External protocols are always available to
Level 2 callers.

Some external protocols contain features which knowledgeable callers can
use to breech the security of your Host.  On uploads, many external
protocols will accept a full D:\PATH\FILENAME.EXT allowing files to be
placed in directories other than your 'Host Upload Dir' -- possibly even
over-writing important files on your system.  When Intellicomm Host
executes an external protocol, complete control of your computer is (must
be) turned over to the external protocol, possibly putting your system in a
vulnerable position.  If you use external protocols, make certain that you
have read the external protocol's documentation carefully (particularly any
section discussing "Using the protocol on a BBS"; most external protocols
have such a section in the documentation) and have DISABLED any potentially
hazardous features.  See the tips below for more information.

Intellicomm's internal protocols, with no special setup work, provide much
more control than default external protocol setups do.  If a D:\PATH is
specified with an incoming filename, it is automatically stripped so that
files will ALWAYS be placed in your 'Host Upload Dir'.  Further, existing
files are never* overwritten (*see File Transfer Settings; you may want to
shut off Zmodem crash recovery in your custom Host Main Setup File), and
Zmodem's ability to execute DOS commands is disabled.	Yes, part of the
Zmodem specification is the ability to transfer a DOS COMMAND instead of a
file, and to have the receiver EXECUTE the command; this feature is also
disabled in the DSZ external protocol program, but it's a good example of
the 'potentially dangerous features' that are sometimes built in to
external protocols.

If security is an issue on your Host system, and you are not intimately
familiar with the external protocols you have set up in Intellicomm, it
would be prudent to set 'Level 1 EXTERNAL Protocols' to NO.

TIPS
────
If you wish to use different external protocols for Intellicomm Host than
you use for regular Intellicomm sessions, see 'Host Main Setup File' above. 
After you configure for a HOST main setup file, you can then set the
External Protocols screen (in HOST.INI) the way you want it... possibly
using different .BAT files with different options, or removing certain
external protocols entirely.

DSZ Tips
────────
When using DSZ as an external protocol for Intellicomm Host, use the
'restrict' command line option in your DSZ-D.BAT file:

DSZ port %2 speed %1 ha on restrict rz -mrr

'Restrict' causes DSZ to restrict incoming pathnames to the current drive
and directory (Icom Host changes to your 'Host Download Dir' before calling
external protocols), and prevents existing files from being modified or
overwritten.  'Restrict' also causes partially received files to be deleted
and refuses files using the names AUTOEXEC.BAT or CONFIG.SYS.

Direct CABLE Link?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Set to NO for modem use, set to YES for direct computer-to-computer cable
hookups (no modem).  When set to YES, Host Mode assumes a direct cable link
and it bypasses the host 'Waiting for Caller' menu, sends no commands to
the modem (since there is no modem to send commands to) and ignores the
state of the port 'carrier detect' signal (modem online/offline status).
.Please see File Tagger Introduction for general information on the
File Tagger.

File Transfer Speed [CPS]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The File Tagger displays the file Transfer Time in the split-screen report
of the currently hilighted file.  This transfer time is based on the
average CPS (Characters Per Second) you've obtained on all internal
protocol transfers you've done with Intellicomm.	And due simply to the
fluctuations in transfer speed that can occur from day to day, due to line
noise, etc., this "overall real average" may not be typical.  One bad day
can reduce your average CPS by quite a bit...  So here in this option, if
you know the REAL average CPS your modem gets, you can plug it in...
causing the Tagger to use this CPS rate instead of the 'real' (or unreal)
average.

Tagger Screen Size
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Icom itself must call BBS's ... and not all BBS's operate in an extended
line (more than 25 lines) video mode.  Further, Icom's main menu looks
funny in anything other than 25 line mode.  So this option allows you to
use extended 43/50 line mode only for the File Tagger (where it's quite
useful and looks fine), while leaving Icom itself in 25 line mode.  If you
do use more than 25 screen lines in the Tagger, you should consider
increasing the number of file description lines shown (next option).

Description Lines Shown
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines how many (if any) file description lines are shown in Tagger
browse mode.  If you set this to zero, the entire split screen report is
removed, and the Tagger looks just like the Icom v1 File Tagger.  If you
set it to any number from 1-8, then the bottom eight lines are reserved for
an extended split screen report (which takes up eight lines minimum).  If
you use an extended line video mode (see above), you may want to display
more than eight description lines... particularly if the BBS you call
frequently posts 10 and 12 line file descriptions.  To read descriptions
longer than will fit in the split screen report, simply "Edit" the record,
press [Up] arrow to edit the description, and browse through the long
description using [Down] arrow.  Press [Esc] twice when done.

Auto Hilight Bar Lock
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If on, the Tagger's top hilight bar (browse mode) "locks" at mid-screen
whenever the hilight bar is in that position.  You can release an auto-lock
by pressing the [Scroll Lock] key, and you can re-activate it by simply
moving the cursor (up or down) to the mid-screen position.	Alternatively,
if you prefer to lock the cursor in a different position, you can turn Auto
Hilight Bar Lock off, and simply activate it manually at the desired
position by pressing [Scroll Lock].

View Date Filters Noted?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines whether the Tagger "View Date" filters out Noted files or not. 
Tagged files are never filtered out by the View Date, and Noted files are
not by default.  But if you tend to keep a lot of older Noted files around,
you may want to turn this option on to avoid having to see all the noted
files every time you browse the catalog.

Duplicate Checking
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
On New Files Imports, the Tagger goes through quite a commotion when a
duplicate file shows up.  If the duplicate is for the same BBS, the
description length is checked (see below) and that's the end of it.  But if
the duplicate exists on another BBS, this "Duplicate Checking" option then
comes into play.  If off, duplicate files on multiple BBS's are ALL added
to the catalog, and it's up to you to sort them out as you see fit.  If on,
the Tagger compares the "D/L Priority" (download priority) set in each of
the BIFs "Bank/List" screens to determine which BBS is more desirable as
far as downloads are concerned.  If the duplicate BBS has a higher
priority, the existing record in your catalog is replaced with the new
duplicate record (again, checking file description lengths first).  If both
BIFs have the same (or no) priority, then the filesize is checked.  If the
existing file record in your catalog is smaller than the duplicate (by 1500
bytes; thus ignoring most BBS ads), then the existing record in your
catalog is replaced with the new duplicate record (checking file
description lengths first).

Use DOWNLOAD.NDX
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The duplicate checking mentioned above only works for filenames that exist
in your current download (NEWFILES or custom) catalog.  The DOWNLOAD.NDX
index picks up where the duplicate checking leaves off, and causes the
Tagger to ALSO ignore any files that exist (or did exist at one point) on-
disk, in a given set of directories (defined below).  This "Use
DOWNLOAD.NDX" option allows you to temporarily disable use of the index,
without deleting the actual DOWNLOAD.NDX file (\ICOM directory, if you do
want to delete it and start fresh) itself.

File .EXTensions in DNDX
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
File .EXTensions are always STORED in the DOWNLOAD.NDX (which simply is a
dBASE index containing nothing but filenames).  But this setting determines
whether or not you actually want to put the extension to use.  Do you want
ICOM200A.ARJ to show up in a future new files list, if you already
downloaded ICOM200A.ZIP (the same file, but simply using a different
extension)?  If not, then set this item to "No".	If you do want extensions
to 'count', and you want a file you already downloaded to show up in a
future new files list just because it had a different extension, set this
item to "Yes".

DOWNLOAD.NDX Directories
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
These are the directories the DOWNLOAD.NDX searches for new downloads in. 
Each directory defined should be on a separate line, and should contain the
full D:\PATH with no filespec.  Example:

C:\ICOM\GET
C:\TELIX\DOWNLOAD
C:\OZCIS\DOWNLOAD

Any/all files in all three directories listed above would be added to
DOWNLOAD.NDX, if they didn't exist in the index already.  Do not enter a
filespec:

C:\ICOM\GET\*.ZIP

Icom automatically appends *.* (and a trailing slash, if necessary) to each
line you define in "DOWNLOAD.NDX Directories", so the above would end up
as:

C:\ICOM\GET\*.ZIP\*.*

This would result in NO files in \ICOM\GET being added to the DOWNLOAD.NDX.

Filter Graphics Chars
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines whether IBM graphics characters are filtered (removed) from file
descriptions during New Files Imports.	BBS's are not the sole property of
IBM compatibles, and many BBS's run on Apple and other equipment that
doesn't support the IBM extended graphics characters.	Further, due to the
varying margins when entering file descriptions (auto-uploads) on different
BBS software, graphics characters often end up looking quite silly.  They
are most frequently used to place a 'box' around a given description to
make it stand out more... but in most cases the box/description will be
mangled as travels from BBS to BBS.  Even further still, in order to
perform accurate description length comparisons (see next), only "words"
should count.	A line of graphic characters isn't meaningful to most
people, and for all these reasons, Filter Graphics Chars defaults to "Yes". 
Do not turn it on unless you painted polka dots on the tree in your front
yard, have dingle balls hanging in the window of your car, and wear purple
pants with pink flamingos on them.
  
Replace Shorter Comments
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
After stripping all the double/triple spaces, removing all control
characters and graphics characters, and applying the
Strip Comment Keywords and Replace Keywords to all file descriptions the
Tagger sees, they're all pretty well "equal".  And when duplicate files are
found during New Files Imports, the descriptions of duplicates can be
compared against the length of the existing description in your catalog to
see which (if any) description is longer.  If Replace Shorter Comments is
on, a longer description will be "stolen" from a duplicate file, whether
the duplicate file itself is ignored (according to the usual duplicate
checking rules) or not.

Extract NEWFILES in QWK
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This setting determines whether Intellicomm attempts to auto-extract the
NEWFILES.DAT file (new files listing) from newly downloaded .QWK mail
packets.	QWK mail packets are almost always just renamed .ZIP files, and
to extract the NEWFILES.DAT, Icom creates and changes to a temporary
directory, then sends the "Main Unpack" command (defined on the
Filenames and Paths screen; defaults to PKUNZIP.EXE) followed by the packet
name, followed by the NEWFILES.DAT filename, like so:

PKUNZIP C:\READER\QWK\BBSID.QWK NEWFILES.DAT

If a NEWFILES.DAT exists in the QWK packet, this command will extract it
(and only it) and the NEWFILES.DAT file will then exist in the temporary
directory mentioned above.  If this is the case, Icom renames the file to
BBSID.NEW and moves it to the \ICOM\LST directory, for auto-import by the
File Tagger (see next setting).  If NEWFILES.DAT doesn't exist in the
temporary directory, the command is sent again, but the second time using
the "2nd Unpack" command.

If you never obtain new files listings in your QWK packets, this can be a
pain.  And you can shut the NEWFILES.DAT auto-extraction off here if you
like.

Auto Import New Files
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines whether the File Tagger imports \ICOM\LST\*.NEW (all new files
lists captured during the last automated job).  If you use something else
to process your .NEW files lists, you can shut this off.

Keep an Upload Catalog
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines whether the File Tagger maintains a FILELIST catalog.  The
FILELIST catalog keeps track of all files you auto-download, and also
allows you to Tag files for upload to other BBS's.

Purge Noted # Days Old
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This setting applies only to download catalogs (NEWFILES and/or custom
catalogs) and it determines whether and when Noted files are auto-purged
(deleted) from your catalogs.  If set to 0, Noted files are never purged. 
If set to any other number, Noted files that are older (in days; according
to the CATALOG DATE of the file) are deleted.

Purge Untagged # Days Old
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This setting applies only to download catalogs (NEWFILES and/or custom
catalogs) and it determines whether and when Untagged files are auto-purged
(deleted) from your catalogs.  If set to 0, Untagged files are never
purged.  If set to, for example 3, Untagged files that are older than 3
days old (according to their CATALOG DATE) are deleted.  Note that Tagged
files are NEVER auto-purged, and there is no auto-purge setting for Tagged
files.

Auto Pack when # Purged
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Both of the auto-purge items mentioned above do not physically remove files
from your catalog.	To physically remove file records, and free up the disk
space the records were using, a "Pack" (a rebuild of the catalog, minus the
deleted records) must be performed.  On large catalogs, Packs can take some
time, so this item allows you to determine when (if ever) the auto-pack
takes place.  It defaults to 30, which means that an auto-pack is only
performed once 30 or more records have been auto-purged.  It would be a
waste of time to pack an entire catalog, just to remove 1 or 2 records.

Auto Bookmark Update
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines whether the File Tagger automatically saves your position in a
given catalog when you exit the Tagger, or "Load" another catalog for
viewing.

Auto View Date Update
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This setting determines whether the File Tagger automatically sets a given
catalog's View Date to 'today' when it imports a .NEW files list to the
catalog.	If set to "Yes", the Tagger displays ONLY the records that were
imported on (or after) the last auto-View Date Update.  Please see
File Tagger Introduction for more information.
BSome of the largest BBS's in the world are using Intellicomm v2 to automate
their network mail transfers and file collection.  These BBS's formerly
used a combination of several programs to automate their mail runs and file
collection: they have been able to consolidate and use Intellicomm
exclusively, and more effectively than was ever possible before, with the
introduction of these Intellicomm v2 main setup options.

While these setup options were outlined and requested mainly by Sysops,
they are of use to non-Sysops as well, for organizing files.

Export D/L's to TEXT FILE
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This is the D:\PATH\FILENAME.EXT of a text file you want Icom to append
newly downloaded file records (name, date, size, description) to.  It's
intended to be used by BBS Operators mainly, to auto-update the BBS file
listings.  The format of the appended records (position of the filename,
size, date, description) is determined by the 'BIF Format for Export' item
below.

Export by ID/Conference
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If exporting all newly downloaded files to a single text file (the 'Export
D/L's to TEXT FILE' option above) is not suitable, turn this option on to
have Intellicomm export to filenames based on the BIF ID / conference the
file was downloaded from.  For example if Icom downloaded two files using a
BIF called JOESBBS; one file from conference 0 on JOESBBS and the other
from conference 1, Icom would export the file records to two text files:

	\ICOM\LST\JOESBBS.0
	\ICOM\LST\JOESBBS.1

[\ICOM\LST\ being the 'Filelist Dir' defined on the Filenames and Paths
screen, JOESBBS being the BIF ID, and .0 being the conference Icom
downloaded the file from.]  You can then append these files to the proper
conference file listing for your BBS.

BIF Format for Export
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This is the BIF format (BIF "Bank/List" screen settings) to use for the
export above (if any).  If you run a PCBoard system, you'd probably pick
one of the [PCBoard] BIF templates as the BIF Format for Export.  Please
see Automation in Detail for more information.

Move to Subdir
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This option allows you to define a D:\PATH\ in which Intellicomm will
create subdirectories based on the BIFID/conferences it downloaded files
from, to then move newly downloaded files into separated subdirectories. 
For example if you defined \TEMP in this option, and Icom downloaded the
following files:

	E:\ICOM\GET\FILE1.ZIP   [From JOESBBS, conference 0]
	E:\ICOM\GET\FILE2.ZIP   [From JOESBBS, conference 1]

Icom would create directories (if necessary) and move the files to:

	E:\TEMP\JOESBBS\0\FILE1.ZIP
	E:\TEMP\JOESBBS\1\FILE2.ZIP

[The Subdir you defined, the BIFID, then the conference the file was
downloaded from are used to create the subdirectory name.]	You can then
operate on the files separately, grouped by the BBS's and conferences
Intellicomm downloaded from; instead of having all files lumped in one
directory.  Note that the files are moved AFTER POSTFILE.SCR has done its
virus checking, so only files that are virus free are moved to the
subdirectories.  Note also that in order to perform a MOVE (instead of a
slow COPY) the 'Move to Subdir' directory must be on the same DRIVE (X:) as
the file(s) Intellicomm is moving.  Thus a drive letter (X:) must not be
defined in the Move to Subdir option: Icom will substitute the drive letter
based on the location of the file it is moving.

Don't set up any .BAT files to automatically handle new downloads, until
you perform an auto-download or two and are 100% positive of the
subdirectory names Intellicomm moves the files to.

Auto Tag Remaining Files
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If you use Intellicomm for automated file collection on your BBS, you may
also want to turn on the 'Auto Tag Remaining Files' option, which is on the
TAGGER KEYWORDS main setup screen.  If this option is on, Tagger
automatically tags all newly imported files -- meaning that Icom will
automatically download all new files (which you haven't previously
downloaded, and which aren't excluded due to the 'Exclude Keywords'), at
any BBS's you want.  Combined with the above options, a couple of .BAT
files, and Auto Tag Remaining Files, you may be able to leave Icom to run
your BBS, and go to Hawaii.  Please see Tagger Keywords for more
information.

More Support for Sysops
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Intellicomm also supports execution of PREJOB.BAT, POSTJOB.BAT (batch files
that are executed before and after all automated jobs) PREMAIL.BAT,
POSTMAIL.BAT (before/after jobs that performs a mail run), POSTFILE.SCR
(once per newly downloaded file; virus checking, etc., as included with
Intellicomm) and PREDOWN.BAT, POSTDOWN.BAT (before/after jobs that perform
an automated download).	Script versions of these files are also supported
for the ultimate in flexibility (PREDOWN.SCR, POSTDOWN.SCR, etc).  Please
see Automation in Detail for a full explanation.
Tagger Keywords are used by the File Tagger during New Files Imports. 
They're used to clean up file descriptions automatically, to point out the
types of files you're most interested in, and to exclude the files you
aren't interested in.  There are four types of keywords, stored in four
separate keyword lists:

	Strip Comment Keywords
	Replace Keywords
	Exclude File Keywords
	Note File Keywords

Auto Tag Remaining Files
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If you use Intellicomm for automated file collection you may also be
interested in the 'Auto Tag Remaining Files?' option which is also on the
main setup 'Tagger Keywords' screen.  If Auto Tag Remaining Files is set to
YES, Tagger automatically tags all newly imported files.  A 'newly imported
file' is a file that (a) doesn't exist in DOWNLOAD.NDX (previously
downloaded files); (b) doesn't exist in the catalog already; (c) wasn't
excluded by the Exclude File Keywords; (d) wasn't "noted" by the
Note File Keywords.  I.e. all files that would normally be UNTAGGED are
instead automatically TAGGED for download if Auto Tag Remaining Files is
turned on.  Great for Sysops: turn this option on, and Icom will collect
all new files that you haven't downloaded previously, and that don't exist
on your 'Exclude' or 'Note' keyword lists.
óLoad a New Setup File allows you to instantly change all the global
Intellicomm settings.  When you exit the main setup, you are permitted to
enter a filename (ICOM is the default filename given).  If you enter
another filename here, another main setup file is saved on-disk.  And you
can then load that main setup file either using this "Load a New Setup
File" option, or by using the /ini:FNAME command line option.
/Exit Setup options:

 ■ Press ENTER to RE-SAVE the setup file under the same name.

 ■ Press ESC to exit and ABANDON any changes you made.
 
 ■ Press   to CANCEL eXiting and return to the setup menu.

 ■ Enter a NEW FILENAME to save this information in a
   different setup file, then load that setup file.  Setup files
   can also be loaded using the 'Load a New Setup File' option
   (on the setup menu) or via the /ini:FNAME command line switch
   when you start ICOM.EXE.  This allows you to keep several
   main setup files handy, for use at any time.
7Before using Intellicomm for automated mail transfers you must first
"interface" it with your Mail Reader by defining two directories in the
Icom main setup, on the Filenames and Paths screen:

║ Reply Dir	C:\READER\MSG							    ║
║ Message Dir	C:\READER\REP							    ║

[The above two directories are just examples and you most likely will NOT
define those exact directories.]	The "Reply Dir" is where Intellicomm
looks for reply packets (created by your Mail Reader) to UPLOAD back to the
BBS mail system.  The "Message Dir" is where Intellicomm should place newly
DOWNLOADED mail, where your mail reader expects to find it.  Most Mail
Readers allow you to define these two directories in their own main setups
as well -- you must make sure that the directories defined in your Mail
Reader MATCH these directories defined in the Icom main setup.  That's
really all there is to interfacing Intellicomm with any offline mail
reader.  Of course you can also define your mail reader command in the Icom
main setup (same setup screen, just above the two directories outlined
above), to allow access to the reader from the Icom main menu and in
various other places:

║ Mail Reader> C:\READER\READER.EXE					    ║

This setting is optional and is not required by Intellicomm itself.  If
your Mail Reader is NOT on the DOS PATH, you must precede it with the
proper directory name as above.  If you use a .BAT to start your Mail
Reader (i.e. to perform a CHDIR or some other function prior to starting
the reader), define the .BAT file name instead of the .EXE name.

See also:
	PTR Uploads
▐
The Qmail, Rosemail, and Tomcat message systems support a .PTR file which
holds the settings of the message 'pointers' for all conferences you've
selected.  [If you don't use one of the above mail systems then this help
topic does not apply to you.]

The message pointers tell the mail system where to start looking for NEW
mail, in each message area, each time you perform a message download.   If
your message pointers are corrupted on the BBS or otherwise need resetting
for some reason, the .PTR file included in your .QWK mail packets can do it
in a jiffy with no manual labor on your part.  Message pointers *can* be
corrupted from time to time (it happens more on some BBS's than it does on
others) and by having Intellicomm upload this .PTR file prior to each new
message download, you can always be sure that your pointers are where they
should be, instead of one day getting the unpleasant surprise of several
megabytes of old mail.  Intellicomm has a feature which allows you to
upload this .PTR file just before each new mail download, which sets your
message pointers to where they were AFTER your last message download (i.e.
right where they should be for this new download).

It's simple to control uploading of the .PTR file: if Intellicomm finds it
in your Reply Directory, it uploads it.  If it doesn't find it, it doesn't
upload it.  Thus, if you don't want this file uploaded you can either tell
your Mail Reader NOT to extract it (many have a setting in the reader main
setup) or can use a .BAT file to run your reader:

Echo off
C:\READER\READER.EXE
DEL C:\READER\REP\*.PTR

Alternatively, you can use Intellicomm's PREMAIL.BAT file to delete one or
more .PTR files prior to automated mail runs if you like.  There is
absolutely NO reason to keep a .PTR file on-disk unless you intend to use
it (i.e. unless you intend to have Icom upload it for you).

IMPORTANT SETUP
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Qmail, Rosemail and Tomcat all handle .PTR uploads differently, and
Intellicomm determines which of its .PTR upload routines to use based on
the setting of this item on BIF screen #1:

║ BBS/Host Name  > The BBS		 Message Type	 > Qmail v4		    ║
							 ─────────────────────────

You must hilight and set this item to either Qmail, Tomcat or Rosemail for
Icom's .PTR uploads to work properly.

WHAT IF I DELETE THE .PTR, THEN NEED IT LATER?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
QWK mail packets are simply renamed .ZIP files and you can extract the .PTR
from the .QWK packet any time you need it, using your usual UNZIP program:

PKUNZIP BBSID.QWK BBSID.PTR


The above command extracts BBSID.PTR from BBSID.QWK.  If Intellicomm finds
BBSID.PTR (BBSID being the usual packet filename for the BBS) in your Reply
Directory, it uploads it, with no questions asked.  

If you are new to BBS's and are not familiar with offline mail readers and
offline mail systems as yet, please see BBSTUTOR.DOC, included with
Intellicomm, for more information.

Intellicomm can fully integrate with most any external mail reader.  All
that's needed for this integration is for you to tell both Intellicomm and
your reader to use the same directories for message and reply packets. 
Icom places newly downloaded mail in the Message Directory (Message Dir),
and it looks for replies to upload in the Reply Directory (Reply Dir). 
Both items are defined in the main setup, on the Filenames and Paths
screen.

║ Reply Dir  > C:\READER\MSG							    ║
║ Message Dir> C:\READER\REP							    ║

Your mail reader must be configured to LOOK for message packets, and to
CREATE reply packets in the same directories.  See your reader's main setup
for details.

Further, Intellicomm provides a Main Menu option for easy access to your
mail reader after automated mail runs.	All you must do is plug the command
you'd normally enter from the DOS prompt, to call your mail reader (again,
on the main setup Filenames and Paths screen):

║ Mail Reader> SW:C:\BAT\READER.BAT					    ║

It's often useful to use a .BAT (batch) file to call your reader, since it
allows you to perform a CHDIR command (necessary with many readers), and
also to perform any post-mail cleanup.	Here's an example READER.BAT:

C:\READER
READER.EXE
DEL C:\READER\REP\*.PTR

Of course C:\READER and READER.EXE would have to be replaced with the
proper directory/command to access your own mail reader.

Some QWK-compatible (Qmail-compatible) readers leave the ".PTR" (message
pointer information) file lying around, and unless you want Intellicomm to
upload this file to the BBS before your next mail run (which will have the
effect of making sure your pointers are where they should be; it does NOT
set them to where they were before the last transfer), you should delete
this file.  It doesn't hurt anything to let Intellicomm upload the .PTR
file, and in fact it can help you in many cases if the BBS message pointers
were corrupted somehow.	But many people choose not to waste the time
uploading the file, and if that's the case with you, just delete the file
or tell the reader not to leave it lying around in the first place in the
reader's main setup program.	Note that you can ALWAYS extract a .PTR file
from a .QWK mail packet, if it becomes necessary, just by using PKUNZIP:

PKUNZIP BBSID.QWK BBSID.PTR


QWK packets are simply renamed .ZIP archives.

The "SW:" preceding the Mail Reader command ensures that Intellicomm swaps
itself out of memory (to EMS, XMS or to disk) before executing the reader,
which leaves lots of free memory for the reader to work with.  If you omit
the SW: you may have problems running large external readers.

TIP: If you use a database-type external reader, and the reader offers a
command line switch (or external program) to "import" new mail, you can
have Intellicomm auto-import the mail for you after the mail run by using
Icom's POSTMAIL.BAT file.  If you perform your mail runs at night while
you're sleeping, when you wake up the next day all your mail will then be
ready to read!  Please see the remarks in POSTMAIL.BAT, and your reader
documentation for more details.

See also:
	Message Directories
	PTR Uploads

The Hotkey Menu is accessed by pressing [Shift-F1] (while OUTSIDE the help
system; [Shift-F1] gives you the Help Index while in the help system) from
any major Intellicomm area.  If you press [Shift-F1] and nothing happens,
you are in an area of Intellicomm where the hotkeys are disabled. 

You can use this menu until you learn the major Icom hotkeys ([Alt-M] to
return to the Main Menu for example), or permanently as a substitute for
learning the hotkeys.  You can also use it to view the current date and
time of day.
┐For more help on using this help system, press the [F1] key now or click on
the [F1] at the bottom of the screen.  For quick access to all major help
topics press [Shift-F1] (or click on the [Shift-F1] at the bottom of the
screen with your mouse) to access the Help Index.

Main Menu
▀▀▀▀▀▀▀▀▀
Icom's Main Menu gives you easy access to all other major areas of the
program and also lists usage statistics so that you can easily see what was
accomplished on the last automated run, as well as total usage information. 
See "Usage Statistics" below for more information.

Please select a Help Link below for more information about a specific Main
Menu option.  Press [F1] (Help on Help) if you don't know how to select a
Help Link:

╓─────────────────────────────╖
║	Job Directory			║
║	BBS Directory			║
║	Learn Modes			║
║	Script Manager 		║
║	Terminal				║
║─────────────────────────────╢
║	Mail Reader			║
║	File Tagger			║ ── [Browse New Files and Prior Downloads]
║	File Manager			║ ── [Review Session Captures]
║─────────────────────────────╢
║	Intellicomm Setup		║
║	Host Mode 			║
║	File Manager			║
║	DOS Shell 			║ ── [Registered Version]
║─────────────────────────────╢
║	ORDERING INFORMATION	║ ── [Evaluation Version]
║	Exit Intellicomm		║
║						║
╙─────────────────────────────╜

HOTKEYS
▀▀▀▀▀▀▀
The Main Menu also lists the HOTKEYS you can use to traverse the major
program areas without going through menus.  For example, you can access the
Job Directory from just about anywhere in Intellicomm by holding down the
[Alt] key and tapping the [R] key ([Alt-R]).  And though the hotkey is not
listed on the Main Menu, you can return to the Main Menu from just about
anywhere by pressing [Alt-M].

Note also that the Hotkey Menu (a pseudo Main Menu) is available from
anywhere in Intellicomm by pressing [Shift-F1] or clicking your right mouse
button (in most areas).	Until you learn the Icom hotkeys, you can access
this menu by pressing [Shift-F1] (while OUTSIDE the help system; you get
the index IN the help system) from any major Intellicomm area.  You can
also view the current date and time of day via the Hotkey Menu.

If the Hotkey Menu isn't displayed when you press [Shift-F1], hotkeys are
disabled in the area of the program you are in, and you'll have to exit
back to any 'major' program area and try again.

USAGE STATISTICS
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The Usage Stats (or Evaluation Stats if using an unregistered copy)
displayed at the Main Menu are there for your informational purposes only. 
Intellicomm does not monitor them in any way.  To reset the Usage Stats to
zero, press [Ctrl-S] (S for Stats) from the Main Menu.

With a communications program such as Intellicomm that does all the work
for you, it can be hard to gauge how much use you're actually getting from
the program.  The Usage Stats are designed to let registered users know how
much use they're getting out of Intellicomm for their money, and to let
unregistered users set goals to determine when to make the purchase.

Another important aspect of the Usage Stats is in seeing what was
accomplished during the last automated run.	Intellicomm clears the "New
mail packets downloaded", "New files available for D/L", and  "New
downloads waiting" stats prior to each automated run.	When you return to
your computer after the automated run, you can quickly see what's new by
checking the Usage Stats.  If one or more mail packets were downloaded,
(and if you have defined your Offline Mail Reader command in the Icom main
setup on the "Filenames and Paths" screen), you can then select
Mail Reader from the Main Menu to handle the new mail.  If new files are
available for D/L (new files listings were collected), you can select
"Browse New BBS Files" to browse them.	If new downloads are waiting (and
"Keep an Upload Catalog" is set to Yes in the main setup on the
File Tagger Settings screen), you can select "View Prior Downloads" to
check them out, and/or to Tag them for upload to other BBS's.
ÇWhen you exit Intellicomm, either by selecting "Exit Intellicomm" from the
Main Menu, or by pressing [Alt-X], you are presented with a menu of the
following options:

Yes
▀▀▀
Exits Intellicomm, returning you to DOS (or whatever called ICOM.EXE).  If
you are connected and attempt to exit the program, Icom will alert you and
ask whether you wish to disconnect or not.  If you select "No" from the
Disconnect menu, your modem remains connected AFTER Intellicomm exits (i.e.
you could then start another comm. program or tool and pick up the online
session).

No
▀▀
Cancels the exit request and returns you to whatever you were doing.

Pack
▀▀▀▀
This option is used to permanently delete JOBS (in the Job Directory) and
BIFs (in the BBS Directory) which are flagged as deleted.  A job/BIF is
flagged as deleted if it is displayed in the Job or BBS Directory with
brackets around it (you can undelete such items if necessary by hilighting
them and selecting "Delete" again).  When you select "Pack" from the exit
menu, these items are deleted permanently and cannot be recovered (deleted
entries in the BBS directory also delete the .BIF file from disk).
¡The Job Directory (hotkey [Alt-R]) is used to create, edit, execute, and
otherwise maintain your automated JOBS.

The @Temporary Job
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This job is meant to be used for those little temporary jobs you need from
time to time.	Instead of keeping dozens of little jobs on-disk that you
used once and may never use again, just "Edit" the @Temporary job entry!

Tag
▀▀▀
Tag is used execute multiple jobs with a single "Run" command (see below). 
When you Tag/Run several jobs, Icom builds a temporary job on-disk which
MERGES all the tagged jobs together one after the other, in the exact same
order in which they are displayed in the Job Directory.  There are a couple
of considerations for this type of job execution, namely job pauses (which
delay a job until a specific day/time), Exits to DOS in jobs, and Repeat
tasks which repeat the entire job.  In order to gain a good understanding
what Icom will do when you Tag multiple jobs, you must PICTURE the tagged
jobs as a single job, all merged together in the same order as they're
displayed in the Job Directory (this is exactly what it looks like to
Intellicomm when it runs the job).

Icom handles multiple dialing pauses by locating the pause that is nearest
to "now".  If today is Friday, and it is 12:00pm, Icom looks for the pause
that is nearest to Friday at 12:00pm and starts the job there.  Once the
first pause elapses, the job executes until Icom runs into another pause. 
I.e. several BBS's could be called if no intermediate pauses intervened. 
Again, picture your job as a single job merged together and you'll get no
unexpected surprises.  Once the next pause is found, the process begins
again and Icom looks for the pause that is nearest to "now" and again
begins executing the job at that point (a pause is considered "execution of
the job"... a pause is just another job task to Intellicomm).

"Exit to DOS" and "Repeat Job" tasks are ignored until *all* other job
tasks are finished (or removed from the queue due to error).  If both an
Exit to DOS and Repeat exist, the Exit to DOS is ignored and the entire job
repeats.	If no repeats exist, and any of the Tagged jobs had an Exit to
DOS task in them, Icom exits to DOS once all jobs are complete.

Run
▀▀▀
Executes the currently hilit job (if none Tagged) or all Tagged jobs.  Once
"Run" is selected you can usually leave.  Icom does everything from dialing
to logoff unattended.  Note that you can also "Run" jobs by using the /run:
command line switch.  See Command Line Options for details.

Two notes: To stop a job prematurely, the best bet is to use the [Alt-Z]
terminal menu (look on the right side of the terminal status line if you
forget the key... it says "[Alt-Z] for Menu" there).  The very first option
on the menu is the "Job and Script Control Menu" (the hotkey is [Alt-Q] ...
Q for Quit).  Select the Control Menu, then pick "Abort Job/Script, switch
to manual" to abort the job and switch to manual.  [Note that a Job and a
Script are two different things... By selecting Abort Job/Script you abort
both the job AND any script that might also be running (scripts can be
called from automated jobs).	If you select "Abort Script only" then only
the script is aborted (if one is running) and the automated job continues. 
Please see Script Language and SCRTUTOR.DOC if you're curious about what a
script is, and what they can do for you.

Alternatively if you just have some work to do online and would like to
TEMPORARILY switch to manual, use [Alt-G] (G for Goto Manual ... this item
is also on the Terminal Menu, just under the Control Menu option if you
forget the key).  You can then choose to go to manual NOW, or to have Icom
page you when it finishes its automated work at this BBS.  In either case,
press [Alt-G] again (or simply log off the BBS) to return to automatic
mode.

Find
▀▀▀▀
Find is not really designed to help you find a job... the Job Directory
normally won't hold so many jobs that you'll 'lose' a job.	Rather, Find is
used to allow you to quickly tag (or untag) a group of jobs.  For example,
assume you have three jobs called "Send/Get Mail - BIFNAME", where BIFNAME
is three different BIFs for three different BBS's.  To quickly Tag all of
these jobs, select "Find", enter "Send/Get Mail" (no quotes) when asked
what to search for, then pick "Find all/Tag all" and all three jobs will be
tagged for you!  Pick "Run" and you're done.  Similarly, if you make a
mistake you can use the same technique to UNTAG jobs.	If you repeated the
above process, all the jobs that were previously Tagged would be Untagged.
Since performing a "Find", then "Find all/Tag all" and selecting "Run" is
exactly what the /run: command line switch does, you can also test out
various /run:"search strings" using Find | Find All/Tag All.

Create
▀▀▀▀▀▀
Create is used to create a new job.  After selecting create you are
immediately asked to "Select" a BIF to call, and then you enter the
Job Editor to create a new job.

Edit
▀▀▀▀
Edit is used to view or modify an existing job.  Hilight the job of
interest before selecting Edit.

Delete
▀▀▀▀▀▀
Flags (or unflags) a jobs "deleted" status.	If a job is flagged as
deleted, it will have brackets around the description in the Job Directory. 
To undelete a job you inadvertently delete, just hilight it and select
"Delete" again.  To physically (and permanently) delete the job, select
"Pack" when you Exit Intellicomm.

Untag
▀▀▀▀▀
Untags all tagged jobs (if any).

BBS Dir
▀▀▀▀▀▀▀
Switches you to the BBS Directory where you may dial BBS's for manual
sessions, and otherwise maintain your BIFs.

Terminal
▀▀▀▀▀▀▀▀
Changes to the Terminal for direct modem access.	To return to the Job
Directory from the Terminal, the best way is to press [Alt-R] (the Job
Directory hotkey).	Alternatively you can call up the Terminal's menu with
[Alt-Z], select eXit from the Terminal menu, then pick "Job Directory" as
the area to exit to.

Tools
▀▀▀▀▀
Calls up a menu of useful secondary functions.  Most of the functions on
the Tools menu are available from the Main Menu, but Icom v1 didn't have a
Main Menu and The Job Directory was the Main Menu in Icom v1.  The Job
Directory Tools menu was maintained mainly for Icom v1 users.

DOS
▀▀▀
Accesses the File Manager.

eXit
▀▀▀▀
What eXit will do depends from whence you came.  If you came from the Main
Menu, eXit returns you to the Main Menu.  If you came from DOS (i.e. if you
have changed the program startup area to the Job Directory in the Icom main
setup) then eXit calls up the Exit Intellicomm menu.
=For general information on the Job Editor, please see:
	Job Editor Introduction

Job Editor Menu Options (bottom menu)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

BBS
───
This first option lets you insert a "Call Some BBS" task in your job at the
position of the Job Hilight bar (to have Icom call multiple BBS's per job,
or to add a Call to a blank job).	You can also insert a "Switch to another
BIF" task in the job to simply load a new BIF without disconnecting.	When
you select "BBS" you are asked whether to disconnect or not, and if you
answer "Yes", then a new "Call" is assumed, if you answer "No" a "Load new
BIF" is assumed.  You are then prompted for the new BIF to Call or Load.

Why would you want to load a new BIF while connected to the same BBS?  The
possibilities are numerous, but the usual reasons are to download mail from
two or more different message systems (i.e. multiple mail doors, possibly
for different BBS message networks), or to capture new files listings and
import them into separate File Tagger Catalogs (registered users only). 
Once you are more familiar with BIFs and jobs you'll probably find at least
one case where you'd like to use multiple BIFs for the same BBS.

Edit
────
Allows you to modify data (if any) in the job task at the hilight bar. 
I.e. if you had previously entered a Dial starting time and want to change
the time and/or day, hilight the task and select "Edit".

Delete
──────
Removes the job task at the hilight bar, and pulls any tasks below the
hilight (if any) up.

Clear
─────
Clears the entire job, after confirmation.  This is mainly of use for
TEMPORARY jobs, to quickly clear out the last set of temporary tasks. I.e.
if you keep a @Temporary job in the Job Directory (the @ sorts it near the
top of the Job Directory for quick access), you can Edit it for those quick
custom tasks, using "Clear" to clear it out when you enter the Job Editor.

Description
───────────
Allows you to change the job description without exiting the Job Editor. 
You can also modify the description when you eXit.

eXit
────
Displays the job description for editing (or for entry, if creating a new
job).  Press [Enter] to save the job, press [Up] or [Down] to cancel the
eXit and return to the Job Editor, or press [Esc] to exit without saving
the job.

Job Tasks
▀▀▀▀▀▀▀▀▀
To insert one or more job tasks at the position of the job hilight bar,
type the number beside the job task.  This will display an entry line where
you can insert multiple tasks (i.e. use 1-5 to insert tasks 1 through 5 all
at once).  Mouse users can simply click on the task to insert it at the
hilight (click in the job window to move the hilight).

For information on a job task, please select one of the following help
links:

	Set job starting day/time
	Bank Withdrawal
	Send message replies
	Get all new mail
	Get new files list
	Upload tagged files
	Download tagged files
	Bank Deposit
	Get personal mail only
	Change BBS/File Areas
	Search BBS for files
	Custom Command/Run script
	DOS Command/Run a program
	Go to terminal mode
	Capture on/off
	Repeat job
	Exit to DOS
e
Set job starting day/time
─────────────────────────
To have Intellicomm pause a job until a specific day/time (midnight every
night, 4am on Tuesday, etc.), you must enter the details in your job.  To
add a pause to a job you must first load the job into the Job Editor (if
your job is already loaded, proceed to the next step).  To do so, press
[Alt-R] to access the Job Directory, then either select "Create" to create
a new job, or "Edit" to edit an existing job.

Once in the Job Editor you must move the job hilight in the job (right-
hand) window TO the "Call" you wish to pause, then select task 1 by either
pressing 1 or clicking on the "Set job starting day/time" task in the left
window with your mouse.	You'll then be prompted for the day/time to pause
until, and the pause will be inserted into the job.  Here's an example of
what the finished product should look like:

	Pause job until 1:00am on Everyday
	Call Sound Advice
	  Get new files list
	  Download tagged files

The 'Pause' task must be directly ABOVE the Call you wish to pause.
If you ran this job before you went to sleep (or left the office),
Intellicomm would wait until 1am and then call Sound Advice, pick up the
new files list, and download all tagged files.  "Everyday" means you can
run the job on any day of the week, and Intellicomm will simply wait until
the time specified, ignoring the day.  If you enter a specific day,
Intellicomm will wait for the day AND time you defined before placing the
call.  Here's an example of a job with multiple "Calls" in it:

	Call BBS #1
	  Send message replies
	  Get all new mail
	Pause job until 5:00am on Tuesday
	Call BBS #2
	  Upload tagged files
	  Download tagged files

If you ran this job, Icom would immediately call BBS #1 and send any
message replies then get the new mail and disconnect from BBS #1.  It would
then pause until 5:00am on Tuesday, then call BBS #2 and upload/download
any tagged files (if any are files tagged... if not, the call would be
redundant and Icom would cancel that call).

NOTE:  The Job Directory allows you to Tag/Run several jobs at once, and
Icom processes job pauses in a special way if multiple pauses are
encountered.	The way Intellicomm runs multiple jobs is to temporarily
merge all the jobs you tag (in the same order as shown in the Job
Directory) into a single job.  It then runs that single temporary job.  If
multiple pauses are found, Intellicomm waits for the pause that is nearest
to the current day/time, then performs that job (along with any "Call"s to
other BBS's that follow, as long as those jobs don't contain their own
pauses).	Then the next pause is processed in the same way, and so on until
the job completes.	Imagine the jobs you tag as a single job merged
together and you should have no unexpected surprises.

TIP:  Knowing the above, you can change the way jobs are sorted in the
Job Directory by preceding certain job descriptions with an exclamation
mark or other symbol to sort it to the top, to get the pauses (in the jobs)
sorted the way you want.  A better way in many cases though, assuming you
only need a pause from time to time on various jobs, is to define a job
that contains nothing but a pause, sort that entry to the top in the Job
Directory (call the job "@Pause until <day>/<time>" or the like, with a '@'
to sort it to the top), then just Tag that job with other jobs whenever you
want a pause to take place.
±Bank Withdrawal
───────────────
This job task can only be used if (a) the BBS has a Time Bank, and (b) you
have set up the BIF "Bank/List" screen (the "Bank" portion of it).  [Time
Banks are usually "DOORS" on BBS's, and they allow callers to store unused
online time and/or unused download bytes, for withdrawal on a later day.]

If the Time Bank accepts deposit/withdrawal of "download bytes" as well,
you can also have Icom handle these.  If not, enter 0 when asked how many
bytes to withdraw.
Send message replies
────────────────────
If message replies exist, they are uploaded to the message system, then the
reply packet is renumbered to avoid duplicate uploads of the same packet. 
Please see Automated Mail Runs for more general information on reply
uploads.
LGet all new mail
────────────────
This task uses the BIF "Message" section, and the "Get Mail" protocol
defined on the BIF "General" screen, to get new BBS mail.  You can either
have Icom capture mail to a text file (by using the ASCII protocol), or
download a compressed mail file such as those produced by Qmail, Tomcat,
etc.  To set Icom up for mail downloads, either use BIF Learn, or enter the
BIF Editor, select "Message Type" (column 2, screen 1) and pick the proper
message system from the menu.

Please see Automated Mail Runs for general information on message
downloads.
╒Get new files list
──────────────────
This task should only be used when there is no better alternative.  Most
QWK-compatible message systems (Qmail, Tomcat, etc) allow you to download
both the mail AND all the new BBS files *compressed* in a single file,
which shortens the transfer time.	Icom will extract the new files from the
.QWK file after it is downloaded, and will import the files into the File
Tagger.

The "Get new files list" task simply sends this command, on the BIF "File"
screen:

║ New Files  . . . N S U NS			 Enter U/L Fname			    ║
  ─────────────────────────

(The command might be something other than N S U NS... that's the usual
PCBoard command.)  You must make sure that the command defined displays the
new files in NON-STOP mode, without displaying a "more" prompt... or Icom
will answer "No" to the more prompt as it always does, and you won't get
all the new files.	If you can't stack commands as above, add the non-stop
command after a CR (N^MC  ... would send N [Enter] then C for
[C]ontinuous).

The new files are capture to \ICOM\LST\<BIFID>.NEW, where <BIFID> is the
filename of the BIF in use.  The File Tagger looks for \ICOM\LST\*.NEW
after all automated jobs and imports/deletes any lists found.
┴Upload tagged files
───────────────────
Transfer any files tagged for upload (in the File Tagger FILELIST catalog)
to a specific BBS.	Please see Automated Uploads for detailed information.
┘Download tagged files
─────────────────────
Transfer any files tagged for downloading (in the File Tagger NEWFILES or
custom catalog) from a specific BBS.  Please see Automated Downloads for
detailed information.
αBank Deposit
────────────
See Bank Withdrawal if you need details on this one.  This is the
complement to Bank Withdrawal, and it deposits unused online time and/or
download bytes (usually at the end of an automated job).
0Get personal mail only
──────────────────────
If the BBS's mail system supports this, and if you have the proper command
defined in the BIF on the "Message" screen:

║ Personal Read  . P			    Receive Success 			   ║
  ──────────────────

(the command may be something other than 'P' in your mail system) the "Get
personal mail only" task can then be used to obtain only your personal mail
(as opposed to all new mail).  If you request a Personal mail transfer and
no "Personal Read" command is defined in the BIF, Icom performs a General
read (all new mail).

Change BBS/File Areas
─────────────────────
This task can be used for custom work, to have Icom either change BBS Menus
(from the Main Menu to the Message Menu for example, or vice versa) or to 
change BBS message/file areas (to change conferences/forums).  To change
BBS conferences/forums, just enter the new conference number.

║ 10  Change BBS/File Areas		  │	 New Area: 2				   ║

To carry out this BBS/File area change, Icom will replace the percent sign
in this BIF Response with whatever conference # you enter in your job (BIF
"File" screen):

║ Area Change	. . J % Q 			 File More  . . . More? «	   ║
  ──────────────────────

Using the two examples above, Icom would send the command "J 2 Q" (no
quotes) to join conference/forum 2.  The % above in the BIF "Area Change"
command was replaced with the 2 from the job task.  Use whatever format the
BBS uses when you enter your New Area.	If the BBS uses conference/forum
NAMES instead of numbers, that's what you use in your job:

║ 10  Change BBS/File Areas		  │	 New Area: ICOM			   ║

Changing BBS Menus
──────────────────
To have Icom change BBS Menus you must enter one of the following as the
area to change to (including the square brackets):

[L]		Change to the BBS Logon Menu (Main Menu).
[M]		Change to the BBS Message Menu.
[F]		Change to the BBS File Menu.
[B]		Change to the BBS Bank Menu.

Example:

║ 10  Change BBS/File Areas		  │	 New Area: [L] 			   ║

The above would ensure that Icom was at the BBS Main Menu before it
continued the job (normally you'd use this prior to a "Custom Command" or
script which was designed to run from the BBS Main Menu).  Such menu
changes assume that the menu prompt is defined in the BIF, as well as the
command needed to ACCESS the sub-menu, as well as the command needed to
EXIT sub-menus (each major BIF section contains slots for this
information).	So, if Icom was at the BBS Message sub-menu (or DOOR), and
it ran into the "New Area: [L]" task above, it would first send this
command to the BBS (BIF "Message" screen):

║ Leave Msg Menu . Q				Message Pause	.			   ║
  ──────────────────

Then it would wait for either of these BBS prompts (BIF "Logon" screen):


║ Startup Command					Main Menu A  . . Board Command? « ║
║ Logoff . . . . . G				Main Menu B  . . rence Command? « ║
								────────────────────────────────

Once the basic information is plugged into a BIF, you can do all sorts of
interesting things using the Change BBS/File Areas, Capture on/off, and
Custom Command/Run script tasks.  All without script programming, of
course.
âSearch BBS for files
────────────────────

Prompts for a search string.	When online, Icom sends the "File Search"
command, defined on the BIF "File" screen, replacing the percent sign with
the text you entered as the search string:

║ File Search	. . Z^M%^MA NS 	   Enter D/L Fname				   ║
  ───────────────────────────

The above is an example of a PCBoard command ([Z]ippy Scan, [Enter], your
search text, another [Enter], then [A]ll file areas, in Non-Stop mode.

Icom captures the results to \ICOM\LST\<BIFID>.NEW (same as new files)
where <BIFID> is the name of the current BIF.  The Tagger will import these
lists for viewing, if found.
}Custom Command/Run script
─────────────────────────
Allows you to send custom commands to the BBS during an automated job, or
to run a script (use @SCRIPTNAME to run a script, where SCRIPTNAME is the
filename of the script).  Up to 150 characters can be entered allowing
multiple commands to be sent with a single Custom Command (see notes
below).

These commands can be used in combination with the other custom tasks
(Change BBS/File Areas, Capture on/off, etc) to handle things such as
capturing BBS bulletins or file listings, etc.  The following special
characters can be used in Custom Commands:

 ^	Allows specification of a control character.  ^M (Ctrl-M) is [Enter],
	^[ is [Esc], etc.  See ASCII Codes for details.  To send multiple
	commands with a single Custom Command for example (assuming the BBS
	requires [Enter] after each command), you might use

	Command 1^MCommand 2^MCommand 3"

	in your Custom Command.	Do not FOLLOW the Custom Command with ^M if
	the 'CR w/Commands?' (Carriage Return with Commands) item is set to
	YES on BIF screen 1.  When CR w/Commands is on, ^M is automatically
	added to the end of Custom Commands.  To check the BIF CR w/Commands?
	setting (if necessary), move to the 'Call BBS Name' task in the job
	and select "Edit".

 ~	Causes the Custom Command to pause for one second of BBS inactivity
	before sending the next character.  Again this is of use between
	commands "Command 1^M~~Command 2 ..." to let the BBS catch up between
	command entries.  If you specify 1 tilde (~) Icom waits for 1 second
	of BBS inactivity before sending any further portion of the Custom
	Command.	If you specify five tildes (~~~~~) Icom waits for 5 seconds
	of BBS inactivity before continuing.  ['BBS inactivity' means that the
	BBS has stopped sending data; usually meaning that it's waiting for
	further input.]

 ||	Two vertical bars cause Icom to pause and wait for a BBS menu prompt
	(Main Menu, Message Menu, File Menu, or Bank Menu) before continuing. 
	When displaying BBS bulletins or file lists, etc., you'll almost
	always want to have Icom wait for the BBS menu before it continues
	with any further jobs (or logs off).  Add two vertical bars to the end
	of your command to do so.  Again, if 'CR w/Commands?' (Carriage Return
	with Commands) is set to YES on BIF screen 1, ^M ([Enter]) is
	automatically added to the command portion before ||.	For example, if
	CR w/Commands? was on, and you defined a Custom Command of:

	  B 1 NS||B 2 NS

	Icom would send "B 1 NS^M" ([Enter]) then wait for a BBS Main Menu. 
	Then "B 2 NS^M" would be sent.

	To check the BIF CR w/Commands? setting (if necessary), move to the
	'Call BBS Name' task in the job and select "Edit".

NOTE: Immediately after the Custom Command finishes, Intellicomm attempts
to locate its position on the BBS, readying for the next job task (or
logoff).	If you use neither || nor tildes (~) after your Custom Commands,
you may return control to Intellicomm too SOON, and Icom may interrupt the
job that your Custom Command was performing.

For example, if you wanted to capture a large file listing with a Custom
Command, and you simply used "F 1 NS" ([F]ile Area 1, Non-Stop) without
following the command with either || (wait for a menu) or ^M~~~ (send
[Enter] to enter the command, then wait for a few seconds of BBS inactivity
while the command completes); very shortly after sending the command,
Intellicomm would attempt to locate its position (likely before the file
list had been fully displayed) and would keep trying; interrupting the file
list capture each time.	At best, Intellicomm would cancel the File listing
and continue with the next job task.  At worse, the file listing would keep
right on going, until after 3 tries Icom would finally give up (being
unable to locate its position on the BBS) and disconnect.  Keep this in
mind when you define Custom Commands, and make sure that you don't return
control to Intellicomm prematurely.
zDOS Command/Run a program
─────────────────────────
Normally this will be used before the first "Call Some BBS" task, or after
the last online task, to handle some sort of pre or post-job setup work (be
aware that Icom also supports several .BAT files for this purpose:
PREJOB.BAT, POSTJOB.BAT, PREMAIL.BAT, POSTMAIL.BAT, PREDOWN.BAT,
POSTDOWN.BAT.	These files, if they exist in the \ICOM home directory, are
executed before/after a job, before/after a mail run, and before/after a
Automated Downloads).

However you could even call another communications program or tool using
this task, while online, to handle some special work.
ÅGo to terminal mode
───────────────────
Causes Icom to sound a pager every ten seconds, for up to two minutes,
until you return to the computer.	If you return and press a key, Icom
switches to manual terminal mode to let you interact with the BBS manually. 
When you've finished your manual work, either logoff the BBS, or press
[Alt-G] to return to automatic mode (see the terminal [Alt-Z] menu if you
forget the [Alt-G] key... it'll say "Return to automatic" on the menu).

If you fail to return and press a key within the two minutes, the "Go to
terminal mode" task is cancelled and Icom continues with any other jobs
task and/or calls to other BBS's.
wCapture on/off
──────────────
This task allows you to open a new capture file during an automated job, or
to close the current capture file at a specific point.

If you specify a new capture file in this task, Icom opens the file (when
running the job) and starts capturing BBS output to the file.  If no
capture file is specified in this task, Icom closes the capture file.
₧Repeat job
──────────
Use this task when you go on vacation or otherwise will be away from your
machine for a few days, weeks, or months.  It repeats the entire job on a
specific day (or every day) at a specific time.  If you add a Repeat do NOT
add a "Pause job" (task #1).	See the notes in the Job Directory under the
"Tag" help for information on what happens if multiple Repeats (or pauses)
are encountered.
░Exit to DOS
───────────
This task causes Icom to exit to DOS (or to whatever called ICOM.EXE) when
the job completes.	Yes, Icom will logoff the BBS before carrying this task
out... In fact if it an error occurs and Icom can't hang up on the first
try, it'll try again... and again, and again, until hell freezes over or
the connection is broken (or you return to your machine and unplug it),
whichever comes first.

If multiple jobs are Tagged/Run, Icom also saves the Exit to DOS until all
other jobs have finished.  Exit to DOS is also ignored if a "Repeat job"
tasks exists.	See the notes in the Job Directory link under the "Tag" help
for information on multiple Exit to DOS tasks.
5General Information
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The Job Editor is accessed by selecting "Create" (create a new job) or
"Edit" (edit an existing job) from the Job Directory.	Jobs, in combination
with one or more BBS Information Files (BIFs) are used for automation of
BBS sessions.

In the Job Editor there are three things to notice, and three new terms to
learn: the JOB TASKS are listed in the box on left side of the screen; the
JOB itself (which you are editing or creating) is on the right side of the
screen; along with the JOB HILIGHT BAR.  The JOB EDITOR MENU, runs along
the bottom of the screen.

The Job Hilight Bar
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
First, let's cover the job itself in the upper left box.  You will notice
at least a "Call Some BBS" task in the job box, and also a hilight bar
which you can move with the [Home], [End], [Up] or [Down] arrow keys (or by
clicking your mouse at the desired position).  When you add a job task, or
use the Job Editor menu along the bottom, it affects the job AT THE
POSITION OF THIS HILIGHT BAR.  Thus, if you want to delete a certain job
task, you move the hilight bar over the task, then select "Delete" from the
bottom menu.  To edit a job task, move the hilight bar to the task FIRST,
then pick "Edit", etc.  If you want to insert a new job task somewhere in
the job, move the hilight to the position you want to insert at, then enter
the job task number, etc.  

Job Tasks
▀▀▀▀▀▀▀▀▀
Next, let's briefly cover the JOB TASKS listed on the left side of the
screen.  Intellicomm has built-in routines that know how to perform all the
tasks listed.	However, most of the routines (Get all new mail, for
example) depend upon correct BIF information to get the job done.  BBS's
all do things differently, and even BBS's that run the exact same software
(PCBoard, for example) can operate differently from one BBS to the next,
due to the unfortunate practice of Sysop customization.

Thus there is no way for Icom's built-in routines to automate BBS tasks
using constant (hardcoded) data.  The BIFs tell Icom's built in routines
what they need to know to automate whatever it is you need done.  It's up
to you to ensure that if you ASK Icom to automate something, that you've
already done the proper BIF setup (i.e. used BIF Learn to fill in the data
for that particular BIF area).  For example you should not add "Send
message replies" or "Get all new mail" tasks to a job UNTIL you have set
the BIF "Message" screen up since Icom uses the information in that BIF
section to automate mail runs.  You should not add "Get tagged files" tasks
until you've set up the BIF "File" screen, and you should not "Get new
files listing" until the BIF "Bank/List" screen is set up.	Each BIF
screen/section serves a specific purpose... and is directly connected to
the automated tasks you see listed in the Job Editor.

See also:
	Job Editor
¿The BBS Directory is used to Dial BBS's for manual online sessions, and
also to create, edit and otherwise maintain your BBS Information Files
(BIFs).  [Alt-D] is the hotkey to access the BBS Directory, which is the
standard hotkey in most all communications programs to access the dialer.

The @Temporary BIF
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This BIF is meant to be used when you get a new BBS telephone number, and
you want to place that first telephone call (using "Dial" ... see below) to
take a look.  It is quite common for BBS phone numbers to change, or to go
out of service, etc.  Also, not all BBS's are to all people's liking.  You
may logon for the first time and find that the BBS just isn't for you.  By
using the @Temporary BIF to place that first call, you won't have to create
then delete a BIF each time you call a new BBS.

NOTE: The @Temporary BIF should *never* have a Logon Password defined in
it.	If you define a password, that's the signal to Intellicomm to attempt
an AUTO-LOGON upon connecting after "Dial"!	And letting Icom attempt an
auto-logon is simply not a good idea when logging on to an unknown BBS for
the first time.  Leave the "Password Answr" item BLANK in the @Temporary
BIF.

TIP: Remember that when logging on to a BBS for the first time, you can
press [Alt-1] to send your logon name, [Alt-3] to send your Street Address,
etc. (as long as you've defined the proper information on the Icom main
setup User Settings screen).	Also remember that [Alt-Y] pops up the BIF
Notes.  In the @Temporary BIF, you might use the BIF notes to keep track of
the specific password you used to log on to the last new BBS you called. 
If you write passwords down on a piece of paper.... you might lose the
paper.

Tag
▀▀▀
Toggles the tag status (Tagged/Untagged) of the currently hilit BIF. 
Tagged BIFs have a large arrow () to the left of their descriptions.

In the BBS Directory, Tag is used to Tag/Dial several BBS's.  If the first
tagged BIF dialed is 'busy', then the dialer cycles to dial the next tagged
BIF, leaving the 'busy' BBS Tagged.

Dial
▀▀▀▀
Dials all Tagged BIFs, or the currently hilit BIF if none are tagged.  Note
that while BIFs (when combined with automated jobs) have the capability of 
automating BBS calls, you certainly don't *have* to use them for that
purpose.	If you like, you can define nothing more than the BBS/Host name,
telephone numbers and port settings in BIFs (the usual information you'd
define in a comm. program dialing directory), and use "Dial" to dial them. 
Icom's dialer is quite full-featured and provides the same functionality
(or better) as you'll find in general comm. packages.	Also see the
"Manual" option below, which can also be used to dial.

If you have problems dialing, see Common Questions & Answers and
Setup Problems for possible solutions.	See Dialer for full details on the
dialer.

Find
▀▀▀▀
As with the Job Directory's "Find" option, this is not intended solely to
be used to help you find 'lost' BIFs.  A main use of this item is to easily
tag a number of BIFs for dialing by using the "Find all/Tag all" feature. 
There are several tricks you can use to get various BBS's tagged using
Find.  One is to put special a special symbol in the BBS/Host Name item of
the BIF (this is what is displayed in the BBS Directory, and is what "Find"
searches) such as $, %, !, etc.  If you put ! in four BIF descriptions, to
dial all four you'd select "Find", enter ! when asked what to search for,
then pick "Find all/Tag all".  All the BIFs with a ! would then be tagged
and you could pick "Dial" to dial them.

Create
▀▀▀▀▀▀
This option enters the BIF Editor allowing you to create a new BBS
Information File.  But don't select Create until you have *hilighted* the
BIF you want to use as your starting point.	Normally you will hilight one
of the templates first (the BIFs at the end of the directory with square
brackets around their descriptions, which hold the proper information for
various BBS types), before selecting Create.  The [Blank Template] allows
you to start with a clean slate (i.e. it contains no BBS prompts or
responses).

Edit
▀▀▀▀
Used to view/modify the BIF (or template) that is currently hilighted.  See
BIF Editor, or access the online help after selecting Edit while in the BIF
Editor for full details.

Del
▀▀▀
Toggles the deleted status of the currently hilit BIF.  When a BIF is
flagged as deleted, its description is enclosed in brackets in the BBS
Directory.  To UNdelete a BIF marked as deleted, simply hilight it and
select "Del" again.  To physically remove the BIF description from the BBS
Directory, AND to delete the .BIF file on-disk, use "Del" then press [Alt-
X] to exit Intellicomm and select "Pack" from the exit menu.  Note that
Pack also deletes any JOBS that are marked as deleted in the Job Directory.

Untag
▀▀▀▀▀
If all tagged BIFs get untagged, then you had BIFs tagged.	If nothing
happens, then you didn't have any BIFs tagged.  (?)  Well, you asked...  

Learn
▀▀▀▀▀
Pops up the Learn Modes menu, to either learn a new BIF or (if you're a
registered user) to have Icom write a script for you.

Terminal
▀▀▀▀▀▀▀▀
Enters the Terminal for direct modem access.  This option can actually be
quite handy for those times when BBS's hang up, and call you back to verify
your telephone number.  When this happens, Icom will automatically switch
back to the BBS Directory.  At this point, simply select "Terminal" to get
back to terminal mode and wait for the BBS to call back.  Of course, the
terminal also has a hotkey you can use to get to it ([Alt-M]), and if you
forget the hot key you can also use the Hotkey Menu.

Manual
▀▀▀▀▀▀
Allows you to dial a number without creating a new BIF first.  Use this
when you first get a new BBS telephone number, just to verify that the BBS
is still operational and is still at that number.  If you connect, Icom
will switch to manual terminal mode just as if you had dialed via a BIF,
and you can then carry out your initial logon on the BBS manually.  If the
BBS is to your liking, THEN you can go ahead and create a BIF, either using
the BBS Directory "Create" option discussed above, or using BIF Learn,
whichever you prefer.

Read
▀▀▀▀
This option causes Icom to read the BIF Directory (\ICOM\BIF), extract the
BBS/Host Name item from all the BIFs, and build the BBS Directory.  This is
done automatically when Icom detects a new BIF, or after a Pack via the
[Alt-X] menu, but if for some reason your BBS Directory is damaged or
otherwise seems to need rebuilding, use this option.

eXit
▀▀▀▀
Exits the BBS Directory back to wherever you came from, if practical, or
back to your usual startup area otherwise (the Main Menu, Job Directory...
etc., whatever you've defined in the main setup).

See also:
	BIF Editor
	Dialer
	Automated Logons
┤The "Select a BIF" menu is displayed when Icom needs a BIF for some purpose
(to insert a Call in an automated job, etc).  Usage of this menu is quite
involved and it should not be used while on heavy medication:

 1.	Hilight the BIF of interest by using [Up], [Down], etc (the keys
	listed on the screen).

 2.	Press [Enter] or click on "Select" with your mouse to select the BIF.

 3.	Sorry, there really is no 3.	You're already done.
BIF Editor

If you are editing your BIF after a BIF Learn session and would like to
refer back to the tips that were displayed previously, please see 
Finishing up after BIF Learn.  If you're new to Intellicomm and are not
familiar with BIFs as yet, please see BIF Overview and BIF Setup Tips.
BIFs are the key to reliable automated calls and it's important that you
understand the basics.

ACCESSING THE BIF EDITOR
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The BIF Editor is accessed through the BBS Directory (hotkey [Alt-D], D for
"D"ialing Directory) and is used to create a new BIF or to view/modify an
existing BIF.	To create a new BIF, hilight the BIF template you wish to
use as a starting point (or the [Blank Template] to start fresh), and
select "Create".  Or hilight a BIF and select "Edit" to view/modify an
existing BIF.

GETTING AROUND IN THE BIF EDITOR
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
BIFs are organized into seven different sections on six screens, plus
optional notes you can attach for general information about the BBS.
Two hilight bars appear on each BIF screen:	The top hilight bar is used to
select an item to "Edit" (press [Up], [Down], [Left], [Right] or click your
mouse to move the top hilight), while the bottom hilight bar controls
actions such as "Edit" or "eXit", and allows you to change screens or view
the BIF Notes.

■ The BIF General Settings screen holds general information such as the BBS
telephone numbers, the transfer protocols you use on the BBS, and general
automation settings such as the timeouts.  You can also import a new Bank
or Message Template file (to set up for automation of a different
bank/message system) via the "Message Type" and "Bank Type" items.  Note
that you're free to set up ONLY the BBS/Host Name and telephone numbers and
use a BIF for manual sessions just as you might use the phone book in a
general comm. package.  To dial a BIF set up in this way, use the BBS
Directory's "Dial" option.  As long as you do not define a "Logon Password"
on the BIF Logon Screen, Intellicomm will not attempt to auto-logon the
BBS, and will simply connect and leave you online in Terminal mode for a
manual session.

■ The BIF Logon Screen holds the information necessary to complete
automated logons.

■ The BIF Message Screen holds the information necessary to automate mail
transfers.  You can change this screen to the proper prompts/commands for
various mail systems very easily by using the "Message Type" option
mentioned above on the General screen.

■,The BIF Bank/List Screen is two sections on one screen: the "Bank"
settings hold the information necessary to automate BBS Time Bank
transactions, while the "List" settings hold information about BBS file
listings, which the File Tagger uses for New Files Imports.


■ The BIF File Screen holds all the information necessary to automate file-
related tasks such as BBS New Files scans and file SEARCHES, as well as
file uploads and downloads.

■ The BIF Extras Screen allows you to define miscellaneous BBS prompts and
commands for the various tasks listed above.  These Extra prompts are meant
to handle the "stupid" BBS prompts, which probably shouldn't exist on the
BBS in the first place, such as "Enter your Birth Date", "Enter your Home
Phone Number", etc., (to verify that you aren't an imposter... though no
BBS I know holds national secrets that warrant this kind of security, and
your Logon Password really should suffice).

To exit the BIF Editor, select eXit from the bottom menu or just press the
[Esc] key.  A box will then pop up allowing you to save your changes to
disk, or to exit without saving your changes.

See also:
	Automated Logons
	Automated Mail Runs
	Automated Downloads
	Automated Uploads
	Automated Bank Transactions
	─────────────────────────────
	BIF Overview
	BIF Setup Tips
3A BIF 'response' is text defined in the BIF which sends one or more
commands (responses) to the BBS.  BIF responses are in the left-hand column
of the BIF Editor:

║ Your Logon Name  Siouxie Que	   Name . . . . . . st Name? «	    ║
			    ───────────
During an automated logon, if Intellicomm found the text "st Name? " from
the BBS, it would send the response Siouxie Que.

But there's lots more you can do with BIF responses (if the need arises)
and the following special characters may also be used:

 Character					What it does
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
	^		Allows you to specify a control character.  This will
			normally be used to send multiple commands with a single
			response (^M is [Enter]), or to send [Esc] (^[).	For
			example, you might have to send multiple commands to access
			the Message Menu: M^MOPEN^M5	 This sends 'M', then OPEN,
			then 5, each followed by [Enter].	See ASCII Codes for a
			list of all the ^ characters.  NOTE: to send a single caret,
			use two (^^).
	~		Causes a one second pause (presumably to let the BBS catch
			up).  You might use this before a response (~Siouxie Que),
			or after a ^M (Siouxie^M~Que), etc.  Note that you can also
			set a global "Response Delay" on BIF screen 1 to pause
			Intellicomm for some amount of time (in tenths of a second)
			before EVERY command, if necessary.
	&		Allows you to execute a script command (&DOWNLOAD "Z").  See
			Script Language for all the details.  You'll be limited by
			what you can do with this due to the length of the BIF
			response fields (20 characters or less).  Use the next item
			if you can't use this one.
	@		Allows you to run a script (@SCRIPTNAME).  The script can be
			a single command that wouldn't fit in the BIF response
			field, or can be a multi-line program that accepts user
			input and performs an entire online session.  Whatever you
			need.
	$		Allows you to execute another DOS program, a .BAT file, or a
			regular DOS command ($MYPROG.EXE, $MYBAT.BAT, $DEL
			AFILE.EXT, etc).  This could be used to call an external
			protocol program (perhaps in one of the BIF "Extra" slots),
			or even another communications program.  Note that if the
			external program you run won't load due to a lack of memory,
			you should precede the command with SW: (Swap) which causes
			Intellicomm to swap itself out of base memory before running
			the external program.  Example: SW:MYPROG.EXE  By default,
			Intellicomm does NOT swap itself out of memory if you are
			connected (see the main setup screen, "General" settings...
			you can change the default if need be).

Note that in order for &, @ or $ to work, it must be the FIRST character in
the BIF response.  If you precede any of them with any other character, the
text is treated literally and will be sent to the BBS.  If you must use &,
@ or $ as the first character of a regular BIF response (i.e. if you want
it sent to the BBS), escape the character with a caret (^&, ^@, ^$).

The CONNECT COMMAND
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

Sometimes you'll have to send a response to the BBS (or run a script, etc)
*before* Intellicomm begins its automated logon.	This is what the BIF
"Connect Command" (BIF screen 1) is for.  This command is often used to
send [Esc] characters to BBS's which require [Esc] to be pressed twice
before the logon begins:

║ Dial Prefix	. . 1			   Connect Command	^[~^[		    ║

The above sends [Esc], pauses for a second, then sends another [Esc].  The
pause between [Esc] characters is necessary on some BBS types.

SPECIAL CONSIDERATIONS
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Intellicomm automatically adds a 'Carriage Return' (CR; same as pressing
[Enter]) after regular BIF responses (not &, @ or $) if this item on BIF
screen 1 is set to Yes:

║ Phone Number   >				   CR w/Commands? . Yes			    ║
							   ────────────────────
If the BBS uses hotkeys (i.e. if it accepts commands without [Enter]) then
CR w/Commands may be set to NO, and in this case you must specify ^M to
send [Enter] when necessary:

║ Pause Answer . . ^M			   Pause	. . . . . er) to continue«   ║
			    ──
Do NOT do this if CR w/Commands is set to Yes, however, or Intellicomm will
send *two* CR's (one for the ^M, and another due to CR w/Commands), which
may foul up the next BBS prompt.  To send [Enter] when CR w/Commands is on,
use a single space character as the BIF response.
à&Many of the common BIF and other Icom setup problems are outlined in the
Common Questions & Answers and Setup Problems links.  This screen covers
BIF setup tips in more detail, for tricky situations.

GENERAL BIF PROMPT TIPS
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The most important thing to understand about the BBS prompts you plug into
your BIFs is that you do NOT have to define the entire BBS prompt, and the
prompt does not have to match at the end of the line.	You can define text
from the start of the BBS prompt, the middle, or the end ... wherever you
can manage to find UNIQUE constant text.  During automated jobs,
Intellicomm checks for matches of the relevant BIF prompts after EVERY
CHARACTER received from the BBS, and not only at the end of each line of
received text.  For example, if you're trying to automate batch downloads,
and the BBS displays something like this when prompting for filenames:

Enter file #1: ICOM201A.ZIP
Enter file #2: ICOM201B.ZIP
Enter file #3: ...etc.

The proper text to define in the BIF would be this:

║ File Search	. .				   Enter D/L Fname	Enter file #«	    ║
											────────────
You simply eliminate the variable portion of the prompt.

UNIQUE PROMPTS
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
It is also important that you choose UNIQUE text when defining BIF prompts. 
For example, the password prompt below will probably work on any BBS:

║							  Password . . . . password«		   ║

...since the word "password" is very likely to show up in the BBS logon
prompt that asks for your logon password:

What is your password?
Enter your password:
Password please>

...etc.  HOWEVER, the word "password" is *also* likely to show up in BBS
logon news: in reminders to change your password every once in a while,
information about "hackers" who logged on and stole the BBS password list,
etc.  If such a logon bulletin is displayed, Intellicomm will SEND YOUR
PASSWORD every time it runs across the word "password" in the logon news
(up to 3 times total; Icom gives up sending your name/password after 3
tries during a logon).  And this could completely foul up the auto-logon
process.	Thus, rather than just finding the "easiest" text to define in a
BIF prompt, it is a much better idea to find UNIQUE text, and particularly
PUNCTUATION, where possible, when defining BIF prompts.

ANSI CODES
▀▀▀▀▀▀▀▀▀▀
Many BBS's use ANSI codes to move your cursor around, and to change the
color of the text displayed on your video display.  Intellicomm's
"tracking" routines (the routines that watch for BIF prompt matches)
completely ignore these ANSI codes, and thus it is important that you ALSO
omit portions of any BBS prompts where you suspect ANSI codes (color
changes are fine; it's only the cursor movement codes you have to watch). 
For example, PCBoard BBS's display something like this when asking for your
password:

Password (Dots will echo)? (			)

The second bracket, however, is put where it is by an ANSI screen code.  If
you defined something like this in the BIF:

║							  Password . . . . )? (			)«  ║

...Icom would never match it, since it strips the ANSI codes before looking
for prompt matches (again, don't worry about color codes; just suspected
cursor movement codes).	Thus it is best to leave OFF portions of prompts
where you suspect such ANSI codes might be used.	The most you could define
of the above password prompt (the right-most text) is:

║							  Password . . . . dots will echo)? (« ║

But you needn't include EITHER of the brackets to get a match:

║							  Password . . . . will echo)?«	 ║

The above prompt contains enough punctuation, and is unique enough, that it
would work fine.

BIF RESPONSES
▀▀▀▀▀▀▀▀▀▀▀▀▀
BIF Response(s) are defined in the left-hand column of the BIF Editor and
either respond to a given BBS prompt (Enter Logon Name for example) or they
send a command then WAIT for a BBS prompt (Access Msg. Menu, etc).  There
are three important BIF Command features you should be aware of:

 1.	You can send MULTIPLE BBS commands with a single BIF response.
 2.	You can pause the command sequence (usually between commands, to let
	the BBS catch up) anywhere in a BIF response.
 3.	You can run a script (to handle anything imaginable) in any BIF
	response.

Feature 1 simply requires ^M (signifies [Ctrl-M], which is the same as
pressing [Enter]) in the command ... Or if the BBS accepts commands without
[Enter], it may simply require a pause between commands.  Here's an
example:

║ Access Msg Menu> M^M~OPEN^M~5	   Message Menu . . Message Menu:«     ║

It may look like a mess, but this causes Icom to send "M" and [Enter] to
access perhaps a [M]essage sub-menu, then pause for one second, then send
OPEN and [Enter], then another pause, then "5" (no enter is needed at the
*end* of any BIF response, if "CR w/Commands?" is set to "Yes" on BIF
screen 1).  Using this technique you should be able to handle most any
situation.  However, if it's not enough you can write a script (see
Script Language), or have Intellicomm write the script for you with
Script Learn, and plug the name of the script into the BIF response,
preceded by '@':

║ Access Msg Menu> @ACSMENU.SCR	   Message Menu . . Message Menu:«     ║

If @ is the first character of a BIF Response, Intellicomm runs a script
instead of sending a hard-coded response.  This would only have to be done
in rare cases, when you cannot get the job done with the usual BIF Response
procedures.  ACSMENU.SCR might do something like this to access the BBS
Message Menu:

;ACSMENU.SCR
SEND "M"				 ;sends 'M' to the BBS (same as typing M on the
					 ; keyboard in Terminal mode)
WAITFOR "Some prompt:"	 ;pause the script to wait for a specific BBS
					 ; prompt
SEND "OPEN"			 ;send another command
WAITFOR "Another prompt:" ;wait for yet another prompt
SEND "5"				 ;send yet another command (OPEN door #5)
;end here and return to Intellicomm where Icom will then wait for the text
; "Message Menu:" as defined above in the BIF example.

The above script does basically the same thing as the previous BIF Response
example did (sends "M^MOPEN^M5" to access the Message Menu) but it handles
it in a more controlled manner, pausing between each command and WAITingFOR
a specific BBS prompt between each command.	Using SEND and WAITFOR in
scripts, then plugging the @SCRIPTNAME into the BIF, you can handle even
the most complex BBS commands, when necessary, without forsaking the entire
BIF concept.

The same goes for all the other BIF responses, including all the responses
to the prompts defined on the BIF "Extras" screen.  No matter what you run
across, no matter HOW complex a task is, you can accomplish virtually any
task, anywhere, using the tips above and some creative thinking.

BIF "MENU" PROMPTS
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The BIF Menu prompts are on the "Logon", "Message", "Bank", and "File"
screens:

║ Startup Command				 Main Menu A  . . Board Command? «     ║
║ Logoff . . . . .				 Main Menu B  . . rence Command? «     ║

║ Access Msg Menu				 Message Menu . . <COMMAND>«		    ║

║ Access File Menu				 File Menu  . . .				    ║

║ Access Bnk Menu				 Bank Menu  . . . ] Command? «	    ║

[The actual prompts defined above are just examples.]	These prompts all
work in basically the same way, and actually Intellicomm uses a single
routine to access (and leave or logoff) all BBS menus and sub-menus.	The
process is simple: Icom first finds the proper "Access XXXX Menu" slot in
the BIF, depending on the job it's about to automate (Get Mail, Download
Files, Deposit time in the bank, etc., all may require access to different
BBS sub-menus).  If no command is defined Icom assumes it can carry out the
task right from the BBS Main Menu, and that's what it will attempt.  If a
command IS defined, then it sends the command and begins watching for ALL
the menu prompts listed above (and also begins tracking the proper "Extra"
prompts for the area it's trying to access).

As soon as it finds a menu prompt it recognizes (any of the five listed
above), it checks to see whether the text matches the menu we were looking
for ... and if so, the next automated task (Get Mail, etc) continues.  If
not (i.e. if we ended up back at the Main Menu, or Icom THOUGHT it had
ended up back at the Main Menu due to a conflict in the menu prompts), Icom
prints a message stating "Unable to access sub-menu/DOOR" and it tries
again.  Thus, if you define "Access XXX Menu" commands, you MUST define a
BBS menu prompt to the right of the command (it needn't be right on the BBS
command line; the text can show up anywhere from the time the Access Menu
command is sent until the BBS sub-menu/door is waiting for a command), AND
the prompt you define must be unique when compared to all the other menu
prompts that are defined.  This is absolutely necessary for reliable error-
handling.

As an example, some BBS's display the exact same command line prompt at ALL
menus something like this:

File Menu:    <-- Unique Text
[D]ownload    [U]pload	  [N]ew Files	  [L]ocate a File
[P]age Sysop  [M]essages   [Q]uit		  [G]oodbye

Your Command? _

The prompt "Your Command?" might be used at every single BBS menu and sub-
menu, but ABOVE that the text "File Menu:" is unique and identifies the
particular menu.  In such a case it's fine to do this:

║							 Main Menu A  . . Main Menu:« 	    ║
║							 Main Menu B  . .				    ║

║ Access File Menu F			 File Menu  . . . File Menu:« 	    ║

Intellicomm would send the "Access File Menu" command, and start watching
for "File Menu:".  When found Icom then waits for a short period of
inactivity at the BBS to ensure that the full menu is displayed and that
command prompt is ready for input.  Even if no text such as "File Menu:"
exists, you could even use one of the menu options, such as "[D]ownload" as
the File Menu prompt -- as long as the text is unique and only shows up at
the BBS File Menu.
`See BIF Editor for general information on using the BIF Editor.

The BIF General Settings screen holds the BBS telephone numbers, as well as
most of the "global" information used throughout automated sessions.	It
also allows you to instantly configure Intellicomm for various Message
Types and Bank Types.

This BIF screen can be considered the "dialing directory" entry screen, and
it can be used in much the same way as the regular dialing directory in a
general communications program: Start with the [Blank Template], Fill in
the BBS name, the phone numbers, the port settings, dialing prefix, and the
default protocols, leave it at that, and you can use "Dial" from the
BBS Directory to use Intellicomm just as you'd use a general comm. package! 

General Settings
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

 ───────────────────────────────────   ───────────────────────────────────
 BBS/Host Name: The name of the BBS    Message Type: Edit this item to see
 or host (Joe's BBS, etc).  This is    the various message types Icom
 displayed in the BBS Directory.	    knows.  Fills in all the prompts/
							    responses on the BIF "Message"
							    screen.
 ───────────────────────────────────   ───────────────────────────────────
 Phone Number: The main telephone	    Bank Type:  Edit this item to see
 number for the BBS/Host (see 	    the various bank types Icom knows. 
 Enter Phone Number).			    Fills in all the prompts/responses
							    on the BIF "Bank/List" screen.

 ───────────────────────────────────   ───────────────────────────────────
 Phone Number:  An optional second     LD Service: Long-distance service
 number to dial for the same BBS (if   to dial through to connect to this
 multi-lines). 				    BBS.	See Long Distance Services.

 ───────────────────────────────────   ───────────────────────────────────
 Phone Number: An optional third	    City/Address: The PC-Pursuit CITY,
 number to dial for the same BBS.	    or address to iNet from Datapac. 
							    See Long Distance Services.
 ───────────────────────────────────   ───────────────────────────────────
 Phone Number: An optional fourth	    CR w/Commands: Whether Icom adds
 number to dial for the same BBS.	    [Enter] after *all* BIF Responses.

 ───────────────────────────────────   ───────────────────────────────────
 Phone Number: An optional fifth	    Add Line Feeds: Whether Icom adds a
 number to dial for the same BBS.	    line feed after receiving a CR from
							    the BBS.

 ───────────────────────────────────   ───────────────────────────────────
 Port Settings: Port Settings and	    Case-sensitive: Whether BIF prompts
 minimum CONNECT speed Icom will	    must match exactly.	If No, "Name"
 allow connections at (300 = any	    matches "name" or "NAME", etc.
 speed).
 ───────────────────────────────────   ───────────────────────────────────
 Dial Prefix: Which main setup Dial    Connect Command: A BIF Response or
 Prefix to use (Dialer Settings	    @SCRIPT Icom executes immediately
 screen). 					    after connecting.  Use "^[~^[" to
							    send two ESC characters to bypass a
							    BBS front end program.

 ───────────────────────────────────   ───────────────────────────────────
 Max. Redials: Maximum number of	    Gen. Menu Exit: The command
 dialing attempts to make before	    sequence Intellicomm sends to the
 giving up (manual AND automated	    BBS when it cannot locate its
 mode).						    position (a timeout, etc).  ^K
							    [Ctrl-K] usually cancels a long BBS
							    text display, such as a bulletin
							    listing, etc.
 ───────────────────────────────────   ───────────────────────────────────

Protocols/Timeouts
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

 ───────────────────────────────────   ───────────────────────────────────
 Send Mail: The protocol used to	    Last Connected: The date you last
 send message reply packets.	Must     connected to the BBS (manual OR
 be the same protocol defined in the   automated mode).
 mail system, on the BBS.

 ───────────────────────────────────   ───────────────────────────────────
 BBS Letter: If the BBS mail system    Total Connects: The total number of
 displays a protocol menu, this is     connections made to the BBS.
 the response sent to the menu to
 select the above protocol.
 ───────────────────────────────────   ───────────────────────────────────
 Receive Mail: The protocol used to    Response Delay: Causes a delay (in
 receive message packets.  If set to   tenths of a second) before all
 ASCII, messages are simply		    BIF Responses.	If responses are
 "captured" to the "Msg. Filename",    "disappearing", set a delay of 10
 defined on the BIF Message Screen.    or 15 to remedy the problem.

 ───────────────────────────────────   ───────────────────────────────────
 BBS Letter: If the BBS mail system    BS Protection: Causes a number of
 displays a protocol menu, this is     backspace characters to be sent
 the response sent to the menu to	    before all BIF Responses.  Used to
 select the above protocol.		    eliminate line noise.  On most all
							    BBS's, the BS characters are simply
							    ignored if no line noise was
							    present (protection without
							    consequence).

 ───────────────────────────────────   ───────────────────────────────────
 Send Files: The protocol used to	    Logon Timeout: Timeout after this
 upload files to this BBS.  Must be    many seconds during a logon and
 the same as your "default protocol"   logoff.  A timeout is a period of
 on the BBS (if you have a default     time when the BBS stops sending
 protocol set).				    text (nothing received), and is
							    usually the result of an
							    unrecognized prompt (a mismatched
							    prompt on the BIF Logon Screen). 
							    Timeouts prevent Icom from sitting
							    online, doing nothing, forever.  If
							    a timeout occurs, Icom sends the
							    "Gen. Menu Exit" command defined
							    above, in an attempt to get a
							    recognizable BBS menu up (see Max.
							    Timeouts below).
 ───────────────────────────────────   ───────────────────────────────────
 BBS Letter: If the BBS file system    General Timeout: Same as the Logon
 displays a protocol menu, this is     Timeout above, but the General
 the response sent to the menu to	    Timeout is used after the logon
 select the above protocol.		    completes, and before the logon
							    begins (duration of the online
							    session).	You'll normally want
							    this set to a higher value than the
							    Logon Timeout.

 ───────────────────────────────────   ───────────────────────────────────
 Receive Files: The protocol used to   Max. Timeouts: The maximum number
 download files from this BBS.  Must   of consecutive timeouts to allow. 
 be the same as your "default 	    Once Max. Timeouts elapses, Icom
 protocol" on the BBS (if you have a   hangs up.	On automated runs, Icom
 default protocol set).			    will call back to attempt to
							    salvage the online session, up to 3
							    connections total.

 ───────────────────────────────────   ───────────────────────────────────
 BBS Letter: If the BBS file system    Max. Online Time: Mainly for
 displays a protocol menu, this is     protection during long-distance
 the response sent to the menu to	    calls, this is the maximum amount
 select the above protocol from the    of time (in seconds) you want
 BBS Protocol Menu. 			    Intellicomm to stay connected for. 
							    Lengthy file transfers (and
							    particularly auto batch transfers)
							    can cause much longer connect times
							    though.  Icom checks the connect
							    time BETWEEN each automated task,
							    and BETWEEN each file transfer,
							    during automated mode.  Thus, if
							    you allow batch transfers, it's
							    easy to go over the allotted
							    maximum time.
 ───────────────────────────────────   ───────────────────────────────────

See also:
	BIF Setup Tips
	Finishing up after BIF Learn
▀ See BIF Editor for general information on using the BIF Editor.

The BIF Bank/List screen holds the information necessary for automated time
bank deposits/withdrawals, as well as New Files Imports.

Time Bank Commands and Prompts
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

 ───────────────────────────────────   ───────────────────────────────────
 Access Bnk Menu: The BBS command	    Bank Menu: BBS text recognized as
 needed to access the Time Bank Menu   the Time Bank main menu (if any). 
 (if any) from the BBS Main Menu.	    Do not define unless the BBS has a
 If the 'Deposit/Withdraw' commands    Time Bank.
 defined below can be entered
 directly from the BBS Main Menu,
 leave this entry blank.
 ───────────────────────────────────   ───────────────────────────────────
 Deposit Bytes: Time Bank command to   Deposit Bytes: Time Bank prompt
 deposit download bytes in the bank.   asking for the number of download
							    bytes to deposit.

 ───────────────────────────────────   ───────────────────────────────────
 Deposit Time: Time Bank command to    Deposit Time: Time Bank prompt
 deposit online time in the bank.	    asking for the amount of online
							    time to deposit.

 ───────────────────────────────────   ───────────────────────────────────
 Withdraw Bytes: Time Bank command     Withdraw Bytes: Time Bank prompt
 to withdraw download bytes from the   asking for the number of download
 bank.						    bytes to withdraw.
 ───────────────────────────────────   ───────────────────────────────────
 Withdraw Time: Time Bank command to   Withdraw Time: Time Bank prompt
 withdraw online time from the bank.   asking for the amount of online
							    time to withdraw.

 ───────────────────────────────────   ───────────────────────────────────
 Leave Bank Menu: Time Bank command    Bank Pause: The format of the
 (if any) to leave the Bank Menu and   'Pause' prompt while performing
 return to the BBS Main Menu. 	    Time Bank transactions.  The usual
							    response to the Pause prompt
							    (defined on the BIF Logon Screen)
							    is sent.  If no prompt is defined,
							    the 'Pause' prompt on the BIF Logon
							    Screen is assumed.

 ───────────────────────────────────   ───────────────────────────────────
 Logoff Bank Menu: Time Bank command   Bank More: The format of the 'More'
 (if any) to logoff the Bank Menu	    prompt while performing Time Bank
 and disconnect.  If no command is     transactions.  The usual response
 defined, the 'Leave Bank Menu'	    to the More prompt (defined on the
 command is sent, and Icom performs    BIF Logon Screen) is sent.  If no
 a regular logoff from the BBS Main    prompt is defined, the 'Pause'
 Menu.						    prompt on the BIF Logon Screen is
							    assumed.
 ───────────────────────────────────   ───────────────────────────────────

BBS File List Details
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
File Tagger uses the BBS File List Details to import BBS new files listings
(see New Files Imports).  Please see BBS File List Details for an
introduction to these BIF settings.


 ───────────────────────────────────   ───────────────────────────────────
 Catalog to Use: (registered users     Year Positon: The position of the
 only) tells Tagger which catalog to   YEAR in file dates (2 numeric
 import to, and which catalog to	    characters assumed [93, 94, 95,
 scan when looking for Tagged files    etc).  The year needn't come last
 to auto-download.	If blank, the	    in the actual file date.
 NEWFILES catalog is assumed.
 ───────────────────────────────────   ───────────────────────────────────
 D/L Priority: The priority this BBS   Date Separator: The character used
 has for downloading files.  When	    to separate the month/day/year from
 the same file exists on more than     one another -- on the BBS file list
 one BBS, Tagger uses these		    itself.  This does not determine
 Priorities to determine which BBS     how file dates show up in the File
 to actually download from (if you     Tagger: it is only used to find
 Tag the file).  0 is the lowest	    proper dates on BBS file lists.
 priority (no priority at all) 1 is
 the highest (as in 'priority one'),
 2 is next, etc.  Define Priority 1
 at the local BBS you have the most
 online time/download bytes at. 
 Define higher priorities (or leave
 at the default of 0) at BBS's you
 must call long-distance, and BBS's
 where you have limited online time
 per day.  TIP: Use Priority 1, then
 10, then 20, 30, etc., so that you
 can later INSERT other BBS's into
 your priority structure without re-
 editing all your BIFs.

 ───────────────────────────────────   ───────────────────────────────────
 Default Lst Area: On New Files	    Comment Start: The starting
 Imports, this is the BBS		    position of the PRIMARY file
 area/conference Tagger STARTS with.   comment (description) line.  This
 It then watches for /Area: switches   has nothing to do with extended
 and text matching the 'New File	    description lines: only the portion
 Area' text below.	This item is	    of the description (if any) that
 only relevant to file lists which     shows up on the SAME line as the
 contain files from MULTIPLE file	    filename, size, date.
 areas (extracted Qmail file
 listings, etc).

 ───────────────────────────────────   ───────────────────────────────────
 Filename Start: The position of	    Comment End: The ending position of
 filenames on BBS file lists		    the PRIMARY file comment line.
 (position 1 = the left-most
 character on each line).  If
 'Extension Start' (below) is 0, 12
 characters is assumed for this
 item.  If 'Extension Start' is non-
 zero, 8 characters is assumed for
 this item.
 ───────────────────────────────────   ───────────────────────────────────
 Extension Start: If zero, this	    Continue Comment: One or more
 tells Tagger that filenames appear    characters that signify a
 on the list as FILENAME.EXT (both     continuation of the primary comment
 together separated by a period).	    line.  Use several spaces if no
 If non-zero, defines the starting     special characters are displayed
 position of file extensions.  E.g.:   prior to extended comment lines.
 FILENAME  EXT
 3 characters are assumed for this
 item if non-zero.

 ───────────────────────────────────   ───────────────────────────────────
 Size Position: The position of the    Continue Comment: An alternate to
 file size.  8 characters are 	    the above (if more than one type of
 assumed for this item: so count 8     extended comment character is
 positions to the left of the END of   used).
 the size field on new files lists.
 If the letter 'K' exists within the
 8 characters, (as in 10K, 100K,
 etc) Tagger removes the 'K' and
 multiplies the prior number by 1024
 (1024 = 1K).	Thus if "    100K"
 showed up on a list at the 'Size
 Position', Tagger would remove the
 'K', multiple 100 by 1024, and
 store a size of 102400.

 ───────────────────────────────────   ───────────────────────────────────
 Month Position: The position of the   New File Area: Only of use on file
 MONTH in file dates (2 numeric	    listings which display files from
 characters assumed [1-12]).	The	    multiple BBS conferences (Qmail
 month needn't come first in the	    listings, for example, which can
 actual file date.				    collect new files lists from
							    multiple conferences).  Example:
							    Conference 1
							    FILE1.ZIP	 1234  MM-DD-YY  ...
							    Conference 2
							    FILE2.ZIP	 1234  MM-DD-YY  ...
							    If the above was the format of the
							    list, you'd define the word
							    'Conference' here in the New File
							    Area' item.  Tagger watches for the
							    text defined here (if any) and when
							    found it takes the next group of
							    characters and stores is as the
							    file area (1 and 2 above).  It
							    would then Join conference 1 to get
							    FILE1.ZIP, conference 2 to get
							    FILE2.ZIP, etc.
 ───────────────────────────────────   ───────────────────────────────────
 Day Position: The position of the     COUNT File Areas: Please see
 DAY in file dates (2 numeric 	    COUNT File Areas for details.
 characters assumed [1-31].  The Day
 needn't be in the middle of the
 actual file date.
 ───────────────────────────────────   ───────────────────────────────────


See also:
	BIF Setup Tips
	Finishing up after BIF Learn
cA rather bizarre item "COUNT File Areas" has been added to the "Bank/List"
screen, and what this item does is to start the file area (imported into
the Tagger catalogs) at "0", and every time it runs across one of these on
a file list:

  ║ Month Position . XX			 New File Area  . File Area:		  ║
							 ─────────────────────────── 

(the text "File Area:" is used by TriBBS, but anything can be defined), it
increments the file area stored in the Tagger records ...  So given the
following new files list:

  File Area: Anti-Virus Software
  File Area: Audio Files
  File Area: Unchecked Uploads
  ICOM201A.ZIP    XXXXXX  MM-DD-YY  Intellicomm v2.01.

The file ICOM201A.ZIP would be stored as being in file area "3" (due to the
3 occurrences of the text "File Area:".  If you tagged and auto-downloaded
the file, Icom would access file area #3 ... not "Unchecked Uploads".  So
far this has only been necessary on TriBBS lists, which do not display the
actual area number you must access.  I.e. above, Icom could not [C]hange to
the "Unchecked Uploads" area to download ICOM201A.ZIP.  It would have to
[C]hange to area 3.
≈Introduction to the BIF "BBS File List Details" settings
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
By examining a BBS new files list, and configuring the BIF "File List
Details" settings accordingly, Tagger can import virtually any type of BBS
file listing.

The most important items on this BIF screen are the various 'position'
settings.  They tell Tagger where on a typical line from a BBS file list,
it will find various pieces of information.	Take the following example BBS
file list for example:

─────────────────────────────────────────────────────────────────────────
	    1	    2	    3	    4	    5	 Numeric ruler
12345678901234567890123456789012345678901234567890	 for reference.
─────────────────────────────────────────────────────────────────────────
(Unsorted Uploads)
EXAMPLE.ZIP   12345678	12-25-94	This is an example file demonstrating
						   | proper BIF "Bank/List" setup.

Main Board Command?
─────────────────────────────────────────────────────────────────────────

Tagger will import this list line by line, starting with the (Unsorted
Uploads) line.

STEP 1:  The first thing Tagger looks for is either an /Area: switch (which
Icom places on captured file listings so Tagger knows which FILE
AREA/CONFERENCE a file list was captured in) or a line of text matching the
'New File Area' text:

║ Month Position . 24			 New File Area  .				    ║

Since the text "(Unsorted Uploads)" doesn't match the blank "New File Area"
text, the next thing Tagger checks (STEP 2) is whether the line has 'Date
Separator' character(s) between the positions defined in the 'Month
Position' / 'Day Position' / 'Year Position'.  Position means the position
of the item (starting at column 1) from the left-most margin of the list. 
Above, the position of the Date Separators (-) is 28 and 31.  To determine
these positions, Tagger finds the LOWEST Month/Day/Year position (the Day
or Year may come first on some BBS's) and adds 2 to that to skip over the
actual date, then finds the HIGHEST Month/Day/Year position and subtracts 1
from that.  Assume the following positions:

  Month Position: 26
  Day Position  : 29
  Year Position : 32

The MONTH has the lowest position, so to find the first Date Separator
character position, Tagger adds 2 to 26 and comes up with 28 (which is the
position of the first Date Separator on the list above).  The YEAR has the
highest position, and looking one character to the LEFT of that (position
31) Tagger expects to find the second Date Separator.	Tagger currently has
the line "(Unsorted Uploads)" ... it checks at position 26, finds no Date
Separator, and ignores the line/reads the next line.

The next line is:

EXAMPLE.ZIP   12345678	12-25-94	This is an example file demonstrating

Here, Tagger does find the Date Separator character at positions 26 and 31,
and thus it assumes that it has a valid file line for importing.  It then
checks the 'Filename Position' and 'Extension Position' to see if both the
Filename and Extension are specified together (if Extension Position is 0,
it's assumed that the FILENAME.EXT are together, separated by a period). 
Then it reads 8 characters from the 'Size Position' (8 is always assumed as
the length of the Size item), reads in the actual Month/Day/Year using
'Month Position', 'Day Position', 'Year Position' settings (which, again,
can show up in any order; the Month can be first, the Year can be first, or
the Day can be first and so forth.  Tagger assumes 2 positions per date
item).  And finally it reads in the primary file description/comment line
using the 'Comment Start' / 'Comment End' positions, and is finished with
that line.  But before starting over at STEP 1 and looking for another 'New
File Area' line or a valid file line with Date Separators on it...

STEP 3: Tagger reads in the next line of the list to check for an EXTENDED
file comment.	The next line is:

						   | proper BIF "Bank/List" setup.

Tagger checks this line to see if the text defined in either of the
'Continue Comment' items is found anywhere along the line.	Assume the
following:

║ Extension Start  0			 Continue Comment  |«			    ║

Above, a space and a vertical bar (|) are defined as the first 'Continue
Comment' string; Tagger finds this on the line and assumes that the line is
a continuation of the previous comment.  It then STRIPS the characters
matching the 'Continue Comment' text (one space and the vertical bar), then
strips all leading and trailing spaces, then appends the line to the
existing file description.  This process continues until Tagger finds text
matching the 'New File Area' text, an /Area: switch, a VALID file line
(with date separators in the proper positions), or a line that DOESN'T
match either of the strings defined in the 'Continue Comment' item.  Once
any of the above happens, Tagger goes back up to STEP 1 above.

This simple logic, combined with just a few BIF settings, allows Tagger to
import a very wide variety of BBS file listings -- and also allows it to do
so reliably, filtering out any extraneous garbage on the file list.

See also:
	BIF Bank/List Screen
b&See BIF Editor for general information on using the BIF Editor.

The BIF File Screen holds all the settings related to BBS file activities,
such as automated file uploads, downloads, new files list captures, and
file searches.  If the BBS has a 'File Menu' it is assumed that all of
these file-related activities are performed from the File Menu.

File Commands and Prompts
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀


 ───────────────────────────────────   ───────────────────────────────────
 Access File Menu: The BBS command     File Menu: BBS text Intellicomm
 needed to access the File Menu (if    watches for (if any) to determine
 any) from the BBS Main Menu.  If	    when it's at the BBS File Menu.
 the file-related commands defined     Leave blank if the BBS has no file
 below can be entered directly from    sub-menu/door.
 the BBS Main Menu, leave this entry
 blank.
 ───────────────────────────────────   ───────────────────────────────────
 Default BBS Area: This is the file    File Pause: The format of the
 area Intellicomm accesses prior to    'Pause' prompt while in the File
 uploads/downloads, if the files it    Menu.  If blank Intellicomm assumes
 is transferring have no file area     the 'Pause' prompt defined on the
 attached in the Tagger Catalog.	    BIF Logon Screen.  The RESPONSE to
 Also the file area Icom accesses	    this prompt is always the 'Pause
 prior to 'Get new files list'	    Answer' command, defined on the
 tasks; if a specific 'Change 	    BIF Logon Screen.  Use a 'File
 BBS/File Areas' task is not used	    Extra' prompt if you must send a
 before the new files task.		    different response to the File
							    Pause prompt.

 ───────────────────────────────────   ───────────────────────────────────
 Area Change: The command Icom sends   File More: The format of the 'More'
 to access various BBS file areas.     prompt while in the File Menu.  If
 A percent sign (%) signifies the	    blank, the 'More' prompt defined on
 position of the actual file area in   the BIF Logon Screen is assumed. 
 the command.

 ───────────────────────────────────   ───────────────────────────────────
 New Files: The command Icom sends     Enter D/L Fname: This BBS prompt
 when a 'Get new files list' task is   asks for the filename to download
 defined in a job.				    after sending the 'Download
							    File[s]' command.
 ───────────────────────────────────   ───────────────────────────────────
 File Search: The command Icom sends   Enter U/L Fname: This BBS prompt
 when a 'Search BBS for File[s]'	    asks for the name of a file to
 task is defined in a job.  A 	    upload after sending the 'Upload
 percent sign (%) signifies the	    File[s]' command.
 position of the actual search text
 defined in the job.

 ───────────────────────────────────   ───────────────────────────────────
 Download File[s]: BBS 'download'	    Enter Protocol: Prompt which asks
 command: usually 'D' for Download.    for a transfer protocol (uploads or
							    downloads).  The responses to this
							    prompt are defined in the 'BBS
							    Letter' items under the Send Files
							    / Receive Files protocols, defined
							    on the BIF General Settings screen.

 ───────────────────────────────────   ───────────────────────────────────
 Upload File[s]: BBS 'upload' 	    Duplicate File: BBS prompt reports
 command: usually 'U' for Upload.	    that a file Icom is attempting to
							    upload already exists at the BBS. 
							    Icom removes the 'Upload Pending'
							    for the file, on the current BBS.
 ───────────────────────────────────   ───────────────────────────────────
 Descrip @SCRIPT: Allows you to	    Enter Descrip: BBS prompt asks for
 execute a custom @SCRIPTNAME to	    the description of a file on
 enter file descriptions (uploads),    uploads.
 for tricky situations.	See the
 Wildcat \ICOM\SCR\WCDESC.SCR for an
 example.

 ───────────────────────────────────   ───────────────────────────────────
 Chars per Line: The maximum		    File Not Found: BBS prompt stating
 characters accepted per line for	    that a file Icom is attempting to
 file descriptions (uploads).  Icom    download no longer exists on the
 reformats the description according   BBS.	Icom untags the file.
 to this setting.

 ───────────────────────────────────   ───────────────────────────────────
 Max Lines: The maximum number of	    No Time: BBS prompt stating that
 lines accepted per file description   not enough online time remains to
 (uploads).					    transfer a file (uploads or
							    downloads).  Icom flags the file as
							    'done' for the current session, but
							    leaves it Tagged for the next
							    session.
 ───────────────────────────────────   ───────────────────────────────────
 Files per D/L: Sets a limit to the    No Bytes: BBS prompt reporting that
 number of filenames Icom will enter   not enough download bytes remain to
 per batch download.  This item is     transfer a file (downloads).  Icom
 mainly of use when using the 'Max.    flags the file as 'done' for the
 Online Time' (BIF General Settings)   current session, but leaves it
 setting: Icom only checks the max.    Tagged for the next session.
 online time BETWEEN each batch
 transfer.  The more filenames it
 enters at once, per batch download,
 the more likely the chance that
 Icom will end up online for LONGER
 than the Max. Online Time.  If you
 want relatively accurate Max.
 Online Time protection, define 1
 file per D/L.

 ───────────────────────────────────   ───────────────────────────────────
 Files per U/L: Sets a limit to the    File Accepted: The filename Icom
 number of filenames Icom will	    just entered (upload or download)
 enterper batch upload.	If you	    was accepted by the BBS.	Leave
 frequently experience aborted batch   blank if no reliable text can be
 uploads on a BBS, set this item to    found.
 1 or 2 files to limit your risk
 (the entire batch may have to be
 re-transmitted on some BBS's, if
 the connection is lost in
 mid-transfer).  Also see the 'Files
 per D/L' notes above.

 ───────────────────────────────────   ───────────────────────────────────
 Batch Full Answr: The response Icom   Batch Full: Icom has entered the
 sends to the 'Batch Full' prompt	    maximum number of files per batch
 (if any).					    that the BBS accepts; this prompt
							    normally presents a menu of
							    options, such as [A]bort Transfer,
							    [G]oodbye after Transfer,
							    [Enter]=Continue.  Icom sends the
							    'Batch Full Answer' (if any) and
							    waits for the BBS to give it
							    further instructions (enter
							    protocol, start the transfer, etc).
 ───────────────────────────────────   ───────────────────────────────────
 File Password: The response Icom	    Enter Password: This BBS prompt
 sends to the 'Enter Password'	    asks Icom to enter a password when
 prompt (if any).  It's probably	    downloading a particular file. 
 easier just to download password-     Icom sends the 'File Password'
 protected files manually; but if	    defined next door (<--).
 you regularly download a password-
 protected file from a BBS, you can
 define the usual password here.

 ───────────────────────────────────   ───────────────────────────────────
 Leave File Menu: BBS command(s)	    Download File[s]: BBS prompt tells
 needed to exit the File Menu (if	    Intellicomm to begin the download. 
 any) and return to the BBS Main	    Icom does the equivalent of
 Menu.  Leave blank if no 'Access	    pressing [PgDn] and selecting the
 File Menu' command is defined	    protocol you defined in the
 above.						    'Receive Files' slot on the BIF
							    General Settings screen.

 ───────────────────────────────────   ───────────────────────────────────
 Logoff File Menu: BBS command(s)	    Upload File[s]: BBS prompt tells
 needed to logoff directly from the    Intellicomm to begin the upload. 
 File Menu (if any).  If no command    Icom does the equivalent of
 is defined (i.e. if the file system   pressing [PgUp] and selecting the
 doesn't support direct logoffs)	    protocol you defined in the 'Send
 Icom first sents the 'Leave Msg	    Files' slot on the BIF General
 Menu' command (if any) then logs	    Settings screen.
 off from the BBS Main Menu.
 ───────────────────────────────────   ───────────────────────────────────
 Upload PATH: Allows you to override   Transfer Abort: The transfer
 the usual Upload PATH (defined on     aborted (upload or download).	On
 the main setup 'Filenames and	    downloads, Icom looks on-disk to
 Paths' screen) for a given BBS.	    see which files it got, then begins
							    the transfer from the last file
							    that DOES exist on-disk (assumes
							    that this is the file the transfer
							    aborted on).  On uploads, Icom re-
							    transfers the entire batch: any
							    files the BBS received will come up
							    as 'Duplicate Files' (the BBS will
							    send the 'Duplicate File' prompt);
							    the ones it didn't get will be
							    accepted.	NOTE: If the transfer
							    aborts 3 times in a row, Icom
							    cancels and continues with the next
							    job task (if any).

 ───────────────────────────────────   ───────────────────────────────────
 Download Dir: Allows you to		    Transfer Okay: The transfer
 override the usual Download Dir	    wassuccessful.	On downloads, all
 (defined on the main setup		    files Icom finds on-disk (from the
 'Filenames and Paths' screen) for a   previous batch) are untagged.	On
 given BBS.					    uploads, the 'Upload Pending' BIFID
							    is removed for all files in the
							    batch.
 ───────────────────────────────────   ───────────────────────────────────

See also:
	BIF Setup Tips
	Finishing up after BIF Learn

See BIF Editor for general information on using the BIF Editor.

The BIF "Extras" screen allows you to define several extra BBS prompts and
responses for whatever purpose you see fit.	Only one set of extra prompts
is tracked (watched for) at a time by Intellicomm: either the "Externals"
are being tracked, or the "Message" extras, or the "File" extras are being
tracked.	Icom never watches for prompts from more than one extra set at a
time.

External Extras
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
These prompts are tracked during automated logons AND logoffs, and when
Icom is performing tasks from the BBS Main Menu (i.e. Custom Commands that
were started at the BBS Main Menu).  Whether or not there is a BBS "Message
Menu" defined in the BIF, Intellicomm will not track the External Extras
during automated mail or file transfers.  They are called "external" due to
the fact that they are not watched for while 'inside' a sub-menu/door.

Message Extras
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
These prompts are tracked during message-oriented automated tasks (Send
message replies, Get all new mail, Get personal mail only) whether or not a
Message Menu is defined in the BIF.  Further, if an "Access Msg. Menu"
command is defined in the BIF, Icom starts tracking the Message Extras just
*before* it sends the Access Msg. Menu command (i.e. if accessing the
Message Menu is a tricky process for some reason, you can use a Message
Extra prompt to help out).  They continue to be tracked throughout all the
mail-oriented tasks, until Icom reaches the Main Menu again (they're
tracked while LEAVING the Message Menu as well).

File Extras
▀▀▀▀▀▀▀▀▀▀▀
These are prompts follow the same rules as the Message Extras mentioned
above, but during file-related tasks instead of message-related tasks.  The
File Extras are tracked while accessing/leaving the File Menu (if
applicable) and during automated uploads, downloads, file searches, and new
files scans.  Use them as you see fit, to handle whatever silly BBS prompts
need handling.

I'm out of Extra Prompts and STILL have more prompts to handle
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Solution: Use Script Learn to have Icom write a script to handle the task. 
Scripts created with Script Learn track only a single BBS prompt at a time
(using the script WAITFOR command) and thus they can handle an unlimited
number of BBS prompts.  For reliable automation, Icom (as opposed to a
script) watches for all relevant prompts at the same time.	I.e. all the
logon prompts, all the menu prompts, and all the External Extras are
tracked at the same time during logons.

You can integrate learned scripts WITH your BIF and automated job(s), thus
adding new automated routines to Intellicomm.  See SCRTUTOR.DOC for all the
details.

Alternate Solution: Talk to the BBS Sysop and see if you can get the
problem prompt(s) removed somehow.  Icom BIFs handle more BBS prompts than
any other BBS automation system we're aware of, and if you can't get the
job done with Icom, automation of the task likely isn't do-able with ANY
automation system, and the BBS is simply out of whack.  Most often if you
TELL your Sysop about your automation problems, due to non-standard or
customized BBS prompts, the Sysop will be very cooperative in helping to
resolve the situation.

See also:
	BIF Setup Tips
	Finishing up after BIF Learn
;	You are now in the Text Editor and are free to modify the file description
as you see fit.  Press [Esc] when you're done.

A couple of pointers: Do NOT try to add graphics characters or control
characters other than  (see below).  Also do not try to format the
description by cutting certain lines short, or putting double spaces
between words to right-justify.  Tagger strips all double spaces, all
control characters (other than ) and all end-of-line characters when
you're finished, so you'll be wasting your time trying to get the
description into a specific format.

This is done to keep file descriptions as standardized and "unformatted" as
possible, and it makes Intellicomm capable of auto-uploading files to
virtually any BBS type.	From BBS to BBS the margins used for file
descriptions (as well as the maximum number of lines accepted) changes. 
Thus, Intellicomm stores all file descriptions formatted in the same way
(with no line breaks at all), and only attempts to re-format when auto-
uploading to a specific BBS.	If you're intent on putting tacky graphic
boxes around your file descriptions: create a text file containing the
description/bells and whistles, do the upload manually, and enter the
description from the text file using an ASCII upload.	Or create/learn a
script to do it.

NOTE: In the FILELIST (upload) catalog, you may see items such as these
when editing the file description:

Upload Pending BIFID1;BIFID2
Uploaded To BIFID3

What these items are is self-explanatory, but note that you can add these
items manually yourself while editing the file description, and you can
also delete them if you like (to produce the  character, hold down the
[Alt] key and press 1 then 6 [sixteen] on the NUMERIC KEYPAD, then release
the [Alt] key).  If you clear all the "Upload Pending" ID's, the file will
be automatically untagged/re-sorted when it's written back to disk.  If you
add "Upload Pending" text, then one or more BIFID's, the file will be
automatically Tagged when it's written back to disk (this doesn't take
place until after you exit the description editor, then leave the record by
pressing [Esc] or [PgUp]/[PgDn]).	You can also add to either of the above,
adding new BIFID's onto the end, as long as you separate each from the
previous BIFID with a semicolon (BIFID1;BIFID2;BIFID3...etc).

See also:
	Text Editor
"Export D/L's to TEXT FILE" is an optional item defined in the Icom main
setup on the File Tagger Settings screen.  It is used in combination with
the BIF Format for Export option, and (if BOTH items are defined) they're
used to have Icom automatically update a given text file, in a given BIF
format, with the filenames, sizes, dates, and descriptions of all newly
downloaded files.

The option is mainly of use to BBS Sysops, to have Icom automatically
update the BBS file listings after automated file collection (please see
Automation in Detail, and BIF Format for Export for a complete
description).

The name of the TEXT FILE you define in this item should include a drive
and path.  If you define only a filename, and omit the \PATH\ the \ICOM\LST
directory is assumed.  If you omit the drive, the current drive is assumed. 
Thus, it's best to define the full D:\PATH\FILENAME.EXT of the file you
want to export to (add to) in this item.

See also:
	BIF Format for Export
	Automation in Detail
	Automated Downloads
≡
The "BIF Format for Export" main setup option is optional, and is used in
combination with the "Export D/L's to TEXT FILE" option.

After an automated job in which one or more new files were successfully
auto-downloaded (Tagged in the File Tagger and downloaded using an
automated job), Icom starts is "post-job" processing.

During this post-job processing, one of the little jobs Icom can take care
of for you is to export (append) the filename, date, size, and description
of all downloaded files to a user-configurable text file (the "Export D/L's
to TEXT FILE" main setup option) in a specific BIF format (the "BIF Format
for Export" option).

This is mainly of use to Sysops, to automatically update their BBS file
listings after Icom auto-downloads some new files.  Not all types of BBS
file listings can be properly supported, however, and the BBS must use a
relatively standard format in its file listings, such as this:

FILENAME.EXT 12345678  MM-DD-YY  Description line 1.
						   Description line 2.
						   etc.

or with a special character preceding the extended comment lines, and/or
any other date format:

FILENAME.EXT 12345678  DD/MM/YY  Description line 1.
						 | Description line 2.
						 | etc.

or with separate filename extensions:

FILENAME EXT 12345678  YY.MM.DD  Description line 1.
						 | Description line 2.
						 | etc.

The filename, extension, size, date positions (month, day, year), date
separator, and extended comment "preface" character are all defined on the
BIF "Bank/List" screen, and this is the information Icom uses for the
export.  Simply set a BIF up with the proper information, then use that BIF
as the "BIF Format for Export" in the main setup/File Tagger Settings.

The BIF (or [Template]) you choose for the export must have its "Bank/List"
screen set up with the proper positions where various items are to be
placed on the text file (filename position, extension position [if any],
year, month, day position, date separator, etc).	To get a special
character such as the vertical bar (|) illustrated above place before the
extended comment lines, place the desired character(s) in the first
"Continue Comment" item in the BIF:

║ Extension Start  0			    Continue Comment |«			   ║
							    ──────────────────

If defined, this character (or a number of characters) is placed two spaces
to the LEFT of the 'Comment Start' position:

║ Default Lst Area				    Comment Start  . 34			   ║
							    ───────────────────

preceding each extended comment line.  This leaves one space between the
extended comment character(s) and the extended comment itself, as
illustrated in the example above.	If you don't want any characters
preceding the extended comment lines, simply clear the "Continue Comment"
item, or define a single space in it.
≥Hilight and "Tag" the BBS(s) you wish to upload the file to, or select
"Untag" to untag all BBS's.

Note that Intellicomm keeps track of both the location that the file was
auto-downloaded from originally (stored in the "Location/ID" field of the
catalog record), plus all BBS's you have already auto-uploaded the file to
(if any).  If you Tag a BBS that you've already uploaded the file to (or
the one that had the file originally), Icom displays a warning asking you
to confirm the tag.  You can't really do any harm by trying to upload the
same file to the same BBS more than once, since the BBS will simply tell
Intellicomm that the file already exists... and Icom will then clear the
upload flag for that location.  But it does waste a bit of online time.

To save your changes (if any) when done, choose "Select" from the bottom
menu.  To leave without saving any changes you made, select "eXit" or press
the [Esc] key or right mouse button.  Don't exit with the [Esc] key if you
want to save your tags!
╫DOS Shell lets you go to the DOS command prompt temporarily, and it's
available from just about everywhere in Intellicomm by pressing the [Alt-J]
hotkey (J for 'J'ump to DOS Shell).  [Alt-J] is NOT available during file
transfers.

Once at the DOS prompt you can run other programs or .BAT files, or execute
DOS commands such as DISKCOPY, FORMAT, etc.	Do not run another copy of
ICOM.EXE, however.	It's not designed for multiple instances; and it
shouldn't be necessary.

When you're ready to return to Intellicomm, just type 'EXIT' (no quotes) at
the DOS prompt.

NOTE: The 'Enable Swapping' item on the General Settings main setup screen
controls whether Intellicomm will swap itself out of base memory (to either
extended memory, expanded memory, or disk depending upon what is available)
before going to the DOS prompt.  You can have Icom swap itself out in any
of these cases:

 Never
 When not connected
 Connected or not
 
[Note that this setting also controls Icom's action when you shell out to
your Mail Reader, Archive Viewer, etc., unless the command you define on
the main setup "Filenames and Paths" screen overrides the default setting
with use of SW: (swap) or NS: (no swap).]

If set to 'Never', Icom never swaps itself out of memory, and while this is
faster than using swapping, it will leave you with much less base memory to
work with while shelled out.	ICOM.EXE uses about 350K of base memory
('base' memory meaning the memory DOS will use; the lower 640K), so you'll
be left with whatever you had when you started ICOM.EXE, minus 350K, if
Icom doesn't swap out.

If set to 'When not connected' then Icom only swaps itself out if your
modem is offline at the time of the shell (further, the modem must be
REPORTING the proper connect status to Intellicomm.  Most modems don't by
default, but that can be remedied.  See Common Questions & Answers for
help).  After the swap, you'll have all the memory that was available when
ICOM.EXE was started (minus just about 200 bytes of code which Icom keeps
resident to swap itself back in to base memory after the shell).

If your modem is ONLINE at the time, and Enable Swapping is set to 'When
not connected' Icom will still be processing characters from the COM port
while it's shelled out.	By "processing" this doesn't mean that you can
perform an entire BBS session in the background: it simply means that
Icom's interrupt handler will take characters that arrive at the port, and
store them in the internal "Receive Buffer" (size is configurable on the
main setup/Terminal screen; defaults to 4 kilobytes).	Once the Receive
Buffer is about three quarters full, "Flow Control" is activated to get the
modem to stop sending characters.	When you return from the DOS shell, all
the characters sitting in the Receive Buffer are then processed and
displayed on the screen.

If Enable Swapping is set to 'Connected or not', then Icom swaps itself out
of base memory whether you're online at the time or not.  In order to do
this, Icom must disconnect its interrupt handler from the COM port before
shelling out (it must, because the interrupt handler, which handles
characters from the COM port, will not be in base memory after the swap). 
I.e. If any characters are received from the modem while you're shelled
out, they will be lost.

Multitasking
▀▀▀▀▀▀▀▀▀▀▀▀
If you want true background communications (the ability to perform an
online session with Icom WHILE running another program in the foreground),
you should install DESQview, OS/2, or Windows 3.1 (or greater).	These
systems give you task-switching/multitasking abilities for ALL the programs
on your system, and they'll do it quite reliably if they're set up properly
(see Multitasking Intellicomm for specific setup information).  Building
background abilities into ICOM.EXE itself would be similar to writing our
own version of the Windows/DESQview/OS/2's kernels, it would increase
Icom's size and memory requirements needlessly, and it would add a great
deal of (probably inferior) code to the program that REAL task-switchers
already have built in.  If you want multitasking, and you're running MS-DOS
alone, you're simply running the wrong Operating System.  Multitasking and
task-switching are the responsibility and domain of Operating Systems --
not individual .EXEs.
¬
Disabling the Screen Blanker
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
To disable Intellicomm's screen blanker, enter the Intellicomm Setup,
access the Screen/Color Settings screen, and set "Blank Screen # Seconds"
to 0 (zero).

Screen Blanker
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Icom's screen blanker watches for periods of inactivity, such as long file
transfers, or while sitting at a menu doing nothing, and it clears the
screen during these times to avoid screen burn-in.  Icom is still working
behind the blank screen: it just stops updating the video display.  Note
that the blanker works only if Icom is set for DIRECT VIDEO WRITES (see
main setup/Screen Settings).

You control how long Icom should wait (periods of no keyboard activity/
mouse clicks) before blanking the screen with the "Blank Screen # Seconds"
setting on the main setup Screen/Color Settings screen.  The inactivity
period is 120 seconds (two minutes) by default. If you set this item to 60,
then Icom will blank the screen one minute after your last keypress/mouse
click, if you press no other keys in the meantime.  If you set it to 0
(zero) then the screen blanker is disabled.

The screen blanker was added internally due to the fact that many external
screen blankers do not (and often cannot) do an adequate job for a program
such as Intellicomm.  Many screen blankers re-display the screen whenever
any video activity takes place.  And since Intellicomm is almost constantly
updating the screen, either with file transfer statistics, the BBS online
data, or the time of day, many screen blankers are useless while using
Intellicomm.

Further, unlike external screen blankers, Icom's screen blanker has
knowledge of exactly WHAT Intellicomm is doing, and thus it can operate in
a more intelligent manner.  For example, during Automatic Browse Mode in
the File Tagger, when Icom is displaying files without your having to press
a key, the screen blanker is disabled.	Or, if a file transfer aborts or
the connection is lost, and the screen was previously blanked, Icom
immediately re-displays the screen.  And whenever entering a new menu (the
dialer menu, etc), Icom also re-displays the screen: If you are in the room
at the time, this will get your attention and keep you updated as to what
is going on (but only if something IS going on, or if an error occurred),
without your having to walk across the room to press a key.  If you aren't
in the room at the time, the screen will simply be blanked again when the
next period of inactivity elapses.

The screen blanker is active (other than in the Tagger's autobrowse mode,
or if you shut it off in the main setup) in all areas of Intellicomm,
whether it's sitting at a menu, carrying out an automated online session,
or running a script.  Thus, even the scripts you write come with built in
screen blanking!

──────────────────────────────────────────────────────────────────────────
NOTE: There is a known conflict between Icom's screen blanker and the PC-
KWIK Power Pak screen accelerator.  If you use this product, you may
receive Bad CRC errors during file transfers when you press [Enter] to de-
activate Icom's screen blanker.  To fix the problem, create a batch file
(I.BAT or the like) to start Intellicomm:

Echo off
PCKSCRN /disable
ICOM.EXE %1 %2 %3 %4 %5
PCKSCRN /enable

Or, use another key such as [Down] arrow to de-activate Icom's screen
blanker.	The problem only occurs when [Enter] is pressed.
──────────────────────────────────────────────────────────────────────────
SThe 'Terminal' is the part of Intellicomm that your modem communicates
with.  It can be used while Offline (not connected) to enter commands
directly to your modem (to change various modem settings), and is used
while Online to communicate with remote computers (BBS's or other Host
programs).  'ANSI' codes, to change screen colors and move the screen
cursor, are directly supported by Intellicomm's Terminal.

Intellicomm communicates with your modem directly (without going through
the Terminal) when initializing the modem, and when performing uploads and
downloads.

Accessing the Terminal
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Press [Alt-T] from any major Intellicomm area to access the Terminal (use
the Hotkey Menu by pressing [Shift-F1], if you forget the [Alt-T] key). 
You can also access the Terminal by selecting "Terminal" from the Main
Menu, Job Directory and BBS Directory.	The Terminal is AUTOMATICALLY
entered when a connection is made after using the Dialer.

Status Line
▀▀▀▀▀▀▀▀▀▀▀
If the main setup/Terminal Settings 'Status Bar' option is set to ON, the
bottom screen line of the Terminal is reserved for status information:

Connect Status  HH:MM │ Mode	│ SpeedΘSET │ Capture Stat │ Alt-Z for Menu

Connect Status:	If the modem is connected (online) this status line
				item contains either the BBS Name (as defined in the
				BIF) or 'Online [Unknown]' (if no BIF is loaded; Manual
				connections or connections that were made before Icom
				was started).
	    HH:MM:	If connected, HH:MM shows the total length (in
				hours:minutes) of the connection.	This item is also
				updated during internal protocol transfers.
		Mode:	Intellicomm's current mode:
				 AUTO = Intellicomm is in automated mode and is
				watching for various BBS prompts (press [Alt-W] to see
				the prompts Icom is watching for, press [Alt-Q] and
				select "Abort Job/Script" to cancel Auto mode and
				return to Manual).
				 MANUAL = Icom is currently in manual Terminal mode (no
				timeouts are in effect and Icom is not watching for BBS
				text to respond to).
				 SCRIPT = a script is currently running (press [Alt-Q]
				and select "Abort Script Only" to abort a script and
				return to Auto Mode, press [Alt-Q] and select "Abort
				Job/Script" to abort both the script AND Auto mode, and
				switch back to Manual).
				 LEARN = BIF Learn is currently active.  Press [Alt-Q]
				and select "Learn mode OFF" to abort Learn and return
				to Manual mode.
				 SLEARN = Script Learn is currently active.	Press
				[Alt-Q] to abort Script Learn and return to Manual
				mode.
	SpeedΘSET 	When Offline, 'Speed' displays the current COM port
				speed.  When Online, 'Speed' displays either the
				current COM port speed or the modem CONNECT speed
				(controlled via the main setup "Status Bar Displays"
				item defined on the "Terminal Settings" screen).	The
				"ΘSET" portion of this item always displays the current
				port SETTINGS in the following order: PARITY (N = None,
				E = Even, O = Odd) DATA BITS (7 or 8) and STOP BITS (1
				or 2).  To change the current Port Settings press [Alt-
				P].
  Capture Stat 	If 'Capture Off' then no capture file is currently
				open.  If 'Capture Paused' then the capture file is
				currently paused.  If a filename is displayed (ICOM.CAP
				normally) then Intellicomm is writing each new line
				displayed in the Terminal to the capture filename.  To
				change the current Capture status, press [Alt-L] (L for
				Log; as in Capture Log).  To review Capture files after
				an online session, select "Review Session Captures"
				from the Icom Main Menu.  TIP: The main setup / General
				Settings items: "File Renumber Mode" and "Capture
				Renumber Total" determine (a) how old capture files are
				renumbered (b) how many (if any) old backup files are
				kept on hand (see General Settings for more details). 
				To change the current Capture
Terminal Hotkeys
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Alt-Z for Menu 	Hold down [Alt] and tap [Z] to display the
				Terminal Menu.  The Terminal Menu gives you access to
				all Terminal features, and also serves as a reminder of
				the HOTKEYS you can use while in the Terminal.  For
				example, If you forget that [Alt-Q] is used to abort
				jobs/scripts/learn mode, simply press [Alt-Z] and
				select "Job and Script Control Menu  [Alt-Q]" from the
				Terminal Menu ([Alt-Q] is the first item on the
				Terminal Menu).

Exiting the Terminal
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
To exit the Terminal all you must do normally is disconnect from the BBS. 
Intellicomm will then return to the BBS Directory or Main Menu.	You can
also use the Terminal [Alt-Z] Menu to exit to the Main Menu, Job Directory,
BBS Directory or to DOS (select eXit from the Alt-Z menu).	You can also
simply press a Hotkey to switch to another Intellicomm area: use the
Hotkey Menu (press [Shift-F1]) until you familiarize yourself with the
various Hotkeys.

See also:
	Terminal Menu
≡&The Terminal Menu is accessed by pressing [Alt-Z] (hold down [Alt] and tap
the [Z] key) while in the Terminal.  To use the Terminal Menu, either use
the cursor keys (Left, Right, Up, Down arrow keys) to hilight a specific
item / [Enter] to select the hilighted item; press a BOLD 'hotkey', or
click your left mouse button on a given item.

There are SIX Terminal Menu SUB-MENUS which run along the TOP of the
Terminal Menu from left to right: "Terminal" (Terminal-related items),
"Keys" (Keyboard-related items), "File Transfer" (File Transfer related
items), "Tools" (various Icom tools), and "eXit" (exit Terminal mode to
another Intellicomm area).  To open a SUB-MENU use the Left/Right arrow
cursor keys, or press the BOLD 'hotkey', or click your mouse on the sub-
menu of interest.

Most items on each Terminal Menu sub-menu can be selected directly (without
pressing [Alt-Z] first to pop up the Terminal Menu) by pressing the [Alt- ]
hotkey listed next to the item.  For example, to access the "Job and Script
Control Menu" simply press [Alt-Q].

Terminal Sub-Menu
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

Job and Script Control Menu [Alt-Q]
───────────────────────────────────
When the Terminal is in 'Auto' mode, [Alt-Q] accesses the Job and Script
Control menu, which allows you to abort a job or script, or switch into
script debug mode.

Interactive Learn Modes [Alt-Q]
───────────────────────────────
When the Terminal is in 'Manual' or 'Learn' mode, [Alt-Q] accesses the
Learn Modes menu (activate a learn mode, pause Learning, or turn learn OFF
and return to Manual mode).

Host Mode [Alt-G]
─────────────────
When the Terminal is in 'Manual' or 'Learn' mode, [Alt-G] activates
Intellicomm's Host Mode.

Goto Manual Mode Now/Later [Alt-G]
───────────────────────────────────
When the Terminal is in 'Auto' mode, [Alt-G] allows you to TEMPORARILY
switch from Auto to Manual mode.  If you select "Goto Manual Now", Icom
immediately switches to Manual; if you select "Page me just before logoff",
Icom finishes the current automated job, and pages you/switches to manual
just before logging off the BBS.  In either case, press [Alt-G] again (or
simply disconnect from the BBS) to return to 'Auto' mode.

Return to Automatic Mode [Alt-G]
────────────────────────────────
After temporarily switching to MANUAL (see above), the Terminal Menu
displays 'Return to Automatic Mode' beside the [Alt-G] hotkey, as a
reminder that Intellicomm is in TEMPORARY manual mode, and was previously
running an automated job.  Select this item (or press [Alt-G] to return to
Auto mode.

Scrollback Buffer
─────────────────
Accesses the Scrollback Buffer, allowing you to review text that has
scrolled off the screen.  TIP: You can adjust the SIZE of the Scrollback
Buffer via the main setup / Terminal Settings "Scrollback Size [Kbytes]"
item.  Defaults to 10 Kbytes (approximately 1 page per Kbyte).

Chat Mode [Alt-T]
─────────────────
Activates Chat Mode.

Script Manager [Alt-U]
──────────────────────
Accesses the Script Manager allowing you to execute or maintain your
scripts.

View/Edit BBS Notes [Alt-Y]
───────────────────────────
If a BIF is currently loaded (Icom is online), allows you to review or
modify the attached BIF Notes.  Add to the notes as you see fit, perhaps
keeping track of the BBS's hours, the Sysop's name, or any other important
information regarding a particular BBS.

Usage Log
─────────
Allows you to open, close, or pause the Usage Log (\ICOM\CAP\ICOM.USE by
default) which keeps track of important usage information such as Connect
date/time, file transfers, etc.  The Usage Log is automatically opened by
Intellicomm if 'Auto-Open Usage Log' is set to YES on the main setup /
General Settings screen.  There is no hotkey for this item: you must access
the Terminal Menu to open/close/pause the Usage Log.

Capture Log [Alt-L]
───────────────────
Allows you to open, close, or pause the Capture log (\ICOM\CAP\ICOM.CAP by
default).  The Capture Log is automatically opened by Intellicomm if 'Open
Capture on Connect' is set to YES on the main setup / General Settings
screen.  The capture log is always APPENDED (added) to.

Capture Mark [Alt-Space]
────────────────────────
Writes the line:

==<< CAPTURE MARK [nnn] >>==============================================

in the Capture log ([nnn] is a number from 1-999; the first Capture Mark
receives the number [001], the second [002], etc).  You can use Capture
Marks as reminders of important information, which you intend to review
once offline (a new BBS prompt that you want to plug into your BIF, a
bulletin you want to read carefully, etc).  Note that [Alt-Space] means
hold down [Alt] and press the space bar.

Screen Capture [Alt-S]
──────────────────────
APPENDS (adds to the end of the file) the contents of the Terminal screen
to the default Screen Capture file (\ICOM\CAP\SCREEN.CAP by default). 
Select 'Review Session Captures' from the Icom Main Menu to view the screen
capture file(s).

Clear Screen [Alt-C]
────────────────────
Clears the contents of the Terminal screen and moves the screen cursor to
the top left corner.

Hangup [Alt-H]
──────────────
Causes your modem to go 'on hook' (disconnect from the remote modem).  If
'Confirm Hangup' is set to YES on the main setup / Terminal Settings
screen, you must confirm the hangup after pressing [Alt-H].

Port Settings [Alt-P]
─────────────────────
Accesses the Port Settings menu, allowing you to change COM ports, set the
port speed, parity, data bits and stop bits.

Initialize Modem [Alt-I]
────────────────────────
Sends the 'Initialize Modem' string defined on the main setup / Terminal
Settings screen (re-initialize your modem; offline only).

Set Local Echo [Alt-E]
──────────────────────
Determines whether the Terminal displays characters you enter on the
keyboard.  If you see nothing on the screen when you type, turn Echo ON. 
If you see double characters when you type set echo OFF.  Chat Mode
automatically sets Echo ON.

Set Add Line Feeds [Shift-Tab]
──────────────────────────────
Determines whether the Terminal adds a line feed character when carriage
returns are received from the modem.  If lines overwrite each other, set
Add Line Feeds ON.	If lines are double-spaced, set Add Line Feeds OFF. 
you see nothing on the screen when you type, turn Echo ON.	Chat Mode
automatically sets Add Line Feeds ON.

Send Break Signal [Ctrl-End]
────────────────────────────
Sends a break signal to the modem.

Keys Sub-Menu
▀▀▀▀▀▀▀▀▀▀▀▀▀

Keystroke Buffer [Alt-K]
────────────────────────
Enters the Keystroke Buffer allowing you to re-send any (or all) of the
last five commands you entered to the BBS.

Doorway Mode [Alt-=]
────────────────────
Causes all Terminal HOTKEYS (other than [Alt-=] which turns Doorway mode on
AND off) to be sent to the BBS.  Of use only when using a portion of the
BBS (a full screen editor for example) that supports Doorway codes.

[Alt-1] through [Alt-9]
───────────────────────
Send the information defined on the main setup User Settings screen.

File Transfer Sub-Menu
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

Receive File[s] [PgDn]
──────────────────────
Accesses the protocol menu allowing you to select a protocol and begin a
download.

Send File[s] [PgUp]
───────────────────
Accesses the protocol menu allowing you to select a protocol and begin an
upload.

Check/set transfer mode
───────────────────────
Allows you to force internal protocols to use Binary or ASCII translation. 
ASCII translation ensures that each line is terminated with both a Carriage
Return and Line Feed (the IBM-PC standard for text files).	Of use when
transferring text files from UNIX systems.

Tools Sub-Menu
▀▀▀▀▀▀▀▀▀▀▀▀▀▀

Intellicomm Setup
─────────────────
Accesses the main setup (change all global Icom settings).	There is no
hotkey for this option.

Show WHENs [Alt-W]
──────────────────
'WHEN' is a script command used to watch for various BBS prompts and to
perform some specific action when a prompt is found.  Icom also uses its
own equivalent of 'WHEN' to track BBS prompts during automated logons, mail
runs, file transfers, etc.  'Show WHENs' shows you the prompts that Icom
(or a script) is currently watching for; and the response (sometimes, not
always) that will be sent to each prompt.  This is of use when debugging
both BIFs and scripts.

Archive Viewer [Alt-V]
──────────────────────
Calls the external Archive Viewer defined on the main setup Filenames and
Paths screen.

Script Manager [Alt-U]
──────────────────────
Accesses the Script Manager (run a script, etc).

File Manager [Alt-F]
────────────────────
Accesses the File Manager (view, edit, delete, copy files, etc).

DOS Shell [Alt-J]
─────────────────
Temporarily 'shells' to the DOS command prompt.  Type EXIT from the DOS
prompt to return to the Terminal.

Editor [Alt-A]
──────────────
Accesses the internal Text Editor or the external editor defined on the
main setup Filenames and Paths screen.

Hotkey 1 [Alt-N] / Hotkey 2 [Alt-O]
───────────────────────────────────
Calls the external program defined as the [Alt-N] or [Alt-O] Hotkey
program, on the main setup Filenames and Paths screen.

eXit Sub-Menu
▀▀▀▀▀▀▀▀▀▀▀▀▀

Back to Terminal [Esc]
──────────────────────
Exits the Terminal Menu.

To Main Menu [Alt-M]
────────────────────
Accesses the Main Menu.	If connected, you remain connected (select
"Terminal Mode" from the Main Menu to return to the Terminal).

To Job Directory [Alt-R]
────────────────────────
Accesses the Job Directory.  If connected, you remain connected (select
"Terminal" from the Job Directory to return to the Terminal).

To BBS Directory [Alt-D]
────────────────────────
Accesses the BBS Directory.  If connected, you remain connected (select
"Terminal" from the BBS Directory to return to the Terminal).

To DOS [Alt-X]
──────────────
Exits Intellicomm and returns to DOS (after confirmation).	If connected,
you are asked whether to disconnect before exiting to DOS.
Φ
The Scrollback Buffer allows you to review Terminal text which has scrolled
off the screen.  If something scrolls by too fast for you to read, press
[Alt-B] to enter the Scrollback Buffer.

The size of the Scrollback Buffer (Scrollback Size [Kbytes]) is defined in
the main setup on the Terminal Settings screen.  The default size is 10
kilobytes, which holds anywhere from 2 to 10 previous screens of text (the
length of each line in the Scrollback Buffer varies, and the longer the
lines are, the fewer lines can be stored in the 10 Kilobytes of memory
space).  The larger the Scrollback Buffer is, the slower the Terminal will
display text: since the contents of the buffer must be constantly shifted
to make room for each new line.  If you set the size of the Scrollback
Buffer to 0 (no scrollback buffer at all) the Terminal will operate more
quickly.

When you press [Alt-B] to access the Scrollback Buffer data, Intellicomm
passes the contents of the buffer to the internal Text Editor.  Thus the
keys you use while viewing (or even modifying) the scrollback data are the
same as the Text Editor.  Commonly used functions while viewing the
Scrollback Buffer data are:

[Esc]		exits the Scrollback Buffer back to the ^HTerminal^H.
[PgUp]		displays the previous page of data (if any).
[PgDn]		displays the next page of data (if any).
[Ctrl-PgUp]	displays the top-most page of data.
[Ctrl-PgDn]	displays the bottom-most page of data.
[Alt-N]		saves the entire contents of the Scrollback Buffer to a
			specific filename.
[Alt-P]		prints the entire contents of the Scrollback Buffer to the
			printer.
[Alt-F]		find specific text (up or down).
[Alt-A]		find again.

Marking Blocks
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Marking blocks of text is also useful in the Scrollback Buffer since it
allows you to print or save to disk a specific PORTION of the Scrollback
Buffer data, instead of printing/saving all data.  To mark a block, move
the cursor to the first character you want to mark, then hold down either
[Shift] key and use the cursor keys (WHILE holding down the [Shift] key)
until the text you want to mark is hilighted.  Then:

[Alt-N]		saves the marked BLOCK to a specific filename.
[Alt-P]		prints the BLOCK to the printer.
[Alt-K]		copy the block to the ^HKeystroke Buffer^H, adding a SPACE
			character to the end.  This is intended to be used for
			FILENAMES contained in the scrollback data.	For example, if
			you perform a manual file search on the BBS and several
			filenames are displayed which you want to download: press
			[Alt-B] (enter Scrollback Buffer), move to the first
			filename you want to download, hold down [Shift] then press
			the [Right] arrow key to BLOCK the filename, then press
			[Alt-K] to copy it to the Keystroke Buffer.	Do the same for
			any other files you want to download, then exit the
			Scrollback Buffer, enter the BBS [D]ownload command, and
			when asked which files to download press [Alt-K] (Keystroke
			Buffer) and follow the on-screen instructions to send all
			the filenames!  It's either that, or write the filenames
			down on a piece of paper (or try to remember them), then
			enter each filename manually.
[Alt-M]		does the same as [Alt-K] (dump to Keystroke Buffer) but
			instead of adding a SPACE after the marked block, a Carriage
			Return is added.  This allows you to dump up to 5 filenames
			from the Scrollback Buffer to the Keystroke Buffer --
			filling the 5 slots in the Keystroke Buffer, one filename
			per line.  [Of use on BBS's which don't accept multiple
			filenames on one line).
£The Port Settings menu (hotkey [Alt-P]) allows you to change COM ports, and
to set the baud rate, parity, data bits and stop bits of the current COM
port.  The menu also displays the state of the current COM port: the UART
type (either 16550 or 8250), and on/off (high/low) state of the CTS, RTS,
DSR, and DTR lines (Clear to Send, Request to Send, Data Set Ready, Data
Terminal Ready).

To operate this menu, use the cursor arrow keys (Left, Right, Up, Down) or
press the bolded letter of the item of interest or click on the item of
interest with your mouse.

To exit and return to the Terminal, select eXit, press the [Esc] key, or
click your RIGHT mouse button.
AChat Mode (hotkey [Alt-T]) is used when communicating directly with another
Terminal or modem.	Normally when you type characters, the BBS 'echoes' the
characters back and thus you see them on the screen.  But when
communicating directly with another Terminal both sides expect the other to
'echo' the characters back (which, since you're not running BBS software is
not done) and nothing you type is displayed on your screen, and nothing the
other person types at the other end is displayed on his screen.	The
solution?  You both enter into "Chat Mode", which solves this problem.

Chat Mode splits the screen display in two, and immediately 'echoes'
(displays) any characters you type to bottom portion of the screen, while
also displaying any characters the person at the other end types in the top
portion of the screen.  Further, since the person at the other end will
simply press [Enter] after each line of text (which causes his
communications program to send only a Carriage Return and NOT a Line Feed),
Chat Mode also adds a Line Feed after each Carriage Return, to ensure that
the lines from the remote user do not overwrite one another.

Using Chat Mode
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Simply type to the person you're chatting with (pressing [Enter] after each
line).  Chat Mode will display what you type in the bottom portion of the
screen, and will also immediately send the characters you type out the
current COM port so that the remote user will see what you type on his/her
screen (as you type it).

TIP: A common convention used when chatting in this way is to say what you
have to say (type what you have to type), then follow it with /ga (Go
Ahead) when you're finished.	This lets the remote user know that you're
finished, and prevents situations where you're both talking (interrupting
each other) at the same time.  For example you might type:

Hi, Jennifer, how goes it?  /ga [Enter]

...then you wait for a response from Joe, which will show up in the top
portion of the screen:

Good, how are you?	/ga

When you see the /ga from Jennifer, you can then go ahead and type
something else.

Correcting Mistakes
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Don't be overly concerned with spelling while chatting in this fashion. 
Often people will go back to correct simple spelling errors, which is
simply a waste of time, and can be quite tedious when reading from the
other end.  Unless what you meant to say is COMPLETELY lost by the spelling
error, just leave it be and continue typing.  If you just have to correct a
typing error, press the [BackSpace] key (just above the [Enter] key) to
correct your error(s).  Each time you press the [Backspace] key, it will
erase the character to the immediate left of the cursor from both your
screen and the remote user's screen.

Exiting Chat Mode
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
When you're finished chatting, simply press [Esc] to return to regular
Terminal mode.
tIntellicomm's Host Mode is a multi-featured host system which turns your
computer into a miniature BBS, providing remote users (either via modem or
direct cable linkup) with password-protected access to the following
functions:

	[L]ist Files		 [C]hat
	[F]ind a File		 [E]nter DOS command
	[V]iew File		 [S]hell to DOS
	[D]ownload		 [N]ew Directory
	[U]pload			 [H]elp
	[G]oodbye 		 [A]bort Host

Each of these commands is explained in detail in HOST.DOC which accompanies
Intellicomm.  The documentation was provided in a separate file so that it
could be made available for download by callers who are unfamiliar with
BBS's and Host Modes.

Various settings regarding Host Mode are discussed below, ALL of which are
defined in the Intellicomm main setup on the Host Mode Settings screen.

Waiting for Caller
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
While at the "Waiting for Caller" menu, Intellicomm Host is monitoring your
modem for the "Modem RING Message" (as mentioned above, this item is
defined on the main setup Host Mode Settings screen, as with all other
host-related options discussed below).	The Waiting for Caller menu gives
you access to the options listed below, and if any of these options are
selected (other than the "Terminate Host" option), Intellicomm Host sends
the "Modem Offhook Command" to take your modem off-hook so that callers
will get a busy signal until you return to the Host.  Once you return to
the Host, the "Modem Init Host Command" is then sent to the modem, which
puts the modem back on hook and readies it to accept callers.

The options on the Waiting for Caller menu are as follows:

Local Logon
───────────
Logon to the Host locally for testing purposes.  When this option is
selected, you are asked whether you wish to logon using the name defined in
the "Sysop Name" option of the Host Mode Settings main setup screen.	If
you select Yes, then the Host will not prompt you for your name or
password, and the Level 2 security level will be issued.  If you select No,
then Host prompts you for a name and password (allowing you to enter the
Level 1 password to test Level 1 access).

Terminate Host  [Esc]
─────────────────────
Terminates Intellicomm Host, leaving the caller connected.	You are asked
for confirmation before the host terminates.

Archive Viewer [Alt-V]
──────────────────────
Calls the external Archive Viewer defined on the main setup Filenames and
Paths screen.

File Manager [Alt-F]
────────────────────
Accesses the File Manager (view, edit, delete, copy files, etc).

DOS Shell [Alt-J]
─────────────────
Temporarily 'shells' to the DOS command prompt.  Type EXIT from the DOS
prompt to return to the Host.

Editor [Alt-A]
──────────────
Accesses the internal Text Editor or the external editor defined on the
main setup Filenames and Paths screen.

Hotkey 1 [Alt-N] / Hotkey 2 [Alt-O]
───────────────────────────────────
Calls the external program defined as the [Alt-N] or [Alt-O] Hotkey
program, on the main setup Filenames and Paths screen.


When a caller connects
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
When a caller is connected to the Host, you can press regular keys to help
the user along, and can also access the Host Menu (a variation of the
Waiting for Caller menu) to perform special functions.  The following keys
are of particular note while a caller is online:

[Alt-Z]	calls up the Host Menu which shows you all of the options
		available while Intellicomm Host is active, and also shows you
		all of the available 'hotkeys'.

[Esc]	Terminates Intellicomm Host.	The caller is not disconnected.

[End]	Terminates (hangs up on) the current caller, and returns to the
		"Waiting for Caller" menu.

See also:
	Host Menu
	Host Mode Settings
ÆThe Host Menu is accessed by pressing [Alt-Z] while Intellicomm Host is
active.  The Host Menu provides menu-driven access to all available Host
functions, and also lists the 'hotkeys' associated with each item.  To
Terminate the Caller, for example, you can either press [Alt-Z] and select
"Terminate Caller  [End]" from the menu, or simply press the [End] key
without going through the Host Menu.  The options on the Host Menu are as
follows:

Terminate Host  [Esc]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Terminates Intellicomm Host, leaving the caller connected.	You are asked
for confirmation before the host terminates, giving you a chance to back
out.

Terminate User  [End]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Terminates (disconnects) the current caller and returns to the Host
"Waiting for Caller" prompt.	You are asked for confirmation before the
host terminates the user, giving you a chance to back out.

Archive Viewer [Alt-V]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Calls the external Archive Viewer defined on the main setup Filenames and
Paths screen.	The caller will be "suspended" until you return from the
Archive Viewer.

File Manager [Alt-F]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Accesses the File Manager (view, edit, delete, copy files, etc).  The
caller will be "suspended" until you return from the File Manager.

DOS Shell [Alt-J]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Temporarily 'shells' to the DOS command prompt.  Type EXIT from the DOS
prompt to return to the Host. The caller will be "suspended" until you
return from DOS.

Editor [Alt-A]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Accesses the internal Text Editor or the external editor defined on the
main setup Filenames and Paths screen.	The caller will be "suspended"
until you return from the Editor.

Hotkey 1 [Alt-N] / Hotkey 2 [Alt-O]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Calls the external program defined as the [Alt-N] or [Alt-O] Hotkey
program, on the main setup Filenames and Paths screen.  The caller will be
"suspended" until you return to the Host.
äIntellicomm's dialer is accessed with no manual input while running
automated jobs.  To access the Dialer manually, for a manual online
session, switch to the BBS Directory (hotkey [Alt-D]) then hilight the BBS
you want to dial, or hilight several BBS's and "Tag" them, then select
"Dial".  Alternatively, if you do not have a BIF set up for the BBS as yet,
select "Manual" instead of "Dial", then enter the telephone number
manually.  Intellicomm will then begin dialing, and will display a menu of
the following options:

Next
▀▀▀▀
Cycles to the next number, if any, for the current BBS (up to five
telephone numbers can be defined for each BBS) and leaves the current
number in the dialing queue.	"Next" is automatically selected if any of
the three "Dial Busy/Retry" strings (main setup/Dialer Settings) are
received from the modem.  Examples: BUSY, NO CARRIER.

Exclude
▀▀▀▀▀▀▀
Cycles to the next number, if any, for the current BBS, and REMOVES the
current number in the dialing queue.  "Exclude" is automatically selected
if any of the three "Exclude Dialing" strings (main setup/Dialer Settings)
are received from the modem.	Examples: ERROR, NO DIALTONE, VOICE.

Remove
▀▀▀▀▀▀
Removes the current BBS (all telephone numbers in the current BIF) from the
queue and untags the BIF.

Timeout
▀▀▀▀▀▀▀
Allows you to temporarily adjust the timeout period.

Hold  
▀▀▀▀
Puts all dialing on hold until you press a key.  Useful if you use the same
phone line for both voice and data calls, and you have to make a phone
call.

eXit
▀▀▀▀
Stops all dialing, exits the dialer and returns to the BBS Directory menu.


See also:
	Dialer Settings
	Long Distance Services
¡The Keystroke Buffer (hotkey [Alt-K]) allows you to edit and/or re-send any
or all of your last five commands to a BBS.

Usage of the Keystroke Buffer is simple: just press [Alt-K], use the
up/down arrow keys to select the command you wish to edit or send (the
editing keys are displayed on-screen while in the Keystroke Buffer), then
either press [Alt-S] to send the currently hilit line, or [Alt-D] to 'dump'
all lines from the hilighted line onward.

Examples: You enter "D ICOM291*.ZIP Z" at a BBS and get a "File not found"
error.  You press [Alt-K], change ICOM291*.ZIP to ICOM201*.ZIP then press
[Alt-S] to re-send the command, which saves you from retyping the entire
command.
ÄCapture is used to keep records of your online sessions.  When the Capture
Log is open (\ICOM\CAP\ICOM.CAP by default), each new line from the BBS is
written to the file.  Once offline, you can then read the Capture Log by
selecting "Review Session Captures" from the Icom Main Menu.

Capture files are 'renumbered' just prior to dialing.	Where most
communications programs simply append (add) to the capture log, Icom
maintains your capture files automatically, preventing the main Capture Log
from growing to an unwieldy size.	The main setup item "Capture Renumber
Total" (on the General Settings screen) controls the number of backup
Capture Logs to keep on hand.  By default, 10 backup files (your last 10
previous online sessions) are maintained.  If you would rather maintain the
Capture Log yourself, set "Capture Renumber Total" to 0 (zero) and Icom
will simply append to the Capture Log, as with most general communications
programs.

Further, Intellicomm opens the Capture Log automatically when it connects
to a BBS.  If you would rather open the capture file manually set the "Open
Capture on Connect" item (main setup|General Settings) to NO.  You can then
selectively open/pause/close the Capture Log by using the [Alt-L] Terminal
hotkey.  It is not recommended that you handle the Capture Log in this
manner, however, as the Capture Log is your main "record" of what
Intellicomm did during automated runs.	After automated calls, and
particularly automated calls that failed, you should always check the
Capture Log (and the Usage Log ICOM.USE, and the Debugging Log ICOM.DBG,
which are stored in the same directory as the Capture Log) to see what
happened.
ÖIntellicomm's Usage Log keeps track of important usage information such as
connect/disconnect times (to verify long-distance telephone bills), and
file transfer times (to verify any extra charges you incur for downloads).

Icom uses the Call Data Standard (CDS) Usage Log format, which was
developed by a third party (Rob Rosenberger, the author of a popular Usage
Log Analyzer) in an attempt to standardize the Usage Log format of
communications programs and external protocols.  For those who use two or
more communications programs, perhaps also use external protocols with
those programs (which all use their own Usage Log standards) it's difficult
to coordinate all of the various Usage Logs with telephone bills, online
service fees, etc.	Under the CDS standard, ALL communications programs and
external protocols write to the same Usage Log file, in the same format.

Usage Log Filename
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The first step in coordinating your CDS Usage Log information is to turn on
CDS support in all external protocols / communications programs you use. 
If the program doesn't support CDS, contact the developer to see if support
can be added.	The CDS format is documented in the file CDS.ZIP on most
BBS's, and it can be implemented in just a few hours.

Once CDS Usage Log format is turned on (it's always on in Intellicomm) you
must coordinate all your communications programs to use the same FILENAME
to stamp usage information.  To change the filename Intellicomm uses,
access the main setup | Filenames and Paths screen, item "Usage Log".

External Protocols
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Communications programs that support the CDS format always make a command
line switch available to external protocols (for use in the .BAT files you
use to interface the external protocol with the communications program). 
Intellicomm passes the -CDS switch to external protocol .BAT files as
parameter 3.  Please see External Protocols for details.
3The File Picker is an alternate way to specify filenames when performing
manual uploads.  When you press [PgUp] (upload) in the Terminal and select
a protocol, you are then prompted to enter the filename(s) to upload.  If
you press [Alt-F] here, you enter the File Picker where you can select
files without typing their filenames.  The File Picker can also be used
with many external protocol uploads.

To use the File Picker, simply hilight the file you want to upload, or
hilight several files and select "Tag", then select "Send" from the bottom
menu.

To view another directory, select "Newdir" from the bottom menu.
NOTE: You cannot upload files from multiple directories using the File
Picker.  If you Tag several files, then pick "Newdir" to change to another
directory, you'll lose the previously Tagged files.
─The Download Directory is where all newly downloaded files are placed:
excluding message packets obtained during automated runs.  Message packets
are placed in the "Message Dir" instead of the Download Directory.

The Download Directory is defined in the main setup on the "Filenames and
Paths" screen (\ICOM\GET by default).  You can also override the main setup
Download Directory by defining another Download Dir in BIFs (on the BIF
"File" screen).
LThe Upload Directory is where Intellicomm looks for files when uploading
(\ICOM\SND).  Since it is inconvenient to force a single Upload Directory,
Intellicomm supports an Upload "PATH" which allows you to specify several
directories Icom will search for files to upload.  Each directory on the
Upload Path must be separated by a semicolon.  Example:

C:\ICOM\SND;C:\ICOM\GET;C:\TELIX\DOWNLOAD

The Upload PATH is defined in the main setup on the "Filenames and Paths"
screen.  You can also override the main setup Upload PATH by defining
another path in BIFs (on the BIF "File" screen).
Screen Capture (hotkey [Alt-S] only while in Terminal mode) writes the
current contents of the Terminal display to the "Screen Cap" filename
defined on the main setup Filenames and Paths screen (\ICOM\CAP\SCREEN.CAP
by default).

Screen Capture [Alt-S] always APPENDS (adds) to the Screen Capture file. 
It never overwrites it.	To prevent your Screen Capture file from growing
to an unwieldy size, the file is also 'renumbered' when the Capture File
Maintenance is performed (just prior to dialing).  See Capture for details.
V&The File Manager (hotkey [Alt-F]) is used to Edit, View, Find, Copy,
Rename/Move, and/or Delete files in a given disk directory.  You can
display any directory on any disk drive on your computer.	You can also
execute .COM, .EXE, .BAT, or .BTM (4DOS batch files) or perform a "DOS
Shell" from the File Manager to temporarily go to the DOS command prompt
for special work.  Each feature is outlined below.

To use the File Manager, you'll normally move the top hilight bar in the
window displaying the filenames to the file you're interested in, then
select an 'action' from the bottom menu.  The bottom menu options Copy,
Ren/Move, and Delete support "Tagged" files.  I.e. if you hilight and "Tag"
several files, these options operate on all tagged files (Delete asks for
confirmation first).

Current Directory
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The current drive/directory and 'filespec' being viewed are displayed in
the top border of the File Manager:

╔═╡ File Manager - C:\ICOM\*.* ╞══════════════════════════════════════════╗

The first portion (C:) is the DRIVE being displayed, the second portion
(\ICOM\) is the DIRECTORY being displayed (may also be something like
\ICOM\SCR\ if in a subdirectory) and the third portion is the 'filespec'
(standard DOS wildcards) being displayed.  Note that the directory being
displayed will also be the DOS 'current directory'.  The File Manager
performs the equivalent of a DOS "CHDIR" (change directory) command before
displaying a directory.

If wildcards (*, ?) are shown in the filespec following the directory name,
then all files matching that filespec are displayed.  For example, *.*
displays all files (and subdirectories) in the current directory.  *.SCR
displays only files with a .SCR extension.  You can change the current
drive, directory and/or filespec by selecting "Newdir" from the bottom menu
(see below).

Tag
▀▀▀
Tag works differently depending upon what is currently hilighted in the top
window.  If a <DIR> (directory) is currently hilighted, Tagging it changes
to, and displays the hilighted directory.  Tagging the "..	<DIR>" (..
means "parent" directory in DOS) you move 'up' one directory.  For example
if the File Manager was displaying C:\ICOM\*.*, and you hilighted  ".. 
<DIR>", then C:\*.* (the root directory) would be displayed.

If a regular file (as opposed to a <DIR>) is hilighted when you select Tag,
then the current tag status for the file is toggled on/off.  If the file is
tagged, a "" character is displayed to the left of the filename.  Tagging
files is handy for the Copy, Ren/Move, and Delete options (see below) when
you want to operate on several files as a group.

Edit
▀▀▀▀
Edit also works differently depending upon what is currently hilighted in
the top window.  If a <DIR> is hilighted, "Edit"ing it changes to that
directory as with the Tag option above.

If a regular file (as opposed to a <DIR>) is hilighted when you select
Edit, then a check is made to see what 'type' of file it is.  If the file
has an extension of .COM, .EXE, .BAT, or .BTM (4DOS batch file) then the
File Manager asks you whether you wish to execute the file instead of
editing it.  If you do want to execute the file, select "Yes" when asked. 
If you select "No" then the file is edited (see next paragraph).

If the hilighted file is not a .COM, .EXE, .BAT, or .BTM (or if you select
"No" when asked whether to execute a file) then the file is loaded for
editing.	'Where' the file is loaded for editing depends upon whether you
have defined an "Extnl Editor" in the Icom main setup on the "Filenames and
Paths" screen.  If you have not defined an external editor command (the
default) then the file is loaded into Icom's internal Text Editor where you
can browse through the file and modify it if need be.	If you have defined
an external editor, then the File Manager "shells out" to the external
editor, passing the full pathname of the hilighted file to the editor as
the first command line parameter.	If the external editor is capable of
loading files based on a command line parameter, then it will load the file
for editing.  If not, you'll simply enter your editor and you'll have to
load the file manually.

View
▀▀▀▀
View works the same as the "Edit" option above, but instead of loading the
file for editing, it is either loaded into Icom's internal File Viewer or
into the external viewer defined in the Icom main setup/Filenames and Paths
"File Viewer" item.  All the same rules outlined for "Edit" above apply to
the "View" option.

The difference between Edit and View is that if you Edit a file, you can
modify it, but if you View a file you can look at it, but cannot modify it. 
Further, if you have no "Extnl Editor" set up on the main setup/ Filenames
and Paths screen (i.e. you're using Icom's internal Text Editor) you can
only Edit files that are 64K or less in size.  Since the internal editor
was designed to be used as the Scrollback Buffer viewer (size must be 64K
or less), and for editing and creating scripts (which also must be 64K or
less), this 64K limit in the internal editor is not really an issue in most
cases.

However when VIEWing files, such as program DOCumentation, or CAPture files
or the like (i.e. you do not need to modify the file, you simply want to
read it) you should use the "View" option (File Viewer), which can display
files of any size.	Icom's internal File Viewer uses a fixed memory buffer
(about 4K in length) and simply loads "pieces" of the file to display, as
you move around in the file.	The Text Editor loads the entire file into
memory, and this is why it has a 64K limit.

Find
▀▀▀▀
Find allows you to search an entire disk for a given file (wildcards * and
? are supported).  To search the current drive you need only specify the
'filespec' you want to search for.  To search another disk drive, precede
the filespec with the drive letter (A:*.DOC, D:*.ZIP, etc).  The search
begins at the root directory of the specified (or current) drive, and
subdirectories are searched as they are encountered.

If a file is found matching the specified filespec, the File Manager
automatically switches to the directory in which the file was found, and
places the top hilight on the file.

Copy
▀▀▀▀
Copy is used to copy one or more files from one directory to another on the
same drive, or from one drive to another.  To copy from one directory to
another on the same drive, simply specify the destination directory without
specifying a new drive letter (\TEMP, \TEMP\SUBDIR, etc).  To copy from one
drive to another, specify the new drive letter in the destination (A:\,
B:\TEMP, D:\TEMP\SUBDIR, etc).  You needn't specify the FILENAME in the
destination; the same filename is used.  

If any files are Tagged when you select Copy, then all Tagged files are
copied to specified destination.  If no files are tagged then the file
currently hilighted in the top window is copied.

Ren/Move
▀▀▀▀▀▀▀▀
This option is used to either rename or move one or more files.	To rename
files, simply specify the new filename when asked what to rename the file
to.	To move files, specify the new directory when asked what to rename the
file(s) to (e.g. \TEMP, \TEMP\SUBDIR, etc).	When moving files, they must
be going from one directory to another on the SAME disk drive, and you must
not specify a filename (only a directory name) when asked what to rename
to.

If any files are Tagged when you select Ren/Move, then all Tagged files are
either renamed or moved.  If renaming (i.e. if you do not specify a
\DIRECTORY\ name as the new name), the File Manager prompts for a new name
for each tagged file.  If moving, then all Tagged files are moved to the
specified directory.

Delete
▀▀▀▀▀▀
Delete is used to erase one or more files from disk (permanently, unless
you have some sort of DOS "Undelete" utility installed).  If no files are
Tagged when you select Delete, the File Manager displays the name of the
file it's about to delete and asks for confirmation.  If one or more files
are Tagged when you select Delete, the File Manager tells you how many
Tagged files it's about to delete, and asks for confirmation.  If you
answer "No" when asked for confirmation, no action is taken and the Delete
is cancelled.	If you select "Yes" then the file(s) are deleted.

Untag
▀▀▀▀▀
Removes the tags () from all files.

Newdir
▀▀▀▀▀▀
Changes to, and displays a new directory.  If the directory does not exist,
you are asked whether you wish to create it (i.e. Newdir can also be used
to create new directories).  You can enter a drive, directory AND filespec
when asked which directory to you wish to view.  If you omit the drive, the
current drive ("D:" as displayed in the top border) is assumed.	If you
omit the directory (\DIRECTORY\) then the current directory is assumed.  If
you omit the filespec, then *.* (all files) is assumed.  So, to display all
files in the \TEMP directory on the current drive, you would enter "\TEMP"
(no quotes) when asked which directory you wish to view.  To view all files
in the root directory of drive D:, you'd enter "D:\" when asked what to
view.  To view only the .BAT files in the \BAT directory, you'd enter
\BAT\*.BAT (all files with a .BAT extension) when asked what to view.  Note
that the equivalent of a DOS "CHDIR" (change directory) command is also
executed, if the new drive/directory you specify is valid.

DOS
▀▀▀
Performs a DOS Shell, putting you at the DOS command prompt (C>).  From the
DOS prompt you can do anything you like including running other programs
(do not run another copy of Intellicomm, however).  When you're finished
and wish to return to the File Manager type "EXIT" (no quotes) at the
command prompt.

eXit
▀▀▀▀
eXit (or pressing the [Esc] key) exits the File Manager and returns to
wherever you were in Intellicomm previously.
BThe File Viewer can be used to view text files of any size.  To access the
File Viewer, access the File Manager or Script Manager, hilight the file
you wish to view, then select "View" from the bottom menu.

Note that you may also use an external File Viewing program such as Vern
Buerg's "LIST" by plugging an external command in the "File Viewer" item
defined on the main setup Filenames and Paths screen.

Browsing in the File Viewer
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Press [], [], [PgUp], [PgDn], [Home], or [End] to browse through the file
you're viewing.  If using a mouse, click on the SCROLLBAR that runs from
top to bottom on the right edge of the screen.  Clicking on  moves up one
line, clicking on  moves down one line, clicking between ■ and the top
arrow moves up a page, and clicking between ■ and the bottom arrow moves
down a page.  If you try to go up or down and can't, you're either at the
top or end of the text for the current topic.

The File Viewer also has a menu of options which can be accessed by
pressing [Alt-Z].  Please see File Viewer Menu for details. 
┤The File Tagger is accessed via the "Browse New BBS Files" and "View Prior
Downloads" options on Icom Main Menu.  Alternatively it can be accessed
from the Job Directory "Tools" menu (options "Tag files for Downloading"
and "Tag Files for Uploading").  There is no hotkey for the File Tagger.

If you are new to the File Tagger, or are still unsure which catalog does
what (or what 'Catalogs' are), or don't understand the View Date, auto-
purge/pack and other "fuzzy" details about the Tagger, please see the
File Tagger Introduction.

Browse Mode
▀▀▀▀▀▀▀▀▀▀▀
When you first enter the File Tagger, you are in what is called "browse
mode".  This mode allows you to view BBS file lists in much the same way as
you would on a BBS, except that you can instantly re-sort the list forwards
or backwards in any of three way, and you can move around the list of files
much more easily and conveniently.

The main purpose of the File Tagger, and main the purpose of browse mode,
is to allow you to Tag files for automated transfer by Intellicomm.  The
type of transfer performed depends upon which catalog you are viewing: if
viewing the NEWFILES catalog (or a custom catalog), you Tag files for
DOWNLOADING (from the BBS to your computer).  If viewing the FILELIST
catalog, which is a list of all the files you've auto-downloaded with
Intellicomm, you Tag files for UPLOADING (sending from your computer to the
BBS).

NOTE: Tagging a file does not cause Intellicomm to place any calls.  You
must define one or more automated JOBS (see Job Directory and Job Editor)
and "Run" them to tell Intellicomm WHEN you want to transfer the files, at
each BBS.  A job such as this can be defined and Run daily, whether you
have files tagged for transfer or not (if nothing is tagged for the BBS,
nothing is transferred):

  Pause job until 12:00am on Everyday
  Call My Favorite BBS
    Get new files list
    Upload tagged files
    Download tagged files
  Call Another BBS
    Get new files list
    Upload tagged files
    Download tagged files
  ...etc.
 
This is the type of job most people use to transfer files (the "Pause job"
is optional, but it's usually much easier to get through to a BBS late a
night; you might instead choose to run the job during the day, while you're
at work or school).  Alternatively, you can split the jobs for each BBS up
separately and selectively Tag and Run specific jobs on specific days.

Using Browse Mode - Keyboard
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Use [], [], [PgUp], PgDn], [Home] and [End] to move the top hilight bar
and browse through the file list (Home goes to the first file in the
catalog, according to the current sort order, End goes to the End of the
catalog; the rest do as you'd expect).

Once you have a file of interest hilighted in the top window, you can
perform an "action" on it by using the bottom bar menu (press the bold
letter, or move the hilight bar with [], [] then press [Enter], to select
an action.  See below for more details).

Using Browse Mode - Mouse
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Use the scrollbar on the right edge of the file window to move around the
catalog: Clicking on the  moves the hilight bar down one file,  moves it
up one file, clicking between ■ and  moves down one page, clicking between
■ and  moves up one page.

Clicking the left mouse button anywhere on a file (filename, date, size, or
description) Tags the file, while clicking the right button Notes the file.

Split Screen Report
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
As you move the hilight bar in the top window, Tagger displays the full
file description, along with some information about the currently selected
file:

File Num	  : Where the file is in the catalog, relative to the top/bottom.
Location	  : The BIF ID (BBS Information File) or Location of the file.
Priority/Day: The transfer priority and day.  See Transfer Priorities and
		    Transfer Day for details.
Trans. Time : How long it will take to transfer the file (you can customize
		    your modem's average transfer speed in the Intellicomm Setup
		    on the File Tagger Settings screen, item "File Transfer
		    Speed".
Imported	  : How many days ago the file was added to the catalog.
File Age	  : How many days old the file is, according to today's date.
File Size   : File size in kilobytes.
▒▒▒▒▒│▒▒▒▒│▒▒▒▒│▒▒▒▒│▒▒▒▒│  This graph shows the file size relative to
0K  200  400  600  800  1M  1 megabyte (quickly see how large a file is).

Action Menu
▀▀▀▀▀▀▀▀▀▀▀
The bottom bar menu allows you to perform various actions.	Tag, Note,
Edit, Del, and View all operate in the file that is currently hilighted in
the top browse window.

Tag
▀▀▀
Tags the file for automated transfer (or untags it if currently tagged; it
works as a toggle).  If a file is Tagged while viewing the FILELIST
(upload) catalog, your list of BBS Information Files is then displayed,
allowing you to Tag/Select the particular BBS's you want to upload the file
to.

Note
▀▀▀▀
Allows you to Note a file for future reference (or un-Note it, it works as
a toggle), without actually Tagging it for download.  Noted files have
their own "Auto Purge" setting (main setup, File Tagger Settings), which
allows you to keep noted files in your catalogs for longer than Untagged
files (or forever).  Further, the "View Date" does not filter out older
noted files by default (also configurable in the main setup
File Tagger Settings, item "View Date Filters Noted?").

Priority
▀▀▀▀▀▀▀▀
Allows you to set a Transfer Priority and/or Transfer Day for the currently
hilighted file (if Tagged).  See Transfer Priorities and Transfer Day for
details.

Find
▀▀▀▀
Prompts you for text to search for, and the type of search to perform (Find
Next finds the next matching file, Find Next/Tag it does the same bug tags
the file, Find All/Tag All finds all matching files and tags them [or
untags them if they are currently tagged).

The filename and description fields of all records are searched from the
hilight DOWNWARDS looking for a match.	If a match is found, the hilight is
moved to the file.	If no match is found, Tagger asks whether to search
from the TOP of the catalog downwards.	[Not applicable to Find All/Tag
All, which automatically operates right from the top of the catalog to the
bottom.]

Edit
▀▀▀▀
Enters Tagger Edit Mode, allowing you to modify the currently hilighted
record (enhance the file description, etc).

Del
▀▀▀
Toggles the current file's "Deleted" status on or off.  Deleted files are
removed from the catalog when a Pack is performed (see Tagger Tools).

View
▀▀▀▀
Of use only when viewing the FILELIST catalog, View searches for the file
and, if found, shells out to your external Archive Viewer to allow you to
view the contents of the archive.

Untag
▀▀▀▀▀
Allows you to quickly untag mass records.  You can Untag all the Noted
files, all the Tagged files, or both the Noted and Tagged files.

Sort
▀▀▀▀
Allows you to change the Tagger Sort Order.

Column 2
▀▀▀▀▀▀▀▀
The Column 2 item is now located on the "Tools" menu.	See Tagger Column 2
for details.

Load
▀▀▀▀
Displays a menu of all catalogs available and allows you to select a new
catalog to view.  Your position and sort order in the current catalog are
saved before the new catalog is loaded.

Add
▀▀▀
Adds a blank record to the catalog, then enters Tagger Edit Mode to allow
you to fill in the fields.

Tools
▀▀▀▀▀
See Tagger Tools for details.

eXit
▀▀▀▀
Exits the File Tagger.  Your position and sort order in the current catalog
are saved on exit.

See also:
	Automated Downloads
	Automated Uploads
	New Files Imports
░Changing the Tagger Sort Order allows you to change the way the catalog is
displayed.

■ Tag Status/Location  sorts Noted files first (grouped by Location), all
Tagged files second (grouped by Location), and Untagged files third (again,
grouped by Location).  "Location" means both the BIF ID of the file *and*
the File Area ON the BBS where the file is located.  For example, files in
conference 1 on the BBS are displayed first, files in conference 2 are
displayed second, and so forth.

■ Catalog Date/Filesize	sorts the catalog according to WHEN the records
were actually imported (the Catalog Date of each record is the date on
which it was added to the catalog), with the smallest files for each day
displayed first and the largest files last.

■ Filename/File Date  sorts the catalog according to the actual filenames
(similar to how most BBS's display new files lists).

You can reverse the order of any of the above by sorting the catalog
"Backwards".  For example, if this is done with the Catalog Date/Filesize
sort order, the NEWEST files are displayed first.  If done with the Tag
Status/Location sort order, Untagged files are displayed first, then Tagged
files, then noted files LAST.
\Changing "Contents of Column 2" on the Tagger's Tools menu allows you to
change the information displayed in column 2 of the main browse mode
window.  You can display either the File Sizes, File Dates, Location of
files (BIF IDs), or the Catalog Dates.

This item is saved permanently in catalog (as with the Sort
Order/Direction) when you set it.
ü-What does the File Tagger do?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Icom's File Tagger was designed to resolve the following problems with
regular BBS new files lists:

  ■	Eliminate duplicate files from one new files scan to the next.
  ■	Eliminate files you've already downloaded and thus have no interest in
	seeing again (the DOWNLOAD.NDX feature, which can be turned on or off
	on the main setup File Tagger Settings screen).
  ■	Allow automatic elimination of offensive files, or files you simply
	have no interest in (the Exclude File Keywords list defined again in
	the main setup/File Tagger Settings).
  ■	Allow easier location of files you ARE interested in (Tagger's Find,
	Find all/Tag All options, and the Note File Keywords list).
  ■	Allow offensive or abbreviated words in file descriptions to be
	automatically replaced with something more suitable to your taste
	(Replace Keywords).
  ■	Allow OFFLINE browsing of new files lists at the speed of your
	computer, instead of online browsing at the speed of your modem and
	wasting your valuable online time (and possibly incurring long-
	distance charges).
  ■	Allow quick re-sorting of new files lists in several ways, instead of
	being forced to view files rigidly the way the BBS sorts them.
  ■	Provide a way to specify (tag) files for automated file transfers:
	without having to remember and enter obscure filenames online.
  ■	Simplify the process of both uploading and downloading files (the
	Intellicomm automated transfer functions, which read File Tagger
	'catalogs' directly).
  ■	And more.

To accomplish all of this, File Tagger, through user-defined settings,
converts or "imports" regular BBS new file listings that Icom captures for
you (or extracts from mail packets) into indexed, dBASE-compatible
databases.  These databases are called Catalogs.

By default, the File Tagger maintains two catalogs: NEWFILES and FILELIST. 
The catalogs are stored in the \ICOM\DBF directory by default (configurable
in the main setup on the "Filenames and Paths" screen) and each catalog is
made up of five files: one .DBF, (database file) one .DBT (memo file for
extended file descriptions), and three .NDX files (indexes for fast re-
sorting and duplicate checking) all using the same 'base' filename.

The NEWFILES catalog is automatically created, added to, and maintained by
the File Tagger whenever you run an automated job that obtains one or more
BBS "new files listings" (see New Files Imports and BIF Learn for more
information on setting up jobs to obtain new files listings).

The FILELIST catalog is created and added to whenever Icom auto-downloads
one or more files from a BBS.  I.e. when a tagged file in the NEWFILES
catalog is successfully downloaded, Icom moves the catalog 'record'
(filename, date, original description, etc.) from the NEWFILES catalog to
the FILELIST catalog.  By viewing FILELIST later you can easily look up the
files you've downloaded up (to recall what a given program does), and can
also easily Tag files for automated UPLOAD to other BBS's.

So: when you ask Icom to auto-download files, it looks in the NEWFILES
catalog to see what (if anything) you Tagged for download, on the BBS's
Icom is about to call.  When you ask Icom to auto-upload files, it looks in
the FILELIST catalog to see what (if anything) you Tagged for upload.  
While in the File Tagger, you can switch from one catalog to another by
selecting "Load" (Load a new catalog for viewing) from bottom menu.

Note that in the registered version, Intellicomm allows multiple 'new
files' catalogs, instead of placing all new files into the NEWFILES
catalog.	This allows you to keep separate catalogs for different BBS's,
and/or even to keep separate catalogs for various "file areas" on the same
BBS.  Please see New Files Imports for more details.

Why 'Catalogs'?  Why not use text files?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
As mentioned above, Tagger catalogs are dBASE-compatible databases, and
that format was chosen for several reasons: (1) ASCII text files such as
those you download or 'capture' from the BBS are inflexible and difficult
to access and maintain, while databases allow quick and easy access to (and
maintenance of) large amounts of information; (2) databases can be quickly
'indexed' allowing instant re-sorting of information in various ways,
unlike rigid text files; (3) database indexes allow very fast duplicate
checking.  One or more duplicates from your LAST new files scan will almost
always show up on the NEXT new files scan due to the way BBS's keep track
of what new files you've seen and haven't seen.  In fact, BBS's don't keep
track of that at all: all they keep track of is the DATE on which you
performed your last new files scan.  On a BBS that posts many new files per
day, this can lead to dozens or even hundreds of duplicates from one "new"
files scan to the next, which wastes your time since you have to go through
some of the same "new" files from on scan to the next.  But by converting
the text file listings into indexed databases, the File Tagger can quickly
eliminate duplicates from one new files list to the next... thus
eliminating this problem.

In order to accomplish this the Tagger must keep (at minimum) all the files
from the LAST new files scan on-hand, to compare them to the NEXT list of
new files, to find the duplicates.  By default, the Tagger keeps 3 day's-
worth of old 'new files' around, for the purpose of duplicate checking the
next list.  After the duplicate check is complete (i.e. after each "import"
of a new files list to the NEWFILES catalog), the Tagger automatically
DELETES any new files that are more than 3 days old, since they've now
served their purpose in eliminating duplicates from the latest list of new
files.

If you like, you can change this in the Icom main setup (File Tagger
Settings/"Purge Untagged # Days Old") so that Tagger keeps older files
around longer.  If you set "Purge Untagged # Days Old" to zero, the Tagger
never deletes ANY old files from the NEWFILES or custom catalogs
automatically.  If you set it to 14, Tagger keeps two week's worth of old
files around, etc.	Purge "Untagged" means that only files that are NOT
Tagged or Noted are purged.  There is a separate auto-purge setting for
"Noted" files (defaults to zero, or never purge Noted files) while "Tagged"
files are never auto-purged.	If you tell the Tagger not to purge ANY older
untagged files, it will then be up to you to perform a manual purge (via
the Tagger Tools menu) when your catalogs get too big.

Purge versus Pack
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The 'purge' mentioned above doesn't actually remove anything from the
database.  It simply FLAGS older file records as 'Deleted'.  It's not until
a 'pack' is performed that deleted records are physically removed from the
database, freeing up the disk space they were using.  Since packs can take
a fair bit of time to complete, the Tagger doesn't perform one until at
least (by default) 30 records are flagged as deleted.	If the packs are
occurring too frequently for your liking, or not often enough, you can
adjust this 30 deleted records 'auto-pack' on the main setup
File Tagger Settings screen, item "Auto Pack when # Purged".  Again, if you
set it to 0 (zero) Tagger never performs an auto-pack and you'll have to
perform packs manually via the "Pack/Rebuild" option on the Tagger's Tools
menu.

Catalog Date
▀▀▀▀▀▀▀▀▀▀▀▀
In order to know how old a given new file is (i.e. on which date it was
added to the catalog) the Tagger must keep track of this whenever it adds a
new file to the database.  The date on which each file is added to the
catalog is called the "Catalog Date", and every file in the catalog has its
own Catalog Date.  If Tagger imports a list of new files from a BBS on the
1st day of June, 1994, each file on the list (that is not a duplicate and
is added to your catalog) will have its own "Catalog Date" of 06/01/94. 
This "catalog date" is the date the Tagger checks when performing the auto-
purge of older records, mentioned above.

View Date
▀▀▀▀▀▀▀▀▀
The Catalog Date is important not only for auto-purges, but also because
(by default) the File Tagger automatically sets its "View Date" to the date
of the last new files list import.

The View Date FILTERS OUT any files containing an older Catalog Date.  For
example, if the View Date is set to 01/01/94, only files that were imported
to the catalog on or AFTER January 1st, 1994 will be visible.  Older file
records may exist in the database, but they're not visible due to the View
Date.

By default, after each new files list import, Tagger sets the View Date to
the current date (the date of the import).  This means that ONLY the files
that are 'new' (the files that were added on the last new files import),
are displayed when you browse through the catalog the next time.  The
purpose is to weed out the files from the LAST import that are sitting
around waiting to be purged, since they've now served their purpose in
eliminating duplicate files from the current batch of new files.  I.e. the
way the Tagger is set up by default, it works in much the same way as a
real new files scan works on the BBS (minus the duplicate files from the
last scan): you only see NEW files.  You don't see files you've already
viewed previously from the LAST new files scan.

You can change this as well though.  If you don't want the View Date
updated each time a new files list is imported, set "Auto View Date Update"
to No, again on the main setup File Tagger Settings screen.  You can then
just set your View Dates manually via the Tagger Tools menu, and Tagger
won't automatically change the View Date after each import, to filter out
older records.

Further, by default the View Date does NOT filter out "Noted" files,
regardless of their Catalog Date.	But this can also be changed on the
Tagger Settings screen via item "View Date Filters Noted?".  If set to Yes,
Noted records with a Catalog Date older than the current Tagger View Date
ARE filtered out by the View Date (though they still exist in the catalog
and you can view them by manually adjusting the View Date).

You can also temporarily set your own View Dates to refer back to older
files by accessing the Tagger Tools menu, item "Set View Date".	Setting a
View Date of 01/01/90 (January 1st, 1990) will ensure that all files in the
catalog are visible.

Putting it all to use
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Hopefully with the explanations above, you've seen a logical cycle.  The
idea is that you (a) run your job(s) to pick up new files from all the
BBS's you normally get new files lists from (Tag and Run all the jobs at
once, or create a single job with multiple "Calls" and new files scans);
(b) enter the File Tagger at your next convenience and browse through the
new files, Tagging the files you want, and Noting the ones you don't want
purged (but don't want to download yet).  Then, and only then should you
run your job(s) again to get the next batch of new files.  If you don't go
through each batch of new files between the new files scans (keeping in
mind that YOU control when the new files scans are done by determining
which jobs Icom runs; you can split your "Download tagged files" and "Get
new files list" tasks off into separate jobs if you like), you'll either
lose files you never saw (due to the auto-purge of files older than 3
days), or will have to manually adjust the Tagger's "View Date" (via the
Tools menu) so that it shows you older files, from the last new files scan.

See also:
	File Tagger
	New Files Imports
	Automation in General
	Automation in Detail
≡Tagger Edit Mode is used to modify existing catalog records, or to add new
records (a 'record' is the combined items the Tagger keeps track of for
each file: Tag status, Filename, File Date, Import Date, Description, etc). 
To modify an existing record, simply hilight it from Tagger Browse Mode and
select "Edit".  To add a new record, select "Add" from the Tagger bottom
menu.

Once in Tagger Edit Mode, the [Up] and [Down] arrow keys (or mouse up/down
motion) can be used to select the 'field' (item) you wish to modify.	See
Input Text for a complete list of editing keys; see the list below for a
description of the various fields

[PgDn] (or the left mouse button) and [PgUp] (or the middle mouse button,
if available) can also be used to view/edit the next and previous record.

[Esc] (or the right mouse button) exits Edit Mode and returns to Browse
Mode.  IMPORTANT:  As with all data input throughout Intellicomm, [Esc]
cancels any changes you made to the item you are currently editing.  If you
change an item and want to SAVE it before exiting, you must press either
[Up] or [Down] or [PgUp], [PgDn] BEFORE you press the [Esc] key.  Otherwise
any changes you made to the CURRENT field are lost.

The following is a description of each field you can modify in Edit Mode:

Tagged?
▀▀▀▀▀▀▀
Enter 'T' (no quotes) to Tag the record, 'N' to Note the record, and 'U' to
Untag the record.  Records with this field set to 'T' are automatically
transferred by Intellicomm when (a) you "Run" a job that contains either a
"Download Tagged Files" or "Upload Tagged Files" task (b) the
"BIF/Location" field (below) is set to the same BIF as the job uses in its
"Call" task.

Priority
▀▀▀▀▀▀▀▀
Allows you to set a Transfer Priority if the file is Tagged.  See
Transfer Priorities for details.

Transfer Day
▀▀▀▀▀▀▀▀▀▀▀▀
If this field is set to a particular day, Intellicomm will not transfer the
file on any other day of the week.  For example, if you Run your Download
Tagged Files job once per day, and a Tagged record has a Transfer Day of
Monday, Intellicomm will not attempt to auto-download the file any other
day of the week but Monday.  The only time you'd want to use this is if you
Run your Download Tagged Files job on a regular schedule (once per day,
etc), and it will normally be used to avoid downloading a very large file
until a specific day.

Record Status
▀▀▀▀▀▀▀▀▀▀▀▀▀
Determines whether the record will be permanently removed from the catalog
on the next Pack.  You can delete and undelete records at will, since it
only sets a flag and doesn't remove the record.  Only when the catalog is
Packed will deleted records actually be removed.	To Pack you can either
wait for Intellicomm to perform an auto-pack, or can select "Pack/Rebuild"
from the Tagger Tools menu.

Filename
▀▀▀▀▀▀▀▀
The DOS filename.

File Date
▀▀▀▀▀▀▀▀▀
The file modification/creation date.

File Size
▀▀▀▀▀▀▀▀▀
The size of the file (in bytes).

Catalog Date
▀▀▀▀▀▀▀▀▀▀▀▀
The date on which this record was imported to the catalog.	This field is
used by the File Tagger both for the "View Date" feature (filtering out
older records) and to determine when a record is automatically purged
(deleted) from the catalog.  Intellicomm defaults to automatically purging
records that are *3* days old, or older based on this Catalog Date.  You
can change this 3 day auto-purge to another number (or 0 to never auto-
purge) in the Intellicomm Setup on the "File Tagger" settings screen.
The idea behind this 3 day auto-purge is to keep only enough older file
records around to do effective duplicate checking.  I.e. you browse the new
files, Tag what you want, Note files for future reference (Noted files have
a separate auto-purge number, and by default they are never purged) and
should never have to look at them again.  With the View Date and auto-purge
you won't have to browse through files you've already seen, and older
records will be automatically deleted after they've served their purpose
(duplicate checking for the next New Files Import).  The Catalog Date is
the key to all of this.

BIF/Location
▀▀▀▀▀▀▀▀▀▀▀▀
This is the BIF ID/filename that tells Intellicomm WHERE this file is to be
downloaded from.

File Area
▀▀▀▀▀▀▀▀▀
This tells Intellicomm where the file exists on the BBS (the BIF defined
above).  I.e. if a specific conference/forum has to be accessed to get the
file, the conference name/number should be defined here.

Description
▀▀▀▀▀▀▀▀▀▀▀
Loads the file's description (if any) into the Text Editor to allow you to
modify it.  Intellicomm pays no attention to your formatting of this
description when it's entered during automated uploads.  The description
line length and max. lines per description VARY from one BBS to the next,
and Intellicomm automatically reformats descriptions according to these two
items defined in the BIF on the "File" screen:

║ Chars per Line . 45			 Duplicate File .				    ║
║ Max Lines  . . . 1			 Enter Descrip. .				    ║


No matter how you formatted the description in the Tagger, Icom would RE-
FORMAT it to 45 characters per line, 1 line maximum when entering it to the
BBS on an auto-upload.  I.e. do not attempt to put boxes around your
descriptions or otherwise attempt to force a specific line length: you'll
most likely end up with a mess when you upload the file.  Descriptions
should be WORDS ONLY.
>Automatic Browse
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Enters Automatic Browse Mode, allowing you to browse through the new files
lists (and Tag/Note files) effortlessly.

Tagged File Stats  [Alt-S]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Displays a report on all Tagged files.	The report shows the number of
files tagged, total bytes of all tagged files, and the estimated transfer
time for all tagged files -- for each BBS.  If the transfer time is off,
change "File Transfer Speed [CPS]" in the Intellicomm main setup, on the
File Tagger Settings screen.

Find/Save Bookmark
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Allows you to save your place in the catalog, go somewhere else to do
something (tag a file, etc), then return to the previous position.

Set View Date
▀▀▀▀▀▀▀▀▀▀▀▀▀
Allows you to change the View Date (please see File Tagger Introduction for
information on the View Date).  Setting a View Date of 01/01/90 (or the
like) ensures that ALL files in the catalog are displayed... since
Intellicomm wasn't released on that date, so it's impossible for a file to
have a Catalog Date before January 1st, 1990.

Intellicomm Setup
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
See File Tagger Settings and Intellicomm Setup.

Import/Export
▀▀▀▀▀▀▀▀▀▀▀▀▀
See Tagger Import/Export.

Update DOWNLOAD.NDX
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Scans the disk drives/directories defined in the 'DOWNLOAD.NDX Directories'
(main setup File Tagger Settings screen) and adds any filenames that do not
exist in the DOWNLOAD.NDX index.  [Filenames that exist in DOWNLOAD.NDX are
excluded from New Files Imports, and Tagger warns you if you Tag a file for
download that exists in the index.]  If 'Use DOWNLOAD.NDX' is turned on
(main setup, Tagger Settings screen) this update is performed automatically
before all new files list imports.  Use the Tagger Tools/Update
DOWNLOAD.NDX option to perform an update manually whenever need be.

Create a new Catalog
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Creates a new catalog (the .DBF, .DBT, and 3 .NDX files) and loads it.  You
can then you one of the Import options above to add files to the empty
catalog.	NOTE: Remember that Intellicomm will NOT scan newly created
catalogs for Tagged files, nor will it automatically import to them, unless
you TELL it to, by filling the catalog name in on a BIF "Bank/List" screen
(item "Catalog to Use").  See New Files Imports for more details.

Delete a Catalog
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Deletes an existing catalog (the .DBF, .DBT, and 3 .NDX files).	You cannot
delete the catalog you are currently viewing.

Purge (Delete mass records)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Allows you to quickly delete a number of older records in the current
catalog.	Purge only MARKS records as "Deleted"; use Pack/Rebuild to
permanently remove the deleted records, and free up the disk space.

Pack/Rebuild
▀▀▀▀▀▀▀▀▀▀▀▀
Rebuilds a catalog, excluding all the records marked as "Deleted" (see
Purge above).

Archive Viewer  [Alt-V]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Calls your external Archive Viewer.

Jump to DOS  [Alt-J]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Temporarily shells to DOS.  Enter "EXIT" from the DOS prompt to return to
the File Tagger.

eXit
▀▀▀▀
Exits the tools menu (no action is performed).
╙Import BBS Lists (*.NEW)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Looks for *.NEW in the "Filelist Dir" defined on the main setup
Filenames and Paths screen (\ICOM\LST by default), and imports all .NEW
files lists into their respective catalogs (according to the BIFID of the
.NEW list).  See New Files Imports for details.

Import from Text File
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This uses the same import routine as the item above, but it allows you to
import files of any name (as opposed to *.NEW), for any BIF ID, into any
catalog (it's up to you to ensure that you have the PROPER catalog Loaded
before you use this option ... the current catalog is assumed).

One good use of this option is to import files you captured online manually
(i.e. import from the \ICOM\CAP\ICOM.CAP file).  ONLY valid file lines are
imported... extraneous BBS menus and other garbage is ignored.

Import Files from Disk
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Probably of use only when viewing the FILELIST catalog, this option prompts
you for a filespec and imports all filenames matching the filespec (* and ?
are accepted).  Once the files are imported, it's up to you to add
descriptions to the files, if you intend to upload them to an online
service that requires a file description.

Export to Text File
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Writes file records from the current catalog, to a text file, in a specific
BBS file list (BIF) format.  You can export All files, only Tagged files,
only Noted files, Tagged and Noted files, or Untagged files only.
µAutomatic Browse Mode is accessed via the Tagger Tools menu, and it allows
you to effortlessly browse through Catalogs, without even pressing a key!

Each line of the file description is hilighted for a period of time
(adjustable; see Faster/Slower below), and the time each line is hilighted
is adjusted according to the line length.  Once you get a comfortable
reading speed set, the hilight will guide you to the next file description
line just as you finish reading the previous line.

If the file description is too long to fit in the description window at the
bottom of the screen, it will scroll in the window until the full comment
is displayed.

Tag
▀▀▀
Tags the currently hilighted file for automated transfer.  If you're a
mouse user, you can Tag the current file by just keeping the mouse cursor
anywhere in the main browse window (where all the files are listed, not in
the bottom window) and clicking the left mouse button.  I.e. put your feet
up, put your mouse in your lap, sit back and enjoy.

Note
▀▀▀▀
Notes the currently hilighted file for future reference.  If you're a mouse
user, you can Note the current file by just keeping the mouse cursor
anywhere in the main browse window (where all the files are listed, not in
the bottom window) and clicking the right mouse button.

Delete
▀▀▀▀▀▀
Toggles the "Deleted" status of the currently hilighted file.

Next
▀▀▀▀
Moves to the next file immediately.

Direction
▀▀▀▀▀▀▀▀▀
Changes the autobrowse mode direction.	If you miss something, just hit
"Direction" to go back.

Faster
▀▀▀▀▀▀
Speeds up autobrowse mode (shortens the time each description line is
hilighted for).  Saved permanently when you exit autobrowse mode.

Slower
▀▀▀▀▀▀
Slows down autobrowse mode (lengthens the time each description line is
hilighted for).  Saved permanently when you exit autobrowse mode.

Pause
▀▀▀▀▀
Pauses autobrowse mode until you press a key (useful if the phone rings, or
if you want to study a particular file more closely).

eXit
▀▀▀▀
Exits autobrowse mode.
The Text Editor accessed by pressing [Alt-A] and is used to view and modify
standard ASCII text files (as opposed to word processor documents and
binary files).  It is can also be accessed by selecting "Edit" from the 
File Manager or Script Manager, and it's also used as the
Scrollback Buffer viewer, to edit BIF Notes and to edit file descriptions
in Tagger Edit Mode.

To exit the Text Editor, press the [Esc] key, or click the right mouse
button, open the eXit menu and select "Exit Editor".  If the file you're
working on was modified and has not been saved to disk as yet, the Editor
will warn you and allow you to save the file before exiting (where
applicable; not necessary for BIF Notes or editing descriptions in the File
Tagger).

Until you memorize the editor hotkeys (or if you prefer to use a mouse),
the Text Editor's menu can be used.  To access the menu, press [Alt-Z], the
right mouse button, or click on "Alt-Z for Menu" on the editor status line
with your mouse.

See also:
	Editor Cursor Keys
	Working with Blocks
╟Most everything that happens in the Text Editor takes place at the cursor
position.  To move the cursor with your mouse, use the scrollbar on the
right side of the screen.  It works the same as the scrollbar in the help
system; press [F1] for details if you need 'em.  To move the cursor with
the keyboard, use the usual keys:

[Left]		Moves the cursor one character to the left, or the next line
			if at the end of the line.
[Right]		Moves right one character, or to the previous line if at the
			beginning of the line.
[Ctrl-Left]	Moves to the beginning of the next word.
[Ctrl-Right]	Moves to the beginning of the previous word.
[Home]		Moves the cursor to the first character on the current line.
[End]		To the last character on the current line.
[Up] 		Rolls up the window.  No wait, that's what [Up] does in my
			car...  It moves the cursor up a line in the editor.
[Down]		Three guesses.
[PgUp]		Moves up one screen (if possible).
[PgDn]		Moves down one screen (if possible).
[Ctrl-PgUp]	Moves to the first character in the file.
[Ctrl-PgDn]	Moves to the last line in the file.

You can also move the cursor to a specific line number using [Ctrl-Home].

After you've got the cursor where you want it, check whether you're in
Insert or Typeover mode (see the status line, or the cursor; it's half-
height in insert mode and a small line in typeover mode) and start typing. 

Use the [Del] key to delete the character AT the cursor, use [Backspace] to
delete the character to the LEFT of the cursor.  You can also delete end-
of-line characters (joining two lines together) using either [Del] or
[Backspace].  To delete all characters from the cursor to the end of the
line, press [Ctrl-End].

See also:
	Working with Blocks
,When you want to delete, cut/paste (move), copy, clear, save to disk, or
print one or more characters, first block the text you're interested in
(see below) then use one of the block commands.

To mark a block with the keyboard, just hold down one of the [Shift] keys
while pressing an Editor Cursor Key.  For example, to block one line, move
the cursor to the beginning of the line (press [Home]), then hold down
[Shift] and tap [End].  The blocked text will be displayed in a different
color.

To mark a block with your mouse, move the mouse cursor to the starting
position, then press and hold the left button (or right button if in
lefthanded mode) while moving the mouse cursor where you want to end the
block.  While marking a block with your mouse, if you move the mouse cursor
on to the editor border/status line, the text scrolls (to let you mark
blocks larger than can be displayed on the screen).

Once the block is marked:

[Alt-N]		to save it to disk in another file.  [Alt-N] is normally
			"Save as...", but it changes to "Save BLOCK" when a block is
			marked.
[Alt-P]		to print the block to your printer.  Make sure your printer
			is turned on and loaded with paper BEFORE you press [Alt-P]. 
			See Printing Problems if you have a problem.  Note that
			[Alt-P] normally prints the entire file, but it changes to
			"Print BLOCK" if a block is marked.
[Shift-Del]	cuts the block for later use with [Shift-Ins] (used to move
			text from one place to another).  Cut first SAVES the block
			to an internal clipboard, then deletes it.
[Ctrl-Ins]	similar to "cut" above, this saves the blocked text to an
			internal clipboard (for later use with [Shift-Ins]), but it
			doesn't delete the block after saving it (this is used to
			COPY text from one location to another).
[Shift-Ins]	pastes the last block saved to the internal clipboard (with
			either [Shift-Del] or [Ctrl-Ins]) to the CURRENT CURSOR
			POSITION.  I.e. cut/copy the block first, then move the
			cursor to where you want to paste the block, and press
			[Shift-Ins].
[Del]		deletes the block.	This is similar to [Shift-Del] (cut),
			but it doesn't save the block in the internal clipboard, and
			thus it cannot be pasted with [Shift-Ins].  Blocks deleted
			in this manner ARE saved, however, and you can get them back
			by pressing "Undo" ([Alt-Backspace]).  Note that [Del]
			normally deletes only the character at the cursor position,
			but if a block is marked it deletes the block instead.
[Ctrl-Del]	clears the blocked area, leaving the end-of-line characters;
			Use [Del] (explained above) to clear the end-of-line
			characters as well.  You can also reverse a [Ctrl-Del] by
			pressing "Undo" ([Alt-Backspace]).

To unmark a block without doing anything, just release the [Shift] key then
press a cursor key.  Or release your mouse button and click once.
LHilight the file you wish to edit, then select "Edit" from the bottom menu.
IThe Job Pause Menu is displayed when Intellicomm executes a "Pause job
until HH:MM on XXXDay" or "Repeat job at HH:MM on XXXDay" task in an
automated job (see Job Editor for setup details).  The menu allows you to
regain control of your computer during a pause (shell to DOS, etc), or to
cancel the pause.

Start Now
▀▀▀▀▀▀▀▀▀
Cancels the pause, and begins the automated job immediately.

Cancel Job
▀▀▀▀▀▀▀▀▀▀
Cancels the pause, and aborts the automated job (return to manual mode).

Mail Reader
▀▀▀▀▀▀▀▀▀▀▀
Shells out to your external Mail Reader.

Archive Viewer
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Shells out to your external Archive Viewer.

Jump to DOS
▀▀▀▀▀▀▀▀▀▀▀
Shells out to the DOS command prompt.

Run Editor
▀▀▀▀▀▀▀▀▀▀
Enters either Icom's internal Text Editor, or the external editor defined
on the main setup Filenames and Paths screen.
]Exit BIF Editor options:

 ■ Press ENTER to RE-SAVE the BIF under the same name (only if
   editing a previously saved BIF).

 ■ Press ESC to exit and ABANDON any changes you made.

 ■ Press   to CANCEL eXiting and return to the BIF Editor.

 ■ Enter a NEW FILENAME to save this information in a different
   BIF (or create a new one).  The filename you use to save a BIF is
   called the "BIF ID", and is used in various places in Intellicomm to
   identify a particular BBS.  The filename you enter should remind
   you of the name of the BBS (e.g. Joe's BBS could be saved with an
   ID of JOESBBS).
─In order to perform Automated Downloads, you first must get some BBS
filenames imported into the File Tagger.  There are several ways of
accomplishing this, but the easiest is to simply add a "Get new files list"
task to your automated job that calls the BBS.  Example:

Call Joe's BBS
  Get new files list
  Download tagged files

Such a job (assuming the BIF for Joe's BBS is set up properly) will call
Joe's BBS, ask the BBS for all the new files and capture the results to a
special file (\ICOM\LST\BIFID.NEW ... NEW for "New" files).  If any files
were previously imported and Tagged for download in the File Tagger they'd
also be downloaded automatically, due to the "Download tagged files" task. 
Once disconnected the BIFID.NEW file is then automatically imported into
the File Tagger.

Alternatively, if you're using a QWK-based mail system that is capable of
including a new files listing with your mail (Qmail, Tomcat, etc., you must
[C]onfigure the door to send a new files list before it'll include one),
you can simply run a job that picks up the mail, and Intellicomm will
automatically extract the new files list from the QWK packet and import
them that way.

You can also capture new files listings (you can even leave them in
ICOM.CAP, you needn't open a special capture file) manually or through a
job Custom Command, then use the Tagger Tools | Import from Text File
option to import the files into the database you're currently viewing.

Finally, you can also download file listings from your BBS (if they're
available for download), uncompress them if necessary, then use the Tagger
Tools | Import from Text File option to import the list that way.  It is
not intended that you keep entire BBS file lists in Tagger Catalogs, though
you 'can' do it if you have the disk space to spare.  If you use this
method, you MUST set the Auto Purge item in the File Tagger Settings (in
the Icom main setup) to 0.  Otherwise Icom will eventually PURGE (delete)
files from the database.

TROUBLESHOOTING: If you have problems with your imports (if nothing gets
imported, or if it's just not importing various fields correctly), the
problem is almost surely on the BIF Bank/List Screen in the BIF Editor
(press [Alt-D] then hilight the problem BIF and select "Edit" to get to the
BIF Editor, then choose "Bank/List" from the bottom menu).	On this BIF
screen all the details about the BBS file listing can be modified to suit
the BBS you call.  Study a BBS new files list, make note of the positions
of all the various items (Filename position, date position, etc.) then plug
the proper positions into the BIF and your imports should work fine.	The
most crucial settings are the DATE position settings, and the DATE
SEPARATOR.  The date is how Icom separates valid file lines from other
lines on the new files list.	See the BIF Bank/List Screen help link for
more details.

Another common problem is a misunderstanding of the Tagger "View Date". 
When the Tagger imports a new files list, it automatically sets the View
Date to the DATE OF THE IMPORT.  Thus only the files on the LAST new files
import are displayed when you enter the Tagger.  If nothing was imported,
when you enter the Tagger it will show you an empty catalog.  The previous
files are still there... they're just being filtered out due to the View
Date.  You can shut off this automatic update of the View Date in the Icom
main setup on the File Tagger Settings screen.  You can also manually
adjust the View Date when browsing the catalog by selecting "Tools" / "Set
View Date" from inside the File Tagger.  Please see
File Tagger Introduction for more details on the View Date.

REGISTERED USER TIP: By default, Intellicomm imports all new files to the
NEWFILES database.	If you want to have the files from a specific BBS
imported into another database, just edit the BIF for the BBS (as described
above), switch to the "Bank/List" screen, and enter a new database name in
the "Catalog to use" item, then eXit and re-save the BIF.  You needn't
create the database; Icom will create it automatically before the first
import.  It will also make sure to scan that database for tagged files
whenever you request an automated download.	But you have to be sure that
you REQUEST a download for that particular BIF.  For example, if you have
two BIFs set up for the same BBS, and you have the new files from one
conference go into the NEWFILES database, but have files from another
conference go into, say a GAMES database, then you must define your job as
follows to get Icom to import to/scan the GAMES database for tagged files:

Call Joe's BBS 		    [the BIF without the GAMES database defined.]
  Area: 0 			    [the "Change BBS/File areas" task.]
  Get new files list	    [new files imported into NEWFILES database.]
  Download tagged files	    [scans ONLY the NEWFILES database.]
Switch to Joe's BBS - GAMES  [the BIF WITH the GAMES database defined.]
  Area: 10			    [changes to conference 10.]
  Get new files list	    [new files imported into GAMES database.]
  Download tagged files	    [scans ONLY the GAMES database.]

How to define a "Switch to"?	Just select the "BBS" option from the Job
Editor's bottom menu, and when asked whether to Disconnect select "No". 
Then Select the appropriate BIF and the "Switch to" will be included in
your job.

Of course, if you want ALL the new files from a given BBS to go into a
different database, you needn't (and can't) use a "Switch to" task in your
job... or the BBS will never be dialed.  "Switch to" simply causes
Intellicomm to LOAD a new BIF and use the settings in the new BIF (in this
case, namely the new catalog name).  It doesn't cause a call to take place. 
You'd simply define the new database name in your BIF (as outlined above)
and run your normal job:

Call Joe's BBS 		   [the BIF has a special catalog defined.]
  Get new files list	   [imported into the special catalog.]
  Download tagged files	   [scans the special catalog for downloads.]

For these cases you needn't do anything but define the special catalog name
in the BIF.  

Use of multiple new files catalogs is a bonus feature available only in the
registered version of Intellicomm.

TIP 2: You can also manually import BBS file listings (from a .CAP file, or
downloaded from the BBS) by accessing the File Tagger ([Alt-M], F),
selecting "Load" (if necessary) to load the catalog you want to import to,
then select "Tools" | "Import from Text File".

See also:
	File Tagger
	Strip Comment Keywords
	Replace Keywords
	Exclude File Keywords
	Note File Keywords
µIn order to make use of the File Tagger and thus Automated Downloads, and
Automated Uploads, the first step is to "import" one or more listings of
BBS files into your File Tagger Catalogs.  The process of importing is
covered in the New Files Imports link.	BEFORE importing any prospective
new file into your Tagger Catalogs, Intellicomm checks each file against
four different lists of "keyword" text, which gives you complete control
over both HOW files, and WHICH files get imported into your catalogs. 
Keywords are defined using the keyword editor, which is accessed through
the Intellicomm Setup / File Tagger Settings.

The keyword editor can handle 64K's worth of data for EACH of the four
lists of keywords, so you can define quite a few thousand keywords if you
want to.	But, since each and every keyword is compared to each and every
file description (and filename in some cases) Intellicomm runs across on
BBS new files lists, each keyword you add to each of the lists is going to
slow down your import times.	So try to keep the number of total keywords
down to a reasonable number if you're concerned about speedy imports.  If
you've got a 486 and a fast hard drive, then you probably won't notice much
of a difference between having ten or fifty keywords defined.  If your
system is slow, you'll notice the difference more.

However, the best way to use Intellicomm is to run it either when you're
out or sleeping.  If you do that then imports will take place automatically
when the job finishes, import times thus won't concern you, and you can
define as many keywords as you like no matter what the speed of your
system.

It's important to understand how the keywords work before you set out
defining too many of them.  You could end up stripping comment lines that
shouldn't have been stripped, missing out on interesting files, or creating
nonsense file descriptions through the improper use of the keywords.

To make sure you're matching the exact word(s) you have in mind, precede
and/or follow your keywords with spaces when possible.  For example "win"
would match "windows" and would also match "Darwin", since both contain the
letters "win".  If you want just the word "win" define it as " win " (with
a space preceding and/or following the word).  Intellicomm automatically
re-formats file descriptions before applying them to the keywords; and it
inserts a space prior to the first/last words in the description, and
replaces CR's (end of line) with a space... so a description such as this:

Description line 1.
Description line 2.

ends up as " Description line 1. Description line 2. " before it's compared
to the keywords (a space is also temporarily added to the beginning AND end
of the description text).  I.e. there are always spaces at the beginning
and end of each line, allowing you to PRECEDE or FOLLOW your keywords with
a space, if you want it to match the beginning and/or end of a word.

When defining Replace Keywords, you must also be sure that if you use one
or more spaces in the search portion of the string, that you do the same in
the replace portion, or the spaces will be lost and the word will merge
into the previous word.	Example:

 win31;Windows 3.1

[Note the space preceding "win31", and no space preceding "Windows 3.1"
after the semicolon.]  On a description containing the following:

"This is a Win31 utility."

you'd end up with:

"This is aWindows 3.1 utility."

Search/replace FIRST deletes the search text (including the space, since
there's a space in the search text), and then replaces it with the replace
text; which wasn't preceded with a space in the example above.  So the
space is lost.

Intellicomm re-formats descriptions after all the keywords have done their
work, strips all control characters (and all IBM graphics characters if you
have the "Strip Graphics Chars" option turned on in the main setup
File Tagger Settings) and will either wrap words to the next line if the
line ended up longer than can be displayed, or will pull words up from the
next line if text was removed from the previous line.	It's similar to what
a word processor does to adjust paragraphs to fit within the margins when
you add/remove text.

If you later have Icom auto-upload the file to a BBS, then the description
is again re-formatted to fit within whatever margins the BBS uses (defined
in the BIF in the "File" screen's "Chars per line" and "Max lines" items). 
If the descriptions aren't sent to the BBS properly on Automated Uploads,
you can adjust the BIF accordingly to remedy the situation.
╨
For general help with the editor, see Text Editor.

Strip Comment Keywords are used to strip unwanted text from the EXTENDED
description/comment lines of BBS new files lists (if you are unfamiliar
with imports, and keywords in general please see the Keyword Tips).  Before
Icom imports a new file, it checks each file's extended description lines
(any lines below the first description line) for any matches in your list
of defined Strip Comment Keywords.  If a match is found, then everything
from the position of the match to the end of the description is stripped. 
Case is not significant, so "text", "TEXT" and "Text" are all considered
the same.  For example, if you define:

uploaded by:

as a Strip Comment Keyword, and Intellicomm runs across a file containing
the following description:

ZIGGY.ZIP 	  1234  12-01-94  ZIGGY.ZIP main comment line.
						   ZIGGY.ZIP extended comment line 1.
						   Uploaded by: David Bowie

then the text "Uploaded by:", and everything from that point to the end of
the description will be stripped (the entire last line in this case).  If
any other lines followed the "Uploaded by:" line they would also be
stripped.  These keywords are provided specifically for stripping the type
of text in the example above, and won't be of much use for anything else. 

The reason Tagger strips all the text right to the end of the description
is due to the fact that there is always some "variable" text (David Bowie,
above) that follows the keywords, which must also be removed.  The reason
Strip Comment Keywords don't affect the main (1st) comment line is because
the type of things these keywords are intended to strip ALWAYS appear only
in extended comment lines, after the main file description. 

"Uploaded by:" is something you see mainly on PCBoard BBS's, and there are
various other 'garbage' lines added to descriptions such as "Last date in
archive:", "Oldest: MM-DD-YY	Newest: MM-DD-YY" and so forth, that you
might also want stripped.  Make sure you define a good portion of the
keyword (and punctuation, such as a colon [:] where possible) to avoid
having valid comment lines stripped.  Use spaces IN the keywords themselves
too, to make sure you've got the word(s) you want (see the Keyword Tips for
more information on that).

When you want to strip specific text without stripping to the end of the
description, or want text in the main description line to be removed, use
the Replace Keywords.

Strip Comment Keywords are the first set of keywords applied to BBS file
listings on imports, and they are followed (in the order shown) by the
other types of keywords listed below.

See also:
	Keyword Tips
	New Files Imports
	Replace Keywords
	Exclude File Keywords
	Note File Keywords
	File Tagger
≈
For general help with the editor, see Text Editor.

Replace Keywords are used to search for/replace text in ALL file comment
lines, during imports of BBS new files listings.	To define these keywords
enter them in the format:

search for this;replace with this

with a semicolon (;) separating the search/replace text.  In the example
above, portions of file comment lines that contained the text "search for
this" would be replaced with the text "replace with this".	No spaces
should be used before or after the semicolon -- unless you also want spaces
to count in the search and/or replace text.	Often spaces can be very
useful in making sure you've got the words you want (tips on using spaces
are given in Keyword Tips).

Replace Keywords can also be used to STRIP unwanted text entirely, since
you needn't define a replace string (in which case the search string is
eliminated and is replaced with nothing at all).	Examples:

remove this;
remove this

Note the semicolon following the text in the first example with no 'replace
text' following the semicolon, and the lack of a semicolon in the second
example.	Both have the effect of simply removing the text "remove this".

If you must use a semicolon in the search portion of the string, precede it
with a caret (^) to have Icom treat it literally and not use it as the
search/replace separator.  Example:

search^; for this;replace; with this

This causes occurrences of "search; for this" to be replaced with
"replace; with this".  You don't have to use a caret in the replace portion
of the keyword -- only in the search portion prior to the ; separator.  If
you used "replace^; with this", then you'd get the caret in the replace
text.

One use of these keywords is to replace annoying or offensive text in file
descriptions with something you prefer; or just to remove redundant
adjectives ("very, very nice" could be changed to "nice").	If you get
tired of looking at the word "awesome", you could define a few
search/replace keywords to change it:

 awesome; interesting
 awesome!; interesting.
 awesome!!; interesting.
 awesome!!!; interesting.

Intellicomm would then replace the text " awesome" (or AWESOME, or
Awesome... case is insignificant) and all the other variations with
exclamation marks with the text " interesting" or " interesting." whenever
it was found in a file description.  The space preceding each keyword is
intentional and is used to make sure we really have the word we want and
not just a portion of another word.  You can also do something like this:

 win3; Windows 3
 win 3; Windows 3
 windoze; Windows
 wp5; WordPerfect 5
 wp 5; WordPerfect 5

and automatically improve upon the descriptions of hasty people who don't
bother to type in the whole word.	Then, when you're doing searches in your
Tagger Catalogs (or when using the Exclude File Keywords and
Note File Keywords which follow these replace keywords), you can perform
the search on the word "Windows" without worrying about missing the files
that only state Win3 or Win 3.  Obviously you want to be careful about the
words you pick... you wouldn't want to just use "win;Windows", since that
would cause the phrase "win money" to end up as "Windows money", and so
forth.  You can avoid these types of problems by using numerals,
punctuation, and/or spaces in the search (and replace) portion of your
keyword, as in the examples above.  See the Keyword Tips for more tips on
defining keywords.

See also:
	New Files Imports
	Strip Comment Keywords
	Exclude File Keywords
	Note File Keywords
	File Tagger
^For general help with the editor, see Text Editor.

Exclude File Keywords are applied to BOTH the FILENAME.EXT of the file and
ALL file description lines during a BBS new files list import -- after the
Strip Comment Keywords and Replace Keywords have done their work.  These
keywords are used to avoid importing files you have no interest in.  For
example, if you aren't interested in games or pictures, you could define
the following keywords:

game
.GIF
.MAC
.PIC
.FLI

The first keyword would eliminate any files that contained "game" (or GAME,
or Game... case is insignificant) in the filename or description.  The
subsequent keywords would (due to the .) match file extensions, eliminating
any files with the extension .GIF, .MAC, .PIC, or .FLI.  Note that even if
your BBS file listing displays filenames without a period separator:

EXAMPLE	ZIP	  123456	MM-DD-YY	File description.

Intellicomm will have reformatted the filename to EXAMPLE.ZIP by the time
these keywords see the filename.  So you can always use .EXT to specify
file extensions.

You also want to be careful with the way you define these keywords (see the
Keyword Tips) to avoid accidentally excluding files you ARE interested in. 
Don't go overboard with them.

See also:
	Keyword Tips
	New Files Imports
	Strip Comment Keywords
	Replace Keywords
	Note File Keywords
	File Tagger
ùFor general help with the editor, see Text Editor.

The Note File Keywords are used to have the File Tagger point out BBS files
you're especially interested in.  Before Intellicomm imports BBS new files
listings, it compares the FILENAME.EXT of the file, and all file
description lines of each file, to your list of Note File Keywords.  If any
of the keywords are located, the file will be specially marked and will
show up in the Tagger with a double arrow (») to the left of the filename.
 
For example, if you're interested in Intellicomm, Windows and WordPerfect
add-ons, you could define the following Note File Keywords:

Intelicom
Intellicom
Icom
Icomm
WIN3
WIN 3
WordPerf
WP5
WP 5

Any files containing any of these keywords in either the filename or file
comment would be "noted" for you.	The Note File Keywords are the last set
of keywords to be applied to a potential new file before it gets imported
into the catalog (within the usual duplicate checking rules).  You can use
this to your advantage, since the Replace Keywords will already have done
their work on the file description, and could change all the occurrences of
"Intelicom", "Intellicom", "Icom", and "Icomm" to "Intellicomm".  And then
you wouldn't have to define all these variations here in your Note File
Keywords.  Please see the Replace Keywords link for more information.

TIP:  "Noted" files are also special to the Tagger in that they are NOT
purged by the Tagger 'Auto Purge' routines (see File Tagger Settings), nor
are they filtered by the
View Date setting as other files are (both of those 'rules' can be changed
via the Icom main setup, File Tagger Settings screen, if you'd like things
to work differently).  As well, by using the Tagger's "Sort" option and
setting the sort order to Tag Status/Location, you can sort all noted files
together at the top of the catalog; which makes it easy to view all the
interesting files at once.  You can also operate on noted files as a group:
"Untag" in the Tagger allows you to remove the "note" status from all noted
files.

See also:
	Keyword Tips
	New Files Imports
	Strip Comment Keywords
	Replace Keywords
	Note File Keywords
	File Tagger
1There is a little-used (as yet) but very useful feature built into
Intellicomm that allows complete automation on any BBS by just downloading
a small file from the BBS.  The file is ICOMAUTO.ZIP, and if available it
will contain a complete pre-configured BIF for the BBS, and possibly even a
list of interesting BBS files to auto-download!  Logon the BBS using the
Dialer, then download ICOMAUTO.ZIP, logoff/disconnect, and Icom will
extract the BIF(s) in ICOMAUTO.ZIP, will prompt you for any necessary
information such as Logon Name, Password, etc., will display any special
BBS Notes contained in the BIF, will install the BIF in your BBS Directory,
will import into the File Tagger any files lists included in the
ICOMAUTO.ZIP (assuming you don't already have the files, or are filtering
certain files out with Exclude Keywords; they're ignored in that case), and
will even create several jobs to automate various tasks on the BBS, ready
for immediate use!	All with a simple download.

Where does ICOMAUTO.ZIP come from?  It comes from someone just like you,
who previously called the BBS and set up a BIF.  Once you get *any* BIF
working for *any* BBS you should create an ICOMAUTO.ZIP and upload it to
the BBS so that every other Intellicomm user who calls the BBS can avoid
the BIF setup.  Meanwhile, other Intellicomm users will be doing the same
for you at other BBS's you might call in the future.  Creating an
ICOMAUTO.ZIP is simple:

1.	Use BIF Learn to get your BIF set up and working.  Test it for a
	couple of weeks, doing mail runs, auto-file uploads/downloads, new
	files imports, bank transactions if available, file searches, etc.
2.	When the BIF is working, Edit it from the BBS Directory and replace
	your logon name with %FIRST% %LAST%.  For example, if your BIF
	contained John^MSmith (^M is ENTER... you might use a space instead if
	the BBS accepts both names at once), you'd change it to
	%FIRST%^M%LAST%.  Make sure to also change any OTHER occurrences of
	your name if used in any BIF prompts.  People sometimes use part of
	their name in the BIF Logon "Confirm" prompt and if that's the case
	you should replace your name in the prompt with %LAST% to have the
	user's own name used in the BIF prompt.
2.	Change any occurrences of your Birth Date to %BDATE%, and any
	occurrences of your Home Phone Number to %HPHONE% (i.e. on the BIF
	"Extra" screen, if applicable).
3.	Save the BIF, then press [Alt-X] to exit Intellicomm, and ZIP it up
	with these three commands:

	CD \ICOM\SND
	PKZIP ICOMAUTO.ZIP \ICOM\BIF\BIFNAME.BIF
	COPY ICOMAUTO.ZIP \ICOM\GET

	where \ICOM\SND is your Upload Directory, \ICOM\BIF is your BIF
	Directory, BIFNAME is the filename you used to save the BIF, and
	\ICOM\GET is your Download Directory.  DO NOT enter BIFNAME.BIF ...
	you must substitute with the real name of the BIF (e.g. JOESBBS.BIF).
4.	Start Intellicomm again and watch what happens.  It should find the
	ICOMAUTO.ZIP in \ICOM\GET (and will think you downloaded it), rename
	it to ICOMA000.ZIP (so the file doesn't get processed twice), extract
	the BIF, display the BIF Notes you entered (if any) ask you for your
	FIRST and LAST names, ask for your Birth Date and Home Phone Number if
	you used %BDATE% and/or %HPHONE%, and ask you whether you want to
	create automated jobs for the BIF.  If everything worked, upload
	ICOMAUTO.ZIP to the BBS with a description of: "Intellicomm Auto-BIF
	for BBS Name", where BBS Name is the name of the BBS.

NOTE: If something goes wrong and you want to start over, you'll find the
original BIF (with %FIRST% %LAST%, etc) in \ICOM\BIF renamed to BIFNAME.OLD
(where BIFNAME is the name of the BIF).  

The theory behind this is that ONE person does this for each BBS.  It only
has to be done once, per BBS, and in time (assuming you think it's a
reasonable concept and participate) there will be ICOMAUTO.ZIPs available
everywhere.  And imagine how pleasant BBSing will become when that day
comes!  No script writing... no flaky "learned" scripts, just reliable
automated communications with NO setup work at all, save for downloading a
single file.

NOTE: If you upload an ICOMAUTO.ZIP without making sure the BIF within it
works first (for both mail and file transfers), and without copying
ICOMAUTO.ZIP into \ICOM\GET and giving it a test run, you may end up doing
more harm than good.  It's something that only has to be done ONCE and it
must be done correctly to be of any use to fellow Intellicomm users.

This topic is explained in much more detail and with many more tips in
AUTOICOM.DOC.	Please give this document a read now for more detailed
information (7 pages... nothing major).
*There are two types of interactive Learn Modes available in Intellicomm. 
Please select the type you are interested in:

	BIF Learn
	Script Learn

Also see BIF Overview for a quick outline of BIFs (BBS Information Files)
and the advantage they have over scripts and Script Learn.	There are
important differences that you should be aware of before choosing a learn
mode.

See also:
	ICOMAUTO Easy Setups
	BIF Learn - Message/Reply Transfers
	BIF Learn - New Files Collection
	BIF Learn - File Downloads
	BIF Learn - Time Bank Transactions
í&BIF Learn is used to help you set Intellicomm up for automation of various
BBS online tasks such as logons, message transfers, and file downloads. 
However, is not meant to be used to call an unfamiliar BBS for the *first*
time!  To call a BBS the very first time (meaning you've never called the
BBS with Intellicomm or any other comm. program) you should use the
@Temporary BIF and the BBS Directory "Dial" option (or use no BIF at all,
and just enter the telephone number via the "Manual" option).  Anything you
plan to automate, whether it's a mail run, downloads, new files list
collection, or a time bank transaction: it should be done at least once
MANUALLY before you attempt automation.  By doing something manually first,
it ensures that you've set the BBS (or the mail system, etc) up properly
FIRST, before Intellicomm attempts to automate.  Manual use will also give
you crucial information, such as the TYPE of mail system in use on the BBS,
and the PACKET FILENAMES used, etc.  Icom can't automate tasks that you
haven't even done manually yet!

Two things are needed for automation: (1) a BBS Information File (BIF) that
contains the information necessary to accomplish the task (the BBS prompts
Icom will watch for, and the proper responses and commands to send to those
prompts); (2) an automated JOB that tells Intellicomm what to do when
online (logon/switch to manual, logon/get mail and send replies,
logon/download files, etc).  The JOBS tell Icom *what* to automate, the
BIFs tell Icom *how* to automate it on a particular BBS.  BIF Learn will
help you to create both a BIF, and the automated job(s) needed to use the
BIF for unattended communications.

Script Learn can also be used to automate BBS tasks, and actually requires
slightly less input from you than BIF Learn does.  But there are important
differences between BIF Learn and Script Learn that you should be aware of
before you choose to use Script Learn.	The BIF Overview link outlines the
most important differences between BIF Learn and Script Learn modes, and
also will give you a good idea how BIFs work if you aren't familiar with
them as yet.

To activate BIF Learn, press [Alt-Q] (hold down the [Alt] key then tap
[Q]), or select "Learn" from either the Main Menu, BBS Directory, Job
Directory (Tools) or Terminal menu.  The [Alt-Q] key is used simply because
it's one of the few hotkeys left available after the usual terminal hotkeys
were used.

Note that Learn can only be activated when Intellicomm is in Manual Mode:
you cannot activate it while running an automated job or script.  [Alt-Q]
pops up the "Job and Script Control Menu" when an automated job or script
is running, which allows you to cancel or 'Q'uit auto mode and return to
manual.

The first order of business after activating BIF Learn is to specify
whether you wish to Create a new BIF or Modify an existing BIF.

Create a new BIF
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Select Create to start fresh with a new BIF (this is what you want on your
first time using BIF Learn).	You will be prompted for the BBS/Host Name,
the BBS telephone number(s), the one of the Long Distance Services to dial
through (if any... if you don't know what these services are, you don't use
them).  You are also asked whether [Enter] must be pressed after BBS
commands.  Some BBS's have "hotkeys" and accept commands without you having
to press [Enter], and if this is the case you should answer "No" to this
question.  You're then asked for a BIF ID, which is simply the filename
Icom uses to store the information on-disk in the BIF Directory.  You have
only eight letters (a regular DOS filename) to use as the BIF ID, and
cannot use spaces, so use an abbreviation of the BBS/Host Name if
necessary.  If the BBS/Host Name was Joe's BBS you might use a BIF
ID/filename of JOESBBS.

Icom then dials the BBS and, upon connecting, watches in order to determine
which *type* of BBS it is connected to (PCBoard, Wildcat, RBBS, etc).  If
the BBS software type is recognized (i.e. if Icom has a BIF template for
it... the BIF templates are defined in the file BBSTYPES.DAT, in the \ICOM
directory and you can add new BBS types to this file later as you gain more
experience) the default prompts and commands are loaded from the BIF
template.

BIF templates that accompany Intellicomm are set up and tested using the
default prompts and commands that BBS developers provide to Sysops (at
least three different BBS's of each type are tested with Intellicomm's
template data, usually accompanied by examination of our own stock setup of
each BBS type).  So unless your Sysop has modified one or more of the BBS
prompts or commands as it is shipped from the BBS developer, the BIF will
work as is and you'll be ready for complete automation of all BBS tasks
with no further interaction save for entering your logon name/password, and
possibly picking a different Offline Mail System if the BBS isn't using the
default Mail System given in the BIF (more below).

If Icom fails to answer any of the logon questions the BBS asks you, due to
a non-standard prompt defined by the Sysop or due to the fact that Icom did
not recognize the BBS type, enter the response manually.  IMPORTANT:	Do
not "anticipate" and answer BBS prompts before they are displayed.  When
you press a key during BIF Learn, Intellicomm captures the text to the
immediate left of the cursor (i.e. the BBS prompt), for insertion in the
BIF when you finish entering the command.  Thus, if you answer a BBS prompt
before it has been fully displayed, Intellicomm will NOT capture the proper
BBS text and insert it in the BIF.  Further, Intellicomm may answer the
question on its own, so you should always wait a second or two before you
respond to any BBS prompts during BIF Learn.

Once you finish entering the response (i.e. if you press [Enter]) or once a
Carriage Return is received from the BBS (i.e. if the BBS accepted the
command without your pressing [Enter]) Icom will then present a menu asking
you which BBS prompt you just answered.  If the BBS is using English, and
has semi-standard BBS prompts, in many cases Icom will be able to guess
which prompt you just answered and will hilight it as the default on the
menu.  If you don't see the BBS prompt you answered on the menu, pick one
of the unused "Extra" slots.	If you attempt to select a certain prompt
from the menu and cannot, the prompt has already been used and the
information is already stored in the BIF at that position, and you must
select another (again, use an "Extra" prompt if this is the case).

Once you reach the BBS Main Menu, press [Alt-G] if Icom doesn't recognize
it on its own (this will be the case if the Sysop changed the format of the
BBS Main Menu, or if the BBS type was unknown).  You don't have to remember
the [Alt-G] key right now ... Icom displays a reminder on the bottom screen
line when BIF Learn mode is on.  'G' is used to signify "G"ot it.  I.e.
you're where you're supposed to be.

BIF Learn then displays a menu of other areas to learn.  You can eXit at
this point, and Icom will create a 'Logon - BIFNAME' job which you can
"Run" from the Job Directory to dial and auto-logon the BBS then switch to
Manual.  Or you can continue to automate a Message run or File Download,
etc., and the accompanying automated jobs for those tasks as well.  If the
BBS software was recognized by Intellicomm (you'll be notified if this is
the case), you should quit BIF Learn now, since the entire BIF has already
been set up for you.  You can always come back and use BIF Learn again
later if something doesn't work properly due to Sysop prompt custom-
izations.
  
Modify an existing BIF
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If the BBS changes software, or if the Sysop changed some prompts or
commands and your BIF isn't working properly ... or if you simply want to
learn a BIF area you hadn't learned previously, select "Modify an existing
BIF" from the first BIF Learn menu.  If you are offline, Icom will then
display all the BIFs and ask you to "Select" the BIF you wish to modify or
extend, and will commence dialing.

[NOTE: If the changes are simple (a minor prompt or response modification),
or if the telephone numbers change, or if the BBS has simply installed a
new Message or Bank System, you should instead just edit the BIF and input
the new data manually.  Press [Alt-D], hilight the BIF in question, then
select "Edit" from the BBS Directory bottom menu to go this route.  To
change the Message or Bank type (i.e. to import new prompts and commands
into the BIF "Message" section for a different Message or Bank system),
hilight the "Message Type" or "Bank Type" item on BIF screen 1 (2nd column,
at the top) and press [Enter].  All Message or Bank systems known to Icom
will then be displayed (note that these are the .MTF and .BTF files in the
\ICOM\BIF directory... so they won't be available if you deleted these
files), and if the type you're interested in is available, simply pick it
from the menu, answer any questions asked, and you're done.  If the type
isn't available, use BIF Learn as outlined below.]

The Logon process then continues as outlined above and if Icom misses a
question, simply answer it manually then pick the proper item from the menu
(or use an "Extra" item if none apply).

Once you reach the BBS Main Menu (again, press [Alt-G] if Icom doesn't
recognize it due to a change in the BBS menu prompt) you will be presented
with a menu of tasks to learn.  Select the option you're interested in,
then follow the bouncing ball.  Online help will switch once you've started
the next BIF Learn process, so use the [F1] key again later for new help if
you run into problems.

See also:
	ICOMAUTO Easy Setups
	BIF Overview
	BIF Learn - Message/Reply Transfers
	BIF Learn - New Files Collection
	BIF Learn - File Downloads
	BIF Learn - Time Bank Transactions
	Script Learn
ÑBBS Information Files (BIFs) hold information about a specific BBS, and
they're used by Intellicomm to carry out automated online sessions.  BIFs
can also be used simply to hold BBS telephone numbers for manual online
sessions (you can dial such BIFs from the BBS Directory using the Dialer). 
BIFs are edited and created from the BBS Directory (hotkey [Alt-D]), using
the "Create" and "Edit" options, both of which enter the BIF Editor
allowing you to modify the BIF information.	BIFs can also be created using
BIF Learn, whether Intellicomm has a "BIF template" for the BBS type or
not.  [BIF templates are simply files that hold the correct setup
information for a particular BBS type; \ICOM\BIF\PCB145.BIF is the BIF
template for PCBoard v14.5, etc.  You'll learn more about this later as you
become more familiar with Intellicomm.) 

The advantage of using BIFs is that information about the BBS is plugged in
to specific BIF slots, which gives Intellicomm a very good idea what it's
doing at the BBS (and, just as importantly, what the BBS is doing to it)...
unlike scripts which really have no idea what is actually happening. 
Instead of just mindlessly watching for anonymous BBS text and sending
responses as scripts do, using BIF information, Intellicomm actually knows
which BBS prompt it has received and this allows much better error-
handling.  How does it know?	It knows because of the way BIFs are set up. 
Specific BBS data, such as your logon name, and the BBS 'Name' prompt which
asks for your logon name, goes in a specific place in the BIF:

║ Your Logon Name  Wayne Duff 		 Name . . . . . . st Name? «	    ║
											   │ 	 │
											   └───┬───┘
When this text is received from the BBS ──────────────────────┘ Intellicomm
knows that it's received the 'Name' prompt ... and thus it sends the proper
response (at left) for that particular prompt.  [The double arrow («) is
not part of the prompt but is simply displayed by the BIF Editor to SHOW
trailing spaces defined as part of the BBS prompt.  Most BBS's do add a
space after each prompt to separate the cursor from the prompt, and it can
often help to have Icom WATCH for that space, since (a) it helps to
separate a valid prompt from miscellaneous BBS text; (b) it ensures that
the BBS is actually looking for INPUT when Icom sends the response.  Some
BBS's flush their input buffer just after displaying a prompt... so if Icom
sends the response BEFORE the space after the prompt; the response could be
lost.  By the way, while on the topic, there is also an item in the BIF
called the "Response Delay" (on BIF screen 1) that allows you to pause Icom
for a second or so before sending responses.]

But Intellicomm does not watch for only one BIF prompt at a time.  It can
and sometimes does watch for up to twenty prompts all at the same time. 
During automated logons, all the BBS prompts (and the two "Main Menu"
prompts) on the BIF "Logon" screen are watched for at the same time, as
well as the four "External Extra" prompts on the BIF Extras Screen. During
message downloads, all the message download-oriented prompts on the
BIF Message Screen are watched for at once, as well as the four "Message
Extra" prompts on the Extras screen.  Similar happens with file transfers
and actually it would be very rare for Intellicomm to NOT be looking for at
least five different BBS prompts during any automated task.  And this is
how Intellicomm is able to handle unexpected problems at the BBS ... It's
watching for all sorts of different errors/possibilities all at the same
time.

If Icom tries to access the Message Menu, and an error occurs at the BBS
and it we instead end up back at the Main Menu; Icom will know about it and
will try to access the Message Menu one more time.  If that doesn't work,
it gives up and cancels the message-oriented job, moving on to the next
automated task, and hopefully at least getting something useful done for
you.  A script would, in all likelihood, provide no such error-handling and
might at best simply hang up if it couldn't access the Message Menu (this
is what scripts created via Icom's Script Learn would do... and at least it
provides SOME error-handling).  At worst (and as is common with other
Script Learn modes) the script might just continue as if it was at the
Message Menu, sending erroneous commands to the BBS Main Menu.  Telephone
line noise can sometimes distort the commands Icom (or any script) sends,
and even bugs and improper setup in BBS software/hardware do cause slight
malfunctions in BBS operation now and then, at most every BBS.  By using a
BIF and Icom's internal automation/error-handling, Intellicomm will in many
cases be able to recover from unexpected problems at the BBS.  And while on
the subject of line noise: Intellicomm can also send a number of backspace
characters immediately before sending commands/responses to the BBS, to
erase line noise.  You configure the number of backspaces to send on BIF
screen 1 in the "BS Protection" item, but again BS Protection is only in
effect during automated jobs when Icom is at the helm.  It isn't used by
scripts.

The moral is that while Script Learn (Icom's or otherwise) is easier to use
and requires less input (it doesn't need to know which BBS prompt/command
is which, as is the case with BIFs), you pay for the slightly easier setup
by sacrificing reliability.  If you're like most people, you will
eventually carry out hundreds of sessions online at one or more BBS's.  A
few minutes more effort setting up a BIF with BIF Learn, and with some
manual tweaking, will pay itself off a hundred times over in RELIABLE
unattended communications.  With a properly defined BIF, you can TRUST
Intellicomm to get the job done properly, by itself.  With scripts, unless
you spend the kind of time we have programming Icom's error-handling
routines, even the slightest variation in BBS operation (not to mention
abruptly lost connections in the middle of mail or file transfers) will
cause script failure.  You may even find that Intellicomm is as capable of
handling errors as you are yourself, and if you're a BBS novice you may
find that Icom is MORE capable of handling errors than you are.	There are
hundreds of hours of real-world online testing behind Icom's internal
automation and error-handling routines.  You'll give that all up by taking
the easier route and using Script Learn, so use a BIF and an automated job
when you can!

See also:
	Automation in General
	Automation in Detail
	BIF Learn
	BIF Setup Tips
	Script Learn
ßYou have reached the BBS Main Menu, and your BIF should now be capable of
performing automated logons for you.  IMPORTANT: The BBS software type was
NOT RECOGNIZED when BIF Learn connected, and this means that at this point
your BIF is only capable of performing automated logons.  From this point:

  ■	Attempt to download a file called ICOMAUTO.ZIP from this BBS.  Another
	Intellicomm user (or us, or the Sysop) may already have produced a
	working BIF for this BBS and uploaded it as ICOMAUTO.ZIP.  If
	ICOMAUTO.ZIP exists (it will be in the same file area as Intellicomm
	itself) simply download the file, logoff, and sit back while
	Intellicomm completely configures itself for full automation of this
	bulletin board.  HOW TO CHECK FOR ICOMAUTO.ZIP:  After you exit this
	help screen, select eXit from the BIF Learn Main Menu; then carry out
	the usual MANUAL download procedure on the BBS.  When asked which file
	to download, enter ICOMAUTO.ZIP then simply logoff the BBS and Icom
	will begin the automatic configuration.  If ICOMAUTO.ZIP does not
	exist:

  ■	Logoff the BBS and further instructions will be displayed.	The first
	step is to ensure that automated LOGONS are working properly.  Worry
	about nothing else for the time being.
üYou have reached the BBS Main Menu, and your BIF should now be capable of
performing automated logons for you.  IMPORTANT: The BBS software type WAS
RECOGNIZED when BIF Learn connected, and this means that every BIF item has
been set up for you, according to the type of BBS software in use at the
BBS.  Unless your Sysop has customized one or more BBS prompts (the 'Enter
filename' prompt for downloading for example, or any of the other prompts
defined in the BIF) the BIF will now work without modification.

HOWEVER, since Sysop's often customize their BBS's (and often inadvertently
modify critical prompts needed for automation in the process), your BIF may
not be capable of automating all tasks on this BBS as yet.	This is NOT
Intellicomm's fault, and there is nothing that we can do about it: if your
Sysop is not aware of products like Intellicomm, s/he may have modified
crucial BBS prompts that Intellicomm (and other automation systems, and
scripts) watch for to automate BBS tasks.  However, there is a guaranteed
way to ensure proper BIF setup:

  ■	Attempt to download a file called ICOMAUTO.ZIP from this BBS.  Another
	Intellicomm user (or us, or the Sysop) may already have produced a
	working BIF for this BBS and uploaded it as ICOMAUTO.ZIP.  If
	ICOMAUTO.ZIP exists (it will be in the same file area as Intellicomm
	itself) simply download the file, logoff, and sit back while
	Intellicomm completely configures itself for full automation of this
	bulletin board.  HOW TO CHECK FOR ICOMAUTO.ZIP:  After you exit this
	help screen, select eXit from the BIF Learn Main Menu; then carry out
	the usual MANUAL download procedure on the BBS.  When asked which file
	to download, enter ICOMAUTO.ZIP then simply logoff the BBS and Icom
	will begin the automatic configuration.  If ICOMAUTO.ZIP does not
	exist:

  ■	Logoff the BBS and further instructions will be displayed.	NOTE: 
	Since the BBS type was recognized you COULD DO MORE HARM THAN GOOD by
	trying to learn another area at this point.	You can always modify
	your BIF later by turning on BIF Learn and selecting "Modify an
	existing BIF" instead of doing what you did this time: "Create a new
	BIF".
NOTE: If you activate BIF Learn while online, it is assumed that you wish
to modify the current BIF, and it is also assumed that you are at the BBS
*Main Menu*.  The BBS Main Menu is the starting point for all BIF Learn
tasks.  If you are NOT at the BBS Main Menu, select eXit, correct the
problem, then re-start BIF Learn by pressing [Alt-Q].

If you activated BIF Learn and ended up at this menu but you are NOT
online, please see Common Questions & Answers.  This is a modem setup
problem (your modem is forcing the carrier detect signal on) and it can be
fixed easily.

Message/Reply Transfers
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
See BIF Learn - Message/Reply Transfers.

New Files Collection
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
See BIF Learn - New Files Collection.

File Downloads
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
See BIF Learn - File Downloads.

Time Bank Transactions
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
See BIF Learn - Time Bank Transactions.

eXit
▀▀▀▀
Deactivates BIF Learn and leaves you online in manual terminal mode.

See also:
	BIF Learn
	BIF Overview
&BIF Learn can also help you to automate your message and/or reply
transfers.  Message runs can be anything from a simple capture of the text
messages online, to Qmail/Tomcat type .QWK transfers, to MegaMail and
PCRelay type transfers, to most everything in between.  If you're new to
BBS's and are not familiar with BBS messaging, you can learn all the tricks
of the trade by reading BBSTUTOR.DOC, the BBS tutorial included with
Intellicomm.

PREPARATION
▀▀▀▀▀▀▀▀▀▀▀
If you have never performed a message transfer on the BBS, you're getting
ahead of yourself in attempting to automate mail runs at this point.	You
should have performed at least one or two manual mail runs by this point,
and having a printout of a manual mail run also won't hurt for later use in
the BIF Editor when putting the finishing touches on your BIF.  Remember,
the BIF is set up ONCE, and if done properly you'll be able to enjoy your
efforts for possibly hundreds of effortless unattended sessions: you don't
want to rush through the BIF setup and do a shabby job of it.

If the mail system is an Offline Mail system such as Qmail, Tomcat,
Megamail, etc., you should also know the PACKET ID that the BBS uses for
its mail packets (if the packet filenames are THEBBS.REP for replies, and
THEBBS.QWK for messages, the PACKET ID is "THEBBS").

If you intend to teach Icom how to upload message REPLIES, you should have
a reply packet handy before activating BIF Learn - Message/Reply Transfers. 
The mail system must accept all replies via upload of a single file (Qmail-
style .REP uploads, MegaMail-style .UL uploads, etc).	There are "offline
mail systems" and Mail Readers to handle this for every major BBS type,
they'll cost your Sysop only about $25-$50 and an evening of setup, and
they make handling messages/replies MUCH more enjoyable for you. 
Intellicomm cannot automate your REPLY uploads without such a system.  See
BBSTUTOR.DOC if you're confused as to what offline mail systems do for you.

NO FRILLS SETUP
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Intellicomm comes supplied with many different Message Template Files
(*.MTF, in the \ICOM\BIF directory) and often all you'll have to do to set
up for mail runs is to pick the proper mail system, answer a couple of
questions... and you're done.  All the BBS prompts and commands necessary
to automate the mail run have been pre-configured into the .MTF templates
can be imported easily into any BIF.  You can do this either via BIF Learn
(see below), or the more direct way: Enter the BBS Directory with [Alt-D],
hilight the BIF of interest and select "Edit".  Once in the BIF Editor,
hilight the "Message Type" item at the top of column 2 on the 1st screen
and select "Edit".	If you see the mail system of interest, hilight it and
press [Enter], then answer any questions.  eXit the BIF Editor, then switch
to the Job Directory ([Alt-R]) and "Create" an automated job:

	Call Joe's BBS
	  Send message replies  (task #3)
	  Get all new mail	    (task #4)

eXit the Job Editor, call your job "Send/Get Mail - Joe's BBS" or the like,
and "Run" it, forever more, to transfer the mail effortlessly.

USING BIF LEARN
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
First, logon the BBS by running your automated "Logon - BIFNAME" job
created earlier with BIF Learn, or via the "Dial" command from the
BBS Directory.  Once you reach the BBS Main Menu, activate BIF Learn by
pressing [Alt-Q] and selecting "BIF Learn".	Since you're already online
and at the BBS Main Menu, you'll then go straight to the BIF Learn Online
Menu without having to go through the usual preliminary questions.  Select
"Message/Reply Transfers" from the online learn menu.

Select a Mail System
────────────────────
BIF Learn first displays a menu showing all the .MTF files (the message
template files discussed above).  If you see the proper message type,
hilight/select it, answer any questions (see online help again when being
asked the question if you need more info) and you'll be set up for
automated mail runs immediately and will be returned to the BIF Learn
Online Menu.  If you don't see the proper message type, press [Esc] and
proceed below.

Access the Message Menu
───────────────────────
The first thing you'll have to teach Intellicomm is how to access the
Message Menu (or DOOR, if a mail door).  If there is no message menu on the
BBS (if you can send/get your mail right from the main menu with a single
command) just press [Alt-G] without entering any commands to the BBS.  [A
reminder to this effect is displayed on the status line during learn, you
needn't memorize the [Alt-G] key now.]	If there is a message menu, enter
the command necessary to access it ('OPEN QMAIL', or perhaps just 'M' if
accessing a Message sub-menu), then ALSO answer any other prompts that
happen to come up between the BBS Main Menu and the Message Menu (a 'pause'
or 'more' prompt, for example).  Once at the Message Menu, press [Alt-G].

Sending Replies
───────────────
1.	A menu will then be displayed asking if you have a reply packet ready
	for upload.  Select "Yes" if you do, or select "No" if you don't wish
	to automate reply uploads (or if the mail system doesn't support reply
	uploads).  You may also select "Oops!" if you forgot to create a reply
	packet and need to shell out to your Mail Reader to create one.
2.	Enter the command to tell the mail system you're ready to upload your
	replies.	If the mail system is already expecting your replies with no
	command, skip the next step.
3.	Handle any prompts that come up between the "begin upload" prompt and
	step 1 (i.e. an 'enter protocol' prompt, etc).  If you enter any extra
	commands Icom will ask you which BBS prompt you answered.  If you
	don't see a prompt that applies, just use one of the Message Extra
	prompts.
4.	Wait for the mail system to tell you to begin your reply packet
	upload, then press [PgUp], select the proper protocol (normally
	Zmodem), then enter the path *and* filename of your reply packet. 
	E.g. C:\REPLIES\THEBBS.REP.

Get New Mail
────────────
Note: If you simply wish to capture mail to a text file for later reading,
follow the steps below but use the *ASCII* protocol in step 3.  The ASCII
protocol simply captures BBS text to a specific filename.

1.	Enter the BBS Message Menu command that tells the mail system: "get
	all new mail, in non-stop mode", then download your mail (or skip to
	step 3 if the mail system immediately begins sending your new mail). 
	In most message systems you simply enter the command "D" for
	[D]ownload Mail, though in the older mail systems the command might be
	more involved.  If you cannot tell the system to display all mail in
	non-stop mode, wait for the "more" prompt to come up, answer it
	(selecting "Non-Stop" there if possible), then tell Icom you answered
	the More prompt when it displays the menu of prompts.
2.	Handle any intermediate BBS prompts manually if necessary (an "Enter
	protocol" prompt perhaps).  Many mail systems will show you what mail
	was collected and then ask you whether you want to download it or not:
	that is called the "Confirm Download" prompt by Intellicomm (you'll
	see this prompt listed on the menu Icom displays after you answer it).
3.	When the mail system tells you to start your download, Intellicomm
	will start receiving the file automatically if the Zmodem protocol is
	used for the download.  If the download doesn't start automatically
	(or when you're ready to begin capturing using the ASCII protocol),
	press [PgDn] then enter the path *and* filename of the packet if asked
	(only Xmodem and the ASCII protocol will require a filename). 
	Example: C:\MESSAGES\BBSMSG.TXT, or C:\MESSAGES\BBSMSG.QWK, etc.  Note
	that if you use External Protocols for message downloads, such as DSZ
	or HS/Link, etc., Intellicomm will ask you the name of the transferred
	file after the transfer.  Only when using the internal protocols can
	Intellicomm obtain the name of the transferred file.

Leave the Message Menu
──────────────────────
Since Intellicomm allows you to perform both mail and file transfers (and
other tasks) during the same online session, you must now also teach it how
to LEAVE the Message Menu, if you accessed a Message sub-menu/DOOR earlier. 
Follow the usual steps, answering any intermediate prompts that come up on
the way out of the message menu, and Icom will re-display the BIF Learn
Online Menu when you return to the BBS Main Menu (you may have to press
[Alt-G] if Icom captured some "variable" text in the BBS Main Menu prompt. 
You'll learn more about this later).

NOTE: Once offline you may also enter a BIF Response to "Logoff Msg. Menu"
on the BIF "Message" settings screen.  If this response is entered in the
BIF, *and* if there are no other automated jobs to carry out, Intellicomm
will then logoff right from the Message Menu, instead of returning to the
BBS's main menu and logging off from there.

Once the mail download/capture is complete, you will then return to the BIF
Learn Online Menu, and can either eXit to deactivate BIF Learn, or can
continue learning other areas.  At this point, if Intellicomm doesn't yet
have a BIF "Logoff" command (entered on the BIF "Logon/Global" settings
screen), it will ask you for the proper command.	Normally the command is
"G" for [G]oodbye, but if the BBS Main Menu uses a different command,
replace the G with the proper command.

Testing your Job
────────────────
Once offline, Intellicomm will display the BIF again for you to peruse and
modify.  After giving the BIF prompts a once over in the BIF Editor, you
can test an automated mail run out by switching to the Job Directory with
[Alt-R], then hilighting the "Send/Get Mail - BIFNAME" job (where BIFNAME
is the BIF ID of the BBS) and selecting "Run".
dThe BIF Learn/New Files Collection option helps you to set up for automated
collection of BBS new files lists, and File Tagger imports of these lists. 
After new files lists are collected you browse the files, Tag any you wish
to download, then you Run your automated job to pick up the Tagged files. 
If you're unfamiliar with this process, please see
Automated Downloads and New Files Imports for a quick outline.

NOTE: If Intellicomm tells you that it recognized the BBS software when it
connected, you should NOT use this BIF Learn feature unless you tested your
automated job and ran into problems.  When BIF Learn recognizes the BBS
software, it automatically fills in everything it has to know to capture
and import BBS new files listings, and you could do more harm than good
(i.e. lose the valid settings and have to start over) by activating BIF
Learn/New Files Collection.

It will be helpful for you to know exactly 'what' Intellicomm is planning
to learn in this phase of the learn mode.  There are four things necessary
for new files list collection/imports to the File Tagger, and four things
Intellicomm will attempt to learn:

1.	The BBS command needed to access the "File Menu", if necessary for BBS
	file functions (you may have to press [F] at the BBS Main Menu to
	access a sub-menu of file functions).  If you can get the new files
	right from the BBS Main Menu, no command is needed here and you'll
	simply press [Alt-G] at the BBS Main Menu.
2.	The BBS command to display all the new files (see the BBS online help
	if you don't know the proper command).	If possible, this command
	should display new files in 'non-stop' mode, meaning that no BBS
	"More" or "Pause" prompts are displayed after each screen.	On many
	BBS's, if you append "NS" (for Non-Stop) to the usual new files
	command, the list is displayed in non-stop mode.
3.	The POSITIONS of various items on the BBS file list (filename, date,
	size, and description positions) must be known in order for the File
	Tagger to properly import the new files list for browsing/Tagging of
	files to download.	See New Files Imports for details and
	troubleshooting tips.
4.	The BBS command needed to leave the File Menu and return to the BBS
	Main menu (if a file sub-menu was accessed).

After step 2, during an automated job, Intellicomm opens a capture file
called \ICOM\LST\BIFID.NEW where BIFID is the BIF ID/filename of the BIF in
use.  When the automated job completes and you are offline, Icom then looks
on-disk for \ICOM\LST\*.NEW, and if any lists are found it automatically
'imports' (adds) any files on the list to the Tagger NEWFILES catalog
(performing the usual duplicate checking, scanning for Exclude or Replace
keywords, etc., as defined in the Intellicomm Setup on the "File Tagger"
screen).	Normally the Tagger "View Date" is then updated to today's date
so that you ONLY see today's new files when you enter the Tagger (you can
change the View Date via the Tagger's "Tools" menu to see all the files, if
necessary).  Please see File Tagger Introduction for more details.

However, in order to import new files properly, as mentioned above in step
3 the Tagger must know the POSITIONS of various items on the BBS new files
list.  These items are defined on the BIF "Bank/List" screen (/List meaning
New Files 'List'):

╟─┤ BBS File List Details ├─────────┤ BBS File List Details ├─────────────╢
║ Catalog to Use .				 Year Position  . 30			    ║
║ D/L Priority   > 0			 Date separator . - 			    ║
║ Default Lst Area 0			 Comment Start  . 34			    ║
║ Filename Start . 1			 Comment End  . . 80			    ║
║ Extension Start  0			 Continue Comment |«			    ║
║ Size Position  . 14			 Continue Comment  «			    ║
║ Month Position . 24			 New File Area  .				    ║
║ Day Position . . 27										    ║

BIF Learn will attempt to fill in most of these items in for you by looking
at the format of the BBS file list.  Don't count on BIF Learn to get it
100% correct every time though...	BBS file lists vary widely, and this
portion of BIF Learn is designed mainly to give you a STARTING POINT with
this BIF section.  In some cases you'll have to adjust some of the
positions after BIF Learn finishes.  The ideal way to do this is to capture
a BBS file list manually, then to select "Review Session Captures" from the
Icom Main Menu.  Hilight and "View" ICOM.CAP, then press [Alt-R] to turn
the RULER on.	Then write down the positions of the various items and plug
them into your BIF.

Further, if the BBS displays extended file descriptions:

FILENAME.EXT  12345678  MM-DD-YY  Description line 1.
						  | Description line 2.

(Or using some other character, or perhaps just spaces before extended
comment lines.)  Then you'll want to include a 'Continue Comment' character
such as the '|' above.  All of these items are detailed fully in the
BIF Bank/List Screen link, which is available by pressing [F1] while in the
BIF Editor after BIF Learn finishes.
4BIF Learn/File Downloads is designed to give you a STARTING POINT in
setting a BIF up for file downloads on an unrecognized BBS type.  It does
not and cannot get all the necessary information on an unrecognized BBS
type (particularly the "File not found", "Insufficient Time", "No Bytes",
and "Transfer Aborted" prompts).  It should be a fairly simple matter for
you to get these prompts and plug them into the BIF manually, keeping in
mind that BIF setup is done ONCE and only once, and you then get to sit
back and enjoy your efforts for possibly thousands of reliable unattended
downloads.

The Learn process is simple.	Select "File Downloads" from the BIF Learn
Online Menu, then:

1.	Access the BBS File Menu (if any).
2.	Press [Alt-G] when at the BBS File Menu (or at the BBS Main Menu if no
	File Menu is used).
3.	Enter the BBS "download a file" command.  Normally the command is "D"
	for [D]ownload.
4.	Enter the name of a file to transfer, and carry out a file download as
	usual, telling Intellicomm which prompt was which when you answer BBS
	prompts.	When the BBS tells you to begin your transfer, press [PgDn]
	(if Icom doesn't start the transfer automatically) and select the
	proper transfer protocol.  If the BBS supports "batch" transfers
	(entering of multiple filenames before the download), simply press
	[Enter] when asked for the SECOND filename to download.  When Icom
	asks you which BBS prompt you answered pick "eXit [ignore]" from the
	menu.  When in the BIF Editor after Learn you'll then have to tell
	Intellicomm how many files it should transfer per batch (on the BIF
	"File" screen):
	║ Files per D/L  . 10		    No Bytes . . . .			    ║
	  ───────────────────
	This item defaults to *1* file per D/L if the BBS type is not known to
	Intellicomm, so remember to adjust it if you want to transfer larger
	batches.	You can save quite a bit of online time (and/or reduce your
	long distance charges) by taking advantage of automated batch
	transfers.
5.	When the transfer completes, enter the command to exit the BBS File
	Menu back to the BBS Main Menu (if necessary).  If BIF Learn captured
	some "variable" text in either the BBS Main Menu or File Menu, you may
	have to press [Alt-G] when you return to the menu.

If you haven't already entered a BBS "Logoff" command in the BIF, you will
also be asked for this after the Main Menu is reached.  The "Logoff"
command is the BBS MAIN MENU command needed to disconnect from the BBS
(normally the command is "G" for [G]oodbye).  Note that if a BBS File sub-
menu is used, AND if you can logoff right from the sub-menu/door, you can
later manually enter a "Logoff File Menu" command in the BIF.  If Icom has
nothing left to do on the BBS after the file downloads, AND if a Logoff
File Menu command is defined on the BIF "File" screen, Icom will logoff
from the BBS File Menu instead of returning to the Main Menu (this is only
relevant IF the BBS uses a file sub-menu.  If it doesn't, you don't need a
Logoff File Menu command).

IMPORTANT
▀▀▀▀▀▀▀▀▀
As mentioned above there are several BBS prompts that BIF Learn does not
capture:	Namely the "File not found" (attempt to download a file that no
longer exists on the BBS, in which case Icom will NOT attempt to download
the file again), "No time" (not enough time left to transfer the file...
Icom saves it for next time), "No bytes" (same as No time but not enough
'download bytes'), and "Transfer abort" (the transfer was aborted; not all
files were transferred).  It would be difficult and error-prone for BIF
Learn to attempt to get these BBS prompts, and thus it's up to you to get
them and plug them into the BIF manually at some later time (before you
attempt to carry out automated downloads).  All of these BIF items are
detailed fully in the BIF File Screen link, which is available by pressing
[F1] while in the BIF Editor after BIF Learn finishes.
!If the BBS has a Time Bank available, BIF Learn can also help you to set up
for automated bank transactions.  Why would you want to automate Time Bank
transactions?	The normal use is to get time (and/or Download Bytes, if the
bank supports it) out of the bank just prior to automated file downloads. 
It can also be handy to have Intellicomm deposit some fixed amount of time
AFTER your automated jobs, to keep your account topped up for future use.

Preparation
▀▀▀▀▀▀▀▀▀▀▀
Before starting BIF Learn/Time Bank Transactions, you should logon the BBS
and do two things: (1) familiarize yourself with the command needed to
access the Time Bank (find the door menu, and the proper door name/number
for the Time Bank); (2) find out what TYPE of Time Bank it is.  I.e. the
bank might be called "Spiffy Bank" or the like and Icom might already know
how to handle that bank type.

The BIF Learn process:

1.	After starting BIF Learn/Time Bank Transactions (make sure you're at
	the BBS MAIN MENU when you do so) Icom will present a menu of Time
	Bank systems which it knows how to handle.  Look the menu over, and if
	you see the proper bank type hilight it and press [Enter] (or click on
	it with your mouse).  You'll most likely be asked for the "Access Bnk
	Menu" command, where you'll enter OPEN 5 or whatever command is needed
	to access the Bank Menu from the BBS Main Menu.  [Please see the NOTE
	in step 2 if multiple commands are needed.]	If you DON'T see the
	proper bank type, press [Esc] (or click the right mouse button) and
	continue to step 2.

2.	Enter the command necessary to access the BBS Time Bank.  On most
	BBS's the Time Bank is implemented as a DOOR, so check the BBS DOOR
	menu and online help prior to starting BIF Learn to get the proper
	command.	If the "access door" command was OPEN, and the Time Bank
	door was door #5, you might enter OPEN 5 (or OPEN;5) from the BBS Main
	Menu.

3.	Enter the Time Bank command to "Deposit Time", handle any intermediate
	prompts that come up (More, Pause), then enter some dummy amount of
	time to deposit (5 minutes or the like), then pick "Deposit TIME" from
	the prompt menu when asked which prompt you answered.

4.	Enter the Time Bank command to "Deposit DOWNLOAD BYTES" if the bank
	supports it.  If the bank doesn't support depositing of download
	bytes, just press [Alt-G].

5.	Do the same for withdrawal of time/bytes.

6.	Enter the command to quit the bank door and return to the BBS Main
	Menu.  Note that if the Time Bank also supports a 'logoff' command,
	you'll want to manually enter that command in the BIF (Bank/List
	screen) when BIF Learn finishes.  This way Intellicomm will simply
	logoff from the Time Bank door IF there is nothing left to do on the
	BBS, rather than quitting back to the BBS Main Menu (which wastes
	time) then logging off from there.

Note that when automated JOBS are created by BIF Learn (Send/Get Mail,
Send/Get files, etc), it does NOT add time bank transactions to the jobs
automatically.  BIF Learn has no way of knowing WHEN, WHERE or HOW you want
to handle these transactions, so you must add them to your jobs manually
when BIF Learn finishes.  To do so, enter the Job Directory with [Alt-R],
hilight the proper job (Send/Get Files - BIFNAME, etc) and select "Edit". 
Once in the Job Editor, enter task #2 for a withdrawal, and task #8 for a
deposit.	The finished job should look something like this:

	Call The BBS
	  Withdraw 60 min. 1000000 bytes
	  Upload tagged files
	  Download tagged files
	  Deposit 30 min. 1000000 bytes

Note that you needn't enter NUMBERS as the amount of time/bytes to withdraw
or deposit.  If the Time Bank supports something else (e.g. 'A' to deposit
'A'll Time or 'A'll Bytes) you might want to enter the letter A as the
amount to deposit/withdraw.

If you can't get this working via a BIF and Icom's automated jobs, you
should consider using Script Learn and Custom Command/Run script tasks (to
execute the learned scripts) in your job.  Scripts can automate anything...
and unfortunately some Time Banks are designed poorly and require too much
input for Icom's BIFs to handle.
ÅWhen BIF Learn finishes creating a BIF (or portion thereof) it auto-
matically displays it for your perusal when you logoff the BBS.	

It does this (a) to familiarize you with BIFs so you can see what response
got plugged in where, and can also get familiar with the many useful
settings that BIF Learn never touches; (b) to let you give the BBS prompts
the once over (the BBS prompts are on the BIF "Logon", "Message", "File",
"Bank/List" and/or "Extras" screens in the RIGHT-HAND column) to see if any
varying text was captured by Intellicomm (see below), and; (c) to add BBS
prompts that BIF Learn cannot capture, such as "File not found", "More mail
found", "No time left", etc.	It's up to you to get such prompts from the
BBS manually and plug them in to the BIF, if you used BIF Learn to create a
BIF from scratch on a BBS type unknown to Intellicomm (in most cases Icom
will have loaded a BIF template, and will have filled in all of the prompts
for you).

The BBS prompts that BIF Learn captures while online, sometimes contain
varying text such as the current time of day, or the current BBS conference
number, or the time remaining online, or the total time online, etc.	Such
varying text should not remain in the BIF.  Example:

║ Startup Command				 Main Menu A  . . [10:05am] Command? « ║
										   ───────────────────
This BBS displays the current time of day in its Main Menu prompt, and Icom
captured and stored this text.  Unless it was exactly 10:05am every time
Icom was at the BBS Main Menu... the menu would NOT be recognized.

The solution is to edit out the varying text by hilighting such prompts and
selecting "Edit" (then press the [Del] key to get rid of variable text)
once in the BIF Editor:

║ Startup Command				 Main Menu A  . . ] Command? «	    ║

The above BIF prompt would now work fine no matter what time of day it was.

USE PGUP/PGDN
▀▀▀▀▀▀▀▀▀▀▀▀▀
Once in the BIF Editor you can easily page through the various BIF screens
by pressing [PgDn] (move to the next screen) or [PgUp] (move to the
previous screen).  Make sure you don't forget to check the prompts (if any)
on the "Extras" screen, and also don't forget to use [F1] help key if you
need more help once in the BIF Editor.

SAVE YOUR WORK!
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Once you give the BIF a once over, select eXit to exit the BIF Editor (or
press the [Esc] key or right mouse button), then press [Enter] to SAVE any
changes you made.  The BIF should then be ready for action.  But don't get
ahead of yourself... Try to concentrate on one thing at a time rather than
attempting to get the whole BIF working in a single session.  Get the auto-
logon working first (test this by switching to the Job Directory,
hilighting the "Logon - BIFNAME" job [where BIFNAME is the name of the BIF
you just learned], and selecting "Run").  Note that you can also auto-logon
a BBS for a manual online session by using the "Dial" option of the BBS
Directory.  If a password is defined in the BIF, Icom will auto-logon right
to the BBS Main Menu when it connects after a "Dial".

Learning New BIF Areas
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
To learn a new BIF area/screen (i.e. for automated message or file
transfers) AFTER you have the auto-logon tested and working, start BIF
Learn again (press [Alt-Q] and select "BIF Learn") but instead of selecting
"Create a new BIF", select "Modify an existing BIF".  This bypasses the
questions prompting you for the BBS name, telephone numbers, etc., and
allows you to select an existing BIF.  Alternatively you can activate BIF
Learn while already online in manual mode.  If you activate BIF Learn while
online, Icom goes right to the BIF Learn Online Menu, and assumes you wish
to modify or add to the BIF currently in use.
ΦNo BIFs were found in this ICOMAUTO.ZIP.  This is probably due to an error
uncompressing the ICOMAUTO.ZIP file, and you should be able to remedy the
situation by entering the "Intellicomm Setup" from the Icom Main Menu, and
entering the proper command(s) for your usual ZIP decompression program on
the "Filename and Paths" screen:

║ Main Unpack> PKUNZIP.EXE							    ║
║ 2nd  Unpack> PKUNPAK.EXE							    ║

If PKUNZIP.EXE is *not* on your DOS PATH, you'll have to precede the
command in the item listed above with the proper path (e.g.
C:\UTILS\PKUNZIP.EXE).  If you're short of memory you can make Icom swap
itself out of base memory before running external programs by preceding the
command with SW: (for SWap ... NS: is NoSwap).  Example: SW:PKUNZIP.EXE

Of course, if you don't have PKUNZIP.EXE installed that also could be the
problem and if this is the case you should call the BBS back and
download/install it (the filename is normally PKZ*.EXE, where * is either a
date or the version number of PKZIP/UNZIP).

Another possibility is that whoever uploaded ICOMAUTO.* (it needn't be a
.ZIP file) used a compression program other than PKZIP.EXE.  If this is the
case you can either place the proper decompression command in the "2nd
Unpack" item listed above (e.g. LHA.EXE x, ARJ.EXE e, etc), or you can
simply decompress the ICOMAUTO file manually and copy the extracted .BIFs
to the BIF Directory (COPY *.BIF \ICOM\BIF).  Icom will notice the new
files when it starts up and will take it from there.
▌Input Text (General)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Enter the required response by typing it in, or by editing the default
value if a default was given.  If you press a non-editing key (listed
below) first, the default is automatically cleared.

Editing Keys
▀▀▀▀▀▀▀▀▀▀▀▀

[Ins]		toggles insert/typeover mode on or off.  In insert mode the
			cursor is large (half the size of the character) and
			characters entered are inserted at the cursor position
			pushing characters from the cursor to the end of the input
			field over one position.  In typeover mode the cursor is an
			underscore and characters entered overwrite the existing
			character at the cursor position.
[Del]		deletes the character at the cursor position, pulling to the
			cursor any characters to the right.
[Backspace]	deletes the character to the left of the cursor, then moves
			the cursor left one position, pulling characters from the
			cursor to the end of the field along.
[Ctrl-End]	deletes all characters from the cursor position to the end
			of the input field.
[Home]		moves the cursor to the first character in the input field.
[End]		moves the cursor to the position after the last character in
			the input field (to add to the end).
[Left]		moves the cursor left one position.
[Right]		moves the cursor right one position, if possible.  Use
			[Space] to move past the last character.
[Ctrl-Left]	moves the cursor to the beginning of the next word.
[Ctrl-Right]	moves the cursor to the beginning of the previous word.
òThe following is a list of topics containing tips and troubleshooting
information relevant to automated jobs, modems, dialing, Intellicomm setup,
system setup.

	Common Questions & Answers	Commonly asked questions.
	Setup Problems 			Common setup problems.
	Debugging Log				Very useful in debugging jobs and BIFs.
	─────────────────────────────────────────────────────────────────────
	Automation in General		How does Icom automate?
	Automation in Detail		Detailed explanation of automated runs.
	─────────────────────────────────────────────────────────────────────
	ICOMAUTO Easy Setups		Easiest way to set up for automation.
	Learn Modes				The second-easiest way to set up for
							automation.
	─────────────────────────────────────────────────────────────────────
	Job Editor				Details on a SPECIFIC automated task.
	BIF Overview				What's a BIF and how do they work?
	BIF Setup Tips 			What to watch for when setting up BIFs.
	─────────────────────────────────────────────────────────────────────
	Optimizing Intellicomm		Set Icom up properly; it works better.
	Multitasking Intellicomm 	Help with DESQview, OS/2, and Windows.
╬Intellicomm maintains an extensive disk log of activities that take place
throughout the course of a session, in the file \ICOM\CAP\ICOM.DBG. 

You can view this log by selecting "Review Session Captures" from the
Main Menu, hilighting ICOM.DBG and selecting "View".  You can also change
several settings regarding the log (to shut it off, or expand logging
information if you need more logging information) via the main setup
Debugging Log Settings screen.

By default, ICOM.DBG is 'renumbered' every time you start ICOM.EXE, meaning
that the existing ICOM.DBG file is renamed to ICOM01.DBG, ICOM01.DBG is
renamed to ICOM02.DBG, up to a total of five backup logs, which prevents
the file from growing to an unwieldy size (as long as you exit Intellicomm
periodically, which is a good idea in any case since it resets the entire
program, and may avoid unknown bugs that only occur after extended periods
of use).	It's mandatory that you keep the relevant ICOM.DBG file handy if
you run into a problem and require technical support, and you may be asked
to upload it or post it in a message so that we may view it.

If it's not practical for you to exit Intellicomm periodically, you can
maintain the log automatically by creating PREJOB.BAT (a regular DOS batch
file, which can be created with Icom's Text Editor) in the \ICOM directory,
and including the following lines in the file:

Echo off
if exist \icom\cap\icom01.dbg del \icom\cap\icom01.dbg
if exist \icom\cap\icom.dbg ren \icom\cap\icom.dbg icom01.dbg

The PREJOB.BAT file is executed prior to each automated run, and the above
batch file commands would first delete ICOM01.DBG if it existed, then
rename ICOM.DBG to ICOM01.DBG, leaving you with a fresh log for each
automated run whether you exit Intellicomm periodically or not.

ICOM.DBG was implemented mainly to aid in TECHNICAL SUPPORT, and it keeps
track of all the status/error messages Icom displays (the exact wording of
a status/error message can be very important when reporting problems), as
well as:

■ Operating System type detected, startup directory, ICOM.EXE 'home'
directory, and command line options you used to start the program (if any),
and how Intellicomm separated the command line options up.

■ The modem initialization string Intellicomm used to initialize your
modem.

■ Information about automated jobs, showing the exact structure of any jobs
you ran (how Tagged jobs were merged together to form a single job), as
well as information about particular job tasks that may have been auto-
cancelled (such as an "Upload message replies" task that was cancelled
because the reply packet was not found).  It also shows the "task status"
of each automated task, as each task either completes or is re-tried.  When
the "task status" of a job task is set to 0, it means the task has been
removed from the job queue (all jobs start with a task status of 3, which
in some cases allows the task to be re-tried up to 3 times if it fails),
either due to an error, or due to successful completion of the task.

■ Information about Tagger New Files Imports, particularly which files were
excluded (not imported from the new files list into your catalog) and for
what REASON the file was excluded.  Files can be excluded because the same
filename exists in DOWNLOAD.NDX (names of files you've downloaded already),
or because the same filename already exists in the catalog and the BBS the
Tagger is importing for has a lower "download priority" than the existing
file in your catalog, or because of an "Exclude Keyword" you defined on the
Tagger Keywords main setup screen.

■ Information about file transfers and transfer errors.

■ Information about DOS commands (including the errorlevel returned by the
called program which is displayed in square brackets [n]), and whether
Intellicomm 'swapped out' of memory to execute the command.

■ The names of scripts Intellicomm executed.

───────────────────────────────────────────────────────────────────────────
If the "Debugging Level" on the main setup Debugging Log Settings screen is
set to EXTENSIVE, the log also keeps track of the following information
which may be very useful in locating problems such as BIF setup problems. 
Setting the debugging log to Extensive mode, then carrying out an automated
job and viewing the log afterwards, is probably the best documentation you
could ever read regarding Intellicomm BIFs and automated jobs. 
Documentation can only explain things in general terms: the debugging log,
in Extensive mode, documents your job exactly ... according to how you have
set up Intellicomm and your BIFs.	Extensive mode adds the following
information to the log:
───────────────────────────────────────────────────────────────────────────

■ The BIF prompts Intellicomm was watching for during an automated online
task.  You can learn much about Intellicomm's automated routines and BIFs
by setting the Debugging Level to EXTENSIVE and viewing the ICOM.DBG file
once the job completes.	If Intellicomm does anything unexpected during an
automated job, EXTENSIVE level is likely to show you the reason.

NOTE: If the "Case-sensitive" BIF item (1st BIF screen in the right column)
is set to NO, Intellicomm does not concern itself with the
UPPERCASE/lowercase status of BIF prompts or BBS text: and BBS text and BIF
prompts are converted to lowercase.  When this is the case, all the prompts
and BBS text displayed in the debugging log will be in lowercase.  If you
set "Case-sensitive" to YES then Intellicomm does not convert to lowercase
and BIF prompts must match the BBS text exactly.	This can be useful at
times as if, for example, the BIF password prompt was defined as
"Password", Intellicomm would not match occurrences of "password" or
"PASSWORD" from the BBS.

■ The prompt 'hits' (matches) Intellicomm found in the BBS text.  Sometimes
miscellaneous BBS text will cause an unexpected BIF prompt match: EXTENSIVE
level will show these erroneous prompt matches to you, allowing you to
correct the situation quickly.

■ Every menu title displayed and every menu selection you made; mainly for
technical support, to track down hard-to-find problems which may require a
specific series of events to occur.

Much of the information in ICOM.DBG will be very useful to you in
diagnosing problems with Intellicomm, though some of it will only be of use
in technical support.  If you report a problem, posting the ICOM.DBG log
along with your question/problem may permit a much faster response: the
debugging log (and Capture log as well) are the "pictures" that are worth a
thousand words.
éGeneral Help with Automation
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
■ To permanently abort an automated job and return to manual mode, press
[Alt-Q] and select "Abort Job/Script, switch to manual" from the menu. 
This aborts all automated jobs, as well as any scripts which the job (or
BIF) might have called.	[Note that ALT-Q only behaves this way when a job
or script is actually running.  If you are in manual mode, ALT-Q pops up
the Learn Modes menu.]

■ To abort just a script without aborting the automated job itself (i.e. if
a script was called via a job Custom Command/Run script task or
BIF Response) press [Alt-Q] and select "Abort Script Only".  The script
will abort, but the rest of the automated job will continue.

■ To TEMPORARILY switch to manual without aborting the executing job, press
[Alt-G] (Goto Manual) and select either "Now" or "Page me just before
logoff".	Once you've finished your work in manual mode, either press [Alt-
G] again to return to automatic mode, or log off the BBS, and Icom will
return to automatic mode to complete the remainder of the job.  If you
return to automatic mode without disconnecting (by pressing [Alt-G] again)
MAKE SURE YOU RETURN TO A RECOGNIZABLE BBS MENU BEFORE YOU DO SO. 
"Recognizable" meaning a BBS menu that is defined in the BIF; either the
Main Menu (BIF Logon screen), Message Menu (BIF Message screen), File Menu
(BIF File Screen) or Bank Menu (Bank/List screen).  Ideally you should
return to the BBS menu area Icom was at when you switched to manual.	I.e.
if you switch to manual during a mail download, return to the BBS Message
menu before returning to automatic.

NOTE: If when you forget any of the above, simply use the [Alt-Z] menu from
terminal mode.  [Alt-Z] can be your panic button.  [Alt-Q] / Abort Job or
Script is the first item on the [Alt-Z] menu, and [Alt-G] is just below it. 
If you are in automatic mode, the [Alt-G] menu entry will say "Goto manual
now/later".  If you have ALREADY switched to manual mode, the [Alt-G] menu
entry will say "Return to automatic mode".  I.e. instead of using this help
screen, you should be able to quickly refresh your memory just by popping
up the [Alt-Z] menu.

Automation in General
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Automating BBS sessions with Intellicomm can be accomplished in two ways:
via an automated JOB, and/or one or more SCRIPTS.  Automated jobs (in
general) are covered below and they use ICOM.EXE's *built-in* automated
routines, and one or more BBS Information Files (BIFs).  Jobs normally do
NOT use scripts.

With automated jobs and a BIF you can automate BBS logons, mail runs, file
uploads and downloads, new files list collection and BBS file searches
(both import lists to the File Tagger for easy viewing/selecting files to
download), BBS time bank transactions (deposit/withdraw time and download
bytes if available), and even many custom tasks such as opening a new
capture file and sending custom commands to the BBS, or running other
programs or .BAT files, or even running Icom scripts.	There are also many
"side jobs" you can carry out with automated jobs, such as automated virus
checking of new downloads, executing pre- and post-job batch files and
scripts for custom setup work, etc.  Refer to Automation in Detail
for a full explanation.

Scripts are not necessary to automate most BBS tasks but can be extremely
useful for automating anything that the built-in automation routines cannot
handle to your satisfaction.	You can even define Intellicomm-like user
interfaces in scripts which prompt the user for input to determine what to
do.	The only limit to scripts is your imagination: they can do virtually
anything (anything related to Intellicomm, that is).  Scripts are covered
in SCRTUTOR.DOC and in the Script Language help link.

Automated Jobs
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Icom jobs could be considered your "shopping lists" which tell Icom what to
do, and where (at which BBS) to do it.	Jobs are maintained and executed
from the Job Directory which is accessed by pressing [Alt-R] from most Icom
locations.  However, before creating an automated job, you must first have
the proper BBS Information File (BIF) section(s) set up for whatever it is
you want to automate.  Each BIF screen/section serves a different purpose,
and is connected to a different automated job task.  Auto-logons are
connected to the BIF "Logon" screen, mail transfers are connected to the
BIF "Message" screen and so forth.

BIFs could be considered Icom's "map" of a particular BBS and they tell
Icom where the BBS is (the phone numbers), how to traverse the various BBS
aisles (the BBS menus) and how to get stuff off the shelves (how to
download, how to transfer mail, etc).  BIFs are maintained (and can also be
used to dial for manual online sessions) from the BBS Directory which is
accessed by pressing [Alt-D] from most Icom locations.

BIFs are divided up into seven sections on six different screens: General,
Logon, Bank/List (two separate sections on one screen), Message, File, and
Extras.  Icom uses different BIF sections for different tasks, and the
sections are largely independent of one another.	If you want a job that
automates the logon process, you can concentrate only on the BIF "General"
and "Logon" screens and leave it at that.  If you want to automate mail
runs, you can then move on to the BIF "Message" screen and so forth.	You
needn't set up the entire BIF unless you want to automate ALL the tasks
that Icom's internal routines are capable of automating.  If you never
transfer mail, you can leave the BIF "Message" screen blank.  If you don't
care about auto-logons you can even define just the BBS/Host Name,
telephone numbers, and Port Settings in the BIF... and leave it at that. 
Such a BIF could be dialed from the BBS Directory using the "Dial" command,
just as you'd use the dialer in a general comm. program.

The point is to not assume that Icom *requires* more setup than your
average comm. program does.  It doesn't.  If you want only the same level
of functionality that most comm. programs provide (i.e. no automation other
than through scripts), Icom's setup and use is almost identical to most
other comm. programs.  Only the extra bonuses require extra setup... and
it's all much easier to set up, and much more reliable, than programming a
script for another comm. program would be.  Starting BIF Learn by pressing
[Alt-Q] while in manual mode, is the usual way to set Icom up for
automation (but not the easiest; see below).

Easy Automation
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The easiest way to automate one or more tasks on a new BBS is not to use
BIF Learn, believe it or not.  The EASIEST way is to call the BBS and look
for a file called ICOMAUTO.ZIP.  Actually you needn't even look for it...
just try to download it, and if it doesn't exist the BBS will tell you so. 
Please see ICOMAUTO Easy Setups for more information.

See also:
	Automation in Detail
	Automated Logons
	Automated Mail Runs
	Automated Downloads
	Automated Uploads
	Automated Bank Transactions
┬#Intellicomm can carry out quite a number of "side jobs" for you prior to,
and after running one or more automated jobs.  Below is a detailed list of
tasks Intellicomm carries out after you select "Run" from the Job Directory
to execute one or more automated jobs.

The first thing Icom does after you run a job is to perform a check on the
automated job(s) you selected, to determine whether any valid online tasks
are defined.  It goes through each tagged job (in the order displayed in
the Job Directory) checking each task to see if it's valid.  For example, a
job could contain a "Download tagged files" task, but you might not have
any files tagged for downloading... or you might have a "Send message
replies" task defined, but you might not have created a reply packet as
yet.  If no valid jobs are found, the job is cancelled and no dialing takes
place (see \ICOM\CAP\ICOM.DBG if this happens and you're confused as to
why).  If only a portion of the job tasks on a given BBS are valid, the
call takes place but only the valid tasks are carried out (i.e. a message
reply upload will be automatically cancelled if no reply packet exists; but
a mail download will still take place, if it was requested in the job).

During this pre-job check, Icom performs "Packet Maintenance" on any
existing capture files (\ICOM\CAP\*.CAP) and Message Packets, if any exist
and if you requested a "Get all new mail" or "Get personal mail only" task. 

The settings relevant to Packet Maintenance are in the Icom main setup, on
the "General Settings" screen: "File Renumber Mode", "Capture Renumber
Total", and "Message Renumber Total" allow you to define HOW older files
are renamed (with numbers in either the filename or extension) and how MANY
(if any) backup capture files/mail packets to keep on-hand.

Also during the pre-job check, if a "Download tagged files" task is found,
and there are files tagged for download, AND if the "Move Old Downloads"
item (Main Setup/File Transfer screen) is set to "Yes", all files in the
download directory (\ICOM\GET) are moved to the first directory on the
Upload PATH (\ICOM\SND).  This clears out your download directory before
new downloads, so that when the job finishes, only NEWLY downloaded files
will exist in the download directory.  It also readies files for re-upload
to other BBS's.

Next, a series of optional pre-job setup files are executed, to allow you
to perform any necessary (or desired) custom setup work prior to the
automated run.  Each of the pre-job setup files is listed below and ALL are
optional.  There are two tricks to using these files: the .BAT (DOS batch)
files must exist in the Icom 'home directory' (where ICOM.EXE is, or where
the ICOM environment variable points to), and the .SCR (Icom script) files
must exist in the Script Directory (defaults to \ICOM\SCR but can be
changed in the Icom main setup on the "Filenames and Paths" screen).	And
each file must be named exactly as outlined below to be executed.  If you
don't want to execute one or more of these files, either rename the file
(automatically via another pre-job setup file, or manually via the File
Manager) to another name or don't create it at all.  [No pre-job setup
files are included with Intellicomm.  You must create them using Icom's
Text Editor or an external editor.]

PREJOB.BAT is executed prior to ALL automated jobs, if it exists.  It can
be used to clean out directories, rename or move files... whatever needs
doing prior to ALL automated jobs.  BAT files are no match for Intellicomm
scripts, however, and you can accomplish much more, and gain a lot more
control, by creating a PREJOB.SCR file in the \ICOM\SCR directory, and
using any of the over 200 script commands available.  PREJOB.SCR could even
dial up some sort of online weather service to check what the weather is
like before the automated job... What you'd need this weather report for I
don't know, but the point is that you can do darn near anything with
PREJOB.SCR (any Icom script) while .BAT files are limited in what they can
accomplish.  Spend an EASY and ENJOYABLE evening or two with SCRTUTOR.DOC
the next time nothing is on television and you'll increase your control
over your online sessions/Intellicomm tenfold.  Scripts are no more
"difficult" to write than batch files are: they're just more powerful and
flexible, even for DOS and disk-related tasks.

PREMAIL.BAT is then executed, but only if one or more "Get all new mail" or
"Get personal mail only" tasks are about to be carried out.  You can also
create PREMAIL.SCR for more control if necessary.  One other significant
advantage scripts have over batch files is that all of the Icom main setup
and BIF information is at your fingertips from a script.  So you could
easily get message/reply packet filenames (as defined in BIFs) and the
proper message/reply directories, or check the day of the week, or
date/time, etc.  You'll have a difficult time doing any of this from a .BAT
file.

PREDOWN.BAT is then executed, but only if one or more "Download tagged
files" tasks are defined, AND if there are some files tagged for download
on the BBS(s) Icom is about to call.  Again, you can also create
PREDOWN.SCR for more control and flexibility.  If you read the
"INTRODUCTION TO DATABASE COMMANDS (FILE TAGGER CATALOGS)" in SCRTUTOR.DOC,
the PREDOWN.SCR will be particularly useful to you, since you'll be able to
use it to scan the NEWFILES (or any other) catalog and see what's tagged
for download.	You could then selectively Untag (temporarily, using a
custom tag) or Tag certain files, based on whatever criteria you can dream
up (filesize, file date, etc).

Next on the agenda, Icom clears the "New mail packets downloaded", "New
files available for D/L" and "New downloads waiting" statistics displayed
at the Icom Main Menu.  This way you can easily see what's new (if
anything) when you return to your computer after the automated run.

Finally, the dialer is entered and all BBS's you requested "Calls" to are
tagged and dialed.	If one BBS is busy, Icom cycles to the next until it
connects.  Once online it carries out ALL the jobs for that particular BBS,
even if you had Tagged several separate jobs with separate "Calls" all to
the same BBS.	As each automated task is completed, it is removed from the
job queue (in case of a lost connection, so Icom knows what was done and
what wasn't) and when nothing remains to be done on the current BBS, Icom
logs off the BBS and hangs up your modem.  It then returns to the dialer
and continues dialing any other BBS's until all jobs are complete, or until
the "Max. Redials" defined in each BIF (1st screen) has been reached... or
until you abort dialing by pressing [Esc].

Next comes the post-job processing.  Depending on the job(s) executed, this
could take a few minutes.  But if you use Icom as it was intended to be
used -- running automated jobs while you're out or sleeping (we all do one
or the other once a day, don't we?) -- the length of time the post-job
processing takes won't make any difference.

First up, Icom checks to see whether the "Extract NEWFILES in QWK" setting
on the main setup/File Tagger screen is set to Yes.  If so, and if this BIF
setting contains a filename (BIF "Message" screen):

║ Extract Newfiles NEWFILES.DAT	    More Mail Found  <MAX>«		    ║
			    ────────────
(the BIF is checked for each new mail packet downloaded; Icom keeps track
of the BIF used to download each mail packet) Icom attempts to extract the
file (the new files list) from the mail packet.  It performs this
extraction using the "Main Unpack" and "2nd Unpack" commands defined in the
Icom main setup on the "Filenames and Paths" screen.  If the new files list
is successfully extracted (into a temporary directory), Icom renames it to
BIFNAME.NEW (BIFNAME being the BIF ID/Filename of the BBS the packet was
obtained from)... then moves the list to the \ICOM\LST directory, where it
can be auto-imported into the Tagger (see below).

Next comes the POSTMAIL.BAT and/or POSTMAIL.SCR files, if new mail was
obtained.  You can use these to rename or delete new files lists extracted
in the step above, if you don't want the new files from certain .QWK mail
packets to be imported into the File Tagger... or for anything else that
needs doing such as inserting the new mail into your BBS message base (if
you're a Sysop), or running a program that re-formats or otherwise cleans
up your mail before you read it.  The easiest way to determine whether NEW
mail came in, in POSTMAIL.BAT/.SCR is to check for the existence of a
particular mail packet.	If it exists, new mail was obtained.  If not, no
new mail was obtained.  Remember, Icom performs the "Packet Maintenance" on
existing message packets BEFORE placing the call (renaming the existing
message packet to either MNAME01.EXT or MNAME.E01, where MNAME is the name
of the original mail packet, and .EXT is the original extension).  So by
the time POSTMAIL.BAT/.SCR get to it, if a mail packet exists (assuming you
pick up ALL your mail at the same time, with one automated job), it was
just obtained.

See also:
	Automation in Detail Continued
b'[Continued from Automation in Detail.]

Next come POSTDOWN.BAT, POSTDOWN.SCR, if new files were downloaded (Icom
checks your default Download Directory and will not call either POSTDOWN
file if the directory is empty).  These files (if found) are called once
and only once, no matter how many files were downloaded.  You could use
them to handle all the new downloads en masse (strip BBS ads in .ZIP
comments, or run any other external utility) in a single swipe.	See
POSTFILE.BAT/.SCR below to handle each new download separately.

After that, the File Tagger Catalogs are updated if any file transfers took
place.  Tagged files that you didn't have time to transfer remain tagged,
while files that you did download (or were not found on the BBS, or already
existed on the BBS on an upload) are untagged and *flagged* to be deleted
(the exception being the FILELIST catalog, where files are NOT flagged to
be deleted; they're simply untagged if no more "Upload Pending:" ID's
exist).  These deleted records are not permanently removed, yet.

If the "Keep an Upload Catalog" item on the main setup/File Tagger screen
is set to Yes, files (and the full descriptions) that were successfully
auto-downloaded via a File Tagger catalog are moved to the FILELIST
catalog, so you can later tag those files for re-upload to other BBS's...
The FILELIST (upload) catalog is also useful just for keeping track of
files you download... since it maintains the file's description from the
BBS (new files list) you downloaded from.

During this process, POSTFILE.BAT and/or POSTFILE.SCR are called once for
*each* new file that was downloaded.  The POSTFILE.SCR script has been pre-
programmed (included with Intellicomm) to scan each new download for
viruses -- but it requires a small amount of setup before use.  To use
POSTFILE.SCR you must enter the Script Manager by pressing [Alt-U], then
hilight POSTFILE.SCR and select "Edit".  Then just read the comments in the
script and make any necessary (or more desirable) changes.	When done, save
your changes.	Icom will then execute it on all new downloads.  

POSTFILE.BAT is also supported, but you're really better off doing
everything from POSTFILE.SCR if you can... since you'll have access to the
complete file record (filename, date, size, description, etc.) from
POSTFILE.SCR.	You have access only to the filename (passed as %1),
extension (passed as %2) and full D:\PATH\FILENAME.EXT (passed as %3) in
POSTFILE.BAT.	And you 'can' get the file description in \ICOM\FILE_ID.DIZ,
which Icom automatically creates for each file prior to calling
POSTFILE.BAT / POSTFILE.SCR.	But you can do a lot more from POSTFILE.SCR
than you can from a .BAT file.

Also during the above process, while cycling through newly downloaded
files, an optional export of all new downloads (filename, date, size,
description) can be appended to a user-defined text file, in a specific BIF
format (both the D:\PATH\FILENAME.EXT of the text file, and the BIF format
to use for the export are defined in the main setup on the File Tagger
Settings screen).  This feature is mainly for Sysops who use Intellicomm
for automated file collection, to automatically update their BBS file
listings with the new downloads.  NOTE:  By default, if POSTFILE.SCR
(described above) finds a virus in a file, Icom does NOT export the
filename/ description to this user-defined text file.

We're still not done yet...  Next up is the updating of the DOWNLOAD.NDX,
which is an index Icom uses to keep track of all the files you've
downloaded (also user-configurable; see below).  The idea is that once
you've downloaded a file, even if you delete it later, you don't need to
see it again on a new files list.	The duplicate checking routines in the
Tagger are intended only to eliminate dupes from one .NEW list to the next. 
DOWNLOAD.NDX takes over where the duplicate checking leaves off, and
eliminates any files that already exist (or did exist at one point) on your
disk.  The relevant settings (whether to use DOWNLOAD.NDX, and what
directories to scan for new downloads) are easy to find and are again on
the main setup/File Tagger Settings screen.	Use the online help from there
if you need more information.  Since the updating of DOWNLOAD.NDX is done
*last*, any files that had viruses in them and were deleted above (by
either POSTFILE.SCR or POSTFILE.BAT) are not added to the index, and thus
the file will be permitted in future NEWFILES listings.  It's possible that
the file would be 'infected' on one BBS, but not on another.  It's also
possible that the virus has been removed, and the file was re-uploaded. 
It'll do no harm in any case to re-download the same file; if you re-
download it and it fails the virus check again, you'll know about it via
POSTFILE.SCR.

Next Icom looks for \ICOM\LST\*.NEW (new files lists either captured via a
"Get new files list" job task or extracted from a QWK mail packet as
explained earlier) and if any are found, AND if the "Auto Import New Files"
setting (main setup/File Tagger screen) is set to "Yes", the Tagger imports
each list into the proper catalog, then deletes it.  There are quite a few
user-configurable options connected to these imports, to allow you to
reformat and clean up the file descriptions, to exclude files you aren't
interested in, to point out files you are especially interested in, and so
on.	All the 'global' import options are laid out in the main setup on the
File Tagger Settings screen, and the Tagger Keywords screen.  It's a good
idea to give these settings (and the online help, once you're there) a
look-see before you import many files into the Tagger.  There are also two
useful import settings in each BIF: "Catalog to use", and "D/L Priority" on
the Bank/List screen (/List being settings related to BBS new files lists)
that tell the Tagger which catalog to put the new files in (registered
users only; allows you to keep files from different BBS's and/or different
file areas in separate Catalogs instead of lumping everything in the
NEWFILES catalog), and how desirable the BBS is as far as downloads go (for
use when the same new file shows up at two or more BBS's).	Please see
New Files Imports for more details.

After importing any .NEW files lists, Tagger then performs automatic (but
user-configurable, as usual) maintenance on any catalogs it imported files
to.	The way the Tagger is initially set up to work, it shows you ONLY the
new files that were imported from the last .NEW list, and it only keeps
enough older files around to eliminate duplicates from one .NEW list to the
next.  3 day's-worth of older files are kept on-hand by default, to
eliminate duplicates (which often show up from one .NEW list to the next),
and then it sets the Tagger View Date to filter out those older files,
since they've now served their purpose in eliminating duplicates from the
current .NEW list.

This assumes that you do the following: 1. Run your job to collect new
files; 2. browse all the new files and tag any files you want to download
and "Note" any files you're interested in but don't want to download
immediately; 3. only THEN run your job again to pick up another new files
list.  And at that time you should be completely unconcerned with all BUT
the Tagged and Noted files in the Tagger, and you won't ever want to see
the older files again.

If you do it this way, you'll be happy with the way the Tagger is set up by
default, since it filters out all but Tagged and Noted files, and files
from the very LAST .NEW files import.  All of this is configurable though,
and the relevant settings are: "Purge Noted # Days Old" (when to get rid of
old Noted files; defaults to never) "Purge Untagged # Days Old" (when to
get rid of old untagged files; defaults to 3 days) "Auto Pack when #
Purged" (how many files must be marked as 'Deleted' before the catalog is
packed; defaults to 30 and avoids lengthy packs until something semi-
substantial must be removed) and "Auto View Date Update" (whether you want
the View Date set to 'today' automatically on imports to filter out files
from the LAST new files list).  All are on the main setup/File Tagger
Settings screen.

Finally, the Download Directory (\ICOM\GET) is checked to see if any
ICOMAUTO.* files (Auto-BIFs) were downloaded.  If any were, the files are
processed and installed for you.  Please see ICOMAUTO Easy Setups for
details.

Next, Icom will give a silent sigh of relief, wipe the sweat off its
forehead, and will either Exit to DOS (if you had an Exit to DOS task
defined in any of the jobs you ran; these are always saved until the end)
or will sit back and wait for the next run, complete with screen blanker
(this will be the case if you defined a "Repeat job" task in any of the
jobs you ran; Repeat overrides any Exit to DOS requests if both are found
in the jobs you ran), or will return to your Base/Startup area (normally
the Main Menu, but also configurable on the main setup/General Settings
screen) to await your next move.

When you return to your computer (if Icom didn't exit to DOS, and if your
Base/Startup Area is the Icom Main Menu) you can then check the second
group of Usage Statistics on the right side of the screen to see what was
accomplished.	If new mail is waiting, and you've defined your external
mail reader command on the main setup/Filenames and Paths screen, pick
"Mail Reader" and you'll be whisked off to read the new mail.  If new files
were imported, pick "Browse New BBS Files" to enter the Tagger and Tag what
you want for the next automated run.  If something went wrong, or you just
want to see how Icom handled the malfunctioning BBS and three lost
connections it ran into, pick "Review Session Captures" then "View" the
ICOM.CAP file for a copy of the automated session.  While there, you might
also want to peek at ICOM.USE (the Usage Log) to see what files got
transferred when and where, and when Icom connected and disconnected at
various BBS's.  ICOM.DBG is also useful in debugging a fouled up automated
session (see Debugging Log for details).
ÅYou can automate BBS logons in Intellicomm using one of two techniques. 
The first (and most reliable) is to activate "BIF Learn" mode from the Main
Menu, BBS Directory, or Terminal menu and follow the bouncing ball.  The
second is to use a script to handle the logon, and place the script
FILENAME in the "Connect Command" item on BIF screen 1, preceded by @. 
Example:

║ Dial Prefix	. . 1			  Connect Command  @SCRLOGON		 ║

Note that the BIF *must* have a "Logon Password" defined in it for the
Connect Command to be executed, and the script must logon right to the BBS
Main Menu (at which point it can return to let Icom switch to manual.  Icom
doesn't exit the auto-logon routines until it finds the BBS Main Menu).
If you have purchased Intellicomm, Script Learn can be very helpful in
creating logon (and many other) scripts.

Which logon method are you interested in?

	BIF Logons
	Script Logons
EAutomating your mail runs with Intellicomm:

 1.	Download an offline mail reader program (DeLuxe, Offline Express,
	MegaReader, Blue Wave, SessionManager, RoboMail to name a few: dozens
	of these programs are available on BBS's) and read its documentation. 
	Intellicomm will interface with any Mail Reader.	All Icom cares about
	is (a) where your Reader expects to find newly downloaded mail
	packets; (b) where it creates your reply packets.  The "Message Dir" /
	"Reply Dir" items defined in the main setup Filenames and Paths screen
	is where you defined these items.

  2. Tell Intellicomm what sort of mail system the BBS is using (Qmail,
	RoseMail, TomCat, Blue Wave and so forth).  The only way to find out
	is to access the BBS's mail system and write down the "Welcome to" or
	"Copyright" line when you first enter it.

  3. Activate BIF Learn and select either Create or Modify (Modify can be
	used if you've already automated the Logon process).  When you reach
	the BBS Main Menu, press [Alt-G] if necessary, then select
	"Message/Reply Transfers" and follow the bouncing ball.
Automated downloading with Intellicomm involves three steps:

 1.	Importing one or more BBS files listings into the File Tagger, and
	Tagging the files you want to download.
 2.	Setting up and saving a job (once) to tell Intellicomm you want to
	download the tagged files.
 3.	Running the job.

Importing new files listings into the Tagger can be done in several ways,
and information on imports is available in the New Files Imports link if
you're having trouble, or just want to know the various ways of getting
files into the Tagger.

Setting up the job to download the tagged files is done via the
Job Editor.  To create a new job, press [Alt-R] to enter the
Job Directory, then select "Create" from the bottom bar menu.

You will then be asked to select the BBS you want to call.	Hilight the BIF
you want to use, then press ENTER (or move the mouse cursor to "Select" on
the bottom menu, then click).  You then enter the Job Editor where you
define the job tasks you want Intellicomm to carry out.  A common job
people use to download tagged files is the following:

	Call <some BIF>
	  Get new files list
	  Download tagged files

This causes Intellicomm to first pick up a list of the new files that have
arrived on the BBS since the last time you called (the files are then
automatically imported to the File Tagger when you disconnect, so you can
Tag more files to download), and then download any files you've tagged from
the previous new files list (if any).  You can also add other tasks if you
want to send/get mail at the same time, etc.  But the only task 'required'
to get Intellicomm to download the tagged files is the "Download tagged
files" task.  Just press 7 on either the number keys at the top of the
keyboard, or on your numeric keypad to select the task.  Mouse users can
simply move the mouse cursor to the "Download tagged files" text in the
left column and click.

TIP: If you wish to have Intellicomm delay the job until a specific time,
please see the Set job starting day/time link.

When your job is all set up, select "eXit" and enter a description that'll
remind you about what the job does, then press ENTER.	As a description you
might enter "Download files from Joe's BBS", or "Get mail/files from Joe's
BBS", or whatever will remind you of what the job does.  Whatever you enter
here in the job description will be displayed in the Job Directory, where
you select jobs to run.	You need only define a job once.  From then on you
simply hilight it (and Tag it, if running multiple jobs), then select
"Run".  If you have any files tagged, Icom will call the BBS and download
them.  If you DON'T have any files tagged and you "Run" the job, dialing
might not take place if there is nothing else to do on the BBS.	Icom
automatically cancels a job if there's nothing to do.
ëThere are many methods of automating uploads with Intellicomm.  Due to the
rather complex nature of BBS uploads, there is no BIF Learn feature for
automated uploads as yet and thus the BIF must be set up (or checked)
manually before you attempt automated uploads.  The easiest way to perform
this check is to first perform a manual upload, then make a printout of the
\ICOM\CAP\ICOM.CAP (Capture Log) after the upload for use during your BIF
check.

BIF Upload Items
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The relative items in the BIF that must be filled in properly on the BIF
"General" screen:

Send Files		Protocol to use for uploads
 BBS Letter		Response when the BBS asks for a protocol to use (see
				the "Enter Protocol" prompt below).

...and on the BIF "File" screen:

Access File Menu	If a File sub-menu is used on the BBS
Upload File[s] 	BBS command to upload files
Chars per Line 	Max. characters per line for descriptions
Max Lines 		Max. lines per file description
Files per U/L		Max. files to upload per batch
Batch Full Answr	If applicable (see "Batch Full" below)
Leave File Menu	If applicable
Logoff File Menu	If applicable

File Menu 		The format of the BBS File Menu (if any)
Enter U/L Fname	BBS prompt that asks for a filename to upload
Enter Protocol 	BBS prompt that asks for a protocol
Duplicate File 	BBS prompt tells Icom that the file exists.  You can
				get this prompt easily by simply trying to upload a
				file that you know already exists on the BBS.
Enter Descrip		BBS prompt (any text) that asks for the file
				description.
Batch Full		BBS prompt (if any) displayed at the end of each batch
				of filenames, just before the transfer beings (the
				prompt normally has options such as 
				[G]oodbye after transfer, [A]bort, [C]ontinue).
Upload File[s] 	BBS text that tells Icom when to actually begin the
				upload.

Tag some files for Uploading
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Once the BIF is set up, select "View Prior Downloads" from the Icom Main
Menu to "Tag" one or more files for upload.	Intellicomm automatically
moves any files it automatically downloads into the FILELIST catalog (the
Catalog you view when you select "View Prior Downloads") so that you can
easily upload those files to other BBS's.  To upload a file, simply hilight
it and select "Tag" from the bottom menu.  Your list of BIFs will then be
displayed, and you can then "Tag" and "Select" the BBS's you want to upload
to.

Manual Imports
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If you have some files on-disk that you want to upload, and you don't see
them in the FILELIST catalog, select "Tools" | "Import/Export" | "Import
from Disk" from the Tagger.  You can then import all the files in a given
directory (or *.ZIP, etc).  Once the import is complete select "Edit" and
press the [Up] arrow key to enter a description for the file.  You need
only do this ONCE.	You can then upload the file(s) to BBS's automatically.

Creating/Running the Job
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The last step is to create jobs that contain an "Upload tagged files" task. 
You can either create new jobs, or modify an existing job (such as your
"Download tagged files" job, to have one job perform both uploads and
downloads).  Examples:

[A single job to do everything.]

Call Joe's BBS
  Send message replies
  Get all new mail
  Upload tagged files	───Insert wherever you want
  Get new files list
  Download tagged files

[A single job to handle uploads at all the BBS's you call.]

Pause until 12:05am on Everyday
Call Joe's BBS
  Upload tagged files
Call Another BBS
  Upload tagged files
Call Yet Another BBS
  Upload tagged files

...and so forth.  Icom doesn't create the job(s) for you, since it doesn't
know HOW you want to handle the uploads (in which order you want to handle
them, what other jobs you want to do at the same time, etc).  Creating the
job is done ONCE.  From then on, just "Tag" the files you want to upload,
and hilight and "Run" the job(s) that contain the Upload tagged files
tasks.
8Automating BBS Time Bank transactions involves:

 1.	Setting up a BIF for the Time Bank.  Activate BIF Learn and select
	Create or Modify (select Modify only if you've already used BIF Learn
	to automate the logon).	Press [Alt-G] when you reach the BBS main
	menu, then select "Time Bank Transactions" from the BIF Learn main
	menu and follow the bouncing ball.

 2.	Setting up one or more jobs with "Bank Withdrawal" and/or "Bank
	Deposit" tasks.  Example:

	Call Joe's BBS
	  Withdraw 60 min 1000000 bytes
	  Get new files list
	  Download tagged files
	  Deposit 60 min 1000000 bytes

When you set the Bank Withdrawal/Deposit tasks up, Icom will prompt you for
the number of bytes (Download Bytes) to withdraw from the Time Bank.	ONLY
enter a value of the BBS Time Bank allows deposit and withdrawal of
Download Bytes.
┤To automate a BBS logon using a BIF, select Learn Modes from the Main Menu
then select "BIF Learn".  Once you start the learn mode just follow along,
reading all the instructions on the screen, pressing the [F1] help key when
you need help.  When you finish, you will be asked whether to create an
automated logon JOB for the BIF.  If created, this job will contain the
following tasks:

	Call The BBS				 (where "The BBS" is the BBS/Host Name)
	  Go to manual [terminal] mode

The job will have a description of (i.e. will show up in the Job Directory
as):

	Logon - BIFNAME

where BIFNAME is the BIF ID/filename you entered when asked by BIF Learn. 
To call the BBS and logon/switch to manual, change to the Job Directory by
pressing [Alt-R], hilight the 'Logon - BIFNAME' job, then select "Run". 
Icom will then dial, logon, and sound an alarm every ten seconds (for a
total of two minutes) when it reaches the BBS Main Menu.  If you do not
return and press a key within two minutes, Icom automatically disconnects. 
If you do return and press a key before the two minutes is up, Icom
switches to manual to leave you online for a manual session.

When you're finished, logoff the BBS (enter [G]oodbye at the BBS Main Menu
normally) then hangup by pressing [Alt-H].  You will then return to the Job
Directory and can press [Alt-X] to exit Intellicomm, etc.  If you'd rather
have the job itself exit to DOS for you after your online session (after
you disconnect), "Edit" the job from the Job Directory and add task #17:

║ 17  Exit to DOS				    │ Exit to DOS				    ║

The job would look like this:

	Call The BBS
	  Go to manual [terminal] mode
	  Exit to DOS

There may also be cases where you want to dial SEVERAL BBS's for manual
sessions.  If you have "Logon" jobs defined for all the BBS's, you can
accomplish this from the Job Directory as well by simply hilighting and
Tagging each job, then selecting "Run".  Icom will then dial each BBS,
auto-logon to each in turn and switch to manual.	When you finish at one
BBS and disconnect, Icom returns to the BBS Directory and continues to dial
any other BBS's you haven't connected to yet.  Note that even if there is
an "Exit to DOS" task in the job, Icom will SAVE it until *all* jobs have
finished processing.  So only after you disconnect from the last BBS tagged
will you return to DOS.

Dialing/logging on WITHOUT using a Job
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
You can also dial/auto-logon and switch to manual via the BBS Directory. 
To go this route, press [Alt-D] to enter the BBS Directory, hilight the BBS
of interest (or hilight several and "Tag" each) then select "Dial" from the
bottom menu.  As long as there is a Logon Password defined in the BIF
(which there will be if you use BIF Learn to create the BIF), Icom will
automatically logon upon connecting, and will sound an alarm/switch to
manual when it reaches the BBS Main Menu.  Note that the two minute
pager/logoff protection is NOT in effect when you go this route.  So if you
don't hear the alarm and return, you'll be left sitting at the BBS Main
Menu just as with any other communications program (the "Dial" option of
the BBS Directory is intended to function just as the Dialer in most
general comm. programs).
≡Enter a telephone number, including any area/country codes but NOT
including the modem dialing prefix (ATDP, ATDT, etc).	Examples:

555-1234	 [Most modems ignore hyphens, but you can omit if necessary.]
5551234
1-416-555-1234
14165551234

If you must dial 9 to get out, you should follow the 9 with one or two
commas.  Each comma will cause a two second delay to wait for a dial tone:

9,555-1234
9,5551234
9,,1-416-555-1234

If you have set up any dialing codes in the Icom main setup ("Dialing"
screen) you may specify the code by using the symbol attached to the code
(either !, @, or $).  For example, if you had set up LD dial code ! with
'1-416-', you could use:

!555-1234

This would translate to 1-416-555-1234 when Icom sent it to the modem.
┌&BIF Learn is designed more to familiarize new users with the concepts
behind BIFs and to provide a starting point, than it is to produce fully
working BIFs.	After using BIF Learn you have to (and will also probably
WANT to) get into the BIF manually yourself to check it over and possibly
make some adjustments.

BIFs are the "heart" of Intellicomm's automation, and if you run into a
problem with anything even remotely connected to an automated job, it is
almost surely fixable by changing one or more settings in the proper BIF.
BIFs tell Intellicomm *everything* about a BBS, and if the right
information is defined, Icom works fine.  If the wrong information is
defined, you get the appropriate results (errors).

What to concentrate on?
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The first step when working with BIFs is to decide what to concentrate on. 
BIFs are not taken/used as a "whole" by Intellicomm, and they should not be
taken all at once by you either, or you might become overwhelmed.  There
are over a hundred settings in each BIF... but you should never have to
concern yourself with more than two or three of them at a time.	The tasks
that Icom automates are listed below, followed by what (in general) you
should concentrate on to fix problems you're having in that area:

Problem Area				Techniques/Where the solution lies
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Modem Initialization	If your modem isn't responding, find the problem
					via process of elimination.  Does the hardware
					work?  You can test this by using another comm.
					program.	Most modems come with a comm. program
					you can test with; if it doesn't work with other
					software, two things you can check before bringing
					the hardware in for repair are (1) all the
					connections are tight; (2) you don't have a mouse
					or other driver using the same IRQ line that the
					modem uses.  Re-boot with no CONFIG.SYS or
					AUTOEXEC.BAT file and try Icom again.  If it
					works, there is another device driver using the
					same IRQ line as your modem.	If you're sure it's
					a software (Icom) problem, access "Intellicomm
					Setup" via the Main Menu, change to the "Terminal"
					settings screen and check that the COM port, port
					settings, flow control, and Initialize Modem
					string are all defined properly.  Finally, check
					the BIF "Port Settings".  Each BIF holds port
					settings specific to each BBS.
Dialing				If your modem works, the Intellicomm Main Setup
					"Dialing" screen, or the BIF "General" screen
					(phone numbers/port settings and dial prefix #) is
					where the solution to dialing problems lies. 
					Again, try process of elimination.  Can you enter
					the "Terminal" and dial/connect manually?  Select
					"Terminal" from the Main Menu, type in ATDT5551234
					(where 5551234 is the BBS phone #; substitute ATDT
					with ATDP if you don't have touch tone on your
					line).  All Intellicomm does from its dialer is to
					enter the above command to your modem... then to
					watch for the CONNECT message from your modem
					before switching to Terminal mode.  All the
					settings (dial prefix/suffix and CONNECT message
					particularly) are laid out in the main setup on
					the "Dialing" screen.
Logon				Problems with automated logons (assuming you use a
					BIF and not a script... scripts are self-contained
					and not relevant to this discussion) usually lie
					in a simple prompt mismatch on the BIF "Logon"
					screen.  The best idea is to logon manually and
					make a printout (see below), then to compare the
					BBS prompts and commands (the printout) to the BIF
					prompts and responses.  See BIF Logon Screen for
					specific information.
Mail Upload			If your reply packets NEVER get uploaded and Icom
					never even tries, the problem is that Icom is not
					finding them, and thus thinks you never have any
					replies...  The answer is in the main setup on the
					"Filenames and Paths" screen (Reply Dir) and/or in
					the BIF on the "Message" screen (Reply Filename). 
					Make sure you have the proper directory AND packet
					filename defined.  If you're having a different
					problem, again process of elimination should point
					you to the solution.  Can Icom access the Message
					Menu?  If not, the answer is on the BIF "Message"
					screen in the "Access Msg. Menu" command, and the
					"Message Menu" PROMPT.  Icom must recognize the
					Message Menu (assuming one is defined in the BIF)
					before it continues with message-related tasks. 
					If Icom recognizes the Message Menu, but doesn't
					send the "Upload Replies" command... are you sure
					you have a "Send message replies" TASK defined in
					your JOB?  If not, Icom won't upload replies.  If
					Icom enters the upload command but doesn't start
					the upload, it's most likely a mismatch in the BIF
					"Send Replies Now" prompt.  Icom watches for this
					prompt (if defined) before it starts the upload. 
					Is the upload starting but not getting anywhere? 
					If so you probably have the wrong "Send Mail"
					protocol defined in the BIF, on the "General"
					settings screen (screen 1) near the bottom.	See
					BIF Message Screen for more information, or better
					yet edit your BIF and see use the online help
					while in the BIF Editor.
Mail Download			Please see the above for hints.  Icom handles mail
					downloads in basically the same way it handles
					mail uploads except that it sends a different
					command and watches for different prompts (all
					message-oriented commands Icom sends, and the
					prompts it watches for, are defined in the BIF on
					the "Message" screen).  Prompt mismatches are the
					most common problem.  Note also that Icom "knows"
					the proper prompts and commands for quite a few
					mail systems, and in most cases you will not have
					to define anything on the BIF Message screen
					manually.  Simply set the "Message Type" from BIF
					screen 1 to set the BIF Message screen up for a
					specific mail system.
File Upload			For general information/help on automated uploads,
					see Automated Uploads (important if you haven't
					already read it).  File uploads will either be
					simple or impossible to automate.	There's really
					no middle ground, and everything Icom uses to
					accomplish uploading is laid out in the BIF on the
					"File" screen.  See the online help from there for
					detailed information.  Note also that there are
					four of general purpose File Extra prompts
					available on the BIF "Extras" screen that you can
					use for general responses... or can even use to
					call a script to handle something complicated. 
					All BIF Responses (prompt responses Icom would
					normally send) can be replaced with @SCRIPTNAME to
					run a script from a BIF.  They can also be
					replaced with &SCRIPTCMD (a script command such as
					HANGUP, DOWNLOAD, etc).
File Download			For general information/help on downloads, see
					Automated Downloads (important if you haven't
					already read it).  The automation part of file
					downloads (getting Icom to call and pick up the
					files) is quite straightforward.  If something
					goes wrong, the answer lies in the BIF on the
					"File" screen (see BIF File Screen for detailed
					information).	If you have problems with imports
					of BBS file listings, the BIF "Bank/List" screen
					(only the lower 'list' portion of the screen is
					relevant to BBS file list imports) is where the
					solution lies.  See also New Files Imports and
					BIF Bank/List Screen.

Make a printout
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If you're having problems with an automated job (mail transfer, logon,
etc.) the first step is to do the task MANUALLY, with capture on, and then
to make a printout of the ICOM.CAP file for reference while in the BIF
Editor.  If you're having problems with the logon you'll have to remove
your Password from the BIF before Icom will let you logon manually.  If a
password is entered in the BIF, Icom assumes you want it to auto-logon.  If
no password is defined in the BIF, Icom lets you logon manually.

I'm out of BIF prompts!
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Sooner or later you may run into a BBS that is absurd enough to exhaust the
dozens of prompts that Icom BIFs support.  There are a couple of things you
can do if you run into this...  First, make sure you've used up all the
"Extra" prompts on the BIF Extras screen.  You can handle up to twelve
extra prompts there for general purpose.  Second, try getting one or more
prompts to pull double-duty.	On BBS's that exhaust BIFs, often the BBS
developer or Sysop has just been inconsistent and may have used a colon at
the end of one prompt... a question mark at the end of another... and an
exclamation point at the end of another.  But the TEXT of the prompt, at
some point, will be the same.  Solution: don't define the punctuation at
the end of the prompt (BIF prompts will match anywhere on a line and
needn't be the end of the prompt).  Find a word or symbol that matches in
all the prompts, and use that.  Of course, this is assuming the same
response must be sent to all these prompts, but this is often the case. 
Third, ask the Sysop to fix the BBS.  Any BBS that exhausts Intellicomm's
ample BIF prompts is out of whack.  The Sysop probably got over-ambitious
when s/he learned how to customize the BBS, and you may be able to talk him
or her into reversing these changes (which are probably all but useless to
everyone on the BBS); at least for the important stuff such as mail and
file transfers.

Scripts are always available for use when you absolutely cannot get the job
done with a BIF.  With Script Learn, you should be able to create the
script easily, and you can then just plug the script in to your BIF by
using @SCRIPTNAME as the response to a BBS prompt.
½The following is a list of command line options for ICOM.EXE.  You may
specify one or more command line options from DOS (or via a menu system,
Windows, etc) after the ICOM.EXE command.  See the examples below for
details.

Command line parameters must be preceded by either a hyphen (-) or forward
slash (/) or the usual DOS 'switch' character on your computer, as defined
by the operating system.  Case is not significant (/AREA /Area and /area
all do the same) but each command line parameter must be preceded by at
least one space or tab (/m /o ... not /m/o).  Parameters that require a
second value/argument use a colon (:) to separate the parameter from the
argument (/Run:MAIL).  All parameters, other than the /Run switch, are
processed as they're encountered.	The /Run switch is saved until all other
options are processed.  Below, | means one OR another of the values may be
used.

/Area:M|J|B|T|Ta|S|H	Causes Intellicomm to bypass the usual 'Startup
					Area' defined in the main setup, and instead go
					directly to the 'M'ain Menu, 'J'ob Directory,
					'B'BS Directory, 'T'erminal, 'Ta'gger, 'S'cript
					Manager, or 'H'ost Mode.  Only the first letter of
					the area is required (except for "Ta"), but for
					clarity you can use more: /Area:Job, /Area:BBS,
					/Area:Tagger, etc.	Don't use a space though or
					you'll create a separate parameter: /Area:Job
					Directory is not valid as Icom will set this as
					one parameter of /Area:Job and another of
					Directory.
/Cat:				This switch is only of use in combination with an
					/Area:Tagger switch (see above) and if used it
					must PRECEDE the /Area:Tagger switch.  It allows
					you to specify WHICH catalog the Tagger should
					load for viewing when it's entered.  See below for
					an example.
/Ini:ININAME			Allows you to use another .INI (main
					initialization/ setup) file. ININAME would be the
					'base' name of the .INI file (you can save another
					.INI file by entering the main setup, changing the
					settings, then entering a filename other than
					"ICOM" on exit).  For example, if you use a null
					modem cable between two computers from time to
					time, and have previously created CABLE.INI, you
					could use it with the command ICOM /ini:CABLE. 
/M					Causes Intellicomm to use its default monochrome
					screen colors (black and white).
/O					Tells Intellicomm that you're already online,
					which causes it to refrain from initializing your
					modem, and to go directly to Terminal mode.	The
					main setup option "Init Modem if Connected?"
					(Terminal Settings) can be set to NO to force Icom
					to skip modem initialization of a carrier is
					detected.  But unfortunately many modems will not
					report the carrier status properly UNTIL the modem
					has been initialized and an &C1 command has been
					sent... so that option doesn't work for everyone. 
					Use /o if this is the case with your modem.
/Pack				Same as selecting "Pack" from the Alt-X exit menu,
					causes any Jobs/BIFs marked as deleted to be
					permanently removed from the Job Directory/BBS
					Directory, and will also delete the .BIF file on-
					disk.  Also packs the ICOM.PWD password data file
					and removes old/unused passwords. THIS PARAMETER
					CAUSES AN AUTOMATIC EXIT TO DOS WHEN DONE.
/DBFPack				Packs all File Tagger catalogs.  THIS PARAMETER
					CAUSES AN AUTOMATIC EXIT TO DOS WHEN DONE.
/Run:SEARCHSTRING		Causes Intellicomm to "Tag" all Jobs containing
					SEARCHSTRING in their job descriptions (as
					displayed in the Job Directory; case insensitive),
					then perform an automatic "Run" to run all tagged
					jobs.  THIS PARAMETER CAUSES AN AUTOMATIC EXIT TO
					DOS WHEN DONE.
/Scr:SCRIPTNAME		Allows you to run an Intellicomm script directly
					from the command line.  SCRIPTNAME would be the
					filename of the script.	If no directory is
					specified, the default Intellicomm Script
					Directory (defined in the main setup) is assumed. 
					If no extension is specified, .SCR is assumed. 
					You may use multiple /Scr: parameters if necessary
					(/scr:SCRIPT1 /scr:SCRIPT2 ...).

Examples:

ICOM /CAT:FILELIST /Area:Tagger	Goes directly to the File Tagger without
							initializing your modem or opening the
							COM port, loads the FILELIST catalog for
							viewing.	When you exit the Tagger, you
							will exit right back to DOS.
ICOM /m /o					Causes Intellicomm to use mono colors,
							to bypass modem initialization, and to
							go directly to Terminal mode.
ICOM /Area:B					Causes Intellicomm to go directly to the
							BBS Directory at startup.
ICOM -ini:SPECIAL				Causes Intellicomm to use the main
							settings stored in SPECIAL.INI, instead
							of the default ICOM.INI.
⌐Intellicomm 'Catalogs' are indexed, dBASE-compatible databases that are
maintained by the File Tagger.  Two catalogs are kept by default: NEWFILES,
and FILELIST.	NEWFILES holds (converted) BBS new file listings, and
FILELIST holds a list of files Intellicomm has previously auto-downloaded
from the NEWFILES catalog.

There are many user-configurable settings in the Icom main setup, on the
File Tagger Settings screen, that provide you with control over virtually
all aspects of catalog creation, expansion (imports), and maintenance
(automatic clean ups).  The best way to become familiar with all of the
settings is to enter the Icom main setup (via the Main Menu, etc), select
"File Tagger Settings" and "Tagger Keywords", then have a look at the
settings (using the online help again once there for items you don't
understand... and there will probably be many you don't understand
initially).

There is no "single" help topic that can explain all aspects of File Tagger
catalogs.  There are many factors to consider for each catalog, and a
different set of rules applies to the FILELIST 'upload' catalog, as opposed
to the NEWFILES (or your own custom) 'download' catalog(s).

Instead of duplicating information here, to get a list of *all* the help
topics containing information about File Tagger catalogs, simply press
[Ctrl-F1] (Search) or click on the [Ctrl-F1] at the bottom of the screen
with your mouse.  Then enter the word "catalog" (no quotes) when asked what
to search for.

The help system will then search all the help topics, and will display a
list of all topics containing the word 'catalog'.  If you read them all,
you'll know all there is to know about File Tagger Catalogs.
ê'Optimization in General
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
There are two "parts" of Intellicomm: the online part, which uses your
modem to communicate with BBS's, and the offline parts such as the
File Tagger.

Overall, the best way to optimize the offline portion (and particularly the
File Tagger) is to install a disk cache on your system.  A reasonably good
disk cache called "SMARTDrive" (SMARTDRV.EXE) is included with both MS-DOS
and Windows, and you should make use of it if you have it.	There are also
shareware disk caches available (HyperDisk; probably the best cache on the
market) which you can download from your BBS, and several retail disk
caches (Norton, PC Tools, etc).  Installing *any* disk cache, and giving it
and adequate amount of memory to work with (1 megabyte or more) will speed
up virtually all aspects of Intellicomm -- usually quite dramatically.

Program Overlays
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If you have more than 1 megabyte of total memory on your system, you should
make sure you have installed HIMEM.SYS and EMM386.EXE (if running a 386 or
better), or an equivalent program such as QEMM, or 386 TO THE MAX.  With
adequate *free* high memory available (about 200K or so), Intellicomm can
load its most frequently used "overlays" into high memory, avoiding disk
read delays when changing program areas.  If you notice delays when moving
from one area of Intellicomm to another, it's due to the fact that the area
you're entering is stored in an overlay (it isn't loaded into memory until
it's needed).	You can virtually eliminate these delays by making some EMS
(expanded memory) or XMS (extended memory) available with HIMEM.SYS and
EMM386.EXE (see your DOS reference manual for details) and making sure that
this setting on the main setup "General Settings" screen is set up to use
the proper type of memory:

	║ Put Overlays in XMS/EMS . Either 					    ║

Setting it to "Either" causes Icom to first check for EMS, and to use it if
enough *free* EMS is available, and then to check for free XMS.

Communications
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Optimizing communications is an art rather than a science.	But 
optimization begins with an understanding of how Intellicomm works with
both your computer and modem, and unfortunately there is very little
Intellicomm itself can do to optimize your system for communications.

Your modem is largely irrelevant to a communications program.  Icom never
does anything with your modem that you couldn't do right from terminal mode
(entering "AT" commands, usually to get the modem to dial or to hang up). 
Where the COM port ends, Intellicomm's control ends since communications
programs deal with the computer and the COM port, and not the modem.	The
modem retrieves data from the COM port (put there by Intellicomm) and where
it goes from there is completely unknown to Intellicomm.  Similarly, the
modem puts characters IN the COM port, and where they go from there, the
modem has no idea.

The COM ports on most IBM compatibles are capable of holding only a
*single* character.  The modem places one character (from the BBS) in the
COM port, and the COM port hardware, seeing the new character from the
modem (from anything; the port has no idea that a "modem" is hooked up),
sends an "interrupt" to your computer's processor.  When the processor sees
this interrupt, it turns control over to Intellicomm's "interrupt handler"
(which is installed by Intellicomm), and Icom's interrupt handler then
grabs the character sitting in the COM port, and sticks it in an internal
buffer until a higher level of Intellicomm (perhaps the terminal mode
display, or a protocol) has a chance to process the character.  The "higher
levels" of Intellicomm (as opposed to its interrupt handler described
above) look in the Receive Buffer for new data from the modem.  The size of
this buffer is defined in the Icom main setup, on the "Terminal Settings"
screen:

	║ Receive Buffer Size [K] . 4 						    ║

If/when the receive buffer gets to about 75% full, Icom's interrupt handler
activates "Flow Control" to tell the modem to stop sending data.  Flow
control is quite simple, and can be thought of as a traffic light.  When
the light turns red (when Icom's interrupt handler sets it to red), the
modem stops sending data to the COM port.  After Icom gets a chance to
empty the receive buffer down to about 50% full (as it has time to either
display the information on the screen, or copy it to the "block" buffer if
downloading), the interrupt handler turns the light to "green" again, and
the modem starts sending characters to the COM port again.	Obviously, the
larger the "Receive Buffer" is, the less likelihood there is that the
interrupt handler will have to stop traffic with flow control.  So
increasing the size of the buffer above is one way to optimize your
communications.

Keep in mind that Icom's interrupt handler is run BY THE PROCESSOR.  Icom
has no control over when its interrupt handler is executed, and once the
interrupt handler is installed, communications is driven by the *hardware*. 
If the processor is too busy to turn control over to Icom's interrupt
handler, and if the modem sends another character to the COM port before
the interrupt handler has removed the previous character, the previous
character is lost.	And this is sometimes what causes "Bad CRC" errors on
file transfers:  The processor was too busy doing something else, and it
didn't turn control over to Icom's interrupt handler fast enough.

Intellicomm can do nothing about this, since the processor has complete
control, and *it* decides when it's going to tell Icom about the new
character in the COM port.  But *you* can do something about it.  You can
either slow the COM port down (the baud rate), install a better COM port
chip (a buffered 16550 UART; more in a sec.), or find out what your
processor is so busy with that it can't call Icom's interrupt handler fast
enough.

The first, reducing the port speed, is the easiest.  Simply enter
Intellicomm, access the main setup "Terminal Settings" screen, and change
the "Default Port Settings".	Then, enter your BIFs and make the same
change there (each BIF holds its own port settings, to support various
settings for various BBS's).	Often, if your system is being pushed to the
maximum at a high baud rate, you'll notice no difference in speed by
dropping down to the next-slowest port speed (though you most likely WILL
notice an increase in reliability).  At higher speeds all that happens is
that flow control is activated more frequently and/or characters are lost
causing a bad CRC and perhaps 1024 characters have to be re-transmitted (if
during a download).  Your computer can only process so many COM port
interrupts per second, and setting the port speed higher isn't going to
speed up your processor, or your computer system.  It simply speeds up the
rate at which interrupts are sent from the COM port to the processor: and
if too many are sent too quickly, and the processor can't deal with them
all, you'll get a mess.

The second, installing a 16550 UART (Universal Asynchronous Receiver/
Transmitter), is probably the best way to optimize communications on your
computer.  A 16550 UART holds a *number* of characters (up to 16) from the
modem in its own internal (hardware) buffer, on the chip itself.  Only when
a certain number of characters are in this buffer (from the modem) does it
send an interrupt to the processor to get its buffer emptied.  And when the
interrupt is sent, Icom's interrupt handler grabs *all* the characters in
the port all at one time.  Thus, the overhead is reduced significantly,
since much fewer interrupts (from the 16550) are sent to the processor.  A
traditional COM port (the 8250 UART) sends an interrupt to the processor
for each and every character received.

If you do have a 16550 UART, or plan to get one installed (they are very
inexpensive, and are quite a common upgrade for anyone with a fast modem)
you can control how often it sends interrupts to the processor with this
setting, again on the main setup "Terminal Settings" screen:

	║ 16550 Receive Trigger . . 4 						    ║

Icom 'programs' the 16550 when it opens the port, telling it how often to
send interrupts when characters are received from the modem.  The above
setting would cause an interrupt every 4 characters.  This can be adjusted
all the way up to 14 characters, but that really isn't a good idea since it
gives you almost no "safety zone".  If you let 14 characters pile up in the
16550 before it sends an interrupt to the processor, only 2 more characters
can be received (16 characters maximum) before the 16550's buffer is
overrun (the modem keeps sending whether the 16550 is full or not,
unfortunately).  If the processor doesn't turn control over to Icom fast
enough -- the last character in the 16550 will be overwritten if another is
received from the modem in the meantime.  But if you set the Receive
Trigger to 8 characters, this improves efficiency, and also leaves you a
safety zone of 8 more characters, in case the processor is busy and is slow
to process an interrupt.

The third way to optimize communications is to ensure that your processor
is NOT overly busy doing other things, while you're online.  The more your
processor has to do, the less time it has to process interrupts from the
COM port.  Device drivers and TSR's (memory-resident programs) all take
their share of time from the processor, and systems like Windows and
DESQview add an artificial "layer" to DOS which also uses processor time. 
But with a program like Intellicomm that can do everything on its own with
next to no input from you, there's really no reason to be running dozens of
other programs while Intellicomm is online.	Everyone either goes out (or
sleeps) once a day, and that's when you should handle your communications
-- when you're not doing other things with your computer.  This will also
keep your telephone line free while you're awake or at home.  It may take
you a week or two to get used to it, but once you do you'll wonder how and
why you used to handle your communications any other way! 
╢Intellicomm is now executing a script.	To abort the script or to switch
into Script Debugging mode, press [Alt-Q] and select the desired item from
the control menu.

If the script was called via a BIF Response or automated job
Custom Command/Run script and you wish to abort the script WITHOUT aborting
any automated job currently running, select "Abort Script Only" from the
[Alt-Q] menu.

See also:
	Terminal
	Script Language
φIntellicomm is now executing an automated job.  To abort the job, press
[Alt-Q] and select "Abort Job/Script" from the control menu.  Once the job
(and script, if a script is also running) is aborted, Icom leaves you in
manual Terminal mode.

Alternatively, if you just want to switch to manual to handle something
online and you DON'T want to abort the automated job, press [Alt-G] to
temporarily 'G'oto Manual.  When you're finished in temporary manual mode
and want to return to automatic, FIRST get to a BBS location that Icom can
recognize (the BBS Main Menu, Message Menu, Bank Menu, or File Menu) then
press [Alt-G] again to return to automatic.

If you're having a problem with your job, pressing [Alt-W] (Show WHENs)
will show you all the BBS prompts Icom is currently tracking.  This may
help to point out prompt mismatches defined in your BIF since you can
compare the BIF prompts Icom is watching for to the current BBS prompt.  

See also:
	Troubleshooting
	Script Language
	Terminal
∞Using SND/GET lists, you can have Intellicomm transfer files WITHOUT using
the File Tagger.  A .SND list specifies files to upload, a .GET list
specifies files to download.	These lists are supported mainly for
compatibility with Icom v1.00 (which used SND/GET lists exclusively to
transfer files), and existing (and future) File Tagger replacements for
Intellicomm.  "BBSee", a File Tagger replacement by Martin Vallevand,
interfaces with Intellicomm via SND/GET lists.

To specify WHICH BBS the SND/GET list is for, you use the BIFID in the
filename:

 JOESBBS.SND	contains a list of files to upload to JOESBBS.BIF
 JOESBBS.GET	contains a list of files to download from JOESBBS.BIF

These lists must be place in the Intellicomm 'List Directory', defined on
the main setup Filenames and Paths screen.  The default for the List
Directory is \ICOM\LST.

The format for SND/GET lists is the exact same as the format of the BBS new
files listings on a particular BBS (i.e. the format defined on the BIF
"Bank/List" screen).  And this makes it rather simple to create a SND or
GET list, since all you have to do is cut filenames (and the size, date,
and full description) from .NEW files lists, and paste them onto a .GET
list to get Icom to download the files.  There is one thing you must be
careful of though: if you have Icom capture BBS new files lists from
several different conferences/forums on a BBS, a line such as this will be
placed on the .NEW files list:

/Area:2

(Where '2' is the conference/forum the files were captured from.)  If you
see such a line, you should also cut/paste *it* on the .GET list, so Icom
will know which BBS conference/forum to access to obtain the file(s) that
follow.

Here's an example/tutorial showing use of a .GET list.  The first step
would be to tell the Tagger to STOP importing .NEW files lists.	 This can
be done by shutting off "Auto Import New Files" on the main setup
File Tagger Settings screen.	If you don't do this, the Tagger will gobble
up the .NEW files lists before you get a chance to look at them.  You
should also find a tool suitable for viewing large text files (the .NEW
lists), and capable of marking text (filenames) and pasting it to another
file (the .GET list).  Vern Buerg's "LIST" program is just such a tool.

Once you obtain and install the tool, plug its startup command into "File
Viewer" item on the main setup Filenames and Paths screen.	[Icom's
internal File Viewer isn't yet suitable for this task, since it can't paste
text from one file to another.]

After you've done this, you'd run your usual job(s) to capture the .NEW
files listings (one or more jobs containing a "Get new files list" task). 
Once offline, select "Browse New BBS Files" from the Main Menu.	Since
you've disabled the File Tagger imports of new files lists in the main
setup, Icom will not call the Tagger, but will instead call the
File Manager, displaying the \ICOM\LST directory to you (where the .NEW
lists are kept).  Hilight the list of interest and select "View".

Assuming you're using Buerg's LIST program to view the file, the first
thing you'd do is locate the /Area: line, and dump that to the .GET list so
that Icom would access the proper file area.  To do so, move any /Area:
lines you run across to the very top of the display, press [Alt-M] to
"M"ark the line, then press [Alt-D] to "D"ump the line to another file. 
LIST will prompt you for a filename, and here you'll enter BIFID.GET ...
where BIFID is the same as the base filename of the .NEW list you're
browsing.  LIST then writes the line to the .GET list.

Next, just browse the list using the usual cursor keys to move around.  If
you see a file you want to download, again move it to the very top line and
press [Alt-M] to mark the line.  If the file has multiple description
lines, move the LAST description line to the top of the display and press
[Alt-M] again (this marks all the lines between the two [Alt-M]s.  Press
[Alt-U] to "U"nmark, if you make a mistake).  Once you have the line(s)
marked, this time press [Alt-O] to dump the line to the SAME filename (the
same .GET list), instead of using [Alt-D].

It sounds more involved than it really is.  On the FIRST paste to the GET
list [Alt-M] marks the line, [Alt-D] 'dumps' it, prompting you for the
filename to dump to.  AFTER the first paste, [Alt-M] marks the line(s), and
[Alt-O] pastes the marked line(s) to the same filename.  It's easy.

Once you're finished with the list, press [Esc] to exit LIST, then "Delete"
the .NEW list if you like.  Next, just Run a job that contains the
following (at minimum... it's fine if it contains other job tasks):

 Call <Proper BIF>
   Download tagged files

...where <Proper BIF> is the BIF you originally used to get the .NEW list
(i.e. the same BIFID as the .GET list).  Once you Run the job, Icom will
find the .GET list, and will automatically import all the files on it into
the proper Tagger catalog, tagging all the files while importing.  The .GET
list will then be renamed to BIFID.GBK (GBK for "Get list BacKup, in case
something goes wrong).

The auto-download then proceeds as usual, and all successfully downloaded
files are flagged as "Deleted" in the catalog (the catalog is just a
temporary holding area where Icom keeps the files its auto-downloading). 
The import to a Tagger catalog also serves to (a) clean up the file
description (the Replace Keywords and Strip Comment Keywords are the only
keywords applied when importing GET lists); (b) eliminate duplicate
occurrences of the same file on the same .GET list; (c) eliminate files
you've already downloaded (if "Use DOWNLOAD.NDX" is on, on the
File Tagger Settings screen).

SND lists work in the exact same way (but with an "Upload tagged files"
task in the job; and the DOWNLOAD.NDX is not applies, since you obviously
have already downloaded the file).  They go in the same 'List Directory',
and they also must use the same BIFID.	If you want to upload the same file
to multiple BBS's, you can place the same file on multiple .SND lists. 
When you Run your job, Icom will import the files into the FILELIST catalog
(renaming each .SND list to BIFID.SBK), and will add an "Upload Pending" to
the file for the BIFID used by the .SND list.  If the same file is found on
another .SND list, the Tagger simply adds the new BIFID to the "Upload
Pending" string (meaning the file will be uploaded to more than one BBS;
but it's only uploaded when the proper "Upload tagged files" job is
executed, matching each BIFID).

NOTE: You should not attempt to MANUALLY import a SND or GET list into a
Tagger Catalog, if you want all the files to be automatically Tagged.  If
you manually import one of these lists the import will work fine, but the
files will not be automatically Tagged for you as they are when you Run a
job that contains an Upload/Download tagged files task.
⌐Intellicomm's dialer, combined with special scripts, can dial and log you
on and off of just about any long distance service.  Pre-programmed scripts
and special BIF setup items to accomplish this have been included for PC
Pursuit, and iNet 2000.

This help link provides you with step-by-step instructions to set
Intellicomm up for any of these services and will also give you an idea how
to set up for a 'Custom' service, if you want to add support for a new Long
Distance service yourself.  If you plan to write your own custom scripts to
log through some other LD Service, you should review the logon/logoff
scripts provided with Intellicomm to get an idea what is needed.  Using
Script Learn you should be able to create logon/logoff scripts for any long
distance service, quite effortlessly.

You might want to print this help link before continuing to avoid having to
enter and exit the help system as we go along.  To do so, get your printer
turned on and loaded with paper, then press [Alt-P].  See
Printing Problems if you run into a problem.

LD Services, Global Setup
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The "global setup" items are configured once, for any LD service, and can
then be forgotten.	Global setup consists of entering the LD service's
phone number in the Icom main setup, then entering your User ID and
password in the appropriate logon script.  Simple stuff that takes longer
to explain that it does to actually do it.  

To begin, select "Intellicomm Setup" from the Icom main menu, then select 
the "Dialer Settings" screen.  From there, press [] (Up Arrow) to hilight
"LD Service Phone Num", then enter the local in-dial number for the service
you're setting up for and press [Enter].  Press [Esc] twice, then press
[Enter] again to save the changes to disk.

Next, select "Script Manager" from the main menu, and hilight either PCP-
ON.SCR for PC Pursuit, or INET-ON.SCR for iNet, then select "Edit".

Once in the editor enter the proper information in the 'variables' at the
top of the script (use the cursor keys to move around ... press [F1] again
for help once in the Text Editor if you get stuck).  Press [Esc] when done,
and answer "Yes" when asked whether to save the changes to disk.

That's it for the global setup.  Press [Alt-D] now to change to the BBS
Directory for the BIF setup.

LD Services, BIF Setup
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Each BIF that you want to dial through the LD Service must be configured
using the steps below.

First, hilight the BIF you're interested in, and select "Edit" (or hilight
the proper template and select "Create" if setting up a new BIF).  Enter
the BBS PHONE NUMBER in the first "Phone Number" item for PC Pursuit, or
enter the INET ADDRESS of the BBS for iNet.	For PC Pursuit you might enter 
555-1234 or 1-555-1234.	The number you enter here will follow the ATDT
command sent to the remote modem.	For iNet you might enter A CRS GA to
access a certain BBS through Gateway.

Next, change the Port Settings if necessary.  Most LD services require Even
parity, and 7 data bits (e.g. 2400,E,7,1).

Next, press the right arrow key to change columns, then hilight "LD
Service" select "Edit" and pick the proper service from the menu by
hilighting it and pressing [Enter].  After making your selection you should
then see the name of the logon script (which you modified above) preceded
by a '@', in the 'Connect Command' item (e.g. @PCP-ON).  This causes
Intellicomm to run the logon script after connecting, rather than entering
its internal (BBS) logon routines right away.

Next, Edit the "City/Address" item, and enter either the PC Pursuit 'city'
where the BBS is located, or the Datapac address to iNet.  For example, to
access a BBS in New York via PC Pursuit, you'd enter NYNYO, and nothing
else (the D/ part of the command is contained in the script).

That's it for the long-distance service setup.  Of course, be sure to enter
the usual BBS-related information, (i.e. the items with an arrow following
their descriptions), on the other screens.

When you're finished, eXit and save the BIF by typing in a filename.	It
can then be tagged/dialed and used in automated jobs just as any other BIF
is used!	Please make sure you TEST EVERYTHING CAREFULLY before leaving
Intellicomm unattended.	This is particularly important when long-distance
fees are involved.

You can use BIF Learn with this BIF to set it up for the BBS Logon, Message
Transfer, File Downloads, etc., if you like.  Just pick "Modify an Existing
BIF" when you activate BIF Learn.
F	The Control Menu is activated by pressing [Alt-Q], but only when and
automated job or script is running.  If you press [Alt-Q] in manual mode,
the Learn Modes menu is displayed.

Abort Job/Script, switch to manual
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Selecting this option aborts the automated job, and leaves you online in
manual Terminal mode.  If a script is running (if called via a BIF
@SCRIPTNAME command or a job Custom Command/Run script task) the script is
also aborted.

TIP: To simply switch to manual mode for a temporarily WITHOUT aborting the
automated job, use [Alt-G] (Goto Manual) instead of [Alt-Q].  When you're
ready to return to automatic mode, press [Alt-G] again.

Abort Script Only [if script running]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Selecting this option exits the script processor entirely (meaning that
even if the currently running script was called by ANOTHER scripts, *all*
scripts are aborted), and returns either to manual mode, or back to the
automated job.  For example if the job executed a Custom Command/Run script
task, with a @SCRIPTNAME defined as the Custom Command, 'Abort Script Only'
this would abort the script and flag the Custom Command task as "done" but
would NOT cancel the rest of the job.  Any job task following the Custom
Command would then be carried out.  Use Abort Job/Script (above) to abort
BOTH the script (Custom Command) and the automated job, and switch to
manual mode.

Script DEBUG [Step-by-step]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If a script is currently running, selecting this option turns step-by-step
debugging on.	This means that each script line is displayed on the screen
and waits for you to press a key prior to execution, allowing you to follow
along and trace bugs in the script.  See Script Debugging for more
information.

Script DEBUG [Animate]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If a script is currently running, selecting this option turns animate
debugging on.	This means that each script line is displayed on the screen
momentarily (2 lines per second, without your having to press a key to
execute each line), allowing you to follow along and trace bugs in the
script.  See Script Debugging for more information.

Script DEBUG [OFF]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
If either of the above script debug modes is on, selecting this option
turns off debugging and commences running the script at full speed.
~A 'Message Packet Filename' is the filename a given BBS message system uses
for its mail packets.  If the mail system is Qmail-compatible, the packet
filename will have a file extension of ".QWK".  If the mail system sends
text files, the extension may be ".TXT", etc.

Normally the base portion of the filename is an abbreviation of the BBS
itself.  For example, on the Intellicomm Online Service, the Message Packet
Filename is ICOM.QWK.

ONLY enter the Message Packet Filename now if you have already downloaded
or captured mail from the BBS, and you know the packet filename.  If you
don't know the packet filename, just press [Esc].
┘#"Transfer Priorities" cause TAGGED files to sort differently when using the
"Tag Status/Location" sort order.	This is the sort order or 'index' that
Intellicomm uses to automatically upload/download Tagged files.	By setting
Transfer Priorities, and optionally a Transfer Day, you have total control
over when Intellicomm transfers files.

Noted files also have priorities when they're noted automatically on
imports through a match in the Note File Keywords list.  In this case, the
priority the Noted file receives is the line number from your Note File
Keyword list, on which the keyword match was found (priority 1 if the match
was on line 1, 2 if on line 2, etc).

Using Transfer Priorities
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Setting Transfer Priorities is optional.  If you aren't concerned with the
order in which Intellicomm transfers files, you needn't set Transfer
Priorities at all, and can simply Tag files and run your "Download tagged
files" jobs as usual.  Icom will download files sorted by filename, leaving
the files you don't have time to transfer Tagged for the next session.

However, if you want more control (transferring the most interesting files
first, or leaving large or less interesting files until last), Transfer
Priorities are for you.	The recommended way to handle Priorities is to
refrain from setting them until you've gone through ALL of the new files in
the catalog using the sort order you prefer, and have already Tagged
everything you wish to upload or download.  Once you've done that, then
select "Sort" from the bottom menu and switch to the Tag Status/Location
sort order to see all the Tagged files grouped together, just as Icom will
transfer them.  Then, browse through the tagged files to set your
priorities.  

Transfer Priorities range from 1 (the MOST desirable files; as in 'priority
one') to 200 (the LEAST desirable files).  When you Tag a file, the
priority is automatically set to 100 -- initially giving all tagged files a
"mediocre" priority.  This allows you to go through and pick out the files
you want right away (set the priorities anywhere below 100) as well as
picking out the very large files you DON'T want until everything else is
transferred (set the priorities anywhere above 100).

So when a particularly interesting Tagged file is hilighted, select
"Priority" then press the [] cursor key (or the [-] minus key) to move the
priority DOWNWARDS from 100 (the default Tagged priority is 100) towards 1. 
You should leave room on both sides when you set priorities, so you can
later insert files on either side; Priority 50, for example, might be a
good value for your first Priority since it lets you set the next file
either to 40 or 60, depending on how much you want it.  If you used
Priority 1 on the first interesting file, priority 2 on the second ... then
you saw a file you wanted more than EITHER of the priority 1/2 files, you'd
have to go back and re-adjust.  By using increments of 5 or 10, you should
always have room to insert files into the priority scheme, exactly where
you want them.
 
When you find files that you DON'T want to download immediately, again
select "Priority" but this time press the [] cursor key (or [+]) to move
the priority UPWARDS towards 200.	Priority 200 files are transferred LAST.

Before going further, it will be helpful to know that the Tag
Status/Location sort order, the index Intellicomm uses to transfer Tagged
files, sorts in this manner:

1st grouping: Tag Status
2nd grouping: Location (BIF ID; where the file exists)
3rd grouping: Transfer Priority
4th grouping: File Area (conference on the BBS)
5th grouping: Filename.

I.e. all the Tagged files are grouped together.  The tagged files are
further subgrouped by BBS, THEN the transfer priority takes effect and
further subgroups (re-sorts) from there.  Here's an example of how the Tag
Status/Location sort order works, given various values in different catalog
records (T = a Tagged file, U = an Untagged file):

	Tag Status  Location  Priority  File Area   Filename
	────────────────────────────────────────────────────
	   T 	   BIF-1	    10		 0	   AFILE.ZIP
	   T 	   BIF-1	    10		 2	   AFILE.ZIP
	   T 	   BIF-1	    10		 2	   BFILE.ZIP
	   T 	   BIF-1	   100		 0	   AFILE.ZIP
	   T 	   BIF-1	   150		 2	   AFILE.ZIP
	   T 	   BIF-2	    10		 0	   AFILE.ZIP
	   T 	   BIF-2	    50		 0	   AFILE.ZIP
	   T 	   BIF-2	   100		 0	   AFILE.ZIP
	   U 	   BIF-1	   100		 0	   AFILE.ZIP
	   U 	   BIF-1	   100		 0	   BFILE.ZIP
	   U 	   BIF-2	   100		 0	   AFILE.ZIP
	   U 	   BIF-2	   100		 1	   AFILE.ZIP

To understand this, first look at the Tag Status field and notice that all
the Tagged records (files) are grouped together -- Tagged before Untagged. 
Tag status takes top priority over all other items.  Then look at the
Location field and notice that the files are further subgrouped by BBS,
AFTER the Tag Status field has done its initial grouping.  Then the
Priority field comes into play, though only WITHIN the further subgroup of
each BBS.  Then the conference/File Area is taken into consideration,
though again only AFTER the subgroup of Priorities (in other words the
conference makes no difference unless files have the SAME priority).	And
finally if everything is equal right up to the File Area, the deciding
factor is the Filename.

Thus, do not be alarmed if you set Priority 1 for a given file, and it
doesn't sort to the very top of the catalog.  It will sort to the top only
within the subgroup of the BBS/Location where the file exists.  Also do not
be alarmed if Intellicomm jumps from conference to conference to obtain the
Tagged files, when running your Download Tagged Files jobs.  It will have
done so only because you gave it no choice, due to the order of the
Transfer Priorities you set (which take precedence over conference).
 
EXAMPLE
▀▀▀▀▀▀▀

 ■	You've tagged all the files you wish to transfer, and have switched to
	the Tag Status/Location sort order.

 ■	You're browsing through the Tagged files, and you find an interesting
	file you want to download before the others.  You set the Priority to
	50, which re-sorts the file to the top of the Tagged list (keeping the
	discussion above in mind, regarding subgroups).

 ■	You then find another Tagged file which you want to download before
	the others... but it's not as important as the priority 50 file.  You
	set that one to priority 70, and the file moves just below the
	priority 50 file, regardless of the BBS conference the file exists in. 
	Files with a lower priority number ALWAYS sort towards the top,
	regardless of the BBS conference.	The BBS conference only comes into
	play when files have an EQUAL priority level.

 ■	You then see a file you want even MORE than the priority 50 file...
	and you set that one to priority 30.  It moves to the top of the
	Tagged list, before the priority 50 file.

 ■	Then you run across a very large file that you know will use all of
	your online time if Icom transfers it.	The file isn't THAT important,
	so you give it a Priority of 150.	It moves to the very end of the
	list, after all other Tagged files.

 ■	You find another large file that you don't want right away... You
	decide that you want it more than the priority 150 file though, so you
	give that one a priority of 130.  The file moves to the end of the
	list, just before the priority 150 file.

You needn't go in increments of 10, and you can enter priorities
specifically (1, 12, 139, 177, etc) but it's easier to group them by 10, as
it allows you to insert files later, between, say priority 10 and 20, if
need be.

It's also important to understand that two or more files can have the SAME
priority.  If you want several files, and don't care which ONE of them is
first or last (i.e. you know you have time for them all) you could just set
the whole group to Priority 90 (one press of the [-] key from the Priority
menu) to have them transferred before others (the default priority of 100).

Transfer Day
▀▀▀▀▀▀▀▀▀▀▀▀
On rare occasions, Transfer Priorities may not provide you with enough
control.	When this is the case, you can also set a "Transfer Day" to have
Intellicomm wait until a specific DAY of the week before transferring the
file.  To set a Transfer Day, hilight the file and select "Edit".  Then
press [Down] arrow twice from Edit Mode to move to the Transfer Day field
and enter a number from 1 to 7 to specify the day on which day to transfer
the file.  You must make sure that you run your job on that day, however,
or the file will not be transferred until the following week.  If you use
the Transfer Day feature, you should be in the habit of running your
"Download tagged files" jobs every day, or having a program launcher do it
for you by using the /run: command line switch.

Noted File Priorities
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The only advantage to manually setting Noted File Priorities (i.e.
selecting "Priority" when a Noted file is hilighted), is that it allows you
to group Noted files together when using the Tag Status/Location sort
order, which groups all Noted files above Tagged files, grouped in the same
manner as Tagged files.	Noted file priorities have no other effect.
A "Transfer Day" can be set for tagged files, allowing you to force
Intellicomm to wait for a specific day of the week before transferring a
given file.  Select "Priority" from browse mode to set a Transfer Day:
Tagger will first prompt for the priority (see Transfer Priorities) and
will then prompt for a day of the week to transfer the file.  Press [Enter]
on "Anyday" to allow Intellicomm to transfer the file on any day of the
week.  Or, select a specific day, and Intellicomm will only attempt to
download the file on that day.  If you do set Transfer Days, you'll have to
make sure that you run your Download tagged files job(s) every day of the
week; preferably automatically through a program launcher, or "Repeat job
at HH:MM on Everyday" task (can be set in the Job Editor).
"When you Delete jobs and BIFs in the Job Directory and BBS Directory, they
are not physically removed from disk until you execute a "Pack" when
exiting Intellicomm.  Delete jobs and BIFs are displayed with brackets
around their descriptions, and you can UNDELETE these jobs/BIFs if
necessary, by simply hilighting the item and selecting "Delete" again from
the bottom menu (it operates as a toggle to delete/undelete).  To
physically remove these jobs/BIFs from disk, press [Alt-X] to exit
Intellicomm, then select "Pack" from the exit menu.
▄Archive Viewers are programs that allow you to view and otherwise maintain
the contents of the various types of archives commonly used on BBS's (.ZIP,
.ARJ, .LHA files).	Many archive viewers are available for download on most
BBS's and Intellicomm will operates with any DOS-based external Archive
Viewer.

Once you select an archive viewer, simply enter the command you normally
use to start the viewer in the "Arc. Viewer" item on the Icom main setup
"Filenames and Paths" screen.

Intellicomm will then call the external archive viewer when you "View" or
"Edit" an archive in the File Tagger, File Manager, or Script Manager.
You can also call your external archive viewer from anywhere in Intellicomm
by pressing [Alt-V].
»PKZIP by Phil Katz is a popular compression program used to compress files
before uploading them to BBS's.  It is also normally used to compress mail
packets (.QWK packets from Qmail-compatible mail systems for example).

You can usually identify files compressed with PKZIP by looking at the file
extension: .ZIP signifies a PKZIP-compressed file.  But this is not always
the case, as many mail systems do compress the mail packet using PKZIP, and
then simply rename the file before sending it to you (.QWK packets, as
mentioned above, are usually compressed with PKZIP).

To uncompress these files, the PKUNZIP program is used.  Both PKZIP and
PKUNZIP are available at most all BBS's.
