home *** CD-ROM | disk | FTP | other *** search
-
- CDS Version 2.60
- Copyright Nathan Hartwell, PSI Software 1992. All rights reserved.
-
- WARNING!
- -----------------------------
- There are rare circumstances in which versions of CDS prior to 2.30
- can result in loss of data. Please use 2.30 or later.
-
- *NOTE*
- -----------------------------
- The 11th file bug was fixed in version 2.40 (without my knowledge it even
- existed!). Version 2.41 is nothing but smoothing out the appearance of
- CD-Share on the local side.
-
- *NOTE*
- -----------------------------
- Single file bug in versions 2.40 and 2.41 fixed. Also, increased max file
- count to 1024 files. Enjoy!
-
- *NOTE*
- -----------------------------
- Added 'ready' message to 2.50, but forgot to send it to the user. Fixed.
-
- *NOTE*
- -----------------------------
- Fixed possible network conflict with swap routines.
-
-
- DESCRIPTION
-
- CDS is a program that allows movement of a file from any drive to any
- other temporary drive and subdirecory before download. External
- protocols such as DSZ are fully supported and all parameters are
- passed on to the external protocol. This is fully transparent to the
- caller except a short delay while files are transferred. The program
- is designed for full use of CD-ROM minichanger devices on a multinode
- BBS's without the use of doors. It can be used in any BBS environment
- that allows use of external file protocols. It has been tested with
- PCBoard version 14.5a, 386 and 486 computers, DSZ, and Lantastic NOS
- 4.00.
-
- In addition, this program can be used on any networked BBS to
- significantly decrease LAN traffic during file transfers. Usually a
- file is sent across the LAN to the local node then out over the modem
- as it is downloaded. During the entire download, pieces of the file
- are being sent across the LAN. With this program, there is a single
- copy of a file to the local hard disk, then the file is sent from
- the local disk. LAN traffic for the duration of the download is
- eliminated. This may significantly increase the efficiency of your
- BBS, especially if you run several busy nodes.
-
-
- "SUNDAY" SHAREWARE CONCEPT
-
- No, nothing religious here. This version is fully functional and
- works very quickly... 6 days a week. On the 7th day, Sunday, there
- is a delay for 5 seconds with each transfer to the hard disk. Lest
- the caller think there is something wrong, it also puts out a short
- note to the caller telling him about the delay for unregistered
- shareware. Obviously, this is to encourage registration of the
- software yet to allow full use of CDShare until it is registered.
- With the registration, you'll get a key file that will allow you to
- disable all messages to the caller if you choose. The key allows
- full use without delays every day of the week.
-
- You may upload and freely distribute this program as long as it is
- unmodified and contains only CDS.EXE and CDS.DOC. You may not modify
- this DOC file or program code. You may recompress this file in any
- format but you may not add advertising files to it with the exception
- of a "ZIP header" or equivalent.
-
-
-
- USE
-
- This software is not free. The user may use this program for
- evaluation for a period of 30 days, after which he is expected to
- register the program ($22.50) or discontinue use. Use for more than
- 30 days without registration represents a violation of copyright.
- Please mail checks to:
- Portal System Innovations
- Attn: Nathan Hartwell
- 212 Shoreline Drive
- Lakesite, TN 37379
-
-
- DISCLAIMER
-
- This program is provided "as is" without warranty of any kind, either
- expressed or implied including but not limited to the implied
- warranties of merchantability and/or fitness for a particular
- purpose. (Sounds familiar, doesn't it?) There is no warranty beyond
- refund of any money paid to the author by the user. In no event
- shall the author, supporting BBS systems, Sysops, or PSI software be
- held liable for any damage or losses resulting from the use of this
- program. It is up to the user to determine the correct usage of this
- program on his system and he/she bears full responsibility for
- correct implementation of it.
-
-
- DOCUMENTATION
-
- Now for a quick and simple doc file.
-
- Installation:
-
- In each of your external protocol send batch files, add CDS.EXE
- before your external protocol driver.
-
- Example: DSZ port %P speed %B estimate 0 sz -m %F
- |
- v
- CDS DSZ port %P speed %B estimate 0 sz -m %F
-
- Execution:
-
- CDS <Protocol Program Name> <Required Argument> [Other Optional Args.]
-
- Required Argument: If no options are used, this will should be either
- the filename of the file to send or if the first
- character is an at sign (@), the control file (list
- of files to send). Preferrably, all filenames have
- full path specs.
-
- Optional Args.: You can pass all the arguments you would normally use,
- just make sure the above mentioned required argument is
- the last argument passed.
-
-
- Configuration File:
-
- Filename: CDS.CFG
- Location: Either in current directory or directory from which CDS.EXE was
- executed.
-
-
- Config file format. The following is a list of valid commands and their
- required arguments:
-
- » LogPath - Full pathname for the logfile.
- > LogLevel - A number from 1 to 6, where 1 puts the least amout in the log
- and 6 puts everything in.
- Temp - Directory to use as temp storage. Trailing backslash (\) is
- optional. You may use a RAM-Disk for this directory.
- Drives - The drive letter(s) of the drive(s) you want CD-Share to
- consider removable media and hence copy files off of.
- » Port - The COM Port Number (1 - 4) Use if your COM Port uses standard
- port addressing. See list below.
- » XPort - The hexadecimal address of the base port address your COM Port
- is set to. Example: COM1 is nomrally located at 3F8.
- |> Msg - Used to customize message sent to users.
- > Exec - Command-line to execute on each file that is copied to the temp
- directory. Use '%s' in place of the filename to process.
- |> UseEMS - Enables the use of EMS memory for the swap routines.
- |> UseXMS - Enables the use of XMS memory for the swap routines.
- |> UseFile - Enables the use of a temporary swapfile.
- |> XMSFirst - Tells the swap routines to try XMS memory, then EMS.
- |> SwapDir - Must be set to enable the swap. Set this to where you would
- like the swapfile to be put.
- |> Ready_Msg - Specify a custom start transfer message.
-
- | = Registered only.
- > = Optional parameter.
- » = Optional parameter for registered version, required for non-registerd.
-
- Commands LogPath, Port, and XPort are required for non-registered copies.
- If you are registered, leaving out the LogPath command disables logfile
- output, while leaving out either Port or XPort disbales the message output.
-
- The order of these in the config file is not important, so long as they are
- each on their own line.
-
-
- Environment Variable:
-
- Certain BBS packages allow multiple nodes to be based out of one main
- directory. Turbo-Comm (still under development) and Renegade are two such
- systems. Due to these systems, an environment variable has been added so as
- to tell CD-Share what the configuration filename is. The environment
- variable is, of course, CDS. Just SET CDS=[path]<filename> and you're all
- set.
-
-
- Example config:
-
- LogPath C:\BBS\CDS.LOG
- LogLevel 3
- Temp X:\
- Drives ABJKLM
- XPort 3F8
- Msg Are files all you get?
- Exec PKZip.Exe -z %s MySys.Txt
- UseEMS
- UseXMS
- XMSFirst
- SwapDir X:\
- Ready_Msg Ok, leech, start your download...
-
- In this example, drives A:, B:, J:, K:, L:, and M: will have files copied
- from them to the temp directory, all others will be skipped.
-
- NOTE: Do NOT separate the config commands and their parameters with tab
- characters. You may put multiple spaces in to make the config file
- pretty, but the tab character will only be removed (and not
- translated).
-
- Standard COM Port base addresses: (for COM1 - COM4)
-
- COM1: 3F8
- COM2: 2F8
- COM3: 3E8
- COM4: 2E8
-
-
- DOS Critical error trapping has been added. CD-Share will retry up
- to five (5) times before terminating. No log entries are generated
- for critical errors.
-
-
- Notes:
-
- * - Files are copied from media devices to the specified path.
- This may be a RAM-Disk. The files copied are then deleted
- afterwards, so if you are running multi-node make a .CFG for
- each node.
-
- * - For use with multinode BBS systems, and minichangers you should
- disable all internal protocols. With PCBoard, you'd edit the
- PCBPROT.DAT, see your manual.
-
- * - You may want to put a TEMPFILE subdirectory on each local disk
- to decrease network traffic. The file(s) will be copied from the
- remote device to the local TEMPFILE subdirectory once and deleted.
-
-
- PLUGS:
- Software alpha tested on Rose and Crown BBS (615) 892-0097
- (>5GB, over 60,000 files, USR/DS, 1st call downloads). Current
- version available. Contact author, Nathan Hartwell, on this BBS, or
- RIME CD-ROM echo.
-
- PSI Software: Custom programming available.
-
- Support BBS:
- The Genetics Lab
- SysOp: Tiberious Velnoq (aka Nathan Hartwell)
- (615) 842-0852 - 24 hr/day - 12/2400 Baud
- FidoNet 1:362/116.0 - PSI-Net 91:615/101.0
- Latest version can be downloaded/file requested from this system.
- Compuserve: 71451,300 - Internet: 71451.300@compuserve.com
-
- -------------------------------------------------------------
- Further notes on PCBoard installation, (David Ellison, Sysop,
- Rose and Crown BBS)
- RIME ->RCROWN
- -------------------------------------------------------------
-
- PCBoard SAMPLE BATCH FILES:
- These are for COM2. Change "port 2" to "port 1" for COM1
-
- Zmodem send with DSZ: PCBSZ.BAT
- echo off
- if exist cds.log del cds.log
- if exist pcberr.fil del pcberr.fil
- if exist pcbdsz.log del pcbdsz.log
- cds dsz.com handshake both port 2 pB4096 z sz %3
-
- Zmodem receive with DSZ: PCBRZ.BAT
- echo off
- if exist pcberr.fil del pcberr.fil
- if exist pcbdsz.log del pcbdsz.log
- dsz.com handshake both port 2 pB4096 z pr1 rz -p %3
-
- Xmodem send with DSZ: PCBSX.BAT
- echo off
- if exist cds.log del cds.log
- if exist pcberr.fil del pcberr.fil
- if exist pcbdsz.log del pcbdsz.log
- cds dsz.com handshake both port 2 pB4096 sx %3
-
- Xmodem receive with DSZ: PCBRX.BAT
- echo off
- if exist pcberr.fil del pcberr.fil
- if exist pcbdsz.log del pcbdsz.log
- dsz ha both port 2 pB4096 rx %3
-
- Note: Be sure to change PCBPROT.DAT types (PCBSETUP, FILE LOCATIONS
- 2). "I" reflects internal, "D" is for DSZ.LOG (use for Zmodem
- protocol), "S" is for shelled protocols (use for Xmodem). You
- shouldn't have any internal protocols left when you finish unless
- that particular node doesn't have access to the CD-ROM minichanger.
-
- All protocols must be external, either shelled or DSZ.LOG
- supporting. Use of the wrong type (D instead of S for example with
- Xmodem) can result in the filename not being passed to DSZ. This
- will cause you a bit of lost time (like a weekend).
-
- DSZ is exquisitely case sensitive, change the case in any of the
- above "dsz" lines and you'll have file transfer difficulties. The
- above files do work on the Rose and Crown with Dual Standard
- modems, 16550 UARTS, and registered DSZ.
-
- If you have questions about what is being
- passed to DSZ from PCBoard, put the following line in just above
- the dsz line in the batch file:
- echo %1 %2 %3 %4 %5
- You'll see exactly what's being passed on to DSZ by the BBS.
-
- With 1 or 2 Pioneer minichangers you can have 3.9 Gigabytes with a 6 disk
- changer or 7.8 Gigabytes with 2 stacked changers. For us, it is
- definitely worth the trouble to set up. Minichanger has been trouble
- free since installation.
-
-
-