November 6, 2012 at 11:00 am #8061AnonymousInactive
thanks.November 6, 2012 at 4:34 pm #8067
Just uploaded 0.6 which adds basic support for commandline arguments. You can currently only specify one per process.
I’ve also fixed a bug causing Windows to bluescreen when ProcessAlive attempts to open a 32bit Piriform product on x64 Windows. Apparently Piriform doesn’t limit the number of child processes their products are allowed to create; which leads to a Fork-bomb-like DDOS.November 9, 2012 at 12:39 am #8074AnonymousInactive
tested works as expected.
thanks.November 27, 2012 at 12:21 pm #8114AnonymousInactive
Is there any support for Win8? I ran the software and the ‘save list to a file’ check box does not actually create a file and ticking the ‘start with windows’ check box creates an error : http://i.imgur.com/eISy1.png
Cheers – great app.November 27, 2012 at 12:28 pm #8115
It seems Microsoft have removed support for creating startup entries (via the registry) in Windows 8. You might need to use the Windows Task Scheduler to handle this functionality.
The ‘save list to a file’ option usually starts working when the app has administrator rights. For some bizarre reason, Windows considers writing a text file to be dangerous behaviour.
Once I get a Windows 8 test machine set up; I’ll look at resolving these issues. It will be at least a couple of months though.November 27, 2012 at 12:54 pm #8116AnonymousInactive
No problem. Thank you for the prompt reply!November 30, 2012 at 2:56 am #8126AnonymousInactive
First off ~~Great Program~~ Had our devs’ working on a Sevice but no need anymore cause you guys ROCK~!
I am in the process of converting all our old Dell Boxes to work as Thin Stations.
This program was the last peace of the puzzle(or so I had hoped).
Is there anyway to set the program to not only start ,but run with the pre-configured
settings. For example* It is set to start on windows start up and the list/program has been saved (Path the the Thin Client APP) However when I do not have Explorer.exe set as the shell it does not start Automatically.
So the way i chose to get around that is to run it as a Task via Task scheduler.
but this simply opens the Program and doesn’t start.
So, to re-clarify my question: Is there a way to configure the program (maybe that .INI file) to start the “Keep these programs alive…” thingumabob
Thanks for your time,
CameronNovember 30, 2012 at 12:26 pm #8127
If you’re using the Task Scheduler, make sure you add the “/AUTO” commandline switch which tells ProcessAlive to start monitoring.December 1, 2012 at 12:06 pm #8128AnonymousInactive
Is it possible to add a delay timer?
I mean the amount of second or minutes PA checks if the program is running?
We have a particular program that when exited or even crashes our scripts auto run procs to clean log files.
So even when the program is exited normally we still have to wait 1 min before restarting it until all logs/procs have been run.
If I am missing a cmd augment for delay please let me know.
Thank YouDecember 1, 2012 at 2:32 pm #8129
Shaun; there isn’t currently a delay option. It wouldn’t be overly difficult to add though. If I’m not too tired later, I’ll see if I can whip something up.
- This topic has 89 replies, 15 voices, and was last updated 2 months ago by .