- September 2018
- May 2018
- December 2017
- April 2017
- June 2016
- February 2016
- November 2015
- January 2015
- August 2014
- July 2014
- May 2014
- March 2014
- February 2014
- January 2014
- November 2013
- August 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- December 2012
- November 2012
- September 2012
- June 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- September 2011
- July 2011
- June 2011
- May 2011
- March 2011
- January 2011
- October 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- September 2009
- July 2009
- June 2009
- May 2009
- March 2009
- September 2008
- April 2008
- December 2007
- June 2007
- June 2005
- September 2004
- May 2002
- October 2001
- August 2001
2010-01-26: Created RunExit tool
A user at the VOGONS forums posted a question about being able to start Windows 3.1 (inside DOSBox) with another application and shutting down that Windows instance (and thus DOSBox) immediately when that application exits. This would normally be accomplished by setting the application as the shell in place of the default (Program Manager) by changing the shell=progman.exe line in SYSTEM.INI to the path of the application's executable.
Unforunately, the program in question refused to cooperate and threw an error message upon starting. Because of that, I created a simple utility using the ancient version 1 of Borland Delphi, as it was the only 16-bit version of Delphi, which is what was required to build a 16-bit program. The utility simply executes whatever file is specified as its first command line argument, waits for it to close and then silently shuts down Windows. For instance, starting it as runexit notepad would start Notepad and, after that closes, return to the DOS prompt. Since win.com itself accepts a command line of an application to start, it would be something like win c:\runexit\runexit notepad.
The tools itself and the Delphi 1 source code can be downloaded off the tools page.
Update (2013-05-25): New version adds support for setting the working directory and passing parameters.
Comments
So yes this is exactly what i would want but, the old game i'm trying to run is messed up if i don't startup default shell before anything else. Like i start win then it runs fine if i start it, but otherwise like i add shell=program.exe in the system.ini the windows completely messes up. Even with your runexit program. Anything you can think of to try?
Heroic. I searched long and hard for this -- and it works like a charm. Thanks!
Thank you so much for this utility!
It has been an essential element of a little project of mine, where I've been making links on my Windows 7 desktop that directly start Windows 3x programs housed in DOSBox. I couldn't have done it without this!
...As an aside, you may have the prestige of writing the LAST program ever "Designed for Windows 3.1"...
Glad you like it. I doubt it's the last program ever to be designed for Windows 3.1. After all, people are still writing software for the Commodore 64 and for DOS, too. As long as there are enthusiasts, software will be written.
As of today, it's the most recently updated one though. At least for now ;)
This is so cool, thank you very much.
I'm building up a setup where I can launch games directly and get back to the launcher (which will be either RetroArch or KODI) and thanks to you I can finally add the great Win 3 games to my collection. Fantastic work!
Post a comment