Dec 112017
 
Alter config.sys and autoexec.bat "on the fly" prior to warm/cold boot.
File RBOOT2.ZIP from The Programmer’s Corner in
Category Utilities for DOS and Windows Machines
Alter config.sys and autoexec.bat “on the fly” prior to warm/cold boot.
File Name File Size Zip Size Zip Type
REBOOT.COM 50264 35383 deflated
REBOOT.DOC 5238 2340 deflated

Download File RBOOT2.ZIP Here

Contents of the REBOOT.DOC file









A Professional Programming Partnership













VERSION 2.1

Copyright (c) 1987, 1988
CODEWORKS



Released into PUBLIC DOMAIN. This is a FREE program.

INTRODUCTION
Reboot was inspired by a Public Domain program called REBOCNFG.
The purpose of both programs is to allow you to change your CONFIG.SYS
file on the fly. REBOOT goes a step further allowing the automatic
change of your CONFIG.SYS and AUTOEXEC.BAT files.


CHANGES (2.1) 03/24/89
In response to your request the following features have been added to
REBOOT:
{1} No more hardcoding of your configs directory. Simply place
your various .bat and .sys files in the SAME directory as REBOOT.COM.
Optionally add that subdirectory to your PATH statement.

{2} Typing REBOOT without any parameters will popup a point and shoot
screen where you can optionally view the .bat and .sys files.

{3} Adding a slash C or slash W (ie. "/C or /W") will reboot your system
with a cold or warm boot.

{4} A slight delay has been added so that you can verify that something
has actually happened.

HINTS
A few users have reported a problem with REBOOT when using various disk
caching programs. I suspect that these programs are not passing direct
writes to the disk until such time as a default buffer fills. If you are
using such a program there is no immediate fix. REBOOT is know to work
with Lightening as well as Smartdrv disk caching software without any
problems as they pass all writes directly to the disk.


INSTALLATION
The procedure is very simple.
Copy the supplied file, REBOOT.COM to the C:\ directory or a
directory named in your PATH statement. Be sure REBOOT is located in
the PATH statements of all your AUTOEXEC.BAT variations as described
later in this documentation.

Next create any variations of your config.sys and AUTOEXEC.bat
files in the SAME subdirectory you copied REBOOT.COM to. Give the files
meaningful names such as PLAIN, STANDARD, RAMDRIVE, EMS, etc. The files must
have the same prefix. For example when using Desqview, a stripped down
operating system and all expanded memory is needed. For this purpose
I have two files named DESQ.SYS & DESQ.BAT residing in my c:\CONFIGS
subdirectory. Now to run DESQVIEW simply issue the command:

REBOOT DESQ

REBOOT handles the rest, copying the DESQ.BAT & DESQ.SYS files
to the AUTOEXEC.BAT and CONFIG.SYS files and then reboots the system
with a warm boot.

When finished with Desqview issue the command REBOOT STANDARD and
the system is restarted with my everyday system configuration. I use
this to boot up with ram drives, without ram drives, and various other
parameters that are used often.

The theory behind REBOCNFG was simple and great but most times
when a new config file is needed you also need different AUTOEXEC.BAT
parameters.

The only caveat is to make sure you assign two files for each type of
REBOOT. For example:

PLAIN.SYS PLAIN.BAT
STANDARD.SYS STANDARD.BAT
NOEDRIVE.SYS NOEDRIVE.BAT
RAMDRIVE.SYS RAMDRIVE.BAT

Or whatever works for you.



REGISTRATION INFORMATION
We are not requesting payment for this program. We would
appreciate hearing from you if you find REBOOT to be a useful
utility. If you are not hooked up to a modem please drop us a post
card. We are just interested in knowing how many people are using
REBOOT. Send your cards and letters to:

CODEWORKS
45321 North 7th St. East, Suite 59
Lancaster, CA 93535

Thanks for trying our product. Now to make the legal eagles happy!



DISCLAIMER
==========

Codeworks makes no warranty of any kind, expressed or
implied, including without limitation, any warranties of
merchantability and/or fitness for a particular purpose.
Codeworks shall not be liable for any damages, whether direct,
indirect, special or consequential arising from a failure of this
program to operate in the manner desired by the user. Codeworks
shall not be liable for any damage to data or property which may
be caused directly or indirectly by the use of this program.

IN NO EVENT WILL CODEWORKS BE LIABLE TO YOU FOR ANY DAMAGES,
INCLUDING ANY LOST PROFITS, LOST SAVINGS OR OTHER INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF YOUR USE OR INABILITY TO USE
THE PROGRAM, OR FOR ANY CLAIM BY ANY OTHER PARTY.





C.I.S [ 76416,3452 ] KEN WILCOX




 December 11, 2017  Add comments

Leave a Reply