DP Tool Club 17/CD_ASCQ_17_101194.iso/vrac/womnu24b.zip/WOMENU.DOC

Text File | 1994-07-16 | 38KB | 934 lines

                                   WOmenu
                                   ══════

                          The Windows Office Menu





                      ▄▄▄▄▄▄▄▄▄▄▄
                      █  ▄▄▄▄▄  █  (C)Copyright 1994
                      █  █   █  █
                      █  ▀▀▀▀▀  ▀  Bremer Corporation
                      █  ▄▄▄▄▄  ▄  Austin, Texas
                      █  █   █  █
                      █  ▀▀▀▀▀  █  All rights reserved
                      ▀▀▀▀▀▀▀▀▀▀▀





                                 Version 2.5

                                  July 1994
                              TABLE OF CONTENTS
══════════════════════════════════════════════════════════════════════════════

     Topic                                                          Section

     Introduction ......................................................  3

     Miscellaneous .....................................................  4

     Quick Start .......................................................  5

     Commands ..........................................................  6

     WOmenu INI File ...................................................  7

     User Help INI FIle ................................................ 10

     Menu Rights ....................................................... 11

     Users Windows Environment.......................................... 14

     DOS Environment Variables ......................................... 15

     DOS Program PIF Files ............................................. 16

     Software Metering Service ......................................... 17

     WOmeter Windows Metering Utility .................................. 19

     DOSmenu Menu System ............................................... 20

     Shareware ......................................................... 21
                               INTRODUCTION
══════════════════════════════════════════════════════════════════════════════

WOmenu was designed as a simple yet powerful menu system for both network and
stand-alone environments where users must operate under Windows(tm).  Our
environment demands a safe, secure menu to help our users run both DOS and
Windows applications without allowing undo access to our large Texas-wide
NetWare network.  The menu system we needed had to be both easy to use and
flexible and yet it had to stay out of the way as much as possible for our
user operations.  Because we could not find one, we wrote our own.  We hope it
helps you control your Windows environment as well.  Please use WOmenu as you
see fit, but if you continue to use it, you should register according to the
SHAREWARE section below.


Here is an example of why you might need WOmenu to help you out:

You have a network with one or more servers and many users.  Most of these
users run a couple of business-specific apps and some utilities that you
allow.  Now, you are finding that these users can be much more productive if
they could run their one or two business apps at the same time while having
their email and a utility or two instantly available.  This, of course, means
multi-tasking, which probably means Windows.  But how do you keep all of those
'nice' things that Windows offers, like the File Manager and Write and
Notepad, away from the users while defining a Program Group that makes sense
to _each_ user?  Enter WOmenu...it was made to solve just that!


Here is a quick overview of WOmenu:

o    Low resource utilization.

o    Flexible user-specific menus.

o    Unlimited menu items.

o    Unlimited sub-menus.

o    Run any program, DOS or Windows based.

o    Prevent multiple runs of the same program.

o    Easily operate the menu system without having to outfit users with mice.

o    Many rights options to determine whether a menu item is usable by a user.

o    Works great with NetWare and any other network operating system.  Also
     works well as a stand-alone system.

o    All menu setup tasks handled through one INI file.

o    Complete user logging capabilities.

o    Complete Software Metering Services for Windows applications.

o    Works well in conjunction with our DOS-based product, DOSmenu.
                              MISCELLANEOUS
══════════════════════════════════════════════════════════════════════════════

Requirements
────────────
WOmenu's only additional requirement is that it needs the Visual Basic 3.0
runtime library, VBRUN300.DLL, in order to run.  If you do not have this file
yet, it may be downloaded from almost any on-line service.  We can also
provide you with this program, if required.

Startup Options
───────────────
WOmenu is normally started by specifying the program file as the Windows
shell.  The first line in your SYSTEM.INI should read

     shell=[path]womenu.exe

However, it may be started directly from within Windows.  In this case, the
command should be

     [path]womenu.exe

Here, quitting WOmenu will not quit Windows.

