This help file is a text file, but certain formatting codes are in this
file so that it can be handled in a context sensitive way in DVCONFIG.

MAIN MENU
▀▀▀▀▀▀▀▀▀
From the main menu, you have the following options:

1. General Configuration
2. Edit archiver command lines
3. Download security setup
4. Sysop security setup
5. Quit and save (or ESC)

You will want to go through each of these options while configuring
DataView. There is detailed context sensitive help available in each
part, so please press F1 and make use of this help while configuring! :)





$
GENERAL CONFIGURATION
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
1. WORK DIRECTORY: In this field, you would put a working directory for
   DataView to use to extract files and such. It is best to leave this
   field blank because DataView will create its own work directory. The
   only good reason to specify a drive or work directory for this field
   would be if you had a RAMdrive. Naturally, extracting files and creating
   temporary files on a RAMdrive is a little bit faster then on the hard
   drive. If you are unsure, it is best just to leave this field blank.

   Just FYI, DataView will create its own work directories off of WildCat's
   node work directories. For example, the work directory for node 1 would
   be: "C:\WC30\WCWORK\NODE1\DV$WORK.1\". DataView removes its work
   directory when its done with it however.

2. HOME DIRECTORY: Specify your WildCat home directory in this field.
   DataView needs to know where your WildCat home directory is so that it
   can access the SECLEVEL.DAT file to get information on the various
   security levels. An example of a home directory would be: "C:\WC30\".

3. VIRUS SCAN COMMAND LINE: This is the command line that DataView should
   use when scanning files for viruses. Currently, DataView supports John
   McAfee's fine SCAN.EXE program. Please make sure that the following are
   part of your virus scan comand line:

   "/NOMEM"    - Signals SCAN that it should not do a memory scan which is
                 not necessary for the scanning that DataView does.

   "/NOEXPIRE" - Signals SCAN that it should not give you "Are you sure you
                 want to continue" prompt after your version of SCAN has
                 expired.

   "/NOPAUSE"  - Tells SCAN that we don't want any pause prompts,
                 especially for for online interactive BBS use! :)

   "#PATH#"    - DataView translates this parameter out to the full
                 pathname of where it extracted the files to for scanning.
                 Note that this paramter must be in UPPERCASE.

   Please also make sure that you put a directory in front of your command
   line specifying where SCAN.EXE is located. For example, I keep my copy
   of SCAN.EXE in a directory called "C:\SCAN\". The virus scan command
   line on my BBS looks like this:

   C:\SCAN\SCAN.EXE /NOEXPIRE /NOMEM /NOPAUSE #PATH#

   Your scan command line should look exactly like the one above except
   that the directory in front of SCAN.EXE may be different.

   NOTE: If you don't want to allow virus scanning on your BBS, then simply
   leave the virus scan command line blank, and DataView will disable the
   feature entirely.

4. MAX READ LINES: This field is a numeric field which specifies the
   maximum lines that a user may read in a text file. This is useful if you
   want to prevent users from reading text files when they should just
   go download the thing. As an example, I have source code for various
   programs on my board, and at times (before I added this feature) users
   would go into DataView, turn their capture on, and read all of the
   text files in the archive. This way they got a free download in a
   sense. :)

   Setting this field specifies the maximum lines that a user may read in
   a text file which would prevent situations like the one described above.
   Normally, you probably would not want to limit the reading of text
   files, but in the event that you do, the option is there.

   To disable this feature, simply leave the field blank, or specify the
   value zero. Disabling it will let the user read as many lines in a text
   file as they like.

5. BBS ID NAME: This is an ID name that DataView will use when creating
   archives. DataView's download feature allows creation of new archives
   for download, and naturally when it creates a new archive its got to
   have a name. :)

   DataView uses this BBS id as the filename for the archive. However,
   DataView also adds a 3 character number to this filename so that if the
   user does multiple downloads through DataView they will not have the
   same filenames ...hence the reason for the BBS id being 5 characters
   instead of 8.

   As an example, if your BBS id was: "DATAV" (thats the default), then
   DataView would create archives that started with:

   "DATAV" + FILE NUMBER + "." + ARCHIVE EXTENSION

   Here's a couple examples:

   DATAV001.ZIP - First download through DataView
   DATAV002.ZIP - Second download through DataView, and so on ...
