Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!decvax!ucbvax!MITRE-BEDFORD.ARPA!jhs
From: jhs@MITRE-BEDFORD.ARPA
Newsgroups: comp.sys.atari.8bit
Subject: OmniCom
Message-ID: <8710121507.AA01059@mitre-bedford.ARPA>
Date: Mon, 12-Oct-87 11:07:46 EDT
Article-I.D.: mitre-be.8710121507.AA01059
Posted: Mon Oct 12 11:07:46 1987
Date-Received: Thu, 15-Oct-87 00:46:01 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 29

Several people have sent me questions about OmniCom which make me think
that not everyone will realize that the basic OmniCom program needs to be
linked together with an RS-232 handler to make it work.  In particular,
with the 1030 and 835 direct-connect modems, not all the handlers floating
around work exactly right.  There is a special one called ATARISRS.232
which is 16 sectors long which will work OK with the 850 interface as
well as the 1030 and 835 direct-connect modems.  This handler is shipped
on the disk with OmniCom, so if you've been having trouble making OmniCom
work with an 835 or 1030, but would like a terminal emulator with all its
features, you should probably go ahead and order it on disk from CDY.

If you have a handler sitting around but don't know what to do with it,
make a disk with DOS on it, and make a copy of the handler on that disk,
but name it "OC" (for OmniCom).  They copy the OmniCom shareware program
onto the end of it using the DOS "append" mode, like this:

C<RETURN>
D1:OC.OBJ, D2:OC/A<RETURN>

or the equivalent using your favorite DOS.  With DOS 2.0 or 2.5, the "/A"
on the end of the destination filename makes DOS append the source file
to the end of the existing destination file, instead of writing over it as
it would if you failed to specify /A.

The result is a file containing the RS232 handler, followed immediately
by the OmniCom program.  This should now run properly, assuming the RS232
handler is suitable for your modem interface.

-John Sangster / jhs@mitre-bedford.arpa