SolarStrike Software

As I mentioned in thehttp://solarstrike.net/phpBB3/viewtopic ... eb2f0df75b thread I use a process monitor to make sure crashed clients are removed.

I.E. it runs as a separate MM process, when it detects a "Crash Report" window it terminates the proces (client), this enables the error handler in RoM to catch the error and respawn a client/MM window as described in the above thread.

The userfunction_processMonitor goes into the normal place, the crashmonitor.lua is put in the micromacro/scripts directory.

To start process monitoring use "StartProcessMonitor()" in your scripts onLoad, note that one once monitor will be run for all scripts executing. As an alternative uncomment the "--StartProcessMonitor()" in bottom of userfunction_processMonitor to always have monitor starting when your botting.

Regards,
DX

This was working great (still does when it crashes) but ROM seems determined to thwart our desire to mitigate our crashing. I have had very few crashes of late. Now ROM just gets stuck in a "This program is not responding" freeze up that I do not notice until I see Window's little blue disc of death spinning hopelessly on the screen. Is there anyway to detect "Not Responding" in the process monitor and kill it as well? Lost an hour this morning because I did not notice my bot was just standing there as if it were a .JPG instead of an actual animated program