keep it simple. one thread.

Yep, its in the readme's and/or the Top Post of this thread.

--------------------------------------From Top Post-------------------------
The output line shows the following:
(5s):1713.6 (avg):1707.8 Mh/s | Q:301  A:729  R:8  HW:0  E:242%  U:22.53/m

Each column is as follows:
5s:  A 5 second exponentially decaying average hash rate
avg: An all time average hash rate
Q:   The number of requested (Queued) work items from the pools
A:   The number of Accepted shares
R:   The number of Rejected shares
HW:  The number of HardWare errors
E:   The Efficiency defined as number of shares returned work item
U:   The Utility defined as the number of shares minute

 GPU 1: 73.5C 2551RPM | 427.3/443.0Mh/s | A:8 R:0 HW:0 U:4.39/m

Each column is as follows:
Temperature (if supported)
Fanspeed (if supported)
A 5 second exponentially decaying average hash rate
An all time average hash rate
The number of accepted shares
The number of rejected shares
The number of hardware erorrs
The utility defines as the number of shares minute

The cgminer status line shows:
 TQ: 1  ST: 1  SS: 0  DW: 0  NB: 1  LW: 8  GF: 1  RF: 1

TQ is Total Queued work items.
ST is STaged work items (ready to use).
SS is Stale Shares discarded (detected and not submitted so don't count as rejects)
DW is Discarded Work items (work from block no longer valid to work on)
NB is New Blocks detected on the network
LW is Locally generated Work items
GF is Getwork Fail Occasions (server slow to provide work)
RF is Remote Fail occasions (server slow to accept work)

Thanks, that's precisely what I do. The top thread always points to the announce for the latest release, and I do go to great pains to write human readable changelogs so people can see what has changed, but that does not give the full history. I certainly don't have the time to maintain a wiki.

Version 3.1.1 worked fine, but I went ahead and compiled it anyway out of interest. The segfault is from libpdcurses when writing    applog(LOG_NOTICE, "Probing for an alive pool");
It might be specific to windows. I left a stacktrace on http://pastebin.com/5eMb5dsf

About having seperate threads - I agree it doesn't make sense to start new ones if it means you have to monitor them all. A bug tracker may be easier to work with than forum threads though.

I can send you an anker 10-port USB 3.0 hub if it will help you track this down faster... I'd like to switch away from 3.1.1 but can't just yet...
PM me if interested.

Hence why we have direct USB in the new code... it uses a lot less CPU because the ftdi driver is very inefficient.

I'm seeing about 60% on each of two cores. But the cpu is only runniing at 1Ghz so i don't expect much from it. running 4 erupters and a Radian 6570 GPU.

I only got 10Mh/s out of the on board GPU so i put a small video card in the PCIe slot. getting a whopping 85Mh/s on the video card now. heh.

http://www.amazon.com/gp/product/B007ZT1FAI/ref=oh_details_o05_s01_i00?ie=UTF8&psc=1

Are you sure -S noauto at the end is all I need?  Remember the linux version is different from windows.  Windows required me to input all those COM's one at a time.

Also, could somebody possibly just help me with the command lines on what to type?  You say switch to the zadig driver, but the README is really confusing to me.  95% of what is talked about in there I'm sure doesn't relate to me.

3% on a raspberry pi

Running 9 x cairnsmore fpga's via a couple of USB hubs.....