home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-387-Vol-3of3.iso
/
c
/
cdd10.zip
/
CDD.DOC
< prev
next >
Wrap
Text File
|
1993-03-18
|
14KB
|
365 lines
┌┬┬┬┬┬┬┬┬┬┬┬─┐
││││││││││││ │
││││││││││││ │
││││││││││││ │ ┌───────────┐
││││││││││││ │ │ ┌────────┘
├┴┴┴┴┴┴┴┴┴┴┤ │ │ │ ┌─────────────┐
└┬─────────┴┬┘ │ │ │ ┌───────┐ │
┌──┴──────────┴────────┐ │ │ │ │ │ │
│ │ │ │ │ │ │ │
│ │ │ └─────────┘ └───────┘ │
└──────────────────────┘ └────────────┐ ┌──────────┘
│ │
│ │
│ │
│ │
└──┘
C O M P U T E R P R O F I L E S
406 Amsterdam Ct N.
Virginia Beach, Virginia 23454
BBS (804) 491-4347 491-5061
CD DIRECTOR (tm)
Version 1.00
Created By Gary R. Smith
Copyright (c) 1992 - Computer Profiles
License to Use Agreement
───────────────────────────────────────────────────────────────────────
Computer Profiles, (hereafter referred to as"CP"), grants to
the purchaser - and purchaser accepts - a non-transferable and
nonexclusive license to use, on a single computer, the software
products and accompanying materials provided to the purchaser by
CP. Purchaser is hereby licensed only to read the program from
its medium into the memory of a single computer solely for the
purpose of executing the program.
CP shall have the right to terminate this license if purchaser
violates any of its provisions. Purchaser agrees that the
software products and accompanying materials are the property of
CP and that CP shall maintain title to and ownership of the
software products at all times. Purchaser agrees to make no more
than one (1) additional working copy and one (1) backup copy of
the software products for their personal use only.
CP makes no warranties of any kind, expressed or implied, with
respect to the quality, performance, accuracy, or fitness of the
software products for any particular purpose. CP assumes no
responsibility for any decisions make or actions taken on the
part of the purchaser because of the use of the software
products. In no event shall CP, or any of its representatives,
be liable for any loss of profit or any other damages, arising
out of the use or inability to use this product - even if CP or
an authorized agent of such has been advised of the possibility
of such damages - or for any claim by any other party.
CP reserves the right to make changes, enhancements and
improvements to the software products at any time without
notice.
DISCLAIMER
───────────────────────────────────────────────────────────────
There is made no warranty of any kind, express or implied
including, without limitation, any warranties of merchantability
and / or fitness for a particular purpose. CP shall not be
liable for any damages, whether direct, indirect, special or
sequential arising from a failure of this program to operate in
the manner desired by the User. CP shall not be liable for any
damage to data or property which may be caused directly or
indirectly by the User of this program.
IN NO EVENT WILL CP BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING
ANY LOST PROFITS, LOST SAVINGS OR OTHER INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF YOUR USE OR INABILITY TO
USE THE PROGRAM, OR FOR ANY CLAIM BY ANY OTHER PARTY.
CD DIRECTOR is a Trademark of Computer Profiles Ltd
Borland C++ is a Registered Trademark of Borland International
PCBoard is a Registered Trademark of Clark Development Company
Now that all the Legalities are out of the way, Let me introduce you
to the most versatile CD FILE MOVER for the PCBoard enviornment.
CD DIRECTOR
If you are not running PCBoard then this software WILL NOT WORK with
your bbs. This program was written using the TOOLKIT from Clark
Development Company explicitly for PCBoard systems.
CD Director (herein referred to as CDD) is a simple program to implement
and will provide your system with increased speed as it moves your
users download files to a temporary directory setup and directed by
you. CDD is written with the PCB C TOOLKIT and is very configurable as
you will see in the next couple of paragraphs. We apologize for the
short documentation, but when its easy there is no need to drag it out.
(You wouldnt probably read it anyways....Right<Grin>).
To begin...
Put CDD.EXE and the CDD.CNF files in your path. It is Multinode
Compatible!
SETTING ENVIORNMENT VARIABLES
CDD uses the enviornment variables of PCBoard. These variables are
normally created when a door is run however, since CDD is NOT a door
program and the variables are still expected, You will have to edit
your board batch file and insert the following enviornment variables:
(SEE BOARD.TXT for an example of setting these variables)
Enter in your BOARD.BAT FILE:
SET PCBDRIVE=C: // Or appropriate drive letter
SET PCBDIR=\PCB // Directory where this node of
PCBoard is running
SET PCBDAT=C:\PCB\PCBOARD.DAT // This is the FULL path to the
nodes PCBOARD.DAT file
Example BOARD.BAT:
_____________________________________________________
@ECHO OFF
C:
CD\PCB
SET DSZLOG=H:\PCB\PCBDSZ.LOG
SET PCB=/MAIN /UPCRED:0.2 /BYTECRED:0.5 /NOREG /SWAP
* SET PCBDRIVE=C:
* SET PCBDIR=\PCB
* SET PCBDAT=C:\PCB\PCBOARD.DAT
IF EXIST REMOTE.BAT RENAME REMOTE.BAT REMOTE.SYS
IF EXIST EVENT.BAT RENAME EVENT.BAT EVENT.SYS
IF EXIST DOOR.BAT DEL DOOR.BAT
IF EXIST ENDPCB DEL ENDPCB
C:\PCB\PCB145
IF EXIST REMOTE.BAT REMOTE
IF EXIST DOOR.BAT DOOR
IF EXIST EVENT.BAT EVENT
IF EXIST ENDPCB GOTO END
BOARD
:END
ECHO TYPE BOARD TO RESTART PCBOARD (THANK-YOU).....
_____________________________________________________
* Add these variables
With the above variables set any program that uses these will be able
to also return to the node directory from which it came. This also allows
CDD to find the default directory and access any of the PCBoard files it
needs to run properly.
CREATING A TEMPORARY WORK DIRECTORY
CDD will copy all of your users file requests to a directory determined
by you. (This is set in the Configuration File discussed later). If you
are running multiple nodes you will want to set up a temp directory for
each nodes files to be copied to...ie...
C:\PCB\NODE1
C:\PCB\NODE2
etc..
CREATING THE CONFIGURATION FILE
Note: Ensure you add a number to the end of the directory when creating
it. CDD will append a NODE NUMBER to the directory filename.
If a different drive will be assigned for each node then you will have
to create a config file for each node and drop it in that nodes
directory or path.
CDD will automatically search the path to find the nearest config file.
It starts with its home directory and then moves on to the path stated
in your autoexec.bat file.
CREATING THE CONFIGURATION FILE
Creating the configuration file for CDD is very simple. Items in the
file are not in any order, however if items are not found then the
defaults will be used. Any item Preceeded with a ; is considered a
comment line.
WORKDIR= Assign the directory name for where CDD will place the files
it copies over (MINUS THE NODE NUMBER) (Remember you created
this directory with a node number)
ex. WORKDIR=H:\PCB:TEMP
(CDD will put the files in H:\PCB\TEMP2 if the node
number was 2, Temp1 if you have a single node)
ZIPFILE= This is the full name and path to your zip comment file. If
you want CDD to insert a ZIP comment file into the copied
files then place the name here. If not remove this line from
the config file.
ex. ZIPFILE=H:\PCB\RANDOM.AD
MSGLINE= You can define this line that will be displayed to the caller.
PCB @ color codes are supported. (Only color codes are
supported).
ex. MSGLINE= Processing your files, please wait...
(Notice no "") :)
MSG-LINE-COLOR= This is the color you want the MSGLINE to be when
displayed to the caller. (PCB @ color codes MUST be used)
ex. MSG-LINE-COLOR=@X0D
SHOWMSG= If not in the config file the MSGLINE default is to show the
message. Enter YES to show and NO if you do not desire to
show either a personalized message or the default message
line.
ex. SHOWMSG=YES
SHOWMSG=NO
SHOWSTATUS= This determines if the user will be shown the status of
the file movement. The following is shown to the user if
this option is set to YES:
Filename Status
___________ __________
CDD.ZIP Moving File/Updating File/ Completed
To show this information to your users just place a YES
after SHOWSTATUS:
ex. SHOWSTATUS=YES
You can also define the colors that are used to show the status by using
the PCB @ color codes along with the following variables:
STATUS-COLOR= This is the text color of the status lines
FILENAME-COLOR= This is the color of the filename
END-MSG-COLOR= When completed the status line will default to:
Start your transfer now.
CTRL-X Aborts Tranfer
This variable only sets the color, the words are
not changeable.
MOVE-COLOR= Specifies color for "MOVING FILE"
UPDATE-COLOR= Specifies color for "UPDATING FILE"
COMP-COLOR= Specifies color for "COMPLETED"
See the example config file (CDD.CNF in this zip)
BATCH FILES
Included in this zip are batch files commonly used with PCBoard.
the means will be displayed here in the pcbsz.bat file.
PCBSZ.BAT
@echo off
if exist pcberr.fil del pcberr.fil
if exist pcbdsz.log del pcbdsz.log
1 CDD CDD.CNF %3
2 dsz.exe handshake both pB4096 estimate 0 %5 z sz @%PCBDRIVE%CDD.LST
3 CDD CDEL
The files are the same as distributed with PCBoard with the following
exceptions.
Line (1) calls CDD, Passes the CDD.CNF filename and includes the
%3 (Which is the filename or list passed by PCboard).
Line (2) Is your regular dsz line with the %3 changed to:
@%PCBDRIVE%CDD.LST
Line (3) Tells CDD that all the files have been transfered and to
delete the files that were moved to the directory. NOTE that CDD
only deletes the files that it moved.
The last item to complete is to turn off all of your internal protocols.
This is done within the pcbsetup program. If you allow internal
protocols then CDD cannot do its job and you have defeated the purpose
of installing the program.
The color codes for CDD are easy to use and are exactly the same as
PCBoards 14.5+ codes. The @X color codes correspond to regular PC
display codes.
For instance, a 1 is blue, 2 is green, a 3 is cyan etc...
BACKGROUND FOREGROUND
FIRST DIGIT SECOND DIGIT
BLACK 0 0
BLUE 1 1
GREEN 2 2
CYAN 3 3
RED 4 4
MAGENTA 5 5
YELLOW 6 6
WHITE 7 7
BRIGHT COLORS:
BLACK 8 8
BLUE 9 9
GREEN A A
CYAN B B
RED C C
MAGENTA D D
YELLOW E E
WHITE F F
Examples: Bright white on blue background = 1F or @X1F
Bright yellow on green background = 2E or @X2E
Dark blue blinking on white background = F1 or @XF1