FWIW, the difference between CGMiner 2.3.4 and BFGMiner 2.3.4 consists of (with the rename filtered out) 3252 added lines, and 392 removed. If it was just a rebranding, I'd have a much easier time figuring out what caused that administrator requirement on Windows. :/
I was really hoping I wouldn't have to report this, but.....
I am seeing a slight performance increase (over CGMiner 2.3.3....although I haven't tried CGminer 2.3.4 yet).
More specifically, the overall Shares/Minute average, over my small GPU-Only mining farm (
dually confirmed by the increased hash rate my pool is reporting back to me, based on submitted shares).
My 5 rigs at home are all running Win7 x64 and it's not specific to any one GPU platform, SDK or driver version.
I've got a 6xxx GPU rig running SDK 2.4/CAT 11.12, a 6xxx/5xxx mixed GPU rig running SDK 2.4/CAT 11.12 as well as a few 5xxx GPU rigs running SDK 2.1/CAT 11.12.
I should also note that I didn't have any problems running BFGMiner (
no 'admin' error as described above). I used the same BAT files/shortcuts to launch it, as I was using for CGMiner 2.3.3 and just changing the executable's name in the file. Same settings/overclocks/temp/fan/API and everything....no problems.
My Web Monitor (using the API output) still all works and again, the only difference I noticed was that my GPU Voltage output (
DEVS/GPU Voltage) was spitting out a value to 13 decimal places, but still worked 100% with nothing changed.
As all my rigs are headless & Windows 7 x64 based. They all login automatically (
using an administrator privileged account, although NOT the actual Administrator) and hit the desktop without interaction, so that I can access each rig's UltraVNC server for management without having to worry about running it as a service.
Again, nice job Luke.
(it hurt to say that....lol)bitlane.