4.9.2 was just released, it should work with the U3 stuff now (per the changelog, I haven't tried it yet).

You didn't try very hard, it is literally the first link that comes up if you google "linkedin eric mu".

-S antminer:all also causes 5.2.0 to hang.  -S antminer in the bat file will launch, but bfg doesn't see the U3 with that.  Is there something I can put in place of 'all' that would direct the scan to look at, say, only USB devices?  It's something about the "all" that's freezing 5.2.0 on this system.

-S noauto in the bat file works in so far as bfg will launch with that command in the file, but then I have to use device manager in 5.2.0 to scan auto for the nanofury sticks, so really no point.  I tried "Enter target:antminer" in the device manager, but no luck.

I guess I'm looking for something like what's in the device manager "For example: erupter:\\.\COM40" that would be tailored toward the U3.  Something less encompassing than "all" that will id the U3.

I've never used GitHub, I'll see if I can't figure out how to report a problem there. Judging by my go with bisect, it may take me a round or two to figure it out.

The latest version, 5.2.0, has U3 support, although there are mixed results between users.

tl;dr How do I scan specifically for the usb U3, and not "scan all"?

Did some more digging, I've determined it is the -S command in my batch file that causes 5.2.0 to hang.  If I remove the -S command it starts just fine.  If I try add the device from within bfg (M and +) and scan "all", the program hangs.  If I do M + and "auto", it gives No new devices found, which follows from the readme that says the U3 won't autodetect.  It seems the bug is related to scan all, whether done via batch file (-S all and/or -S antminer:all) or from within the program itself.

If I remove the -S/--scan command then 5.2.0 starts just find and hashes away with the nanofury sticks, they don't need to be scanned for apparently.

So something on this particular computer causes the device scan to go on and on and on and on and the U3 needs to be scanned to be seen... anyone have advice how to work around this?  Or how I could scan specifically for my U3 and not have to "scan all"?  Like how do I tell it to only scan the USB devices?

I wonder why -S all works in 5.1.0, but hangs in 5.2.0 on this box.  Weird and frustrating!

Since this is using the U3 stuff in cgminer, you may want to use cgminer 4.9.0.  4.9.1 does not recognize the U3, it's a known bug, so don't know if that will affect this stick.

You probably also want to add --suggest-diff 1 to your .bat file so that your stick starts at a reasonable pool diff.


Is there a way to do this without using Zadig?  I have a computer that refuses to complete the Zadig installation, so I need to find another way to do what Zadig does.

As KnC brings their new facility online this fall things are going to go up and up.   

Uninstalling the app was the only way to get the information unremembered.

Well get back to work, damn it!
 

Crush your enemies. See them driven before you. Hear the lamentations of their women.

There's no cost effective way do get 500kW to a residence.  Any power company will laugh at you, residential service lines likely wouldn't support that, and you'd be stupid to pay residential rates for a 500kW service.

You could drop $100,000USD and get your own generator:
http://www.cat.com/en_US/products/new/power-systems/electric-power-generation/diesel-generator-sets/18331379.html

But you'll never have peace or quiet, your neighbors will hate you, and it's probably not legal to have it running 24/7 in a residential zone.

So this wasn't as easy to clear up as initially expected.  I cleared all data in both browsers on my phone (chorme and firefox), I cleared all predictive text data, deleted my keyboard and reinstalled, googled "clear autocomplete android" and tried every suggestion I could find and nothing would clear the remembered data from this field.  I finally uninstalled the app from my phone and reinstalled it and it finally cleared, so I posit that this autocomplete information is stored by the app itself, and not the phone's browser or user dictionary or anything else.

Looking forward to those collapsible panels and ckpool solo being a supported pool, sent a few more btc to you last night since I use this app several times a day, every day!

Got it, clear as mud now.

I always have my doubts, but I may let a little coin ride here for a bit and see what happens.

Paper will not ignite until 233*C, card board higher, if your exhaust air is approaching those temperatures you have a bigger problem.

Many professions around the world are "title protected", meaning you cannot simply assume the title and use it professionally.  I'm pretty sure anyone can call themselves anything they want in private, but if you use that title professionally then you can get in trouble.

For UK, try here to start: https://www.naric.org.uk/uk%20ncp/individuals/Regulated%20professional%20titles%20and%20designatory%20letters.aspx

Brought one U3 to the same location as my stick miners, stopped 5.1.0 that was running the sticks, started 5.2.0 for the U3 like I did at home and it just hangs at the "Started" line.  So that issue is not related to the stick miners, it's related to this machine.  I'll run through bisect this afternoon and see if I can't find a build that works on this box.

Here are the bisect results, several builds worked (meaning the launched and started hashing with the sticks), several did not (they just hung at the "Started..." line):


Would love to get 5.2.0 working at this location, as this is where I want to use my U3s.  Thanks!

You do not understand how monthly interest rates work.  You don't get a month's worth of interest if your money has only been there 1 hour.  You leave it there for a month, you get the monthly interest rate.

See link I posted above, it's a little higher than 2% recently, but not much:

Seems to be a lot of that lately on this pool, back to back (and more) solves.  Crazy luck!