home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
UTILS1
/
DOSMNU58.ZIP
/
DOSMENU.DOC
< prev
next >
Wrap
Text File
|
1994-03-09
|
65KB
|
1,739 lines
DOSmenu
"Powerful, Easy Management System"
(C)Copyright 1993-1994
by
Skip Bremer
Version 5.8
March 1994
TABLE OF CONTENTS
==============================================================================
Topic Section
----- -------
Introduction ...................................................... 1
Miscellaneous ..................................................... 2
Quick Start ....................................................... 3
Startup Batch File ................................................ 4
Commands .......................................................... 5
Setup ............................................................. 6
Menu Definition ................................................... 7
Menu Rules ........................................................ 8
Sub-Menus ......................................................... 9
Compiling Menu Files .............................................. 10
Translating Menu Files ............................................ 11
Temporary Batch Files ............................................. 12
DOS Environment Variables ......................................... 13
Noticing .......................................................... 14
Personal Menus .................................................... 15
Software Metering Service ......................................... 16
DMutil Maintenance Utility ........................................ 17
DMquery Batch Input Utility ....................................... 18
DMmeter Metering Utility .......................................... 19
Example Menu File.................................................. 20
INTRODUCTION (1)
==============================================================================
DOSmenu was designed as a simple yet powerful menu system for both network and
stand-alone environments. Our environment that demands an easily changeable,
concise menu system to help us provide proper support for a large NetWare wide
area network domain spanning Texas. The menu system we needed had to be both
easy to use and very flexible and yet it had to stay out of the way as much as
possible for our user operations. Quite simply, we couldn't find one, so we
wrote our own. We hope it helps you control your environment as well. Please
use DOSmenu as you see fit, but if you continue to use it, you should register
according to the documentation in DMLEGAL.DOC.
Here is a quick overview of DOSmenu:
o Small executable size.
o No memory overhead.
o Unlimited menus.
o Run any program, including TSRs.
o Many rights options to determine whether a menu item is usable by a user.
o Automatically knows NetWare. Substitutes are easily defined on other
networks and stand-alone environments.
o Menu environment may be changed on-the-fly while users are active.
o Optional compilation of menu files provides ultimate menu security.
o One utility (DMutil) handles all menu setup tasks.
o Can translate NetWare menu files.
o Complete user logging and reporting capabilities.
o Software Metering Service and reporting capabilities.
o Full mouse support and menu utility set with registered version.
MISCELLANEOUS (2)
==============================================================================
Requirements
------------
DOSmenu's only known requirement is that it must run under DOS 3.1 or higher.
It runs fine from a Windows DOS session (and it loads Windows fine).
Recommendations
---------------
Consider placing the command
SHELL=C:\COMMAND.COM /E:512 /P {or more}
in all CONFIG.SYS files using this menu system. Although not required, if
DOSmenu cannot find enough DOS environment variable space to write a menu
command to a DOS variable, then it will not be able to run the command.
Maximum Limits
--------------
Menu files: unlimited
Sub-menus per menu file: 15 (depending on memory available)
Entries per menu: 20
DOS commands per menu item: 10
Rights per menu item: 10
Items per right: 10
Length of menu items: 50
Length of menu rights: 120
Length of menu commands: 80
Length of help lines: 61
Length of screen title: 40
Question length: 70
Active notices per user: 15
Number of lines per notice: 10
Length of notice lines: 70
Metered applications: 100
Startup Options
---------------
DOSmenu is started with the DOSMENU command from within a batch file.
However, within this batch file, you may specify a user ID, a server name
and/or a node address on the DOSmenu command line through parameters issued
to the batch file. This is not normally necessary because DOSmenu picks the
user ID and server name up automatically on NetWare networks and you may
define DOS variables that are identified from within the DOSmenu init file
to determine the active user and active server on stand-alone environments.
Required Files
--------------
The following files are necessary to run DOSmenu:
DOSMENU.EXE The DOSmenu program.
DMUTIL.EXE The DOSmenu utility program. Used to make, edit, compile and
decompile menu files.
DOSMENU.INI The default DOSmenu init file initially made and edited with
DMutil. This file is used to configure your menu system
environment.
DOSMENU.MNU The default DOSmenu menu file initially made and edited with
DMutil. This file is the default menu.
MENU.BAT The startup batch file initially made and edited with DMutil.
Optional Files
--------------
DOSMENU.PER Personal menu kept in user's private directory.
DOSMENU.NTE The default DOSmenu note file initially made and edited with
DMutil. This file holds user notices.
DOSMENU.LOG 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, menu action, active
menu name, and memory available.
DOSMENU.MTR If metering is enabled, this is the central file where the
metering information is kept.
DMQUERY.EXE An external utility that gets and uses batch file input.
DMMETER.EXE An external software metering utility that can compliment the
metering services offered from within the menu system.
DMSAVER.EXE An external screen saver (you may use your own as well).
NOBREAK.EXE Self-extracting file containing a very useful utility that can
help to guarantee security within your menu system with an
approach that is different than the inherent DOSmenu
{r=nobreak} rights option.
Many additional utility programs (see DMBONUS.DOC) and full mouse support are
shipped with the registered version.
QUICK START (3)
==============================================================================
To quickly get the menu system up and running, do the following (check the
documentation later for specifics):
o Copy all DOSmenu files to a permanent home directory
o Change to that home directory
o Run 'DMUTIL /M' to make the default menu files
o Run 'DMUTIL' to setup all menu system files
o Run 'DMUTIL /C DOSMENU.INI' to compile the init file -optional
o Run 'DMUTIL /C DOSMENU.MNU' to compile the menu file -optional
o Move MENU.BAT to a directory in your users' path
o Run 'MENU' to start the menu system
STARTUP BATCH FILE (4)
==============================================================================
As part of the initial file installation performed by DMutil, the file
MENU.BAT will be made in DOSmenu's home directory. MENU.BAT _must_ be moved
to your users' path, but the rest of the DOSmenu files _must_ stay in
DOSmenu's home directory. All users must be able to 'read' this directory.
Here is a commented MENU.BAT:
@echo off ;Cosmetics only
::this batch file must be in users' path
::uncomment variation of next line on networks when you don't want the menu to
:: appear if user is not logged in (especially if MENU.BAT is in LOGIN dir)
REM if not exist f:\public\*.* goto END
::replace %4 on next line only with menu name if not starting with DOSMENU.MNU
f:\login\dosmenu /batch %1 %2 %3 %4 %5 ;Point to/run DOSmenu {with parameters
; if desired (not required on NetWare)}
::quitting the menu system? ;255 passed with F10 or 'goto END' passed
if errorlevel 255 goto END ;If so, then leave loop and batch file
::run variable set by DOSmenu (DOS command or temporary batch file name)
%_dmcmd% ;The DOS command or temp batch file name
::do it again ;Keep running the batch file (and the menu
menu %1 %2 %3 %4 %5 %_dmmnu% /rerun ; system) and until the system is stopped
:END ;Place to go to when quitting
Be cautious about changing this batch file!
Parameters are normally only needed if you are not running on NetWare and have
not set the names of the user ID and server name variables to be used by
DOSmenu in the menu file and you are not running in a stand-alone environment.
The DOS variable _dmcmd is loaded as either the actual menu command or as a
temporary batch file path and name made by DOSmenu when it combined the
commands for the selected menu item.
The _dmmnu DOS variable holds the name of the current 'main menu' and an
array to get back to the last sub-menu and item.
Quitting will move to the end of the batch file, thereby stopping the system.
You can place a quit command on your user's menu to do the same thing by
defining a single DOS command for that menu item as 'goto END'.
COMMANDS (5)
==============================================================================
F1 HELP Brings up context sensitive help. Press it anytime.
F2 DOS Performs any DOS command from within the confines of the menu
system. This key may be password protected.
F3 VIEW DOS Views the last DOS screen. If quit timing is enabled and an F2
password is enabled, this option is password protected.
F4 VIEW NOTE Views any notices that were directed at a user, and any new
notice that may have been added since the last time they
accessed the note file.
F5 PERSONAL Load user's personal menu file. This option may be disabled.
F6 EDIT PER Edit personal menu file. The option may be disabled.
F7 VIEW MENU Views the commands of the highlighted menu item.
F8 VIEW MTR Views the active software meter file, showing actual concurrent
usage of metered applications. If quit timing is enabled and
the F9 password is enabled, this option is password protected.
F9 ADMIN Edits all of the menu system files at one time, interactively,
while running the menu system. DMUTIL.EXE must be in DOSmenu's
home directory. This key may be password protected.
F10 QUIT Quits DOSmenu (and quits the startup batch file by passing a
255 errorlevel). This key may be password protected.
ESC PREVIOUS Backs up to the previous menu or cancels a question.
MOUSE (registered version only) Normally, the left mouse button
simulates the Enter key and the right mouse button simulates
the Esc key. However, you may also use the mouse to manipulate
the scroll bars, point directly to menu items and then click on
them to run them.
SETUP (6)
==============================================================================
DOSmenu has two setup phases, the initial default file creation and then
configuration.
DEFAULT FILE CREATION
=====================
After moving all DOSmenu files to a permanent home directory, and then moving
to that directory, you must run DMUTIL /M to make the initial menu file set
consisting of DOSMENU.INI (the init file), DOSMENU.MNU (the menu file shell),
DOSMENU.NTE (the note file) and MENU.BAT (the startup batch). DOSmenu must
run from a batch file for the reasons discussed below. We will use the name
MENU.BAT throughout this documentation, however it may be renamed. It must be
found in the users' path.
CONFIGURATION
=============
After DOSMENU.INI is created, you need to edit it in order to set the
environment for your specific system. You may edit this file with DMUTIL.
The init file contains various options and switches that control how DOSmenu
(and DMutil) will work for you and your users. These are discussed here.
[DMutil]
Activate mouse=
---------------
Default=yes. With the registered version, you may optionally engage use of a
mouse (if a mouse driver is available) or disengage use. Disengaging can be
useful if your system takes a long time to reset the mouse driver when loading
DOS mouse-aware programs.
DOSmenu Startup Batch File=
---------------------------
Default={directory you built files in originally}. This option allows DMutil
to load your startup batch file when loading the other menu system files with
the DMUTIL command. After moving the MENU.BAT to your users' path, you should
enter the path and name of the file here.
[Interface]
Use Mouse=
----------
Default=yes. With the registered version, you may optionally use your mouse
to manipulate your menu. A mouse driver (like MOUSE.COM) must be loaded on
the work station to enable mouse support.
Desktop Color=
--------------
Default=21(for color machines) or 70(for monochrome machines). This number
determines the color of the menu system's desktop background. The first
number represents the foreground color, and the second number represents the
background color. If you enter only one color, then it will represent the
background color and the foreground color will be 0. Entering nothing or 0 or
00 will disable the desktop background. For example:
71 = white fore on blue back
7 = black fore on white back
0 = no desktop background
The standard MS-DOS colors are:
0=black 1=blue 2=green 3=cyan 4=red 5=magenta 6=brown 7=white
Screen Saver Time=
------------------
Default=0. 0 disables screen saving.
Screen Saver File=
------------------
Default=[path]dmsaver. You may use your own saver as well. Keep in mind that
using a screen saver WILL NORMALLY NEGATE a timed logout system (see below).
Screen Title=
-------------
Default=DOSmenu Menu System. You may place your company name or something
similar here, if you desire. If this item is left blank, then there will be
no information line at the top of the screen. This line usually shows the DOS
memory free amount, the Screen Title, and the name of the current menu file.
Support Comment=
----------------
Default=For HELP Please Call Computer Support. This phrase will be shown
blinking at the bottom of the main help window so that your users will easily
know what to do in case they need help. We recommend placing your support
telephone number within this phrase.
[Network]
Using NetWare=
--------------
Default=yes. This switch tells DOSmenu whether it should make NetWare API
calls to determine the actual user and server in force when it is running.
These two pieces of information can be overridden by you whenever you wish by
one of the following methods:
Set DOS variables equal to the current network user and file server and
then define those variables for DOSmenu (below). This option is useful
when running on non-NetWare networks. For instance, if you set the DOS
variable _USER to the actual user ID in the network login script, then it
will be found and used by DOSmenu if you enter _USER as the user DOS
variable with the option below.
Non-NetWare DOS User Var=_user
Non-NetWare DOS Server Var=_server
Or you may place them directly in the batch file, like
path\dosmenu /batch /u:%_user% /s:%_server%
or type them when running the batch file, like
menu /u:_user /s:_server
The priority DOSmenu uses to obtain this information is as follows:
1. Actual NetWare information if NetWare=yes and on a Novell network.
2. Already set DOS variables (overrides 1.).
3. Command line parameters (overrides both 1. and 2.).
Non-NetWare DOS User Var=
-------------------------
Default={nothing}. As discussed above, this option allows DOSmenu to find the
user ID for the person running the menu system when not on a NetWare network
(or when you decide to override the API method).
Non-NetWare DOS Server Var=
---------------------------
Default={nothing}. As discussed above, this option allows DOSmenu to find the
server name for the person running the menu system when not on a NetWare
network (or when you decide to override the API method).
Any-Network DOS Node Var=
-------------------------
Default={nothing}. This option allows DOSmenu to use the work station network
node address as a determinant as to whether a menu item will be available or
not.
Private Directory=
------------------
Default=c:\. DOSmenu will write an on-the-fly batch file to run menu commands
embedded within the menu file _only_ when there is more than one command for
the chosen menu item. When this happens, this batch file must be written to
an area where the user has write rights.
Typically, on networks, a 'private' area is mapped for each user on login as
their personally mapped drive (actually just a network directory based on the
user's ID) on the server. In such a case, you should place that location
here. An example might be H:\ if you had performed a
MAP ROOT F:\USERS\%LOGIN_NAME to H:\ (on a Novell network).
If no such directory is mapped or used on your network, then we suggest using
C:\, which should always be private to the user for every session.
If you would rather have all users write their on-the-fly batch files (when
necessary) to the same location, that is OK as long as you are on a Novell
network because DOSmenu also knows and uses the actual user connection number
as part of the batch file name, e.g., _DMBT4.BAT, where this user is using
connection number 4. In this case, simply define the Private Directory as any
one place on the network where all users have 'write' rights.
Remember, this batch file is only written if more than one DOS command is
defined as part of a chosen menu item. You may actually specify two private
locations for this option, like
Private Directory=h:\,c:\
to help take care of special cases like when a user does not have the proper
network mappings.
On a stand-alone environment, you do not need to define a Private Directory,
and in that case, any temporary batch files will be written to DOSMENU.EXE's
home directory.
Allow Personal Menus=
---------------------
Default=yes. If yes, then each user may maintain, run and edit a personal
menu file, DOSMENU.PER, that resides in their defined private directory (see
above). User's must have WRITE rights to this directory.
Force Personal NoBreaks=
------------------------
Default=yes. If personal menus are allowed, this protects the security of
your system by forcing all menu items on the user menu to be run with the
{r=nobreak} right set. This effectively eliminates the possibility of a user
breaking out of a batch file or DOS command by pressing ^C or ^Break.
Strongly recommended. However, understand that any batch file that uses an
embedded NetWare search mapping command will not be honored in this case. The
alternative is to use the included NOBRK TSR utility.
[Security]
F2 Run DOS Password=
--------------------
Default={nothing}. If filled in, DOSmenu will require this password before
allowing users the option of composing and running their own DOS commands,
just as they would at the DOS prompt. If security is a factor, place a
password here and later compile the DOSMENU.INI file with
DMUTIL /C DOSMENU.INI.
When F2 is pressed, an answer box will pop up asking the user for a DOS
command. Also for safety reasons, if a user enters nothing or a command that
has the word 'command' anywhere within it, then it will be ignored. This is
to prevent a user from actual going to DOS by loading another copy of
COMMAND.COM.
F9 Admin Password=
------------------
Default={nothing}. If filled in, DOSmenu will require this password before
allowing anyone to edit the menu system files. If security is a factor, place
a password here and later compile the DOSMENU.INI file with
DMUTIL /C DOSMENU.INI.
If no password is defined, then anyone can edit your menu system.
This password is also queried by DMutil in case someone tries to run DMutil
from DOS.
F10 Quit Menu Password=
-----------------------
Default={nothing}. If filled in, DOSmenu will require this password
before allowing users the option of quitting the menu system.
If security is a factor, place a password here and later compile the
DOSMENU.INI file with
DMUTIL /C DOSMENU.INI.
If no password is defined, then the user will be prompted to be sure they wish
to quit the menu system.
Use Software Metering=
----------------------
Default=no. When enabled, the METER right will be enabled in your menu
system. You will be able to meter any software application your users employ,
which can help keep you and your company out of trouble. See the Software
Metering Service section for specifics.
Meter File=
Default={nothing}. If metering is enabled, then a path and filename must be
entered here. This file will become the central metering file for your system
(on the current server). Users must have write and erase rights for this
file.
Use Logging=
------------
Default=yes. When enabled, the user's log file is appended to every time a
user performs a menu action. Included statistics are: user name, node
address, server name, date, time, menu action, active menu name, and memory
available. The file is normally written to the user's defined private
directory.
Central Logging=
----------------
Default=no. If yes, then one log file for all users is written to the file
specified in the next entry.
Central Log File=
-----------------
Default={nothing}. Where to write central log information to, if activated.
Users must have write rights to this area.
Timed Quit Menu Time=
---------------------
Default=0. This option, if enabled, allows you to control your user's allowed
time of inactivity before forcing them off of the network (or simply out of
the menu system). On our network, connections are at a premium, so we use
this option to remove users from the network after 30 minutes of inactivity on
their part. We do this by entering the command 'logout' for the Quit Menu
Command (discussed below). Entering 0 or nothing disables this function.
Timed Quit Menu Command=
------------------------
Default=logout. If automatic quitting is enabled via the option above, then
whatever is placed in this option will be run when the automatic quit is
invoked. Obviously entering 'logout' will log the user out of a Novell
network. If you simply wanted to remove a user from the menu system at
automatic quit, then enter 'goto end' here. This in affect will take the user
out of the MENU.BAT internal loop that normally keeps DOSmenu going.
[Global Keys]
AltF? Text= (where ? = 1 to 5)
-----------
Default={variable}. These lines determine what text will show by a global
alternate function key.
Alt? Cmnd= (where ? = 1 to 5)
----------
Default={variable}. These lines hold the DOS command for the appropriate
global alternate function key. These commands are alsways shown, when
defined, and are run with the {r=nobreak} option, just like F2 DOS commands.
You may place a '@' within a command to prompt for a question. If no commands
are defined, then pressing the Alt key will not show them on screen.
After defining the above switches/options, you are ready to set up
DOSMENU.MNU which contains the actual menus that will be used by the menu
system.
MENU DEFINITION (7)
==============================================================================
There are two conventions used to control the menu or menus a user gets when
running the menu system, server-based and rules-based. These conventions are
much more difficult to explain than to actually use, so we will briefly both
describe and show example code, offset with ';-----', throughout.
SERVER-BASED CONVENTION
=======================
Approaching the DOSMENU.MNU menu file from the top down, the system can be
thought of as a server-based system. This can become quite robust, as in our
eight-server domain or quite simple, as in the case of a single server or a
stand-alone environment. Basically, the file is divided vertically into
server sections that are defined by the actual server name. An all
encompassing name is also allowed and it is called ALL. Each server name, and
the ALL choice, must start at the beginning of a line with a colon, e.g.,
:OUR_SERVER or :ALL. You can have more than one section defined with the same
server name, such as an :ALL section at the beginning and at the end allowing
you to show certain all-encompassing menu items at the top and also at the
bottom of each user's menu. Here is a segment of a menu definition showing
the vertical server-based method:
;-----
%Main Menu
:ALL
Word Perfect
wp
:MAIN_SERVER
Paradox
paradox
Lotus 1-2-3
123
:SECOND_SERVER
Proprietary application
ourapp
:ALL
Logout of the network
logout
;-----
In the above example, you can see that a person who is running on the main
server would get the following main menu:
_____
Word Perfect
Paradox
Lotus 1-2-3
Logout of the network
_____
while a person running on the second server would get:
_____
Word Perfect
Proprietary application
Logout of the network
_____
Note that any menu items (and sub-menus and their items) may be accessible
depending upon which section they are placed under, subject to the next
convention of discrimination, rules-based, which is discussed below.
RULES-BASED CONVENTION
======================
A secondary, more powerful means of segregating the menu file between users is
the rules-based method. Whereas the server-based convention may be viewed as
vertical, think of the rules-based convention as horizontal. In other words,
after deciding which server a user is using, we then must decide what the
rights of that user are, and this convention does just that. Let's discuss
each method in detail.
All rights assumed
------------------
Rule = no rule line 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 if it is under the correct server name (or
ALL), 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). This method is, of course, exactly what you would
normally use if you were on a stand-alone environment.
;-----
Paradox
paradox
;-----
User gets item if it is available, period.
Directory rights
----------------
Rule = {d=directory name or d=directory name1,directory name2 ..}. DOSmenu
will look to see if any of the listed directories 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.
;-----
Paradox
{d=c:\apps\paradox}
paradox
;-----
User gets item only if F:\APPS\PARADOX is 'visible' in the user's environment.
File rights
-----------
Rule = {f=file name or f=file name1,file name2 ..}. DOSmenu 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.
;-----
Paradox
{f=f:\apps\paradox\paradox.exe}
paradox
;-----
User gets item only if F:\APPS\PARADOX\PARADOX.EXE is 'visible' in the user's
environment.
Server rights (NetWare only unless DOS variable/command line parameters used)
-------------
Rule = {s=server_name1 or s=server_name1,server_name2 ..}. Do not confuse
this method with the server-based convention. 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.
;-----
Paradox
{s=main_server}
paradox
;-----
User gets item only if the user is logged into and running on MAIN_SERVER.
Group rights (NetWare only unless DOS variable/command line parameters used)
------------
Rule = {g=group_name1 or g=group_name1,group_name2 ..}. Normally you define
groups to group certain users that you can later assign trustee rights to,
thereby giving them access to certain programs. This method allows you to use
that work when discriminating in your menu system. There is an advantage
here, however, in that even if you do not bother with trustee rights and your
network is fairly open, DOSmenu will act like it is all set up just right. In
other words, DOSmenu doesn't care about the actual rights; it only cares about
whether the user is in the group name or group names that you tell it. If
not, then the user does not get the menu item displayed (and therefore cannot
run it).
;-----
Paradox
{g=paradox}
paradox
;-----
User gets item only if a member of group PARADOX.
User rights (NetWare only unless DOS variable/command line parameters used)
-----------
Rule = {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 and the server-based convention allows it).
;-----
Paradox
{u=joeb}
paradox
;-----
User gets item only if his user logon ID is JOEB.
Node rights (DOS variable/command line parameter is required for this right)
-----------
Rule = {n=node_address or n=node_address1, node_address2 ..}. This method
takes the discrimination down to the actual user's work station. If the node
address is the same as that of the work station, then the user gets the item
on their menu (if any other specified rights are also approved and the
server-based convention allows it).
;-----
Paradox
{n=fa164505}
paradox
;-----
User gets item only if his work station's address is FA164505.
You must pull the work station's node address to DOS by setting it to a DOS
variable from within the network's initial login script. Only then can you
check for it from the menu system.
Environment rights
------------------
Rule = {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.
Today rights
------------
Rule = {t=su,mo,tu,we,th,fr,sa}. This right tests to see if the current day
is equal to the day specified.
Date greater than rights
------------------------
Rule = {>=MM/DD/YYYY}. This right tests to see if the current day is greater
than the specified date (must be in this format).
Date same as rights
-------------------
Rule = {==MM/DD/YYYY}. This right tests to see if the current day is the same
as the specified date (must be in this format).
Date less than rights
---------------------
Rule = {<=MM/DD/YYYY}. This right test to see if the current day is less than
the specified date (must be in this format).
Password rights
---------------
Rule = {p=password where password is any alphanumeric, non-case sensitive,
from 1 to 10 characters long}. Placing a password on a menu item means that
when the user selects this item (no matter what type it is - command or
sub-menu), the user will be prompted for the correct password.
;-----
Paradox
{p=restrict}
paradox
;-----
User gets item only if he or she can answer the password prompt with RESTRICT.
Question rights (not really a 'right')
---------------
Rule = {q=your question that demands a yes/no answer?} This method simply
pops up your question and asks for a Yes or No answer. If the answer is no,
then the item will not be run.
;-----
Paradox
{q=Are you sure?}
paradox
;-----
Software metering rights (not really a 'right')
------------------------
Rule = {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 DOSMENU.INI). Please see the Software
Metering Service section for a complete discussion of this capability.
;-----
W WordPerfect
{m=wp51:25}
f:\apps\wp\wp
;-----
This many item will run as long as less than 25 other users are running it at
the same time.
Meter dot display (not really a 'right')
-----------------
Rule = {x=1 or 0}. Allows you to not display the meter dot by the menu item
or to display it in case you are metering the item externally with DMmeter.
Run rights (not really a 'right')
----------
Rule = {r=nobreak}. This is where you determine whether batch files will be
run with a second copy of the DOS command processor (NOBREAK) or not. This
right is only appropriate when running multi-line commands (which DOSmenu
turns into batch files) or by running batch files; it should not be used
unless batch files are being run (and then it is your choice). One
disadvantage of running NOBREAK is that NetWare search mapping commands
generated within a batch file will not work. Consider the included NOBRK TSR
utility for fool-proof disabling of the ^C and ^Break keys.
;-----
M My batch file
{r=nobreak}
dir \
pause
;-----
;-----
WordPerfect
{r=nobreak}
wp.bat
;-----
Location rights (not really a 'right' -for notices in note file only)
---------------
Rule = {r=one_to_three_letters}. You may optionally place this right on a
notice to set the location of it on the screen, like
;-----
{l=tl}
A note
;-----
where T=top, L=left, B=bottom, and R=right, N=noise and F=Flash title.
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 separated with a ';'.
For example, you can place both a server (s=) method and a group (g=) method
on the same menu item, like:
;-----
Paradox
{g=paradox} {s=server1}
paradox
;-----
Here, it is read as member of paradox group _AND_ on server1.
;-----
Paradox
{g=paradox;s=server1}
paradox
;-----
Here, it is read as member of paradox _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 {g=paradox} means if the
current user is a member of group paradox, then display the menu item;
{g=!paradox} means display the item only if the current user is NOT a member
of group paradox (they are ORed only within each set of braces {}).
You may use spaces instead of commas. The syntax {g=group1,group2} is the
same as {g=group1 group2}.
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:
;-----
P Paradox
{g=paradox} {u=joe,jim;n=fa164505} {s=!server2}
;-----
will only show on the menu if the user is a member of the PARADOX group _AND_
the user is JOE _OR_ JIM _OR_ the node address is FA164505 _AND_ the user is
not on SERVER2.
TESTING YOUR MENU
=================
After you have placed a lot of restrictions on your menu items, you may find
it frustrating to see what the final outcome of an item looks like. There is
a way around this.
Enter a bogus user id and server name from the command line. For instance, if
you reside on SERVER1 but wish to check the appearance of SERVER2's menu, then
enter the startup batch file with the command
MENU /U:USER_ID /S:SERVER2
where user_id is the name you wish to check for SERVER2. You can do this for
all of your servers and any user.
MENU RULES (8)
==============================================================================
The syntax for the menu file requires certain conventions. In most cases,
DOSmenu will issue an error message if it has trouble interpreting the file
because of a syntax violation of one of the below described rules. If you get
stuck in an error loop within the batch file, press Alt-F10 at the read error
message window to quit.
RULES
=====
Main menu name
--------------
The first line of the file must be the main menu's name, starting with a
percent symbol '%'. You can optionally place the starting x and y coordinates
of the menu window after the menu name, like: %Main Menu, 5, 10. This means
the upper left corner of the menu will be 5 columns from the left edge and 10
rows from the top.
Server sections
---------------
There must be at least one server name before any menu items, unless
operating in a standalone environment. In a network environment, use :ALL, as
a minimum, just after the main menu title and the one REQUIRED blank line.
Comments
--------
Any line starting with a semi-colon ';' is a programming comment only.
Blank lines
-----------
Blank lines are only allowed (and, in fact, REQUIRED) before server sections
and menu titles. See the Menu File Example section for a properly formatted
file.
Menu action character
---------------------
The first letter of a menu item will always be highlighted and will be
searched when the used presses a key to move to a particular menu item. It
may or may not be part of the first word of the menu item. For example,
Lotus 1-2-3
and
L Lotus 1-2-3
offer the same result. It is a cosmetic choice that you must make. Of
course, you could also use
1 Lotus 1-2-3.
Indenting
---------
All server name lines and menu item lines must NOT be indented. All help
lines, rights lines and DOS commands MUST be indented at least one space. A
tab character is allowed for the indentation.
Rights line length
------------------
The maximum length from the beginning of the rights ({}{}..) line from
beginning to end (not including spaces or beginning tabs) is 80. You may have
more than one rights line per menu item for convenience, put there character
count must all add up to 80 or less. (You may only have one rights line per
notice in the note file.)
Parameters
----------
Single-command menu items may be setup to ask the user for a parameter prior
to actually running the command associated with the menu item. This is not
allowed for multi-command menu items. Place a question mark '@' at the exact
location you wish to add input to the command. Here are some examples:
dir @ /p
chkdsk @:
format @: /u
For multi-command items and multi-response items, use the DMquery syntax.
Sub-menu names
--------------
All sub-menu names, both when called as a command and when entered as a
sub-menu title, must start with the percent symbol '%'. There MUST be a
blank line before the sub-menu name. Sub-menus must come somewhere _after_
the menu item that calls them.
Help lines
----------
Help lines for each menu item, if used, must be indented and start with a
number symbol '#'. There can be a maximum of one help line per menu item.
NOTES
=====
You may rename DOSMENU.MNU to another name or copy it to another menu file
because DOSmenu will run any menu file that you have as long as you
specify that file name on the command line. Note that the .MNU is assumed.
No other extension is allowed.
MENU [/U:USER1] [/S:SERVER1] MYMENU.MNU
and
MENU MYMENU
will both attempt to load MYMENU.MNU from DOSmenu's home directory (where all
menu files MUST be located).
LOADING ADDITION MENUS
======================
You may switch menu files from within the menu system by LOADing them or
/MENUing them. This is accomplished by placing the /LOAD MENU_FILE (specify
NO path) or /MENU MENU_FILE (NO path) as the first and only command line for a
menu item, like:
;-----
Support Menu
/load support.mnu
Word Perfect
wp
;-----
Here, if Support Menu is chosen, then the system will load the SUPPORT.TXT
menu file from DOSmenu's _home_ directory to temporarily replace the active
menu file. You may do this an unlimited number of times. After a command is
run, the original main menu reloads.
To prevent the original main menu from reloading, use /MENU. This command
forces the menu to become the permanent new default main menu. If you wish
users to have the option of going back to the original menu later, you will
have to give them that option with another /MENU command in the new menu,
like:
;----
M Main Menu
/menu dosmenu
;----
SUB-MENUS (9)
==============================================================================
Sub-menus are just like the main menu except that their title is the first
line of their definition. The main menu's title is the first line of the
menu file. Their title must start with a percent '%' character, and when
called from another menu, this percent character must be included. Here is an
example:
;-----
%Main Menu
Word Perfect
wp
Utilities
%Utility Menu
Paradox
paradox
;The , 5, 10 is optional and determines x and y menu window coordinates
%Utility Menu, 5, 10
Directory of...
dir @ /p
Check disk
chkdsk @:
;-----
Here, the sub-menu '%Utility Menu' is called from one of the main menu items.
Sub-menus follow the server-based convention along the vertical development of
the menu file. In other words, if a sub-menu is found under the :SERVER2
server name line, then it will not be accessible from a menu calling it which
is situated under :SERVER1. Sub-menus are typically placed at the end of the
menu file under an :ALL alias server name section.
Sub-menus can only be shown on the screen once, yet they can be called from
more than one menu. For example, if the main menu calls sub-menu2 with one of
its items, it is OK for sub-menu1 to do the same thing. However, if sub-menu2
calls sub-menu1 also, and you select sub-menu1 from the main menu, then select
sub-menu2, and then try to select sub-menu1 again, DOSmenu will issue a
non-destructive error explaining that sub-menu1 is already on the work space.
No harm will be done, but you will have to back up to use sub-menu1 again.
There is, of course, no way to call the main menu from a sub-menu because of
the above restriction.
When viewing a sub-menu on the menu screen, a right arrow is added to the
sub-menus menu item text to denote the fact that it is a sub-menu.
COMPILING MENU FILES (10)
==============================================================================
The DMutil program will compile and decompile init and menu files, if desired.
The syntax is:
DMUTIL /C FILENAME
The output compiled file will be the same name. You can then later decompile
the file with the command:
DMUTIL /D FILENAME
Compiling init and menu files is not, repeat not, required. Your users can
run DOSmenu all day long without ever compiling one file. However, there is
one overriding reason why you may wish to consider compiling them after they
have been tested -security. Your menus are much more secure when compiled.
Even smart users will not know what rights you have put where, what the
passwords are, etc. The choice is yours. DOSmenu is smart enough to know
what type of file is being loaded.
TRANSLATING MENU FILES (11)
==============================================================================
You can easily translate NetWare batch files to DOSmenu batch files with the
DMutil utility with the following command:
DMUTIL /T NETWARE_MENU_NAME
The generic default server name flag :ALL will be placed two lines after the
main menu title, giving access to all servers initially.
If your NetWare menu used any @variable"fill-in lines", then you must change
them within the new menu file to DOSmenu's format as it uses the external
DMquery utility for this purpose with additional options.
TEMPORARY BATCH FILES (12)
==============================================================================
Normally DOSmenu simply takes a menu's DOS command and stuffs it into the DOS
variable _dmcmd so that the startup batch file, MENU.BAT, can then run it
after DOSmenu quits. However if their is more than one DOS command, this
approach would not work. Therefore DOSmenu instead will make a temporary
batch file and stuff the name of that batch file to the variable instead.
The location and name of the temporary batch file is as follows:
Name
----
On a Novell network, the name will be _DMBTn.BAT where n is the actual
network connection number taken by the user's work station. This way, a user
could actually run the menu system from two different work stations under the
same login ID without problems.
If not on a Novell network, then the batch file is simply named _DMBT.BAT.
Location
--------
If the Private Directory option in the init file was filled out with a
directory, then the batch file will be written and run from that directory.
If not, then it will be written and run from DOSMENU.EXE's home directory,
which is fine for stand-alone environments.
Notes
-----
Each time a temporary batch file is made, an '@echo off' is automatically
placed at the top of the file, relieving you from having to add that cosmetic
line to every multi-command menu item. Also, 'call ' is placed at the
beginning of every line. This syntax _only_ affects commands that are
actually batch file names, allowing them to return to DOSmenu's temporary
batch file at completion.
Example
-------
If a menu item looked like this:
;-----
Word Perfect
f:
cd\apps\wp51
wp
h:
cd\
;-----
then the corresponding batch file would look like this:
call @echo off
call f:
call cd\apps\wp51
call wp
call h:
call cd\
DOS ENVIRONMENT VARIABLES (13)
==============================================================================
DOSmenu uses up to seven DOS variables to make the system work without _any_
overhead; user ID, server name, workstation node address, command for a
selected menu item, last time the DOSMENU.NTE file was changed (for noticing),
software metering application, and name of the last 'main menu' used.
The node address variable is always 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.
The user ID and server name variables are only needed if you are not running
on NetWare and are not on a stand-alone environment. In this case, you define
and load two DOS variables once during the user login script with the correct
information. In the case of Novell (where this procedure is not necessary)
you would add these lines to the login script:
DOS SET _USER="%LOGIN_NAME"
DOS SET _SERVER="%FILE_SERVER"
where _user and _server and be called anything you wish. You would then add
these two names two the init file so DOSmenu will know what they are called.
It takes care of the rest.
The variable for the menu item command is called _dmcmd and is always used.
When a menu item is selected that has an associated command that is not
another menu (sub-menu command), then DOSmenu either places that command in
this DOS variable if it was a singular command or else DOSmenu makes a batch
file out of the multiple DOS commands for that menu item and then passes the
name of the batch file to this variable. Either way, the MENU.BAT file then
runs that command kept in the variable _dmcmd.
The variable _dmnte is used when you wish to leave dynamic notices to
any and all users.
The menu name variable, _dmmnu, keeps track of the last permanent main menu
used in DOSmenu before quitting to the batch file as well as the last
sub-menu and item selected. This variable is then placed on the re-enter
DOSmenu line of the startup batch file. That is how DOSmenu controls the
/MENU menu command.
The _dmmtr variable holds the meter rights issued with the current DOS
command, if any.
DMquery also uses environment variables. It will use up to 9 variables named
_dmq1, _dmq2, .., _dmq9.
NOTICING (14)
==============================================================================
DOSMENU.NTE is used to leave notices to any and all users -dynamically. Here
you may place notices based on the rights defined for each notice. Each
notice consists of at least two lines; line 1 contains the rights and the
following lines (up to 10) contain the actual notice, like:
;-----
{g=paradox} {s=server1}
Paradox will be down on SERVER1 all day today.
Hopefully it will be up tomorrow...
;-----
Here, only users in group PARADOX on server SERVER1 will get this notice when
they next start up the menu system.
Each user may have up to 15 active notices. Each notice may have up to 10
lines of up to 70 characters long.
You can add and subtract from this section anytime throughout the day. When
a user starts the menu system, and after returning to the menu system, the
notices are checked and shown, if needed. This gives the noticing system a
dynamic quality that can be quite useful to you as an administrator!
The time stamp of the file when the user reads notices is kept in a DOS
variable called _dmnte. This variable is checked each time a user reloads the
menu system after running a command. If you have made a change to the
DOSMENU.NTE file during that time, then the user will see the notices again,
and the variable will be updated.
PERSONAL MENUS (15)
==============================================================================
On a network, each user may use and maintain one personal menu, named
DOSMENU.PER. This menu file is kept and read from the user's defined private
directory.
The F5 key will load (like /LOAD) the menu for the user so he/she can use it.
After running a command from it, DOSmenu will return to the last shared menu.
If the personal menu does not yet exist, a shell will be created for the user
first.
The F6 key allows the user to edit the personal menu with DMutil. All
commands that would grant access to other parts of your network are disabled
while the user is editing the menu. Only the SAVE and QUIT commands are
enabled.
To disallow the personal menu option, set the "Allow Personal Menus" line to
NO in DOSMENU.INI.
If allowed, we recommend setting the "Force Personal NoBreaks" line to YES.
Otherwise, a user may inadvertently set up a DOS command like "dir /p" or
setup a DOS batch file (by entering two or more commands for a menu item) that
they may later be able to break out of with ^C or ^Break. Setting nobreaks to
yes prevents this from ever happening. One disadvantage to using this
approach is that any NetWare search mappings contained within a batch file
will not work. An alternative approach would be to set nobreaks to false and
instead use the included NOBRK TSR utility, which ensures complete nobreak
protection without affecting network batch file-based search mappings.
SOFTWARE METERING SERVICE (16)
==============================================================================
DOSmenu now 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 WordPerfect,
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 DOSmenu 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 the DOSMENU.INI file:
Use Metering=yes
Metering File=f:\share\dosmenu.mtr (or something like that)
Users must have WRITE and ERASE rights to the above area.
2. Place the meter right on those commands you want metered, for example:
;-----
W WordPerfect
{m=wp51:25}
f:\apps\wp\wp
;-----
will meter the use of F:\APPS\WP\WP.EXE for all accesses from DOSmenu. If
25 instances are already in use (in this example), then DOSmenu 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 WP51, 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).
Of course anyone accessing WP.EXE from outside of the menu system will not be
metered in this way. See the DMMETER UTILITY section to find out how to
meter software run 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 meter rights for each item.
Note: RECOMMEND DELETING THIS FILE 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
meter file periodically, perhaps at night before or after your backup. On the
other hand, if a user gets kicked out of a metered application but returns to
the menu system, the count will remain accurate.
Be careful when looking at your meter file. The recommended way to view it is
with the F8 command from the menu itself. However, grabbing an instance of it
with DMUTIL [PATH]METER_FILE_NAME is safe as long as you DO NOT save the file.
Do not look at the file with file viewers that do not cleanly close the file
after retrieving it, else other users will not be able to update it (and
thence your metering numbers will be inaccurate as long as they are in the
metered application). Vern Buerg's shareware LIST.COM program IS a safe
viewing program for this purpose. The Norton Commander viewer is NOT.
This metering option is also quite useful when trying to get the 'pulse' of
what users are doing on your network.
A small dot (·) is placed just to the left of all menu items when metering has
been defined for that item and metering is turned on and a metering file has
been defined.
DMUTIL MAINTENANCE UTILITY (17)
==============================================================================
COMMAND PARAMETERS
==================
The DMutil program keeps all of your menu maintenance requirements in one
utility. Anything you need to do to your menu system can be done with DMutil.
Here is the command syntax:
DMUTIL ?
DMUTIL /M|T|C|D FILENAME
DMUTIL
DMUTIL FILE|SPEC [[FILE|SPEC] ..]
DMUTIL /L [USER_ID]
where:
? = DMutil and system installation quick help
/M = Makes default DOSmenu batch, menu, init, and note files
/T = Translates NetWare menu files
/C|D = Compiles|Decompiles DOSmenu init, menu, or note files
= Edits all menu system files at once
FILE.. = Edits any number of text file(s) up to 64K in length each
/L = parses specific user ID entries from the central log file, if used.
THE MENU FILE EDITOR
====================
The editor is a simple ascii text editor that has specific help screens to
give you some on-line help on all menu file types. In actuality, any ascii
editor can be used to edit the startup batch, init, menu and note files (if
they have not been compiled).
It's operation is self-explanatory, but a few items are worth mentioning:
o Edits files with any DOS attribute set and then resets those attributes
afterwards.
o Automatically decompiles - edits - recompiles your menu files for you.
o Can edit many text files at once with commands like \WINDOWS\*.INI, etc.
o Can show tabs and spaces in a file on screen.
DMQUERY BATCH INPUT UTILITY (18)
==============================================================================
DMquery is a utility that can be used to provide input for batch files made
with DOSmenu.
Here are the command line parameters:
DMQUERY n [/R|U|E|Danswer]
where
n = A number from 1..9
/R = Input is required (an answer must be given)
/U = Input will be forced to upper case
/E = Input will be echoed to the screen afterwards
/Danswer = Input default answer will be 'answer' (must be one word only)
The DOS variable '_DMQn' is temporarily used. DMquery may be run from DOS or
a DOS shell; however, it must be queried for and acted upon within the _same_
batch file, like:
@echo off
echo What is your name? {your question}
dmquery 1 /r/dJoe {answer required, put in var _DMQ1, def=Joe}
if errorlevel 255 goto.. {not enough env space? -optional}
echo %_dmq1% {use answer variable _DMQ1 as you wish!}
Here is an example DOSmenu menu item:
;-----
D Directory
echo Directory of what?
dmquery 1
echo Switches (/w, /p, etc)?
dmquery 2
dir %_DMQ1% %_DMQ2%
pause
;-----
DMMETER METERING UTILITY (19)
==============================================================================
This utility can optionally monitor your software usage from outside of the
menu system. It does the same thing DOSmenu does when you activate the meter
right for a menu item, except it does it from within DOS batch files.
Here are the command line parameters:
DMMETER APP[:LICENSE_COUNT] {before batch command}
and
DMMETER {after batch command}
Here is an example batch file:
@echo off
[path]dmmeter wp51:25 ;add instance of wp51 app to meter file
if errorlevel 1 goto END ;if too many instances already, don't do it
f:\apps\wp\wp ;run the app
[path]dmmeter ;subtract instance of wp51 from meter file
:END
DMMETER.EXE must reside in DOSMENU.EXE's home directory, and DOSMENU.INI must
also be present in DOSMENU.EXE's home directory.
If an errorlevel 1 is returned, an error window pops up to tell the user
of the problem and asks them to try again later.
To reset a problem app (one that locks machines now and then?) to 0 in the
meter file (instead of deleting the entire file) run DMmeter with the reset
switch, like:
DMMETER /RESET APP
Example:
dmmeter /reset wp51
To view concurrent usage of metered software applications from the DOS prompt,
like F8 inside the menu, use:
DMMETER /VIEW
EXAMPLE MENU FILE (20)
==============================================================================
The below network menu file example is listed with a generous helping of legal
and illegal comments. Note that comments must commence only at the start of a
line and NOT at the middle to end of a line even though we use it here to
better comment the code for you.
;The menu name for this overall main menu below.
%Our Network Menu, 10, 5 ;numbers optional: 10 = x, 5 = y on screen
; placement of upper left corner of menu window
;This server section means any server and/or a stand-alone environment.
;These commands will be at the top of every user's menu.
;Note the required blank line before the :SERVER_NAME line
:ALL
M Mail
;All members of EMAIL_USERS will get the Mail menu item.
{g=email_users}
;The help line for this item (shown at the bottom of the screen)
#Send and receive mail to and from other users
;If selected, the command/permanent batch file EMAIL will be run.
email
;This section is for CENTRAL server users only.
:CENTRAL
P Paradox
{g=support,paradox} {p=restrict}
#Database program
f: ;A multi-command item that
cd\apps\paradox ; generates a temp batch file.
paradox ;
W WordPerfect
{g=wp_central} {m=wp51:25} ; metered for 25 instances
#Word processor
f:\apps\wp51\wp
;The next item ask a yes/no question first.
C Check printing
{u=check_printer} {q=Are you sure you want to print checks?}
#Print all due checks to the upstairs printer
checkprt
I INSAPP
{g=insapp_users,support;u=adm} {s=server1}
#Our main database application
ins
S Support Menu ;Another complete menu file which is called
/load support ; with this line.
S Accounting Menu ;Another complete menu file which is called
/menu acctng ; with this line and becomes the default menu.
;This section is for BRANCH_ONE server users only.
:BRANCH_ONE
A Central connection
{g=awlan}
#Connect with the home office by modem
connect
W WordPerfect
{g=wp_branch}
#Word processor
wp
;This server section means any server and/or a stand-alone environment.
;These commands will be at the bottom of every user's menu.
:ALL
U Utility Menu
#Various utilities
%Utility Menu
B Backup Server Menu
#Backup options
%Backup Server Menu
L Logout of network
{q=Are you sure?}
#Log out of the network
logout ;You could also enter 'goto end' to simply quit
; the menu system, if desired.
;Remember to place a blank line before all %SUB-MENU NAME lines
%Utility Menu, 5, 10 ;Display at xy coords 5 and 10 on screen
P Change your network printer
capture @ ;This command asks a question first.
D Directory of...
#Obtain a directory listing
dir @ /p ;This command asks a question first.
D Directory of (another way)...
echo Directory of what?
dmquery 1 ;DMquery external batch utility
echo Switches (/w /p, etc)?
dmquery 2
dir %_dmq1% %_dmq2%
pause
%Backup Server Menu
D Daily backup procedure
bud
W Weekly backup procedure
buw
