Readme.rtf       Date 2020/10/27

BlackWood Systems, Inc.

phone: 602-569-8766
fax:   480-905-8778
email: support@blackwood-systems.com
web:   www.blackwood-systems.com

This file contains the latest version and upgrade information. This file is the first place to look for initial installation and upgrade information.

Please thoroughly read and agree to the License.txt file before using this software.

For an initial install, further in this document the section entitled "FIRST INSTALLATION" describes the installation process from start to finish.

Sections in this document

Compatibility between client and server
Special Notes
CURRENT VERSIONS
NEW FEATURES / BUGS FIXED
CLIENT INSTALLATION NOTES
mini-MOMI
MULTIPLE PLATFORM SERVER SUPPORT
FIRST INSTALLATION
UPDATE AN EXISTING INSTALLATION
RUNNING SSMOMI SCREEN SAVER AS A STAND ALONE PROGRAM
MANUAL INSTALLATION OF NONSTOP BASED PROGRAMS
FUTURE PLANS
Directory layout

Compatibility between client and server

The ability of our customers to upgrade as painlessly as possible to a new MOMI release is important to us.

Our standard release migration recommendation is to upgrade the server first and the client second within a release series (i.e. 4.xx, 5.xx and 6.xx). Normally, when a release series changes, both the client and server must both be upgrade at the same time. However, a 5.xx client will operate with MOMI 6.xx.

Please check below for Oldest client version 	tested with server.

Note that not all features may operate when running a combination of old and new MOMI software.

Special Notes

The PC must be configured with at least 24-bit color for the client to operate fully with MOMI. A warning message is displayed at client startup if a lower color depth is detected. While the client will generally function correctly with a lower color depth, certain features are not available such as the pop-up window when the mouse is placed over the connector lines between systems on the screen SubSystems / Expand / Diagram.

The CAIL Emulator was provided courtesy of CAIL and is not a component of any purchased MOMI product. The Emulator is no longer provided and was removed from the MOMI installation package.
 
The IP Workshop Pro TCP/IP Subnet calculator is provided courtesy of Peter Kostov and Peko Software and is not a component of any purchased MOMI product. BlackWood Systems and Peko Software reserves the right to discontinue, limit or alter the availability in future releases. Please see the IP Workshop Pro help within the calculator for additional information and to check out other tools he has available.

CURRENT VERSIONS
   
	Release Package 	  6.08
   Release Date (yyyy/mm/dd) 2020/10/27

	item	Version
	----	-------
	Latest O/S tested	G06.32.01 - H06.29.00
		J06.23.00 – L20.05.00
	
	Client Version	6.08	Build 876
	Server Version (VPROC)	6.08b  T0000G06___V6_08b___2020_07_20
      
	Buffer Version	Client 21.62   Server 21.62
	History database	3.10
	CONFMOMI	6.01
	OBYMOMI	5.02
	OBYCSQL	5.02
	MomiFTP.exe	2.14
	ssMOMI.scr	6.00
	MomiEMail.exe	1.10
	SendMail.exe	1.01
	IPCalc.exe	1.3.3

	Oldest client version
	tested with server	5.80

	Clients 5.15 and earlier may fail on connect.

NEW FEATURES / BUGS FIXED 
(see MOMI HISTORY.RTF for previous versions)

Common new features (requires current client and server)
If you are using Client Access, newly added screens in a MOMI release update are not available to users by default. This action may be changed on the screen Configure / Client Access / Global Settings by checking the option New screens enabled by default. The user that started MOMI, known as the “Default Security User” always has new screens enabled by default.  

Impacts in this version
The Free version of the CAIL emulator is no longer provided with the MOMI client. If the user has the full-function purchased version installed it will continue to work. If the user has any 6530 Emulator programs on their PC that they want to start from within the MOMI client, the Systems / External screen will allow a button to be created to start their emulator.

MOMI Software short-cuts, as displayed by the Windows Start menu, now use the format of BWS MOMI n.nn. Previously, MOMI software short-cuts were located under BlackWood Systems. This change is for compatibility with Windows 10 which does not handle multiple levels within the Start menu.

