Quote from: joshuajaymiles on April 03, 2014, 04:55:22 AM

Quote from: Jondozer on March 29, 2014, 06:20:17 PM

Hi Nate,

Been really happy with MultiMiner for running my gridseeds on win8.1. It's my most troublefree option I've tested. I wanted to post this problem I've been having running 30 gridseeds in MM. It doesn't seem to occur when I have less than 5 - 10 running at once:

More often than not, when I start mining, 1 or 2 or 3 miners won't find shares, or they find 1 or 2 shares then stop. They are hashing full speed the whole time, even the ones not reporting shares. I've tried various combinations of "restart suspect miners" and "detect orphaned miners", but I rarely see an effect on this problem. The problem is not specific to any particular miner or com port, it jumps around. I hit stop, then start mining again... Previous ones that didn't work, are now working, new ones are now not working. This happens 50-75% of the times I start mining. Its obvious to me when the problem is happening, so I don't wait more than 10 mins usually. If they are all going to work, they tend to all find shares in the 1st 1-2 mins. This has been true for me at any diff setting I use at the pool (multipool.us). But, it only takes about 10 mins of stop/starting to get all of them to work at once, and once they do, they run for days!

thanks

This pic was at a high diff setting, hence the low amount of shares...
http://i.imgur.com/waF1mme.jpg

Can you please explain the processes you went thru to get multiminer working with your gridseed it would be highly appreciated!!!!!!!!!!!!!!

Was pretty easy.

1. Disabled digital driver signatures in win8.1.
2. Installed gridseed drivers, linked by Nate in this thread.
3. Updated mm, hit hardware scan, waited 5 mins.
4. Replaced bfgminer in users/myuser/local/multiminer/miner with Nate's pre-4.0 test version.
5. that was it.

Once each gridseed device has the proper driver showing in device manager (should say "gridseed orb" for each), hardware scan in mm should detect them. If it doesn't, try a restart of mm or a reboot, then repeat.

ugh: forgot a step...