Network Support Encyclopedia 96-1/novell-nsepro-1996-1-cd2.iso/download/netware/mhs184.exe/NOTE.TXT

Text File | 1993-07-30 | 26KB | 614 lines

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*                            NETWARE MHS 1.5                          *
*                Copyright (C) 1991-1993 by Novell, Inc.              *
*                             RELEASE NOTE                            *
*                           July 30, 1993                             *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


NetWare(R) MHS(tm) Multi-Network Edition
Software v1.5M  Revision D

The NetWare MHS Multi-Network edition software uses the Standard Message
Format (SMF) to provide DOS-based messaging services on disk sharing
networks.  NetWare MHS transfers information including addresses, text,
and other data from an MHS-compatible application or gateway to
applications and gateways at other locations.  MHS uses a
store-and-forward communications method, which transports messages
across a broad range of data-communications networks.  Other
applications provide services - such as electronic mail - that allow
users to create and process messages.

This revision of NetWare MHS v1.5 includes public hub support.  It
allows users of MHS-compatible applications to communicate with each
other through third-party hub services such as the CompuServe MHS
Service.

Please read this entire release note before upgrading your NetWare MHS
software.

If you have any questions or comments, please contact:

   Customer Support Response Center
   Novell, Inc.
   2180 Fortune Drive
   San Jose, CA 95131

If you need information about the Novell mail hub (NHUB) or about
registering your workgroup, call the Messaging Hotline at the following
number:

   [phone]

To register your workgroup, you can send an MHS mail message to
hubadmin@NHUB.  In the message, include your workgroup name, your
contact phone number, and the name of the contact person in your
organization.

If you need technical support, call one of the following numbers:

   (800) NETWARE
   [phone]

For other information, send a fax to the attention of the MHS Product
Manager at the following number:

   [phone]

For support using the CompuServe MHS Service, you can call CompuServe
directly at:

   CompuServe US Customer Service
      Within US (toll-free) - 800-848-8990
      Outside US - [phone]

   CompuServe UK Customer Service
      Within UK (toll-free) - 0800-289-378
      Outside UK - (44) 272-255111

   CompuServe Europe Customer Service
      Within Germany (toll-free) - 0130-37-32
      Within Switzerland (toll-free) - 155-31-79
      Outside Germany and Switzerland - (49) (89) 66550-111

Or, you can send mail to:

   SUPPORT@CSERVE

from an MHS site connected to CompuServe, or

   >MHS:SUPPORT@CSERVE

from other CompuServe Mail products.

For information on how to send mail from MHS to CompuServe mail, please
read the <mv>\MHS\SYS\MANUAL.DOC file.


COMPONENTS
----------

NetWare MHS v1.5 Rev. D (Multi-Network edition) consists of
these components:

o       README.TXT (this release note)

o       UPGRADE.EXE

o       EXE.EXE

o       SYS.EXE


SYSTEM REQUIREMENTS
-------------------

The NetWare MHS v1.5 Rev. D (Multi-Network edition) upgrade requires
the following hardware and software:

o       A DOS disk sharing network running NetWare MHS v1.5M, Rev A.

If this copy of the Multi-Network edition will be using an asynchronous
connection on the client workstation, it also requires the following:

o       An available serial communications port (COM1,
        COM2, COM3 or COM4)

o       A modem from the list of modems in the section "Communication
        Enhancements and Improvements."

o       CompuServe User-ID and Password for each host that
        will be connecting to CompuServe


UPGRADING YOUR HOST
-------------------

The following sections describe the steps you must perform before
and after upgrading your host from an earlier revision of NetWare MHS
v1.5.

Before Upgrading Your Host
--------------------------

1.      Upgrade Routing Internet Hosts First. Before you  upgrade a
        nonrouting internet host, upgrade its primary  host.

2.      Stop Mail Processes. Stop all mail processes (Connectivity
        Manager, secondary Transport Servers and applications).  If you
        have mail pending for other hosts, force that mail to be
        delivered before upgrading your host.

3.      Rebuild Queues. Rebuild all existing queue files to ensure they
        are in the correct format.  Use the Rebuild all queues option
        from the MHS Utilities menu.

4.      Back up the existing SYS, MAIL and EXE subdirectories before
        proceeding with the upgrade.


Upgrading Your Host
-------------------

Follow the instructions below to upgrade your host.

