I TRY TO CONNECT to bitminter
but chilli

tell bitforce com72 error

This is a workaround version of BFGMiner until a new firmware update for the chilis

Here's a modified version of BFGMiner, I also included the driver inside of it as well that should fix your problem. (I don't know much about CGMiner though)

http://www.speedyshare.com/uKncp/BFGMiner-Chili.zip

Open up bfgminer.conf and change the Pool and Username to whatever you want (It currently uses mine so make sure you change it)
Run CDM v2.08.30 WHQL Certified.exe to install the correct driver for windows

Once you do both of those, just open up bfgminer.exe and it should read from the config automatically and start hashing for you.
If it doesn't see the Chili, all you have to do is keep BFGMiner open, unplug the USB, Plug it back in, press M then + then type all or auto and enter. It should find it.

Please note if it still isn't working then you need to exit BFGMiner, unplug you chili power, plug it back in and wait for all the lights to stop blinking. If you try to find the miner while it's "Booting up" it will have issues.
"Booting Up" is the two most right LEDs (Closer to the Power) blinking back and forth. Again once all the LEDs are not blinking anymore it should be ready to start hashing, start your BFGMiner and follow the above steps.

Let me know if this helps

Limitations

The Miner Protection Program is not a form of insurance, has no cash value, and cannot be sold, licensed or transferred by a customer. Customer will pay and be responsible for all taxes, duties and shipping for ASICs supplied under the Miner Protection Program. Additional ASICs supplied under the Miner Protection Program will be supplied only to the original purchaser, and may only be shipped to the same address as the original purchase. Nothing in the description of the Miner Protection Program should be read as a reliable or binding forecast of network hashrates, difficulty levels or other future events. The HashFast Terms of Sale sent to you (or if not sent to you, then found here: Terms of Sale) apply to the Miner Protection Program. “HashFast” as used above refers to HashFast Technologies LLC. HashFast™, the HashFast logo, Miner Protection Program™, and MPP™ are the trademarks and service marks of HashFast Technologies LLC.

Yes, lets do that.

Edit:  I am doing everything in my power to make this work out.

The NRE, which I believe is the most important and most critical, to the success of the project has been funded. This is a great time for the company and all of its shareholders.

Looking at the "DID NOT RECEIVE", just the first 5 holders make up 52.77% of those 11,427.
I'm guessing that those folks holding north of 500 shares are going to be pretty motivated
to get registered. My guess is that they are simply off the grid and haven't heard the news.

man, you fucking whine a lot.

If Ken succeeds at a) delivering a reasonable product to market which sells well, b) develops an exchange with some depth that allows for trading c) puts aside a few machines for ActM to mine d) continues to pay out dividends and increases the dividends accordingly, I will hunt Ken down and buy him the best steak which can be bought in a Missouri steak house and will thank him personally. And that is not a threat, that is a promise. Also, I will buy a steak for myself and will join him in dinner.

Also, when you sell a 350GH/s unit that later changes to a 400GH/s unit and out of the box with the base firmware manages to get 500GH/s for most customers, then that's not exactly a failure.

I got my first unit Oct 4th (4 days late). Sure one of the cards died and took a week to replace, but it STILL hashed at 400GH/s with only 3 cards. My other 2 units shipped shortly afterwards and they've all been solid. I'm not saying that KNC was or is perfect, but damn if they haven't set the highest bar for pre-orders.

waited by shares:
Verified: 68%
Failed: 11%
Did not receive: 21%

I also got my Chili nice but i think i need to slow it down because of high error rate is that possible whit next firmware?
I have to say really nice made board quality build 

BTB 0: 56C 450 1327mV | 14.37G/17.54Gh/s | A:198755 R:512 HW:3131 WU:245.0/m
BAS 0:  max 78C 3.27V | 60.88G/60.91Gh/s | A: 79914 R:266 HW: 553 WU:846.6/m
BAL 0:  max 52C 3.29V | 34.91G/35.10Gh/s | A: 13826 R:  0 HW:1610 WU:435.5/m

BAL=Chili

Regards Testit

Also, I'm curious if anyone here has bought anything on Crypto::Stocks?

What're your thoughts on Vircurex's implementation of an "project" exchange?

A guide to verify please some of us still need to by today.

Due to issues with people not having THEIR OWN bitcoin addresses on BitFunder, I will be postponing this weeks dividends in an attempt to help give people more time to get their address situated.

This means the dividends due to go out Oct. 19th and Oct. 26th will BOTH go out on Oct. 26th.