Required Files
──────────────
The following files are necessary to run WOmenu:

WOMENU.EXE     The WOmenu program.

WOMENU.INI     The WOmenu INI (menu) file (see WOMENU INI FILE section below).

THREED.VBX     A Visual Basic library file for WOmenu.

CMDIALOG.VBX   Another Visual Basic library file for WOmenu.

VBRUN300.DLL   The main Visual Basic runtime library.

Optional Files
──────────────
WOMENUUH.INI   The optional administrator-defined main user help screen (see
               USER HELP INI FILE section below).

WOMENU.LOG     (You choose name) If logging is enabled, this file is appended
               every time a user performs a menu action.  Included statistics
               are:  user name, node address, server name, date, time, and
               menu action.

WOMENU.MTR     (You choose name) If metering is enabled, this is the central
               file where the metering information is kept.

*.DMM          Optional user list files for metered applications.

WOCALC.EXE     A calculator utility that works with the keyboard as well as a
               mouse (registered version only).

WOCAL.EXE      A calendar utility that easily works with the keyboard as well
               as a mouse (registered version only).

WOVIEW.EXE     A file viewer with a simple interface that works with the
               keyboard as well as a mouse (registered version only).

WOMETER.EXE    A Windows real-time Meter Viewer/Reset utility.
                               QUICK START
══════════════════════════════════════════════════════════════════════════════

To quickly get the menu system up and running, do the following (check the
documentation later for specifics):

o    Copy all WOmenu files to your Windows directory.  This directory is
     normally C:\WINDOWS on a stand-alone system and F:\WINDOWS on a network
     system.  To use WOmenu for all of your users, copy it to the Windows
     network directory.
     WOMENU.EXE
     WOMETER.EXE
     CMDIALOG.VBX
     THREED.VBX
    (VBRUN300.DLL must also be in the \WINDOWS or \WINDOWS\SYSTEM directory)

o    If not already running Windows, run it.

o    Run 'WOMENU.EXE' from the Windows directory.  This first run will make a
     default WOMENU.INI file in the same Windows directory.

That's all there is to it.  You now have an operating menu system.  You may
use WOmenu to change your menu items and sub-menus as you desire.  After you
get the menu the way you want it (especially if you administer a network) you
will want to change some of the default setup options in the INI file and add
appropriate rights to the menu item lines so as to lock your users and protect
your network.  See the WOMENU INI FILE below for help in this area.

If you plan to run in a network multi-user environment, then check these
sections out also:  DOS PROGRAM PIF FILES and USERS WINDOWS ENVIRONMENT.
                                 COMMANDS
══════════════════════════════════════════════════════════════════════════════

EDIT      Allows editing of the highlighted menu item or sub-menu item.  Edit
          fills in all parts of a menu item or sub-menu item except for the
          item's menu rights.  See MENU RIGHTS section below.  This command is
          not available in multi-user mode.

MOVE      Allows moving of the highlighted menu item or sub-menu item within
          the same menu.  This command is not available in multi-user mode.

INSERT    Allows the insertion of a new menu item or sub-menu item.  This
          command is not available in multi-user mode.

DELETE    Allows the deletion of the highlighted menu item or sub-menu item.
          This command is not available in multi-user mode.

HELP      Brings up a context sensitive help screen.

QUIT      Quits the menu system.  If it was used as the Windows Shell, it will
          first check that all programs have been quit and then it will quit
          Windows as well.

F5        Refreshes (rereads) the INI file and repaints the menu form.

Ctrl-F5   Toggles the Multi-User mode.  This command can be password-
          protected.  It is useful when the system is in Multi-User mode and
          the administrator needs to change it.
                             WOMENU INI FILE
══════════════════════════════════════════════════════════════════════════════

WOmenu has one setup file, the INI file (which is the actual menu file).  This
section explains the INI file specifics.

SETUP
═════

[Windows Office Menu Setup]
───────────────────────────
This section deals with setup specifics.  The actual menus are kept in the
remaining sections of the INI file.

