home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The First Hungarian Family
/
The_First_Hungarian_Family_CD-ROM.bin
/
internet
/
offlread
/
protocol
/
supk412
/
superk.doc
< prev
Wrap
Text File
|
1989-05-04
|
42KB
|
881 lines
SuperK v4.12 MiniNet's External Protocol Driver including
JBatch MiniNet's Driver for Richard B. Johnson's Jmodem Protocol
Protocols Supported: Xmodem Checksum, Xmodem CRC, Ymodem (1k Xmodem)
Jmodem, WXmodem, K9Xmodem and Super8K in full
Batch or Single File Mode.
SuperK is Copyright 12/4/1986, 1989 and JBatch is Copyright 11/01/1988, 1989
by Crater Rim Software. All Rights Reserved.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
SuperK Licensing Agreement
--------------------------
For the sake of clarity, all references and restrictions to the use of
the SuperK also apply to all of the associated support files INCLUDING
the K9Xmodem, Super8K and Jbatch protocols.
SuperK, its overlays and all of its associated support files are not
public domain software, nor are they free software. SuperK is copyright
(C) 1985, 1989 - the K9Xmodem, Super8K, SuperK and JBatch protocols are
copyright 1987, 1989 by Crater Rim.
Non-registered users are granted a limited license to use SuperK version
4.xx on a trial basis for the purpose of determining whether these
programs are suitable for their needs. The term of this limited license
is 30 days. Use of SuperK, except for this limited purpose, requires
registration. Use of non-registered copies of SuperK by any person,
business, corporation, governmental agency or other entity institution
is strictly forbidden.
Registration permits you to use SuperK on a regular basis on a single
computer. A registered user may use the program on a different
computer, but may not use the program on more than one computer at the
same time. Registration also includes priority support on Underdog's
MiniNet BBS. Users need register only one version of SuperK.
Registration includes licensed use of all upgrades.
All corporate, business, government or other commercial uses of SuperK
must be registered. We offer quantity discounts and Corporate or site
licensing is also available.
No user may modify SuperK in any way, including but not limited to
decompiling, disassembling or otherwise reverse engineering the program.
All users are granted a limited license to copy SuperK version 4.xx only
for the trial use of others subject to the above limitations, and also
the following:
SuperK version 4.xx must be copied in unmodified form,
complete with the file containing this license information.
Any and all SuperK documentation must be included with the
copy. No fee, charge or other compensation may be accepted
or requested by any licensee.
SuperK may not be distributed in conjunction with any other
product without prior arrangements with Crater Rim Software.
Operators of electronic bulletin board systems (Sysops) may post SuperK
version 4.xx for downloading by their users only as long as the above
conditions are met.
Distributors of public domain or user supported software may distribute
copies of SuperK version 4.xx subject to the above conditions only after
obtaining written permission from Crater Rim Software. Such permission
usually is granted. Please write or call for details.
ShareWare Software Discalaimer and Warranty
Crater Rim Software makes no warranty of any kind, express or implied,
including without limitation, any warranties of merchantability and/or
fitness for a particular purpose. Crater Rim Software shall not be
liable for any damages, whether direct, indirect, special or
consequential arising from a failure of this program to operate in the
manner desired by the user. Crater Rim Software shall not be liable for
any damage to data or property which may be caused directly or
indirectly by use of the program.
IN NO EVENT WILL Crater Rim Software BE LIABLE TO YOU FOR ANY DAMAGES,
INCLUDING ANY LOST PROFITS, LOST SAVINGS OR OTHER INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF YOUR USE OR INABILITY TO USE THE
PROGRAM, OR FOR ANY CLAIM BY ANY OTHER PARTY.
See the Ordering section for more information on registration, corporate
licensing and similar topics.
WARNING: YOU MAY NOT USE EITHER VERSION OF SuperK ON A REGULAR BASIS
WITHOUT REGISTERING THE PACKAGE.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
SuperK External Protocol Driver - Revision Log
V2.50 - Dated 08/22/88 Initial Release
V2.52 - Dated 09/01/88
V3.10 - Dated 11/05/88
V3.12 - Dated 12/04/88
V3.13 - Dated 12/06/88
V3.14 - Dated 12/27/88
V3.15 - Dated 01/07/89
V3.16 - Dated 01/26/89
V4.00 - Dated 02/20/89
V4.10 - Dated 03/29/89 Changes
Modem Buffer size has been increased from 4K to 8K
Sending files using Super8K will now recognize the receipt of an XOFF
from the modem. Upon receipt, SuperK will cycle for about 5 seconds
waiting for an XON from the modem or a user abort via the Esc or ^X key.
Please Note that the XOFF/XON support is ONLY for use with MNP modems.
The Super8K receiver software does not send the XOFF/XON.
It has been brought to my attention that the latest MS Basic compilers
drop the RTS line when performing a DOS shell. SuperK now checks the RTS
line upon startup and will raise it if it has been dropped.
There have also been some reports of memory errors when using SuperK in
EEMS memory... I suspect that this may have been caused by a Stack/Heap
collision within SuperK. To this end, I have increased both the Stack
and Heap. Please check the new memory requirements to be sure that you
have ample memory available for SuperK to do its thing! Please let me
know if this problem still exists.
The addition of a Work Path so that SuperK can easily access Read Only
files in a networking envirnment (see W - Work Path below).
Corrected a bug in the Overwrite check. Under certain circumstances, an
I/O error would occur if too many files were rejected by the receiver.
V4.11 - Dated 04/05/89 Corrected a minor bug in the ReadOnly copy routine
V4.12 - Dated 05/04/89 Changes
In an effort to make Super8K a little more "bullet proof", I reworked
then Super8K Error Recovery routines.
There have been a number of users having problems with SuperK reporting
a run time error of F0=xxxx. This is due to the fact that SuperK cannot
find its overlay file, SUPERK.000. Seems there are some (antiquated) BBS
packages that change directories before transferring a file! When this
happens, SuperK is unable to find its overalay (or the SKA.COM jmodem
module for that matter). If this is happening to you, be sure to start
up SuperK as SUPERK @ and define OVL Path parameter to the FULL
drive:\path\ where SUPERK resides.
There are also reports that some BBS software is unable to "read" the
SuperK errorlevel returned upon exit. This is a problem with the calling
program NOT with SuperK as the errorlevel returned is fully recognized
by DOS via a batch file.
Memory requirements:
~~~~~~~~~~~~~~~~~~~
Jmodem transfers require a minimum of 125K (128,000 bytes). All of the
other protocols only require about 70K (71,680 bytes). If you don't know
how much memory you have available, it can be checked easily as follows:
1) Copy DOS' CHKDSK.COM to your comm directory.
2) Start up your comm program and execute the comm program's DOS shell
option.
3) Type CHKDSK at the DOS prompt
4) CHKDSK will display its results along with the "bytes free" figure.
In order to perform Jmodem transfers, the "bytes free" must be at
least 128,000 (if you intend on using SuperK's Jmodem).
5) Enter "EXIT" at the DOS prompt.
6) Exit your comm program...
Command Line Syntax:
~~~~~~~~~~~~~~~~~~~
SuperK Px Sbaud [Nx] [M] [R] [E] Dprotocol{by} F filespec filespec filespec
Command line parameters :
~~~~~~~~~~~~~~~~~~~~~~~
Px - Comm Port to use.
Where x = 1 or 2
Sbaud - Modem Speed.
Where baud = 300, 1200, 2400, 4800, 9600, 19200
DirectionProtocol[b][y]
Direction of transfer. Where D = R (receive) or S (send)
and Protocol X = Xmodem
C = CRC Xmodem
Y = Ymodem (1k Xmodem)
W = WXmodem
J = Jmodem
K = K9Xmodem
S = Super8K
b = Perform the transfer in Batch mode. Note that both
computers MUST be using SuperK or K9X in order for the
Batch mode to be operational.
y = SuperK allows you to specify if you want overwriting of
existing files to be performed. By including a Y with the
Direction/Protocol parameter, the default overwrite
setting will be reversed during the current transfer.
In single file mode, the J, X, C, W and Y protocols are fully
compatible with their counterparts used on all/most BBS Both
systems must be using SuperK to invoke the K9Xmodem or Super8K
Protocols.
Both y and b are optional. The y overwrite reversal only works
in Batch mode (when the b is also present). If the b is omitted,
SuperK defaults to single file mode
A brand new protocol!!! As is the case with the other SuperK
protocols, the Super8K protocol itself may be executed in either
Batch (SB parameter) or Single File (S parameter) mode. Along
with a much improved throughput, the Super8K protocol also rounds
file sizes up to the next higher 128 byte sector, ala X/WXmodem,
rather than the next higher 1K byte sector, ala Y/K9Xmodem.
Super8K uses an 8K block with a 1K error fallback/restart and
since it IS NOT a windowing protocol (like WXmodem and K9Xmodem),
the error/abort response time is improved 1000 fold! Super8K
also passes the number of file sectors to the receiving system so
a file size and transfer time (approxomate) is displayed on both
the sending and receiving systems.
Of course, the Super8K protocol has its own colors so be sure to
setup SuperK before you use it.
Since Super8K only does a byte count update each 8K, the tranfer
may seem to be taking a long time... but in reality.... the
following SUPERK.LOG extract displays the preliminary test
results for each of the SuperK protocols and a test comparison to
Zmodem and Jmodem. These tests were run between two AT's via
Null Modem cable. Results via modem will probably be a little
lower accross the board.
Size Speed Cps Errors BlkSize Protocol
--------------------------------------------------------------
60800 9600 bps 533 cps 0 errors 0 128 Xmodem Batch
60800 9600 bps 769 cps 0 errors 0 128 WXmodem Batch
61440 9600 bps 787 cps 0 errors 0 1024 Ymodem Batch
61440 9600 bps 869 cps 0 errors 0 1024 K9Xmodem Batch
60707 9600 bps 861 cps 0 errors 0 1024 Zmodem
60800 9600 bps 965 cps 0 errors 0 8192 Super8K Batch
60707 2400 bps 223 cps 0 errors 0 1024 Jmodem
60707 2400 bps 222 cps 0 errors 0 1024 Zmodem
60800 2400 bps 262 cps 0 errors 0 8192 Super8K Batch
---------------------------------------------------------------
M - Monitor Carrier, abort if not present.
Including this parameter allows you to use SuperK to transfer files
between systems via null modem cable. Default is ON (Monitor
Carrier).
Nx - Node Letter or Number. Where x = A to Z or 0 to 9
E - The E parameter toggles the status of the "erase" flag.
If specified on the command line, SuperK will not erase the BATCHLST
file it creates when multiple filenames are specified on the command
line (until the next time you specify multiple filenames, that is!)
R - This Command Line Parameter is for use with RBBS-PC.
RBBS-PC utilizes a true Batch download with a single file mode
upload. During uploads, RBBS-PC includes the full path and filename
for the f paramter. Since SuperK Batch modes are TRUE Batch in both
downloads and uploads, I have added the R command line switch to
tell SuperK that the F parameter may (or may not) include a
filename. When SuperK sees the R parameter, it will look for the
last \ or : characters and parse all characters after that, thus
leaving just the path... which it then appends to any uploads. The
default is True (non RBBS-PC) batch uploads.
RBBS command line for Batch Receive using K9Xmodem Batch
SUPERK.COM p[PORT#] s[BAUD] r n[NODE] rkb f [FILE]
RBBS command line for Batch Receive using K9Xmodem Batch
SUPERK.COM p[PORT#] s[BAUD] r n[NODE] skb f [FILE]
example: RBBS-PC passes [FILE] as C:\RBBS\99\filename.ext
(or your defined upload path) during uploads
exclusion of the R command line parameter results in an
invalid file specification of
C:\RBBS\99\filename.ext\
inclusion of the R command line parameter results in a valid file
specification of
C:\RBBS\99\
for obvious reasons, if you use the R command line parameter, you
must include the last \ or at least one superflous (non \ or :
character) at the end of the F specification.
when using the R parameter...
valid C:\RBBS\99\*.* results in C:\RBBS\99\
valid C:\RBBS\99\ABC.PAK results in C:\RBBS\99\
valid C:\RBBS\99\ results in C:\RBBS\99\
invalid C:\RBBS\99 results in C:\RBBS\
no f parameter results in *.* (all files saved
in logged drive\dir)
when using the default (non RBBS-PC)
invalid C:\RBBS\99\*.* results in C:\RBBS\99\*.*\
invalid C:\RBBS\99\ABC.PAK results in C:\RBBS\99\ABC.PAK\
valid C:\RBBS\99\ results in C:\RBBS\99\
valid C:\RBBS\99 results in C:\RBBS\99\
no f parameter results in *.* (all files saved
in logged drive\dir)
F - Filespecs Next
This parameter acts as a flag for SuperK and denotes that ALL
parameters after the F are to be interpreted as filenames. For
obvious reasons, this parameter should be the last one specified
(before the filenames)! Each filename may contain a full path in the
form:
[d:\path\]Filename [d:\path\]Filename to send/receive.
or
You may also specify the use of a text file containing a list of
filenames. Each filename in the list may contain a full path. This
option is specified as:
@drive:\path\Filelist (of files to Batch send.
or
You may want to use the second option for file lists... that is,
include a second path where ALL of the files within the list reside.
This option is specified as:
@drive:\path\listfilename@drive:\path
@ - Default Configuration Mode
Modify colors/logfile name/xferfile name/overlay path/options flags
Clone SUPERK.COM if changes are made
The port, speed and direction/protocol parameters MUST be supplied... If
operating in single file mode, the F parameter must be supplied. The B,
E, Y, M, N and R parameters are optional... and the @ parameter is only
used to review/modify the default settings (see modification mode
below).
The direction R and S parameters are mutually exclusive (only one, but
not both).
Command Line parameters may be supplied as upper or lower case, and may
be entered in any order (except for the F paramter which must be the
last one... before any filenames).
SK4.LOG
~~~~~~~
SuperK will record transfer results to the logfile in the following
format:
+--- Transfer Direction
| +------- File Size (0 if transfer fails)
| | +---------- Modem Speed
| | | +---------- CPS efficiency (0 if transfer fails)
| | | | +------------- Number of errors
| | | | | +-- Dummy for DSZLOG compatability
| | | | | | +----- Packet size in bytes
| | | | | | | +--- Filename
| | | | | | | | Protocol ----++- Batch
| | | | | | | | ||
S 27648 1200 bps 108 cps 0 errors 0 1024 C:\DLS\SUPERK.PAK KB
XFER.TXT
~~~~~~~~
If (and only if) a Node character is specified OR a question mark is
used within the XferFile name or SuperK Log file name, SuperK will also
create a Xfer Node File to show success/failure status messages.
This file has the following format :
Filename
Upload or Download
Protocol (X/C/Y/W/K/S/XB/CB/YB/WB/KB/SB)
Success or Fail
EOF (^Z)
Sample:
SUPERK.PAK
Download
KB
Success
^Z
The file will be created in the default directory if no drive/path is
specified during the command line @ parameter modification mode. While
in batch mode, only the first file transfer results will be logged to
this file. However, SUPERK.LOG will contain the results of all files
transferred in the batch.
ErrorLevel Exits
~~~~~~~~~~~~~~~~
For ease of use within batch files... in all cases, SupeK will exit with
an ErrorLevel determined by the success of the transfer.
If ALL transfers are successful, SuperK will return an ERRORLEVEL 0 If
ANY ONE transfer fails, SuperK will return an ERRORLEVEL 1
Command Line @ Parameter Modification Mode
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Starting SuperK with the @ command line parameter will put SuperK into
its default modification mode. SuperK will first display its current
default settings and then prompt you for any changes you may wish to
make. Note that entering a blank line (simply hitting [Enter]) will
leave the current setting intact. SuperK allows modification to the
colors it uses, the logfile name, the xfer file name (for BBS use), the
overlay path and certain operational flags.
C - Modifying colors:
This one's easy! After selecting the C option, SuperK will display
the 127 color palette that it supports. Simply select a number for
each of the 5 colors used... SuperK will cycle through all 5
colors, updating the "current settings" accordingly. If you don't
want to change a current color setting, simply hit the [Enter] key
and SuperK will move on to the next setting. Note: Jmodem window
colors default to black text on a white background. The 5 color
types are:
Xcolors for Xmodem/Xmodem CRC/WXmodem transfers
Kcolors for K9Xmodem transfers
Ycolors for Ymodem transfers
Scolors for SuperK transfers
Ucolors for universal display of the SuperK logo and batch
filenames
D - Logfile Name:
This is the filename SuperK uses to record the results of any
tranfers it performs. SuperK will accept upto 40 characters so you
may include a full drive:\path\ along with the logfile name.
Additionally, you may use a question mark (?) as one (and only one)
of the logfile name characters. If a question mark is present,
SuperK will substitute the Node character in its place. If no node
character is specified, SuperK will use the letter A as a Node
character. The letter A is substituted ONLY if the question mark is
encountered in the logfile name. If you do not want SuperK to
maintain a logfile, simply enter a backslash (\).. which will inform
SuperK to blank out the logfile name. The default logfile name is
SK4.LOG
E - XferFile Name:
This is the filename SuperK uses to record transfer results for use
by BBS programs. Its format and modification is identical to the
Logfile Name. The default Xferfile name is XFER.TXT
F - OvlPath:
Although in most cases, you will be storing all of the SuperK files
in the same directory as your comm/BBS program files, there are
cases where you may want to store them in a directory other than the
logged directory. This option allows you to do this. When SuperK
starts up, it will use the OvlPath to locate its overlay file
(SUPERK.000) and Jmodem module (SKA.COM). You must supply the full
drive and path in which the SKA.COM, SUPERK.COM and SUPERK.000 files
reside and all SuperK files MUST reside in this area. If no OvlPath
is defined, SuperK will expect all of its files to reside in the
logged directory. If, after defining a path, you decide that it is
NOT required, simply enter a backslash \ for the new path. This
will cause SuperK to null out any existing path.
G - Overwrite:
This flag setting tells SuperK whether or not in can overwrite
existing files during Batch mode transfers. The default is NO
H - Save Aborts:
This flag setting tell SuperK whether or not it should keep any
partial files which were aborted during transfer. This flag holds
for any protocol - batch or single file mode. The default is YES
I - Write On 0:
This flag setting tells SuperK whether or not it should create the
XferFile when a transfer is not successfully completed and the
uploaded file contains 0 bytes. The status of this flag is the last
check that SuperK makes before creating the XferFile. A node
character and XferFile Name must be specified before the Write On 0
flag comes into play. The default is YES
P - Patch SKA.COM
In order to facilitate the use of JBatch in a multinode BBS
environment the SK.COM module has been renamed JBA.COM. In a
multinode BBS environement, SuperK requires the presence of an
exclusive copy of SKA.COM for each node. Each SK module is named
according to the BBS node it supports (SKA.COM supports node A,
SKB.COM supports node B, SK1.COM supports node 1, etc.).
In previous versions, there was a separate patching utility provided
so that you could patch SKA.COM (JBA.COM before). SuperK v4.00 now
provides an internal method of performing this modification! After
selecting this option, SuperK will prompt you for the current name
of the SKx.COM file and then prompt you for a new node character.
Upon making the patch, SuperK will rename the old SKx.COM file to SK
+ your new node character.
SuperK will strip the last character of the filename (the A in SKA)
and insert the node character in its place rename the SKA.COM file
to SK + node character + .COM.
If no node character is specified on the SuperK command line (the n
parameter), SuperK will use the A character... as you have probably
surmised, SuperK appends the node character (or temporary A) to the
SK module (JBA, JBB, JB1, etc).
Caution...
If you haven't any use for mutiple copies of SKA.COM, simply copy
SKA.COM down into your comm directory and use it. The default is
SKA.COM
W - Work Path
This parameter was included in order to supply a simple means of
transferring files which have the Read Only attribute set. Since the
Turbo Pascal compiler opens all files in a Read and Write state,
SuperK would experience an I/O error when attempting to open a Read
Only file. Since this problem is more prevelant in a networking
environemnt... and I didn't particularly care to have to revamp all
of the SuperK file read/write I/O routines... This option will
circumvent the compiler problem for those users who wish to use the
SuperK driver to send Read Only files.
By specifying a work path here, SuperK will create a copy of the
requested download in this directory and then proceed to send the
copy. Upon completion (or abort) SuperK will erase the copy. Of
course, you may use this feature regardless of the File's Read Only
Attribute... if you feel insecure at having SuperK access the
"master" file, set up a work path and SuperK. If a work path is
specified, it MUST be a complete path including a drive letter,
colon, backspace, directory etc... upto a maximum of 40 characters.
As is the case with the SuperK support files, you may use a question
mark as a valid character within the path string. If SuperK
encounters a question mark in the Work Path, it will substitute the
node character specified on the command line or, if none is
specified, SuperK will substitute an A for the question mark.
Valid Paths:
Specifed Result
C:\BBSWORK C:\BBSWORK\filename
C:\NODE?WRK if no node specified
C:\NODEAWRK\filename
if node 1 specified
C:\NODE1WRK\filename
C:\BBS\NODE? if no node specified
C:\BBS\NODEA\filename
if node 1 specified
C:\BBS\NODE1\filename
InValid:
C:\NODE?WRK? if no node specified
C:\NODEAWRK?\filename
if node 1 specified
C:\NODE1WRK?\filename
[Enter] Quit:
If you only wish to view the current default settings, simply hit
[Enter] to exit back to DOS. If any changes have been made, SuperK
will go into its cloning mode and ask if you want to clone SuperK to
preserve the new changes. Note that you MUST press the Y key in
order to clone SuperK. Hitting [Enter] here will simply return you
to DOS without saving your changes within the SuperK program.
Program control keys
~~~~~~~~~~~~~~~~~~~~
SuperK will recognize either the [Esc] key or ^X (control X) key during
transfers and will abort the current transfer, returning you to DOS.
Note that the streaming protocols (Wxmodem, K9Xmodem) may require
several [Esc] or ^X to abort the transfer and Jmodem/JBatch may require
a ^Break to abort the transfer.
I have modified the Jmodem module (SKA.COM) to eliminate as much of the
delays as possible... making the batch mode cycling quite "brisk"! Note
however that there is a delay if the Jmodem transfer is aborted for any
reason... this is due to the fact that the buffers have to be "drained"
before recycling.
Batch transfers
~~~~~~~~~~~~~~~
SuperK is capable of sending and receiving multiple files in batch mode.
Since this protocol driver was written for use with my MiniNet BBS
package... the sending of the file creation date (ala DSZ and Telink)
tends to drive me up the wall, creating quite a bit of confusion in
keeeping track of newly acquired files!
For this reason the major difference between SuperK Batch mode and other
Batch modes is that SuperK Batch only sends the File Name and File size
but does not send the file creation date.
During Batch mode transfers, SuperK will display the last 3 files
requested under the SuperK logo so that you may have a running update of
what's happening. The present transfer progress is displayed in its own
window alongside the SuperK logo.
SuperK is able to handle multiple filenames on the command line. The
command syntax remains the same but if more than one filename is
specified, SuperK will create its own BATCHLST file. If a Node character
is specified on the command line, that character will be used for the
extension of BATCHLST. The default is "A" if no node character is
specified.
The number of filenames that can be specified will depend largely on
your own particular system setup, the string length used by your calling
program and the individual filename lengths.
This feature is only active while in Batch Send Mode (receive
automatically gets filename from sender), the command line paramaters
can be in any order, NO WILDCARDS ARE ALLOWED, the first filename MUST
be preceeded by an F (upper or lower case) and EACH filename may include
a full path.
Your command line should look like this...
SUPERK p1 s9600 SWB f FILE1 FILE2 FILE3
Since the BATCHLST is created internally (by SuperK), SuperK will erase
the BATCHLST file once it is done with it... You may override this by
including an E as one of the command line parameters. The E parameter
toggles the status of the "erase" flag. If specified on the command
line, SuperK will not erase the BATCHLST file (until the next time you
specify multiple filenames, that is!)
Receiving files in Batch mode
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You do not have to supply any filename during batch mode receives.
You may of course, include a full drive:\path\ in place of a
filename. Use the F command line parameter to designate the path in
the form: f C:\FOO\BAR (with or without the trailing backslash).
And... DO NOT specify the f parameter if no path or filename is
specified.
Sending files in batch mode
~~~~~~~~~~~~~~~~~~~~~~~~~~~
You may use any valid DOS wildcard configuration with the F
parameter.
Additionally, you may specify a list of filenames for SuperK to send.
The list filename is specified as
@drive\:path\listfilename
You may also specify a full drive:\path\ to where all of the files in
the list reside. This is specified as
@drive:\path\filelist@drive:\path
The filenames in the list may contain a full drive:\path\ (the same
or different) for each filename.
SuperK is capable of reading and extracting filenames from a standard -
single line - BBS files listing. If you use a BBS type files listing,
and call SuperK from the comm or BBS directory, you will have to add the
full drive:\path\ to each filename in the list if the files to send do
not reside in the default directory. There are other ways of accessing
files that reside in directories other than the default (default upload
and download directories, etc.), but I won't go into this area as most
comm and BBS programs do this work for you (K9X does it ALL for you...
automatically!)
Examples
~~~~~~~~
1. Use COM1, 1200 baud, Xmodem, Send files MYFILE.DOC and FILE.COM
SUPERK p1 s1200 SX f MYFILE.DOC FILE.COM
2. Use COM2, 19200 baud, Ymodem Batch, Receive file *.DOC, do not
monitor carrier, override the default "do not overwrite".
SUPERK p2 s19200 m RYBY
Note: The protocol character must follow the direction R. The
second Y above is the override for the overwrite flag. The B
and second Y may be in any order just as long as they are the
third and fourth characters in the Direction parameter.
3. Use COM1, 9600 baud, K9Xmodem Batch Send files in MYLIST.LST which
resides in my C:\BBS\ directory. The files listed in MYLIST.LST
reside in various directories on different drives. Do not monitor
carrier and record success results to Node A of my BBS.
SUPERK p1 s9600 SKB m nA f @C:\BBS\MYLIST.LST
C:\BBS\MYLIST.LST looks like this:
ABC.PAK (this one resides in the default directory)
D:\FOO\BAR\MYGAME.EXE
E:\LOTUS\123GRAPH.PAK
XFER.TXT (or XFERA.TXT if ? specified in the default xferfile name)
will reflect the results of the transfer. Note that only the first
filename and its transfer results will be present in XFER.TXT.
SUPERK.LOG will however, contain the results of all three files.
4. Use COM2, 19200 baud, K9Xmodem Batch Send only files containing an
PAK extension and residing in my C:\DLS directory, and don't monitor
carrier.
SUPERK p2 s19200 SKB m f C:\DLS\*.PAK
5. Use COM2, 19200 baud, K9Xmodem Batch Receive files - store them in
my C:\DLS directory.
SUPERK p2 s19200 RKB f C:\DLS
Batch Files
~~~~~~~~~~~
There are sample batch files included in SUPERK.PAK
SEND.BAT - this batch file is set up for sending file(s) to
another system
RECV.BAT - this batch file is set up to receive file(s) from
another system
Executing any one of the batch files without any parameters (or the
wrong parameter) will display a short message showing the correct
calling procedure and parameter choices. Since these batch files handle
transfers in either Send or Receive mode and single or batch mode, you
will have to supply the proper information in order to have them perform
correctly.
NOTE: If you are operating a MiniNet BBS v18.00 or above... or K9X v8.xx or
above... access to SuperK is handled internally and does not require
the use of the batch files.
If you are not... please read the enclosed PRODUCTS.TXT file... It's
worth a look!
For pure BBS'ing, K9X can't be beat!
------------------------------------------------------------------------------
I have been using this protocol driver on Underdog's MiniNet for quite
some time now. If you need more information on the various transfer
protocols, please get a copy of K9X (my comm program) and review the
K9X.DOC file contained in that package. All suggestions are gratefully
received and reviewed! Let me know...
Sal Manaro dba Crater Rim Softare
4028 41st Ave South
Seattle, Wa 98118 USA
(206) 723-6728 voice
Underdog's MiniNet (206) 725-9233
1200/2400/9600 24hrs 600 megs OnLine
Supporting 22 files transfer protocols!
Enjoy,
Sal Manaro
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
N O T I C E N O T I C E N O T I C E N O T I C E N O T I C E
Due to the amount of time and money I have spent setting up SuperK for
use with your Comm/BBS programs, I am requesting that this and all
subsequent versions of SuperK be registered so that I may be
compensated for the many hours I have spent developing, modifying and
setting up this protocol driver.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
LET YOUR PRINTER DO ALL THE WORK!!!
------------------- INSTANT MAILER ----------------------
Please support quality shareware by registering your copies
We thank you for your support!
Remit To: Sal Manaro dba Crater Rim Software SuperK Order Form
4028 41st Ave. South
Seattle, WA 98118 USA
Quantity Discount Schedule (per purchase). Each:
1-10 $20.00 11-49 $18.00 50-99 $15.00
100-199 $12.00 200-499 $10.00 500+ $ 8.00
Please send the ShareWare Evaluation version 4.00
-------------------------------------------------
____ SuperK Disk(s) without registration ...... @ $ 8.00 ea. $ _______
I would like to register the copy I already have:
------------------------------------------------
____ SuperK Registration(s) Only .............. @ $ 15.00 ea. $ _______
Please register and send the latest version:
-------------------------------------------
____ SuperK Registration(s) and Disk .......... @ $ 20.00 or $ _______
PO, Rush and COD orders add $5.00 ........................... $ _______
Subtotal _______
(Washington residents please add 8% sales tax) Tax _______
Total $ _______
Payment by: ( ) Check ( ) Money Order ( ) PO # ___________________
Use address on check ( ) or mail to:
Name: ______________________________________________________________
Company: ______________________________________________________________
Address: ______________________________________________________________
: ______________________________________________________________
: ______________________________________________________________
Day Phone: (______)__________________ Eve: (______)______________________
ORDERS OUTSIDE USA: Use Check or Money Order drawn on US bank in US dollars
------------------- INSTANT MAILER ----------------------
Fold at the page break below with the printing above facing up and the
mailing label below folded underneath. Staple check to the mailer, fold
letter style, exposing the mailing address and hiding your information.
Fold sides along dotted line and staple or tape sides and top.
|_________________________________ Place |
| |
|_________________________________ Stamp |
| |
|_________________________________ Here |
| |
| |
| |
| |
| |
| |
| Crater Rim Software |
| 4028 41st Ave South |
| Seattle WA 98118 USA |
| |
| |
| |
| |