MOMI Client
New Screens: 	
·	None 

New Features:
•	On screens that have a popup mini-report(Spoolers, Spooler Job, and TCP/IP Status) if the mini-report is displayed and either the "Request" button is pressed or an "Auto-update" occurs the mini-report will now update just like the main screen.
•	The "Alter IPU affinity" feature is now enhanced to show the current process name, IPU and affinity before asking the user to make any change.
•	Files / Enscribe / Files
	- If the user right-clicks on the 'Logical Filename' (by default the last column) of a SMF file the file can be managed as if it was not SMF (i.e. purged etc). (For Tom S.)
•	SubSystems / Logs / EMS Log
- Some Mini-Reports can now have items clicked on that will temporarily filter the EMS log grid to show only those items. Then by pressing the 'Mini-Reports' button(now renamed 'Revert-Mini') again will revert to the previous filter and reshow the mini-report.         (for Gary B.)
- Import and Export now allow wildcards for the Owner and the SubSystem. (For Tom S.)
•	SubSystems / Spooler / Jobs
- Now if the "Search Jobs" feature is used and then the user clicked the found job number to view the job, the list of jobs available to view will be the list of job found to contain the search text not like previously when it was a list of all jobs that had been searched.  If the search has not completed there will not be a list available on the view job screen. Also the list is now positioned on the screen in a location that should not hide much of the job. (for Tom S.)
•	Alarms / List / Import
- Import may now be directed to delete all current records first then import the selected records.
•	Configure / Client / General
- Added new option to "Retain Connection and Logon state during system change".  This option will keep the socket connection up and running for the current system when the user changes to another system. If the user was previously logged On for this system it will still be           logged on.  This in effect allows "AutoLogon" on a system with a single-use password.
	Note: The "Auto Logon with change System" setting is now only used when dealing with an older Server version 5.xx.

Bug Fixes:
•	Sometime if the user had several MOMI clients running then Logged-off or shut them all down at the same time the client as it shutdown would get errors on updating the MOMI.INI file when it saved the client location and would crash causing a MOMI.LOG crash file. Fixed.
•	Under some connection failure circumstances the Client Diagnostics message "Client ReConnected to Server" would not contain the address and port of the socket, Fixed.
•	Systems / Probes
- When the client changed systems and the old system was being probed, the probe socket was mistakenly closed only to reopen the next update. Fixed.
•	Systems / Probes / Base and
   Systems / Probes / Alarm Stats 
- When no systems were selected for probing the systems details were still displayed. Fixed.
•	Systems / File Transfer
- Under some conditions it was impossible to enter a new 'Host Name/Address' or 'Momi Server' that was not already in the dropdown list.  Fixed.
- When changing NSK directories, under some conditions it was possible for the files displayed to be displayed twice.  Fixed.
•	Files / Enscribe / Volumes
- If scroll wheel was used to scroll the grid the client would crash. Fixed.
•	Processes / All Processes
   - If a user requested an All Process list then changed systems before the results were returned the List would still be populated from the request on the previous system. Fixed.