Multi-User=
───────────
Default:  no.  This is the switch that determines whether WOmenu operates as a
simple editable menu system for single users or as an overall system where
editing is not allowed and all menu items can be determined through menu
rights.

AdminPassword=
──────────────
Default:  {nothing}.  Place a password here to inhibit the Ctrl-F5 Multi-User
toggle, which is useful for the administrator to have access to changing the
menu even if it is in Multi-User mode.

MainMenuTitle=
──────────────
Default:  Windows Office Menu.  This determines which section WOmenu uses to
define its first menu screen.

UserVar=
────────
Default:  {nothing}.  This is the DOS variable name (set in the login script)
that holds the user login name, like UserVar=userid.  It is only required if
you plan to use the User right (see MENU RIGHTS section below).  See DOS
ENVIRONMENT VARIABLES section below for how to define this variable.

ServerVar=
──────────
Default:  {nothing}.  This is the DOS variable name (set in the login script)
that holds the active server name, like ServerVar=servername.  It is only
required if you plan to use the Server right (see MENU RIGHTS section below).
See DOS ENVIRONMENT VARIABLES section below for how to define this variable.

NodeVar=
────────
Default:  {nothing}.  This is the DOS variable name (set in the login script)
that holds the user workstation address, like NodeVar=nodeaddr.  It is only
required if you plan to use the Node right (see MENU RIGHTS) section below).
See DOS ENVIRONMENT VARIABLES section below for how to define this variable.

DoLog=
──────
Default:  no.  Enter 'yes' here to turn on user activity logging.

LogFile=
────────
Default:  {nothing}.  Enter the name of the log file to use here, like
LogFile=f:\share\womenu.log.  Users must have 'write' access to this file in
order for logging to work on a network.  The log function logs menu start,
menu end, and all program starts.  The user's login name (if defined), server
(if defined), node address (if defined), date, and time name are all entered
into the log file.  You may wish to periodically erase or archive this file
because it can get quite large after a while if you have many users.

DoMeter=
────────
Default:  no.  Enter 'yes' here to turn on software metering.

MeterFile=
──────────
Default:  {nothing}.  Enter the name of the meter file to use here, like
MeterFile=f:\share\womenu.mtr.  Users must have 'write' and 'erase' access to
this file in order for metering to work on a network.  See SOFTWARE METERING
SERVICE section below for specifics on software metering.

MeterDirectory=
───────────────
Default:  {nothing}.  Enter the directory where the *.DMM user list files used
with Software Metering will be kept, like MeterDirectory=f:\share\meters.
Users must have 'write' and 'erase' access to this directory's files in order
for the enhanced user list metering to work on a network.  See SOFTWARE
METERING SERVICE section below for specifics on software metering.

MaxRunning=
───────────
Default:  0.  The optional maximum number of items the users can run at one
time.  Enter 0 for no limits.  Use this function if you wish to restrict how
many programs can be run at once, perhaps for memory reasons.

Note=
─────
Default:  Welcome to Windows Office Menu.  Enter a note here (of approximately
120-140 characters maximum) if you want your users to see one when they first
start the menu system.  After the first user sees this note, a hidden date
will be appended to the end of it so WOmenu can figure how to not show it on
the following days.  That way you do not have to remember to delete the note.
If you enter a note the night before and then view it by running WOmenu, be
sure to go into the WOMENU.INI file afterwards and change the date at the end
of the note to the next day.  If you wish to show a note for several days,
enter a date in the future.  The format is like:

Note=note text.|||DD-MM


MENUS
═════

[sub-menu titles]
─────────────────
These section headings define the sub-menus used in the menu system.  The
first one is [Windows Office Menu] by default.

Pgm#= {Pgm1, Pgm2, Pgm3, etc. up to the maximum of 15 per section}
─────
These entries hold all information for each menu item or sub-menu item.  The
numbers define only the order of items on the menu.  In Multi-User mode, only
the items that pass the 'rights' tests will be actually be shown.

