Repository navigation
Changes from previous version:
Add support for identifying when an application switches execution to another process
There are some applications that subsequently launch another executable, or perform some other action, which results in the originally launched application being detected as no longer being loaded; and so RunExit would attempt exit Windows while that application was still actually running.
This release includes significant changes to how RunExit determines if the launched application is still running. It will now iterate through the currently loaded modules, and attempt to match loaded modules with that of the launched application based on the paths matching (ie. launching C:\SC2K4WIN\SC2000W.EXE would match with modules containing C:\SC2K4WIN in the path).
If a related module is found, then RunExit will continue waiting until all related modules are unloaded before exiting Windows.
See Related Module Matching for further details and additional configuration options which are available.
This change can be reverted by starting RunExit with the /legacy parameter.
Add support for generating a log file
Starting RunExit with the /log parameter will create runexit.log at the root of the default drive (eg. c:\runexit.log).
If using multiple parameters this option should be the first supplied in order to capture the most amount of information in the output.
runexit.log is overwritten each time that RunExit is run with the /log parameter.
Example
win C:\runexit\runexit.exe /log c:\mps\gpm\gpm.exe
Full Changelog: v1.5...v2.0