1.      Set the MV environment parameter to point to the path containing
        the MHS subdirectory.  For example, if NetWare MHS is installed
        in d:\EMAIL, enter the command "SET MV=d:\EMAIL".

2.      Run UPGRADE. The UPGRADE program warns you to back up the SYS
        and EXE subdirectories, and displays the path constructed from
        the MV environment parameter.  It prompts, Is it OK to continue
        (Y/N):

3.      Type "Y" if you have performed the backup, and if the target
        directory is correct. Otherwise, type "N".

        If you enter "Y" in response to the previous prompt, the program
        upgrades your NetWare MHS installation.

4.      If you plan to connect to the CompuServe Mail hub, print
        MANUAL.DOC, located in the <mv>\MHS\SYS directory, and follow
        the instructions in that document.  It will tell you how to
        configure the CompuServe Mail Hub and register your workgroups
        and hosts with CompuServe.

5.      Run the Directory Manager at least once after upgrading your
        host. The  Directory Manager automatically updates the MHS
        version number and serial number in the Routing Directory
        (NETDIR.TAB).


DOCUMENTATION CORRECTIONS
-------------------------

This section provides updates and corrections to the NetWare MHS
Installation and Operation guide.


Passwords for Asynchronously-Connected Hosts
--------------------------------------------

The NetWare Installation and Operation guide incorrectly describes how
to define passwords for hosts with which you communicate asynchronously.

You can define a Password for access to hubs in the MHS HOST SETUP form.
This is the password that the local host transmits when it communicates
with a remote host.  (It transmits the same password to all the remote
hosts with which it communicates.)

For each remote host the local host calls, and for each remote host that
calls the local host, you can define a Password (in the A HOST THAT THIS
HOST PHONES and the A HOST THAT PHONES THIS HOST forms, respectively).
This Password must match the password defined in the Password for access
to hubs field in the remote host's HOST SETUP form.

If you do not define the remote host's password at your local host, MHS
will take the password transmitted by the remote host in the next
communication session, and write it in the Password field of the A HOST
THAT THIS HOST PHONES or the A HOST THAT PHONES THIS HOST form.

Once a password has been assigned to a remote host, the remote host
administrator must notify you of changes to the password.  When the
remote administrator changes the password in the Password for access to
hubs field, the local administrator must change the Password field in
the A HOST THAT THIS HOST PHONES or the A HOST THAT PHONES THIS HOST
form for the remote host.  Otherwise, if Require Password is set to
"Yes," a password mismatch will occur, and the hosts will be unable to
establish a communication session.

Similarly, when you change the password in the Password for access to
hubs field, you must ask the administrator of the remote host to update
the Password in the form for your host.

To understand how passwords work, consider "Eng," a host that calls
another host named "Sales." Sales has chosen "salpas" as its Password
for access to hubs, and Eng has chosen "engpas" as its Password for
access to hubs.  These passwords are defined in the HOST SETUP form.

The administrators at Sales and Eng can get together and coordinate
passwords.  Sales' administrator enters "engpas" in the Password field
of the A HOST THAT THIS HOST PHONES form that defines the route to Eng.
And Eng's administrator enters "salpas" in the Password field of the A
HOST THAT PHONES THIS HOST form that defines the route to Sales.  Both
administrators can also set Require Password to "Yes."

One or both administrators can choose not to define the password for the
other host.  If they leave the Password for the remote host blank, MHS
will insert the password it receives during the next communication
session.  During this session, Eng's host transmits its password.
Sales' host enters the password received from Eng in its routing table,
and sends its password to Eng's host.  Eng's MHS enters the Sales
password in its routing table, and continues the transmission.

From now on, if either administrator changes their host's Password for
access to hubs, they must ask the other administrator to change the
Password field in the A HOST THAT THIS HOST PHONES or A HOST THAT PHONES
THIS HOST form for the remote host.


96V32 and 96V32HUB Modem Driver
-------------------------------

The 96V32 and 96V32HUB are not drivers for the Hayes Smartmodem, as
stated in the NetWare MHS Installation and Operation guide.  They are
drivers for the Hayes V-series ULTRA modem.


FEATURES OF NETWARE MHS v1.5 REV. D
-----------------------------------

NetWare MHS v1.5M Rev. D incorporates the following new and revised
features.


Communication Enhancements and Improvements
-------------------------------------------

NetWare MHS v1.5 includes the following enhancements and improvements
for communication between hosts:

