Well, thanks to the help of people on this forum, I've managed to get the Blue Furies running alongside the Block Erupters:
This is the miners which have been hashing now for over seven hours:
There's a couple of things to point out, first, many thanks to kabopar who nailed the target strings required in this post:
For those of you that want to run both BE's and BF on same pc (Win 7):
BE's (Block Eruptors) running under an instance of bfgminer 3.2.1, with the following shortcut (text in Target field of shortcut)
C:\temp\bfgminer-3.2.0-win64\bfgminer.exe -o [pool url] -u [user name] -p [password] -G -S erupter:all --icarus-options 115200:1:1 --icarus-timing 3.0=100
(change to suit the location of your executable)
Once the BE's are running, run a separate instance of bfgminer for BF. I used
either bfgminer 3.2.0 ('special', with the BF driver installed per the support thread)
using bfgminer32 ver 3.2.0 and the batch file of the style
bfgminer.exe -S "BF1:all" -o [pool url] -u [user name] -p [password]
(this works ok w/o H errors)
or 3.5.1, using a batch file with the content:
bfgminer.exe -S bigpic:all -o [pool url] -u [user name] -p [password]
(works ok but with increasing H errors)
Had both running on the same old laptop for a few days now (with BF going on and off for different tests and s/w configurations).
Cheers
Now for the record I'm using Win7x32 and the first part of the post above, using BFGMiner 3.2.1 was spot on, the key point here perhaps being that you might have to change your existing target string to
-S erupter:all as this was critical for me as my previous
-S all did work with all the BE's but it wouldn't allow the second instance of BFGMiner to run and separately recognise the Furies. If you take a look at the screenshot, the miner on the left of the pic is BFGMiner 3.2.1 and it runs normally with the BE's with very low hardware errors, under 1%.
I couldn't get the second part of kabopar's instructions to play out properly, I downloaded BFGMiner 3.2.0 but for some reason it just would not recognise any of the Furies, no matter what I did. A point worth mentioning is that thanks to these comments below, I was able to ensure that I had the right driver installed for BFGMiner:
Zadig doesn't install drivers. It associates drivers with devices. When you run Zadig, you're binding the USB device with USB drivers.
In brief, if the device shows up as a USB device, it's probably configured for CGMiner. If it shows up as a COM port, it's probably configured for BFGMiner. I switch between them quite often for testing.
In short, I had problems with the encrypted nature of the drivers linked to on the OP, so this link above from tk1337 allows you to download the files to work with BFGMiner.
This Zadig download link provided by ssinc should, we assume, help with CGMiner:
Epinnoia identified that I was incorrectly using the Zadig drivers, which, as mentioned are more likely to be for CGMiner. So check your devices, you do need to have them show up as COM ports if you're planning to run BFGMiner, using the unencrypted driver link from tk1337 is far easier and then install them individually per Fury device.
For the second instance of BFGMiner, I could only get 3.5.1 to work and even then it was a bit temperamental so you might have to switch on and off your hubs and/or restart the BFGMiner to get the Furies to be recognised.
A strange thing happened, with the 3.2.1 running the BE's, I couldn't get 3.5.1 to recognise the BF's but then when I opened a second instance of 3.5.1 (even although the first instance of 3.5.1 failed to recognise the Furies) the second instance of 3.5.1 did successfully recognise the Furies. So try that if you're getting no-where: Three windows of BFGMiner, first 3.2.1 for the BE's working, then 3.5.1 for the BF's failed, then 3.5.1 for the BF's succeeded. No idea why and at 1.30am after messing around with these dang things for fourteen hours, I really didn't care.
So taking another look at the screenshot above, the BFGMiner on the right is 3.5.1 and as you can see BPM 4 probably requires to be replaced or reflashed as it has the same problem that other people have mentioned hashing only at around 0.5GH/s. Another thing I will check is the psu as I've some of the original 4A bricks but also bought 5A bricks after the original 4A bricks burnt out, so it could be that there's not enough power being supplied to that particular BF, but I'd have thought that three of them (as I have three BF's per hub) would display the same reduced hashing but maybe not. I'll move things around and see if I can increase its capacity.
The other point worth mentioning is that most of the BF's are struggling to get to the lower end of the anticipated 2.2 - 2.7 GH/s and one of the big selling points for me was the reported ability to reflash the units and do some software overclocking, that's needed more than ever now to boost their performance. Some brave folks have talked about hardware overclocking, changing resisters and so on, but that's not something that interests me at this point in time, I'd like the product as advertised to deliver on the promised performance specifications, so with some luck there will be progress made in that direction.
Things have to be kept in perspective though and I'd like to thank BPMC for all their hard work in producing the Blue Furies. Even running at 2.1ish GH/s it's still miles better than 333 MH/s that the Block Erupters hash at and although the delivery date was stretched somewhat past their anticipated 'first or second week in October', the units have been delivered, they are hashing and full credit must be given to a pre-order pretty well-executed all said and done. Yes, there could have been more FAQ or Q&A assistance however from what I can gather BPMC were working flat out to deliver the units and I think all of us would prefer to have some teething problems with the units delivered in hand, than a shiney website with no units delivered. So thanks guys, big tick for Big Pic
-----
Summary:
First run BFGMiner 3.2.1 with this target string to start your Block Erupters:
D:\
[your file path]\bfgminer-3.2.1-win32\bfgminer.exe -o
[your pool and port] -u
[your username] -p
[your password] -G -S erupter:all --icarus-options 115200:1:1 --icarus-timing 3.0=100
When the Block Erupters are hashing, run BFGMiner 3.5.1 with this target string for your Blue Furies:
D:\
[your file path]\bfgminer-3.5.1-win32\bfgminer-3.5.1-win32\bfgminer.exe -o
[your pool and port] -u
[your username] -p
[your password] -G -S bigpic:all --icarus-options 115200:1:1 --icarus-timing 3.0=100
You may have to reboot, turn hubs on and off or even open a second instance of 3.5.1 (keeping the first instance of 3.5.1 open).
-----
Thanks to everyone who has helped make this happen, all at BPMC, Dabs for handling the group buy and FedExing them like a champ, Luke-Jr for rushing out 3.5.1, you guys for all your comments on this thread and a special thanks must go to kabopar for providing the breakthrough info
Now... I only have to work on getting that error rate down... later for that though, it's time to sit back and enjoy the light show
Good luck everyone.
I posted above how it is possible to hardware overclock. Firmware over clocking might be available in the future I just don't want to cause more issues that would then need to be fixed.
