Where you can specific the COM ports. But for this it would be the ttyUSB ports.
I can't just use the 'erupter:all' because I also have a BFL unit and it will not start.
You can specify individual devices as well:
bfgminer -S erupter:\\.\COM3 -o -u etc
Thanks, hopefully this'll force BFGminer to see the BFL as what ever it sees it as. And the erupters as BEEs. ....really hate that 20% HW error rate.
you can specify com ports, or if you wanted you could also just run a seperate instance of antminer for the bfl and for the antminers. I find that works best in alot of instances (of course I even seperate individual ants that perform better to give them the 2.1gh clock speed etc lol) I have found bfgminer to be a champ with multiple instances, wherein cgminer simply crashed alot or created conflicts in most multiple instance scenarios.
I can confirm that running multiple instance of BFGminer is very doable and stable... I have seperated my BEs from my ANTs (AMU) and BFL... now the BE's are actually submitting hashes since they are only running difficulty 4, when I had them mixed in with the other mining units and I was running difficulty 16, they were always taking too long to process and would submit stale shares