o       Connection to CompuServe. Through NetWare MHS v1.5 Rev. D, you
        can use the CompuServe Mail Hub to route mail between NetWare
        MHS workgroups, members of the CompuServe Information Service,
        and other users of CompuServe Mail.

o       Session Recovery. The Connectivity Manager resumes
        transmissions where it left off when a broken transmission
        restarts.

o       Abort and Retry Captured. When a network error occurs, the I/O
        operation is retried.  If the retry count has been exhausted,
        the Connectivity Manager or gateway is restarted.  The
        Abort/Retry counter is reset after a successful connection.

o       Retry Counter Reset. The Retry counter now resets after a
        successful connection to another host.  Previously, this
        function was disabled.

o       Expanded Serial Port Support.  NetWare MHS supports modems on
        serial ports COM3 and COM4.

o       Multiline Hub Support. This edition supports up to sixteen
        lines.  You do not need to purchase a separate multiline
        package.  (However, you must have a dedicated workstation for
        each line.)

o       Support for 9600 Baud Modems. NetWare MHS v1.5 supports 9600
        baud modems.

o       Improved Modem Support. To support new modems with software
        UARTs that use only one stop bit for communication, NetWare MHS
        v1.5 uses only 1 stop bit.  It also supports modem definitions
        with large command sets.  Included with this release are
        versions of the MHS v1.5 modem drivers that handle hang-ups
        properly with CompuServe.  If you are using any of the drivers
        that came with your MHS v1.5 Rev. A software, you must use the
        equivalents included with this release.

o       Support for Additional Modem Drivers. NetWare MHS now supports
        the following modem drivers:

    2400B        For Hayes Smartmodem 2400 and Hayes-compatible modems
                 operating at 2400 baud.  Use for calling hosts only.
    2400B-CE     For modems bundled with the COMPAQ LTE.  Try using
                 the CMPQLTEB modem driver first.
    2400B-HUB    For Hayes Smartmodem 2400 and Hayes-compatible modems
                 operating at 2400 baud.
    96V32        For Hayes V-Series ULTRA 9600 modems.  Use for calling
                 hosts only.
    96V32HUB     For Hayes V-Series ULTRA 9600 modems.
    BULLET96     For E-Tech BulletModem E9696M modems without MNP.
    BULLETEC     For E-Tech BulletModem E9696M modems with MNP.
    CODX3220     For Codex 3220 modems.
    CODX3260     For Codex 3260 modems.
    COMPQLTEB    For modems bundled with the COMPAQ LTE.  Try this modem
                 driver first; if port off-line or other messages
                 appear, try using 2400B-CE.
    DISABLED     To disable asynchronous activity.  For hosts that do
                 not exchange messages with remote hosts through
                 telephone calls.
    FAXMDM       For generic SendFax-compatible modems.
    HAYESMAN     For Hayes-compatible modems that require telephone
                 numbers to be dialed manually.
    HAYES-UN     For Hayes-compatible modems operating at speeds up to
                 2400 baud.
    HAYESX24     For generic Hayes-compatible 2400 baud modems.
    HAYESSM      For Hayes Smartmodem 2400 modems.
    HSTD-HUB     For US Robotics COURIER HST modems with MNP.
    HSTDNMNP     For US Robotics COURIER HST modems without MNP.
    HULTRA       For Hayes V_Series ULTRA Smartmodem 9600 modems.
                 Replaces the 96V32 and 96V32HUB drivers.
    INTELFAX     For the Intel SatisFAXtion board.
    INTELV32     For Intel 9600EX modems.
    MICROCOM     For Microcom QX4232HS modems.
    MULTEC       For MultiTech 932/224 modems.  This driver does not
                 alter Novram setup.
    MULTECNR     For MultiTech 932/224 modems.  This driver alters
                 Novram setup.
    MULTEC20     For older MultiTech 224 modems.  This driver does not
                 alter Novram setup.
    NEC9631      For NEC 9631 modems.
    NEC9632      For NEC 9632 modems.
    NULLMDM      For hosts with a direct cable connection between their
                 communication ports.  You can use NULLMDM as a platform
                 for developing modem-control files.
    PP96-HUB     For Practical Peripherals PM9600SA modems. Use for
                 both hubs and calling hosts.
    UDS322X      For Motorola UDS v. 3224/3225 and Codex 1133 modems.

        This list supersedes the one in Appendix C of the NetWare MHS
        Installation and Operation guide.

        Note:  If you want to use one of these modem drivers, refer to
        the MODEM.DOC file in the <mv>\MHS\SYS directory for
        installation instructions.


