

			 NETWARE REMOTE MHS 2.0
		   Copyright (C) 1993 by Novell Inc.
			     October 1, 1993



This readme file of NetWare Remote MHS includes documentation
corrections, general restrictions and known problems you need to be
aware of.


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

The manual does not document the following:

    o	 On pages 2-8 and 3-8 of the Getting Started with NetWare Remote
	 MHS manual, speed refers to the speed Remote MHS uses when
	 communicating with the attached modem. Based on that
	 speed, the highest possible dial speed is selected.

    o	 To upgrade from an older version of Remote MHS, use the INSTALL
	 batch file.

    o	 The MESSAGES.TXT file, can be found in MHSDIST\SYS directory
	 on the installation diskette and is accessible after the
	 Remote MHS software is installed in the MHS\SYS directory. It
	 contains system generated messages and provides an explanation
	 and recommended action.

    o	 The RMHS -E[1][2] parameter added. This parameter allows
	 part-time remote users to synchronize the MHS directory extract
	 files. To synchronize all of the extract files, use -E. To
	 synchronize the SMF-NS.XRT file only, use -E1. To synchronize
	 the EXTRACT.DAT and EXTRACT.SI files, use -E2. NOTE: This
	 parameter is dependent on the value of the "Net MHS Tree" field
	 on the RSETUP Configuration Setup screen. If your network mail
	 path is changed by your administrator, you must run RSETUP to
	 modify the "Net MHS Tree" field to reflect this change.

    o	 The RMHS -M parameter added. This parameter overrides the DOS
	 MV environment variable. This option must be used when running
	 RMHS.EXE from a directory other than MHS\EXE. For example,
	 C:\UTILS\RMHS.EXE.

    o	 The RMHS -W parameter added. This parameter overrides the
	 password set by RSETUP. If the parameter appears with no
	 value (-W""), the user will be prompted for a password. This
	 parameter applies to both part-time and full-time remote users.

    o	 Page 5-2 of the Getting Started with NetWare Remote MHS manual
	 should include a statement stating that the RMHS -Y parameter
	 synchronizes the user directories up to the network. The
	 RMHS -Y option no longer synchronizes the extract files.
	 NOTE: This parameter is dependent on the contents of the "Net
	 MHS Tree" field on the RSETUP Configuration Setup screen. If your
	 network mail path is changed by your administrator, you must run
	 RSETUP to modify the "Net MHS Tree" field to reflect this change.

    o	 RMHS ignores the MV environment variable when RMHS is run with
	 the -Y option.

    o	 RSETUP ignores the MV environment variable if it is pointing to
	 an MHS directory on a network drive.

    o	 On page 2-9 of the Getting Started with NetWare Remote MHS manual,
	 it states that the password field must match your NetWare bindery
	 password. This is no longer required. It should state this password
	 is used to allow remote access to the user's mailbox on the network.
	 Prior to Remote MHS installation, Novell recommends that the part-time
	 user be logged into the Global MHS server to allow RSETUP to
	 synchronize this password with the password stored in the user's
	 FORWARD.SMF file on the network.
	 NOTE: If the part-time remote user installed Remote MHS without
	 being attached to the Global MHS server, RSETUP will only update
	 the local password. The user must attach/login to the Global MHS
	 server and rerun RSETUP to modify or update the password.

    o	 RSETUP now prompts the user for the old password when you
	 change a password. This applies to part-time remote users
	 only. If the password is invalid, message #9321 "Terminating:
	 The supplied password does not match the existing password"
	 is generated and appears in the log file.

    o	 Remote MHS now provides a new administration utility called
	 RMHS-PWD.  You must provide your Global MHS administrator with
	 the following files:  RMHS-PWD.EXE and RMHS-PWD.HLP.  These
	 files are located at the root of your Remote MHS installation
	 diskette.  This program allows Global MHS administrators to
	 change the Remote MHS password on the Global MHS server for
	 part-time remote users.  This utility is useful when the
	 part-time user requires a password change and is unable to
	 connect directly to the network.  When the RMHS-PWD program is
	 invoked at the DOS prompt, the "NetWare Remote MHS Password
	 Setting Parameters" form appears.  This form requires the
	 following information:

	 NET MHS TREE,	   which indicates the location for the Global
			   MHS directory.
	 SERIAL NUMBER,    which is your 6-digit alpha Remote MHS serial
			   number that appears on the first line when
			   you invoke RMHS. For example: (SN: ABCDEF)
	 SHORT USER NAME,  which is your short user name as given to
			   you by your server administrator.
	 PASSWORD,	   which is the password you defined using
			   RSETUP.

	 Once the changes have been saved, the user's FORWARD.SMF on the
	 Global MHS server is modified, if one currently exists, or created.

    o	 When the password in NAMES.INF has been tampered with or
	 corrupted, message #9077 "Password verification failed..." is
	 generated.  Users are instructed to run RSETUP -I to reset the
	 password.  Other possible solutions include re-installing and
	 restoring NAMES.INF from a backup.

    o	 Remote MHS uses the file FORWARD.SMF when transferring messages.
	 If you change the name of the FORWARD.SMF file, you will lose
	 the configuration information stored there. This applies to
	 part-time remote users only.

    o	 RMHS will prompt users to continue if another RMHS or RSETUP
	 program is active. Users should only continue if they are
	 certain that these applications are not running.

    o	 RMHS will report message #9058 "Possible license violation..."
	 if two remote users are operating with the same serial number.

    o	 New RMHS message, #9073 tells the user what mail tree is being
	 used.

    o	 RMHS -V9 can be used to follow RMHS-to-modem interaction. These
	 messages are sent to RMHS.LOG as message #0.

    o	 When messages/extract files are being synchronized, the status
	 line now contains a percentage process indicator.

    o	 When synchronizing user application mail boxes, each application
	 synchronized, will generate message #9204 "synching application
	 appname..." This applies to part-time remote users only.

    o	 When an application does not have an identical counterpart on
	 the network, message #9205 is generated "... error synching
	 appname. Target directory does not exist." User should
	 reconfigure so that the network applications are a superset
	 of local applications. This applies to part-time remote users.

    o	 When Remote MHS restarts a transmission of a partial transfer,
	 you might notice that the retransmission starts at less than
	 the amount of the message previously transmitted. For example,
	 if a message transfer is aborted at the 50% mark during a
	 38400 bps connection, it is quite possible for the partial
	 delivery to resume at 40%. This is a direct result of data
	 being stored to disk less often when communicating at higher
	 baud rates.


