IHLP1
αIntellicomm Add-ons┼Add-on IdeasYMultitasking Intellicommy'WindowsrIWindows Setup╙[DESQviewì^OS/2π
The following is a list of some of the useful add-ons for Intellicomm.  If
you develop a useful add-on you'd like to have included to this list,
please see Add-on Ideas for our address.  If you require information
(technical or otherwise) on producing an add-on for Intellicomm please see
TECHNICAL SUPPORT for information on contacting us.

Useful Intellicomm Add-Ons
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

FILES	 : BBSEE30A, BBSEE30B  (.ZIP or other)
DEVELOPER  : Martin Vallevand
DESCRIPTION: BBSee (pronounced BB-See) is a feature-rich file catalog disk
system integrated with a BBS file list manager. BBSee's unique BBS file
list manager can be used as a replacement for Icom's Tagger with the
advantage of much faster speed for description searches, a much smaller
database, and a direct link to the disk catalog database to avoid duplicate
downloads.  Other features including a new version report, BBS cross
reference report, direct support for the monthly Hack report, FILE_ID.DIZ
extraction and support for many more BBS file list imports, make BBSee and
invaluable program for Intellicomm users.

FILES	 : BCALCST3.ZIP
DEVELOPER  : John Leaver-Power
DESCRIPTION: Script file for Icom deposits all unused time in PCBoard BANK 
door, less 10 minutes for next session on the same day.  Useful for
building up your account total without sacrificing your ability to logon
again on the same day.  Captures your account stats to ICOM.CAP for offline 
review.

FILES	 : ICOMBLT7.ZIP
DEVELOPER  : John Leaver-Power
DESCRIPTION: Program for Icom which captures specified bulletins from
PCBoard for offline reading.	Captures both Main and Conf. specific		
bulletins whenever they are updated by PCBoard.  Can be used with any
offline reader/utility that supports bulletins in standard format.  Allows
users of the offline reader PMDBM to change bulletin monitor list from
within PMDBM.	Restricted to users of one BBS.  (If using more than one
BBS, I recommend using a similar program by Michael Livsey.)

FILES	 : MAILMSG3.ZIP
DEVELOPER  : John Leaver-Power
DESCRIPTION: Personal mail reminder for Icom.  Records logon notices, ie
"you have personal mail waiting in the following conferences", to a text
file, and runs screen saver with moving text box reminder after logoff
whenever logon notices are displayed by PCBoard, or when the just
downloaded QWK packet contains personal mail.  Screen saver designed for
standard 25 x 80 color mode, and can be set to run a) indefinitely, b) for
a specified number of hours & minutes, or c) until a specified time of the
day.

FILES	 : NFICOM7.ZIP
DEVELOPER  : John Leaver-Power
DESCRIPTION: Batch file for using Icom's TAGGER from within the offline
reader PMDBM; ie when selecting "List New Files" from within the reader.

See also:
	Add-on Ideas
ÆThe following are some ideas for new add-ons.  We'll eventually produce
some of the add-ons below, but with Windows and OS/2 versions of Icom to
worry about, we'd rather one of you clever Icom'ers beat us to it first!  

  ■	More advanced PC-Pursuit logon/logoff scripts.  It will be difficult
	to expand these in Canada, since there is no PC Pursuit up here to
	test with (I've never used it, and wrote the scripts through heresay
	and what PC Pursuit documentation I could find).	Hopefully an avid PC
	Pursuiter can come up with some better logon/logoff scripts now that
	the script language has been expanded.

  ■	Logon/logoff scripts for other long-distance services around the
	world.

  ■	BIF templates for BBS types not included with this release of
	Intellicomm are always great.

  ■	File Tagger add-ons to provide useful functions (script or .EXE). 
	Everything I've seen as far as BBS usage indicates that MOST (70% or
	more) people on BBS's spend MOST of their time with files and never
	bother with mail at all.  So why are there so many QWK mail readers,
	for so few people... and so few File Taggers for so MANY people?  The
	situation should be reversed.

  ■	Conversion utilities to convert ProComm, Qmodem or Telix setups to
	Icom format (would provide a trivial Icom setup at best with the
	sparse information in the regular dialing directories... but it would
	give people a start).  Robocomm to Icom conversion would be much
	easier, and would also be very useful.

  ■	SCRIPT conversion utilities to convert ProComm (DOS), Qmodem, and/or
	Telix scripts to Intellicomm scripts.  Icom's script language was
	compared to all of the previously mentioned script languages when it
	was developed, and script conversion from any of these languages (and
	perhaps others) IS possible.	Telix's SALT language would be the most
	challenging, but Icom does have more functions than Telix SALT and it
	includes everything SALT does (Icom scripts just do things in a
	different manner; but all the functionality is there).  Conversion
	from ProComm and/or Qmodem script format should be fairly
	straightforward, since Icom's script language contains almost
	identical script commands.  With a conversion utility available for
	any one of the three comm. packages mentioned above, the Intellicomm
	script market would quickly burst at the seams.
 
