home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
mhs183.exe
/
MHS183.TXT
< prev
next >
Wrap
Text File
|
1994-02-14
|
23KB
|
649 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: MHS 1.5P, Revision D, Upgrade Patch
DOCUMENT ID: TID200031
DOCUMENT REVISION: B
DATE: 14FEB94
ALERT STATUS: Yellow
INFORMATION TYPE: Symptom Solution
README FOR: MHS183.EXE
NOVELL PRODUCT and VERSION:
NetWare MHS 1.5
ABSTRACT:
This file contains the upgrade to Revision D for the Personal Edition of MHS
1.5. Make sure that you read the entire README.TXT before applying this
patch.
──────────────────────────────────────────────────────────────────────────────
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
──────────────────────────────────────────────────────────────────────────────
ADDITIONAL CONFIGURATION
Third-Party Product and Version:
This revision of NetWare MHS 1.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.
Other:
If you need information about the Novell mail hub (NHUB) or about
registering your workgroup, call the Messaging Hotline at the following
number:
(408) 473-8989
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.
ADDITIONAL CONFIGURATION
Other:
User Interface Information
--------------------------
The following information applies to the user interface in NetWare MHS
1.5:
SYMPTOM
Monochrome Monitor Problems. The MHS screens may be difficult or
impossible to read on certain VGA monochrome monitors.
SOLUTION
If you experience this problem, use the following MODE command at the DOS
prompt before running MHS:
MODE=bw80
SYMPTOM
Color Monitor Problems.
SOLUTION
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
SYMPTOM
Null Username
CAUSE
The Directory Manager treats "" (null; a username with no characters) as
a valid username.
SOLUTION
Check to make sure you have specified a username before you add a new
user.
ADDITIONAL CONFIGURATION
Other:
Communications Information
--------------------------
The following information applies to communications between hosts running
NetWare MHS 1.5.
SYMPTOM
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.
SOLUTION
If you want speed sensing, use the HULTRA modem driver.
SYMPTOM
9600 Baud Modem Support. Machines with 8088 processors running at the
4.77 MHz clock speed are not fast enough to use 9600-baud modems.
SOLUTION
Apply the MHS183.EXE file.
SYMPTOM
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.
SOLUTION
Apply the MHS183.EXE file.
ADDITIONAL CONFIGURATION
Other:
Disk Space and Memory Requirements
----------------------------------
Disk space and memory requirements for NetWare MHS 1.5 have changed, as
follows:
SYMPTOM
Statistics Gathering. Because NetWare MHS 1.5 gathers statistics more
comprehensively, statistics files require more disk space. Monitor disk
space usage carefully.
SOLUTION
Apply the MHS183.EXE file.
SYMPTOM
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.
SOLUTION
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.
SYMPTOM
Disk Space Management. If MHS terminates abnormally, it might be unable
to remove temporary files created in the <mv>\MHS\SW subdirectory.
SOLUTION
Check this subdirectory from time to time, and delete all files except
SWAP.FLG. Note: Do not delete these files while MHS is running.
ADDITIONAL CONFIGURATION
Other:
Other Information
-----------------
The following information applies to NetWare MHS 1.5:
SYMPTOM
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.
SOLUTION
To avoid confusion and routing problems, delete invalid host names.
ADDITIONAL CONFIGURATION
Other:
DOCUMENTATION CORRECTIONS
-------------------------
This section provides updates and corrections to the NetWare MHS
Installation and Operation guide.
Passwords for Asynchronously-Connected Hosts
--------------------------------------------
SYMPTOM
The NetWare Installation and Operation guide incorrectly describes how to
define passwords for hosts with which you communicate asynchronously.
SOLUTION
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.
After 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, he 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.
ADDITIONAL CONFIGURATION
Other:
96V32 and 96V32HUB Modem Driver
-------------------------------
SYMPTOM
The 96V32 and 96V32HUB are not drivers for the Hayes Smartmodem, as
stated in the NetWare MHS Installation and Operation guide.
SOLUTION
The 96V32 and 96V32HUB drivers are drivers for the Hayes V-series ULTRA
modem.
ADDITIONAL CONFIGURATION
Other:
Miscellaneous MHS
SYMPTOM
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.
SOLUTION
Apply the MHS183.EXE file.
SYMPTOM
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.
SOLUTION
Apply the MHS183.EXE file.
SYMPTOM
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.
SOLUTION
Apply the MHS183.EXE file. With this file applied MHS no longer accesses
the COM port when using the "DISABLED" modem driver.
SYMPTOM
Under some circumstances, the MHS workstation would hang if activity
occurred on the COM PORT while a gateway was running.
SOLUTION
Apply the MHS183.EXE file.
SYMPTOM
Sometimes during message queue transfers, the warning message "Dangerous
stuff" would appear.
SOLUTION
The condition causing this problem has been eliminated when you apply the
MHS183.EXE.
SYMPTOM
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.
SOLUTION
Apply the MHS183.EXE file.
SYMPTOM
On faster machines, the Connectivity Manager would sometimes terminate
with a fatal runtime (division by zero) error.
SOLUTION
Apply the MHS183.EXE file.
SYMPTOM
Mhsuser - Option -X01 - When defining a new user of an application,
mhsuser would allow you to add users if you provided an undefined
application.
SOLUTION
Apply MHS183.EXE. With this file applied MHSUSER will no longer allow
you to define a user to an undefined application.
SYMPTOM
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.
SOLUTION
Apply MHS183.EXE. With this file applied MHSUSER now lets you add and
modify the information for the CompuServe host.
SOLUTION
Self-Extracting File Name: MHS183.EXE Revision: B
Files Included Size Date Time
\
MHS183.TXT (This File)
EXE.EXE 257810 08-03-93 10:25a
SYS.EXE 370145 08-03-93 10:25a
NOTE.TXT 22679 07-30-93 5:10p
UPGRADE.EXE 22935 08-03-93 10:25a
Installation Instructions:
SYSTEM REQUIREMENTS
-------------------
The NetWare MHS 1.5 Revision D (Personal edition) upgrade requires the
following hardware and software:
A DOS workstation running NetWare MHS 1.5P, revision A or revision B.
If this copy of the Personal edition will be using an asynchronous
connection on the client workstation, it also requires the following:
■ An available serial communications port (COM1, COM2, COM3, or COM4)
■ A modem from the list of modems in the section "Communication
Enhancements and Improvements."
■ 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 1.5.
Before Upgrading Your Host
--------------------------
1. 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.
2. 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.
3. Back up the existing SYS, MAIL and EXE subdirectories before
proceeding with the upgrade.
Upgrading Your Host
-------------------
To upgrade your host, use the following instructions:
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. If you have performed the backup and if the target directory is
correct, type "Y" and press <Enter>; otherwise, type "N" and press
<Enter>.
If you entered "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).
Solution Specifics:
FEATURES OF NETWARE MHS 1.5, REVISION D
---------------------------------------
NetWare MHS 1.5P, revision D, incorporates the following new and revised
features.
Communication Enhancements and Improvements
-------------------------------------------
NetWare MHS 1.5 includes the following enhancements and improvements for
communication between hosts:
Connection to CompuServe.
Through NetWare MHS 1.5, revision 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.
Session Recovery.
The Connectivity Manager resumes transmissions where it left off
when a broken transmission restarts.
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.
Retry Counter Reset.
The Retry counter now resets after a successful connection to
another host. Previously, this function was disabled.
Expanded Serial Port Support.
NetWare MHS supports modems on serial ports COM3 and COM4.
Support for 9600 Baud Modems.
NetWare MHS 1.5 supports 9600 baud modems.
Improved Modem Support.
To support new modems with software UARTs that use only one stop bit
for communication, NetWare MHS 1.5 uses only 1 stop bit. It also
supports modem definitions with large command sets.
Included with this release are versions of the MHS 1.5 modem drivers
that handle hang-ups properly with CompuServe. If you are using any
of the drivers that came with your MHS 1.5, revision A software, you
must use the equivalents included with this release.
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 1.5 includes the following enhancements and improvements to
the SMF standard:
Support for Extended Addresses.
While MHS 1.5, revision 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: 1-408-555-1212}
mail@fax {FAX: 1-408-555-1211}
Previously, MHS would compare only the base address (mail@fax).
Since the base address is the same in both instances, MHS 1.5 would
only deliver one message, containing the first address, to the fax
gateway.
MHS 1.5, revision 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 previous example, the addresses were the
following then MHS would send two copies:
mail@fax {FAX: 1-(408)-555-1212}
mail@fax {FAX: 1-408-555-1212}
This change supersedes the information in the SMF v70 Programmer's
Reference.
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.