I believe this to be the case, based on statements he had made some time ago (prior to the October orders shipping, if I remember correctly).

I did have success with my RMA. After submitting my Oct 31 RMA for one broken H-board, Yvonne contacted me via email on Nov 12 and the replacement board shipped the next day. I received it yesterday.

One of my October (v1.2) H-boards died on me. 

Just a reminder: make sure you have a backup SD card ready to go. In power cycling to test the H-board, I managed to screw up the originally SD card that came with the starter kit to the point that the OS couldn't properly boot even on a fresh, new image. Having a backup will save you from some future headaches.

Add me to the mix on those seeing incompatibility mixing caps and capless. I've done no modding.

I just added three new cards to my original. With the original in the first slot, it slowly died and dropped to 0, and all the cards seemed to get pretty hot. I moved it to the last slot, and everything seems to be running good (about 3 hours stable now). Although the original card is slower, it was always around that speed, so I don't think it is being negatively affected by the capless cards.

Got my 3 new H-boards today. Unfortunately, I corrupted my SD card (red light only problem on attempted boot). Hoping that a reimage will fix it.

Update: Email from MBP - they were in fact shipped together. Thanks Team MBP.

Received a shipment notification from FedEx.

I have one H-board as order #20x, and two H-boards as order #35x. I'm wondering if they were shipped together (no update yet in MBP order history).

Orders #20x and #35x have not shipped yet. Though there is still time to ship today.

No news on orders #20x or #35x thus far.

I was just basing that off Dave's latest comments.

So I guess no shipping today. Slightly disappointing, but let's hope they ship soon.

The products in the MBP store are all listed for October delivery. I believe that when Dave is talking about November, he is referring to the time after which all of the October orders are delivered.

Welcome back to the forums everyone.

I saw this post by buzzdave on Reddit yesterday.

"We expect to begin receiving product in the week of the 14th."

Full post: http://www.reddit.com/r/BitcoinMining/comments/1nu0ey/bitfury_megabigpower_us_market_shipping_update/

So after missing ~6 hours of mining time due to the BTC Guild DDoS, does anyone have a method for setting up backup mining pools for these devices? Or is this something that we will get with v2 updates?

No ping on BTC Guild. Guess it is still recovering from the DDoS.

Thanks, using port 3333 did the trick. Any reason as to why their site says to use port 8337?

I had posted this in the support thread. I'm hoping to get a quicker response here.

I had been using BTC Guild since I had gotten my miner, and everything was fine up until last night when BTC Guild got hit with a DDoS attack. Since then, I am not able to connect to BTC Guild or any other pool (I've tried 50BTC, Eclipse, and Bitminter). Does anyone have any suggestions? Thanks.

I'm still having trouble with my Bitfury. It had been working fine on BTC Guild for a few weeks prior to the DDoS. My erupters have been fine for a few hours now. Should the Bitfury be working or I am locked out while the pool is still recovering? Thanks.

I had been using BTC Guild since I had gotten my miner, and everything was fine up until last night when BTC Guild got hit with a DDoS attack. Since then, I am not able to connect to BTC Guild or any other pool (I've tried 50BTC, Eclipse, and Bitminter). Does anyone have any suggestions?

EDIT: Eclipse MC worked when using port 3333 instead of 8337. Good enough for me, thanks tom99.

Not too surprising. The mine isn't up to 100 TH yet. I wasn't expecting October shipments until the mine is at its full 200 TH.

http://mining.bitcoin.cz/news/pool-entering-new-era

I'd say avoid Slush's until 2.0 goes up.