Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.

DooKey said:I say do whichever project you like. UD and F@H are both worthy projects that the [H] has endorsed. I've moved the bulk of my production to UD now that it appears we have a nice lead that isn't going anywhere soon. I answered the call to F@H a couple of years ago when asked, but it appears the migration to UD hasn't been what we were promised. Anyway, all the help we can get in UD is much appreciated. There's nothing silly about committing to UD for the [H].
Im just a little producer, glad to hear someone say we are worth a shit.MN Scout said:We don't have the other side of the view expressed yet, so I think I'll chime in now. I started out with F@H and I plan on seeing that project all the way through. Giving them most if not all the boxen I can get borged. I have no problem with people who put a small fraction of their boxes, or even half of their boxen, over to another research project. Moving all of one's boxen from F@H over to UD is just silly.
Someone mentioned that our big hitters are coming back and can hold the lead. I just want to point out if it hasn't been said yet, but our team is mostly made up of smaller producers. In our team the little people mean the most, unlike OCAU where if one of the big hitters go down they take a hit of >50k ppd. Our big hitters don't carry the team, it's all the little people. So we don't need a ton of people flocking over to another project.
That's my 3 cents..
![]()

Joves said:

SmokeRngs said:So, put what you want to UD, I'm not going to complain about it at all. Just don't be content to sit on your ass. Make sure you keep looking for more boxen and/or more borgs. Keep both projects growing.

MN Scout said:We don't have the other side of the view expressed yet, so I think I'll chime in now. I started out with F@H and I plan on seeing that project all the way through. Giving them most if not all the boxen I can get borged. I have no problem with people who put a small fraction of their boxes, or even half of their boxen, over to another research project. Moving all of one's boxen from F@H over to UD is just silly.
Someone mentioned that our big hitters are coming back and can hold the lead. I just want to point out if it hasn't been said yet, but our team is mostly made up of smaller producers. In our team the little people mean the most, unlike OCAU where if one of the big hitters go down they take a hit of >50k ppd. Our big hitters don't carry the team, it's all the little people. So we don't need a ton of people flocking over to another project.
That's my 3 cents..
![]()

Your option sounds like a workable solution. UD, unlike FAH, doesn't work easily with two instances, but easily multitasks with other projects. I've fired up UD on my tech box (A64 3000+), and it is quietly sharing cycles with a F@H "Amber" core 50/50.meisterbrau said:I ran UD for quite awhile - but didn't remember until now that I had signed up with the Horde. So maybe I should come out of retirement to defend my 94th place in the team rankings. I'm currently running 2 instances of FAH on this dual core amd 3800. Is it advisable to have one core running FAH and the other UD?
meisterbrau
![]()


This may not be entirely true with the new Rosetta units.Mattman said:If you just want to help the [H] in the UD points race, you don't even have to switch your fast machines over. Two of my highest scoring machines from when I did UD a few years ago were a PPro 200 and a Pentium 233 laptop - they hung in there with machines 10x as fast! Of course the slow machines don't do many WUs, but with UD's wacky points system, it doesn't matter much what you use. If you can throw a hundred PII/PIII's at UD, you can kick some butt in the points category. Here are two machines I ran that racked up almost identilcal amounts of time and points.
1. 194 days, 57,475 points, 281 results
2. 193 days, 61,431 points, 453 results
Machine 1 was a PIII800 and Machine 2 was an AXP 1.6-2.0 (might have upgraded in that timeframe).
