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.
I believe the command line client is still faster than the gui client due to not having to render all the pretty stuff. If HideitX didn't work try Firedaemon. If you're running it on a Win98 machine then HideitX & Firedaemon won't work, you'll have to stick with the gui client -- but run it as a scheduled task. Take FAH out of the startup folder and it will start as a scheduled task (when you add it as a task) after a reboot. It won't show up in the system tray that way. Good luck!
I can vouch for HideitX working with Win95/98 since I ran it that way for a long time - I'm sure it works just as well on 2K/XP. For 2K/XP, I just run the command line version as a scheduled task. If you run in to problems with the command line version and either of these two methods, we should be able to get you fixed up, so let us know how it goes.
the OS's i am running are xp pro, 2k3 server, and 2k server.
i ended up running the command line version with firedaemon as a service. it seems to be working well
i do have another question tho. what is more efficient, running one command line client on my quad and dual boxes, or running one client per processor?
if i run one, it seems to be multi-threading and using all processors..hence complete one job faster, or
run one command line client per processor, takes longer..but more jobs running...
On the multi-CPU machines, I run one instance on each processor. As far as I know (please correct me if I'm wrong, anyone ), F@H isn't written to take advantage of multiple processors. I know there is a minimal gain with one way vs. the other, but I like to have as many instances running as possible in case of a network outage,etc... Some of the other guys around here can probably explain it better than I can.... Good luck and keep on folding!!
Yes, run one instance per processor. If you have Hyperthreaded processors, you can run 2 instances and get up to 15% extra work done. Therefore, if you have a dual processor Hyperthreaded Xeon system, you can optimize your output by running 4 instances of folding. Make sure that you assign a unique machineid to each instance on a single machine by going into the advanced setup of the client.