•	SubSystems / Logs / EMS Log
- When in 'Lightning mode' the right-click of the config button did not display the collector’s status.  Fixed.
- When in 'Lightning mode' it was possible the 'Lightning mode' was exited before all collectors had finished looking.  Fixed.
- While in 'Lightning mode' if the user went back into config then hit the 'Request with new options' button the display would not change from 'Lightning' mode into the normal display.  Fixed.
- Filter by Color would not filter new incoming records. Fixed.
- Filter by Color was inconsistent when clicking on color button and right-clicking on color button. This sometimes cause result that were not expected.  Fixed.
- Under some circumstances and timing if a EMS request was in progress and the 'Clear' button was pressed a single EMS message would display.  Fixed.
- The detail would not always display the EventBX record. Fixed.
- Under some circumstances a "C/E/R" EventTX record would display from a previous display.  Fixed.
- When 'Reverse scrolling' was enabled and a find was performed, the grid did not scroll the grid so the 'found' record would be on the screen.  Fixed.
- Mini report for severity count was off by 1 (always had one extra Info rec). Fixed.
- In the EMS Message Detail the EventBX record would not always display.  Fixed.
- When loading a lot of EMS messages and the user would "pause" the loading, the time in the top-right corner of the client would drift only to reset to correct time when the loading was resumed.  Fixed.
- The Default Scroll Speed value set in 'Configure/Client/Single Screen/Logs/Ems Logs' was not being used first time into the EMS Log screen. Fixed.
- If multiple collecters were being used and the user changed from scroll speed less that fastest to fastest speed the client might timeout.  Fixed.
•	SubSystems / Logs / EventBX / List-Import-Export
- Negative event numbers would cause the search to fail.  Fixed.
- After no more records were found using Next if the Prev was used it would skip the last record and give the next to last. The same would occur using the Previous then the Next.  Fixed.
- If an EventBX record had been deleted then a search was performed and the deleted record is selected in the 'Skipped because of Errors' list the client would crash.  Fixed.
•	SubSystems / Spooler / Jobs
- Drop down box for Location now displays the same data on the main screen (along the bottom) as on Config. Fixed.
- Errors returned from the Server were not always shown on the screen.  Fixed.
•	Alarms / List / Import
- The import did not automatically import elements required for an imported alarm. Fixed.
•	Configure / Client / Actions
- If 'Version Checking Actions' were checked and the Readme file was empty or connection to the file was lost the client would crash when the version check was performed.  Fixed.
•	Configure / Define Sysems
- When Client was first started with no MOMI.INI file yet created, once the 1st system was entered the client would not connected until it was restarted. Bug introduced in 6.07. Fixed.

Misc. Items:
•	Now when the Client is first started all keyboard and mouse activity is discarded until the client is fully operational.
•	The NonStop runtime param 'DEFAULT-SECURITY-USER' now can contain wildcards (i.e. $ and ?).
•	If the Monitor size is less than 1024x758, the client will automatically set the configuration setting to allow smaller client size and start the client maximized for the small screen.
•	If a user was logged on to the client, then attempted another logon that failed the client would log the user off. Now it will remain logged on as the original user.
•	Several more grids now allow scrolling using the mouse wheel.
•	SubSystems / Logs / EMS Log
- Under some circumstances the socket would timeout if a lot of ems messages were being recieved and the ems display was running at full speed or in lighting mode.  Fixed.
•	Alarms / Define / Export and 
	Alarms / Define / Import 
	- have been moved to Alarms / List tab.
- Virtual disks are now colored to show they are virtual.
•	SubSystems / Spooler / Job
- The display for 'Age of Job' selection has been changed to show the current settings plus a button to convert to All.  To change selection, press the Config button.
•	Configure / Server / Server Info
- Added support for the new NonStop runtime param 'TCPIP-TCP-NODELAY'.
•	Configure / Client / Actions
- Added activity display when deleting all EventBX records.
•	Configure / Client Access / User Define / Alarms
- Since the Export and Import has been moved from 'Display Alarm' to 'Display List', the old check state on 'Display Define - Create/Update Items' no longer sets Export/Import. To enable Export/Import the 'Export/Import Items' must be checked.

	Known issues:
•	The FireFox web browser does not display help correctly if HTML4 is selected. Use HTML5 or another browser instead.
•	When using Windows 7 and a 4K monitor and the client is resized to full screen, the down-arrow on a drop box is very small. They do not resize like other items. It works fine with Windows 10.
•	When converting from Mini-MOMI to full MOMI it may be necessary to restart the client.
•	Systems / File Transfer / SFTP
 - If file is transferred as a Key-Sequenced structured file sometimes SFTP will think the transfer is successful but the host file is left empty.  A check is now done and an error shows if this happened. Note: Sometimes making the REC LEN even will succeed. Some failures are caused by unknown factors and seem to be a failure in the SFTP Server on the NonStop.
