Contents of the MENU.DOC file
Written by Mark M McCurry
For Key Software.
(c) 1990 Key Software
The Mountain Menus System was written for pro and beginner
alike. It is easy to set up and easy to use. It can also run your
most demanding software without getting in the way. Although
there are hundreds of menu programs, all the ones we tried seemed
to have the same pitfall. They remained resident in some fashion
or another taking up precious ram space. Our desktop publisher,
and a few other graphic type programs, just can't stand to share
the system ram with anyone. Some of our clients were not happy
about having anything resident while their important programs
were running. Others already had a bunch of their favorite
resident software running and the menu was just too much. Some of
the menus conflicted with other resident software. For these
situations, I wrote Mountain Menus.
When a program is run from Mountain Menus, the menu itself
completely disappears from memory. The only file it opens is the
batch file it creates to run your application. If you are using
batch files now to run your programs, Mountain Menus provides a
great way to consolidate those files into one VERY user friendly
You can define one main menu and up to twenty nine submenus.
Each menu can have up to twenty items to chose from. Each menu
item has it's own full screen help window. The text in each help
window is up to you, anything you want.
Mountain Menus is fully moused if a mouse driver is loaded.
This feature alone makes it a pleasure to use. If you have a
Novell network, Mountain Menus can use Novell's menu files, as
they are, giving you the added features of a mouse and context
Mountain Menus Ver. 2.7 Page(1) Key Software
Mountain Menus runs fine on Novell's Netware and makes a
great Network menu system. It also runs fine as a single user
menu on a stand alone P.C. with any DOS version from 3.0 to 4.1.
The menu system can use any number of different menu files.
These menu files can have any name, BUT MUST have the extension
.MNU. To call up a different menu, enter it's name on the command
line right after MMENU. Do NOT include an extension. So, to call
up SALES.MNU, just type MMENU SALES at the DOS prompt, to call up
MIS.MNU, type MMENU MIS, etc. If you do not specify a name,
MAIN.MNU is assumed.
Because the menu allows for multiple menu files, I had to do
something about the help files too. Therefore the help files must
have the same name as the menu files they refer to, with the
extension .HLP. So for the above examples, the help files would
be SALES.HLP and MIS.HLP.
If Mountain Menus can not find the menu / help files you
specify in the current directory, it will search the PATH for
them. This is a new feature of 2.5.
Execution of the batch file is now hidden under the menu
screen. The screen is not cleared until the batch file is under
way, also, if DOS 3.3 is detected, the first line of the batch
file will be @ECHO OFF instead of ECHO OFF. This makes the screen
flow a little better. Also a new feature.
There is a screen blanker which activates after 15 minutes
of keyboard and mouse inactivity. To restore the screen, just
press a key, or click the mouse button. The click, or key press
will be absorbed so there is no chance of executing something you
Release 2.5 of Mountain Menus has a new SYSTEM MENU which
provides an easy way to change the system time and date. Also on
the system menu is a quick view calander (mouse driven) which
will display any month from JAN 1,1980 to WAY into the future.
This calendar accounts for leap years, of course.
Finally, a utility which can be used to view, or modify the
system environment. This utility is VERY powerful. It displays
the amount of memory allocated for the environment, how much is
used, and how much is free. Any changes you make to the
environment from here are made to the MASTER environment table.
This means no matter how many levels of COMMAND.COM are running,
no matter how many programs you've shelled out of, when you EXIT
back to the original COMMAND.COM, your changes are there.
There is also a security system for unattended stations.
Mountain Menus Ver. 2.7 Page(2) Key Software
REGISTERED USERS GET...
Registered users of Mountain Menus get a version of the
program which sports a CONFIGURATION FILE !!
The config file can be in the current directory, or anywhere
in the PATH. From the config file, the user has control of...
Direct access to the Menu Builder. The Builder is a stand
alone, mouse driven, menu file builder and editor. It is
available on Compuserve in Novell's forum, and IBMSYS. The
Builder, and access to it, is being distributed with the Mountain
Menus 2.7 registered version.
The ability to DISABLE the ape to DOS has been added
for system administrators who like to isolate their users from
the DOS prompt.
The ability to have Mountain Menus return to the submenu
where the last command was executed from !! (like Novell's)
The ability to RENAME AK.BAT to anything you like using an
THE COLORS!! Any and all of the colors can be set to what
ever you want. This includes back ground, heading, help window,
help window border, menu windows, menu window borders, highlight
bar, and item picked colors.
The top two lines of the heading can say anything you want!
Up to forty characters on each line will be centered and
displayed for you. Your name, Your company's name, what ever you
The date display in the heading can be configured to display
the date in numeric or alpha format. It can either be 10/29/89 or
Sunday, Oct 29 1989. Which ever you like!!
The mouse speed is configurable from here. So you can speed
up or slow down the mouse movement to your liking. You can even
specify different speeds for up and down, and, left and right
Menu items can be optionally sorted via an entry in the
config file. Items can also be left justified instead of centered
if you like.
Finally, for now, the screen blanker time out can be set
from an entry in the configuration file.
DON'T MISS OUT ON THESE OPTIONS !! PLEASE REGISTER YOUR COPY !!
Mountain Menus Ver. 2.7 Page(3) Key Software
USING MOUNTAIN MENUS
Setting up Mountain Menus does require some knowledge of
DOS. You should be familiar enough with directories to be able to
make one to put the required files in. You will also need a text
editor to create and modify the .MNU and .HLP files. Any editor
will do, even EDLIN if that's all you have, or a word processor
that can save files in ASCII text format. Last, but not least,
you should be familiar with batch files, or at least know what to
type at the DOS prompt to get your programs to run.
FILENAME.MNU The user definable menu structure file.
There can be any number of these in the
current directory, or anywhere in the PATH.
FILENAME.HLP The user definable help screen text file.
This should be named the same as the menu
file it applies to, and can also be
anywhere in the path.
MMENU.BAT This batch file is REQUIRED ! even
though it only contains a couple of lines,
it MUST be present or the menu will not
return after your program is done.
this is the file you actually run.
MMMENU.EXE The executable file. The end result of
running the above batch file.
VENV.EXE The view environment program overlay.
This file can be in the current directory
or anywhere in the path.
MMMENU.CFG Registered users only. This is the user
defined menu configuration file. Use your
editor to set it up as you like. It can be in
the current directory, or anywhere in the
If you wish to rename the executable file, you can, but DO
NOT name it MMENU.EXE. Three 'M's is ok, one 'M' is ok, anything
is ok, but not MMENU.EXE !! Be sure to also change the contents
of MMENU.BAT to reflect the new name. MMENU.BAT must NOT be
Mountain Menus Ver. 2.7 Page(4) Key Software
USING MOUNTAIN MENUS
Although Mountain Menus will run from PATH directories just
fine, the best place to install it is in a directory by itself on
a local hard drive. It doesn't even need to be a PATH directory.
We have a 60 station Novell network at work with Mountain
Menus as the standard. Our work station AUTOEXEC.BAT files look
like this: @ECHO OFF
Once at their menu, among other things, they have an option
to log onto the network. In the main.mnu file, it looks like
Now they are logged in, back at their home directory, and
back at their menu. The next option on their menu is NETWORK
MENU. In the main.mnu file there is just one line MMENU NETWORK
calling up another menu is as easy as that. If you get used to
changing drives and CDing to the proper directory to run your
programs, You'll never need to worry about PATHS. The menu
program will always find it's way back to the drive, and
directory where it started from.
Once your in the menu, there are many ways to get around.
First of all, if you have a mouse driver loaded, everything is
accessable with the mouse. You can point and shoot, using the
arrow keys to hilite an item then pressing ENTER. The function
keys can be used to select a menu item, F5 for the fifth item,
SHIFT-F5 for the fifteenth item. etc. You can also press the
first letter of a menu item and execute it that way. It is up to
YOU to make sure no two items start with the same letter. If two
items do, only the first one will be found.
If a sub menu is showing, the ESCape key or the right mouse
button will make it go away. If only the main menu is showing,
ESCape or right button will prompt you to leave the menu program.
Pressing the TAB key, or clicking the left button anywhere
in the heading area, will bring up the help window for the
highlighted item. clicking either button, or pressing the
key will make it go away.
Mountain Menus Ver. 2.7 Page(5) Key Software
THE SYSTEM MENU
Pressing ALT-S, or clicking the left mouse button anywhere
on the words 'SYSTEM MENU' with bring up the system menu.
There are now six items on the system menu. The first is the
QUICK VIEW CALENDAR. If you select it, you will see three windows
pop up. The first is a list of months with this month
highlighted, the second shows the calendar with today
highlighted. The third simply says PREVIOUS YEAR NEXT YEAR. If
you have a mouse, you can just click on any of the months in the
list to display that month. Clicking on the PREVIOUS YEAR NEXT
YEAR will scroll through the years. Clicking the right button
makes it all go away. If you are using the keyboard, the UP and
DOWN arrows scrolls through the months, and the LEFT and RIGHT
arrows scroll through the years. The ESCape key makes it all go
The calendar is just a quick reference. Something I have no
room for on my desk, yet it seems I always need one. Notice that
the day is only hilited in the current month, year. Also note
that leap years are accounted for.
The next two items on the system menu are convinient ways to
set the system time and date. These are direct replacements for
typing TIME or DATE at the DOS prompt. Notice that you only need
to type the numbers, not the colons or slashes. Pressing ESCape
aborts the change.
Item number four deals with the environment. When DOS boots
up, it sets aside some memory for it's environment. The
environment is a place in memory where you can put information
that some programs use to tell them how to run. DOS puts a few
things there itself. The prompt is stored there, so is the PATH
of directories that you told your computer to search for files.
Many programs expect to find variables there which they can use.
Environment variables are always stored using the format
SOMETHING=SOMTHING. At the DOS prompt or in a batch file, the SET
command is used to change the environment. ie.
SET NAME=MARK, SET VIDEO=mono. The variable must be in upper
case, what it's equal to can be anything. The maximum length of a
variable is 127 characters. Normally DOS only sets aside around
160 BYTES for the environment. If your PATH= statement is more
than one line long, half the space is already gone. You can
enlarge the environment by adding a line to the CONFIG.SYS file.
SHELL=C:\COMMAND.COM /e:1024 /p This tells DOS to set aside 1024
BYTES for the environment. NOTE that the /p option is NECESSARY
or the boot will halt.
Mountain Menus Ver. 2.7 Page(6) Key Software
THE SYSTEM MENU
The VIEW ENVIRONMENT option on the system menu provides a
view of the current environment, and the ability to add, remove,
and change environment variables. Press to modify something,
or press the key to return to the system menu. If
you press , you will get a dialog box where you can enter a
change, and a small help window. Pressing ESCape makes it all go
away. To add a variable, type it's name, then equal <=>, then
what it's equal to. Changing an existing variable is done the
same way. To erase a variable, type it's name, then equal <=>,
with nothing following the <=>. Do NOT USE the SET command in the
dialog box. There is no need. For those computer types, YES this
does change the original COMMAND.COM's environment. So, no matter
how many DOS shells are open, no matter how many levels of
COMMAND.COM deep you are, when you EXIT all the way back to the
original COMMAND.COM, your changes are still there. This is the
ONLY program I know of, short of DEBUG which can pull this off.
The fifth item on the system menu provides a direct route to
the Menu Builder with the current menu file. This will only work
in the registered version. Any changes made to the menu file and
saved, will take effect immediately. The Builder is also a free
running .EXE file, so it can be run from the DOS prompt.
The sixth item on the system menu is a simple (but
effective) security device. If you select SECURE SYSTEM from the
system menu, you will be prompted for a four letter (or number)
code. This IS case sensitive!! When the fourth letter is entered,
the screen goes blank, and the keyboard is effectively locked.
The only way back to the menu is to re-enter the code. The only
alternitive is to re-boot.
Mountain Menus Ver. 2.7 Page(7) Key Software
THE FILENAME.MNU FILES
The best way to learn how to set up the ".MNU" file is to
print out the examples that is included and run the menu program
to see how each line is interpreted by the menu program. The
basic structure is as follows:
%MY COMPANY'S MAIN MEN <== the main menu title
ACCOUNTING <== main menu item #1
F: <== batch command
CD\PEACH <== batch command
PEACH <== batch command
WORD PROCESSING MENU <== main menu item #2
%WP MENU <== call up a submenu
DATABASE MENU <== main menu item #3
%DB MENU <== call up a submenu
RUN A DOS COMMAND <== main menu item #4
@1"ENTER COMMAND:" <== prompt user for input
LIST A FILE TO THE SCREEN <== main menu item #5
TYPE @1"ENTER FILE TO LIST:" <== prompt batch command
PAUSE <== batch command
%WP MENU,5,10 <== submenu title,x,y coords
WORD PERFECT <== submenu item #1
CD\WP <== batch command
WP <== batch command
WORD STAR <== submenu item #2
CD\WORDSTAR <== batch command
WS <== batch command
PC WRITE <== submenu item #3
CD\EDIT <== batch command
ED @1"ENTER FILE NAME TO EDIT:"<== prompt batch command
%DB MENU,12,3 <== submenu title,x,y coords
DBASE III+ <== submenu item #1
CD\DBASE <== batch command
DBASE <== batch command
ORACLE <== submenu item #2
CD\ORACLE <== batch command
ORACLE <== batch command
FOXBASE+ <== submenu item #3
CD\FOX <== batch command
MFOXPLUS <== batch command
Notice that I do not include commands to change
directory back to where I came from. This is done
automatically. Notice the @1"prompt" commands. This will
stop and ask for input from the user and put whatever
the user types in place of the @1, in the batch file. If I
selected PC WRITE from the menu and typed in "MYFILE" for
file name to edit prompt, the "AK.BAT" file which is created
would look like this:
Mountain Menus Ver. 2.7 Page(8) Key Software
THE FILENAME.MNU FILE
ECHO OFF <== OR @ECHO OFF if DOS 3.3 or better
CLS <== also provided by program.
CD\EDIT <== first command from main.mnu
ED MYFILE <== compare this to above main.mnu example
C: <== provided by program
CD\MENU <== provided by program
MMENU <== provided by program
The CD\MENU means the menu was originally run from the
MENU directory of the C drive. It could read CD\DIRNAME,
depending upon which directory Mountain Menus was run from.
You can use the @1"prompt" as many times as you like within
a single batch command line. You are, however, limited to 75
total characters on a command line, so keep the prompts short.
An example might be, sending a message on Novell.
SEND @1"MESSAGE:" TO @1"USER or GROUP:"
Mountain Menus does NOT leave the menu file open while a
person is sitting at the menu. The menu file is opened, read in,
and closed. It is opened again when an item is selected to read
in the commands for that item. It's never open for more than a
second. This means that if you have an editor which does not
leave it's files open (like Qedit, the world's best editor), it
is possible to edit the menu file without having to get everyone
out of the menu. This is a VERY helpful feature !!
Mountain Menus Ver. 2.7 Page(9) Key Software
THE HELP FILES
The TAB key brings up a full screen help window, so
will clicking the mouse anywhere in the heading area.
The text in the help window is sensitive to the menu item
which is highlighted when the TAB key was pressed. So
each item on each menu can have it's own help window.
The help screen text for each item can be entered, using
a text editor, into the file called ANYNAME.HLP. This name
MUST match the name of the menu file it is for.
The following page contains a sample of how
MAIN.HLP might look for the above example of the
Each text group begins with a percent sign and the
name of the menu item. The menu item must be an exact
match of the way it is entered in the MAIN.MNU file,
upper and lower case count. The order of the text groups
is not important.
This shows a Sample help file MAIN.HLP:
Here is the help text for the first item on the main menu,
which is PEACH ACCOUNTING. Remember you have 78 columns by
23 lines worth of space for each help item.
%WORD PROCESSING MENU
Here is the help text for the second item on the main menu,
which is the word processing menu. Pressing ENTER here will
bring up the word processing submenu.
Here is the help text for the third item on the main menu,
which is the database submenu.
Here is the help text for the first item on the second menu
defined in MAIN.MNU, which is WORD PERFECT.
Here is the help text for the second item on the second menu
defined which is WORD STAR.
Here is the help text for the third item on the second menu
defined which is PC WRITE.
Here is the help text for the first item on the third menu
defined which is DBASE III+.
Here is the help text for the second item on the third menu
defined which is ORACLE.
Here is the help text for the third item on the third menu
defined which is FOXBASE+.
Mountain Menus Ver. 2.7 Page(10) Key Software
One important thing to note is that batch files must be
handled differently when used in the .MNU files. When a batch
file is run from another batch file, control does not return to
the first batch file when the second batch file finishes running.
Clear as mud, right?
If you put the name of a batch file in the MAIN.MNU file,
the menu will not be re-run when your program finishes. There is
a solution to this dilemma. It uses a seldom called for switch
To run a batch file from MAIN.MNU, replace the following
This tells DOS to run a temporary COMMAND.COM for the sole
purpose of running MYBATCH.BAT. When MYBATCH is finished
executing, the new COMMAND.COM disappears and control returns to
AK.BAT, which in turn, runs the menu program again. The second
COMMAND.COM will take up about four thousand bytes of memory.
The BEST solution to this little problem is to enter the
commands from the batch file right into the MAIN.MNU file.
Users of DOS 3.3 have another alternative. Which is to take
advantage of a new batch command. The above lines could be
If for any reason the menu does not return after your
program is finished, suspect a batch file is being run from the
MAIN.MNU without using one of the above methods.
This little quirk can be an advantage. There are times when
I want the menu to drop me off at the DOS prompt in a certain
directory. I have included a simple batch file called LANDAT.BAT.
Note the way I use it in the MAIN.MNU file.
Mountain Menus Ver. 2.7 Page(11) Key Software
TIPS AND TRICKS
Always be specific in your batch commands, Don't rely on the
PATH= statement to find your program for you.
use the format F:
Don't worry the menu can find it's way home.
It is important that you do NOT run the executable from
inside AK.BAT. You should NEVER have a batch command: MMMENU in
your menu file. Results are UNPREDICTABLE !!
Always run a batch, which runs the executable: MMENU.BAT.
You cannot rename MMENU.BAT, but you sure can have another batch
file, say, MENU.BAT, with the same contents.
Most of our users have a menu item in there menu files which
calls up their favorite editors with the menu file. This way they
can easily change the menus and batch commands without returning
to DOS. Whats neat is that since the menu file is read in every
time the menu program runs, the changes they make, take effect
The key to logging off the network is to be running Mountain
Menus from the local hard drive when you do it. If your running
from the network, you'll almost certainly get a 'batch file
missing' error as soon as it hits the logout command. If you need
to run from the net, just have AK.BAT transfer control to a batch
file on the local drive(boot drive), which actually runs the
logout command. The local batch file can then run the menu from
the local drive. Don't CALL the local batch, just put it's name
in your menu file. When the local batch file is run, AK.BAT is
released. Since the local batch file was run from a drive which
will still be around after them logout command, there will be no
'batch file missing' error.
Creative use of batch files within the .MNU files can solve
most problems. But if you run a batch from within the .MNU file,
it is up to that batch file to get back to the menu.
YES you CAN load TSR's from the menu with no ill effect.
Want to load SideKick? Just have a menu item with one command: SK
When the menu comes back, SideKick is there, easy!!
There is a Novell login script command which executes a
program, but does NOT return to the login script. If you use it,
You will not end up back at the menu.
Mountain Menus Ver. 2.7 Page(12) Key Software
TIPS AND TRICKS
Do NOT TRY to run Novell's menu from Mountain Menus or visa
versa. It has to do with the fact that DOS NEVER forgets when a
batch file is in progress, Neither does Novell. As long as one or
the other menu program has a batch file active, the other can not
get control of the DOS prompt. Also, when a batch is run from
Novell's menu, it DOES return.(they use there own little trick,
and that doesn't help matters.) If one of you folks finds a way
to pull this off, let ME know, would ya?
The HOME BASE is the directory where Mountain Menus was run
from. When my users select NETWORK MENU after they select LOG IN,
the menu file takes them to their USER directory on the network
drive. This sub is mapped to G: in the system login script, so
getting there is simply G: In this 'HOME BASE' directory, that
user has full rights. No one else (except the supervisor) has ANY
rights in this directory. Here, there is a menu file, named after
the user. His own personal menu. For instance; My HOME BASE DOS
prompt looks like this: G:\USER\MARK>_ Here, there is a menu
file: MARK.MNU, my menu.
So, when I get here, the second menu file command runs
MMENU MARK. Now, my home base is G:\USER\MARK, and I am running
my personal network menu.
When MMs creates an AK.BAT file, it creates it in the home
base directory. No one else can even SEE it, much less run it or
delete it. There can NEVER be a conflict.
The conflict arrises when I get to the DOS prompt, CD to a
directory where more than one person has rights, and run the menu
from THERE, and so does somebody else !!
On our network the required files are in a PATH directory,
like PUBLIC. There is another batch file there called simply
MENU.BAT. It contains the following lines:
All of my people know that if they EVER get caught at the
DOS prompt, getting back to familiar ground is as easy as typing
MENU . This gets them back where they belong, running
Also in PUBLIC, there is a COMMON.MNU file. On each user's
menu is an option to run the network COMMON menu. In their menu
files, it's just one line: MMENU COMMON. On the common menu there
is an option to return to your personal menu. It looks just like
the MENU.BAT above.
I can have DOZENS of these common style menus in PUBLIC,
each with a way back to their personal menus. It's all very clean
and hassle free. All AK.BAT files are in home bases.
Mountain Menus Ver. 2.7 Page(13) Key Software
RESTRICTIONS AND CREDITS
Remember to use an ASCII text editor to build the .MNU and
.HLP files. EDLIN is the text editor which comes with DOS,
although I hope you have a better one than that. Any word
processor which allows files to be saved as ASCII text files will
do the trick.
Overall restrictions for Mountain Menus are as follows;
1) A maximum of thirty menus may be defined in a .MNU
file. That's a main menu and twenty nine submenus. If
you define thirty-one menus, the last one will not be
2) Each menu can have a maximum of twenty items on it. If
you define more than twenty items for any menu, only
the first twenty items are used.
3) Menu titles and menu items may be a maximum of forty
characters wide. If they contain more than that, they
will be truncated at forty characters.
4) The batch file command list for any menu item is
limited to twenty commands. Each command line may be up
to seventy-five characters wide.
5) While the menu program completely disappears from
memory when it runs your applications, it does require
enough memory to store the items in the .MNU file. My
test MAIN.MNU file, which had thirty menus defined,
each with twenty items, managed to allocate about 150k
of memory. The only time I can see this being a problem
is if you run a LOT of resident software, AND you have
a very large MAIN.MNU file. If the program cannot find
enough memory, it returns to DOS with a message saying
I hope you enjoy the Mountain Menus system. Any comments you
have about Mountain Menus, ways to improve, things it should do
that it doesn't, things it does that it shouldn't, etc., can be
sent via EASYPLEX mail on Compuserve. My CISID is 71500,1457.
For those who are interested, the program was written in C
using Borlands TurboC 2.0. The windows are courtesy of The Window
Boss, a library of windowing functions created by Phil
Mongelluzzo of Star Guidance Consulting. The time necessary to
write the program is courtesy of my wife.
Mountain Menus Ver. 2.7 Page(14) Key Software
RESTRICTIONS AND CREDITS
I have written several programs for my private use and have,
at this point, built up quite an arsenal of source code. As a
control systems programmer, much of the coding I do deals with
process control, gas plants and the like, but in my spare time
there's no telling what I might dream up for myself to do.
Mountain Menus was a pleasure to write and I'm looking
forward to building it into a first class menuing system geared
toward the networked office P.C.. At this point, Mountain Menus
will probably branch into a stand alone version and a network
specific version. I will be using the Novell C language interface
and I intend to put it to good use.
A more recent note.....
What I've got planned is to continue to make operational
improvements on the menu based on suggestions from my registered
users and my beta testers. These updates will come in the form of
versions 2.8 and 2.9. Shareware versions of these will probably
be available, and currently registered users will receive these
upgrades on the house. Version 3.0 will be aimed at the network.
Although I haven't sat down and drawn anything up, some
preliminary ideas include;
A NETWORK MENU in addition to the SYSTEM MENU. From here I
can see things like, menu to menu chat modes, both group and
private conversations, Email (of course), convinient displays for
userlists and drive maps, Print Queue selections, and what ever
else I can dream up.
A function to automatically detect security equivalence and
bring up a SUPERVISOR MENU to those with that level of security.
On this menu, who knows what? I've been a network supervisor for
over a year now, so I'll probably fill it with things I wish I
had now. More later (as they develop)......
Mountain Menus Ver. 2.7 Page(15) Key Software
OWNERSHIP AND DISTRIBUTION OF
MOUNTAIN MENUS, version 2.7
MOUNTAIN MENUS is the property of Mark McCurry and Key
Software. Use and distribution of the executable MOUNTAIN MENUS
programs are controlled by the following license terms:
1. A registered copy of MOUNTAIN MENUS can be obtained
from KEY SOFTWARE for payment of a $20.00 fee.
Checks should be made payable to Mark McCurry. If you
consider keeping Mountain Menus, Please register your
copy so my wife will learn to love me again.
Registered users will, of course, receive the next
release of Mountain Menus at no charge, up until
release 3.0 comes out.
Let me know what you'd like to see it do.
2. If you need some customization of the program, let me
know when you register. If the change is easy enough,
I'll just do it for you. If it requires substantial
work, we'll work something out. I charge a LOT less for
that sort of thing than Lotus does.
3. The holder of a free or registered copy of MOUNTAIN
MENUS is authorized to make and distribute copies of
MOUNTAIN MENUS provided the files on the distribution
disk are copied unchanged, the disk is copied in its
entirety, and no compensation is received.
4. Bulletin Board SYSOPS are authorized to make
MOUNTAIN MENUS available on their boards provided that
all of the files from the distribution disk are
Please notify KEY SOFTWARE, simply as a matter of
information, if you put a copy on your board. We're
Use of this program acknowledges this disclaimer of warranty:
"This program is supplied as is. Key Software
disclaims all warranties, expressed or implied, including, and
without limitation, the warranties of merchantability and of
fitness of this program for any purpose. Key Software
assumes no liability for damages direct or consequential, which
may result from the use of this program."
Mark M. McCurry, President
P.O. BOX 8323
Corpus Christi, Texas 78468
Mountain Menus Ver. 2.7 Page(16) Key Software