home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
OFFLINE
/
WINK110.ZIP
/
WINK.DOC
< prev
next >
Wrap
Text File
|
1992-12-04
|
18KB
|
539 lines
┌────────────────────────────────────────────────────────────────────────────┐
│ ╔════════════════════════════════════════════════════════════════════════╗ │
│ ║ ║ │
│ ║ QWK as a WINK ;-) ║ │
│ ║ ║ │
│ ╚════════════════════════════════════════════════════════════════════════╝ │
│ │
│ │
│ Copyright 1992 Keith Ford │
│ __ │
│ / \ │
│ \__/ │
│ [__] │
│ │
│ Micro Magic │
│ │
└────────────────────────────────────────────────────────────────────────────┘
┌───────────────────┐
│ TABLE OF CONTENTS │
└───────────────────┘
INTRODUCTION
FEATURES
MANIFEST
QUICK START
REGISTERING
WHERE TO FIND WINK
CONTACTING THE AUTHOR
VERSION NUMBERS
PROGRAM DETAILS
- WINK.HLP
- MULTILINE SUPPORT
- RUNNING LOCAL OR STANDALONE
- AREA NAMING
- WHERE WINK LOOKS FOR FILES
- USING WINK COMMAND LINE ARGUMENTS
- WHICH FILES ARE MODIFIED
- MENU DESCRIPTION
- WINK.CFG FORMAT
- WINK.USR FORMAT
THE AUTHOR
FUTURE PLANS
COMMON QUESTIONS
FOR THE TECHNO HUMOR IMPAIRED
┌──────────────┐
│ INTRODUCTION │
└──────────────┘
WINK is a door for the Opus CBCS. WINK provides your users access to
messages using the QWK mail format. It is very tightly intergrated
with Opus, making it easy to set up for you and easy to operate for
your users.
What does WINK cost? The same as my other Opus programs OBUL, OASWAP,
and ARKALOG. Nothing. WINK is free software in the Opus tradition.
Enjoy it and please report any "features-of-ill-repute" to the author.
There is a registration option mentioned later in this document.
┌──────────┐
│ FEATURES │
└──────────┘
The following is a list of the major features found in WINK. If you
would like to see something added to this list, contact the author.
- works with Opus 1.1x and up
- supports multiline/multitask usage
- works with any com port via FOSSIL
- runs remote and local
- runs stand alone if last login was local
- sysop defined file archivers
- sysop defined transfer protocols
- handles messages of any size
- no door/drop file needed, pulls info from Opus files
- checks privileges & locks for area access
- checks privileges & locks for edit access
- prevents forged messages
- prevents adding messages to readonly areas
- private message posted in public area is made public
- filenames can be task number tagged
- generates echotoss.log file
- update all last read pointers
- does not download authored messages
- commands can be stacked
- new pine scent with no greasy residue
┌──────────┐
│ MANIFEST │
└──────────┘
WINK.HIS - release history & quick upgrade instructions
WINK11.EXE - the Opus 1.1x executable
WINK17.EXE - the Opus 1.7x/1.8x/1.9x executable
WINK.CFG - quick start configuration file
WINK_CFG.DOC - docs for configuration file
WINK.DOC - this documentation
WINK.HLP - sample intro screen
You may have a package that contains only one executable.
┌─────────────┐
│ QUICK START │
└─────────────┘
If you are upgrading from the last release, you should read
WINK.HIS for quick upgrade instructions.
If you are installing WINK for the first time, then follow
these instructions.
- copy all files to your Opus directory
- rename the appropriate EXE version to WINK.EXE
- edit WINK.CFG and follow directions listed there
- add an Opus menu option, for example:
_OUTSIDE Normal "WINK" = DOS c:\opus\wink.exe
- time to rock-n-roll (Rush preferred)
NOTE: The quick start CFG file requires that PKZIP,
PKUNZIP, and DSZ be located in your PATH.
┌─────────────┐
│ REGISTERING │
└─────────────┘
If you decided to send a monetary donation to the author you will:
- receive a special version of the WINK Door which
adds a plaque proclaiming your registered support
- receive express attention in submitted bug fixes
and any enhancements that you request
- receive beta releases of new versions and planned
new support utilities
- see to it that WINK development continues for the
enjoyment of future generations of Cool Shades
- receive a registration program to auto register
future releases
- get that warm fuzzy feeling
To register WINK, send a contribution of 10-25 $US to the author.
Be sure to select a shipping option from the list below and include
a copy of the SYSOP variable from the SYSTEM SECTION of your Opus
BBS.CTL file.
This name will be used as the registration key. It will also be
placed in the QWK control file that is sent to your users and
will also be placed on your registration plaque. If this name
is incorrect, please include an explanation.
SYSTEM SECTION
%
SYSOP Keith Ford
%
When selecting a shipping option, be sure to include ALL the needed
information such as passwords, phone numbers, addresses, etc.
The shipping options are many. Please pick one.
- uuencode and email (preferred)
[ need your Internet email address]
- file attach to your Fidonet node
[ need your net address]
- login to your bbs and upload
[ need login/password/filearea with upload privileges ]
- snail mail
[ need your address ]
- personal delivery
[ need your car ]
┌────────────────────┐
│ WHERE TO FIND WINK │
└────────────────────┘
Majore releases will be placed into SDSOPUS.
The authors bbs, Micro Magic (1:373/12), will always have the latest
for FREQ or download on first call.
For those with Internet/UUCP email access, you can WINK uuencoded and
emailed to you. Send email to server@ingr.com with "HELP" in the
subject line for more information.
Michael Goddard, of BCH BBS in Canada (1:163/140), has also made WINK
available for those with anonymous ftp capabilities. The site name is
m.ehd.hwc.ca [142.4.8.13].
┌───────────────────────┐
│ CONTACTING THE AUTHOR │
└───────────────────────┘
BBS NAME: Micro Magic
BBS PHONE: +1 205 830 2362
MODEM: USR DS - HST/V32bis
FREQ: (see VERSION NUMBERS)
FIDONET: 1:373/12
INTERNET: sysop@umagic.fidonet.org
SNAIL: 203 Creek Trail, Madison, AL, 35758
ICBM: 34 44 18 N / 86 35 19 W
WINK will always be available on Micro Magic. See the VERSION NUMBERS
section of this text for file request information.
┌─────────────────┐
│ VERSION NUMBERS │
└─────────────────┘
The following Magic names and filenames are strongly recommended. If you
choses to make WINK available on your system, please attempt to follow
this naming convention. I'm not being a stinker about it, I just think
it will be easier for others use if it is consistent.
Magic Names
WINKBETA - current betas of all executables & associated files
WINK - all production executables & associated files
WINK11 - Opus 1.1x only production executables & associated files
WINK17 - Opus 1.7x only production executables & associated files
Filenames have changed, the now use the formula:
"WINK" + <Version#> + <Opus-ID>
Current list of Opus-IDs
'#' - betas
- all Opus versions (no Opus-ID)
A - Small memory model for Opus 1.1x
B - Small memory model for Opus 1.7x
The version number of WINK will always be a 3 digit hexadecimal number,
X.Y.Z, where X, Y, & Z are defined as follows.
X - major change, if you use this EXE you MUST change your
CFG file according to the release notes
Y - new features, you can use this EXE without changing your
CFG file, but to use the new features you may need to change
your CFG file according to the release notes
Z - bug fix, simply replace the executable and read the
relese notes
When WINK runs, the tear line it adds will include this version number.
If it is a beta WINK, a 'b' will be appended, as in "1.1.0b".
For version 1.0.1, the filename would be WINK101.ZIP.
For Opus 1.1x, version 1.0.0, the filename would be WINK100A.ZIP.
WINKBETA may be WINK105#.ZIP
┌─────────────────┐
│ PROGRAM DETAILS │
└─────────────────┘
WINK.HLP:
---------
This file is optional, but if used it must be placed in the directory
where WINK starts. You can edit this file as you need. It's contents
are shown to the user when they enter the WINK door. It can be used
to introduce WINK, explain what QWK is, or whatever.
MULTILINE SUPPORT:
------------------
WINK read the Opus PRM file for much of its information. If you have a
multiline system, you will have multiple PRM files. For WINK to work,
it must be told where the PRM file is located. You can do this with
the OPUS environment variable or with the -PRM command line parameter.
For more information on where WINK looks for files, read the section
named "WHERE WINK LOOKS FOR FILES" in this text.
Any filename specified with WINK that contains a # or ## will
be modified such that the # or ## is replaced with the hexadecimal
task number. If these files are not found, the name is modified
again to exclude the task numbers. If task number is decimal 10,
then WINK##.CFG would be WINK0A.cfg, then WINK.CFG. Therefore, when
you start WINK for the first time, it will create a WINK01.USR file,
based upon the task number. If you rename this to WINK.USR, and place
it in the Opus directory, all lines can share it.
RUNNING LOCAL OR STANDALONE:
----------------------------
When in one of these modes, WINK places <bbsid>.QWK in the temporary
directory and looks for <bbsid>.REP there too. The temporary directory
is found in the PRM file or from the WINK -TMP command line argument.
WINK reads the LASTUSER record, so running STANDALONE will run as if
that person were logged on. Use OPUS -K if you need to change the
LASTUSER record to be yours.
AREA NAMING:
------------
The name of a message area is limited to 10 characters. In Opus 1.1x,
the first 10 characters of the message area name are used. In Opus
1.7x, the first area name definition in the CTL file is used. Opus allows
you to define this area name two different ways.
(#1) AREA 0001 Meadow
(#2) AREA 0002
NAME Meadow
WHERE WINK LOOKS FOR FILES:
---------------------------
look for OPUS environment variable pointing to PRM
check command line parameters:
-log : path to LOG file
-prm : path to bbs PRM file (overrides environment variable)
-sys : directory containing area definitions SYS
-lastus : directory containing LASTUS file
-opus : directory of OPUSROOT (echotoss, 1.1x LASTUS)
-tmp : directory for temporary work files TMP
-cfg : path to wink CFG file
-usr : path to wink USR file
if PRM and !OPUSROOT, form OPUSROOT from PRM by stripping PRM filename
else if !PRM and OPUSROOT, form PRM from OPUSROOT plus bbs.prm
if !PRM, use current directory
if !LOG, get from PRM
if !LASTUS, 1.1x uses opusroot & 1.7x looks in PRM
if !TMP, get from PRM, append WINKxx.TMP
if !SYS, get from PRM
1.1x looks for SYSTEMxx.DAT files
1.7x looks for sysmsg.dat
if !CFG, look in current directory
if !USR, look in current directory
echotoss.log uses
1.1x - opusroot
1.7x - get from PRM
USING WINK COMMAND LINE ARGUMENTS:
----------------------------------
For example, to use a separate log file and a different
temporary directory than Opus:
wink -log c:\tmp\wink.log -tmp r:\tmp
WHICH FILES ARE MODIFIED:
-------------------------
wink##.usr
lastus##.dat
last read files
- user.dat (Opus 1.1x)
- LASTREAD (Opus 1.1x, Opus 1.7x if requested in BBS.PRM)
- LREAD.DAT (Opus 1.7x)
MENU DESCRIPTION:
-----------------
C........user configuration for packer & protocol
#........toggle area # on and off
#f.......toggle flag f for area # on and off
(only P flag supported for Personal messages)
L........list available message areas
L#.......list available message areas starting with #
LS.......list selected message areas
LS#......list selected message areas starting with #
D........download QWK packet
DP.......override area flags, download only personal messages
DA.......override area flags, download all messages
U........upload REP packet
Q........quit back to the bbs
G........goodbye and logoff now
=........credits
*........registration plaque
?........help
WINK.CFG FORMAT:
----------------
See WINK_CFG.DOC file for this information.
WINK.USR FORMAT:
----------------
You should not need to worry about this file. If something goes
wrong, you can edit it by hand to an extent. Following is the
format for a record in this file. This record is repeated for
each active WINK user.
User Name
userflags
crc-of-packer-menu-text
crc-of-protocol-menu-text
area# flags
area# flags
area# flags
┌────────────┐
│ THE AUTHOR │
└────────────┘
What would you like to know? My name is Keith Ford. I'm a 3-year-old
dad (heaven help me). I like chocolate, the DragonLance series, and
hard rock/metal music (Rush, Cinderella, Def Leppard, LA Guns). My
bbs iron is a 386SX-16, 4 Megs, 200 Meg HD, DAK CDROM, and USR DS.
I've run Opus since 4/90 and operate a UUCP/Fidonet gateway with
UFGATE, all under DESQview. I still don't have a 3.5" floppy drive,
but I once had a Toyota 4WD. I can do the Time Warp. God bless.
Other software available from the author.
OBUL - Generate a .BBS file that presents a menu to a caller.
This menu is based upon a list of bulletins provided
by the sysop. Any bulletins which have been modified
since the user last visited, are marked on the menu.
This works for Opus 1.1x and up.
ARKALOG - Archive a log file with date embedded in the filename.
Such as OLOG9210.LZH would be my Opus log for the 10th
month of 1992. This program also has a day of the week
check to automate weekly functions. It will work with
any Opus, or any bbs.
OASWAP - In Opus 1.1x message & file areas are tied together.
OASWAP will allow you to swap between areas the message
or file information independently of one another. This
works with Opus 1.1x only.
┌──────────────┐
│ FUTURE PLANS │
└──────────────┘
- sysop defined menu coloring
- sysop defined area names
- sysop exclusion of certain message areas
- multiple language using '~'
- menu option to set/reset last read pointers
- sysop defined NEWFILES generation command
- use PEEK privs/locks for private in public echos
- handle area number greater than 255
- send messages that match a search string
- use Opus origin lines
- use Opus menu help level
- reduce memory requirements
- allow it to operate as a vacation mail catcher
- define a place to dump bad messages
- implement ADD/DROP/REQUEST
- add capability to use Netmail
- add file locking to user.dat
- user switch to send no-mail packets
- flag to send messages user has written
┌──────────────────┐
│ COMMON QUESTIONS │
└──────────────────┘
Q. I'm having problems. What do I do?
A. Look at your log file and see what WINK is thinking. Use this
information and the section of the docs that describe where WINK
finds files to see if you can fix your problem. If not, send as
much information as possible to the author for review.
Q. I log into line #1 and everything works fine. Then I log into
line #2 and WINK says I'm a new user. Why?
A. When you run WINK the first time, if not told differently, it
attempts to open WINK##.USR. This fails since it does not exists.
It then attempts to open WINK.USR, which also fails. Then it
opens WINK##.USR again as a new file. So, your user information
was originally put into WINK01.USR, then you logged onto line #2
and WINK create WINK02.USR. To get around this, rename WINK01.USR
to WINK.USR and delete other WINK##.USR files. Then, all tasks
will use WINK.USR.
Q. I appear to be running out of memory.
A. If you have a large number of message areas, WINK may be running
out of memory using the Small Memory Model. Ask the author for a
Medium Memory Model version. If WINK simply won't fit in memory,
you might try using an EXIT ## to run WINK without Opus loaded or
use the Opus Child program to swap Opus to disk.
Q. WINK says I have some message areas that I removed from my BBS.CTL
file earlier?
A. Apparently, for Opus 1.1x, SALT does not delete old SYSTEM##.DAT
files for message areas that have disappeared. (via John Emmert)
┌───────────────────────────────┐
│ FOR THE TECHNO HUMOR IMPAIRED │
└───────────────────────────────┘
An emoticon is a small figure (icon) comprised of ASCII characters
used to denote and emotion. Many emoticons depict a face and require
you to tilt your head (or monitor) to the left (or right). The ";-)"
is an emoticon representing a winking face, to denote humor,
understanding, sarcasm, and such. So there you have it, or not. ;-)
-kef/MM-