1. I get messages all the time:
"Error accessing the Mobileminer API (500)" & "Error accessing the Mobileminer API (400)"
"Error parsing the Coinchoose.com JSON API"
"Error parsing the Coinwarz.com JSON API"
Click the links in the notifications to see the issue. The APIs are returning errors. Not much I can do there. Sometimes CoinChoose.com is down. Sometimes CoinWarz.com returns API key errors if you go over your allotment. Again click the link to see the issue.
2. Also, I cannot get Multiminer (backend bfgminer) to mine on any GPU card at a decent hashrate without totally crashing my computer using the
following scrypt parameters (but I have no problem using cgminer).
-I 20,16,13 -w 128,128,128 --shaders 2048,1024,512 --auto-fan --auto-gpu --temp-target 85,75,75 --temp-cutoff 95,80,80 --no-submit-stale
--lookup-gap 2 --gpu-platform 0 --gpu-threads 1 --scan-time 60 --disable-rejecting
Try removing all the arguments and adding them back until things are stable. Mining with many different types of GPUs is fraught with frustration, failure, and poor performance. I have never once heard anyone else claim otherwise.
4. I can't seem to get remoting to work - I click on the remote computer node, but nothing displays in the main window. If I go to the remote
computer via Teamviewer, there is a message in the running instance of Multiminer on the (remote) machine stating "Multiminer remoting signature
verification failed."
All rigs need MultiMiner installed and must be on the same Intranet and Workgroup. If you are getting a signature failure that means they are not on the same Workgroup or you have assigned different passwords in the Perks screen.
5. Lastly, my biggest problem seems to be when either an exception occurs in either bfgminer or Multiminer and because of the JIT debugger I must
answer with a "Details", "Continue", or "Quit" button - I don't have this issue in say GUIMiner or GUIMiner-Scrypt. So is there something that I am
doing incorrectly here, or is there no centralized app specific error handler?
Nothing you are doing incorrectly. What you are seeing
is the centralized error handler. Report the error details on here or Github and then click Continue.