home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
RBTCH220.ZIP
/
DOCS.ZIP
/
WHATISA.DOZ
< prev
Wrap
Text File
|
1993-04-09
|
7KB
|
185 lines
-------------------
What is a .DOZ File
-------------------
.DOZ File Internal Structure
(C) by Dan Shore - 1992,93
THE SHORELINE BBS
December 18, 1992
A. Why the .DOZ file was created:
1. For files that do not have the ability to accept a FILE_ID.DIZ
or a DESC.SDI. What types of files are these do you ask? Well,
any file that cannot accept another file "inside" of a file
(.GIF's are an excellent example). Remember that the .DIZ or
.SDI are just text files that are added into compressed files.
2. When a .DOZ file is uploaded or used locally, with descriptions
and category codes, the files uploaded are processed by RBatch
for the file description and the category code without any
intervention by the user or SysOp. Basically AUTOMATIC UPLOADS!
As a user, just start the upload process and sit back and watch
your files posted to the BBS automatically. As a SysOp, just run
FakeXfer, then RBatch, and again just SIT BACK AND WATCH FILES
GET POSTED TO YOUR BBS AUTOMATICALLY!!.
3. ****************************************************************
* REMEMBER THAT YOU ONLY NEED ONE (1) .DOZ FILE WHEN UPLOADING *
* OR POSTING FILES LOCALLY. All the filename are listed in *
* this one .DOZ file. YOU SHOULD NOT HAVE MULTIPLE .DOZ *
* FILES AS THIS WILL NOT WORK WITH RBATCH. *
****************************************************************
NOTE:----------------------------------------------------------------
.DOZ files are VERY USEFULL when you are posting files LOCALLY
to your BBS, when used in conjunction with the FakeXfer program.
See the FakeXfer.Doc file for more information on this excellent
new process that saves time for SysOps who post files to their BBS.
Also, the program CAP2DOZ (CAP2DOZ.ZIP) makes creating a .DOZ file
so simple, that it is hard not to use a .DOZ file when posting files
locally on your BBS!
---------------------------------------------------------------------
The .DOZ filename can be named anything as long as it is a legal
DOS filename. Here is an example of a .DOZ file is shown here
with the internal structure of a .DOZ:
{FI dflat8.zip window x
Description of file goes here with a maximum
line length of 75 characters and a maximum
of 10 lines
{FI jiklan.zip window
Description of file goes here with a maximum
line length of 75 characters and a maximum
of 10 lines
{FI ved201.zip utils n dan shore
Description of file goes here with a maximum
line length of 75 characters and a maximum
of 10 lines
Line 1 : ALWAYS STARTS WITH A {FI and then the filename. Note
that there is a space between the {FI, filename, &
the category code. Do not use a path for the file.
(The {FI is the Smart Text variable for FileName in
RBBS, hence it seemed logical to use this as part of
the structure)
##### The text MUST START AT THE LEFT MARGIN. The example
above starts in the middle of the screen for ease of
reading.
The category code is the code that a user would normally
type when prompted to categorize a file. This is NOT
THE THREE DIGIT CODE in your FMS. For example if your
DIR.CAT had this entry:
"GAMES","GAM","All Games"
The .DOZ entry would look like this:
{FI WARRIORS.ZIP GAMES
This is a great graphical warrior game
The next field is if you are going to be uploading a
personal file to the BBS. If you use a "X", this tells
RBatch to not prompt the user to see if the file is
a personal upload or not. If you use the following
codes:
N = UserName for personal file
S = Personal Upload to SysOp (No additional field needed)
L = Personal Upload to security level
D = Personal Upload to a distribution list
If you use one of these codes, the RBatch EXPECTS to see
a value in the next field after this letter (except for
the SysOp personal upload).
Line 2 thru 11 : The description of the file to be posted, with
a maximum line length of 80 chars and a maximum
of 10 lines.
--------------------------- IMPORTANT ------------------------------------
The .DOZ file is uploaded to a BBS as part of the Uploading process and
can be sent first, in the middle, or last, it does not matter.
REMEMBER THAT THE .DOZ FILE CONTAINS "ALL" THE FILENAMES THAT YOUR ARE
UPLOADING OR POSTING LOCALLY. DO NOT USE MORE THAN ONE (1) .DOZ FILE
WITH RBATCH OR IT WILL NOT WORK.
When using .DOZ files for local posting by the SysOp, you want your .DOZ
file TO BE IN THE SAME DIRECTORY as the files that FAKEXFER is processing.
After the fakexfer file is generated, the .DOZ file will be copied to the
upload directory with all the other files. If the .DOZ file is not in the
upload directory, RBatch will not recognize it, hence you will be prompted
for descriptions/categories. If the file contains a FILE_ID.DIZ or a
DESC.SDI then the .DOZ file description entry is ignored for that file,
but the catgory code is used!
--------------------------------------------------------------------------
On the BBS side when the file is received RBatch will detect the .DOZ
file and then compare the filenames in it, to the filename in the
XFER-?.DEF file. When a match is found, the description within the
.DOZ is used and the user only has to categorize the upload. If a
category is found within the .DOZ file and it matches a category code
on the BBS, then the user or the SysOp is not prompted to categorize as
long as their security level allows them to categorize. If the security
level is too low to categorize then the default code that is specified
in the configuration file is used.
************************** AUTOMATED UPLOADS **************************
If the file being processed has a FILE_ID.DIZ or DESC.SDI and a .DOZ exists,
file category codes are used from the .DOZ, and the FILE_ID.DIZ/DESC.SDI file
description are used, hence the sysop/user does not have to intervene with
RBatch after the upload is started from RBBS!!!!
To aid the user in this new feature, I recommend that you either post
a file or make a bulletin describing how to use .DOZ files with an
upload.
Dan Shore - SysOp
THE SHORELINE BBS
301-946-2771