Original from  Paul Edwards  to Marcello Desantis on 11-03-1996
Original Subject: reboot

                         ---------------------------------------

 PE>> Can someone please send me code that will do a reboot(). Thanks
 PE>> + bye.  Paul. 
 
 RH> You have it: the standard OS/2 SETBOOT command!
 
 MD> SETBOOT requires the Boot Manager.
 
PE> I only have a bootmanager machine, but the target machine 
PE> does not necessarily have boot manager.  Can you tell me 
PE> which bit requires bootmanager?  Is it the "setboot" 
PE> executable that doesn't exist on a non-bootmanager machine, 
PE> or does the "setboot /b" do something wierd on a non-
PE> bootmanager machine?  If so, what does it do?

 I checked further, and SETBOOT.EXE seems to be installed on Warp 3 
Connect systems (and above) regardless of BM being installed or not. 
Many of my classes are taught on machines without a BM partition, and 
setboot.exe appears to still be installed on the systems. I have not 
tested previous systems (and I am assuming that the installers did not
specially add setboot.exe to the Connect install). 
 
 SETBOOT /B will not reboot the system unless a BM partition is 
detected. SETBOOT /IBD:x: (where x is the boot partition) will work 
regardless of a BM partition on the system or not. You have to be able
to pick up the partition for boot, but this is trivial on a system
without BM - it should always be C: .. What I do is to pick up the 
booted partition, and then fire off setboot /ibd:x: with the same 
letter.
 I suppose it is possible that the user could be using an alternative 
method of selecting a boot partition, and that the above will not work
with all systems.. Anybody know if the method used by different 
"multi-boot" systems would be totally incompatable with setboot? 


   Denis       

 All opinions are my very own, IBM has no claim upon them
. 
. 
.
--- Maximus/2 3.01