SMF Enhancements and Improvements
---------------------------------

NetWare MHS v1.5 includes the following enhancements and improvements to
the SMF standard:

o       Support for Extended Addresses. While MHS v1.5 Rev. D does not
        use extended addresses to route messages, it now examines
        extended address elements in braces ({ }) when checking for
        duplicate addresses.

        For example, a message contains the following addresses:

        mail@fax {FAX: [phone]}
        mail@fax {FAX: [phone]}

        Previously, MHS would compare only the base address (mail@fax).
        Since the base address is the same in both instances, MHS v1.5
        would only deliver one message, containing the first address, to
        the fax gateway.  MHS v1.5 Rev. D recognizes the two addresses
        as distinct, and delivers two copies to the fax gateway.  Note
        that MHS does not interpret the contents of the braces; it only
        detects that they are different.  Thus, if in the above example,
        the addresses were:

        mail@fax {FAX: [phone]}
        mail@fax {FAX: [phone]}

        then MHS would send two copies.

        This change supersedes the information in the SMF v70
        Programmer's Reference.


GENERAL INFORMATION
-------------------

The following information applies to networks running NetWare MHS v1.5.


User Interface Information
--------------------------

The following information applies to the user interface in NetWare MHS
v1.5:

o       Monochrome Monitor Problems. The MHS screens may be difficult
        or impossible to read on certain VGA monochrome monitors.  If
        you experience this problem, use the following MODE command at
        the DOS prompt before running MHS:

        MODE=bw80

o       Color Monitor Problems. If the colors on an application display
        incorrectly after you run MHS, use the following MODE command at
        the DOS prompt before running your application:

        MODE=co80

o       Null Username. The Directory Manager treats "" (null; a
        username with no characters) as a valid username.  Therefore,
        check to make sure you have specified a username before you add
        a new user.

o       Host and Queue Review in a Multiline Installation. If you have
        a multiline installation and you select Review a host's route
        and queues from the MHS Utilities menu while that host is
        connected to another transport server, you will receive the
        message:

        missing 'd:\MHS\MAIL\QUEUES\hostname.?' discard queue?

        If you answer "Yes," MHS will discard the queue for that host.
        To avoid this situation, always check incoming lines to see if
        hosts are connected before you select this option.

o       Connection Activities Window. You cannot view the Connection
        Activities window twice in a row.

o       Default Primary Host. In new installations, the default primary
        host for non-routing internet hosts is NHUB.  If you accept the
        default value, mail will not be delivered to or routed from the
        non-routing host.


Communications Information
--------------------------

The following information applies to communications between hosts
running NetWare MHS v1.5.

o       Internet Retries. When a NetWare MHS host fails to connect to
        another internet host, it will retry 15 times.  The Connectivity
        Manager appears inactive for a few minutes during the retry
        attempts.

o       Insufficient Disk Space. If a remote internet file server has
        insufficient disk space during a connection, MHS might not
        transfer mail.  MHS transfers the waiting mail during the first
        internet connection after sufficient disk space is made
        available.  If any of the mail includes attachments, the
        administrative user and the sender(s) on the originating
        internet host might receive an erroneous message that an
        attachment is missing.

o       Deactivated Hosts. When mail is waiting to be delivered to a
        deactivated passive internet host, forcing a connection
        transfers the mail but does not reactivate the internet host.
        To reactivate the host, force a connection a second time, when
        there is no mail waiting.

o       Modem Speed Sensing. The superseded modem drivers for the Hayes
        V-Series ULTRA 9600 modem (96V32 and 96V32HUB) do not sense
        speed.  As a result, they are unable to answer an incoming call
        at 1200 or 2400 baud.  If you want speed sensing, use the HULTRA
        modem driver.

o       9600 Baud Modem Support. PCs with 8088 processors running at
        the 4.77 MHz clock speed are not fast enough to use 9600-baud
        modems.

o       Inaccurate Estimated Transfer Time. MHS attempts to estimate
        the amount of time an asynchronous transfer will take.  It often
        estimates incorrectly, especially for high-speed modems.


Disk Space and Memory Requirements
----------------------------------

Disk space and memory requirements for NetWare MHS v1.5 have changed, as
follows:

o       Statistics Gathering. Because NetWare MHS v1.5 gathers
        statistics more comprehensively, statistics files require more
        disk space.  Monitor disk space usage carefully.

