Merge commit 'b1dfc12' into update_avalon_20130524

Conflicts:
	README

README.GPU

@@ -407,6 +407,10 @@ Q: Can I mine with Nvidia or Intel GPUs?
 A: Yes, but their hashrate is very poor and likely you'll be using much more
 energy than you'll be earning in coins.
 
+Q: Can I mine on both Nvidia and AMD GPUs at the same time?
+A: No, you must run one instance of BFGMiner with the --gpu-platform option for
+each.
+
 Q: Can I mine on Linux without running Xorg?
 A: With Nvidia you can, but with AMD you cannot.
 
@@ -422,12 +426,24 @@ Q: My scrypt hashrate is high but the pool reports only a tiny proportion of my
 hashrate?
 A: You are generating garbage hashes due to your choice of settings. Try
 decreasing your intensity, do not increase the number of gpu-threads, and
-consider adding system RAM to match your GPU ram.
+consider adding system RAM to match your GPU ram. You may also be using a bad
+combination of driver and/or SDK.
 
 Q: Scrypt fails to initialise the kernel every time?
 A: Your parameters are too high. Don't add GPU threads, don't set intensity too
 high, decrease thread concurrency. See the README.scrypt for a lot more help.
 
+Q: BFGMiner stops mining (or my GPUs go DEAD) and I can't close it?
+A: Once the driver has crashed, there is no way for BFGMiner to close cleanly.
+You will have to kill it, and depending on how corrupted your driver state has
+gotten, you may even need to reboot. Windows is known to reset drivers when they
+fail and BFGMiner will be stuck trying to use the old driver instance.
+
+Q: I can't get any monitoring of temperatures or fanspeed with BFGMiner when I
+start it remotely?
+A: With Linux, make sure to export the DISPLAY variable. On Windows, you cannot
+access these monitoring values via a remote session.
+
 Q: Should I use crossfire/SLI?
 A: It does not benefit mining at all and depending on the GPU may actually
 worsen performance.