•	SubSystems / Discovery
- Feature is still under development and subject to change. 
	Comments and suggestions are invited and welcome.

MOMI Server
	New Features:
·	Scanning of spooler jobs across multiple spooler supervisors has been restructured and improves performance. From the 6.07 version of the server.

•	A message is now generated in the MOMI Log if the amount of time to process an alarm, where an interval is specified, exceeds the interval. This situation may indicate the probing interval is too frequent. From the 6.07 version of the server.

•	The alarm DiskFile / Subvolume file count may now specify if the count should include open / closed or open-closed file. The default is open-closed which is how the alarm previously operated. From the 6.08a version of the server.

 	Bug Fixes:
·	Scanning of spooler jobs across multiple spooler supervisors now always resets the job number. Previously, it was possible some jobs in subsequent supervisor may have been skipped. From the 6.07 version of the server.

•	The reading of information from CNF01DB corrects a problem where reading forward could return data from a partial collection of disk records but reading backward correctly returns the complete record. Several other unlikely situations were also corrected. This problem was introduced in the 6.04 client. From the 6.07 version of the server.

•	The server no longer stops an existing logon server when the MOMI client version 6.00 through 6.06 issues a command to release context. This resulted in the inability to logon to a User ID with the requirement from CMON / Safeguard that it may only be accessed by another User ID first. For example, if access to Super.Super first required logon to Tech.* access would never work. From the 6.07b version of the server.

•	The alarm DiskFile / Subvolume now functions. From the 6.08a version of the server.

Misc. Items:
·	Server adjustments to system time now pass the TUID parameter to SETSYSTEMCLOCK to help prevent an adjustment if another adjustment is made outside of MOMI. From the 6.07 version of the server.

•	The error text displayed if a delete is attempted on a purple alarm (i.e. ‘really red’) now better indicates a configuration error was detected and the alarm cannot be deleted. From the 6.07 version of the server.

•	Several performance improvements when reading data from CNF01DB. From the 6.07 version of the server.

•	Additional checks were added to help ensure that Spooler job time-open and time-closed are within a specified limit. Note that the spooler uses 48-bit timestamps with a .01 second resolution which may have a fraction of a second value present but not displayed. From the 6.07 version of the server.

•	Additional error conditions are now displayed when dealing with the Spooler. Also, a failure to open a Spooler Supervisor now stops processing where previously the Supervisor was skipped. From the 6.07a version of the server.

•	The server now performs an update to EventBX data so that the Event Number now considers a negative value and sorts numerically. See the CNF01DB Upgrade Note below. From the 6.07a version of the server.

•	The MOMI Log now shows the file system error when a client disconnects. From the 6.08a version of the server.

•	At the TCP/IP level the server no longer issues a socket option to delay sending data. A CONFMOMI keyword TCPIP-TCP-NODELAY is now available to specifically control this action. From the 6.08a version of the server.

•	Additional information is now logged to the MOMI Log if invalid data is received on the TCP/IP connection. Previously, some error conditions were correctly dropped but did not log the reason.

Known Issues:
·	None 

CNF01DB Upgrade Note:

Server version 6.07 and later performs a one-time conversion, transparently to the user, of the Event Number in EventBX records so that negative values access numerically in order.

If you do not have any EventBX records defined, which are found in the client under SubSystems / Logs / EMS EventBX, there is no concern nor action needed.

When the server is started and if version 1 EventBX records are present they are converted to the version 2. If no EventBX records are present, no conversion occurs. During conversion the MOMI server operates normally other than EventBX data may not be immediately available, depending on the amount of data (processing should be quick perhaps taking a couple minutes). Two messages are recorded in the MOMI Log, one if a conversion is initiated and another at completion. If the server is stopped prior to conversion completion, at server restart the conversion restarts. EventBX records should not be added or changed during conversion as they may be over-written. Once the conversion is complete, subsequent server restarts or upgrades do not repeat the conversion.

Note that server fallback to version 6.06 or earlier will not see any converted EventBX data. It is recommended to make a copy using FUP DUP of CNF01DB prior to running a new version of the server.