If you produce a useful add-on for Intellicomm and would like to have it
included in the Intellicomm Add-ons help link, please send a copy of your
product on-disk to:

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

Make sure you include all the necessary information, such as online
filename (.ZIP name), developer name, price, and a short description of the
product.	If you're expecting to release an update in the near future, also
send the .ZIP name you'll be using for the update and (if possible) make an
estimate as to when the update will be available.
Intellicomm is DESQview, Windows v3.x and OS/2 v2.x aware, and is known to
operate well under all of these systems, even at high speed.  When
Intellicomm is idle and not using the COM port, it will give its "time
slice" back to any of the above multitaskers, making your whole system run
smoother while Intellicomm is running in the background!  While online,
Intellicomm, by default, does NOT give its time slices back.  You can
change this on the Icom main setup / General Settings screen by setting
"Release Time Slices" to YES.  If you experience problems such as missing
characters and file transfer errors, however, you must set this item back
to NO.

Intellicomm also obtains a video buffer from DESQview, allowing direct
screen writes to the video buffer DV assigns.  Specific setup information
for all of the above systems can be found at the bottom of this help topic,
but please read it through before you get started.

The advantage of running Intellicomm under Windows or OS/2 -- even as
opposed to a 'real' Windows or OS/2 application, is that since Icom does
everything itself, you gain the convenience of simply setting up an icon,
clicking on it, and forgetting about the gory online details.  (See
Command Line Options and particularly the /Run: switch, for details.)  Icom
does all the work in the background and your mail and files simply "show
up".  By using an "Exit to DOS" task at the end of your job, you can even
have Icom automatically remove itself from memory when it's done!  With
ProComm+ for Windows and most other Windows and OS/2 communications
packages, you'll have to spend hours and hours writing scripts: and you
still won't get anywhere near the functionality of Intellicomm with its
File Tagger, flexibility of automation, and particularly its error-handling
on lost connections, etc.  ProComm+ for Windows and other GUI comm.
packages may look "prettier" than Intellicomm; but given the fact that
you'll rarely have to even SEE Intellicomm, which would you rather deal
with!?  Native Windows and OS/2 comm. programs may look nicer, but they
make YOU do all the work, and they provide nowhere near the funcionality
and convenience of Intellicomm.

