Category : Communication (modem) tools and utilities
Archive   : CMC501.ZIP
Filename : INSTALL.CMC

 
Output of file : INSTALL.CMC contained in archive : CMC501.ZIP
°°°°°°°° INSTALLATION AND CONFIGURATION OF {COMMO} MASTER CONTROL °°°°°°°°°°°°

VERSION 5.01

4 October 1991

There are only three files that need to be configured to run
CMC.MAC. They are: CMC.BAT; CMC.FON; and CMCINFO.MAC.
These files are described in detail below. Take the time to
do this right. The proper functioning of CMC.MAC depends on
it.


CMC.BAT

The CMC.BAT file can be located anywhere in your path. All
other CMC files must be in the COMMO directory.

c:
cd \com\commo
set commo=c:\com\commo
set DSZLOG=c:\com\commo\commo.log
commo /mcmc.mac /dcmc.fon /:welcome
set DSZLOG=
set commo=
exit

Line by line description.

1. Change to the drive that COMMO is on. Change as
necessary.

2. Change to the COMMO directory. Change as necessary..

3. Set system variable to commo directory. Change as
necessary.

4. Set log file for DSZ to the COMMO.LOG file. Change as
necessary.

5. This line calls COMMO, sets CMC.MAC as the active
macro, CMC.FON as the active .FON file, and starts the CMC
initialization macro. You may omit /dcmc.fon if you plan to
modify your COMMO.FON file to CMC specifications. The rest
should be unchanged.

6. & 7. Sets to null the two system variables DSZLOG and
COMMO.

8. Closes the DesqView window on exit from {COMMO}


CMC.FON

BBS Name Last On Phone # Password\BBSid Macro Para

B-BEARD (Henry Moore) 09/21/91 {294 9657} {password\b-beard} {passparse} {}
CYBER1 (Philip Yanov) 09/22/91 {242 3766} {password\cyber} {passparse} {}
CYBER2 (Philip Yanov) 09/21/91 {242 3994} {password\cyber} {passparse} {}
DOORS1 (Richard Fuller) 09/14/91 {299 3668} {password\doors} {passparse} {}
DOORS2 (Richard Fuller) 09/21/91 {299 3594} {password\doors} {passparse} {}
FORUM! (Doug Glenn) 09/21/91 {862 4616} {password\forum!} {passparse} {}
GCSO-BBS (HDavid Rice) 09/21/91 {242 2792} {password\gcso-bbs} {passparse} {}
ULTBBS1 (Matt Cooley) 09/21/91 {895 3536} {password\ultbbs} {passparse} {}
ULTBBS2 (Matt Cooley) 09/21/91 {895 5836} {password\ultbbs} {passparse} {}
GOLDEN STRIP CONNECTION 09/21/91 {967 8127} {password\golden} {passparse} {}

Note that the BBSID name, (the name on the .QWK and .REP
packets,) is also the name in the "BBS Name" column. When
there is more than one entry the numbers 1, 2, or 3 can be
appended with no space to the BBSID name.

I use the password field to store both the password and the
BBSID name. (A technique that I got from Shad Muegge.) The \
is used as a separator and cannot be used in you password.
Put your password first, the "\" separator and then the BBSID.

The linked macro for all entries is "passparse".




CMCINFO.MAC


This file is in three parts:

Part 1. BBS INFORMATION contains all the variable information
on the BBSs called. Each BBS called must have a
macro named for the BBSID. You must select the prompt
strings for the various variables for each BBS. Make
sure that _all_ the variables are set to a value.
Unless otherwise noted. When selecting "golook"
variables take care to select variables that are as
short as possible to accomplish the purpose. Long
variables have a greater chance of getting hit by
line noise.

Part 2. BBS LISTS contains the lists of BBSs to mark for the
various supported activities. (.QWK Mail, File down-
load from an ascii list, and Bimodem.)

Part 3. USER INFORMATION contains the users name, paths that
are necessary for the proper functioning of CMC.MAC,
and user defined menu key sequences.

I have included information in the CMCINFO.MAC file
to aid in configuring it to your requirements.

Good luck and have fun!

{don}












  3 Responses to “Category : Communication (modem) tools and utilities
Archive   : CMC501.ZIP
Filename : INSTALL.CMC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/