home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Black Box 4
/
BlackBox.cdr
/
bbs_opus
/
mobyop02.arj
/
MOBYOPUS.DOC
< prev
Wrap
Text File
|
1991-03-02
|
8KB
|
205 lines
MobyOpus
AN INTERFACE FOR DSZ for OPUS CBCS
Written by Clinton LaRue
Barn Owl BBS
1:108/165
MobyOpus is an interface that calls Omen Technology's DSZ program and
makes use of the MobyTurbo feature which Omen has installed in recent
releases of DSZ. MobyOpus tries to determine what kind of data you are
working with and helps DSZ select the best options for the transfer.
DISCLAIMER
This program is distributed on an "as is" basis. The author assumes no
responsibility for any problems or errors incurred with the use of this
software. By using this software, you are implying that you understand
the above statement.
The files contained in this package are released free of charge and may
be used under the above stipulations.
The D)SZ-ZMOD and G)YMODEMG interfaces have been tested extensively
with Opus software and have been found to be relatively error free. As
with any new software, problems may arise. Please contact the author
via NetMail should you discover any errors, and every attempt will be
made to correct them.
The Following Files Should Be Contained In This Package:
DSZ-ZMOD.EXE 03/01/91 37015 bytes
GYMODEMG.EXE 03/01/91 36999 bytes
MOBYOPUS.DOC This File
* * * * * * * * * *
FEATURES
1) Supports single or batch uploads and downloads in all Z Modem
forms.
2) MobyOpus automatically calls for the Compression option if
the file being uploaded or downloaded has one of the follow-
ing extensions:
.DOC .LST .LOG .TXT .ASM .BAT .MAP .REF .CTL .CFG
(If you come up with any other file types that are of a text
type let me know and I will add them to the internal table.)
The Compression option can give significant improvements in
speed on text type files.
3) If the file type isn't one of the above mentioned file types
MobyOpus will automatically call for MobyTurbo compression.
This type of compression gives you improvements with .ZIP
.ARC and other binary type files.
4) If the Z Modem on the user's end does not support compression
or MobyTurbo then it will fall back to normal Z Modem!
5) Unlike other external protocols, MobyOpus will write a log
file which Opus will use to read and adjust user's upload
and download limits.
* 6) The interfaces will now write directly to your BBS log file
showing the DSZ statistics.
REQUIREMENTS
1) You must have a registered copy of DSZ. The reason for this
is because some of the "registered only" features are being
used by this program. This is not necessary from the user's
end. DSZ can be registered from Omen Technology. The order
forms, etc., are contained in the DSZ package.
2) Your BBS and the user on the other end must have a version
of DSZ that supports both the Compression and MobyTurbo op-
tions. I believe this support was included in the 02/18/90
and later versions of DSZ.
3) If the user wishes to invoke MobyTurbo via DSZ, he must add
the -m switch to his DSZ command line. Example:
DSZ rz -m
DSZ sz -m
INSTALLATION
1) You will need to add the following three SET statements to
your AUTOEXEC.BAT file:
SET DSZ-ZMOD=C:\OPUS\
SET GYMODEMG=C:\OPUS\
SET DSZLOG=C:\OPUS\DSZWORK.LOG
The SET DSZ-ZMOD(GYMODEMG)=C:\OPUS tells the interface where
it will be called from. (Normally it will be located in your
Opus main directory.)
The SET DSZLOG=C:\OPUS\DSZWORK.LOG tells DSZ to write a work
log file to the Opus main directory and instructs it to be
named DSZWORK.LOG. (The DSZWORK.LOG name is cut in stone at
this time.) This log handles both protocols.
2) Add the following statements to your BBS.CTL (or whatever
you call your control file) and re-compile (SALT) it; or if
you use OPIE, edit line 19, then PEPPER and SALT it:
EXTERNAL Protocol C:\OPUS\DSZ-ZMOD.EXE
EXTERNAL Protocol C:\OPUS\GYMODEMG.EXE
This tells Opus the name of the protocol and where it is to
be found.
3) Put the DSZ-ZMOD.EXE and the GYMODEMG.EXE files in your Opus
main directory.
4) Put the DSZ.EXE or DSZ.COM program (it doesn't matter which)
somewhere in your path statement so the interface can find
it. (The DSZ.EXE {or .COM} does not have to be in the Opus
main directory.)
* Optional: Occasionally, the interface may hang a system. This appears
to be caused by the fossil driver and the interface not communicating
properly. The following procedure will rectify that problem.
Create two files with a text editor in your Opus subdirectory,
one called FOSSIL.REL and the other called FOSSIL.CAP. The
FOSSIL.REL file will contain statements that will release the
fossil driver when MobyOpus is called. Likewise, FOSSIL.CAP
will re-capture the fossil upon termination of MobyOpus. Here
are examples of each:
<FOSSIL.REL>
c:\bnu170\bnu /q (Sample command line for BNU 1.70)
c:\x00\XU CAPTURE:OFF (Sample command line for X00 1.23)
The /q tells the fossil driver to release itself from
the COM Port so that it doesn't interfere with DSZ.
<FOSSIL.CAP>
c:\bnu170\bnu /c (Sample command line for BNU 1.70)
c:\x00\XU CAPTURE:ON (Sample command line for X00 1.23)
The /c tells the fossil driver to recapture the COM Port
so your BBS will run. (WARNING: FAILURE TO RECAPTURE THE
FOSSIL WILL RESULT IN A HUNG SYSTEM!)
The FOSSIL.REL and FOSSIL.CAP are not mandatory. If you do not create
them, the interface will work just as it has in the past.
NOTE: The first time the external protocols are invoked by a user, a
"File Not Found" message will appear on your screen. MobyOpus
is attempting to erase the DSZWORK.LOG file so Opus can adjust
the limits for the current user. This message will not appear
again.
That's it! You should be up and running, and all in a matter of just
a few short minutes.
* = Release 2 in December, 1990. Added Fossil release/capture feature.
NOTES
DSZ is a registered trademark of Omen Technology.
OPUS is a registered trademark of Wynn Wagner III.
LHARC is a registered trademark of Haruyasu Yoshizaki
The documentation was written and edited by Chuck Ammon of ANYTHING GOES
BBS in Pittsburgh, PA. 129/112 in FidoNet.
Clinton LaRue
Barn Owl BBS
1:108/165 in FidoNet