MOMIFTP 
·	None

ssMOMI 
·	None	

MomiEmail 
·	None	

SendMail 
·	None	

IPCalc 
·	None

CLIENT INSTALLATION NOTES

Installation of the PC client via setup requires logon as the PC administrator. A Windows security failure during setup usually means it is necessary to right-click and select Run as administrator to gain Admin rights, which is a level above Administrator.

The setup launcher has an alternate installation option of copying MOMI files to a shared network location.  

mini-MOMI

MOMI provides the ability to operate in a reduced functionality or lite mode. This mode is automatic whenever MOMI is started without a password. To install mini-MOMI, follow the installation instructions but omit a password in the CONFMOMI file.

Mini-MOMI will operate for 2-years from the version date of the NonStop server portion of the program. The expiration date is displayed on the PC Client screen Configure / Diagnostics.

Shops running mini-MOMI are encouraged to check our web site from time-to-time for new versions, updates or a mini-MOMI password.

While it is our intention to provide mini-MOMI in future versions, BlackWood reserves the right to alter, limit or discontinue mini-MOMI in subsequent releases.

MULTIPLE PLATFORM SERVER SUPPORT

MOMI configuration files support S-Series, NonStop Integrity, NonStop Blades and Integrity NonStop X.

On the NonStop system, in the subvolume where MOMI is installed, the following object files are present by default:

   BWMOMI		- 32-bit TNS/R native (S-Series)
   BWMOMIi	- 32-bit TNS/E native (Integrity & Blades)
   BWMOMIx	- 32-bit TNS/X native (Intel X64 & Virtual NonStop)

The TACL obey files OBYCSQL, used to SQL/MP compile MOMI objects, and OBYMOMI, used to start the MOMI subsystem, automatically select the correct object file.

If automatic platform selection logic does not function, the error Illegal program file format is encountered, simply change the obey files to reference to the correct BWMOMI? object.

FIRST INSTALLATION
UPDATE AN EXISTING INSTALLATION

If you are installing MOMI for the first time, or updating an existing installation of MOMI, this section will walk you through 1) installing MOMI on the PC, and 2) installing MOMI on the NonStop System.

Installing MOMI software to the local PC requires Administrator access under Windows. 

1)	If you need MOMI software, download the latest version of MOMI from our web site.

2a) If you downloaded an EXE file:

a. double click on the downloaded file

2b) If you downloaded a ZIP file:

a. expand the ZIP file to an empty subdirectory on your PC

     b. double click on the file Launcher.exe

2c) If you have a MOMI DVD / Flash Drive:

a. double click on the file Launcher.exe

3)	Once the installation process starts your given the options to a) Install the MOMI Client, b) Install the MOMI Server files on NonStop Server, c) Copy MOMI client files to common server location, or d) View ReadMe file for MOMI. Select Install MOMI Client. A logon prompt may occur for administrator. Click though the initial and Welcome screen. Please read and accept the license agreement.

4)	The next screen is Choose the Destination Folder, or location, where the MOMI files on the PC are to be installed (default recommended). By default, each version of MOMI installs into its own version specific subdirectory.

5)	The next screen selects the Setup Type. Choose Complete Installation.

6)	Choose the name of the program group for shortcut on the Start menu (default recommended). By default, each version of MOMI creates its own version specific shortcuts.

7)	Click Next to begin the installation (which may take some time).

8)	Click finish.

9)	The program MomiFTP is automatically started and will perform the FTP or SFTP transfer of files from the PC to the NonStop.

On the 1st Connect to NonStop page, select the transport type, fill in the Host Address (your NonStop IP address), User ID, password and initial Volume/Subvolume where the MOMI files are placed. The User ID specified owns the files once the transfer takes place. Press Connect. If the connection was successful, you will see a big green "Connected..." .

Press Next >>> to advance the screen.

On the 2nd Select Vol/SubVol on NonStop screen shows a list of the files present in the selected location. Change the location if desired and press Change.

Press Next >>> to advance the screen.

