Quote from: JohnWasser on February 22, 2014, 12:59:29 PM

Ran until just after 6 AM and crashed:

Code:

2014.02.22 [06:51] IOReactor error java.lang.SecurityException: Trusted-Only loader attempted to load sandboxed resource from https://bitminter.com/beta/httpcore-nio-4.2.4.jar at com.sun.deploy.security.CPCallbackHandler$ParentCallback.check(Unknown Source) at com.sun.deploy.security.CPCallbackHandler$ParentCallback.access$1700(Unknown Source) at com.sun.deploy.security.CPCallbackHandler$ChildElement.checkResource(Unknown Source) at com.sun.deploy.security.DeployURLClassPath$JarLoader.checkResource(Unknown Source) at com.sun.deploy.security.DeployURLClassPath$JarLoader.getResource(Unknown Source) at com.sun.deploy.security.DeployURLClassPath.getResource(Unknown Source) at java.net.URLClassLoader$1.run(URLClassLoader.java:358) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.addExceptionEvent(AbstractMultiworkerIOReactor.java:265) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.addExceptionEvent(AbstractMultiworkerIOReactor.java:274) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:396) at com.bitminter.gridnode.net.GridClientThread.run(SourceFile:309)

Hmm. This securityexception looks like a bug in older java 6 and java 7 releases that I have a workaround for. Basically a "should not happen" case.

Which java version is this with? Can you try upgrading to the latest Java from java.com and see if this problem goes away?

Quote from: ciaovince on February 23, 2014, 04:21:22 PM

I wanna ask if my desktop is applicable for this one.
Is it working or something wrong?

That old nvidia GPU is slower than most CPUs. And even fast GPUs aren't profitable anymore for bitcoin mining. Try ASIC hardware: https://en.bitcoin.it/wiki/Mining_hardware_comparison#ASIC

Quote from: suchysuchy on February 23, 2014, 10:08:21 PM

how's going work with overclock version?

Almost done, just getting sidetracked by other things.

Quote from: euro4321 on February 24, 2014, 12:54:42 PM

Hi, I installed the driver and I also replaced them with zadig, but on my Windows 7 pc the antminers u1 are not recognized. I already tried to replace the driver again and restart my pc but nothing happend. Hope you can help me

Use Zadig only for cgminer. For all other mining clients use normal drivers. For Antminer U1 use http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

Quote from: theweiss on February 24, 2014, 07:13:20 PM

Is the Beta worth switching to now? My rig has been getting bumped off more and more often and its starting to annoy me. When it goes down I have to start the client, hope it finds all my asics, assuming it does, hit start, hope they all start and if not...... start all over again. Every time I restart my computer or it randomly stops mining it takes me a good 15-20 minutes of open, close, start, stop, restart, disconnect, reconnect, etc.. to get my the miners all going again. It wasn't like this 2 or 3 weeks ago but the frequency seems to be increasing.

If it helps to know, I'm running 3 Butterfly Labs 30 GH/s little singles. When they are running, they run great but I think it might be the client (or the pool) that I've having issues with. I love the simplicity of the interface and the DR. seems to be really proactive with the pool but I hate the constant stops and the issue mentioned above.

Yes, the beta should not have this issue. It would be very useful if you can try the beta and confirm that the issue goes away. The more BFL devices you are mining with, the faster the issue will occur.