Most of the guides and things you find for cgminer will work for bfgminer.  The commands and things are the same.  So if you cant find what you are looking for under bfgminer, look for cgminer.

Read this today. Maybe this would work.

https://bitcointalk.org/index.php?topic=257486.0

Im sure there are adapters out there, but all the ones I have ever seen have been for running a 1x pci-e card on a pci slot.  Trying to run something with a pci-e x 16 on it, havent seen that.  Could you theoretically daisy-chain a pci to a pci-e 1x and then 16x to 1x riser to go into that?  All the connections would line up, but would it actually run and be seen by Windows, thats a complete other matter.

the FPGA readme that comes with cgminer gives a sourceforge link to download zadig.

Okay, a few questions. 

1)  Are you solo mining?
2)  What schedule are you actually trying to achieve here?  CGWatcher has a function that actually will let you set a mining session at specified time and run for a specified amount of hours (i.e. start at 11pm and run for 8 hours every during the work week).

I noticed in your config file that you have "gpu-engine" listed twice.  You need to delete the one that goes "gpu-engine" : "0",  This sets your gpu engine as default, but you are using auto-gpu to throttle your gpu between 700 and 1000 to reach a target temp of 80 so you might have been confusing cgminer.

One last thing, when you are running it from task scheduler, are you targeting the shortcut, or the .exe directly?

Looks to be just front panel cables to a case, nothing special.  You just need something that will carry a signal.  Doesnt have to be a JTAG cable specifically.  We used a IDE cable that just hung off the side.  Worked just fine.

Possibly, but it could also be the fact that the difficulty is so high that 2Mh/s isnt going to make any affect.

So you are using 3.1.1. and using zadig to change your drivers?  That might be your problem.  The change over to using winusb drivers didnt come until version 3.2.0, back in 3.1.1 it was still using FTDI drivers which are the normal drivers installed when you plug in your erupters.  So....either use zadig to go back to stock drivers, or upgrade cgminer to something 3.2.0 and above and see if that works.

I would say it is probably, almost 100% because you arent using a powered hub.  Get that and try and if you are still having problems then look further.  Only other thing would be if you are declaring the correct COM port.

1) Do use a powered hub.  The erupters require a good amount of power and normal ports on a motherboard just dont quite do it.

2) What versions of BFG and CG miners are you using?

I think that means you had a share from either another pool, or from a previous solved block that is not valid.

I would use either btc-e.com or coinbase.com, I currently use coinbase.  You can have them draft money directly out of your bank account, then use that cash to buy coins.

Are you mining simply off of the integrated graphics on your Mac?

Good luck with getting donations, most people see this and immediately yell scam.  Plus with difficulty, people are hording coins.

Have you tried buying coins on an exchange and then using those coins go buy your erupters?

Are you using a config file? Or all on the command line?  Post which ever one you are using.

We used the pre-compiled firmware from ckolivas that he posted here.

https://bitcointalk.org/index.php?topic=244235.msg2602712#msg2602712

I used to do this, and when I did I found I had to make a .bat file and told task scheduler to run that.  Running cg directly from task manager is flaky.

On a side note, what about using an app like cgwatcher?  You can use task scheduler to run that app, and it will load cgminer and all the arguments for you, as well as watch it and restart mining ever if needed.

Cant remember seeing if you posted it, but did you flash your Jala?  I did mine, but i never measured the increased in consumption and have been too lazy to unplug it and test.

Ive seen that config file before, its just a sample one.  First off, you dont need all those extra spots because you only have 2 video cards, this config is for 4 cards.  So, I would suggest 1) Change your config file to only be for two cards (ex for gpu-engine, it should be "0-985,0-985",   Do that for all the other lines as well.  And 2) Your intensity for GPU 0 is "d".  That may be the cause of it.  Change that to be "9" like the other settings, save, restart CGMIner, and see what happens.

Almost like clockwork I would have to restart my Pi every 2 and a half days. Finally got sick of it and just hooked up my Jalapeno to my desktop.