home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 15
/
CD_ASCQ_15_070894.iso
/
vrac
/
cp_211.zip
/
README.206
< prev
next >
Wrap
Text File
|
1994-05-18
|
3KB
|
63 lines
cPoint update v2.06 ...
- added configurable base directory
- added command line argument to load an alternate .Cfg file at startup
- the default .Cfg file is cPoint.Cfg and if you only have one BOOS system
you will not need this feature
- to use cPoint with more than one system take an existing .Cfg and
copy it to a unique name in the same directory as cPoint.Exe
- run cPoint with the name of the new .Cfg file on the command line (note
that the .Cfg must not be entered) eg: cPoint AXAXA
- edit your configuration to provide a path for the base directory and
the BOSS information as required
- all configuration files MUST end in .Cfg
- when you want to call a system you would run cPoint with the name (and
no extension) of the configuration file to use
- example: if you call A_X_A_X_A and Object Code Systems you would
start with a raw cPoint.Cfg file and copy it to, say,
AXAXA.Cfg and then rename the cPoint.Cfg to, say, OCS.Cfg
- run cPoint AXAXA
- configure the BOSS phone number and addresses and enter
a mail path for the messages that you will get from the
A_X_A_X_A system.
- run cPoint OCS
- configure as above but this time for the Object Code
Systems BOSS data and a separate message path for any
messages that you will get from the Object Code Systems
system
- from then on you run cPoint with the appropriate .Cfg file
name on the command line
Please note that from a FidoNet persprective it is VERY important that you
keep messages separated by system.
Once again, ALL .Cfg files MUST be in the same directory as the cPoint.Exe
file.
Please note that if you are only a point to one single system you will not
need to worry about any of the above. The default path of .\ will work just
fine. Although you may change it to the specific directory that is the base
of your RECV, SEND and MAIL directories it isn't really necessary.
In review, to create a new .Cfg for a new BOSS system that you will be calling
you must 1) copy the original cPoint.Cfg file (or any .Cfg) to a unique file
name and then run cPoint with that name (no extension) as a command line
argument. You must then alter the Base Path in the configuration section for
your system info. You will also need to alter the BOSS configuration.
When you enter the name of the base directory for a new configuration the
root must exist already. For example, if you enter...
C:\SYSTEMS\AXAXA
... and C:\SYSTEMS doesn't exist then the operation will fail. The AXAXA part
will be created if, and only if, the paths preceding it exist already. The
C:\SYSTEMS\AXAXA\MAIL, C:\SYSTEMS\AXAXA\RECV and C:\SYSTEMS\AXAXA\SEND
directories and all of the MSG*.BBS files in the C:\SYSTEMS\AXAXA\MAIL
directory will be created if, and only if, C:\SYSTEMS already exists.
Confused? So am I. Good luck, the tests and debugging processes work so if
you encounter any difficulties you can bet that they are likely to be in the
directory structure as described above.