o       Memory Allocation Error. If the NetWare MHS workstation has a
        limited amount of available memory, and a large number of files
        accumulate in the SND directory, a memory allocation error
        occurs.  Delete any *.BAD files in the SND directory and, if
        possible, terminate memory-resident programs sharing the MHS
        workstation.  Do not run MHS from a shell.

o       Disk Space Management. If MHS terminates abnormally, it might
        be unable to remove temporary files created in the <mv>\MHS\SW
        subdirectory.  Check this subdirectory from time to time, and
        delete all files except SWAP.FLG.  Note:  Do not delete these
        files while MHS is running.


Other Information
-----------------

The following information applies to NetWare MHS v1.5:

o       Invalid Remote Host Name. MHSUSER does not prevent you from
        adding an invalid remote host name (for example, a name
        containing invalid characters) to the Routing Directory.  To
        avoid confusion and routing problems, delete invalid host names.


FIXES IN THIS REVISION
----------------------

1)      When MHS messages are upgraded from SMF-64 to SMF-70, MHS might
        reject the message indicating "Bad Expiry Date Header".  This
        problem occurred every 256 days; the last known date on which it
        occurred was January 7, 1992.

2)      MHS would fail when it connected to the Compuserve Mail Hub from
        outside the United States, if the connection was made through a
        data network that uses 7-bit data.

3)      Although it was using the "DISABLED" modem driver, MHS would
        still require the selected COM port to be present, and would
        alter the settings of that COM port.  MHS no longer accesses the
        COM port when using the "DISABLED" modem driver.

4)      Under some circumstances, the MHS workstation would hang if
        activity occurred on the COM PORT while a gateway was running.

5)      Sometimes during message queue transfers, the warning message
        "Dangerous stuff" would appear.  The condition causing this
        problem has been eliminated.

6)      Disk write errors that occur during INET message deliveries
        are no longer considered fatal errors.  MHS will now count that
        as 1 failed connection attempt and continue processing.

7)      Some common INET delivery errors used to cause immediate
        deactivation of the INET host.  All errors now accumulate as
        single failed connections and the host is deactivated when the
        system retry limit is reached.

8)      Hosts are no longer deactivated when a login to a remote host's
        server fails.  All errors now accumulate as a single failed
        connection and the host is deactivated when the system retry
        limit is reached.

9)      On faster machines, the Connectivity Manager would sometimes
        terminate with a fatal runtime (division by zero) error.

10)     Mhsuser - Option -X01 - When defining a new user of an
        application, mhsuser would allow you to add users if you
        provided an undefined application.  MHSUSER will no longer
        allow you to define a user to an undefined application.

11)     Mhsuser - Option -X31 - The switch -NS for adding / modifying
        information for the CompuServe host's configuration would only
        work for the initial creation of the Cserve host.  MHSUSER
        now lets you add and modify the information for the CompuServe
        host.

12)     When the Connectivity Manager attempts to process a locked
        file in the SND directory, it will abort and drop back to
        the Main Menu.  The Connectivity Manager will no longer abort.

13)     Under certain condition, the Connectivity Manager incorrectly
        deletes a newly submitted message during its 0-length file
        clean-up processing.  Connectivity Manager now checks to
        ensure it has proper access to the 0-byte file prior to
        deleting it.


TRADEMARKS
----------

Novell, the N design, and NetWare are registered trademarks and NetWare
MHS is a trademark of Novell, Inc.

Codex is a registered trademark of Codex Corporation.  COMPAQ is a
registered trademark of COMPAQ Computer Corporation.  CompuServe is a
registered trademark of CompuServe, Inc.  E9696M and BulletModem are
trademarks of E-Tech Research, Inc.  Hayes and V-series are registered
trademarks and ULTRA and Smartmodem are trademarks of Hayes
Microcomputer Products, Inc.  Intel is a registered trademark and
SatisFAXtion is a trademark of Intel Corporation.  IBM and PS/2 are
registered trademarks of International Business Machines Corporation.
Microcom and MNP are trademarks of Microcom, Inc.  MS-DOS is a
registered trademark of Microsoft Corporation.  Motorola is a registered
trademark of Motorola, Inc.  NEC is a registered trademark of NEC
Corporation.  Practical Peripherals is a registered trademark and
PM9600SA is a trademark of Practical Peripherals, Inc.  USRobotics is a
registered trademark and COURIER, HST, and ASL are trademarks of U.S.
Robotics, Inc.