I'm now almost sure that the miner's mhash display is wrong when using -v1,2.

In 3 hours one rig created 2530 shares, which translates to 1006 MH/s. This is a statistical process, so we can assume an error of magnitude sqrt(2530) -> 50. So with very high propability, the hashrate is in a range of 986-1026 MH/s. The miner says 1370 MH/s which is nowhere near that value. 1000 MH/s is also much more realistic because I'm now using SDK 2.6 and a miner optimized for SDK 2.1...

As much as I would like to believe in those 1370 MH/s, no matter how I look at it, there is no support for this value.
I think you should really double-check the mhash display... If there is anything I can do, let me know.

Yes, I know the pool only "guesses" the hashrate, but btc guild is averaging over some time period (something like 10 minutes) and in the past miner mh/s and pool mh/s did not differ by more than 5%. While I was using -v2 the numbers where very close to each other, and now that I'm using -v2,1 (or -v1,2) the numbers differ by a large amount (1260 vs. 920 MH/s). I never saw such a big difference before... that's why I'm asking if you can say for sure (!) that the numbers displayed by your miner are 100% accurate.

I just checked... a 5850 with 850/1000 clocks, SDK 2.6 and the version of your miner linked in op gives 390 MH/s. Is that realistic given the fact you did not update the package in op and as such I'm using a miner not optimizied for SDK 2.6?! Using poclbm and SDK 2.5 I got something around 340 MH/s...

Using -w 256 is a bit slower than -w 128 (1230 vs. 1260 MH/s).

Edit: One more sign that something is wrong with the mh/s display: Let's say I have a nominal rate of 1000 mh/s. The pool sometimes shows less, sometimes more... like 950 mh/s and then 1050 mh/s - I saw that before (the 5% I was talking about). But now, using -v2,1, I *only* see less, but *never* more... And it's not "a bit less" but the pool always shows at least 20% less than the miner.

So the linked zip-package is still the same? I thought it was updated because you said "you can now upgrade to 2.6"... and that's what I did

But maybe there is no 16% increase at all - are you sure the MH/s display in your miner is always correct? Taking the numbers from the console I should be around 2,6 GH/s - but BTC Guild  says I just have about 2 GH/s.

In one PC I now have 2x5850 (@850/1000) and 1x5870 (@950/1200). The console says 1260 MH/s, BTC Guild says 920 MH/s... I have to say that 1260 GH/s is also somewhat unrealistic because that would be 420 MH/s per card... which looks ok for the 5870 but is too much for the 5850, isn't it?!

My commandline:
start "DiabloMiner" DiabloMiner-Windows.exe -u xxx -p bitcoin -o btcguild.com -r 8332 -f 2 -v 2,1 -w 128

Windows 7 32-bit, AMD driver 12.1

(when using -v2 the console says ~1000 MH/s and BTC Guild says ~950-1000 MH/s... so both numbers are almost matching)

Oh, and the SDK version is not displayed when starting your miner. Is this normal when 2.6 is installed? Before it showed "...using SDK 2.5", when 11.8 was installed.

Using -v1,2 I get a 16% boost compared to -v2. -v3 and -v4 are even slower than -v2. (Driver 12.1, 5850/5870.)
Is this expected behaviour? In the first post you recommend -v4 and say "Layered vectors, probably not faster"... but my findings are just the opposite.

O rly? HD 7000 Series is not supported by this driver....

I did, but it looks like you dind't. There are only drivers for Vista 32/64 and Win7 64. No XP and no Win7 32.

...where can I find them? Are they shipping with the card (on cd)? Or ist there no Win7 32-bit support yet?

Then I'm going to send you 1 BTC each two months

Release it and I will start using -b... (just some motivation for you :p)

Did some posts disappear?

Ars is SMPPS not PPS.

So the poolserver is offline ATM?

I'm sorry.

I can't connect to pps.btcguild.com, but btcguild.com is working fine.
Traceroute also not showing any problems.
What happened? Is my IP (range) banned?

"Request Payout" now gives me An error occurred while processing your payout, please try again..

Anyone else having problems with payouts or is it just me? :/

I had about 0,3% stales on deepbit, now 0,1% on btcguild. 0,5% less "fees" for same features PLUS e-mail idle notification.

So using btcguild is really a no-brainer.

(I'm using deepbit as backup)

eleuthria, I have a big problem with your pool. Now that Idle Warnings are back, I'm also.

BUT: I cannot connect to uswest.

2005-01-10 15:34:12: Listener for "***" started
2005-01-10 15:34:13: Listener for "***": 10/01/2005 15:34:13, Setting pool *** @ uswest.btcguild.com:8332
2005-01-10 15:34:19: Listener for "***": 10/01/2005 15:34:19, Problems communicating with bitcoin RPC 0 2
2005-01-10 15:34:25: Listener for "***": 10/01/2005 15:34:25, Problems communicating with bitcoin RPC 1 2
2005-01-10 15:34:31: Listener for "***": 10/01/2005 15:34:31, Problems communicating with bitcoin RPC 2 2
2005-01-10 15:34:37: Listener for "***": 10/01/2005 15:34:37, Problems communicating with bitcoin RPC 3 2

I have no peerguard or any similiar or any other blocking software installed. Note that I can ping uswest.

No problem connecting to useast.... currently using that server but if you change that one to poing to the loadbalancer, too, I will be unable to mine on btcguild.

Are Idle Warnings going to return?

On deepbit you can set "Averaging window for hashrate display" to 60 minutes, this way the variance of the Mhash/s display will be reduced. I'm pretty near at what GUIMiner says (variance smaller than 5%).

Simplest way would be to get GUIMiner (nice graphical user interface), select File > New Miner > New CUDA Miner.
But you should really get an ATI card for mining bitcoins... Even a 5770 is faster (twice as fast) than a GTX 580 when it comes to bitcoin mining.