$
EDIT ARCHIVER COMMAND LINES
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
On this archiver edit screen, you've got a list of all of the archiver
command lines that DataView uses for its various features. There are
archiver command lines for the folling functions:

1. Extracting files
2. Archiving files
3. Integrity scanning
4. Deleting files in archives
5. Adding files to archives

Normally, you would not want to modify these command lines because the
default command lines are setup exactly to work with DataView. The only
reason that you might have to change one of these command lines would be if
(for instance) a new version of PKZIP came out which used different
parameters.

Now, before you stop reading this, there is one important thing that you've
got to do with these archiver command lines! :) It is very important that
you specify a directory where these archivers are located in front of the
command lines. This is not 100% necessary, but for security reasons, its a
very good idea that you do so.

If DataView can find your archivers in the Path, it will do this for you
automatically, otherwise you will have to specify them manually. Here is an
example. Lets say that your ZIP extract command currently looks like this:

PKUNZIP -o #ARCHIVE# #FILENAME#

Now, lets say that you have your copy of PKUNZIP.EXE in a directory called:
"C:\UTILS\". Knowing that, you would want to modify your archiver command
line to look like this:

C:\UTILS\PKUNZIP -o #ARCHIVE# #FILENAME#

That command line is exactly like the previous one except that its got the
"C:\UTILS\" directory in front of it. Thats the only necessary change. You
must do this with ALL archiver command lines on the archiver entry screen.

You might also notice that some of the archive command lines for creating
archives have a "@" or a "!" in front of them. Those are supposed to be
there, do not delete them. Those characters mean that the following
filename is a list file which is a text file containing file names. This is
the way that DataView creates archives. So whenever you see one of those,
it means that the "#FILENAME#" parameter is actually a text file that
contains filenames of other files. Knowing this is not really important,
but I thought I'd just mention it since people have asked me about the "@"
and "!" before. :)
$
DOWNLOAD SECURITY SETUP
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This screen simply contains a picklist of security levels. You should go
through and mark all security levels which have access to download files
through DataView. If you want to disable the download feature in DataView,
then just don't mark any security levels.

The download feature will allow users to download individual files from an
archive seperately, or create their own archives consisting of files in the
archive that they are viewing. This is very useful when you only want to
get certain files from the archive, such as the documentation files or
something like that.

However, even though this feature may be useful, a lot of shareware authors
don't like to have their archives split into multiple pieces like that. You
might also have users thinking that they can get free downloads through
DataView or something. What security levels will have access to download
through DataView will be up to you. Most people do one of the following:

1. Give all users access to download through DataView.
2. Give only registered users access to download through DataView.
3. No one has access to download through DataView except the Sysop.

For my personal use, I let all users download through DataView except the
REALLY low security levels. DataView *DOES* perform full ratio checking and
daily download limit checking.
$
SYSOP SECURITY SETUP
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This screen is another picklist almost exactly like the one for the
download security setup. In this picklist, you should go through and mark
all security levels which you want to have SYSOP access in DataView. Having
SYSOP access in DataView allows the user to delete files from the archive
and add files to the archive from the local hard drive.

This feature is especially useful for Sysops who like to go through and
delete the mess of BBS ads and such that build up in archives.

The Add feature is good for Sysops that would like to add their own BBS ads
or any other files to the archive.

Now, be careful that you do not give general users SYSOP access in
DataView, these are very powerful features which you would definitly not
want your users to have access to.

On my BBS, the only people that have access to the Sysop features in
DataView are myself and my file sysop (who manages the files on the BBS).
$
End of help file.
