i haved moved the worker to slush startum proxy still same
Total MHS:   00000
Received:   0000000000
Accepted:   0000000000
Per Minute:   000.00
Efficiency:   000.00%
Up Time:   0d,00h,00m,04s

Current Server: +http://api.bitcoin.cz:8332
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

yes it should. you connect to the proxy and the proxy connect to the pool.

how do i set up the proxy tried slushs download still no luck

I have two of the old style blades. one has been chugging along nicely at 10 Gh/s with the low clock. today i started the second one. They are both sharing a 490 watt supply. the second one came up with a bunch of Xs. powering on and off got it down to 4 Xs it was running at about 4Gh/s and after the last restart is running at 1Gh/s. is this a power supply issue? do i need to give each it's own Power supply? Both are using the same Slush proxy with unique workers.

Depends on the PSU! Its now how many Watts in total the PSU delivers, its about the Amperes on 12V it can provide! How many Amps does does your PSU deliver on the 12V rail(s)?! Each Blade pulls about 10A at 12V, so if the PSU only delivers 15A at 12V there is a problem if you try to run 2 Blades on that 12V rail! Can you post a picture of the that sticker on your PSU?

For example, one of my PSUs has 560W in total, but only 348W at 12V which is sufficient to run 2 V2 blades (2x 120W). Connecting a 3rd would 'cause the PSU to overheat and shutdown!
You might look as well for a 12V DC LED-driver with about 250-300W to run your 2 blades, those LED-drivers are much cheaper than a PSU for your desktop!

So i need some help i have downloaded stratums proxy download and run it and pointed the blade to my pc which is running the proxy but on the proxy it just keeps saying clean=false and blade keeps restarting  can anyone help me what am i doing wrong on bf g miner the usb are hashing away nicely

now i get the following error

Failure: stratum.custom_exceptions.TransportException Failure:

hi i have a good power supply all wiring as to the pictures 4 black 2 yellow on a splitter. the blade powers up for about 2 min 15 sec and then restarts.
i have installed virtual machine with win 7 32bit and ran in mining proxy then directed the blades to my pc in virutal machine but still no luck. i use the mining proxy download from bitcoin.cz and use bat file with my details, i have bitminter,slush pool and btcguild tried all different setting but still same.
can any one setup a proxy for me (via instructions or remote)and i will give 0.2 btc as a reward 

Here's something to try:

For my example I'll pretend i'm connecting to Slush's pool, my worker is named 'myloginname.blade', and the password is 'testpassword', my computer is a Win7 32bit system with an IP of '192.168.5.5'.

Download BFGMiner - the best Blade Proxy

First step is to download the Windows7 BFGminer: http://luke.dashjr.org/programs/bitcoin/files/bfgminer/3.2.3/bfgminer-3.2.3-win32.zip

(revision: use this link to grab the latest copy for your windows build: http://luke.dashjr.org/programs/bitcoin/files/bfgminer/latest/ )

Setup the blade

Next, go to the blade's setup menu, make sure your gateway and both dns entries are correct (they usually point to your router). For my example they would point to 192.168.5.1 (yours will be different)

Third step is to point the blade to your BFGMiner proxy. I would set '8332,8332' for the ports (or 8339 if you have wallet software on the proxy computer). For the Server addresses I point to the windows machine, '192.168.5.5,192.168.5.5'. Finally I make up a username and password on the blade, something like 'myblade:mypass,myblade:mypass' (it shouldnt match what you use for your pool connection, nor should it match any other blade).

Press the 'update/restart' button on the blade.

Prepare the computer

Now to setup the BFGMiner software, it's easy to give a test run. First thing to do is make sure your Windows machine isn't  blocking port 8332 (or whichever port you are using). Easiest way to do this is to disable all firewalls (if only to test, you want to make sure to properly set the firewall up later). Once you're sure it won't block the port (or you tell it to unblock if it asks you), then move to the proxy itself:

Starting the proxy

Slush's pool url is 'mining.bitcoin.cz', and my pool worker info is 'myloginname.blade' 'testpassword'. Knowing this, and knowing I told the blade to connect to port 8332 of the proxy, here would be my command line:

bfgminer -o mining.bitcoin.cz -u myloginname.blade -p testpassword --http-port 8332

Debugging Issues

If BFG starts up and it connects to slush's pool, then you know the software proxy is working. You'll see a line which says 'HTTP server listening in port 8332', this lets you know the proxy is running. This means BFG is good to go. If it doesn't connect or doesn't run, then debug that first.

You should shortly after see a worker connect (usually shows up as PXY) and it'll start hashing. BFG will show connected to slush's pool with your worker settings. Wait 3 minutes if needed.

If you don't see anything connect, log into the blade and make sure it's pointing to your computer's IP on the proper port, and then hit 'update/restart'. This will force the blade to try again.

Let us know how it goes.