Tuesday, Oct. 22nd, I will be freezing LRM on BitFunder and taking the final asset list.  At this time I am requesting that all individuals send a signed message in the format detailed below between Tuesday, Oct. 22nd Noon and Thursday, Oct. 24th 11:59 PM Eastern Standard Time.

If you fail to send a signed message via email to labrat@labratmining.com by the end of the time specified, your dividends will be rolled over to the following week.

Thursday, Oct. 31st will be the cut off for the week following.

If you do not verify ownership of your bonds via this method by Thursday, Nov. 7th, your bonds and accrued dividends will be absorbed by LRM.

I am giving everyone plenty of warning, so make sure your address on BitFunder is one of your own.

Format for signed message must be as follows:

EMail Title:
BTC address (must be the address on the bitfunder asset list which is the same one you signed the message with)

EMail Body:
Bonds: # owned
Name: (Name on BitCoinTalk or BFL Forums, not your real name)
BTC Address: (Preferred address, may keep the same or change)


Message Signature: xxxxxxxxxxxxxxxxxxxxxxxx


The information in the body should be copy pasted from the signed message to your email, no leading or following spaces other than to separate the message signature from the message. No additional information necessary.

How to sign a message using blockchain.info:
- Log into blockchain.info
- Click on receive money
   - click on the actions button to the right of the address your using for labrat
   - click on sign message
      - enter email body as detailed in the post/s above
   - click sign message
   - copy "signature" output
Close "Sign Message" window

Using the message and signature, you can create a new email which you can send to labrat - this process proves that you have control of the BTC address.


How to VERIFY your message:
- Log into blockchain.info
- Click on receive money
   - Click on "More Actions" (bottom right - below the Balance)
   - Verify Message
   - Enter details
   - Click Verify - you should get a green "Message Successfully Verified" notice
Close "Verify Message" window

- Log out of blockchain.info if you are finished

The private key is what enables you to spend the BTC associated with the address.

http://bitcoin.stackexchange.com/questions/7536/how-do-i-export-my-private-keys-from-my-bitcoin-qt-client

http://www.blockrun.com/faq/how_to_sign

And a sample signed message that I posted yesterday:


------------------
Test message.  Ignore the dashes above and below when you copy and paste this to verify.

If you can verify this, you've probably figured out enough to sign messages with your own keys.
------------------

Signed with:  1grnbrg3Ea4t6bxHvQKRvorbBeLNDXv2N

Signature:  HKT07NvQ31Mz3mpMUD+38RSnEPa0/HyrE0zx8qse5THhq3SDrsBHVLt+UogA1bsxqwy+MhYkRy1Uc+ph+627bXI=



grnbrg.

Sooo...

We have today :


Verified : 146

Failed   :  42

Did not receive : 170

sounds like they made the right decision to eff over con and kano and just write their own firmware if you have a 5k machine that is that erratic.   lol.
karma

try to degrade and if possible destroy the competition so that their Jupiters/Saturns provide the ROI that they never will.

If it's 2 weeks late, that's probably a difference of 5-8 BTC or so per BabyJet. Profitability all depends on precisely how the MPP is executed (eg, how many extra chips, exactly when they'll ship, whether they ship to the entire batch all at once, whether customers will have to bear the costs of the additional chassis for chips 3-4, etc...).

It's incorrect to conclude that batch-1 customers are "officially screwed" without knowing these details (but maybe I missed them somewhere... links if so, please).

What if a super-duper Exa-hash machine shows up? 

The MPP coverage extends to up to 400% of the capacity purchased. For a Baby Jet, with a nominal 400 Ghash/s capacity, the MPP is limited to sending an additional 1.6 Terrahash/s of additional ASIC hashing capacity, for a total of 2 Terahashes!

We have received such a  positive response to the added benefit that the MPP will provide full modules for batches 2 & 3, that we have officially decided to extend this benefit to everyone covered by the HashFast Miner Protection Program™ in Batch 1.

This means that full modules will be made available to cover any MPP obligation to Batch 1 Baby Jet customers.  At that time, Hashafast will make empty rigs available for sale at competitive prices.

Offline here too. It has been like this for a few hours now.

Because 120,000 IceDrill shares will get you 1.2TH of world-class HashFast hardware on a newly-solidified mid-Nov delivery schedule (with no MPP)

With a first of December delivery, standing to mining.thegenesisblock.com, we will lose 75% of our "investment".
I can't even tell how i regret my bought.