-----------------------------------------------------------------------
			    MODEM SUPPORT
-----------------------------------------------------------------------

Remote MHS supports the following modems:
(The corresponding modem definition file is enclosed in parenthesis.)

    o	 Codex Motorola 3260 (codx3260.mdf)
    o	 Codex Motorola 3220 (codx3220.mdf)
    o	 Everex Evercom 24 (ever24.mdf)
    o	 Everex Evercom 24E (ever24ep.mdf)
    o	 Generic Fax Modem (faxmdm.mdf)
    o	 Global Village Communications 9600 (gvc96.mdf)
    o	 Hayes compatible modems (hayes.mdf)
    o	 Hayes Smartmodem 1200 (hayes12.mdf)
    o	 Hayes Smartmodem 2400 (hayes24.mdf)
    o	 Hayes Smartmodem Optima 24 (optima24.mdf)
    o	 Hayes Smartmodem Optima 96 (optima96.mdf)
    o	 Hayes V-Series Smartmodem (hayes96v.mdf)
    o	 Hayes V-series Smartmodem 2400 (hayes24v.mdf)
    o	 Hayes V-series ULTRA Smartmodem 9600 (ultra96.mdf)
    o	 Intel 2400EX (intel24.mdf)
    o	 Intel 9600EX (intel96e.mdf)
    o	 Intel SatisFAXtion (intelfax.mdf)
    o	 Megahertz 2400 Pocket Fax/Modem (mhz24.mdf)
    o	 Megahertz 2400 Pocket Fax/Modem (mhz24e.mdf)
    o	 Microcom QX/4232hs and QX/4232bis (mcom4232.mdf)
    o	 Microcom AX/2400c (mcom24c.mdf)
    o	 Multi-Tech MultiModem 932ba (mtech96.mdf)
    o	 Multi-Tech MultiModem 224ba (mtech24.mdf)
    o	 NEC N9631 (nec9631.mdf)
    o	 Null modem (nullmdm.mdf)
    o	 Practical Peripherals 9600SA (prac96sa.mdf)
    o	 Practical Peripherals 2400SA (prac24sa.mdf)
    o	 Supra FaxModem V.32bis (supra.mdf)
    o	 Telebit T1600 (t1600.mdf)
    o	 Telebit T1000 (t1000.mdf)
    o	 US Robotics Courier 2400 (usr24.mdf)
    o	 US Robotics Courier 2400e (usr24e.mdf)
    o	 US Robotics Courier HST, Dual, and V.32bis (usrhst.mdf)
    o	 UDS 3225 (uds322x.mdf)
    o	 Zoom v.32 (zoom96.mdf)
    o	 Zoom v.32 Turbo (zoom96t.mdf)

Use the modem definition file, nullmdm.mdf, to configure non-modem
connections using a "null modem" serial cable. The file nullmdm.mdf
contains a wiring diagram for an RMHS-compatible null modem cable.

Each modem type corresponds to a modem definition file that can be
found in the MHS\SYS directory.  To update your installation with
new or enhanced modem definition files, copy them to this directory.

As Novell continues to expand the list of supported modems, newly
certified modem definition files will be made available through
the following facilities:

    o	 NetWire forum on CompuServe
    o	 Novell Technical Support
    o	 sending Email to LIBRARY@NOVELL

-----------------------------------------------------------------------
			  GENERAL RESTRICTIONS
-----------------------------------------------------------------------

The following lists general restrictions that you need to be aware of:

    o	 This version of Remote MHS supports encrypted passwords in
	 part-time user mode. In order to take advantage of password
	 encryption, your Global MHS server must be running NGMAMP.NLM
	 version 2.0b dated 09-08-93 or later.

    o	 Remote MHS cannot be used with MHS 1.5 Rev A.

    o	 If the modem you are using does not have a corresponding
	 Novell-supplied MDF file, it may exhibit unusual behaviour.
	 MDF files can be created by developers to support these
	 modem types. Refer to the MDF developer documentation on
	 NetWire.

    o	 Remote MHS cannot take advantage of the Global MHS auto-
	 registration feature.

    o	 You cannot run RSETUP or RMHS concurrently with  each other
	 or with other applications that manipulate the MHS database
	 files.


-----------------------------------------------------------------------
			     KNOWN ISSUES
-----------------------------------------------------------------------

The following lists known issues that could not be corrected before
the final release of the software:

*	The USRHST modem does not support the 14400 speed setting.
	Select a speed higher or lower than this number. When using
	this particular setting, RMHS indicates that either the
	modem or com port is configured incorrectly.

*	During an upgrade, if the MAIL variable is used, a redundant
	mail directory is created under the Remote MHS directory.


-----------------------------------------------------------------------
		  IF YOU HAVE QUESTIONS ON REMOTE MHS
-----------------------------------------------------------------------

If you have questions on Remote MHS, call Novell Technical Support
(800-NETWARE, outside the U.S., call 801-429-5588).


-----------------------------------------------------------------------
			   END OF README.TXT
-----------------------------------------------------------------------
