home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-386-Vol-2of3.iso
/
b
/
bootr03.zip
/
BOOTR.DOC
next >
Wrap
Text File
|
1993-02-20
|
11KB
|
288 lines
BOOT'R v0.3ß
Copyright 1993
by
Stevenson Technical Services, Inc. (STSI)
108 Second Avenue West
Bertha MN 56437-0297
Phone: (218) 924-2050
FAX: (218) 924-2050 (Ext. 11)
The Bertha BBS: (218) 924-2060
■─────────────────────────────────────────■
│ Disclaimer: │
■─────────────────────────────────────────■
Users of BOOT'R must accept the following disclaimer of warranty:
"BOOT'R is supplied as is. The author disclaims all warranties,
expressed or implied, including, without limitation, the warranties of
merchantability and of fitness for any purpose. The author assumes no
liability for damages, direct or consequential, which may result from the
use of BOOT'R."
■─────────────────────────────────────────■
│ Registration: │
■─────────────────────────────────────────■
BOOT'R is distributed under the shareware concept. You may try BOOT'R
for a period of two weeks. After this period, you must either discontinue
using BOOT'R, or register it. For registration information, please read the
REGISTER.DOC file included with BOOT'R.
■─────────────────────────────────────────■
│ Technical Support: │
■─────────────────────────────────────────■
Technical support is available to BOOT'R users via The Bertha BBS. New
versions of BOOT'R will be posted here as soon as they are available. The
Bertha BBS uses a U.S. Robotics Dual-Standard, which is capable of V.32bis,
V.32, HST, and 2400 baud connect speeds. The access number for The Bertha
BBS is (218)-924-2060. Technical support questions should be addressed to
SYSOP.
■─────────────────────────────────────────■
│ What is BOOT'R? │
■─────────────────────────────────────────■
BOOT'R is a program designed to change a computer's CONFIG.SYS and
AUTOEXEC.BAT files to different configurations, and reboot the machine.
This allows the creation of optimal configurations for each operating
environment. For example, DOS users may want to load certain device
drivers that would give trouble under DESQview. Certain games might
require an exhorbitant amount of free memory, which is impossible to
achieve with many device drivers loaded. With BOOT'R, different
configurations can be used for DOS, DESQview, and many other
configurations. Similarly, some TSRs may interfere with the operation
of specific programs, such as tape backup programs. BOOT'R allows the
creation of an operating environment without these TSRs.
■─────────────────────────────────────────■
│ Why was BOOT'R created? │
■─────────────────────────────────────────■
BOOT'R was created to meet a specific requirement that my business
has for a multiple configuration manager. We need to alter more files
than just CONFIG.SYS and AUTOEXEC.BAT. In our case, optimizing the
SHELL.CFG file is also important. We are also seeing more and more
programs using .INI files to alter their settings. BOOT'R is capable
of changing them too!
■─────────────────────────────────────────■
│ Installing BOOT'R: │
■─────────────────────────────────────────■
Create a C:\BOOTR sub-directory, and extract the BOOT'R files into it.
The files needed are BOOTR.EXE, BOOTR.INI, and BOOTRWBT.COM. The BOOTRWBT
file is a small program that performs a warm-boot on the computer. Do NOT
run this program, unless you want your machine to reboot!
■─────────────────────────────────────────■
│ Using BOOT'R: │
■─────────────────────────────────────────■
BOOT'R operates by using command line parameters. To change to a
different configuration using BOOT'R, you simply specify the desired
configuration on the BOOT'R command line.
The BOOT'R command line structure looks like this:
BOOTR CONFIGURATION TEST
BOOTR - BOOTR should always be the first entry entered on the
command line. All command line entries should be in
UPPER CASE, and should be separated by a single space.
CONFIGURATION - This is the name of the desired configuration. These
configurations are maintained in the BOOTR.INI file.
TEST - This command line parameter is optional, and allows the
configuration files to be changed WITHOUT actually re-
booting the computer. This option is useful to test to
see if the CONFIG.SYS, AUTOEXEC.BAT, and any other files
are being written properly. It is also useful to
verify that the cache is being properly flushed and
disabled, without risking data corruption.
BOOT'R Examples:
BOOTR CPBACKUP
BOOTR DESQVIEW
BOOTR DESQVIEW TEST
BOOTR LANTASTIC
BOOTR NORMAL
BOOTR NOVELL
BOOTR WINDOWS
BOOTR WINDOWS TEST
■─────────────────────────────────────────■
│ The BOOTR.INI File: │
■─────────────────────────────────────────■
The BOOTR.INI file is an ASCII text file, created in the C:\BOOTR
sub-directory. It can be edited with any editor that can create an ASCII
text file. The format of this file is as follows:
[REGISTRATION]
John Doe
XYZ-1234-567
[DELAYS]
PrelogDelay=10
[REBOOT]
C:\PCKWIK\SUPERPCK /F /D
There must be a blank line between each section, but the sections can
be in any desired order. Each statement in a section must be on a separate
line.
The [REGISTRATION] section contains the name of the individual or
company that registered BOOT'R. The name must appear first and the
registration number second. Both of these items are CASE SENSITIVE. If a
valid registration name and number are not entered here, the remaining
items in the ZIPR.INI file will not function.
The [DELAYS] section allows registered BOOT'R users to specify the
length of time that the Prelog screen is displayed. Most users will likely
use PrelogDelay=0, which will force BOOT'R to not display the Prelog screen
at all.
The [REBOOT] section allows registered BOOT'R users to execute commands
or programs prior to rebooting the computer system. This feature is useful
for flushing and disabling a cache, especially when using write-caching.
For each configuration needed, a .INI file must be created in the same
sub-directory as BOOT'R. An example of my WINDOWS.INI file is shown here:
[WINDOWS]
<C:\CONFIG.SYS>
HIDOS=ON
DEVICE=C:\QEMM\QEMM386.SYS NRH DMA=32 ST:M RAM
DEVICE=C:\DRDOS\HIDOS.SYS /BDOS=FFFF
HIBUFFERS=35
STACKS=28,512
FILES=80
LASTDRIVE=M
SHELL=C:\COMMAND.COM /e:1024 /p
DEVICE=C:\PCKWIK\PCKWIN.SYS
<C:\AUTOEXEC.BAT>
CLS
ECHO OFF
PROMPT $P $G
PATH C:\;C:\DRDOS;C:\WINDOWS
SET COMSPEC=C:\COMMAND.COM
SET HAYESESP=180,3,3
SET ZIPR=N:\ZIPR
SET 123MEMSIZE=512
C:\PCKWIK\SUPERPCK /EM+ /D* /H* /P- /W- /B- /S:1024 /L-
C:\QEMM\LOADHI /B C:\UTILITY\LOGMOUSE\LMOUSE 1
C:\UTILITY\NUM_OFF
C:\DRDOS\SHARE
C:\QEMM\LOADHI /B C:\LAN\IPX
C:\LAN\NETX
C:\DRDOS\DISKMAP C:
N:
LOGIN
The first line of a configuration file must contain the name of the
configuration, enclosed by brackets.
Example: [WINDOWS]
The next line contains the fully qualified path and name of the first
file to be altered, enclosed by the less-than and greater-than signs.
Example: <C:\CONFIG.SYS>
The lines following this statement contain the information that will
be placed into the specified file. After these lines, a blank line is
mandatory.
Example: HIDOS=ON
DEVICE=C:\QEMM\QEMM386.SYS NRH DMA=32 ST:M RAM
DEVICE=C:\DRDOS\HIDOS.SYS /BDOS=FFFF
HIBUFFERS=35
If additional files need to be modified, the filename must follow a
blank line, and must be enclosed by the less-than and greater-than signs.
■─────────────────────────────────────────■
│ Advanced BOOT'R features: │
■─────────────────────────────────────────■
Advanced Feature #1: Using the BOOTR.INI file to specify a location for the
configuration files.
BOOT'R allows the capability to specify the exact location of the new
configuration files when they are written. There is no requirement that
they be placed on the current drive, or in the root directory. This allows
the modification of files that are inaccessable to other configuration
managers.
Advanced Feature #2: Using .INI files to modify up to five different
configuration files.
Not only can the CONFIG.SYS and AUTOEXEC.BAT files be changed, but up
to five different files can be changed for each configuration. For example,
network users may maintain a file called SHELL.CFG in their workstation's
root directory. Rather than keeping the same set of instructions for each
configuration maintained, SHELL.CFG could be optimized for each configuration
that uses the network.
■─────────────────────────────────────────■
│ Using BOOT'R with a Multitasker: │
■─────────────────────────────────────────■
Caution is advised when using BOOT'R in combination with Windows or
DESQview. Exit all open windows and exit the multitaskers BEFORE attempting
to execute BOOT'R. Attempting to execute BOOT'R from inside a multitasking
window could cause data corruption! You have been warned!
■─────────────────────────────────────────■
│ Cautions! │
■─────────────────────────────────────────■
Do NOT use BOOT'R in combination with any disk cache that performs
write-caching, unless you flush and disable the cache in the [REBOOT]
section of the BOOTR.INI file. Refer to the BOOT'R documentation for more
information.
■─────────────────────────────────────────■
│ Programs mentioned: │
■─────────────────────────────────────────■
AutoMenu is copyrighted by Magee Enterprises.
DESQview is copyrighted by Quarterdeck Office Systems.
QuikMenu is copyrighted by OSCS Software Development, Inc.
Windows is copyrighted by Microsoft Corporation.