The information is separated by commas, so do not use commas in your
descriptions.  Here are the sections:

Title, Wintitle, Description, Program, Workdir, Rights

Title
─────
The item's button text, like '&WordPerfect'.  Use the & character to
underscore a letter for a hotkey, if desired.

Wintitle
────────
IMPORTANT:  The actual name of the program's Windows title.  You may have to
run a program it check this one time.  Do not add any dynamically appended
text here.  For instance, Notepad's Windows title in version 3.1 is 'Notepad'.
But after loading a program, it becomes 'Notepad - [filename]'.  Make sure
only to add the 'Notepad' part here.  Case is not significant.  Another
example:  for Winword, use 'Microsoft Word'.  For PIF files, you will decide
yourself what that Windows title will be -- just place it here as well.

Description
───────────
The item's optional description text, like 'A word processor'.

Program
───────
The item's executable call to Windows and/or DOS, like 'f:\apps\wp\wp.exe'.
This could be a PIF file or batch file as well.

Workdir
───────
The item's optional work directory, like 'h:\'.

Rights
──────
The item's optional rights to determine whether the user will get this item on
their menu, like '{d=f:\apps\wp}'.  See the MENU RIGHTS section for specifics
on this powerful feature.


SUB-MENU TITLES
═══════════════

Sub-menu titles are annotated slightly differently than normal menu items for
program.  Where '&WordPerfect' may define a menu item, '< &Word Processing >'
would define a sub-menu (and subsequent new section '[Word Processing]').
WOmenu takes care of this for you, but if you decide to edit your menu file
manually, take this into consideration.


NOTES
═════

Not all sections must be filled out.  Although the title and program section
is always required for a menu item, only the title section is required for a
sub-menu item.  Just be sure that commas remain to identify which section text
belongs to, like:

;─────
Pgm1=&Lotus 1-2-3,LOTUS 1-2-3,,123
;─────
This is enough to run 123 if it exists and can be found in the path.
                              USER HELP INI FILE
══════════════════════════════════════════════════════════════════════════════

The administrator can opt to have a home-grown main help screen (the one that
appears when the user presses F1 at a menu or sub-menu screen).

WOmenu creates a file called WOMENUUH.INI (UH is for User Help) in its
directory the forst time it is run.  This INI file is a shell that allows
input of up to 14 help lines of 48 characters or less each.

When a user presses F1 for help at a menu screen, WOmenu checks to see if at
least the first or second line of this file (1= or 2=) is filled out.  If so,
then this data is used to fill in the help screen.  If not, the normal
built-in help screen is shown.
                               MENU RIGHTS
══════════════════════════════════════════════════════════════════════════════

A powerful means of segregating the menu file between users is by applying the
'rights' feature in Multi-User mode.  We can decide what items should actually
appear on a user's menu by defining certain rights for some or all of the
items listed in the INI file.  You must manually add these rights into the
menu file, preferably after you have made it the way you want it to be with
the Edit, Move, Insert, and Delete commands.  Let's discuss each right.

All rights assumed
─────────────────-
Right = no rights entered.  This method is the quickest and least secure way
of checking users rights because it checks nothing.  In other words, a menu
item will show up on a user's menu, period.  Here, you will be relying on your
defined network rights to determine whether a user will be able to _run_ an
item or not (they will see them on their menu).

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\,
;─────
User gets item if it is available, period, because the final section is empty.


Directory rights
────────────────
Right = {d=directory name or d=directory name1,directory name2 ..}.  WOmenu
will look to see if any of the listed directories exist when it reads the menu
file, and if none of them do, it will not place the item on the user's menu.

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\, {d=f:\apps\editor}
;─────
User gets item only if F:\APPS\EDITOR is 'visible' in the user's environment.


File rights
───────────
Right = {f=file name or f=file name1,file name2 ..}.  WOmenu will look to see
if any of the listed files exist for the user when it reads the menu file, and
if none of them do, it will not place the item on the user's menu.