On the 3rd Select New Install or Update screen press Put Files on NonStop. The status boxes indicate the outcome of the transfer.

Press the Exit button to disconnect and stop the program.

10)	From a TACL terminal emulator, Logon with the User ID and password to operate $MOMI. Volume to the location where the MOMI files were placed.

11)	Edit the file OBYMOMI. This is a TACL obey file used to start MOMI and provide initial configuration information. Page down to the section "set values below here". This marked portion of the obey file is the place to change initial startup values for MOMI.

Check the process name, CPU $MOMI operates in, priority and home terminal. The default values are good for most systems.

12)	Edit the file CONFMOMI. This edit file is used to set various MOMI attributes using keywords. Set the System-description and check the TCP/IP process name and port that MOMI will 'listen' on for PC client connections.

mini-MOMI users, the above should be about the only items of concern.

MOMI users, add your MOMI password. Also, define any history files desired. MOMI automatically creates the history files in the location specified.

13)	SQL/MP compile MOMI (if you don't have SQL/MP, ignore this step):

From a TACL prompt: OBEY OBYCSQL

14) Create a Super Group helper program (the steps below omit logon to the super.* ID):

Purge BWSSG2

Rename BWSSG1, BWSSG2

Rename BWSSG, BWSSG1

FUP DUP BWMOMI, BWSSG, sourcedate			(BWMOMIi or BWMOMIx)

FUP GIVE BWSSG, <super.group>					 

FUP SECURE BWSSG, NGNG, PROGID

An existing BWSSG must be updated any time BWMOMI is updated.
(The FUP DUP option of SOURCEDATE or SAVEALL must be used)

15)	Start MOMI:

    From a TACL prompt: OBEY OBYMOMI

    (wait at least 1 minute before proceeding to the next step)

16)	On your PC, start the PC MOMI client (Start/ALL Programs/BlackWood Systems/MOMI_n.nn/MOMI). The MOMI client will detect an initial start on the PC and will prompt for the TCP/IP address of the NonStop and port. The port is defined in the CONFMOMI file and has a default of 2010.

Note that these instructions may reoccur in other portions of this document or provide optional installation methods.

RUNNING SSMOMI SCREEN SAVER AS A STAND ALONE PROGRAM

Some users have requested the ability to run the ssMOMI screen saver as a standalone program that does not stop when the screen is clicked, or the keyboard is pressed.

To run ssMOMI as a standalone program:

1)	Copy the MOMI screen saver ssMOMI.scr giving it the name ssMOMI.exe.

2)	Start the program as follows:

ssMOMI.EXE /c AsEXE

3)	A pop-up window displays. Select the location of your MOMI.INI file. By default this is located at:

C:\Documents and Settings\<user>\Application Data\BlackWood Systems\MOMI

4)	After pressing OK, the screen saver appears. Press X to close.

5)	Create a Shortcut with the Target as follows:

ssMOMI.EXE AsEXE

(path details to the EXE omitted)

The run-time param /c directs the program to display a pop-up window to configure the location of the MOMI.INI. AsEXE directs the program to continue executing after keys are pressed (i.e. don’t function as a screen-saver).

MANUAL INSTALLATION OF NONSTOP BASED PROGRAMS

If the MOMIFTP utility cannot be used to transfer files from the PC to the NonStop server, these instructions describe how an alternate file transfer program would be used. The MOMIFTP utility does not perform any 'special' actions, but simply renames files (if existing are present) and transfers MOMI files from the PC to the NonStop System using FTP or SFTP.
 
The first step is to locate the source files. If MOMI is installed on the PC the files are located by default at:

C:\Program Files (x86)\BlackWood Systems\MOMI_n.nn\Tandem Install\NonStop\
 			
(where n.nn is the release package number)

If you have the MOMI download ZIP from our website expand the files to an empty subdirectory and look for the subdirectory \NonStop Install. The MOMI DVD files are in the same subdirectory name.

Note that under the subdirectory \NonStop there are two additional directories \Ascii and \Binary. This grouping indicates the file transfer mode (i.e. ASCII or Binary).

