home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CBM Funet Archive
/
cbm-funet-archive-2003.iso
/
cbm
/
c128
/
archivers
/
nzp12811.sfx
/
qpe.bas.docs
< prev
next >
Wrap
Text File
|
1990-02-12
|
13KB
|
331 lines
QPE v1.1 (C)1994 by David Schmoll: 04-25-94
=====================================================================
= QPE =
=====================================================================
COPYRIGHT:
I have decided to distribute QPE as FREEWARE with the only
requirement that the distribution of this software be left in it's
original distibution form.
David Schmoll
1703 Pagosa Way
Aurora, Colorado 80011
USA
I am currently also available on the CBM and CBM-128 FIDO Echo's to
answer any questions or suggestions you may have. I am able to send
and receive Internet mail at the below address as well.
david.schmoll@f518.n104.z1.fidonet.org
Netmail can be received at 1:104/518
Please do not distribute this program except in the original archive!
---------------------------------------------------------------------
PROGRAM DESCRIPTION V1.1:
QPE IS A BASIC program written to interface with the offline Readers
QWKRR128 and QWKie 64 to create a more automated process of dealing
with your QWK mail packets. You have the choice to un-ZIP (see note
1) or un-ARC (see note 2) your QWK packets - the archive type is now
auto-detected. When QPE is run and the unpacking process is complete,
either QWKRR128 is executed if you are in 128 mode, or QWKie 64 is
executed if you are in 64 mode.
* NOTE 1: Permission has been requested from Bill Lucier to allow the
release of a special 64 unZIP module that runs under QPE, but
permission has not been given as of yet, so for now the only 64
option is to use the CSX64.ml to un-ARC the QWK packets. If and when
permission is granted, the 64 module can then be interfaced to QPE
will no further modifications. I have offered this module to Bill
Lucier so he can release it himself if that is more acceptable. As
QPE is written it expects the 64 module to be called unzip4.ml.
* NOTE 2: To un-ARC packets you need a separate program called
CSX01.SDA (written by Chris Smeets - see note 3). Included with
CSX01.SDA are two machine language modules called CSX64.ML and
CSX128.ML You need to copy these over to the same disk or partition
as QPE is on - nothing else is required.
* NOTE 3: No part of CSX01.SDA may be distributed in any form except
the original .SDA without the expressed consent of the current
copyright holder (Parsec). CSX01, CSX64.ML, CSX128ML, CSX01.SDA are
not part of the UNZIP128 distribution package, and must be downloaded
separately.
Page 1
QPE v1.1 (C)1994 by David Schmoll: 04-25-94
---------------------------------------------------------------------
FIRST TIME:
The first time QPE is run, you will see a listing of the current
configuration along with the prompt "Accept Defaults". The very first
time you run QPE, answer no to this default, since QPE does not know
your needs. This will bring up individual prompts so you can set you
own defaults. If you do not give any response, QPE will autostart in
10 seconds (see autostarting), accepting whatever defaults that are
set - whether they are correct or not! It is your responsibility to
answer the prompts correctly, as QPE has no way of knowing when an
error has been made. The archive type is now auto-detected by reading
the first two bytes of the QWK packet and comparing it to "pk". If a
match is made then the packet is assumed to be ZIP, otherwise it is
assumed to be an ARC. Another change is that input file type no
longer matters.
AUTOSTARTING:
There is a 10 second countdown timer displayed on the screen showing
you how much time is left before QPE will accept the current
defaults, and then proceed to unpack the QWK packet and run the
appropriate OLR. To stop this timer just answer no to "Accept
Defaults" before it reaches 0 - you can also start the unpacking
sooner by answering yes to the prompt instead.
PROMPTS:
The prompts you will see when you are setting your defaults are as
follows:
CRC CHECKING:
This prompt now shows up regardless of whether the input file is an
ARC or ZIP file, because the archive type isn't known at this time,
but it is only valid on Zipped packets. This is a file integrity
checksum (after the file is unzipped) and can be turned on or off.
Even if a CRC errors happen, the offline readers seem to work just
fine, so the importance of this information and choice is yours.
Answer "y/n".
One reason to turn off CRC checking is if you want to run the OLR
regardless of the result of the CRC check.
* Note: Any error during the unpacking will cause QPE to stop when
control is returned to BASIC and before control is given to the OLR.
Should an error occur during the unpacking and you wish to continue
(only recommended with a CRC error), you can type in "cont" and press
return, and the appropriate OLR will then load and run - this applies
to both the un-ARC and un-ZIP option. Make sure you see the BASIC
"ready" prompt before typing in "cont" and pressing return! If any
other error occurs, besides a CRC, try running QPE again, and if an
error occurs again, something is wrong with the QWK packet.
FILE TO UNPACK:
Page 2
QPE v1.1 (C)1994 by David Schmoll: 04-25-94
This is the name of the QWK packet that you downloaded. The .ARC or
.ZIP extension is no longer needed unlike the full version of
UNZIP128 ie: "qwk mail" works fine
MAXIMUS KLUDGE:
Sometimes when you have downloaded from a Maximus BBS, a extra
chr$(0) needs to be appended to the QWK packet before it can be
successfully unpacked. So if you have unpacking problems, try
answering yes to this prompt. Answer "y/n".
ACCEPT QWKRR DRIVES:
You will only see this when QPE is run in 128 mode, and it allows you
to bypass the usual drive prompts that QWKRR128 asks for and accept
whatever is defined in the QWKRR128 default file. Answer "y/n".
AUTO-INDEX:
You will only see this when QPE is run in 128 mode, and it allows you
to automatically trigger the indexing function when starting QWKRR128
Answer "y/n".
INPUT DEVICE:
This is the drive unit where the QWK packet that you downloaded is
located.
INPUT PATH:
This is the drive path where the QWK packet that you downloaded is
located. Non CMD users will use drive 0, while CMD users will give
the path location, such as "3//wherever/". Do not add the ending
colon as that will be appended for you to overcome the error message
that BASIC will give you should you include one.
OUTPUT DEVICE:
This is the drive unit to where the extracted files from the QWK
packet are to be extracted.
OUTPUT PATH:
This is the drive path to where the extracted files from the QWK
packet are to be extracted. Non CMD users will use drive 0, while CMD
users will give the path location, such as "3//wherever/". Do not add
the ending colon as that will be appended for you to overcome the
error message that BASIC will give you should you include one.
OLR DEVICE:
This is the drive unit number where, depending on computer mode,
either QWKRR128 or QWKIE 64 is located.
OLR PATH:
This is the drive path where, depending on computer mode, either
Page 3
QPE v1.1 (C)1994 by David Schmoll: 04-25-94
QWKRR128 or QWKie 64 is located. Non CMD users will use drive 0,
while CMD users will give the path location, such as "3//wherever/".
Do not add the ending colon as that will be appended for you to
overcome the error message that BASIC will give you should you
include one.
SET CONTROL.DAT TIME:
This is only seen when QPE is run in 128 mode, and it gives you the
option when using QWKRR128 to set the date from the control.dat, in
case you do not have a Real Time Clock (RTC) available. Answer "y/n".
SAVING CONFIGURATION:
After the options are set, you can save the changes to disk if you
desire to, otherwise the changes are for the current session only.
When the changes are saved, the entire program QPE is saved using
dynamic keyboard methods; so beware of renumbering QPE, as this can
cause problems during the save, otherwise minor changes are possible
to QPE to meet your needs! The program saved is called QPE, while the
master version is called QPE.BAS. This prevents you from destroying
the original should something go wrong!
FILES INSIDE THE PACKET:
The files inside of the QWK packet can vary by BBS, and the files
needed depend on whether you are using QWKRR128 or QWKie. QWKRR128
only needs the files "CONTROL.DAT" and "MESSAGES.DAT", while QWKie
needs the files "CONTROL.DAT", "MESSAGES.DAT", and the files ending
in ".NDX". To save BASIC memory space and simplify programming logic
all files inside the QWK packet are extracted, regardless of their
importance. The best way to avoid this situation, is to see if you
can exclude the files that you do not need from the QWK packet when
you define your offline reader settings on the BBS. In my experience
the added files are usually very small, so their extraction doesn't
really consume much time anyway.
PATH WARNINGS:
QPE, CONTROL.DAT, AND MESSAGE.DAT do not need to be on the same disk
or partition as either QWKRR128 or QWKie 64, but be aware that the
current version of QWKie doesn't recognize CMD paths, so if you
unpack to a sub-partition that is not the current partition as well,
QWKie 64 will not automatically see it until you make that path or
partition the current one. Fortunately, this can be accomplished with
the QWKie Dos command (wedge) very easily.
The path information is for CMD drives only (Ramlink, Hard drive,
Ramdrive, and FDx000) and does *NOT* support 1581 partitions. If CMD
path information is entered, the it must follow the general form of
"x//wherever/" - where x is the actual partition number, the "//"
means start from the root partition, "wherever" is the subdirectory
name, and it must end with a "/". The ending "/" is a change from
the earlier verion of QPX by Russell Prater!
Page 4
QPE v1.1 (C)1994 by David Schmoll: 04-25-94
Alternately, the 0 in the path becomes the drive number that the
other Commodore drives understand, and no error checking is done if
things are wrong.
A ":" is appended to either path style to complete the path name!
MEMORY USAGE:
Memory usage for the special 128 UNZIP modules is currently: $1300 -
$1bff, $3400 - $3fff and $0400 - $0801. QPE memory usage will use any
normal basic area not used by the ML or buffers. Memory for the
buffer storage needed by the all of the UNZIP modules is from $4000 -
$ffff. When running in 64 mode, QPE will set the top of free basic
memory to $28ff so variable memory is not corrupted during the
unzipping - otherwise the ability to call QWKie would not then be
possible - note this is also due to the potential memory usage of the
unreleased 64 unzip module which is currently from $2900 - $3fff.
* NOTE: Zero page is saved to $3f00 when the unZIP modules are
called, to avoid corruption, and then restored when control is
returned to QPE.
Page 5