Try a different pool then.
https://bt.irlbtc.com/view/14085.0
and see if that makes a difference.

Do you know how long the primary pool has to be down before cgminer will switch to the backup pool in failover-only mode?  And is there a setting somewhere to adjust it?

Thanks.

I have a pull request up to tidy this up and maybe fix your problem:
 https://github.com/ckolivas/cgminer/pull/215
If you come to FreeNode IRC #cgminer I'll give you a windows executable compiled with that pull request
My IRC name is kanoi (and I'm one of the two ops in #cgminer - ckolivas (aka conman) is the other of course)
.. and we can see if it sorts it out for you

Just pulled code into the cgminer git tree that adds support for the modminer FPGA.

https://bt.irlbtc.com/view/79637.0

I am running Win 7 x64.

My guess is the problem depends on different 32bit implementations on the 64bit windows versions and the bug that I guess might be in different Windows 64bit->32bit Serial/USB code.

e.g. in Win7-64bit there is a limit of 8 USB devices when running 32 bit (XP) mode
(according to http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/windows-7-xp-mode-usb-limit/ff50b790-6e6e-47e4-8f48-5727896f5aeb )
xDGDZEx had the problem when he hit 7 or 8 BFL's (not 9)
https://bt.irlbtc.com/view/80852.0
The first problem there actually suggests it may even be opening and closing valid devices multiple times (but it also happens on invalid devices)

The only change relevant to FPGA in the versions he compared was that Icarus opened the devices first (and failed) then BFL opened the devices but ran out before it got to 8 devices.
The previous version worked where it did the BFL code first so the BFL's all opened successfully

I came to the uncertain conclusion that the problem was that the open code in windows seems to sometimes identify bitforce:\\.\COMn as a USB name and allocated some resource to it but then failed to open it (as expected) but returned an error without always releasing the resource
I was hoping for xDGDZEx to test the change but I've not seen him in IRC since I last PM'd him.

The code change was to not attempt to open the invalid device names (and hopefully solve the problem if it is a windows bug)

That same code change worked for you bitpop so again I'm guessing it's related to a USB count issue in your different version of windows.

Either way, the change isn't a problem in any way (it simply stops doing the "expected to fail" opens) and if that solves the problems for some people - good

Is the mod miner included in the build script yet?
Nothing in the readme about the build option for the modminer, nor in ./configure --help.

Edit: Ah, needed to do a re-autogen.

At the top of the output, "cgminer -h" will tell you that when you compile in ModMiner (MMQ) support.
e.g. for me on linux:
 cgminer 2.4.2b
 Built with GPU bitforce icarus mining support.
but the git version would say
 cgminer 2.4.2
 Built with GPU bitforce icarus modminer ztex mining support.
If you compile in ModMiner and ZTex also (like the binary releases will have)

If you mean the API - yeah I'll do that tonight.

I recently reinstalled my windows 7 64bit, I have Catalyst 12.4 official and SDK 2.7 installed.

When I doubleclik cgminer.exe nothing happens, did I miss a step needed to install properly cgminer, it did work before reinstalling windows 7 but not anymore.