Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!chalmers.se!mathrt0.math.chalmers.se!d9mikael
From: d9mikael@dtek.chalmers.se (Mikael Wahlgren)
Newsgroups: comp.os.os2.misc
Subject: Re: DOS dual boot & shutdown
Message-ID: <1991Apr16.150207.21273@mathrt0.math.chalmers.se>
Date: 16 Apr 91 15:02:07 GMT
References: <9656@star.cs.vu.nl> <1991Apr15.193226.1861@serval.net.wsu.edu>
Sender: news@mathrt0.math.chalmers.se (Evald Nyhetsson)
Organization: Chalmers University of Technology, Gothenburg, Sweden
Lines: 15

>I believe that doing a boot down issues the shutdown command as a system call.
>By doing that, It will actually send the close message to all running Apps, 
>and then when it has gotten control again, actually cause the reboot.
>
>I know that for some reason on my system, boot /dos doesn't manage to reset my 
>system.  It sets it up so that the next time I fire up, it boots dos, but I have
>to do a shutdown and reboot the system myself.

If the DUAL BOOT option fails to reboot your machine in OS/2, this is
typically because you haven't the DOS.SYS driver loaded.  By adding the
line "DEVICE=C:\OS2\DOS.SYS" in your CONFIG.SYS this should be avoided.
I think this is because the BOOT-program can't reboot by itself, but
has to send a special call to the DOS.SYS driver to tell it to reboot.

Mikael Wahlgren      d9mikael@dtek.chalmers.se