Dnetc client can't find proper core for RC5 for Athlon XP?

[ugh]

Hi all,

Just got an Athlon XP and I'm surprised that the dnetc client (469) isn't able to determine which core to use. It always defaults to finding the fastest core and takes like nearly half a minute to do so. Anyway I can force the program to use a specific core to crack the keys?

Thanks.

 

[bot2600]

Sure you can. After it determines which core is fastest right click on the dnet window and select configure. In the menu, choose 3(core selection) then you can manually set a core. You can also experiment with different cores from here to see what gives you the best numbers.

Bot

 

[ugh]

<< Sure you can. After it determines which core is fastest right click on the dnet window and select configure. In the menu, choose 3(core selection) then you can manually set a core. You can also experiment with different cores from here to see what gives you the best numbers. >>


Ahh... Thanks.. Should've poked around a bit more b4 asking the question

 

[ViRGE]

Humm, I'll have to ask Moose if/when a new version of the client will come out with XP support; I'm suprised Dnet hasn't allready done it.

 

[ugh]

<< Humm, I'll have to ask Moose if/when a new version of the client will come out with XP support; I'm suprised Dnet hasn't allready done it. >>


I've been using the 463 client all along and I thought that was very outdated since it's been a while since I've updated. I too was surprised that the 469 client doesn't recognise XP as well.

 

[Jay]

Well, since 469 came out in late May or early June, and XP was released in October, it would be safe to assume that the 469 won't recognize it. If someone could tell you chich core it uses for the T-Bird, I would think that would be the safest route to go.

 

[ugh]

<< Well, since 469 came out in late May or early June, and XP was released in October, it would be safe to assume that the 469 won't recognize it. If someone could tell you chich core it uses for the T-Bird, I would think that would be the safest route to go. >>


Actually I'm running core #6 (re-pair II or something).

 

[bot2600]

Yeah, my duallie duron box is showing core#6...


Bot

 

[ugh]

At least it's faster than P4s....

 

[bot2600]

I think the cyrix chips might give the p4 a run...atleast clock for clock...

Bot

 

[Jay]

<< I think the cyrix chips might give the p4 a run...atleast clock for clock... >>


Well, I don't think it's a better core for the Cyrix than it is the P4 Core not being built with RC5 in mind.

 

[Wamingo]

hi yall. woa, it's been a while since I've been here...

I bought an 1800+ xp running at 1.5 GHz just recently, and I noticed this core selection too, took way over a minute for it to calculate it, which was somewhat annoying. But I chose core #6 too. quite fast, compared to my old piece of junk at least. Maybe if I'm lucky I can beat 10k workunits per week now?

 

[SaX0N]

yeah the dnet client doesn't detect my mobile p3 1.2ghz either
i get the same "Running micro-bench to select fastest core..."

 

[ugh]

<< Well, I don't think it's a better core for the Cyrix than it is the P4 Core not being built with RC5 in mind. >>


Which CPU is built with RC5 in mind anyway?

 

[ugh]

<< yeah the dnet client doesn't detect my mobile p3 1.2ghz either i get the same "Running micro-bench to select fastest core..." >>


That's strange. The Tualatins aren't that much different than Coppermines...

 

[SpaceWalker]

<< That's strange. The Tualatins aren't that much different than Coppermines... >>



Tualatins are a higher stepping so the client sees a different chip