Subj : Re: Remote safe reboot To : Holger Granholm From : Mike Luther Date : Wed Nov 21 2007 08:53 am Yes, Holger.. HR>\ecs\bin\shutdown.exe HG> I have it also in the \os2\install\ directory Spot on correct. But the question of focus on at the start of this romp was how do we get whatever shutdown.exe to automagically do a reboot .. as well as close down all running objects without intervention on the path through the code forest to properly do that! My guess is that however IBM originally created this escapade was to use the , if smashed from the keyboard on the original keyboard IRQ ring level priority, to accomplish this task. Which, if I was trained well enough to know how this works, exactly, I could have impersonated in the REXX file written. But as un-informed as I am on this problem, that is sort of how I got toward making my original post here! I'd thought about starting the reading project to go through all the blocking stuff that is out there to see what could be done here, but figured it would be likely better and less time spent to just ask for the help the way I did. As well, the shutdown.exe file in the OS/2\INSTALL directory is different as to size and release date for a Warp4 vs. MCP2 installation from what I've seen here. Warp4 FP17 --------- 19,010 bytes 08-09-96 1:01am MCP2 XRC05 -------- 25,362 bytes 09-24-01 3:56pm And now that you've said this, I wonder. My research on the externally furnished shutdown.exe from the shtdwn16.zip archive was originally done on an MCP2 system. The remote system is Warp4 FP17. As originally done on the MCP2 system, a fully running couple of my own objects were automatically closed with I ran the test. The MCP2 box came right back up with no need to tell the shutdown to stop any process. But the above all thought about, maybe what I ran remotely at the test site was really nothing more than the IBM supplied shutdown.exe and not the test I thought I was running at all! Hmmmm.... I think when I'm out at the remote site I will rename the externally furnished shutdown.exe to a different name, as well as change the program name in the REXX .CMD file I wrote. It just might be that the path priority in whatever the system is using when all this fires up actually isn't using the shutdown.exe from the archive! --> Sleep well; OS/2's still awake! ;) Mike @ 1:117/3001 --- Maximus/2 3.01 * Origin: Ziplog Public Port (1:117/3001) .