• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

OGR is BACK!

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Jay, one quick suggestion, you may want to change the title, "Team Team Anandtech" doesn't quite seem right.

strates
 
Well, one thing's for sure, /. is having the same scramble as we are right now....

One other thought...did the PhF do a OGR=0 in all those ini files?

viz

edit- The P233 MMX that came from SocrPlyr must be a super SOB or I got some easy nodes. It completed one in 17 minutes @ 1.05 Mnodes/s.

I think that I will flush now. 😀
 
ok so should i let it keep running OGR or RC5?
and since i haven't got but likw 1600keys
i dont think it will matter

whats ogr doing?

cracking 64bit encrp?

whats it have to do with stars?

and whats rc5 doing

i have never really heard what each do

which would it be wise to start with?

is there going to be ogr teams or are they the same as rc5 teams?

thanks
i know its alot of questions
but i think yall experts can anwser them and help me out

thanks again
Brandon Bauer
brandon@sysreview.com
ICQ 27448822
 
It's great to see that OGR is back. Now we can BBQ the DPCs in 2 contests at once!😀 As for your question viz, it depends on what client he's using. If it's the 460s(which considering the timeline, it probably isn't), then yes, he'll probably auto-switch, otherwise, they'll crack invalid OGR blocks(that isn't such a bad thing😉), or stay with RC5.
 
OGR time line depends on how many people convert. we expect OGR-24 not to take very long.

As far as ogr stats. they are done and you should see them run tomorrow evening. assuming no problems occur 🙂

moose
 
Brandon: OGR is the search for the shortest (optimal) ruler with certain number of nodes. Right now we are searching for the shortest 24 node ruler. The catch is that no two nodes can be the same length apart from each other on a ruler.

hope that helps a little bit.
strates
 
Damn. :| I'm with Russ. I had just got a fairly credible key rate going and wham!:Q Everything is running OGR. I have to go into every machine and knock it out. Problem for me is that they are spread all over the country and though all the machines could be reset by the owners, not all of them understand the client, only that they're helping me "do something geeky!"

Sad day. 🙁
 
Excuse me, but am the only one who feels screwed by this ABRUPT event? NO WARNING. According to Moose my machines started doing OGR atleast 1 hour earlier than the "offical" time. I did not join to do OGR but to help TA get to number one in RC5-64. One could almost say that with the lack of advanced knowledge given by Dnet that they have turned their client into a trojan.

I am both quite pissed off and very dissapointed in this turn of affairs.
🙁🙁🙁🙁🙁🙁🙁🙁🙁🙁🙁
 
Dvch, it's more our fault than Dnet's. We(ok ok, it's all BK's fault😉) didn't take OGR into account when creating the main FAQ, so it'll start OGR on it's own.🙁 Sorry about that, and a new FAQ will be in the works to fix it.🙂
 
Virge-it is only you fault if you knew that OGR was going to restart and when. Otherwise it is the fault of Dnet. I object to the "notice" given. The notice I got was that I looked at my client and discovered that I was crunching something I had set to zero! THIS IS NOT A CLASS ACT! I have several machines off premises which now need to be reconfigured if they are to serve the purpose I-not dnet, me,-installed them for. This is I feel a basic betrayal of trust.
 
I think that us old timers should have done a little better job of informing the newbies what was coming. It's all in the Dnet info, but that's another story.

3 OGR WUs done on my slowest machine. Go figure!

viz
 
Moose, Decibel, dBaker, and others in d.net,

Personally, I'm so glad that OGR is back and going again that I've been running around with a grin from ear to ear all evening. 🙂

However, in my opinion, I'd have say that the complete lack of notice was a misjudgement of monumental proportions. 🙁 If you didn't realize just how many "feathers" would be "ruffled"... well.... you know now. 😉

Thank you for bringing it back (for those of us that have been looking forward to it for so long), but even I'd appreciate 48 hours or more of advance notice the next time.

Good luck with OGR! 😀

-Brian
 
YEEEE-HAW!!!!!! 😀

I'm curious about what Moose said about stats. Are the stats for RC5 and OGR going to be merged at some point? I'd like to find out so I can use my computers to their best advantage. In other words, I want to ride my cows as hard as I can! 😉
 
Hi,

In testing org on an 800mhz k7, it seem kind slow. what speed should I expected & what core should I used to get the best speed? Thanks.

os: windows me (beta) 🙂

ps. run benchmark, core 0 give me 6 MNodes but when actual run ...much, much slower. about the same speed as my p200 laptop. 🙁 BTW, I kill almost everything in the system.
 
crystal, you're rate in OGR will vary due to the nature of the "stubs" that its calculating. After a couple of days it should somewhat average out.
 
If people are worried about what this will do to the team, may I suggest that people run two clients - one with OGR and one with RC5, that way the team will get the most from everybody. Just a thought, feel free to post objections/ideas.
 
Back
Top