Topic: Newbie problems with BFGminer 4.4.0 on Windows (Read 1112 times)

SiLabs driver will assign a new COM # each time you add another U2.
  Some people prefer to use bat files but BFG miner has the ability to write its own conf. file built in. You just need to navigate to S_ettings and select [W]rite config file. I choose to then hit [Enter] and use the default filename.
  If you unzip BFG Miner to C or D then you can open cmd prompt and use cd\bfgminer-4.4.0-win32 [Enter]
  then type bfgminer  [Enter].
  The miner should launch. It may take a few moments and will pause with the add device press M + but if you leave it alone it will continue, this is not the only way to start the miner but it works. Antminers may or may not always be detected when you open BFG Miner but I have not had issues adding them from the console once BFG miner has started.
   You could cd\bfgminer then launch with   bfgminer -S antminer:all --set-device antminer:clock=x0981  and let the user and pool info fill in from the config file you saved before. Then save the conf file in settings again using the default filename. I know, extra step, but this has worked for me in the past when I had trouble getting the program to launch the antminers at start up.
 As far as the reinit after using [Q]uit  I have not run into those issues using the config file as I am but it will sometimes take longer to start again. Just don't try to [R]estart BFG Miner from the S_ettings console in BFG Miner, it has been broken option for a long time and usually freezes the CMD Prompt for some reason if it doesn't crash and close.
 I have Win 7 and Win 8.1 and up to 30 Antminer U2+'s but I have not tried mining with XP in a long time.

The more I read, the more I conclude that as long as I'm using the CP210xVCP driver, added Antminer U2s will be individually identified via COM numbers and so WinXP Vs later revisions isn't an issue.  If someone knows this to be incorrect, then please tell me about it, otherwise, guess I'll just wait and see.  It's just that I prefer to learn about issues before I hit them rather than after!

Started a week ago with GUIminer running my GPU and ordered a  used Antminer U2.  From reading decided to go with BFGminer, downloaded 4.4.0 and spent some time reading online.  Setup a powered USB hub Friday and today the U2 arrived.  Took a number of tries to get it detected and running but now it is.  However, I'm having presumably newbie problems with BFGminer (WinXPsp2 32bit with CP210xVCP driver).

1) I can't get it to start from a .BAT file, always prompts for a URL.  The name of my BAT file is "antminer.bat" (also tried "bfgminer.bat", no change) and I've tried locating it in the same directory as bfgminer.exe (D:/bfgminer) and also in C:/.  Neither works.

(Hmm, I've realized my dumb goof with bat file startup, but that still leaves items 2 and 3.)

2) I can't get it to start as a command line where I use the same command string as in my .BAT file.
"bfgminer.exe -S antminer:all –-set-device antminer:clock=x0981 -o stratum+tcp://stratum.bitcoin.cz:3333 -u [worker] -p [password]", it always says "Unexpected extra arguments in the command line".

(Hmm, the "--" is turning into "^" somehow, needed to delete and retype those characters, but still leaves item 3.)

3) If I [Q]uit BFGminer while it's running the U2, afterwards it's unable to reinitialize with the pool -- appears to be some kind of timeout elapsing, probably from the pool end (not sure how long, perhaps 20 to 30min?).  That implies it's not closing cleanly.  How does one close BFGminer cleanly?

(Hmm, seems like [D]isabling the U2 before [Q]uiting solves the problem. Any further insights?)

PS. Questions regarding how to bring up more than one U2 may well be following when I've a second, perhaps an issue of serial number assignment for system differentiation?  Would appreciate inputs on this topic.

Thanks much for any help!