hmm..the files are generated just a few hours ago, and my best deadline with the java miner using these files was around 5min an hour ago. is it possible that the miner doesnt like to be a 32bit miner? ^^
dcct-miner/dcct-miner: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID[sha1]=0x09410d96b865886551d02c360cae703322d5336f, not stripped
Are you using the correct passphrase?
passphrase? where? i used the tutorial here:
http://burst-pool.cryptoport.io/howto.html there's nothing written about a passphrase when using your miner. I just checked back with the java miner, and instantly got much better deadlines:
{"result":"success","deadline":756214}
{"result":"success","deadline":824025}
...
edit: ah, I guess you meant the passphrase when generating the plots? yes, should have been the correct one.
i just checked the code of the miner, and the extremely high deadline that has been submitted can be explained with the fact, that the pool does not have a limit (well...nearly):
if(best < 5000000000000ULL)
so I still don't understand why the java miner finds much better and more deadlines, and why the C miner does only show ~320GB from ~620GB
edit: i'll try again and let it run a little longer...