CDBatch


                      (C) Ron Reynolds & Greg Bastow


This  product  is released under the shareware concept.  This means that if
you  find it useful and use for in excess of 21 days (Trial Period) you are
requested to mail the enclosed form with the requested payment.


                   CDBatch was conceived by Greg Bastow
                       and Written by Ron Reynolds.


Purpose
~~~~~~~

This utility requires Workbench 2.0 or newer.

Multi-Disk  CDROMs have a small problem with DLG and users downloading from
them.  When the user moves about the CDROM and downloads a file, the device
is locked out from other users being able to get at any of the other CDROMS
that  are  online.   DLG also cannot keep accurate download records for the
file  with CDROMS - DLG reads the file comment of the file to find the *.FD
to update them and cannot find/create these files on READ-ONLY devices.

CDBatch is a small program that is used in the FILE menu of DLG Professional.
Once  installed, the user will use it exactly as the TAG ('.') command.  It
will  then  move  the  file  to  another  location  (in accordance with the
switches  used)  so  the user can then Batch-Download it from their private
directory.   This  will  free  up the CDROM devices so other users can have
access to it.


Usage
~~~~~

This is the output if you just tpe CDBATCH into a shell.


 CDBatch 1.0 Copyright © 1993 Ron Reynolds

 Usage:

 CDBatch %FILE_FILENUMBER %FILE_FILEPATH %FILE_AREANUMBER [PRIV]

 You MUST have a Directory Assigned to "HOLD:" or an Environment
 Variable set pointing to a Valid Path. (including a trailing ":" or "/")


Installation
~~~~~~~~~~~~
    If you have an alternate area for DLG modules, copy CDBATCH into there.
    If  not  might  I  suggest  you  create  one,  perhaps  called DLGX (or
    something) and copy the executable into there.

    In your DLG.START either

		SETENV CDBATCH "FILE:HOLD/"
                        ==========> This would be your temporary location.

				- OR -

		ASSIGN HOLD: FILE:HOLD

		In both of these examples, you would be required to create the FILE:HOLD
		directory.

    Edit your FILE_MAIN menu, I would suggest using the '+' command for the
    COMMAND letter. The menu entry should look like the following.

	[ 1] Letter:                   +
	[ 2] Executable: (path/name)   DLGX:CDBATCH %UNAME %FILE_FILENUMBER
(cont)                                            %FILE_AREANUMBER PRIV
	[ 4] Description:              CD-ROM Batch Utility
	[ 5] Type:                     Executable
	[ 6] Help File:                FILE_MAIN/+
	[ 7] Lower level:              5
	[ 8] Upper level:              255
	[ 9] Hidden:                   NO
	[10] Load type:                OVERLAY
	[11] Ask user if sure:         NO
	[12] Pend messages:            NO
	[13] Cli mode:                 NO
	[14] Pause on completion:      NO
	[15] Log value:                None
	[16] Activity string:          CD-ROM Batching
	[17] Priority:                 DEFAULT
	[18] Edit help file

	And that's it....I would suggest making all your CDROM areas as READ-ONLY
	areas  (no upload/download ability) and that way someone cannot use the
    normal [D] Download command. Also creat an ENTERAREA.TXT file that says

    --cut--
	Please use the '+' command to BATCH-TAG the files you want from this file
	area, and then move into your private file area to download your tagged
	files.
    --cut--


Explanation
~~~~~~~~~~~
	The  DLG  switches  can  be looked up in your user documentation if you
	wish more clarification on what they do.

	The  PRIV switch forces the program to upload the files into the USER's
	private file area.  The [FREE] bit is _not_ set on these files.

    In your assign HOLD:  directory, the program will create a directory of
	the users name and put their files into this directory.

	DLG Debits the user's record ONLY when the actual file is downloaded.


Caveats
~~~~~~~

	There seems to be a problem with DLG and loading the BATCH.FILE. Sometimes
	the user will have to exit FILE and re-enter it, so that the batch file
    is loaded. We decided not to force an exit & reload like the multi-bbatch
	programs, as when your in SIGS they tend to not work very well.