;─────
Pgm1=&Notepad, NOTEPAD, Win Notepad, notepad, h:\, {f=f:\windows\notepad.exe}
;─────
User gets item only if F:\WINDOWS\NOTEPAD.EXE is 'visible' in the user's
environment.


User rights (uses UserVar definition)
───────────
Right = {u=user_id or u=user_id1,user_id2 ..}.  This method takes the
discrimination down to the actual user id running the system.  If the user
name is in the list, then the user gets the item on their menu (if any other
specified rights are also approved).

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\, {u=joeb}
;─────
User gets item only if his user logon ID is JOEB.


Server rights (uses ServerVar definition)
─────────────
Right = {s=server_name1 or s=server_name1,server_name2 ..}.  Here, by placing
one or more server names with a menu item, you are saying only show this item
when the user is logged into one of those servers.

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\, {s=main_server}
;─────
User gets item only if the user is logged into and running on MAIN_SERVER.


Node rights (uses NodeVar definition)
───────────
Right = {n=node_address or n=node_address1, node_address2 ..}.  This method
takes the discrimination down to the actual user's workstation.  If the node
address is the same as that of the workstation, then the user gets the item
on their menu (if any other specified rights are also approved).

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\, {n=fa164505}
;─────
User gets item only if his work station's address is FA164505.


Environment rights
──────────────────
Right = {e=dos_env_var~env_var_text, ..}.  This right tests for the contents
of a DOS variable.  For instance, to run a menu item depending on what room a
person is in, set ROOM=room_number at login; then enter this right for the
menu item in the menu file:  {e=room~102}  to test for room 102.

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\, {e=room~102}
;─────


Software metering rights (not really a 'right')
────────────────────────
Right = {m=command[:number]}.  Entering this rule on an item's right line will
force the command for the item to be metered, if metering is turned on and the
meter file has been defined (within WOMENU.INI).  Please see the SOFTWARE
METERING SERVICE section for a complete discussion of this capability.

;─────
Pgm1=&Word,MICROSOFT WORD,Microsoft Word,winword.exe,h:\,{m=winword:25}
;─────
This item will run as long as less than 25 other users are running it.


Password rights (not really a 'right')
───────────────
Right = {p=password where password is any alphanumeric, non-case sensitive,
phrase}.  Placing a password on a menu item means that when the user selects
this item, the user will be prompted for the correct password.

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\, {p=restrict}
;─────
User gets item only if he or she can answer the password prompt with RESTRICT.


Question rights (not really a 'right')
───────────────
Right = {q=your question that demands a yes/no answer?}  This method simply
pops up a question and asks for a Yes or No answer.  If no, it will not run.

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, h:\, {q=Are you sure?}
;─────
Will only run if the user answers Yes.


Group rights (how to 'fake' this right)
────────────
Right = no such right; use directory rights instead.  WOmenu was built to be
generic as far as networks are concerned.  Therefore, the networks 'groups'
are not used.  Instead, we suggest (and use ourselves) a method that actually
invokes the directory right method.

Let's say you only want users who are a member of group WP or a member of
group WORD_PROCESS to be able to run WordPerfect.  Within SYSCON or NETCON
(for NetWare networks), you should give each of these groups a trustee
right assignment to a directory called, let's say, F:\FLAGS\WP.  Read/file
scan is enough to 'see' the directory.

Then, in the user's INI (menu) file, define the following right:

Pgm1=&WordPerfect, WORDPERFECT FOR WINDOWS, A wordprocessor, ...
     ... f:\apps\wp\wp, h:\, {d=f:\flags\wp}

which in effect will perform the same function as checking for a member of a
group, because only those users who _are_ a member of one of the above sample
groups will be able to see this directory.


NOTES
═════

More than one of the above methods may be used at one time, either within the
same right grouping or by having two or more groupings.  For example, you can
place both a server (s=) and a group (u=) method on the same menu item, like:

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, {u=joeb}{s=server1}
;─────
Here, it is read as user joeb _AND_ on server1.

