Thank you very much for that detailed explanation.  It has definitely cleared up a lot of my confusion!

Is this true of all power supplies?  When I check the specs for an Enermax 1350W supply, it shows a "peak power" rating, which is generally higher than the wattage rating of the supply (but within the efficiency).  I couldn't find the same specs for my Corsair AX1200.

Basically, I'm looking to see what the peak power is for the AX1200, which should be at least 1500W since it is 80+ efficient.

I'm trying to add another card to my rig and when doing so, the system becomes unstable and eventually crashes.  Consequently, I suspect that I may be drawing too much power from my power supply.  I have a Corsair AX1200 80+ Gold power supply; it has one 100.4A rail.  Under full load, this power supply is rated to be about 88% efficient.

When I measure power consumption at the wall, I read about 1050W.  What does this number represent?  Is it the power draw of the power supply, after which 924W are provided to the system?  Or is it the actual consumption of the system after taking into consideration its efficiency (1050 / 88% = 1193W)?

I really don't need to change the fan speed since I'm generally running at 100% all the time (one card runs at 50% though since it is well ventilated).  However, being able to collect the fan speed will allow me to write a script that will let me auto-tweek the speed based on temperature, if needed.

Currently, I am using MSI Afterburner to monitor fan speed.  This program, along with the ATI Catalyst program both report the speed as a percentage so there must be some API in place to retrieve this data; maybe I can pop a question to the RivaTuner author and ask which API he uses for this purpose.  Since I am not using the ATI program actively, my default fan control is in fact whatever MSI Afterburner chooses to do.

My goal is to ultimately use your tool without relying on MSI Afterburner to monitor and report fan speeds (if possible).

Several of us with 5770 and 6770 cards have reported that the program does not detect the fan speed (reports N/A).  What is the model number and manufacturer of your 5770 card?  A special model might be worth the replacement given the maintenance and automation headache I deal with now.

Thank you for your work!  Can you recommend a way to capture the sampled hashrate to a file in Windows?  The program emits various control codes to overwrite the previously printed hashrate, which makes piping the output in a file difficult to parse later on.

I don't have the link handy, but I recall reading that either Windows 7 SP1 or an updated Catalyst driver (11.6) increases the previous limit of four GPUs to eight.

I think this error text is omitted from the most recent version of ClockTweak.  I recall that after updating to v0.91b, the error is no longer rendered.

I'm using a 6770 @ 1.01Ghz with phatk 2.2.  When I run the memory clock at 300Mhz with the VECTORS option, I get 234.5Mhps.  However, I can't seem to reap the benefits of VECTORS2 or VECTORS4 at a higher memory clock (i.e. 1.2Ghz).  I've reduced the WORKSIZE from 256 to 128 and 64 and peak around 213Mhps;  with these options, I can only achieve between 204 and 213 Mhps.

Not for me.

Note that installing Catalyst 11.7+ will also install the APP SDK runtime for you.

What is the format of the "time" field that is present in the JSON output (root level field)?  For instance, a recently captured time value yields the number 1311642616.9349999.

I've given this a bit of thought and realized that this is pretty straightforward to do with an external script or driver.  The driver can query the core temperature via the clocktweak interface, parse the JSON results, and then set the temperature accordingly.

Unfortunately I don't have a card that allows fan control via clocktweak.  I'll likely be getting one soon and will post this script when tested.

What happens to these late/unconfirmed entries?

I somewhat eluded to this in a separate thread message, but I'm curious as to why my estimated rewards keep decreasing per round.  My miners are on 24/7 and once every two days may disconnect for up to 5 minutes due to network problems or maintenance.  However, I've noticed that my eligible share-count is decreasing, even though I constantly produce more shares in the round than the eligible count.

What is the relation between eligible and actual shares produced by a miner, and what factors affect the eligible share count?

Hi there!

Could you elaborate on how shares "eligible for reward" are calculated and how they differ from the total shares submitted by a user for the current block?  Also, the formula for BTC reward refers to submitted shares, and thus it is unclear why there would be a difference between submitted and eligible shares.

Thanks!

The banner at the top of the page states "New round starts in this Friday 20:00 (8pm) UTC", but the rules state "round ends when no one have placed their bet for a 24h".

Which one is it?

Driver version appears correct.  See http://www.techspot.com/drivers/driver/file/information/15407/ for more info.

• No change in hash-rate (4x6770)
• No change in temperature readings (when ambient room temperature the same)
• No longer need for dummy plugs or resitor hacks
• 100% CPU issue still present

How do I know which versions of the tools were installed for Win7 x64?  When I use the Catalyst Install Manager to see which components were installed, I see the following versions.

• APP SDK Developer 2.4.595.10
• APP SDK Runtime 2.5.684.213
• ATI Display Driver 8.872.0.0000

However if I query the display adapter properties, Windows reports a driver version of 8.872.0 with a date of 7/7/2011.

Does anyone else have these versions after installing the new toolkit?  For what its worth, I uninstalled the previous set of components, rebooted, and installed the new set.

Looks like the site that is providing the clock is unresponsive; the countdown iFrame isn't rendering.

Thanks for the info.   I will gladly return my refunded BTC once this feature is supported!

Another suggestion -- it would also be nice to have a user-defined fan-speed function a-la MSI Afterburner (i.e. table of temperatures v.s. desired speeds).