home *** CD-ROM | disk | FTP | other *** search
-
- ------------------------------
- Motor City Software
-
- File Request Door
- Configuration
- Editor
-
- MCFREQED.EXE
-
- Version 2.00
- Beta #1
- ------------------------------
- Copyright(c) 1990,1991 - All Rights Reserved
- Motor City Software
-
-
-
- Introduction
- ------------
-
- {* NOTE *} If you are ugpgrading from version 1.45, then you
- simply run McFreqEd and fill in the new fields. If
- you are upgrading from a previous release, then
- then you will need to delete your MCFREQ.CFG and
- MCFREQ.SYS and re-enter the data. Also be sure to
- delete the *.PND file.
-
-
- MCFREQED is the program used to create and modify the data
- files used by MCFREQ, the File Request Door. You MUST run
- this and create the data files in order for the File Request
- Door to run.
-
-
-
-
- Operation
- ---------
-
- When you run MCFreqEd, you will see the opening screen. Hit any
- key, or mouse button.
-
-
- Menu Layout
- -----------
-
- The Main system of PullDown menus is laid out as
- follows:
-
-
- MCFreq Info This System Other Systems Maintenance Exit
- ----------- ----------- ------------- ----------- ----
- Credits Miscellaneous List Systems List Pending Exit & Save
- Registration Outbound Info Add Systems Kill Pending Exit & Abort
- Inbound Info Delete System Kill Recieved
- Security Edit System Re-Request File
- Multi-Node Get File Lists
- Verify Paths View User Files
- Menu Setup View Inbound
-
-
-
- Use either the mouse or your Cursor Keys to move around this menu.
-
-
- Each menu option Is Explained Below:
-
- MCFreq Info
- -----------
-
- Credits
- -------
- Simply displays the names of the programmers, and the copyright
- notice. Hit Any Key to return to Menu.
-
- Registration
- ------------
- This screen shows information on to register your copy of MCFreq
- This includes the price, and the address. Hit Any Key to return
- to the Menu.
-
-
- This System
- -----------
- All Information Entered here is stored in Memory until you Exit.
-
- Miscellaneous
- -------------
- This is where you enter and modify general information about
- your bbs. An input screen is drawn, and you simply use the
- arrow keys to move around through the input fields. When all
- the information is correct, hit F10 to exit this screen.
-
-
- Sysop Name :
-
- Your Name goes here. This field will be used if
- you run MCFreq in local mode.
-
-
- BBS Name :
-
- Enter the name of your BBS. This is also used if
- you run MCFreq in local mode.
-
-
-
- Network Address Zone : Net : Node : Point:
-
- Example: 1:229/418.0
-
- Zone : 1
- Net : 229
- Node : 418
- Point : 0
-
- This is your FidoNet Address (or any net you
- belong to)
-
-
- Path\Filename To Your File List:
-
- You enter the full path and filename to your
- own list of files. This is used to verify that
- users are not requesting files that you already
- have on your system. When the user finds a file
- on another system, MCFreq will scan this file
- for a match. If a match is found, then the user
- will be told that the File Request was Aborted
- because the file already exists on your system.
-
-
- FULL Drive:Path to DorinfoX.def:
-
- This is the path to your DorinfoX.Def file which
- is usually created in your bbs directory. McFreq
- can also read a GAP or DOORWAY style Door.Sys
- This path can be over-ridden on the command line
- in MCFreq. See MCFreq.Doc for details.
-
-
- Force McFram To Scan NetMail? :
-
- If your system takes a long time to scan for
- matching filenames on a request, and the other
- mailer keeps timing out, you may force McFram to
- scan netmail for messages addressed to McFreq.
- This way, other systems simply address the
- message to MCFREQ, and list each file they wish
- to request on a seperate line with a \ in front
- of the name. (See McFram.Doc for details) The
- other system sends this message to yours, they
- hang up, and McFram scans the netmail, and then
- searches for the files on your system. It places
- the files on hold, and the other system may poll
- back immediately to get the files. The system
- doing the file request does not need to be using
- McFreq to make use of this feature.
-
-
- Drive:Path\Filename of Freq List:
-
- This should point to a file which contains a
- list of your directories that hold files avail-
- able for file request. The format of this text
- file is as follows:
-
- c:\files\uploads\
- c:\files\utility\
- c:\files\games\
-
- This file may contain any number of directory
- names. Note the trailing backslash, all lines
- start flush with the left column, no leading
- spaces are permitted. These directories will be
- searched by McFram to find matching files to be
- put on hold for the other system. This is only
- used if you tell McFram to scan the netmail area
-
-
-
- Maximum Matches To Send:
-
- This number will limit the number of files that
- another system can request in one message to
- McFreq. A 0 will not allow ANY requests.
-
- Maximum Size to Send:
-
- McFram will add up to total size of all files
- that are put on hold for a system. If the total
- size is greater than this number of KBytes, then
- no more files will be allowed.
-
-
- OutBound Info
- -------------
-
- Netmail :
-
- This is the full path to your OUTbound netmail
- message area. When the user requests a file
- from another system, MCFreq will create a net-
- mail message to the other system. This netmail
- message is the file request. MCFreq creates this
- ?.MSG file in this directory where your mailer
- will find it.
-
-
- Files Path :
-
- This is where MCFram will expect to find files
- that have been requested. When your mailer does
- the file request, it should place all recieved
- files in this directory.
-
-
- Inbound Info
- ------------
-
- File Area :
-
- This is just a text description to help the user
- find the file area which contains the files he
- requested. This should be the same as you have
- it defined for your bbs.
-
- Example: New Files Via Requests
-
-
- File Path :
-
- This is where MCFram will move the inbound files
- This should be a directory that is available to
- the users, so they can download the files once
- they are received.
-
-
- Files.BBS :
-
- This is the full path to the name of the file
- description file. It should normally be the same
- path as File Path but will also contain the file
- name as well. Usually this is FILES.BBS, but we
- made it configurable in order to take advantage
- of Remote Access's ability to store the file
- descriptions in any directory.
-
-
- Msg Path :
-
- This is the path to your message base that
- MCFram will write the user notification messages
- in. This message is written to the user when his
- file arrives.
-
-
- Msg Type :
-
- This is the TYPE of message to write to the user
- MUST be one of the following:
-
- R - Remote Access
- Q - Quick BBS
- F - Fido compatable .MSG
- N - No Messages to users
-
- Msg Board :
-
- If you are using R or Q as the TYPE, then you
- must supply the message base number that you
- want mail written in.
-
-
- Security
- --------
-
- Sysop Level :
-
- It is VERY IMPORTANT that you set this to a high
- enough level that your users cannot access the
- SYSOP REQUEST (See Below) Sysop request allows
- the user to request ANY file from ANY system,
- even if you do not have it configured... This is
- the ONLY unrestricted request available. It will
- create a message, and if your mailer is set to
- dial anywhere, then the request will go. This
- field is also used as your security level when
- you run MCFreq in local mode.
-
-
- Max Requests Per Day Per User :
-
- You may specify a 0 here for unlimited requests
- per day. A 2 will limit each user to a maximum
- of 2 file requests each day. This rolls over the
- first time MCFreq is run after midnight.
-
-
- Level For Unlimited # Requests :
-
- Any user with this level or higher will not be
- limited by the above requests per day limit.
-
-
- Level For Unverified Requests :
-
- Any user with this level or higher will be able
- to request ANY file from the systems you have
- configured. No Checks are done to ensure that
- the file does not exist on your system, nor
- does it check to make sure it is available from
- the other system. The user is prompted whether
- or not they wish to search the other systems
- list, and if they choose not to, then they will
- be required to enter the description themselves
-
-
- Level To Allow Re-Requests :
-
- A user with this level or higher will be able
- Re-Request files that they have previously
- requested, but have not yet arrived. This has a
- security level because no checks are made as to
- when the file was last requested. A user with
- this level could fill your netmail directory
- with file requests for the same file.
-
-
- Disallowed Extensions :
-
- Users will not be allowed to request any file
- with an extension that matches one of five that
- you may configure here. This way you can keep
- your users from requesting tons of GIF files or
- whatever.
-
-
- Use Log Files? :
-
- This allows you to specify whether you want
- MCFREQ and MCFRAM to keep log files. It is
- advisable to keep logs at least until you have
- everything working properly.
-
- MultiNode
- ---------
-
- Special Note: Even though you may not be running multi-node,
- you should still enter then information on this
- screen.
-
- Running Multi-Node BBS? :
-
- Yes, if you run more than one node, No if not.
-
- Mailer Running On Node # :
-
- If you are running a multi-node system, you can
- specify the node number on the commandline when
- you run MCFREQ. If the mailer node is available
- when a user on another node requests a file,
- MCFREQ can force the mailer to rescan for any
- outgoing netmail. (See Below)
-
-
- Type Of Mailer :
-
- Set this to FD for FrontDoor, DB for D'Bridge
- Leave blank if not either of the above. This is
- only used so MCFreq can force the mailer to re-
- scan netmail.
-
- Force Rescan On File Requests :
-
- If this is a Y then whenever a file request is
- made via MCFREQ or MCFREQED, the mailer will be
- forced to rescan for outbound netmail. This
- will force the file requests to be processed at
- once. Again, this is only useful in a multinode
- setup.
-
-
- Path To Mailer :
-
- This is the full path to your front end mailer.
- MCFram will also store its In-Transit-Request
- packets here. They are .MCF files, and MCFram
- will remove them when they are no longer needed
-
-
- Force Dorinfo1def on nodes :
-
- If you run a multi node system, you can set this
- to Y for Yes. This will mean that all nodes will
- read a file called Dorinfo1.Def rather than the
- node number. See MCFreq Docs.
-
-
-
- Verify Paths
- ------------
-
- This will verify each of the paths and filenames
- entered above. If there is a bad one, a window will
- pop up with the problem indicated. If there are no bad
- paths, then nothing will happen. If there is a bad
- path, you can re-edit it with the above screens.
-
-
-
- Menu Setup
- ----------
-
- This is a new addition to McFreq V2.00 You now have the
- ability to define your own hotkeys and Prompts. While a
- lot of it is still hardcoded into McFreq, you may design
- your own menus if you are registered. See McFreq.Doc for
- complete details
-
- The following Fields take one character, this is the key
- to activate the command specified.
-
- [ ] Help File Display
- [ ] List Other Systems
- [ ] Keyword File Search
- [ ] View Other File Listings
- [ ] Request A File
- [ ] Quit To BBS
- [ ] Pending File Re-request
- [ ] Sysop Request
- [ ] ANSI Graphics Toggle
- [ ] List Users Online (RA1.xx QBBS2.75 Only)
- [ ] Read Online Message (RA1.xx QBBS2.75 Only)
- [ ] Send Online Message (RA1.xx QBBS2.75 Only)
- [ ] Goodbye (Hang Up)
-
-
- Prompt :
- You may redefine the prompt that McFreq uses at
- the Main Menu. If you put a tilde (~) in this
- string, it will show up as the users remaining
- time.
- Example : ~ Min. Command =>
-
- will show 43 Min. Command =>
-
- CR :
- This will be used in place of the Hit RETURN to
- Continue.
-
- TxtFile:
- This is the path to your text files directory.
- If you are a registered user of McFreq, then you
- may design your own menus, and other ANS/ASC
- screens to be used in place of internally hard-
- coded screens.
-
- M Menu :
- If you wish to create your own main menu display
- then create the file in the TxtFiles directory
- using your favorite ANSI/ASCII editor. Enter The
- name of this file here, without any extention.
- You must at least have a .ASC file.
-
- ListHdr :
- This file will be displayed instead of the hard-
- coded display at the top of a list of systems.
-
- Other Systems
- -------------
-
- This is information on the systems which you will be doing file
- requests from.
-
- List Systems
- ------------
-
- Simply pulls up a window and lets you scroll through a listing
- of the systems you have configured. Hit RETURN to exit the
- listing, scroll up and down with the ARROW keys.
-
-
- Add System
- ----------
- You can enter all the information on this screen, and when you
- are finished, press F10 to exit. You will be prompted whether
- you wish to save this information. If you simply hit RETURN then
- the info will be saved.
-
-
- Sysop Name :
- Enter the name of the Sysop of the BBS
-
- BBS Name :
- Enter the name of the BBS
-
-
- Network Address Zone : Net : Node : Point :
-
- Example: 1:229/414.0
-
- Zone : 1
- Net : 229
- Node : 414
- Point : 0
-
- This is the other systems NetWork Address.
-
-
- Path\Filename To File List :
-
- You enter the full path and filename to that
- BBSs list of files. This list is created by most
- systems daily to keep their list up to date. Try
- to keep a fairly recent one if you can.
-
-
- Password For Freqs If Used :
-
- If you are requesting from a system that
- requires a password for file requests, then
- enter the password here. If not, then just
- leave it blank.
-
- NOTE: If you add a password, be sure to also
- include the field seperator used by your mailer.
- FD uses ! Check your mailer docs for the
- correct one.
- EXAMPLE: !password
-
-
- Send Msg to McFreq?
-
- This will allow file requests to systems that
- have a problem handling regular file requests.
- For instance, on a system with MANY files it can
- take some time to scan all directories to find
- the files. If your mailer times out waiting for
- the other system to find the files, and that
- system is running McFram, then set this to Yes.
- This will force McFreq to send a NetMail message
- addressed to MCFREQ, rather than a file request
- message. Your mailer will deliver this message,
- and then hang up. When the other system runs
- McFram ( usually on all incoming mail ) then
- McFram will scan its netmail directory, and when
- it finds a message to MCFREQ, searches for the
- files requested, and places them on hold for you
- The other system MUST be running McFreq V2.00 or
- greater for this to work.
-
-
- BBS Phone Number :
-
- Enter the phone number for the BBS. This will be
- displayed to the users.
-
-
- User Level :
-
- This is the level needed by the user in order to
- access this bbs via file requests. If the user
- does not have high enough security, then they
- will not even be aware that this bbs is listed.
-
-
- Description Start Position :
-
- Look in the files list that you have for this
- BBS and see what column number the descriptions
- start at. This is configurable because some
- lists contain file dates, and some do not.
-
- Maximum Freqs/Day :
-
- If this system has a limit set, or you wish to
- limit the number of Freqs/Day from this system,
- just enter the number here. A 0 will allow
- unlimited requests. If the Maximum number has
- been reached, the user will be informed of this
- and MCFreq will not allow the request. Sysop
- level WILL allow you to override this.
-
- Routing Address :
-
- NOTE: DO NOT LEAVE THIS FIELD BLANK OR 0's
-
- Please see Route.Doc for more info. If you are
- not routing requests for this system, then
- enter the same address as entered above.
-
- PassThrough :
-
- If this is set to Y for Yes, then other systems
- will be able to route their requests through you
- to this system. If you set it to N for No then
- your system will refuse to forward the request,
- and will notify the sysop of the Requesting
- system that you do not allow Request Routing for
- this system. This is important if you have a
- system configured for your requests that is long
- distance. Routed requests DO NOT take into
- account security levels.
-
- NetMail Attributes :
-
- Two Attributes are preset, Local is turned ON,
- and FileRequest is ON. These MUST be ON so it
- seemed logical to hard code them. The Following
- are configurable by you:
-
- P - Private This will mark the message as a
- private message to the sysop.
- C - Crash This will force the mailer to send
- the file request to the other bbs now.
- K - KillSent Once the request has been sent the
- mailer will delete the message.
- H - Hold Mark the file request message for
- HOLD. It will hold it until the other
- system calls you, or you connect for
- other reasons.
-
-
- Baud Rate :
-
- Enter the systems highest baud rate here. This
- is Not used, other than being displayed to the
- user.
-
-
- File List Name :
-
- This is the name of the systems file list. You
- may specify a MAGIC name here if you wish,
- unless you are routing through another system to
- get to this one.
-
-
- Delete System
- -------------
- First, all systems configured will be listed in a window. Simply
- use the ARROW keys to move to the system you wish to delete. Hit
- SPACE BAR to tag this system for deletion. Hit RETURN to delete
- tagged systems.
-
-
- Edit System
- -----------
- All systems will be listed in a window. Hit RETURN on the system
- you wish to edit. Information will be presented on your sceen
- exactly like the Add system screen. (See Above)
-
-
- Maintenance
- -----------
-
- List Pending
- ------------
- This will open a window and list ALL files which have been
- requested. It will also show the Status of that request.
-
-
- Kill Pending
- ------------
- This will remove the records of unrecieved files from the
- Pending file. This is useful if a file was requested from a
- system, and that system does not have the file available for
- some reason.
-
- Kill Recieved
- -------------
- This will remove the records of recieved files from the Pending
- file. This needs to be done from time to time in order to keep
- this file from growing too large. You will still have the .LOG
- file for reference if it is used.
-
-
- Kill Recieved (Cont'd)
- ----------------------
-
- This is the only function that can be run automatically with a
- command line parameter. If you put MCFREQED P in your nightly
- batch maintenance file it will pack the pending file without you
- needing to remember.
-
-
- Re-Request File
- ---------------
- This will scan the pending file, and display a list of files
- that have been requested, but not recieved. You can TAG any of
- these files using the space bar, and when you exit this screen,
- new file requests will be generated, and force the mailer to
- rescan if rescan is forced ON.
-
-
- Get File Lists
- --------------
- This will bring up a list of ALL the systems you have configured
- Cursor through the list and TAG systems by hitting the SPACEBAR.
- You may tag as many systems as you wish, and then hit RETURN.
- MCFreqEd will then create a file request for each system, and
- force the mailer to rescan if rescan is forced ON.
-
- NOTE - This will create a file request DIRECTLY to the specified
- system. Request Routing is NOT supported in this function.
-
-
- View User Files
- ---------------
- This brings up a window that contains the directory listing for
- your users download directory. Space bar toggles between two
- layouts. You can also move between directories.
-
-
- View Inbound
- ------------
- Same as above, but for the directory where your mailer puts
- Inbound files.
-
- Exit
- ----
- Exit & Save
- -----------
- Exit the configuration program and SAVE the information you
- entered in the 'This System' area.
-
- Exit & Abort
- ------------
- This will exit the configuration program, and WILL NOT Save the
- information entered in the 'This System' area.
-
-
- 3. Operational Notes.
-
- The systems that you add should be made aware that your users will be
- making file requests from them.
-
- MCFREQ will create a netmail message in the .MSG format used by Front
- Door in your specified NETMAIL directory.
-
-
- 4. Copyright, Disclaimer, Etc.
-
- MCFREQ, MCFREQED & MCFRAM are copyright 1990,1991 by Motor City Software
- ALL RIGHTS RESERVED You are granted permission to use these programs for
- a period of 30 days to evaluate the product. You may also distribute
- them freely in unmodified form along with all documentation so long as
- you are not charging money for this specific product.
-
- I make no claims about these programs except that I have done everything
- possible to make sure it does not do any harm to your system, and that I
- am running it here myself, and have had no problems.
-
- These programs ARE NOT Public Domain, but Shareware. This means you will
- be expected to register the software if you find it Useful. See the
- Register.Doc file for more up to date information. Failure to do so is a
- direct violation of this license agreement.
-
-
- 5. Contacting the Author.
-
- Any problems, Bug Reports, or comments should be directed to:
-
- Rod Hancock
- Motor City Software Online
- Oshawa Ontario Canada.
- (416)579-6318
- 1:229/418 FIDO
- 89:485/207 IMEX
-
- Voice Support is available between the hours of 9am and 9pm
- (EST) Monday thru Saturday at (416) 579-3256
-
-