or by using the OR ';' such as

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, {u=joeb;s=server1}
;─────
Here, it is read as user joeb _OR_ on server1.

Note that when using more than one grouping {}, each of the groupings must be
true for the item to be shown (they are ANDed).  When using one or more
methods within the same group, they are ORed.

Placing a '!' before a name means 'not'.  Where {u=joeb} means if the current
user is joeb, then display the menu item; {u=!joeb} means display the item
only if the current user is NOT joeb.

The biggest rule that you must remember about the rights methods are that
within each set of braces {}, the answer must be true.  So if you use more
than one set of braces for a menu item, they all must be true.  For example:

;─────
Pgm1=&Notepad, NOTEPAD, Windows Notepad, notepad, ...
     ... {d=f:\apps\wp}{u=joe,jim;n=fa164505}{s=!server2}
;─────
will only show if the user can 'see' directory F\APPS\WP _AND_ the user is JOE
_OR_ JIM _OR_ the node address is FA164505 _AND_ the user is not on SERVER2.
                        USERS WINDOWS ENVIRONMENT
══════════════════════════════════════════════════════════════════════════════

The WOmenu system can make your users' Windows environment a simple one that
is very easy to maintain.  We'll explain our setup as an example.

o    We set up Windows as a network install in F:\WINDOWS.  We ran one user
     SETUP from the Windows directory to get the default WIN.INI and
     SYSTEM.INI files.  We changed the shell defined in SYSTEM.INI to
     WOMENU.EXE.  Then we copied the necessary files to our own SETUP
     directory under F:\WINDOWS.  These files, surprisingly enough, consisted
     of only the following files:

     WIN.COM
     WIN.INI
     SYSTEM.INI

     Note that no Program Manager files are needed at all.

o    For each DOS program our users may run through their menu definitions, we
     defined a PIF file.  Our defined items in the INI (menu) file point to
     these PIF files on the Pgm#= lines.

o    To set up a user, we add them to a WINDOWS group in Syscon, make a
     directory under their private directory called WINDOWS, and copy the
     above listed files into that directory.

o    Our users run mostly DOS PIF-defined programs and have no need for a
     mouse.  WOmenu runs and handles nicely without one.

That's all there is to it.  Easy and quick to add/delete users from the menu
setup.   And we have security while providing our users with multi-tasking.
                        DOS ENVIRONMENT VARIABLES
══════════════════════════════════════════════════════════════════════════════

WOmenu uses up to three DOS variables to tell the system about your
environment; user ID, server name and workstation node address.

In the case of NetWare, you define and load this DOS variable once during the
user login script with the correct information.

     DOS SET USERID="%LOGIN_NAME"

where userid can be called anything you wish.  You could then add this name
to various rights as desired.  Womenu takes care of the rest.

If you plan on using server name rights, then you would set up the server name
variable in a similar manner.  For NetWare,

     DOS SET SERVER="%FILE_SERVER"

place the above line in the users login script.

The node address variable is needed if you intend to restrict any menu items
by comparing a work station's node address.  In a Novell network, you could
define this variable like:

     DOS SET _NODE="%P_STATION"<<4

where the <<4 takes the first 4 numbers away from the actual twelve digit
address.
                          DOS PROGRAM PIF FILES
══════════════════════════════════════════════════════════════════════════════

When placing DOS programs on a user's menu system, through their INI (menu)
file, there are a few cautions and guidelines we have learned and would like
to pass on to you.  they are all optional but make a lot of sense toward
keeping the menu usable and secure.

o    Make sure the entry for the "Window Title" is the same as the entry you
     will place in the INI file on the Pgm#= line.  In this way, WOmenu will
     easily be able to find this program's DOS window when trying to determine
     if the user has already run the program once or not.  (WOmenu attempts to
     allow users only one run of each program on their menu.)

o    Recommend setting the option "Full Screen" to on.

o    Recommend setting the option "Background" to on.