The second step, using a file transfer utility, copy files from the PC to the NonStop (all to the same destination subvolume) -

Binary

 				BWMOMI
 				BWMOMIi
	  BWMOMIx
 				EMSEXPO

ASCII

		FUPEVTCX
OBYMOMI
CONFMOMI
OBYCSQL
OBYALTER

The third step is to logon to the NonStop System, volume to the location where the files were placed and OBEY the TACL obey file OBYALTER to alter the file codes (or manually perform the steps below):

a) FUP alter BWMOMI		,code 700
b) FUP alter BWMOMIi	,code 800
c) FUP alter BWMOMIx	,code 500
d) FUP alter EMSEXPO	,code 845

At this point the files are transferred. Continue the instructions in the section First Installation / Update an existing installation after the step using MOMIFTP.

FUTURE PLANS (may or may not be in future releases)

		1) CMON   
		2) More history chart-able entities
		3) New functionality as requested by our users
		4) Additional Tools and References as we think of them
		5) Pathway information

We welcome comments, suggestions and bug reports. Please send them to:

support@blackwood-systems.com

*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*

The MOMI DVD / Flash Drive or EXE files follow the same general layout.  

The following is the general file layout and purpose for each file:

Documents							= Directory of documentation
License.rtf      			=		MOMI disclaimer/license
License.txt      			=		MOMI disclaimer/license
MOMI History.rtf 			=		Change history
Readme.rtf       			=		This file	(<<<---START HERE)
Extras            		= Directory of Optional Programs
	ssMOMI.SCR          	=		MOMI Screen saver
   
	Help               		=	Directory of Help files
	HTML5										=		Directory of HTLM5 style help
	Microsoft_HTML_Help 	=		Directory of CHM style help			
	WebHelp	         			=		Directory of Web style help
	MOMI_User.doc					=		Help in Word format
	MOMI_User.pdf					=		Help in Adobe PDF format

	NonStop Install    		=	Directory for Setting up NonStop
	NonStop 							=		Directory of NonStop software
				ASCII								=			Directory of Ascii files
					CONFMOMI						=				Initial configuration file
					FUPEVTCX						=				FUP obey file to create EVENTCX file
					OBYALTER						=				TACL obey file to alter file codes
					OBYCSQL						= 			TACL obey file to SQL compile MOMI
					OBYMOMI						=				Startup obey file
				Binary								=			Directory of Binary files
					G06.29-and-later	= 			optional use if G06.29 or later
						BWMOMI						= 				MOMI Server (TNS/R native code 700)
					Pre-H06.05				=				optional use on pre-H06.05
						BWMOMIi				 	=					MOMI Server (TNS/E native code 800)
					BWMOMI     			 	=				MOMI Server (TNS/R native code 700)
					BWMOMIi					 	=				MOMI Server (TNS/E native code 800)
					BWMOMIx					 	=				MOMI Server (TNS/X native code 500)
					EMSEXPO					 	=				Compiled EMS filter (code 845)

	MomiFTP.EXE					   	=			FTP MOMI files to NonStop System
			TanFiles							 	=			MomiFTP.EXE config database

   PC Manual Install 			=	Directory for Manual Install
		CAIL										=		Directory containing CAIL Emulator
		Documents							=		Directory of documents
		Extras									=		Directory of optional programs
		Help										=		Directory of Help formats
		Misc_Sounds						=		Directory of misc. sound files
		Sounds									=		Directory of MOMI sound files
		Tandem Install				=		Directory for Setting up NonStop
		Calendar.new					=		MOMI calendar database
		ErrorCodes.mom				=		MOMI system supplied error database
     MOMI.EXE								=		MOMI client
   		Readme.rtf						=		Readme instructions (<<<---START HERE)
     TimeZone.mom					=		MOMI time zone database

		Launcher.exe						= Program allowing user to select install options
       CentralServer.exe    = Program that copies Client files to central PC           Server
		Readme.rtf							= This file
		MOMI_Client.exe				= MOMI Client Installation program