     The  file MEX-OS.OBJ is already assembled and overlaid for the Osborne  1
with Comm-Pac modem. It is an earlier version of MEX (1.0) but the Comm-Pac is
limited and MEX1.0 can handle almost all of its capabilities.

     The complete document explaining MEX is a large (for Osborne SD) WordStar 
file --80k. It is broken into two files, MEX11DOC.TOC is the table of contents 
for  the MEX11DOC.WS WordStar file.  There is also a HELP file that goes  with 
MEX (an on-line help system);  it is large too,  probably much too large for a 
SD  Osborne to have on line along with MEX.  However,  except for the  Osborne 
specific overlays, the whole thing can be used on any CP/M computer. 

     I've  played with MEX enough to have started to get to know my way around 
it, used command files (READ), tied it to some useful OS-1 function keys, etc. 
For  now,  try  using  the command extension (STAT EXTEND  ON)  files  I  have 
included  below  to get a feel for MEX.  Enter them on the same disk with  MEX 
using your word processor. INI.MEX is used to initialize some settings on MEX. 
Notice  the  warning  about no disk in drive B before you use  MEX  with  this 
INI.MEX!  Also, until you have defined some phone numbers from within MEX, you 
will  get an error message about not having the file for  phone.phn.  Entering 
phone numbers is easy; just type (once in MEX):

        PHONE label=555-5555

where  label is the name of the number (like ALB) and 555-5555 is the  number. 
Then save the numbers you have entered by typing SAVE PHONE.PHN (the PHN  type 
is necessary).  You now have a phone number file;  use it by typing CALL label 
(for example, CALL ALB). Pretty nifty. CALL ALB # calls the phone number until 
it  answers (if busy);  CALL ALB # 5 calls ALB five times;  CALL ALB DEC calls 
ALB,  if  it  is busy it calls DEC;  CALL ALB DEC # does  the  same  alternate 
dialing until one of the two boards answers, etc.

     The  other  files can be used as command files from the command level  of 
MEX --just type,  for example, GET anyfile. This would tell the remote to send 
the file anyfile and tell MEX to receive the same.  GETLIB works the same  way 
except it takes two arguments:

        GETLIB library libfile

where library is the name of the library on the remote and libfile is the name 
of  the  library member file you want to receive.  SEND sends a  file  to  the 
remote,  etc. If anyone has a question (or some ideas!!) drop me a message. If 
you  examine the files you can get some ideas for more powerful  "MACROS".  In 
particular, note that {1} is the first entry following the command, {2} is the 
second,  etc.  For  the  uninitiated  (those without Pascal),  to get  the  {} 
characters on the Osborne 1 press <ctrl> and < or <ctrl> and > simultaneously. 

     I realize these notes are rather cryptic --I'll try to write some  better 
soon!

Sherman Wilcox
10/20/84




FILES FOLLOW - FILE NAMES BETWEEN DOTTED LINES

-------------
INI.MEX
-------------
>>  This file will be executed each time you run MEX-OS.   It is important  to 
know  that  the last line will log you onto Drive B (where most files will  be 
downloaded  onto with OS-1 because of lack of space on Drive A  -- where  MEX-
OSCP resides). If you don't have a disk in Drive B -- guess what!!<<

LOAD PHONE.PHN
STAT SEARCH 2
ALT A0:
TYPE DFKEYS
B0:

-------------
GET.MEX
-------------
SENDOUT "XMODEM S {1}"
RT {1}

-------------
GETLIB.MEX
-------------
SENDOUT "XMODEM L {1} {2}"
RT {2}

-------------
SEND.MEX
-------------
SENDOUT "XMODEM R {1}"
ST {1}

-------------
DFKEYS
-------------
            ==>>  FUNCTION KEYS <<==
               1 - DIR <CR>
               2 - DIR B: <CR>
               3 - TYPE
               4 - CALL ALB #
               5 - CALL DEC #
               6 - CALL ALB DEC #
               7 - GETLIB
               8 - GET
               9 - ERA B:*.BAK
               0 - BYE
===================================================
>>This file is typed on the screen each time I run MEX --it reminds me of  the 
OS-1  special  function keys that I have defined --I always forget  which  key 
does what<<
