Xref: utzoo comp.os.msdos.apps:1258 comp.os.msdos.misc:1423
Path: utzoo!news-server.csri.toronto.edu!rutgers!mit-eddie!uw-beaver!ubc-cs!alberta!mts.ucs.UAlberta.CA!Al_Dunbar
From: userAKDU@mts.ucs.UAlberta.CA (Al Dunbar)
Newsgroups: comp.os.msdos.apps,comp.os.msdos.misc
Subject: Re: automatic boot pc from batch file
Message-ID: <RN.219@mts.ucs.UAlberta.CA>
Date: 7 Mar 91 03:07:59 GMT
References: <1991Mar2.233927.20706@macc.wisc.edu>
Organization: MTS Univ of Alberta
Lines: 61

In article <1991Mar2.233927.20706@macc.wisc.edu>, oper@vms.macc.wisc.edu (MACC Operator) writes:
>In article <3629@casbah.acns.nwu.edu>, halpern@casbah.acns.nwu.edu (David Halpern) writes...
> 
>> 
>> 
>>Many times I have to reboot my computer because I change my config.sys
>>file in order to include a particular device driver for communications
>>or graphics software.  There is not base memory to run the graphics
>>software if I load both communications and graphics device drivers.
>>I would like to have a batch file that would test for the presence of
>>the appropriate device drivers, change my config.sys if required and
>>reboot my computer without having to press CTRL-ALT-DEL.
>> 
If you want to do the above with a batch file, you can
have it reboot your PC by running the executable .COM file
generated with the following DEBUG script file:
 
Filename: REBOOT.SCR
Contents:
            A
            mov ax,40
            mov ds,ax
            mov ax,1234
            mov {72},ax
            jmp ffff:0000
 
            rcx
            10
            n reboot.com
            w
            q
 
To generate REBOOT.COM, type: 'debug <reboot.scr' at the
DOS prompt. When run by your batch file, this program will
perform a warm boot; to make it a cold boot, change the 1234
to something else. The first version of this that I used had
a jump to F000:E05B instead of FFFF:0000, and it worked
equally well on a variety of PC's.
 
Testing for the presence of device drivers will be a bit 
trickier. One way would be to read CONFIG.SYS (obviously
requires a program, not just a batch file), but that would
miss drivers loaded as TSR's, such as ANSI.COM. Another 
would be to trace through the PCP's of all drivers and
TSR's loaded. A better way would be to find a utility
program that tests for a particular driver and returns an
appropriate ERRORLEVEL. 
 
Changing the CONFIG.SYS file is easy; just have all the possible
ones there under different names, and copy the one you need to
CONFIG.SYS. Or rebuild CONFIG.SYS from scratch with lines
such as:
 
echo device=c:"drivers"mouse.sys > "config.sys
 
 
 -------------------+-------------------------------------------
 Al Dunbar          | 
 Edmonton, Alberta  |  Disclaimer: "I disclaim disclaimers"
 CANADA             |                              
 -------------------+-------------------------------------------