Shipping to Ohio isnt all that bad, for a nominal fee I would do it

That is a question I have no answer to.  I only have ever mined BTC so never had a need to looking to doing LTC and running dual. Its basically and linux/debian distro so if there is a way to do that then probably.

At one point in my playing around with getting my Jalapeno running I had installed cgminer 3.1.1 and 3.2.1, so I am guessing if you can install two different cgminers you can.  You would have your standard on that begins when BAMT starts automatically, and then other you would have to manually start and enter your info each time.

**8/16/13** - Removed instructions and condensed them down into the below thread so everything is together.

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

I use CGWatcher as well but I have never had to use an API argument. I thought by default it was set to allow all to access and you only used api-allow to filter it down to certain things if you didnt want everything to access it, but I could be wrong.  Only thing I have now that is running with CGWatcher is my Jalapeno.

Now, judging from those errors, maybe the issue can be solved with dummy plugs. Seems to not like to access the cards unless they are being used, so maybe a dummy plug would trick the system into thinking it was being used?

Maybe try an older SDK like 2.6.

Might have to flash the firmware.  This will reset all settings as well. If that doesnt work, then I suggest contacting Avalon.

Check out their Wiki.  Gives all the pertinent information, as well as setup instructions.

https://en.bitcoin.it/wiki/Avalon

Since its based on OpenWRT, have you tried doing a factory reset with the button?  Hold down for 30 seconds, let it wipe all settings and start over new like it just came off the line.  Then you can use the regular setup instructions from Avalon like you had just received it from them.

Why are you compiling cgminer yourself when there is an already compiled Windows version available?  All you would need to do is install your catalyst drivers, set your parameters, and go.

Put it around the $50/GH and you will have me interested.

This is most likely due to the fact that after 3.1.1 cgminer changed USB drivers from FTDI to winusb.  If you want to run a USB ASIC in cgminer above 3.1.1 then you have to use zadig to change over your diver association and then cgminer will see your unit(s).

In the README it tells you that its a USB driver issue and that you have to use zadig to change from FTDI drivers to winusb drivers in order for you Jally to be recognized and run.

Probably because starting with 3.2.0 cgminer rewrote its USB instructions and if you dont have the right usb drivers installed it doesnt play well.  Solution for most people are to either downgrade back to 3.1.1 or to switch over the minepeon to BFG and use it as they can keep it updated and they still use the old set of drivers.

Happens more often that you think.  Not necessarily fires, but burnt circuitry and what not, especially overclocking video cards.  I mostly see it in LTC mining as the extra push for VRAM overclocking seems to be what causes most of the problems.

As the total bitcoin network hash rate is increasing, blocks are being found at a faster rate.  What you are you looking at right at that time frame is when a lot of ASICs starting coming online from BFL and other companies, making the total network hashing power exponentially increase.  Therefore burning through 2016 blocks was happening much faster at the difficulty that was listed at that time.  In order to compensate for this increase total hashing across the network, the difficulty increased ~20% as now it was harder to find shares with so many high hashing equipment coming online. 

Back in the day, you could have a GPU that could has at ~400Mh/s and in the beginning days could solo mine and find blocks by itself.  Now we are in the days of 100+Gh/s ASIC miners and having to compete agasint those.  This makes mining and finding a block and getting the reward much more difficult, but also means, assuming "luck" isnt completely horrible, finding 2016 blocks can happen in half the time under the right circumstances.

I've never used anything other than cg or bfgminer besides back in the day when I first started out and I used guiminer for a bit.  My suggestion, post this question in the official cgminer thread and see what they have to say.

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

Well I personally have never mined LTC, and have always down-clocked my Gigabyte cards memory so I guess I never have had an issue.  But you are right, from a design stand point, they are very flawed.  I was merely giving him some info that may benefit him in the future.

If you are not using the pci-e x16 slots on your motherboard, and are using the pci-e x1 slots and running your cards off risers, there are two different types, powered, and non-powered.  This is how you  are able to see people say they are running 5 cards off one board, they are using risers. 

The biggest difference is that powered risers give more power to the bus of the cards, the powered risers have an additional molex connector attached.  This is important in ltc mining as the power to overclock your vram on your cards for ltc mining comes from the bus.  While btc power comes from the pci-e power connectors from the psu since thats what is powering the gpu overclock, thus you dont need powered risers to run them.

Just tried the new version, and it is not starting my version 3.1.1 of bfgminer.  Going to try the updated version of bfg and report back to see if watcher is able to start it.

*EDIT*

Okay, for some reason I dont know if it is bfg, or watcher, but something no longer likes config files. So I had to dump all my old settings and go with command lines.  Seems to be working now.

Sounds like someone lives in Texas.  Used to work with a guy who would throw that line around all the time.  Made me laugh every time.