home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
OFFLINE
/
QWKRQ10.ZIP
/
QWKREQ.DOC
< prev
next >
Wrap
Text File
|
1994-01-09
|
48KB
|
1,058 lines
───────────────────────────────────────
╗ ╔
║ ║
╠═══╣╒══╕╞══╕╒══╕╒══╕╤══╕
║ ║╒══╡│ ││ │╒══╡│
╝ ╚╘══╛╛ ╛╘══╡╘══╛╧
└──┘
ONLINE SERVICES
───────────────────────────────────────
QwkRequest Version 1.0
An Automatic File & Information Request Program
for AutoReq
Copyright (C) 1993,1994 by Jason Hyland and
Hangar Online Services
19 Chantry Drive, Worle, Weston-Super-Mare, Avon. BS22 OPP.
BBS (44) (0) 934 511751
All Rights Reserved
QwkRequest v1.0 WHAT IS IT ?
─────────────────────────────────────────────────────────────────
What Is It ?
You know what its like when you use a BBS for mail and on the odd
occasion you require a file. Or when you just want to view one of
the Bulletins, or grab a list of conferences available. You have
to log into the BBS manually and search for the file then download
it, or if its a bulletin, you need to capture the screen. This can
be a real pain at the best of times, especially if you use an
automated mail run script / program, or are just terminally lazy
like me ! Well thanks to AutoRequest (see later) and QwkRequest,
you now have no need to !
QwkRequest allows you to browse or search a BBS File List and tag
files for download. You can request to be sent a message containing
a list of conferences, or request a bulletin. If the SysOp of the
BBS you are requesting from has provided you with a '.MGC' file
for his system, you can request virtually any information about the
BBS or your account (subscription details, current download ratio,
logins etc).
QwkRequest generates specially formatted requests to AutoRequest in
a standard format REP packet (appending to any existing replies
you may have). You can then upload your REP packet as normal.
Most BBS's running AutoRequest will process your requests once
a day (The Hangar BBS processes requests at 6am). Normally your
requested files or information will be available in the next QWK
packet you download.
Some of the features you'll find in QwkRequest;
o Easy to use and consistent user interface
o Smooth integration with SLMR and OLX
o Work easily with ALL QWK/REP format Offline Mail Readers
o Appends to any existing REP packets
o Can run standalone without an OLR
o Multiple BBS File Lists Supported
o Fast indexed databases provide quick access to file areas
o PKZIP/PKUNZIP and ARJ compression supported
o Fast searches across multiple areas
o Password protected files are requestable
o Context sensitive help
o Request up to 50 files in one REP packet (registered)
o Fully supports AutoRequest 'Automated Information
Service' and 'Magic Requests'
o Configurable colours (can use OLX/SLMR colours)
.... and there are plenty more !
QwkRequest v1.0 WHAT IS AUTOREQUEST ?
─────────────────────────────────────────────────────────────────
What Is AutoRequest ?
QwkRequest came about because of the excellent and innovative
program produced by Adam Stevens at AddTech Consultancy Ltd for
Wildcat! SysOps called AutoRequest (AutoReq). Adam describes
Autorequest as;
"........ a WildCat! 3.xx SysOp utility which enables
users to download requested files automatically within
their TomCat QWK packets. All the user needs to do is
send a message to a user called "FILE REQUEST", with
the name of the file he wants to receive in the subject
line."
but it also allows;
".... the Sysop to configure AutoRequest so that the user
just has to send a message to FILE REQUEST with a subject
line beginning with a forward slash to automatically
receive, as a message, any text file you want to make
available."
AutoRequest runs on your SysOp's BBS normally once a day. Some
BBS's will run Autorequest much more - it depends on how many
requests are generated and is controlled by the BBS SysOp. If your
SysOp doesn't currently run AutoRequest, QwkRequest will be of no
value to you. But then again, if your SysOp _isn't_ running
AutoRequest, do you really want him to stay as your SysOp ?
Full details on where you or your SysOp can obtain AutoRequest are
available in the REGISTER.DOC file within this archive.
QwkRequest v1.0 USER INTERFACE
─────────────────────────────────────────────────────────────────
User Interface
QwkReq has been designed to provide a clear and easy user interface.
Many of the keys used are "common standards". Windows (or as I've
now grown to call them - "picklists") provide the standard display
method. Each window has a "title" in the top left hand corner
which describes what is contained therein. All windows are scrollable.
This means that what you see on the screen is just a "window" on
the data - if the data in the window (a list of files for example)
doesn't fit, you can scroll though the data.
The last line displayed on your screen will always display the
key you need to press to get context sesitive help. This "status"
line also displays some other useful information;
BBS Id - Displays the BBS Id that the current File List is
from, and the BBS Id that will be used when generating
requests.
Request - Requests from this file list will be entered in the
Conference conference displayed here. You should check with
your SysOp what conference to use.
Some keys are common to ALL windows which allow you to select
data. These keys are;
F1 - Context sensitive help. Each window has different
functions, and therefore different keys perform
different actions. Pressing F1 will display a list
of the keys and their uses in the current window.
F2 - About. Displays the "About" screen which shows
current version and support contact details.
Down - Move the selection bar down one item in the
Arrow current window.
Up - Move the selection bar up one item in the
Arrow current window.
Page - Move the selection bar down one page in the
Down current window.
Page - Move the selection bar up one page in the
Up current window.
Home - Move the selection bar to the first item in the
current window
End - Move the selection bar to the last item in the
current window
Most windows also include a rudimentary "search" option. For example
in the files window (which lists all files for a selected area),
pressing "P" will move the selection bar (starting at the current
position) to the next item starting with "P".
QwkRequest v1.0 SYSTEM REQUIREMENTS
─────────────────────────────────────────────────────────────────
System Requirements
QwkRequest has been tested on a number of different machines without
problems, and runs fine on anything from an 8088 to a 486. Memory
requirement is very much dependent on the number of files contained
in the filelist. QwkRequest currently has an in built maximum of
2000 files per area. This is quite simply to prevent QwkRequest from
blowing out if a huge area is selected without enough free RAM. I do
intend to look at using EMS to remove this limit. I would suggest
that minimum RAM free to run QwkRequest is in the region of 400k.
QwkRequest has configurable colours, so will run fine on a colour or
mono monitor.
QwkRequest _requires_ that your compression / decompression programs
are accessible via your PATH environment variable, or they reside
in the _same_ directory as QwkRequest.
Before you can run QwkRequest, you will need at least one of the
following from the BBS that you wish to request files from;
o A BBS File List (Standard WCPRO format - speak to your
SysOp if you aren't too sure about this)
o A standard QWK mail packet from the Tomcat mail door.
You need the file list for obvious reasons. The QWK packet is
required because QwkRequest needs to know certain information about
the system that it is going to generate REP packets for.
If you are going to use the "Magic Requests" feature, you will need to
obtain the '.MGC' (or "MAGIC FILE") file from the BBS also.
Your SysOp can help provide you with all of these items if you have
a problem. Please don't contact me asking where you can obtain them !
QwkRequest v1.0 CONFIGURATION
─────────────────────────────────────────────────────────────────
Configuration
QwkRequest should be unpacked / installed into its own working
directory. Whilst it is entirely possible for it to run in some other
directory, it is far tidier and less prone to problems to install it
in its own directory, perhaps C:\QWKREQ (as is used in the examples
here).
Unpack the QwkRequest archive into the C:\QWKREQ directory. Make sure
that your compression / decompression programs are either in your
PATH environment variable, or in C:\QWKREQ.
If you are a registered user, copy your QWKREQ.KEY registration key
file into the same directory.
If you are an SLMR or OLX user read the following sections. If you
use other mail readers or intend to use QwkRequest as a standalone
program, skip to 'Other OLR / No OLR'.
SLMR / OLX Users.
QwkRequest has been written specifically with SLMR/OLX in mind. I have
tried to make QwkRequest integrate with these OLR's as seemlessly
and painlessly as possible. QwkRequest will read the configuration
file from either OLR and use the settings therein for the following;
o QWK Packet Directory
o REP Packet Directory
o Colours
For QwkRequest to read the CONFIG.MR or CONFIG.OLX configuration file
from these mail readers, it needs to know where your mail reader
configuration file is. QwkRequest uses the environment variable
"QWKREQ" for this purpose. For example, if your OLX mail reader is
installed in the directory C:\OLX you need to set the environment
variable as follows;
SET QWKREQ=C:\OLX\
This environment variable needs to be set _before_ running QwkRequest
and should normally be placed in your AUTOEXEC.BAT. If you fail to
set this variable, QwkRequest will look in its own directory for
the CONFIG.OLX / CONFIG.MR file. If the file is not found, QwkRequest
assumes default colours and the QWK & REP Packet directory to be
QwkRequest's own directory.
Changing the colours or packet paths in QwkRequest is simply a
matter of changing them within your mail reader !
Skip now to 'Creating a File List Database'
Other OLR / No OLR
QwkRequest doesn't _require_ a configuration file, but one will
normally be used. If you do not use a configuration file, QwkRequest
will assume default colours and the QWK & REP Packet directory will be
set to QwkRequest's own directory. This is not normally the case.
QwkRequest reads a config file in the current directory (or looks for
it in a directory pointed at by the QWKREQ environment variable) called
'CONFIG.MR'. This file is a text file which contains configuration
information. The following is an example of the CONFIG.MR file;
;
; Example CONFIG.MR File
;
QWK = C:\TELIX\DOWNLOAD
;
REP = C:\TELIX\DOWNLOAD
;
The above example simply set the QWK and REP Packet directory to
equal C:\TELIX\DOWNLOAD. This is where QwkRequest will look for
packets when you initially generate a file list database, and where
it will store request REP files.
Colour Definitions
The configuration file may also contain colour definition variables
which define the colours of various item on screen. These are;
BORDER = Windows Border
HEADER = Function Keys
SCROLL = Scroll Bars
HIGHLIGHT = Selection Bar
MESSAGE = Alert or Message Box
WINDOW = Windows Text
HELP = Help Display
STATUS = Status Bar
BUTTON = Options Buttons
Any of these may be used in the configuration file. Here's an
example of a black and white colour set;
;
; Black & White / Mono Colours
;
WINDOW = 0F
BORDER = 07
HEADER = 70
SCROLL = 07
BUTTON = 70
HIGHLIGHT = 70
MESSAGE = 70
HELP = 70
STATUS = 70
;
Colour values must be entered in HEX. The colour value is calculated
as follows;
color attribute value =
foreground color value + (16 * background color value)
Colour values;
Black = 00 Dark Grey = 08
Blue = 01 Light Blue = 09
Green = 02 Light Green = 10
Cyan = 03 Light Cyan = 11
Red = 04 Light Red = 12
Magenta = 05 Light Magenta = 13
Brown = 06 Yellow = 14
Light Grey = 07 White = 15
Therefore, a Yellow character on a Blue background would have a colour
attribute value of (14 + (16 * 1)) = 30. Just remember to convert
this number to HEX !
This is all the configuration that QwkRequest needs.
QwkRequest v1.0 CREATING A FILE LIST DATABASE
─────────────────────────────────────────────────────────────────
Creating A File List Database
QwkRequest reads a standard BBS file list and produces its own
'indexed' version in its home directory. After this database has
be created, the file list is no longer needed. New file lists from
BBS's already setup in QwkRequest can be used to overwrite and
therefore update a file list database.
If you have a '.MGC' file from your BBS, make sure this is now copied
into QWKREQ's directory.
If you were to execute QWKREQ now, you will be presented with a
message telling you that you can't run QwkRequest without applying
a file list first. This is what we need to do first.
Make sure that you have unpacked the file list - QwkRequest reads the
text file list, it cannot read the archived file.
Start QwkRequest with the full path / filename of the file list. For
example;
QWKREQ C:\DOWNLOAD\HANGAR.TXT
Please make sure that you specify the _full_ pathname to the file
list bbs - do not use directory defaults on other disks like
for example, C:HANGAR.TXT.
QwkRequest will now start. You are presented with a "picklist" and
asked to select a QWK packet from the BBS that the file list you are
using came from. If you cannot see a QWK packet for the correct
BBS, press ESCape to end QwkRequest, and recheck your configuration.
Note that the "BBS Id" has been updated to reflect the choice.
The required information will be extracted from this mail packet, and
you will then be asked to select a conference from the displayed
"picklist". This picklist displays all the conferences from the
selected BBS's QWK packet, and you are required to select the
conference that QwkRequest will use when generating REP requests.
It is important that you check with the SysOp which conference he
recommends using for requests - if you select the wrong conference
here it cannot be changed without recreating the file list database.
Some BBS's allow requests in any conference, others restrict you to
one specific conference.
Once you have selected the Request Conference QwkRequest will display
'HANGAR.TXT has not been applied before.'
and after you have pressed a key to confirm this message;
'The filelist HANGAR.TXT will be applied to BBS HANGAR'
(obviously the file list name and BBS name will reflect your BBS).
QwkRequest maintains a list of files it has processed in the past
and their BBS Id's. This is so that in a future version you will
be able to 'update' your database list with other more recent file
lists (or 'new files lists') without specifying a QWK packet. This
feature has not yet been implemented.
QwkRequest then displays that it is generating a file list database.
This can take sometime depending on the size of the file list. As
an estimate, it generates roughly 140 file entries per seconds on
a 25Mhz 386sx. Once this has finished you are taken straight into
QwkRequest's Main Screen. Press ESC to exit this for now.
QwkRequest generates 4 files for each filelist. These are;
BBS_ID.DAT - File List Database
BBS_ID.IDX - File List Database Index
BBS_ID.ARX - File List Area Index
BBS_ID.CNF - BBS Conference List
If any one of the first three of these files are corrupted or deleted
the whole database becomes unusable. Delete any remaning files for
this BBS and recreate the database.
QwkRequest v1.0 STARTING QWKREQUEST OUTSIDE AN OLR
─────────────────────────────────────────────────────────────────
Starting QwkRequest Outside An OLR
For now we will concentrate on getting used to QwkRequest in it's
'standalone' mode, that doesn't run within an OLR. See 'Integrating
with SLMR/OLX' for information on how to start QwkRequest within
your OLR.
QwkRequest can now be started up by just entering QWKREQ in the
QwkRequest Directory (although QwkRequest can be started outside
its directory if the its directory is in the PATH variable), without
specifiying a file list filename or switches.
QwkRequest Switches
QwkRequest has a number of switches that can be used to control
various settings within the program. To see what switches are now
available enter QWKREQ /? for a full list. The two switches that
are relevant in this mode are;
/o - Use original colours. Tell QwkRequest to ignore
any colour changes in your CONFIG file.
/c:xyz - Override the default conference for Requests, for any
BBS you may select. The conference is set the the
value 'xyz'
Starting QwkRequest
Start QwkRequest by entering QWKREQ in QwkRequest's own directory.
You will be presented with a "picklist" where you are asked to select
the database file list. Listed is _not_ the file list name, but the
BBS Id for that file list. If there is more that one database on
disk you may select which to use. Select by moving the selection bar
up and down, then pressing ENTER on the database to use.
QwkRequest will read the database and then open up its main "work"
windows. These are;
File Areas - This window lists all the file areas in the
database along with the number of files in each
area.
Tagged Files - This windows will list all the files that are
currently 'tagged' for download for this system
in the current REP packet.
Magic Requests - This window displays the default set of Magic
Requests, along with any from the BBS '.MGC'
file (obtainable from your SysOp).
QwkRequest v1.0 MOVING AROUND AND MAKING SELECTIONS
─────────────────────────────────────────────────────────────────
Moving Around And Making Selections
Navigating the Windows
Once you have entered QwkRequest's Main Work area with the three
standard windows displayed, you have a number of new keys available
to use. These are available in any of the three windows;
TAB - Use the TAB key to jump between the different windows
on the screen. The currently selected window will be the
windows with the selection bar visible.
F6 - Jump to the File Area's window
F7 - Jump to the Tagged Files window
F8 - Jump to the Magic Requests windows
F10 - Generate request for this BBS. This will generate the
specially formatted messages for AutoRequest, and write
or append them to your .REP file.
ALT&E - Manually enter a filename to request for download.
ESC - Quit QwkRequest to DOS.
Using the ESC option to quit with requests that have not yet be
generated will result in QwkRequest asking you if you need to generate
the requests before quitting.
Making Selections By Tagging
To select a file, move to the file areas windows and select the
area you wish to browse. Do this by highlighting the area with the
selection bar and pressing ENTER.
You will now see the File Selection window, displaying details about
all the files in the selected area. Details show here are;
File Name, File Size, File Date, Summary Description
If you wish to see additional information about the file (such
as the full description, number of downloads so far, last download
date,) highlight the appropriate file and press the SPACE bar.
To tag a file for download highlight the required file and press the
ENTER key. You will then be asked if you wish to enter a password for
this file. Some files in a file area may be password protected. If
you select a file for download that is password protected, and do
not give the correct password, AutoRequest will send you a message
telling you that the request has failed due to an invalid password.
Select Yes or No by either moving the box to the apropriate option
by using the RIGHT and LEFT arrow keys or the SPACE bar, or by
pressing 'Y' or 'N' key. Pressing ESC assumes that no password is
required.
Pressing ESC from the File Selection window will return you to
the File Areas window. You'll notice that any files you have tagged
will be displayed in the Tagged Files window.
Manually Entering A Filename
If you already know the filename of the file that you want to request,
you can use the Manual enter facility rather than browsing and tagging.
From any of the three main windows select manual entry by pressing
ALT & E.
You are asked to enter a valid filename, with a maximum of 12
characters. You will then be asked if you wish to enter a password for
this file. Some files in a file area may be password protected. If
you select a file for download that is password protected, and do
not give the correct password, AutoRequest will send you a message
telling you that the request has failed due to an invalid password.
You'll notice that the file you have entered will be displayed in the
Tagged Files window.
Deleting A Tagged File
If you have tagged a file by mistake, or just have changed your mind
about requesting it, you can delete the request. Move to the Tagged
Files windows, highlight the appropriate file request and press
the DEL key. The request will be deleted from the list.
QwkRequest v1.0 SEARCHING THE DATABASE
─────────────────────────────────────────────────────────────────
Searching The Database
QwkRequest offers a search facility to locate a particular file for
you. This search function is only available from the File Areas
window by pressing ALT & S.
QwkRequest will now ask the type of search you wish to perform by
asking 'Search just the filename (much faster) ?'. If you select
to search just the filename for the search text, QwkRequest performs
an index search which is far faster. Otherwise QwkRequest will have
to do a full database scan.
You are now prompted to enter a search string of no more than 20
characters. Case is not important - the search transends case.
A window similar to the Files Selection window is displayed. Whilst
QwkRequest searches the database/index, it will display "SEARCHING
FILES' in the window area. The window title will display the current
search string.
When the search has completed the files matching will be displayed.
This window now functions in an identical manner to the File
Selections window with the following exceptions;
F10 no longer functions as Generate Requests; ALT & E no
longer functions as Manually Request File.
Pressing ENTER for selecting a file for download, or SPACE to view
more information still function identically. Pressing ESC will
return you to the File Areas Window.
QwkRequest v1.0 GENERATING REQUESTS
─────────────────────────────────────────────────────────────────
Generating Requests
Simply having the files in your tagged list will not create the
requests. To generate the request messages, you must press the
F10 key from either of the three main windows.
When QwkRequest starts, it will read any current REP packet for
any current requests (either manual ones you have entered via
your OLR, or ones previously created by QwkRequest), and make
sure these are displayed in the Tagged Files Window.
When QwkRequest generates the request file, it will append to
any current replies packet you may have. This reply packet can
be a normal standard reply packet, with your replies contained
in it. Generating involves rewriting the .MSG file and then
repacking using a compression program.
If you try to quit QwkRequest with 'unsaved' requests you will
be asked if you want to generate the requests before exiting. The
default YES will generate the request REP packet then exit.
QwkRequest v1.0 INTEGRATING WITH SLMR/OLX
─────────────────────────────────────────────────────────────────
Integrating with SLMR/OLX
QwkRequest works very well on its own, but its even better with
SLMR/OLX. You do need to make a few changes to your SLMR/OLX
configuration, but I don't think its too taxing !
The way QwkRequest is integrated with SLMR/OLX is by asking if
you want to generate any file requests when you select a QWK
packet for reading from the main QWK Packet menu. Unfortunately due
to the way SLMR/OLX maintains a 'memory image' or REP replies,
it is not possible to run QwkRequest from withing SLMR/OLX when the
packet has been opened. If you do, unpredictable results _WILL_
occur !
Load up SLMR/OLX and select the configuration screen. Select the
'Packers' configuration screen. SLMR/OLX will display a list of
packers and the commands that it uses to execute them.
You need to select the UNPACKER for the unpacking program you
use. For example PKUNZIP. The unpacker option will normally say;
PKUNZIP !
and you will need to change this to;
QRUNZIP.BAT !
Save your config, then double check it !!
You now need to create the QRUNZIP.BAT file IN THE SAME DIRECTORY
AS SLMR/OLX. The batch file will look like this;
@echo off
REM
REM This batch file is used to intergrate QwkReq with OLX or SLMR
REM
REM Check if unpacking QWK or REP (REP unpacking passes 2 params!)
REM
if "%2"=="" goto RunQR
goto UZip
:RunQR
REM
REM Ensure that use specify the path to QWKREQ, and DO NOT change
REM directory to it !! Or stick QwkReq in the path ....
REM
C:\QWKREQ\QWKREQ /M:%1
:UZip
REM
REM Get on with decompression.
REM
PKUNZIP %1 %2
REM
REM End of QRUNZIP.BAT
You will obviously need to change the 'PKUNZIP' to 'ARJ e' if you
are using ARJ instead of PKUNZIP. Also make sure that the path to
QWKREQ.EXE is correct.
How it works
When you start SLMR/OLX and select a QWK packet for unpacking, you
load QwkRequest, passing the QWK packet name to it. QwkRequests will
check that a file list database exists for this packet. If it doesn't,
QwkRequest will simply exit.
If QwkRequest finds a database, you will be asked
'Do you want to generate any file requests?'
Pressing 'Y' or selecting the YES button and pressing return will
automatically load QwkRequest. You WILL NOT be asked for the
file database list to use, because QwkRequest is clever enough to
pick the correct one for you.
QwkRequest now functions exactly the same as in 'standalone' mode.
When you exit QwkRequest, you'll continue to unpack the QWK packet
in SLMR/OLX and continue there as normal. You will notice the new
replies that QwkRequest has generated for you !
QwkRequest v1.0 MAGIC REQUESTS
─────────────────────────────────────────────────────────────────
Magic Requests
Magic Requests are a niffty idea. They benefit both the user and
the SysOp. They benefit the user because of the ease of selecting
them, and the use of "standard" requests. For example, how often
have you logged onto a BBS and wanted the filelist. Is is called
FILELIST.ZIP ? ALLFILES.ZIP ? HANGAR.ZIP ? or any one of a 100
other different ideas that SysOps have. Wouldn't it be nice for a
user to just say "I want a File List!| and be done with it ? Well,
QwkRequest and AutoRequest make this dream come true!
If you're a SysOp you know how demanding running a BBS can be. If
you're like me, you spend a fair amount time sending new users FAQ
files, or details of subs, or any number of other bits of
information. The problem is you have to do it over and over again!
Now you as a SysOp can setup a .MGC file to have QwkRequest and
Autorequest cut down on all that (some say unproductive) time you
spend on it.
In QwkRequest's main work area you will see a window called Magic
Requests with at least five entries in it (these are hard coded
for the sake of trying to implement some common standard!). These
request generate the following request;
AutoReq Help Message - Ask AutoRequest at the BBS end
to send you a help message detailing
how to use AutoRequest.
BBS File List - Ask AutoRequest to send you a full
file list
BBS Subscription Details - Ask AutoRequest to send you a message
detailing subscription schemes and
costs.
Bulletins Available - Ask AutoRequest to send you a message
listing all the bulletins carried on
the BBS
Mail Area Conference - Ask AutoRequest to send you a message
Listing listing all the message conferences
on the BBS
There may well be other Magic requests there - it depends if the
SysOp has created a '.MGC' file and if you have it in the QWKREQ
directory.
Magic File Support For SysOps
If you are a SysOp using AutoRequest I hope you will support these
Magic requests - they offer some excellent benefits to you and your
users.
To start with you should support the 5 default magic requests as
detailed above. These generate the following 'Request' on the
Subject Line of the request message;
AutoReq Help Message - /HELP
BBS File List - //FILELIST
BBS Subscription Details - /SUBS
Bulletins Available - /BULL
Mail Conferences Listing - /CONFLIST
The /HELP message is in built to AutoRequest. The others need to be
Configured, which means that your AUTOREQ.XRF file should look something
like this;
;
HANGAR.ZIP,FILELIST
;
Messages:
;
J:\WC30\MSGS\SUBSINFO.TXT,SUBS
J:\WC30\BULLS.LST,BULL
J:\WC30\CONFLIST.TXT,CONFLIST
;
Note that FILE REQUEST just need the filename as it appears in the
WildCat Database. Messages require a pathname ! See your AUTOREQ.DOC
for full details.
Additional AUTOREQ.XRF entries should be made for any .MGC entry you may
make.
'.MGC' File Format for SysOps.
If you want to let your users benefit from the extensive possibilities
that Magic Requests offer, you need to create a '.MGC' file for your
users to download. The format of the '.MGC' file is;
;
; Example .MGC file for The Hangar BBS (44) (0) 934 511751 24hrs
;
/USER,User Account Details
/TIMETAB,Events Timetable & Mailruns
/TOPTEN,Hangar Top Tens
/RULES,The Hangar Rules !!
/SECLEV,Security Access Levels
//FAQ,Frequently Asked Questions File
/NETMAIL,How to Send Netmail
The magic 'code' is entered before the ',' (comma), and the description
is entered after it. No spaces are allowed between the comma and the
code or description. The code is limited to 14 characters in total, and
the description is limited to 35 characters (it gets chopped if longer).
QwkRequest v1.0 SETTING UP YOUR TOMCAT ACCOUNT
─────────────────────────────────────────────────────────────────
Setting Up Your Tomcat Account
To use QwkRequest and AutoRequest you _must_ have file attachments
enabled in the Tomcat Offline Mail Door. Select Tomcat from your
BBS, then select [C]onfigure your settings (Press 'C'!)
Select the [A]ttachment size limit, and you will be asked;
Enter maximum attachment size limit in Kbytes:
Enter the maximum size of the file you are likely to request. After
entering this, and by pressing ENTER you will be asked;
Do you want to include attachments to [A]ll or just to [Y]ou ?
Enter 'Y' for just your attachments. Quit the Configuration screen and
exit Tomcat. You are now setup for File Requests !
QwkRequest v1.0 REGISTRATION
─────────────────────────────────────────────────────────────────
Registration
QwkRequest is Shareware. This means that your are licensed to try
it out for a reasonable length of time, after which if you continue
to use it, you should register it with me. Details of how to
register and the costs of registration are in the REGISTER.DOC
which accompanies this archive.
QwkRequest uses a 'Key' file for registered users. Registered users
benefit because;
o You are not limited to 5 requests per packet.
o The message generated by QwkRequest is much shorter. This will
please your SysOp !
o The warm feeling you'll get for helping me to produce even
more helpful programs for peanuts !
o 24hrs Support via my Bristol based BBS
As you can see, there is very little 'crippled' about the unregistered
version. I hope that you will feel that QwkRequest is worth the small
amount I ask for it. There's very little other inducement to
register !
QwkRequest v1.0 TECHNICAL SUPPORT & SUGGESTIONS
─────────────────────────────────────────────────────────────────
Technical Support & Suggestions
Technical Support is primarily available to registered users. Requests
from registered users will take priority and will be processed. Requests
from unregistered users will be processed, but no guarantees can be made
on "turn-around" time.
I am _always_ keen to hear peoples views and suggestions on any of my
programs. If you have any comments to make, please _do_ contact me !
I cannot offer voice support for QwkRequest. The registration cost is
too low to make it viable. All contact must be electronic. I can be
emailed at the following addresses;
Internet : j@hangar.royle.org
FidoNet : 2:255/60
Compuserve : 30317,2621
Or you can contact me on my BBS by leaving a message to Jason hyland,
or call to download the latest version of QwkRequest;
The Hangar BBS +44 (0) 934 511751 V32b/24hrs
You can alse leave me a message in any one of the following mail
conferences (although email is _far_ better !)
ILink Network : SLMR Conference
The Net : BBS Software Conference
Wild Net : Shareware
MSI Net : Wildcat Support
RIME (#5411) : Common Room
The latest version of AutoRequest and support may be obtained
from Adam Stevens BBS;
Transworld BBS: +44 (0) 272 444025 2400 baud
+44 (0) 272 444026 14400 baud
+44 (0) 272 444027 14400 baud
Or on The Internet as "astevens@cheshire.demon.co.uk"
QwkRequest v1.0 AND THANKS GO TO ....
─────────────────────────────────────────────────────────────────
And Thanks Go To ....
To the ever suffering Yvette, my *better* half, for putting up with
a SysOp AND a programmer to boot. For supplying copious amounts of
black coffee at just the right moments. And for dragging me off to
bed at the exact perfect moment :)
To Adam Stevens for writing AutoRequest and for beta testing
QwkRequest. Watch out for some more excellent programs from Adam
in the future.
To all beta testers, whoever and wherever they are!
To ALL my subscribers at The Hangar, for neglecting them during the
fanatic coding binges !
Zortech (sadly now Symantic) for an excellent development environment.
QwkRequest v1.0 LIMITED WARRANTY
─────────────────────────────────────────────────────────────────
Limited Warranty
THIS PROGRAM IS GUARANTEED TO DO ABSOLUTELY NOTHING EXCEPT TAKE
UP DISK SPACE. USE IT AT YOUR OWN RISK. NEITHER HANGAR ONLINE
SERVICES NOR ANY OTHER PERSON INVOLVED IN ITS DISTRIBUTION IS
RESPONSIBLE IN ANY WAY, FOR ANY DAMAGES RESULTING FROM ITS USE OR
MISUSE, DIRECTLY OR INDIRECTLY.
THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF SETWMLOG! IS
ENTIRELY WITH YOU. SHOULD QWKREQ PROVE DEFECTIVE, YOU ASSUME THE
COST OF ALL NECESSARY SERVICING, REPAIR OR OTHER DAMAGES TO YOUR
EQUIPMENT, SOFTWARE, OR OTHER PROPERTY.
HANGAR ONLINE SERVICES IS NOT RESPONSIBLE TO YOU FOR DAMAGES,
INCLUDING BUT NOT LIMITED TO, ANY LOST PROFITS, LOST MONIES, OR
OTHER SPECIAL, GENERAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OR INABILITY TO USE (INCLUDING BUT NOT
LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE PROGRAM TO
OPERATE WITH ANY OTHER PROGRAMS) OR ANY OTHER LOSS EVEN IF YOU
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY
CLAIM BY ANY OTHER PARTY.
QwkRequest v1.0 LICENSING AND DISTRIBUTION AGREEMENT
─────────────────────────────────────────────────────────────────
Licensing and Distribution Agreement
Copyright (C) 1993, 1994 by Hangar Online Services and Jason
Hyland. ALL RIGHTS RESERVED. COMMERCIAL DISTRIBUTION AND/OR USE
PROHIBITED WITHOUT WRITTEN PERMISSION FROM Hangar Online Services.
Non-Commercial distribution and/or use is permitted under the
following terms:
1) You may copy and distribute copies of QwkReq
executable code as you receive it, in any medium,
provided that you do so in a lawful, friendly manner
and that you conspicuously and appropriately publish on
each copy of each file that is a part of the
distribution package a valid copyright notice:
"Copyright (C) 1993, 1994 by Hangar Online Services. Any
copies that you distribute must be distributed free of
charge to the recipient of the copy. QwkReq may not be
sold and you may not rent or lease it to any other person."
2) You must keep this License Agreement intact and give
any other recipients of the QwkReq program a copy of
this License Agreement along with the program.
3) You must distribute QwkReq in unmodified form. You
may not add an advertisement for your Bulletin Board
System, User Group, or anything else either as a file
in the distribution packet, only as a header in any
archive. You may not add, modify or delete any of the
files in the QwkReq distribution archive.
4) QwkReq must be distributed for free. You may not
charge a distribution fee for the physical act of
transferring a copy of this program. You may not place
this program in any file area of a Bulletin Board
System where a fee is required for download.
5) You may not modify your copy or copies of QwkReq or
any portion of it and you can not copy and distribute
any modifications.
6) You may not copy, sublicense, distribute or transfer
QwkReq except as expressly provided under this
License Agreement. Any attempt otherwise to copy,
sublicense, distribute or transfer QwkReq is void and
your rights to use the program under this License
agreement shall be automatically terminated.
7) You may not incorporate parts of QwkReq into other
programs without the written permission of Hangar
Online Services. Permission may or may not be
granted based upon a determination of what your
intended use is.
8) For the purposes of this document, "COMMERCIAL USE" is
defined as concurrent operation of the software on
two or more computers or data lines owned by the same
for-profit organization. Any organization may operate
this software under the terms of this Non-Commercial
Agreement if operation is limited to one computer or
data line.
9) You may use the software only after understanding and
agreeing upon the above terms.
QwkRequest v1.0 COPYRIGHT AND TRADEMARK RECOGNITION
─────────────────────────────────────────────────────────────────
Wildcat! is a trademark and copyright of Mustang Software Inc.
Tomcat is a trademark and copyright of Mustang Software Inc.
WCPRO is a trademark and copyright of Mustang Software Inc.
PKZIP/PKUNZIP is trademark and copyright of PKWARE Inc.
ARJ is trademark and copyright of Robert K Jung
AutoRequest is copyright AddTech Consultancy Ltd.
Extracts from AutoRequest documentation reproduced by permission
of AddTech Consultancy.
─────────────────────────────────────────────────────────────────