The best way to run Intellicomm, even under a multitasker, is to obtain a
"program launcher" for your multitasker (a scheduler program that can run
programs for you automatically at certain times each day; there are many
shareware program launchers available on BBS's), and to have the program
launcher run Intellicomm to call all the BBS's you normally call, at some
point in the day (or night) when your system is quiet and you're not
working with other tasks in the foreground.

The way IBM PC's work, and particularly the way UART's work (the COM port),
no matter *which* communications program you're using, you can get dropped
characters and "Bad CRC" errors on file transfers, if you push your system
too hard.  And unfortunately there is nothing Icom can do to prevent it;
characters are usually dropped by the HARDWARE, because it couldn't keep
up, before any software even knows what happened.  At 38400 baud, your COM
port [UART] may send over *3,000* interrupts to your processor, every
SECOND.  If your processor is busy doing other things (drawing graphics on
the screen and processing mouse/keyboard interrupts for example), dropped
characters can result even with the fastest computers.  And both Windows
and OS/2 give DOS communications programs an even further handicap by
"virtualizing" (basically duplicating) the COM port interrupts.

Following the tips in the Optimizing Intellicomm link can help, but the
ultimate solution to this problem, particularly given Icom's unique
automation abilities, is to carry out the bulk of your online sessions when
your system is quiet, and when your computer has ample time to process all
the COM port interrupts.  It's not absolutely "necessary" that you do this,
particularly if you have a fast computer; it just makes more sense to do it
this way, particularly if you run into communications problems.

Which system are you interested in:

	DESQview
	OS/2
	Windows
≈!There are two Windows help topics.  This first one covers the basics,
assuming that you already have Windows set up for reliable communications,
while Windows Setup covers Windows setup issues in particular.

Microsoft Windows 3.1
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
First, to those who wonder whether a Windows version of Intellicomm can be
expected the answer is yes (as to when, we have no valid estimate as yet).
Unfortunately developing a Windows application is a rather long and
involved process, so we're going to make you a deal.  If you support the
cause by registering the DOS version of Intellicomm (which works fine under
Windows 3.1 if you follow the tips below) we will guarantee that (a) you
will see a Windows version of Intellicomm as very soon as we're able to get
it ready, and (b) you will be able to purchase it for $15 or less (or
possibly for free)!  I.e. previously registered users of Intellicomm for
DOS will be able to upgrade to Intellicomm for Windows, directly through
Liberation Enterprises (and perhaps through dealers if we can arrange it),
for $15, or maybe $10, or maybe $5, or maybe for nothing.  We'll have to
check our bank account at the time of the release and see how much money we
have available.  If we're broke, you'll pay $15.	If we have some modest
amount of money in the bank, you'll pay $10 or $5.  If we have ample funds
by that time, you'll get it for nothing, which would really be worth it for
us as well since it saves us from having to process orders and mail out
disks (your ICOM.REG key file would simply enable the registered user
features in the Windows evaluation version after you downloaded it from a
BBS... as with free updates of the DOS version).

Without your support today, we cannot possibly continue development of
Intellicomm, and if you consider $39.95 (Icom for DOS) plus $15.00 or less
($54.95 maximum), you'll still get one of the best deals ever for a Windows
communications package!

CHCOMB.ZIP
▀▀▀▀▀▀▀▀▀▀
The communications driver included with Windows 3.1 is better than the
driver that came with 3.0, but it still is far from perfect for high-speed
communications with a DOS comm. program.  If you have a high-speed modem
and an 80386 machine or better, we recommend that you check your local
BBS's for a file called CHCOMB.ZIP (or CHCOMB.LHA, CHCOMB.ARJ, etc).	This
driver for Windows, produced by Cherry Hill Software, is free (with a
suggested donation of $10) and has been tested and recommended by several
Intellicomm users for high speed communications under Windows.

Setting up for Windows 3.1
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Setting up Intellicomm to run with Windows 3.1 is usually very easy.	Start
by copying ICOM.PIF (included with Intellicomm) into a directory on your
DOS PATH.  The \WINDOWS directory will do fine.  Then start Windows and
open the PIF Editor just to double-check a couple of things (the PIF Editor
is in the "Main" group, or the "Accessories" group if you upgraded from
Windows v3.0).

Once in the PIF Editor, open the File menu, select Open... then enter
ICOM.PIF in the dialog box.

Now just double-check that the proper "Program Filename" and "Start-up
Directory" items are defined properly.	If you installed Intellicomm on
another drive or in another directory (or have renamed ICOM.EXE) please
change these items to suit.  Nothing else should require modification here.

If you're using a fairly slow modem (2400 or below) you can probably get
away with lower "Foreground/Background Priority" than the 200 defined in
this PIF ("Advanced..." settings).

Save the PIF when you're done, then exit the PIF Editor.

Next you'll need an icon to run Icom.  To set that up, open the group you
want to place Intellicomm in (Applications, etc.) open the "File" menu,
select "New..." then OK.  Enter the following in the Properties
box:

   Description:	   Intellicomm
   Command Line:	   ICOM.PIF
   Working Directory:  
   Shortcut Key:	   None	(defined in the PIF, Alt+Ctrl+I)
				  
Don't enable the Run Minimized box.  Then select "Change Icon" and enter
PROGMAN.EXE as the File Name in the Change Icon box.  Browse through the
icons and select one you like, or if you don't like any of them go back to
the File Name box and enter MORICONS.DLL (Microsoft supplies a number of
icons in this file).  Select OK twice, then double click on the new icon to
start Intellicomm.

From Icom, select "Terminal" and type a few commands to ensure that your
modem is responding (normally if you enter AT, your modem will respond with
"OK").  If your modem doesn't respond, the first step is to make sure it's
plugged in properly (check the cables).  If so, the next step is to check
that you have Intellicomm set up to use the proper port: press [Alt-P] from
Icom's Terminal mode to check this out.  If everything checks out, and
you're sure the modem is operational (i.e. if Windows' Terminal works),
please see Windows Setup.

