• 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 probs

Ausm

Lifer
I am trying to crack OGR packets but the damn thing keeps d/loading RC5 packets. I reconfigure the client to give priority to the OGR packets with no luck....WHATS UP WITH THAT?!?!


Ausm
 
i have the exact opposite problem!

i had a buttload of computers working on rc5 and all the sudden they decide they want to work on ogr. wtf? grrrrrrrrrr i cant get em to work on rc5 anymroe for some reason.
 
Check your client version number. If it is not one of the newest clients, the keyservers won't send you the "switch" that turns on OGR. Upgrade to a newer client and you'll get potentially greater speed (depends on processor) plus OGR compatability.

v2.8009.460+ (July 7th 2000)
Client version v2.8009.460 will be the minimum build from which OGR results will be accepted from, even though earlier builds on some platforms included preliminary beta OGR support. Please be sure to verify all of your installed client versions.


http://www.distributed.net/download/clients.html

nuttervm, your problem isn't just yours. There are several other threads that discuss just what you want.
 
ausm, I'm sure you've already done this, but just in case:

Priority: OGR,RC5=0,CSC=0,<that other one>=0 with latest client.

If you set it to OGR,RC5,etc., it will do both OGR and RC5.

And make sure you run the 463 client because it's 20-30% faster in OGR than 462. (imagine shocked look gif - dunno how to do that) (People were wondering why my lowly Celeron was kicking all the Athlons and PIIIs in existence not only on a per MHz basis but also in raw cracking power until we figured out it was the client.)
 
Back
Top