This thread needs a bright shiny gold star. Thanks for this. Working fine for me, Windows 7 64bit.

This ^^

*cough*difficulty doesn't drive price*cough*

Depends on the security. While windows might technically be more prone to malware and infections due to market share and stupid users, given the broad market of linux as server software on the internet, it contains much much much more known exploits and hacks than Windows.
Also, stupid users are gonna be stupid no matter what OS they run. I'm just sayin.
If you avoid things like installing suspicious software, toolbars, and running every exe you get in the emails, keep up to date with malware scanners and to an extent, antivirus... Windows can in fact be more secure than linux. Or at the very least, just as secure.

Still waiting on an answer to this... i could append well enough, but dont want to wipe out my entire sig for 3 months just for 0.10 btc

So, suggestion on the site, a page that lists previous winners and not just the last winner. I know there have only been 2 winners so far, but eventually that number will get larger, and it's always fun to see who's won

I also have been hit recently by this person.
Sadly, I don't know if I will use bitcoinmarket again in the future, for any trades. It's just not trader friendly at the moment, there's no real limitations sellers can set on buyers other than price and currency. And the inability to change feedback is a real pita.
When this transaction when through, the buyer had over 10 positive feedback, so even if i could review buyer stats before going through with a transaction, i probably would have approved it on rating alone.
I have submitted email to PayPal and screenshots of all transaction information as my proof that i in fact sent the goods in question, which is just a silly requirement to refute my case since goods received isnt even the dispute, its unauthorized transaction. I will also be closing my paypal after this incident too. I dont think i should be held personally responsible for someone elses weak passwords.

Did you mine at Eligius pool at all with your cpu about oh, exactly a week ago?

Fixed it for you

I'm not sure if El has conclusive evidence yet, but most things point(ed) to an attack.
There was a massive spike in connections, a massive drop in poolspeed, a massive increase in idle miner and rpc coms for everyone.
El has gone to bed for the night it would seem, but before he left, he tweaked the iptables to be a bit more restrictive (which appeared to help for a bit, but wasn't an end all solution) and implemented better more specific logging techniques to further investigate over night behavior when he can tomorow.

While im sure the idle miners and rpc coms are annoying, i have to point out at least the server has stayed up through this (possible)attack. That's pretty awesome in it's own. That's a bit more than other pools can say about some of their more recent attacks. Not only has it stayed up, but our luck hasn't been too shabby through it either

Eleuthria mentioned in the IRC channel that he found the cause for the idle miner issues, which should be much better now. Apparently, the server was mistaking miner traffic for syn floods.
So, everything should theoretically be back to pretty stable now.

I could think of 2 possibilities, but I'm not saying. If they wanted the world to know who they were, they would hop on here and be all like "Yeah, you see that awesome powa? That's me bitches."

If you spend any amount of time in the IRC channel, you could probably draw your own conclusions.

sort of have to know what the batch file looks like before anyone can tell you why it might not be working

Unknown. Would help if people either halted their miners or pointed them somewhere else for a little little bit.

That would be for a 5550
There's only one 5450 on there, and its at 11.99 so one could assume further tweaking might break into the 12's

buy a new card?
seriously, according to the mining hardware chart HERE you are getting about what you should be from your current card.

No, but older clients won't recognize anything beyond x.xx and in fact, those amounts would be lost for various reasons if sent/recieved. Also, the current default transaction rules for the bitcoin client will require a 0.01 transaction fee unless...
the block is currently under 27kB, in which case, the transaction will be free
the block is currently more than 250kB, in which case, the transaction fee will increase until the block size reaches it's maximum size of 500kB, at which point transaction fees will be 5x the normal amount.

So as you can see, until it is sure that everyone has upgraded their client, its safer to just store any remaining balance beyond x.xx for a later transaction.

yeah, since OP mentioned they were trying to connect to guild i was throwing out most likely guild culprits.
i believe i heard slush's were due to load balancing issues which should be fairly resolved by now?
i really try not to slander any particular pool, since every pool has some pretty serious issues as development furthers.

Luck is Luck, it doesn't obey laws of physics. To give an example, we just had a 2 million share round that lasted like 5 or 6 hours, which was then followed by three rounds in less than an hour, which was in turn followed by another 2 million share round... there's no telling when these things are gonna happen, they just happen, and they can happen to the biggest fastest bestest of the best.

On a related note, even with the incredibly unlucky 2million share rounds, we're still only slightly longer than average overall on our estimated block time and shares. Nothing that another couple 10 minute rounds can't remedy.

Not sure if you're still having problems, but here's a few suggestions...

A. if you use peerblocker, make sure you add a rule for the pools ip
B. make sure that whatever you put in the password field on the command line is like, i dont know, we'll say 4 or more characters (someone reported connection problems with a single character password earlier today)
C. if you randomly connected earlier after having the problem, and can't figure out what you did to fix it, it was probably not your fault. the pool underwent a very minor attack, it didnt bring the pool down at all but did cause a few brief rpc errors and idle miners for some.

short of that, you could try changing the host to mine1.btcguild.com if you are currently using btcguild.com.