home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
New Horizons Shareware Collection
/
HORIZONS1.BIN
/
WMINSTAL.INF
< prev
next >
Wrap
Text File
|
1994-07-30
|
21KB
|
442 lines
---------------------------------------------------------------------------
WILDMAIL! v3.5/v4.0 Installation Information
Date: 07/02/1994
---------------------------------------------------------------------------
Dear WILDCAT! SysOp:
We'd like to take this moment to thank you for choosing WILDMAIL! as your
mail tosser for your FTSC mail needs. We're extremely proud to release
this new release because it incorporates what you as a SysOp has asked for
and does so with a much needed speed increase along with a features list
that easily establishes itself as the leader in FTSC mail processing.
Installation
------------
WMINSTAL! will be the program that you execute either from the
installation diskette or from a drive/directory of your choice.
BBS Download
------------
If you've downloaded this new release from a BBS, you should create a
temporary directory and uncompress the contents of the distribution
archive using PKZIP into that directory.
Similar to: C: <Press Enter>
MD \tempdir <Press Enter>
COPY <archive> C:\tempdir <Press Enter>
CD \tempdir <Press Enter>
PKUNZIP <archive> <Press Enter>
When choosing a temporary directory to install from, you should NOT use
one called \WM40, especially of it's on the drive you're attempting to
install to. Instead, simply use a different name. From there you would
simply execute WMINSTAL from the DOS prompt such as:
WMINSTAL <Press Enter>
and follow the instructions on the screen. If you're unsure about a
particular option, position the highlight bar on that field and
press [F1] for online help information.
Installation Diskette
---------------------
If you are installing from the installation diskette, you simply
need to change directories to that drive and type WMINSTAL.
Similar to: A: <Press Enter>
WMINSTAL <Press Enter>
From here, simply follow the instructions on the screen. If you're
unsure about a particular option, position the highlight bar on
that field and press [F1] for online help information.
Depending on your installation requirements, this program has up to two
major steps to it. The first step performs the creation of
subdirectories, moving of files etc. The second, if so chosen will
convert your previous installation of WILDMAIL! v3 to the new data
structures.
Listed below are the available installation types.
Normal Install
--------------
WMINSTAL! will require you to enter the destination drive along with your
primary address as well as the location where you pick up your mail from.
This is typically referred to as your "hub" or "uplink/feed" address.
You may begin the installation by pressing [F10] and then after some
initial checking configuration checking, WMINSTAL! will create the
necessary directories and then proceed to uncompress the contents of
WM4FILES.DAT into the \WM40 directory. Once the uncompression process is
complete and the files are moved to their respective directories, a screen
will be displayed indicating the installation is complete and you will be
returned to the previous menu.
Install/Upgrade
---------------
This process is a combination of a "Normal Install" and an upgrade. You
would typically select this option if you already have a previous version
of WILDMAIL! and would like to have the datafiles converted over to the
new formats.
NOTE: Only v3.00 thru v3.11 releases of WILDMAIL! can be upgraded with
WMINSTAL!. Any of the earlier versions will require you to use the
upgrade program that came with v3 of WILDMAIL! before using this
program to perform a second upgrade.
From here you need to specify the drive letter where the new WILDMAIL! is
to be installed. Once that is complete, you will notice that you are no
longer asked for your primary and hub addresses, but instead asked for the
path to where your existing installation of WILDMAIL! is located. From
here you need to simply specify that path and once you're ready, you may
begin the installation/upgrade process by pressing [F10].
Once the initial installation is complete, you will be so informed and
will be presented with a new upgrade screen. If you wish to abort the
upgrade process, you may do so by pressing the [ESC] key, otherwise you
may begin the upgrade process by pressing [F10]. Once the upgrade process
is complete, you will be returned to the previous menu.
Forward List Definitions
------------------------
Due to the new configuration of WILDMAIL!, in order for the upgrade process
to be performed properly, conferences will need to be associated with a
particular network before they may be added to the new configuration. The
only way to do this is to have whats called "Forward List Definitions" in
the older version of WILDMAIL!.
This option may be found from the Main Menu in WMCONFIG! under:
AreaRequest Manager
\ \
Forward List Definitions:
NOTE: In order to simplify this process, WMINSTAL comes with three
"pre-configured" echo list definitions. This also includes three
configured "network" definitions as well. These definitions are as
follows:
FIDONET_NA (uses/includes FIDONET.NA)
FIDONET_NO (uses/includes FIDONET.NO)
OCRNET_NA (uses/includes OCRNET.NA)
If you carry conferences for these particular networks, then you
won't have to be concerned about locating/defining these forward
list definitions. However, you should read the Post Installation
Notes for additional information. (see below)
Pressing [ENTER] on the Forward List Definitions option presents you with
a list of all the previously defined lists similar to below.
┌──────────────────────────────────────────────────────────────────────────┐
│ WMCONFIG! v1.11 WILDMAIL! v3 Configuration (Protected Mode) │
└──────────────────────────────────────────────────────────────────────────┘
╒════════════════════ AreaRequest Manager Information ════════════════════╕░
│ │░
│ ╒═════════════════════ Forward List Definitions ═════════════════════╕ X░
│ │ │ ░░
│ │ Network Name Echo List Hub Node │ ░░
│ │ ───────────────────────── ──────────── ─────────────────────── │ ░░
│ │ OCRNET OCRNET.NA <Originating Node> X ░░
│ │ FIDONET_NA FIDONET.NA <Originating Node> ▓ ░░
│ │ FIDONET_NO FIDONET.NO <Originating Node> ░ ░░
│ │ Y ░░
│ │ │ Y░
│ ╘════════════════════════════════════════════════════════════════════╛ │░
╘═════════════════════════════════════════════════════ PgUp/PgDn for More ╛░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
F1-Help Alt-V-View F8-Modify ESC-Exit Alt-D-Shell ENTER-Edit INS/DEL
After selecting the appropriate list, pressing [ENTER] brings up the
definition in edit mode similar to:
┌──────────────────────────────────────────────────────────────────────────┐
│ WMCONFIG! v1.11 WILDMAIL! v3 Configuration (Protected Mode) │
└──────────────────────────────────────────────────────────────────────────┘
╒════════════════════ AreaRequest Manager Information ════════════════════╕░
│ ╒═════════════════════ Forward List Definitions ═════════════════════╕ X░
│ │ Ne╒══════════════ Edit Forward List Definition ═══════════════╕ │ ░░
│ │ ──│ │ │ ░░
│ │ OC│ Network Name: OCRNET <- Important field! X X ░░
│ │ FI│ Echo List: H:\WM\OCRNET.NA <- Important field! ▓ ▓ ░░
│ │ FI│ Originating Node: Y ░ ░ ░░
│ │ │ Hub Node: 1:161/123.0 ░ ░ ░░
│ │ │ AreaRequest Name: ░ ░ ▓░
│ │ │ Password: ░ ░ ░░
│ │ │ From AKA: 1122:1/0.0 ░ ░ ░░
│ │ │ AreaRequest Flags: ░ ░ ░░
│ │ │ Add Nodes: ░ ░ ░░
│ │ │ ░ ░ ░░
│ │ │ Notify text: Y Y ░░
│ │ │ │ │ Y░
│ ╘════╘═══════════════════════════════════════════════════════════╛═══╛ │░
╘═════════════════════════════════════════════════════ PgUp/PgDn for More ╛░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
F1-Help F8-Modify F10-Save ESC-Exit Alt-D-Shell
* IMPORTANT * IMPORTANT * IMPORTANT *
-------------------------------------
These Forward List definitions are REQUIRED in order to perform a
successful upgrade. Again, it is absolutely IMPERATIVE that they be there
otherwise WMINSTAL! will be unable to convert all of your previous
installation. If you don't have any defined, please read the following
VERY CAREFULLY and refer to the WM v3.11 documentation as necessary when
creating them.
Now having said that, lets explain why. But first, you should make note of
the two most important fields (annotated above).
Network Name: OCRNET
Echo List: H:\WM\OCRNET.NA
Network Name:
This MUST be filled in with a name containing NO SPACES and must be
shorter than 20 characters long. This name will be used as the network
definition in your new installation. Typical names might be:
FIDONET_NA WILDNET_NA OCRNET
FIDONET_NO WILDNET_NO
When defining these names, you should try to use names that are
representative of the echolist your defining. In the above examples,
you'll notice a _NA and _NO protion of the names. This is used to indicate
the different echo lists that are associated with FidoNet, WildNet etc.
NOTE: If you only carry one network (i.e. only a member of FidoNet etc),
then you will only have 1 Forward List definition, 2 networks - 2
definitions and so on. In other words, one definition for each
networks conferences you carry.
For example, a network name of FIDONET_NA would be used with the echo list
file called FIDONET.NA and FIDONET_NO used with the echolist called
FIDONET.NO and so on.
Echo List:
This field should be the "echolist" ASCII text file (and complete DOS
path) which contains a list of all the conferences in this particular
network. This file is in a format similar to:
!CHINESE General topic chatting in Chinese
12_STEPS 12 Steps Discussion
4DOS 4DOS ECHO
60S_70S_PROGROCK 60's/70's Progressive Rock Music Echo
80XXX Assembly language programming
ABLED disABLED Users Information Exchange.
The above is a sample from the familiar FIDONET.NA file and is formatted
in 2 basic "columns". The first being the area name (i.e. - !CHINESE,
12_STEPS etc) and the second column being the description. If you don't
have this file, you should contact your hub for the networks that you
participate in.
Hint: WMINSTAL! comes with 3 lists already, FIDONET_NA, FIDONET_NO and
OCRNET. Any other smaller networks, you'll definately need those
echolist files!
As mentioned above, the "Network Name:" field contains the network name
WMINSTAL! will use when it reads the contents of the "Echo List:" defined
file and adds all the individual area names to the Master List database in
WMCONFIG!.
This database is a culmination of ALL the echo conferences for ALL of the
networks you have defined on your system and will be used when adding new
conferences to WMCONFIG!'s configuration. You may not be carrying all the
conferences, but they will be added to the Master List database anyway,
remember, this is only a Master List, not your actual configuration.
But the key here is that you are associating a network name with a given
conference (area name). Then any future "adding of conferences" in
WMCONFIG! will draw this area name from the Master List database and adds
it to your configuration and thereby "knows" that this conference (area
name) comes from that network. While this might seem a little confusing,
bear with us for a little bit longer as it will come a lot clearer once
you see the final results.
Okay, now that we've come this far, here's how the actual conversion takes
place:
1) Create network definitions by reading all the Forward List
definitions network names and add them to the WMNETS.DAT database
file. (Networks database).
2) Create the Echolist database file using all the echolist file names
found in the Forward List definitions. This is a database that
associates a echolist text file with a given network name.
3) On a network by network basis, read the contents the networks
associated echo list file (FIDONET.NA, WILDNET.NA etc) and import
all the area names along with their descriptions into the Master
List database file.
4) Read the old conferences database in WILDMAIL! v3 and if the area
name exists in the "new" Master List database, add that area name
to the new WMCONFIG! conferences database using the network name
from the Master List database as the conferences new network. If
it's NOT found in the Master List database, then skip it.
^^^^^^^^^
* IMPORTANT * IMPORTANT * IMPORTANT *
-------------------------------------
This is the single most important reason for WMINSTAL! NOT adding
conferences to your new configuration. And the reason is that the
old area name was NOT found in the Master List database which got
its area names from the Forward List definitions (see step #3).
This is why the Forward List definitions in the old WMCONFIG! are so
crutial to a accurate conversion/upgrade.
5) Read the old nodes database and add all the nodes to the new
WMCONFIG!'s nodes database.
6) Link all the nodes to their respective conferences and add
"memberships" to the networks that the node is picking up
conferences from. In other words, if the node picks up area:
!CHINESE, then that node will be a member of FIDONET_NA etc.
A node may be a member in multiple networks, so depending on how
you have your systems configured, a node my be a member of more than
one network.
Okay, there you have it. <g> Now that you're probably totally lost, I
think you're going to find that for the most part everything will go rather
easily and shouldn't be too painful.
But just bear in mind, if the forward lists are not defined, nothing will
be added to the master List database and consquently, nothing gets
converted over.
A Complex Upgrade
-----------------
The information here is being presented in this high degree of detail
because of the complexity of the conversion process. What we're trying to
accomplish here is to organize a completely disorganized collection of
area names for various different networks you may be carrying. This is
certainly no small task by any stretch of the imagination and is equally
difficult to program for.
However, the hardest part for you is just to make sure the Forward Lists
are properly defined and WMINSTAL! will do the rest. We've provided a log
file that keeps track of everything that WMINSTAL! did, so this should
hopefully help make sense out of everything. If all else fails, you can
always call for technical support.
Install/Upgrade Logging
-----------------------
WMINSTAL! keeps track of all the processes it goes through and maintains a
ASCII text log file for your reference. You may view the contents of this
file by selecting the main menu option "Result from Install/Upgrade". From
here you may use the normal PgUp/PgDn keys to view the file. Pressing the
[ESC] key returns you to the main menu.
Post Installation Steps
-----------------------
As with any automated upgrade process, you should always go back and
verify that the information was converted correctly and make the necessary
changes as needed.
Due to the structure differences between the old and new versions, there
has been a "casualty" that can't be reliably converted over. Specifically,
you will have to go back and re-define all your "flags" for both
conferences and nodes (used for AreaRequest). By using the Global Modify
options, you can easily add these back in, but you should know that you'll
need to before being able to rely on them again.
You should also go back and adjust the addresses on ALL of your network
definitions and verify they are correct. The default ones of FIDONET_NA,
FIDONET_NO and OCRNET will be set to a best guess value. In order to have
AreaRequest operate properly, you'll need to check these!
Version Differences
-------------------
Since the new database structures have changed with the new v4 of
WILDCAT!, WILDMAIL! now comes in two distinctive flavors.
v3.50 This version incorporates all the new features of WILDMAIL!
v4.00 but has been modified to work with the earlier releases
of WILDCAT! (circa v3.5-v3.91). This will not work with the
WC4 series.
v4.00. This version incorporates all the new changes and fully supports
WILDCAT! v4.00. This version not work with WC3 series.
Since both programs are nearly identical (the only difference being the
database structures), you can very easily switch versions of WILDMAIL!
(between v3.50 and v4.00) by simply using the appropriate WM.EXE/OVR,
WMCONFIG.EXE/OVR and WMUTIL.EXE file.
If you do switch versions of WILDMAIL! (between v3.5 and v4.0) besides
replacing the files, you will need to go back into WMCONFIG! and change
the path to the WILDCAT! home directory as necessary. Other than that,
those are the only changes necessary.
30 Day Evaluation Keys
----------------------
If you are installing WILDMAIL! for the first time for evaluation (You
haven't registered the program yet), before you can execute the actual
WM.EXE file, you will need to download a 30 day evaluation key file from
the support BBS. The phone number is:
(707) 552-0602 - 28.8Kbps
You should log on and select the Main menu option #3, 30 Day Eval Keys and
follow the instructions as they're presented. Once you've downloaded the
file, you should uncompress it and copy the WM.ID file into the new \WM40
directory.
If you have already downloaded a evaluation key for an earlier release of
WILDMAIL!, the entire evaluation keys database has been reset so you may
come back and get another one.
Upgrading/Registering WILDMAIL!
-------------------------------
Since we are coming out with two releases at the same time to work with
both the new and older versions of WILDCAT!, we have used a numbering
scheme that some may find confusing. Since you will only be able to order
the upgrade to WILDMAIL! v4.00, you will not be able to purchase v3.50 as
a separate version.
Instead, upon ordering WILDMAIL! v4.00 (either the upgrade or new), you
will automatically receive both v3.50 and v4.00 to work with the
appropriate version of WILDCAT! you are running. So by ordering v4.00,
you will actually receive 2 separate copies of WILDMAIL!.
You may register/upgrade WILDMAIL! by using our toll free order line by
dialing:
1-800-39-EMAIL (1-800-393-6245)
You may also fill out the REGISTER.DOC file which is located in your \WM40
directory and mail it off to the address listed.