home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 11 Util
/
11-Util.zip
/
MENUMIN3.ZIP
/
READ.ME
< prev
next >
Wrap
Text File
|
1992-12-31
|
5KB
|
111 lines
This is my moddification of the basic cdd.sys program to allow for
the use of a menu/security system to select the next step in the process.
This zip file should contain the following files.
read.me ----- the file you are reading
config.* ----- sample of the 3 config files that I use, you
may use these as a guide in setting up yours
cdd.sys ----- the new cdd.sys
cdd.c ----- the modified cdd.c source
menumini.exe ----- the program that cdd.sys executes instead
cmd.exe
menumin.cmd ----- a special .cmd file that allows you to alternate
shells from a system that is already booted. This
.cmd file passes a simple parameter that tells
menumini.exe to bypass security from a running
system as it is somewhat redundant.
secpass.exe ----- the security/password maintenamce program
secu.dat ----- security/password file
The security file is currently expected to be in a sub-directory
named \userdir\usersys that has to be on the boot partition.
All the other files on the original cdd system remain the same.
Although I use this system for loading alternate shells, it really
can be used to alternate different config.sys files at boot up. Here
are a few things that you must keep in mind.
The first entry in the config.sys files is a rem entry and is
necessary for proper operation of menumini.exe. Basically the
system keys on this rem statement to determine what environment
is in the process of booting up. This entry MUST be the first
entry in your config.sys
Description of the first entry in the config.sys
examples:
1 2
12345678901234567890123456 general comment not used by menumini ************* config name
rem FULL WPS-aaaaaaa11005N used for the full work place shell config.001
rem 1.0 SHEL-bbbbbbb21005N used with to OS/2 1.0 shell config.002
rem MENUMAST-ccccccc31005N used with a special menu shell config.003
The names config.001, config.002, and config.003 are necessary and these
names must be used in order for the menumini system to work properly.
pos 1-4 Identifies this as a remark. -- must be rem
pos 5-20 Description of the shell being loaded. -- can be anything
This is the description that appears
on the menu.
pos 21 The number of the shell being loaded. -- must be 1,2 or 3
The system is currently set up to handle
3 different shells and position 21 is used
to make or switch a selection.
pos 22-23 The number of delay seconds for the auto boot screen.
The default is 5 seconds and if this entry is
left blank that is what you will get. An entry
of 00 will bypass the auto boot display screen.
All others will be the # of seconds to delay
before auto booting.
pos 24-25 The number of seconds to wait for a response when
the menu is displayed. Blank or zero then use the
default of 10 seconds all others is the delay time.
pos 26 Security flag. A 'Y' in this position activates the
security processing. Any other value bypasses security.
If you don't want the security feature leave this blank.
The config file names are critical and must be as shown, config.001,
config.002, or config.003. Obviously one of these three will be the
config.sys that is being loaded and the other 2 will have their
original name. For example if you were running with the full work
place shell with my examples you would have the following config files.
config.sys ---- this is the currently active config file
config.002 ---- 1st alternate
config.003 ---- 2nd alternate
Look at the config file samples to get some idea of how I use this
system.
The cdd.sys may be placed anywhere on you HD as long as it is pointed
to properly in the config.sys.
All .cmd and executables must be somewhere that your path statement
pointing to.
The secu.dat must be in a sub-directory named \userdir\usersys that
is on your boot partition.
The security system is now set up for 2 users:
The first usercode is the number 1 with no password and the second
usercode is master with a password of master. Use secpass.exe to
add or delete different users. The system will allow up to 102
different users. Actually this is a subset of a more comprehensive
security system that I scaled down somewhat for this use.
If you have any questions or difficulties let me know through a msg
in the OS/2 echo of Fidonet.
bill oconnor