Windows TIPS for Intellicomm v2.0
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Using Windows 3.1 you may set up program items in the Program Manager to
run Intellicomm jobs in the background with absolutely no manual work on
your part, save for double-clicking an icon.  If you obtain a Windows
"Program Launcher" type of program (which start programs for you
automatically at a given day/time) you needn't even double-click... you can
simply have the launcher do it for you (you can also do this by keeping
Intellicomm running in the background constantly, using a "Repeat job"
task, but it's much more efficient to use a program launcher).

After following the setup tips below, you will simply double-click an icon
and Icom will start, tag whatever jobs you want, and reduce to an icon
where it will run the desired jobs in the background with no intervention. 
When everything is finished, Intellicomm will then automatically remove
itself from memory and the bottom icon will disappear.  You'll have even
the ProComm for Windows users envious of you!

Setting this up requires two things:

 1. A proper search string to use in a -Run: command line option.
 2. A new program item in a Program Manager group.

1. The -Run switch:  Intellicomm accepts a command line option that allows
you to Tag then Run a series of jobs using a search string.  The command
line option uses the format -Run:"Search String".  [The double quotes must
be used to keep search strings that contain SPACES together.]  All jobs
matching the search string are Tagged then Run.

To test various search strings to use in -Run: command line options,
start Intellicomm, switch to the Job Directory and use the "Find" / "Find
All/Tag All" option.  The -Run: option causes Icom to switch to the Job
Directory, do a Find All/Tag All on the search string, then to "Run" and
tagged jobs.  For example, assume you want to use a -run switch to run all
your mail jobs.  If you have three jobs called Send/Get Mail - BIFNAME, you
could try a "Find" search string of "Send/Get Mail", then select "Find
All/Tag All".	If all the jobs you wanted tagged got tagged, you're all set
and can proceed to step 2.  If not, you'll either have to adjust your
search string, or "Edit" one or more job descriptions so that only the jobs
you want tagged get tagged.  You can ALWAYS get the proper jobs tagged by
either changing your search string and/or modifying one or more job
descriptions.	Use symbols (!, #, $, etc) in various job descriptions, then
just use the symbol (/Run:!) if you get stuck.

2.  Once you have the proper search string, exit Intellicomm and enter the
Windows Program Manager to create a new program item (open the group you
want the item to appear in, then open the File menu and select New..., then
OK for a new Program Item).  In the Properties box you'll want something
like this:

 Description:		Send/Get E-Mail
 Command Line: 	ICOM.PIF -Run:"Send/Get Mail"
 Working Directory: 
 Shortcut Key: 	None
				X Run Minimized

If ICOM.PIF is not in a directory on your PATH, you should precede it with
the proper directory (e.g. C:\PIFS\ICOM.PIF -Run:...etc).  Note that the
"Run Minimized" box should be checked so that Intellicomm will be
immediately reduced to an icon to carry out the jobs in the background.

Select "Change Icon" to select an appropriate icon (a mailbox, etc.) then
click on OK when you're done.  Repeat the above for as many convenient jobs
as you desire.

From now on you can just double-click the icon you just created, and have
all your runs carried out effortlessly in the background.  Or if you pick
yourself up a program launcher, have the launcher execute the whole shot
for you each day, or on certain days, without even having to think about
it.	Isn't that what computers are for?

Enjoy!
_WINDOWS/SYSTEM SETUP
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
These tips really have little to do with Intellicomm, as all comm. programs
will run into problems under Windows, if Windows is not set up properly. 
But it's really not covered adequately in the Windows documentation so
we'll address it here.

General Tip
▀▀▀▀▀▀▀▀▀▀▀
If you experience missing characters or excessive file transfer errors, the
first, most logical step, is to prevent Intellicomm from releasing time
slices back to Windows.	Do this by entering the Icom main setup, selecting
the General Settings screen, and changing "Release Time Slices" to NO.

If that doesn't work, reduce your port speed (baud rate).  For example,
drop down from 38400 to 19200 in both Windows (see below) and Intellicomm
(both main setup AND your *BIFs*).  In most cases, even when using a 14.4K
modem, there are few advantages to running your COM PORT at 38400 baud,
under Windows. Optimizing Intellicomm discusses this in more detail.

Control Panel / PORTS
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The first stop in your Windows setup is the Control Panel.	Once open,
double-click on the "Ports" icon to configure your COM ports.  You should
see COM1, COM2, COM3, COM4 in the Ports dialog box: double click on the
port your modem is connected to.

Next, set Windows up the same way you set Icom up, with the same baud rate. 
In particular, if your modem supports Hardware Flow Control, you should
also set Windows up to use Hardware Flow Control.  If your modem doesn't
support hardware flow control, you should set the Windows Flow Control to
NONE, then set Icom up to use XON/XOFF flow control.

SYSTEM.INI
▀▀▀▀▀▀▀▀▀▀
The Windows SYSTEM.INI file holds all of the settings relevant to
communications.  Before changing this file you should always make a backup,
and store the backup in a safe place for future reference and comparison. 
Use File Manager (Windows or Icom's) or the DOS COPY command to copy your
\WINDOWS\SYSTEM.INI file to a safe place (a floppy, etc) before continuing
below.

Next, edit the SYSTEM.INI file, with NotePad or any other Text Editor and
find the [386Enh] section by paging through the file.	If you don't have a
[386Enh] section (and assuming you do HAVE a 386 computer or better), add
it just before one of the other sections.  Example:

[386Enh]

[NonWindowsApp]

Next, between the [386Enh] line and the next [Section], check for and
either modify the following settings (if the tag already exists), or add a
new line including both the tag, the equals sign, and the proper setting
(do not add the comments that begin with a semicolon):

COM1Base=03F8
COM1Irq=4
COM2Base=02F8
COM2Irq=3
COM3Base=03E8
COM3Irq=4
COM4Base=02E8
COM4Irq=3
COM1Buffer=0	 ;Please see the note below!
COM2Buffer=0
COM3Buffer=0
COM4Buffer=0
 ;Below are the settings specific to the COM port your modem is
 ; using.  You must replace the x in COMx with the actual port
 ; number (e.g. COM2AutoAssign=0).
COMxAutoAssign=0
COMxFIFO=1

IMPORTANT NOTE: If you experience communications problems when running
Intellicomm, change the COMxBuffer setting to COMxBuffer=8192 ('x' being
the port your modem is connected to: e.g. COM2Buffer=8192).  Setting it to
zero can either solve problems or CAUSE problems, depending on your system. 
Try setting it to 0 first.  If you run into problems set it to 8192,
exiting Windows between changes, to see which produces better results.

Once you check and/or add these lines, re-save SYSTEM.INI and exit the
NotePad or Text Editor.	Then exit Windows and RESET your system (use the
reset button or turn it off/on ... Pressing [Ctrl-Alt-Del] may not be
sufficient).  Then start Windows again and click on your Intellicomm icon
to see if Intellicomm is working.	If not there's one other thing you can
try before calling your dealer for help:  Temporarily remove ALL TSR's and
device drivers in your AUTOEXEC.BAT / CONFIG.SYS, re-boot, and try again. 
You may have a device driver/TSR that is stealing interrupts or otherwise
conflicting with Windows or Intellicomm.  If the problem doesn't occur with
no device drivers/TSR's loaded, you can add them back in to your
CONFIG.SYS/ AUTOEXEC.BAT one by one (re-booting each time) to locate the
culprit.	

Don't let any tech. support people tell you that a problem you're running
into is due to Intellicomm itself, unless you can execute other DOS comm.
programs without problems.  They'll just be trying to brush you off and
avoid doing their job.  Intellicomm has been tested with Windows on many
different systems and it DOES work just fine as long as Windows, your
system (AUTOEXEC.BAT, CONFIG.SYS.. the possible TSR conflicts mentioned
above) and Intellicomm are set up properly.

See also:
	Windows
╕Quarterdeck DESQview
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Start by copying IN-PIF.DVP (included with Intellicomm) to the directory
that ICOM.EXE is located in (\ICOM by default), then start DESQview.

If not at the "Open Window" menu, press O.

From the Open Window menu, type AP (Add Program), then press O (Other).

Enter the directory you copied IN-PIF.DVP to (\ICOM normally) when asked
for the path of the program to add, then press [Enter].

Select "Intellicomm v2" by following the on-screen instructions, and once
selected press [Enter] twice.

Starting Intellicomm
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
The above setup need only be done once.  From now on, simply select "Open
Window" then type "IN" to run Intellicomm.
⌡IBM OS/2 2.x
▀▀▀▀▀▀▀▀▀▀▀▀

For those who wonder whether an OS/2 version of Intellicomm is expected,
the answer is yes.	Due to the current market situation (the number of
Windows users vs. the number of OS/2 users) a Windows version of
Intellicomm is top priority.	But there are development tools on the market
that permit quick conversion from a native Windows application, to a native
OS/2 application, and if we can afford these tools when the Windows version
is released, the OS/2 native version of Intellicomm won't be far behind.

In the interim, we'd like to make you a deal.  Intellicomm for DOS runs
under OS/2 just fine (details below) and if you support the cause by
purchasing Intellicomm for DOS, we will guarantee that when Icom for OS/2
is released you will be able to purchase it for $15 or less (or perhaps for
free)!  I.e. previously registered users of Intellicomm for DOS will be
able to upgrade to Intellicomm for OS/2, directly through Liberation
Enterprises (and perhaps through dealers if we can arrange it), for $15, or
maybe $10, or maybe $5, or maybe for nothing.  We'll have to check our bank
account at the time of the release and see how much money we have
available.  If we're broke, you'll pay $15.	If we have some modest amount
of money in the bank, you'll get it for $10 or $5.  If we have ample funds
by that time, you'll get it for nothing, which would really be worth it for
us as well since it saves us from having to process orders and mail out
disks (your ICOM.REG key file would simply enable the registered user
features in the OS/2 evaluation version after you downloaded it from a
BBS... as with free updates of the DOS version).

Unregistered users will pay full price (likely $40-$50), and this offer
will NOT be valid once the OS/2 version has been released.	Without your
support today, we cannot possibly continue development of Intellicomm, nor
can we purchase the tools necessary to develop the OS/2 version.  And if
you consider $39.95 (Icom for DOS) plus $15.00 or less ($54.95 maximum),
you'll still get one of the best deals ever for an OS/2 communications
package!

Setting up Icom for use with OS/2
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
We have not tested Intellicomm directly with OS/2, but a number of
Intellicomm users have reported success, even with high-speed modems.  This
information was gleaned from other Intellicomm users in the Icom support
echoes:

■ Install the service pack, with the updated OS/2 comm. driver
(COMMGA3.ZIP, available on CompuServe and elsewhere), or Ray Gwinn's
drivers for OS/2 v2.

■ Run as a FULL-SCREEN application.  Not in a window.

■ DOS Settings which differ from the default:

	DOS_FILES 	   40
	DOS_HIGH		   On
	HW_ROM_TO_RAM	   On
	HW_TIMER		   On
	IDLE_SENSITIVITY  100

■ Communications settings for IBM's COM drivers:

	COM_DIRECT_ACCESS		  Off

	Enable 16550 if Found?  .  No

■ Communications settings for Gwinn's SIO/VSIO drivers:

	SIO_Virtualize_16550_A	  On
	SIO_Virtualize_COM_Ports   On
	SIO_Virtual_RTS_is_HS	  Off

	Enable 16550 if Found?  .  Yes

NOTE: The "Enable 16550" is on the "Terminal Settings" screen of ICOM's
own main setup.

Thanks to Graham Elliott for putting in the time to obtain and test all of
the above settings.  Thanks also to all the other OS/2 users who
contributed to the OS/2 testing.
