Home › Forums › Product Support › ProcessAlive – Automatically restart crashed programs
- This topic has 91 replies, 15 voices, and was last updated 1 year, 3 months ago by
Phobos.
-
AuthorPosts
-
June 25, 2012 at 10:05 am #5592
Sujay
GuestWhere does “Save list to a file” saves that file? Does this mean even after closing the interface the list will remain? I cannot find that feature working.
I have a suggestion. Please add “close to tray” option.June 25, 2012 at 10:06 am #5593Shane Gowland
Keymaster“Save list to a file” stores the created file in the same directory as ProcessAlive. It allows your list of programs to be preserved after the program is closed.
“Minimize to tray on close,” will be added to the 0.4 release. It will be available in about 10 minutes
June 25, 2012 at 10:06 am #5594Sujay
GuestHello Shane,
Thanks for your reply and the initiative in releasing an update.. But I seem to find some strange ‘bug’s.
1. “Minimize to tray on close” occurs only when it is monitoring one or more program. When its not monitoring clicking on ‘X’ button closes it completely.
2. I cannot seem to close the software by clicking on the right click tray menu “Exit ProcessAlive” when it is monitoring an application (do note that no monitoring no tray icon as I said before). “Exit ProcessAlive” seem to be working when the interface is shown; it hides the interface by clicking on that menu (but tray icon/software remains running).
3. So, unless you stop monitoring you cannot close ProcessAlive unless you force close it from Task Manager.
4. For the first time “Save to list” works & creates process_list.ini (in the same folder as the application) only if you add an application to the list, monitor it and then close monitoring and then exit the application. But if you add an application to the list and them exit the application it cannot save that list first time. But once the process_list.ini has been created it works as expected.See the demo video for an illustration of some of the problems I described.
[code]http://www.datafilehost.com/download-0ab1408e.html[/code]June 25, 2012 at 10:08 am #5595Shane Gowland
Keymaster1: This is the expected behaviour. I don’t see much point having the program running in the background unless it’s actually doing something.
2 & 3: Thanks. I’ll get that fixed asap.
4: I can’t reproduce this, even with the video. I’ll spend a bit of time going through the code later tonight.
June 25, 2012 at 10:08 am #5596Sujay
GuestThanks Shane,
Close bug is fixed.
In Windows XP Pro 32 bit it could not even create process_list.ini file.
If you got time please check the codes.June 25, 2012 at 10:08 am #5597J-C Pautet
GuestSince the last monthly update from Microsoft (May) the ini file is create, saved and works well.
Best Regards.
Jean-ClaudeNovember 1, 2012 at 9:39 pm #8043Anonymous
Inactivehi,
is it possible to add support for command line argument? by the way, how frequent do you perform checking for process life? or do you use other elegant pooling method.
thanks.
November 1, 2012 at 9:56 pm #8044Shane Gowland
KeymasterThe process update checking method uses the WIN32_GET_ACTIVE_PROCESSES API. It runs on a low priority thread and loops in a non-stop fashion. The stack is cleared on every iteration so memory allocation is minimal.
Oh; and what commandline args do you want to see?
November 2, 2012 at 10:56 pm #8056Anonymous
Inactivefor example, “notepad.exe mytext.txt”
i mean, command line argument for the application that are going to be monitored.
thanks.November 6, 2012 at 11:00 am #8061Anonymous
Inactiveany updates?
thanks. -
AuthorPosts
- You must be logged in to reply to this topic.