home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 8
/
CDASC08.ISO
/
VRAC
/
RIPIV101.ZIP
/
RIPIV.DOC
< prev
next >
Wrap
Text File
|
1993-08-19
|
14KB
|
255 lines
┌──────┐ ┌───────┐ ┌──────┐ ┌───────┐ ┌─┐ ┌─┐
│ ┌───┐└┐ └──┐ ┌──┘ │ ┌───┐└┐ └──┐ ┌──┘ │ │ │ │
│ │ ┌┘ │ │ │ │ │ ┌┘ │ │ │ │ │ │ │
│ └──┘ ┌┘ │ │ │ └──┘ ┌┘ ┌────┐ │ │ │ │ │ │
│ ┌──┐ └┐ │ │ │ ┌────┘ └────┘ │ │ │ └┐ ┌┘ │
│ │ └┐ │ │ │ │ │ │ │ └┐ └─┘ ┌┘
│ │ │ │┌┐┌──┘ └──┐┌┐│ │┌┐ ┌──┘ └──┐┌┐ └┐ ┌┘┌┐
└─┘ └─┘└┘└───────┘└┘└─┘└┘ └───────┘└┘ └───┘ └┘
We've got your medicine!
│ The RIP Icon Verifier v1.01
┌─┐ ├─┬─┬─┬─┬─┬─┬─┬─┬─┬─┬─┬─┬─┬─┬─┬┐
│█├──────────┤ │ │▓│░░░│░░░│░░░│░░░│░░░│░░░│├─┐
│█│██████████│700│600░500░400░300░200░100░░0│█├──────────────
│█├──────────┤ │▓│░░░░░░░░░░░░░░░░░░░░░░░░├─┘
└─┘ ├───┴─┴────────────────────────┘
│ (c)1993, ArenaSoft, Inc.
All rights reserved.
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ About RIP-IV v1.01 ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
RIP-IV is written using MS QuickBasic Extended 7.1 Professional. It
took about 3 cases of Programmer/Operator Petrol (POP) and cost about 4,000
individual hairs to finish. On a more serious note, I would really like to
thank Mark over at TeleGrafix Communications for all the invaluable help he
gave me. In all honesty, RIP-IV would have never made it past a stupid toy
if he had not helped me debug the crucial RIP_FILE_QUERY and RIP_BLOCK_MODE
sections of the code. I also want to tell you about the vacation I took in
July. I had just finished with my last novel, and.....
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ What's New In Version 1.01? ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
Well, not a whole lot, to be honest. I've fixed a couple bugs which
some people never knew existed, and updated the documentation to show it.
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ Introduction ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
Well, let's begin by saying that I don't much care for documentation
that takes a day and a half to read, so I am going to make the majority of
it short and sweet. If I hear too many complaints that it is too short, or
if too many people call up with silly questions, then I will re-write it so
that it includes the history of the world and all my golf scores this year.
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ Credits ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
Just to keep everything in good order:
- The RIP Icon Verifier is (c)1993 by ArenaSoft, Inc.
Written by Randy Schad. The RIP-IV name and the
hypodermic needle are trademarks of ArenaSoft, Inc.
All documents and included files (except DSZ.COM)
are copyrighted by ArenaSoft, Inc.
- RIPscrip, RIPaint, RIPdraw, and RIPterm are all trademarks of
TeleGrafix Communications, Inc.
- Qmodem Pro is a trademark of Mustang Software, Inc.
- DSZ.COM is copyrighted by Owen Technology, Inc.
- ZIP, PKZIP, PKUNZIP, etc. are trademarks of PKWare, Inc.
- ARJ is copyrighted by Robert K. Jung.
- PAK is copyrighted by NoGate Consulting.
- ARC is copyrighted by System Enhancement Associates, Inc.
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ What does RIP-IV do? ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
RIP-IV is a utility for virtually ANY Bulletin Board System that has
RIPscrip graphics available. Most RIP menus display a few bit-mapped icons
on each screen. For speed, the guys at TeleGrafix decided it would be best
if these icons were stored as files on the remote terminal end, and let the
host call them up when they are needed. (Are you still with me?)
The problem with this is that every time the Sysop changes a menu to
include a new icon, each individual user must download that icon. And most
Sysops don't want to take the time to set up each individual icon for down-
loading, nor do users want to download an entire archive of icon files when
they only need the few new ones. (See where this is going yet?)
So RIP-IV was designed to fix all of that. It compares all the icon
files on the host system with all those on the remote. When RIP-IV detects
a missing file on the remote end, it queues that file up for download.
After RIP-IV has checked through the entire host system, it lets the
remote user decide how he/she wants to receive the files. They can either:
1). Have all new icon files compressed and archived for downloading. Then,
once the transfer is complete, they can jump to DOS and extract the new
icons into their icon directory; OR,
2). Have RIP-IV AUTOMATICALLY INSTALL the new icons. The program transfers
the files directly into the user's icon directory, one at a time, with-
out the user doing anything at all... It's fully automated from here!
So that's what RIP-IV does. Now we'll get into setting it all up.
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ Installation ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
Make sure you have read this section COMPLETELY before attempting to
set up RIP-IV. Failure to do may result in improper program execution.
First, make sure all necessary files were included in the archive. A
complete file listing can be found in the "Files in this archive" section.
Place RIP-IV and all its files into its own directory. This is not a
necessary installation procedure, but it helps keep things from cluttering.
It also helps when the program uses its work sub-directories.
Run the RIP-IV installation program IVSETUP.EXE. If you are setting
up RIP-IV for the first time, you will need to let IVSETUP create it's work
directories, which are \WORK and \OUTBOUND. RIP-IV MUST have these two sub-
directories in order to function at all. It does not matter what directory
RIP-IV is in, just as long as RIP-IV's directory has its sub-directories.
If you don't feel comfortable letting IVSETUP create the directories
you may exit the program and create them yourself.
You will also need to let IVSETUP create your RIPIV.CFG file. While
you COULD create and edit the file with any ordinary text editor, I suggest
that you let IVSETUP do the work. (It helps eliminate silly mistakes.)
Once the sub-directories are in place and you are sure the RIPIV.CFG
file has been created, you may begin with the configuration. The following
section goes into more detail on the commands and functions of IVSETUP.
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ Configuration ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
To configure RIP-IV, run the configuration program IVSETUP.EXE. Run
through this checklist to make sure you've entered data for all fields:
1). The Path to your BBS Drop File (like: C:\BBS\DORINFO1.DEF)
2). The BBS Name (The name of your BBS...duh!)
3). Sysop's First Name (You should know this one by now!)
4). Sysop's Last Name (This one too!)
5). Path to RIP icon files (include trailing backslash, like: C:\BBS\RIP\)
6). Filename of icon files (use wildcards, like: *.ICN)
7). Command to invoke archiver [name] [switches] (like: PKZIP -a -o)
8). Name you want the archive to have (like: ASI_ICON.ZIP)
9). Registration number (see Registration section or REGISTER.DOC for info)
The RIPIV.CFG file is totally ASCII based, which makes it accessible
to any ordinary text editor. When editing, use the exact order above, with
each item on a line by itself, beginning in the very first column. EXCEPT:
When inserting your registration code, insert a SPACE before typing in your
registration number. If you fail to do this, RIP-IV will not recognize the
code as valid, and you'll be giving us a call wondering what's wrong.
And that basically does it for the configuration. Now for operation:
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ Operation ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
Most BBS systems run external doors out of a batch file. If so, set
up your batch file so that you first change to the RIP-IV directory, before
giving the command to start the program. After RIP-IV has finished up, you
should change back to your system directory and exit the batch file.
A sample batch file (mine) looks like this:
CD \BBS\DOORS\RIPIV
RIPIV.EXE RIPIV.CFG
CD \BBS
Note that the configuration file MUST BE SPECIFIED immediately after
the filename. If you don't specify the configuration file RIP-IV will exit
with the "No configuration file specified" error and return control to your
system. All errors that occur (including this one) will be logged to a log
file named DFRAME.ERR for troubleshooting purposes.
MULTI-NODE SYSOPS: I have not tested this on a multi-node system, so
I'm not real sure how well it will work out. All other doors from ArenaSoft
never had any problems, so I'm not expecting any out of RIP-IV either.
To run the program on a multi-node system, you may need to have more
than one configuration file. If so, simply copy RIPIV.CFG to RIPIVxxx.CFG,
replacing the xxx with the node number. Then, when you call the program on
that node, have your batch file read: RIPIV.EXE RIPIVxxx.CFG.
I have also been informed by some Sysops whose BBS software uses the
DORINFOx.DEF drop file that once the configuration file has been copied, it
should be edited (using a text editor) to reflect the DORINFOx node number.
I would assume that you could set up RIPIV.CFG for one node, copy it to the
RIPIVxxx.CFG name, then go back into IVSETUP and edit RIPIV.CFG for another
node, repreating the process as necessary. (I dunno...)
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ Liability ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
ArenaSoft, Inc. provides this package "as-is" without any guarantees
of any kind, expressed or implied. ArenaSoft shall not be held liable for
any loss or damage resulting from the use (or misuse) of any portion of the
RIP-IV software package. The use of this product constitutes acceptance of
this liability agreement.
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ Shareware License Agreement ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
License is hereby granted for the use of this product for evaluation
purposes only. If you wish to continue using this product after the thirty
(30) day evaluation period, you must register or discontinue use. Failure
to register after the evaluation period has expired constitutes a violation
of this license agreement and the loss of rights to this license.
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ Technical Support ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
You may obtain technical support by one of the following:
The Arena BBS: 419-636-7197
ArenaSoft,Inc: 419-636-3265
C-$erve EMail: 71174,637
FidoNet EMail: 1:234/44
ArenaSoft's hours: Monday thru Friday - 8am to 5pm
The Arena BBS always has the latest releases.
Address all E-Mail to Randy Schad.
┌───────────────────────────────────────────────────────────────────────────┐
│ ░░░ History ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
└───────────────────────────────────────────────────────────────────────────┘
Version 1.00 -- The first Shareware release of RIP-IV.
Version 1.01 -- Fixed a bug in the registration variable that caused RIP-IV
to "hang" due to a variable overflow. The variable has now
been declared as a LONG variable, and the bug was squashed.
Also fixed a problem in IVSETUP which caused a couple lines
to not be saved to the RIPIV.CFG file. (It was just a typo,
I misspelled a couple variable names.)
END OF DOCUMENTATION