o    Recommend locking out all "Shortcut Keys" except Alt-Tab (which is needed
     to switch between programs and back to the menu window).

                        SOFTWARE METERING SERVICE
══════════════════════════════════════════════════════════════════════════════

WOmenu includes a powerful capability called software metering which enables
you to control the number of simultaneous run instances of an application.
For instance, if you have bought 25 licenses for Microsoft Word, you now have
the means to insure that only 25 copies are run at one time from with the menu
system on your network.

There are more expensive and perhaps more foolproof offerings on the market
for this service, but WOmenu does the job simply and easily.  And we believe
that an administrator's effort level in attempting to control software
licensing is at least 95% of any large distributor's concerns.

Here is how you set up metering:

1.  Place these commands in WOMENU.INI under [Windows Office Menu Setup]:

DoMeter=yes
MeterFile=f:\share\womenu.mtr (or something like that)
MeterDirectory=f:\share\meters (or something like that) {this is optional}

(Note:  If MeterDirectory is defined, then UserVar and NodeVar must also be
defined.  See WOMENU INI FILE for instructions.)

Users must have WRITE and ERASE rights to the above area(s).

2.  Place the meter right on those commands you want metered, for example:

;─────
Pgm1=&Word,MICROSOFT WORD,Windows word processing, ...
     ... f:\apps\word\winword.exe,h:\,{m=word:25}
;─────

will meter the use of F:\APPS\WORD\WINWORD.EXE for all accesses from WOmenu.
If 25 instances are already in use (in this example), then WOmenu will
instruct the user that the maximum licenses are in use and to try again later.

The syntax is important.  The application keyword, in this case WORD, may be
10 or less characters with no spaces, followed by an immediate colon ':',
followed by an immediate number from 1 to 999 (with no spaces) -or- if no
:number is entered, then 999 is assumed (good for counting accesses only).

These both work:
{m=word:25} ;limit 25
{m=word}    ;no limit

Of course anyone accessing WINWORD.EXE from outside of the menu system will
not be metered in this way.  See the WOMETER METERING UTILITY section to find
out how to meter DOS software runs from outside the menu system.  Also, if you
call the application from more than one menu item in your menu file, make sure
you place the same meter rights for each item.

The MeterDirectory entry, which is optional, allows WOmenu to keep track not
only of how many users are in an application, but also who those users are and
their node address.  These 'live' user lists are kept in the defined
directory.  FOR THIS FEATURE TO WORK, YOU MUST GRAB THE MENU USER'S NAME AND
NODE ADDRESS (read WOMENU INI FILE section for instructions on how to do
this).

Note: RECOMMEND DELETING METER FILES PERIODICALLY/NIGHTLY...
If any user locks up while in a metered application, or gets rebooted at that
point, then the meter count for that app will remain off by one (it will show
one greater than actual).  For this reason, we recommend deleting the defined
main meter file (and the user list *.DMM meter files, if used) periodically,
perhaps at night before or after your backup.  See WOMETER WINDOWS METERING
UTILITY section for how to do this automatically.

Be careful when viewing your meter file.  The recommended way to view it is
with WOmeter (see below).
                    WOMETER WINDOWS METERING UTILITY
══════════════════════════════════════════════════════════════════════════════

This utility can optionally monitor your software usage from outside of the
menu system but from within Windows.  All of your users' programs can be
reliably monitored for metering.

There are no command line parameters; just run:

     WOMETER

WOMETER.EXE will attempt to find the meter file's name in its WOMETER.INI
file.  If it does not, it will make this file in its home directory and then
you can fill in the name of the meter file, like:

[Setup]
MeterFile=c:\windows\womenu.mtr (or something like that)
MeterDirectory=c:\windows\meters (or something like that) {this is optional}

(Note:  If MeterDirectory is defined, then UserVar and NodeVar must also be
defined.  See WOMENU INI FILE for instructions.)

WOmeter allows real-time reseting of specific metered applications, in case
the count has gone astray (perhaps from user lockups, etc.).

