• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

F@H Thoughts

Sunin

[H]ard|DCer of the Month - August 2008
Joined
Dec 27, 2005
Messages
3,421
You think they have ever considered having one overall application that is the shell to all others and can auto update clients, install clients as needed by performing an analysis of your system allowing you to install multiple clients at once and also allow you to deselect ones you do not want etc...

I'm thinking similar to your anti-virus software where it can upgrade itself, as well as the definitions etc... all automatically with out user intervention?



 
I think they are already going toward this goal. A unified client able to run SMP/GPU/UNI just with flags and be able to adjust itself on the host system. A good example is the Linux 6.02 unified client which can handle the classic or SMP client with just a flag.

 
I think they are already going toward this goal. A unified client able to run SMP/GPU/UNI just with flags and be able to adjust itself on the host system. A good example is the Linux 6.02 unified client which can handle the classic or SMP client with just a flag.


but the client doesn't upgrade itself.. I'd really like to see it where it just can auto upgrade itself and we the users install and forget.

 
It does upgrade the core and add dll files itself. As for the client itself, I'm not sure if they will program this for security reasons. Also, not everyone will want to see the client upgrade itself in fear to have a broken client like it happened with the initial 6.22 SMP client fiasco.

 
It does upgrade the core and add dll files itself. As for the client itself, I'm not sure if they will program this for security reasons. Also, not everyone will want to see the client upgrade itself in fear to have a broken client like it happened with the initial 6.22 SMP client fiasco.


Yeah but we all upgraded... we all had issues.... if the client could have downloaded each r2 and r3 for fixes then we would not have had to touch it... It honestly just points to they can't issue things like that... they need to give it more alpha and beta tests...

I mean this last time if you weren't folding 24/7 it impacted you. If you were folding 24/7 and had any type of reboot you were pretty much SOL... you could set the date back to 7/30/08 and start client and set the date back...

There has got to be a better way overall to manage the clients without having to install 3-5 clients indvidually on each machine.



 
I want to know why the standard client hasn't, at the very least, gone "multi-core" by opening up multiple instances for each core in a single window or with a service. I can't imagine how much processing power they're throwing away because people:

A. won't touch the SMP client.

B. can't be bothered to install multiple copies of the uniprocessor client in different folders.

C. only want to use the Windows graphical client.

I think folding was originally run in the background and they make it very difficult for the average user to load unused cores on a typical system.
 
I want to know why the standard client hasn't, at the very least, gone "multi-core" by opening up multiple instances for each core in a single window or with a service. I can't imagine how much processing power they're throwing away because people:

A. won't touch the SMP client.

B. can't be bothered to install multiple copies of the uniprocessor client in different folders.

C. only want to use the Windows graphical client.

I think folding was originally run in the background and they make it very difficult for the average user to load unused cores on a typical system.

This is a valid request, I'll try to talk with Uncle_Fungus to see if he could whip something like that.

 
I want to know why the standard client hasn't, at the very least, gone "multi-core" by opening up multiple instances for each core in a single window or with a service. I can't imagine how much processing power they're throwing away because people:

A. won't touch the SMP client.

B. can't be bothered to install multiple copies of the uniprocessor client in different folders.

C. only want to use the Windows graphical client.

I think folding was originally run in the background and they make it very difficult for the average user to load unused cores on a typical system.

Exactly. The BOINC client has been able to do this for how long now?
 
Back
Top