
QWK command help:
-----------------

Generally:
There are 5 commands in the QWK menu. All global MBBS-commands
are of course available directly from the QWK menu. Stacking of
commands are fully supported as normally in MBBS. Another issue
to pay attention to: Most QWK-servers are, as you might know,
capable of receiving special messages containing various requests
like automatic joining/resigning conferences, order for files
and/or bulletins etc. Many kinds of message-requests are
supported also on this system. Later in this helpfile the
requests are listed and explained in detailes.

Now the commands in the QWK menu:

"<D>ownload QWK packet" will export new messages in QWK-format,
archive them into a standard QWK-packet and send the QWK-file to
your computer. It works mainly as the normal 'GRAB' command, but
will give you a QWK packet instead.

"<UP>load REP packet" will receive a REP packet from you and
inserts your message(s) into the MBBS messagebase.

"<PTR> upload PTR file" will receive a PTR file from you and
update all your message pointers according to that PTR-file.
The PTR-file is included in every QWK-packet you download, and it
contains all your message pointers *before* the QWK-packet is
created.

"<C>onfigure your QWK settings" command will take you to the
QWK Config menu. (see below)

"<QH> download QWK helpfile" will send this helpfile to your
computer.



QWK Config Command help:
------------------------
The <C> command in the QWK menu will, as mentioned, take you to
the 'QWK Config Command' menu where you may configure your own
QWK profile. None of the global MBBS commands will be available
from the 'QWK Config Command' prompt since this is a submenu of
the QWK menu.

The config menu has these options:
(All options are ON/OFF switches or toggles, so by giving the
actual command the switch will be reversed)

<B> send new bulletins
----------------------
When this one is on any *new* bulletins (bulletins updated since
your last logon), will be added to your QWK packet.

<C> FULL conference list
------------------------
This switch affects the CONTROL.DAT file which *always* is
included in any QWK packet. CONTROL.DAT countains among other,
info about the different conferences and also the internal
numbers of these. If you keep this ON, the conference list in
CONTROL.DAT will contain all the conferences you have access to
even if you are not currently joined into them. Turning this OFF
will result in a list of only those conferences you have joined.

<W> send WELCOME file (prelog)
<N> send NEWS file (bull0)
<G> send GOODBYE file (postlog)
-------------------------------
These are switches for three ascii/ansi files which you may
request to be included in your QWK-packet. Many QWK readers have
builtin support for handling these files.

The 'WELCOME'-file is the file containing the text presented to
you just before MBBS asks for your name.

The 'NEWS'-file is the file containing the text presented to you
after you've entered your password but before you get to the MBBS
command-line prompt.

The 'GOODBYE'-file contains the text presented to you when you
log off the system.

<F> scan for new files
----------------------
When this switch is on, a list of new files (NEWFILES.DAT) since
the last time you were logged in, will be included in your QWK-
packet. The list is identical to the list presented to you when
you issue the "F N" command from the file menu. Most QWK readers
are capable of showing this file to you upon request.

<X> send NDX-files
------------------
This should be ON in most cases. It should only be set to OFF, if
you are absolutely sure your QWK reader doesn't need NDX-files.

<S> send SESSION.TXT
--------------------
SESSION.TXT is a ascii-file containing the raw screen output
during creation of the QWK packet. Set this switch ON if you
want SESSION.TXT to be included in the QWK-packet. Most QWK
readers offers you to view the SESSION.TXT if it is included
in the packet.

<FAST> QWK export
-----------------
If turning this option ON, AG-QWK will perform a 'raw' export of
the messagetexts. This means that AG-QWK will NOT support your
'charachter set'-choice. This is no problem if you are using the SAME
charachter set as MBBS itself (normally that would be IBN, but check
with your sysop if you're not sure)
Also when running 'FAST', AG-QWK will NOT strip any color-codes from
the messages. (MBBS uses ASCII-codes 0-9 for setting different colors
in messages). Most QWK readers will handle this OK, but, if your reader
fails to import the QWK-packet properly when running 'FAST' export,
it is probably getting confused by these color-codes. In such cases
turn FAST export OFF (or change to another QWK-reader)

<PREPACK> automatic QWK Prepacking
----------------------------------
This feature is ONLY available if sysop has registered his AG-QWK
and ENABLED the QWK PrePacking utility. If so and you turn this
switch ON, the system will have a QWK-packet ready for you to
collect *before* you log in to the system. Then when you enter the
QWK menu and issue the D command, you will be informed of your
prepacked QWK-packet's creation date/time, contents and then a
choice to download the prepacked QWK-packet or to do a normal "QWK
D"-session. Obviously a prepacked QWK-packet will not contain
messages entered on the system after it was created, so how updated
the packet is, depends on *when* and *how often* the system runs
(sysop's decision) the QWK Prepacking utility to create/update your
packet. Your message pointers will always be updated to reflect your
*last downloaded* message in each conference, so if you choose to
download the ready packet and there are new messages entered after
it was created/updated, you will *not* miss such *recently* entered
messages! You will get them in your next QWK-packet!

<L> view your QWK settings
--------------------------
Present a list of your current QWK settings.

<Enter>
-------
Will take you back to the normal QWK menu.


'QWK requests':
===============
Your may request different task to be performed automatically by
entering messages to the QWK-server. By writing a message to
'AG-QWK' and put your 'order' in the 'Subject'-field, you are
able to request the QWK-server to automatically join/resign
conferences, send files to you etc.

Such a request message must always be adressed to 'AG-QWK', and
the subject-field must contain one of the requests described
below:

ADD (or JOIN)
DROP (or RESIGN)
BLT:<bulletin-number>
RESET:<message-number>
DL:<filename>
FILEINFO:<filename>
USERINFO:<user name>

The first four of these (ADD/JOIN, DROP/RESIGN, BLT: and RESET:)
requires the message to be written in the actual conference the
request regards. The rest may be entered in any conference.

ADD (or JOIN)
----------------
Join you to the conference (as if you issued the <J>oin command
directly from MBBS)

DROP (or RESIGN)
-------------------
Resign you from the conference (as if you issued the <RES>ign
command directly from MBBS)

BLT:<bulletin-number>
---------------------
Requests bulltin number <bulletin-number> in the conference.
The request is saved until the next time you collects a
QWK-packet, then the bulletin is added to the packet.

RESET:<message-number>
----------------------
This work just as the MBBS command "M S", which sets your last
message read pointer in the conference to a given message-number.
The last message read pointer is the internal pointer to the last
message you've read in the conference.

DL:<filename>
-------------
This request works almost like the download command in the file
menu. DL:TEST.ZIP will put the file TEST.ZIP in the QWK packet
together with messages/bulletins. But of cource only if the file
is present in MBBS and you have normal access to download it.
The request is saved until the next time you collects a
QWK-packet, then the file is added to the packet.

FILEINFO:<filename>
-------------------
This request works like 'DL:' described over, but will send you
the *fileinfo* for the file instead of the file itself. The
fileinfo is collected from the fileinfo conference and then put
into the mail conference as a private message to you, which you
then will receive together with any other new messages the next
time you collect a QWK-packet. If there isn't any fileinfo
message for the file for the given file, the request is simply
ignored.

USERINFO:<user name>
--------------------
Works just like the 'FILEINFO:'-request described above, but
instead USERINFO:XXXX YYYY gives you the 'user-info' (resume) for
the user 'XXXX YYYY'.