You may also set up WOmeter to automatically erase your meter file(s) on a
daily basis at a specified time.  The default is 00:01 (one minute after
midnight).

You may also define the length of time WOmeter waits between re-reads of the
meter file (between 10 and 60 seconds).

If you also use our DOS-based menu product, DOSmenu, WOmenu can easily work
in concert with it for both meter files and log files.  Simply point the name
and location of these files to the same files delineated in the DOSmenu INI
file.  Then you will have a complete picture of your user activities on your
network.
                           DOSMENU MENU SYSTEM
══════════════════════════════════════════════════════════════════════════════

We have another product called DOSmenu that is a network menuing system as
well.  However, DOSmenu works from DOS.  It is a very popular product that
can work nicely in conjunction with WOmenu.  If you are interested in this
product, please contact us.  If you wish to try it first, it is available from
Compuserve in the shareware form.  Look in the NOVUSERS/New Uploads forum for
the file DOSMNU.EXE.  It is also available on many BBS's.
                                SHAREWARE
══════════════════════════════════════════════════════════════════════════════

Evaluation Copy
───────────────
THIS IS NOT FREE SOFTWARE!  You may evaluate and use this product, but if you
decide to make use of it on a regular basis, you must register your copy.

Note:  Businesses, government agencies and institutions are required to
register this software package before extended use.

We offer several inducements to you for registering.  First of all, you will
receive the most up-to-date copy of the program -- and we update the program
on a regular basis.  Second, we have additional mini-utilities that work
nicely with WOmenu not included in this package that we will ship to you upon
registration.  Third, you will never see the shareware message again.  Make no
mistake, however -- this is a fully functional version of WOmenu that is not
"crippled" in any way.

Distribution
────────────
This is "user-supported" software.  You are hereby granted permission to
distribute this evaluation copy of WOmenu and its documentation, subject to
the following conditions:

1.  Shareware WOmenu may be distributed freely without charge in evaluation
    form only.  The original PKZIP self-extracting file, WOMNU.EXE, is the
    preferred method.

2.  WOmenu in its shareware form may not be sold, licensed, or a fee charged
    for its use.  If a fee is charged in connection with WOmenu, it must cover
    the cost of copying or dissemination only.  Such charges must be clearly
    identified as such by the originating party.  Under no circumstances may
    the purchaser be given the impression that he is buying a registered
    version of WOmenu.

3.  Shareware WOmenu must be presented as a complete unit with documentation.
    Neither WOmenu nor its documentation may be amended or altered in any way
    without permission of the copyright holder.

4.  By granting you the right to distribute the evaluation form of WOmenu, you
    do not become the owner of WOmenu in any form.

Any other use, distribution or representation of WOmenu is expressly forbidden
without written consent from the copyright holder.

Registration
────────────
The non-commercial single-user registration fee for WOmenu is $40.00 US.
($5 shipping is included.)

The commercial/government and multi-system site fee for WOmenu is:

     Non-network environment:
          Per machine        -  $35.00 US.
     Network environment:
          Per server         - $160.00 US.
($10 shipping is included.)

Send a check, money order or company P.O. for the appropriate amount to:

          Bremer Corporation -WOmenu
          3401 Cactus Wren Way
          Austin, Texas 78746

Thank you.

Telephone: [phone]
CompuServe ID: 71614,2556

See ORDER.TXT for a ready-made ordering form.

Disclaimer
──────────
The author does not warrant that the functions contained in this program will
meet your requirements or that the program operation will be uninterrupted or
error free.

The author specifically disclaims all other warranties, expressed or implied,
including but not limited to implied warranties of fitness for any particular
purpose and of merchantability.

In no event will the author be liable to you for any damages, including but
not limited to any lost profits, lost savings, commercial damage or other
incidental or consequential damages arising out of the use or inability to use
this program, or for any claim by any other party.

Trademarks
──────────
Trademarks of companies or products mentioned in WOmenu documentation files
are the property of their respective companies.