BL> 1. Check/accept files
BL> Check the inbound for .TIC
BL> Read file name and check that the file exists
BL> Read the point name, password, and area.
BL> Check the password, and area access.
BL> Move the file to the correct directory.
BL> Add the file details in a line on the end of the FILES.TXT
This is not what TIC does at the moment, it just adds it to the FILES.BBS at the end.
BL> Add the name and date to "LATEST FILE" field in header
Current operation is to get the name and date when creating the file list.
BL> This could be done online, which means the next caller could get the
BL> file rather than wait overnight.
That is what happens now. You can FREQ something straight away. What you
can't do is get an updated files list, because that only happens once/day.
Although now that it's so fast, maybe I should add that.
BL> 2. Update FILES.TXT
BL> Read a directory (starting at #1) for list of file names.
BL> Sort names
I don't think there is any requirement for this.
BL> Read FILES.TXT, copy section header.
I don't think you should read the input from an old output, it should be
read from another file. Just specify that I have to pass a file with a
header in it as parameter 1.
BL> Find same name, copy that line to new FILES.TXT
BL> If no name in FILES.TXT add a new line with no description
Current practice is to generate the lot from scratch. That's not a
problem, and should be simpler and safer.
BL> This will create an updated FILES.TXT that conforms to the actual
BL> directory on disc, sorted alphabeautifully. If you start from scratch
BL> with no previous FILES.TXT it will knit one with no file descriptions.
BL> I'll always keep the old one as a backup, just in case. I have to read
BL> right through the file anyway, but in most cases the files will be in
BL> order with minimal file pointer movement, and it'll be a straight
BL> copy.
Another thing is that I will sometimes add a file (like CVS19.ZIP) by
myself, by editting files.bbs directly.
BL> The bit I don't like is that your FILES.TXT has sections numbered,
BL> and I need to keep a master list of numbers, real directory names, the
BL> names you use in the list... plus the names you use in the TIC. It is
That is kept in a different file, I'll post an excerpt from that file.
BL> too easy to screw up. Did I ever tell you what a hopeless engineer you
BL> are? To make it worse, there is nowhere in FILES.TXT I can read the
BL> number, with those fancy ascii-art numbers.
Forget fancy art. Bear in mind that this is a competition between dir
c:\bbssoft, dir c:\pdomain etc and your program.
Here is where my area definitions are. This actually gets compiled into
another file, which is what downsort uses, but this file can be used
equally as well. BFN. Paul.
% -----------------------------------------------------------
% FILEAREA.CTL -- a sample file area control file for Maximus
% -----------------------------------------------------------
%
%
% This file contains all of the information about your system's message
% areas. Each file area can be given a name. This name consists
% of letters, numbers, and any of the following characters:
%
% . / _ ~ ! {at} # $ % ^ & * ( ) - + = |
%
% File area names can be up to nine numbers or letters long. If you
% wish, you can use numbers for area names, such that you'd have
% area names like "1", "2", "3" and so
forth. However, it's usually
% easier to give each area a short name which is easily remembered.
Area 0
% FileAccess specifies the priv level required to access this
% file area.
FileAccess Sysop
% `FileInfo' specifies the name of the file area, as it will
% appear to the user.
FileInfo Unchecked uploads
% `Download' specifies the DOWNLOAD path for this area. This
% directory should contain FILES.BBS and all of the files to
% be made available.
Download File\Uncheck
% `Upload' specifies the UPLOAD path for this area. This directory
% tells Max where to place files which are U)ploaded into this area.
%
% You will usually want to handle uploads one of two ways:
%
% 1) Validation required. All "Upload" paths will point to the
% same, private directory. This directory will have SysOp
% access only, and those files must be moved to the main
% file areas manually.
%
% 2) No validation required. All "Upload" paths will point to
% the current "Download" path. Files uploaded in this manner
% will be automatically placed in the file directory for
% each area, and users will be able to access those files
% right away.
%
% The default configuration uses the validation method, such that
% all files will be uploaded to file area 0.
Upload File\Uncheck
% This tells Maximus that the area is barricaded, and that
% access can be controlled by the user's name or by a
% password. Please see MAX_REF.PRN for more information.
% FileBarricade
% This tells Maximus to use an alternate file area menu
% name while the user is in this area. This can be used to
% show certain options for one area only.
% FileMenuName
% This option can be used to adjust the privilege level of
% a menu option for one file area only. Please see
% MAX_REF.PRN for more information.
% FileOverride
% If the FILES.BBS-like catalog for this area does not
% reside in the same directory as the files themselves,
% you can specify the path and filename of the file
% listing for this area. This feature is especially
% useful for CD-ROMs.
% FileList
End Area
Area 1
FileAccess Disgrace
FileInfo Stuff required for FREQing/pointing
Download C:\MINPOINT\
Upload File\Uncheck\
End Area
Area 3
FileAccess Sysop
FileInfo BBS Related Stuff
Download C:\BBSSOFT\
Upload File\Uncheck\
End Area
@EOT:
---
* Origin: X (3:711/934.9)
|