I would like to file a complaint. I never received my bribe from the FPGA factories.

In my client's GUI I show the highest of the two temperatures reported by BFL devices. Maybe you should do the same, using the highest value instead of average. This way, if one chip gets very hot that won't be hidden in a slightly higher average.

It should probably work with my mining client without modifications then. Thanks for the information.

It says custom code. Does it still use the same protocol over a virtual serial port to be compatible with the same mining clients that support BFL's products?

What about Z-Link, how is that exposed over the protocol?

BitMinter client v1.4.2beta1 is ready for testing.

New:

• Remove password from credentials dialog, mark worker name as optional.
• Support rescanning all ports repeatedly, not just probing new ports once.
    Useful for those with usb ports or devices that go haywire but begin
    functioning again a few minutes later. This option is available under
    "settings" -> "options" in the menu, under the "devices" tab.
• No more warnings about missing settings for Codebase and Permissions in
    java console of newer java versions
• Attempt to fix hashrate gauges not working for some users

Please check it out:

I don't have access to a device yet, so I can't implement support yet.


Anything can create blocks, even an old laptop solomining, or a much smaller pool than ours. But the time it takes on average will vary a lot.

We had a 99.9% CDF block. 1 out of 1000 blocks will be that unlucky, for any pool. What we need to push through unlucky blocks faster is more hashpower. So tell your friends to join

For mining, the user and worker names have been made case insensitive, and passwords have been removed.

This should help somewhat with all the users having problems authenticating. I see many are still having problems, though. As a reminder, your user name is displayed in the upper right corner of the website when you are logged in.

On the website there is now a warning on the login page about myopenid.com shutting down, and noone is allowed to sign up using myopenid.com anymore. If you are still using them to log in, please go to "my account" -> "logins" on the website (after logging in) and add another way to log in.

Update: Some bfgminer and cgminer users try to use only their worker name. You have to put the user name first, like username_workername. For example DrHaribo_MyWorker

Quick restart now of the mining service to get a new version in.

Hmm, I would have at least expected timeout errors.

Did you try it with bfgminer? It uses the same drivers, so should be quick to test.

Could you change the BitMinter vardiff from "20 SPM" to "20 SPM / User Defined" ?

Thanks

What happens if you try to start it? Anything in the log then?


Sounds like the USB ports and/or devices are not functioning very well. I'll have a new version of the client out soon that lets you configure it to keep trying the same COM port over and over indefinitely. That could be useful in cases like this.

BitMinter client does not log to the Windows event logging system, if that's what you mean. I'll have a new version ready soon that can rescan the same ports over and over. So if the device reappears but is still unresponsive for a while, it will still get picked up when it starts working again.

Or do you really have to reboot to fix this situation? "devices" -> "probe all ports"  doesn't help?

Which strange issues?

My jala runs with BitMinter client without a single issue.

It would be useful to know what you see in the log and what you need to do to get mining again.

What messages do you see in the log?

Easy mode isn't for boosting your earnings, but for reducing the daily variance in your earnings, if you feel a need for that.

Read this for more info: https://bitcointalk.org/index.php?topic=27062.msg3142713#msg3142713

What's the difference between red fury and blue fury?

OpenCL headers won't help, those are only for programming OpenCL. You need OpenCL capable drivers.

You probably have some open source drivers installed. As far as I know those still don't support OpenCL. You'll need proprietary drivers from AMD, assuming it is an AMD GPU.

I'm looking into all the stale namecoin blocks today.

So far I couldn't find anything wrong.

Namecoin stale work ratio is going up as some users turn on the new setting to disable flushing of stale namecoin work. I also see namecoin blocks are being created at a very quick rate right now. But I don't think that explains this many stales.

It may be that something was causing our blocks to be rejected / not propagated. Could be an old bitcoin bug, namecoin still has a bunch of those.

Anyway, just to let you know I am looking into it.

If you consider low fees important, then merged mining of namecoins should be important to you as well. They can make as much difference as the difference in fees, if not more. Ixcoins and Devcoins could matter too if someone was willing to buy them. But I sure wouldn't.