BETA! Folding Manager....

[Marvin_The_Martian]

If you got allot off cores and want an easy way to set them up and monitor them try this. Please read the first post there and try for yourself. I would love some more feedback!

Due note it's work in progress, don't download if you don't want to participate in getting it right

You can always mingle in the discussion offcourse, I also need allot off feedback on what's actually needed/wanted/requested

Cheers,

Marvin

[Sparky]

Looks good, so basically it removes them as services so it needs to be in the startup folder, but does that mean the console windows are visible?

I think what would be neat is if you could somehow make it control remote clients on other computers on the network.

[Marvin_The_Martian]

Looks good, so basically it removes them as services so it needs to be in the startup folder, but does that mean the console windows are visible?

I think what would be neat is if you could somehow make it control remote clients on other computers on the network.

Yes it will remove them as service but no the windows are not visible that's just the thing. The console clients are faster then the gui one's but some think it is harder to set up or use. Also you can not use those with more then one instance. When you have multiple cores this way you can easily manage and setup all your instances. Stats gathering/remote monitoring and management are the next stages, first I need to put the feedback I already got to good use and fix a few initial shortcomings. The link is down for the time being but I updated a small changelog and will try to get most things done tomorrow. Had to be updated with the new url for the gpu client anyway so the setup wouldn't have finished

I thought about just putting an interface together to start/pause the service and parse through the log files but I ran into file aces problems so decided to do it another way. For those who like the service because they can run unattended without user's logging on it will be a drawback you can always circumvent by just automaticly logging in. I think I'm trying to reinvent the wheel here since their are already installers and monitors, but I haven't seen any combined yet. And what you call neat is one off the things I will try to accomplish, I'm just not ready to take the blame if someone would borg someone's farm because I can't write a secure login procedure So that's one off the last things I'm thinking about. What's not in that changelog but should be: there already was a autoconfigure flag which would read your settings from a text file and set up all instances without user interaction but since I was adding and removing settings that got screwed up. I will restore that option to.

Edit: changing settings over a network could be done if I limit tcp acces to the subnet mask? Basicly the program just writes a configuration file which it uses to start and manage the clients, having the program recieve those settings and write a new configuration file isn't so hard, making it in a way john doe doesn't try to change your teamnumber to mine is ( atleast for me atm... )