is it possible to make this mine at about 3/4 of full speed on windows?  it seems like the -f doesnt do anything when i set it to more than a few hundred.

We should have a forum just for trolling (I realize there already may be one, and if so I'm glad I don't know about it yet).  This thread would fit nicely there...

So then, without the NMC bounty, did you use BTC or cash to pay the Botnet OP to attack other pools in order to buy you enough time to be the first big pool to get merged mining completed and made public ?

Wow,what a paranoid group (bitcoin miners) we have become,the only one to fear is BitcoinExpress,DUH!!!!!! Ok,maybe a couple or others too

Oh, so that's where bitcoin's central authority is

You are a bit wrong comparing apples and oranges. You don't know network's total hashrate, you can only know network's resulting "blocks per unit of time" speed.
It may be a 12 TH/s with a very bad luck, or the opposite. So if you are comparing network with some pools, you should compare same parameters, like that "blocks per unit of time" (which is almost useless because it's based on past luck).

What I'm trying to say is that deepbit's hashrate didn't changed dramatically in last days and I really doubt that only those who aren't mining in deepbit are leaving the network (which can explain such increase of pool's part if it was real), so this deviation is probably just caused by luck.

Hey Diablo, what's your commision from Ars, ABC and Bitcoin.lc? I can pay a little more to be the first on your list ;-)

NMC is now in the top ten.

For all pool users: This attack is worse than attacks before. Actually it's probably a tenth DDoS to pool in it's almost year history (I didn't counted them carefully and you probably even don't know about small attacks which I was able to handle somehow without public attention).

This attack is worse because Linode LLC, server provider for pool infrastructure, frozen my account for periodical violation of their ToS. I can access pools servers, but I was asked to not start another balancers with public IP because those attacks are harming datacenter infrastructure.

It means that I cannot start pool at this infrastructure and I need to find another provider. Which is pretty hard once I start asking to their anti DDoS policies. Back in July I was in touch with Rackspace, company providing custom solutions for big enterprises and even they told me that they cannot handle such large scale attack for some reasonable price (we're talking about thousands of US dolars monthly just for anti-DDoS protection). Posts of some users above are really naive, there's NO way how to handle those attacks just by banning some subnets.

Fighting attacks become much worse with falling bitcoin price, because even if I have 1/3 of all network hashrate and 2% fee I simply cannot pay for any real solution which really helps to handle attacks. Last week I tried to use services of one DDoS mitigation company (the same as deepbit is using), but they had pretty high ratio of false positives, so although I paid them big money for a single day protection, almost 40% of users were still unable to mine on the pool. So this isn't the way to go.

Since tomorrow I'll try harder to find any server provider which at least don't shut down pool infrastructure on first DDoS attack, but I cannot promise that I'll succeed. There's no point in running a service which is every week for one day offline thanks to attacks.

So far it's 1:0 for attackers. However I don't want to capitulate too easily; I spent insane amount of time and energy in inventing and running my pool and I don't want to simply disappear, because I really believe in long-term Bitcoin success (small note: people, don't get scared with current panic on market, it's just an oposite of July's insane price peak). I "invented" (maybe it's better to say "realized") first really usable and widely used Bitcoin pool ever and now I feel again that I'm on the track of another innovation of Bitcoin mining, which will be DDoS resistant yet easy to use and with steady payouts like normal share based pools.

Technical note: Because the downtime of mining.bitcoin.cz will be probably more significant than anytime before, I'll wait until all mined blocks will be matured and then will send all balances of users to their wallets. Don't worry, I'm not running away with your hardly mined coins!

I have a 6990 and Debian unstable, which includes fglrx 11.9.1. I have tried AMD SDK 2.4 and 2.5. Either way, DiabloMiner uses about 90% of a CPU core when mining on one GPU, and about 180% (nearly 2 CPU cores) when mining on 2 GPUs.  It also causes lag when trying to play games on the primary GPU while mining on the second, which worked fine on fglrx 11.4.  I understand this is a driver bug, but how can I fix it?  Which driver can I install and how?  There's no fglrx driver at all in Debian testing (presumably due to bugs in 11.9).  Debian stable has no support for AMDOverdriveCtrl so I couldn't underclock my RAM.  I tried to downgrade my deb packages, but then got dependency problems with libmesa and couldn't install anything new.

Would AMD's installer for an intermediate version, like 11.7 work better?  Or can we just fix or report the actual bug in the driver?

I tried to get this running but constant crashes on Exception in thread "main"java.lang.UnsatisfiedLinkError: no lwjgl in java.library.path

With 11.9 driver I started to have 10% HW errors but the CPU usage disappeared.
I added to the previous configuration -w 128 and now it all works perfectly (HW errors <0.5%, gained another 4% MHs and CPU usage is 1%)
Thanks