Yes, increasing the size of the command window (before starting cgminer) has helped people with similar symptoms.

(EDIT: I've seen you already got it working.)

To set a larger size as a default, hit start->run and type in cmd.exe<enter>; then click the black system icon in the top left corner of the command window that pops up. Choose 'properties'. The important thing here is the 'Layout' tab. Specifically Window Height. Set the Window height to 40 or 50. You can change the font as well to make it fit your monitor better. Click ok. You may then exit the command window. Any command window you open after this will come up with its new size.

There is a difference in how different versions of cgminer behave with Singles. 2.3.6 worked perfectly for me with up to 15 Singles. I since moved to 2.4.1 (and now 2.4.2) and have found that, using the same command line and command window layout size, 15 Singles crashes it. 2.4.1 are happy with 10 Singles, but not 15. 2.3.6 works fine with 15.

I don't know what broke between cgminer 2.3.6 and 2.4.1. It also behaves differently when Singles go offline; 2.3.6 just exited (which was good) but 2.4.1 and 2.4.2 just mark them as 'OFF' and do not exit (bad).

I use 2 6870s at dynamic and 9 for intensity. I definitely wouldn't recommend putting it above 9 because it sends your rejects through the roof.

Oh cool, thanks.

Run two (or more) cgminers on the one computer?
7 (or less) BFL's in each cgminer

Edit: N.B. for the API, each miner will need a different --api-port

Just for my reference and for others wondering about this. It seems they only clock back up slowly after the temperature reaches (target temp. - hysteresis ).

For example if the target temp is 70 then they will only start clocking back up when reaching 64.5.

This was requested, and seemed logical. Would it be more acceptable to you, if it automatically reenabled the devices when they're plugged back in?

cgminer 2.6.2's display worked very well with 15 devices under Windows. 2.4.1 does not. I don't know if this change was intentional or an accidental side-effect, but it certainly is frustrating to find that something which *used* to work before is suddenly broken without notice.

I have a PC with a 'bucketload' of devices. Under Windows I can conveniently remotely connect to it via Remote Desktop, or VNC, or Live Mesh, or TeamViewer ... I don't use the API because I've no need for it. If cgminer's display remains broken for 'bucketloads' of devices, at least I can run multiple instances. Inefficient and inelegant, but we're not in an aesthetics contest here.

So in the 'grand scheme' of things, it doesn't really matter.

Not only a coding GOD but a good sense of humour too !

2.4.2 works very well for me in LINUX.

Windows <- there's your problem. Are miners still using Windows ? LOL.

If a Single is unplugged, it won't be detected when the new cgminer starts... so you get the same thing, minus the ability to enable it later. Is there something else going on here?

A most enlightened response. Thanks. All I can do is try my best within reasonable effort.