[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[newuser01]

Doesn't work - that is what i just downgraded from.

50 Burst to whoever gets me up and running within the next 15 minutes!

too many quotes..

which versions have you tried? with r9 280x

I have 14.4 installed now and it doesnt work.. downloading 14.6 and 14.7 and will try them both

[1715435872]

1715435872

[1715435872]

1715435872

[1715435872]

1715435872

[alphateam]

Ok there is tested config for 280x:

Code:

gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you.

You put 64 instead of 256?

I'll try 64 to see if i got more too

Replaced the openCL dll for the error - now Everytime - 'Display driver has stopped responding'. All at stock settings - no OC.

FUCK man this is bullshit.

I don't understand how a 280X works, but a 7970 and 7990 don't work. They are virtually the same core, minus a couple of minor differences.

Totally agree - Its the fucking AMD drivers I bet - Constant problems, one thing fixed, something else unknown gets broken.

What version of Catalyst is everyone using who has to WORKING 100%?

14.6

yea but you have a 290x no? better to write that since we are talking about 280X... and they are NOT the same..

If someone with 280x want to try to downgrade to 13.xx that might be a temporarily fix.

Hey guy, you are not alone, so calm down, if you're not happy, try to resolve the problem yourself

[SpeedDemon13]

New client Update 1.1.0

Backend is caught up to date with nxt 1.2.8.
Nxt new APIs are usable.
Hard fork on block 11800 to enable new nxt features(encrypted messaging, DGS).
UI is not yet updated for new features.

Move your burst_db folder from 1.0.3 into the new folder to avoid a resync. Db upgrade will take a few minutes though.

https://mega.co.nz/#!3xZ2DIwR!QQnamRK_JCz-QvFwb_A9gS6_tWCxAiFtVoqI8Unqlhg
sha256: f9d2a2d199993088eb9a03f1cb282ecbb36e704a4b7c609d5e878573752dad30

yes yes yes

That means Bittrex will be able to enable Burst on their market.

[HoldTheLine]

Doesn't work - that is what i just downgraded from.

50 Burst to whoever gets me up and running within the next 15 minutes!

too many quotes..

which versions have you tried? with r9 280x

I have 14.4 installed now and it doesnt work.. downloading 14.6 and 14.7 and will try them both

Using the HD 7990 - exactly the same as the r9 280x except I have two gpus - no difference.

I have tried 14.7, 14.6, and on 13.12 now. ALL crash to display driver has stopped responding. Usd driver sweeper before each new driver install. All GPUS at stock speeds and stock voltage.

Nothing changed in CCC.

[newuser01]

Ok there is tested config for 280x:

Code:

gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you.

You put 64 instead of 256?

I'll try 64 to see if i got more too

Replaced the openCL dll for the error - now Everytime - 'Display driver has stopped responding'. All at stock settings - no OC.

FUCK man this is bullshit.

I don't understand how a 280X works, but a 7970 and 7990 don't work. They are virtually the same core, minus a couple of minor differences.

Totally agree - Its the fucking AMD drivers I bet - Constant problems, one thing fixed, something else unknown gets broken.

What version of Catalyst is everyone using who has to WORKING 100%?

14.6

yea but you have a 290x no? better to write that since we are talking about 280X... and they are NOT the same..

If someone with 280x want to try to downgrade to 13.xx that might be a temporarily fix.

Hey guy, you are not alone, so calm down, if you're not happy, try to resolve the problem yourself

so do you have a 280x or 290x? xD

[coinits]

http://burst.cryptoport.io/acc/2715798095717378439 - Now there is some mining power!

Looks like he's 15.5% of the hashpower on my v2 pool.

Must be a small farm

[AnonymousEconomist]

New client Update 1.1.0

Backend is caught up to date with nxt 1.2.8.
Nxt new APIs are usable.
Hard fork on block 11800 to enable new nxt features(encrypted messaging, DGS).
UI is not yet updated for new features.

Move your burst_db folder from 1.0.3 into the new folder to avoid a resync. Db upgrade will take a few minutes though.

https://mega.co.nz/#!3xZ2DIwR!QQnamRK_JCz-QvFwb_A9gS6_tWCxAiFtVoqI8Unqlhg
sha256: f9d2a2d199993088eb9a03f1cb282ecbb36e704a4b7c609d5e878573752dad30

yes yes yes

That means Bittrex will be able to enable Burst on their market.

exactly. now is the time to buy!

[SpeedDemon13]

Ok there is tested config for 280x:

Code:

gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you.

You put 64 instead of 256?

I'll try 64 to see if i got more too

Replaced the openCL dll for the error - now Everytime - 'Display driver has stopped responding'. All at stock settings - no OC.

FUCK man this is bullshit.

I don't understand how a 280X works, but a 7970 and 7990 don't work. They are virtually the same core, minus a couple of minor differences.

Totally agree - Its the fucking AMD drivers I bet - Constant problems, one thing fixed, something else unknown gets broken.

What version of Catalyst is everyone using who has to WORKING 100%?

14.6

yea but you have a 290x no? better to write that since we are talking about 280X... and they are NOT the same..

If someone with 280x want to try to downgrade to 13.xx that might be a temporarily fix.

Hey guy, you are not alone, so calm down, if you're not happy, try to resolve the problem yourself

Better yet, everyone should help each other to resolve this issue. I'm semi-confused why this wouldn't work on 7970, since the 280x just has a couple little more features and better ram structure. But they are still the same process and mostly the same main core technologies.

[bipben]

Hi everyone,

After many hours of setup I finally made it. I have a 1Tb generation in progress and 3x100Gb already finished.
I would like to test the V2 pool but I haven't any BURST for now. Could someone send me 1 BURST to test it please ? Here is my address : BURST-YA29-QCEW-QXC3-BKXDL.

Regarding the plot generation, I found an OpenCL implementation of Shabal (https://github.com/aznboy84/X15GPU/blob/master/kernel/shabal.cl) that could be used to make a GPU version of the generator. I will try to work on it when I have some free time.

Regards

Hi everyone,

As promised I have been working on a GPU plot generator on the last few days. I made a little program built on top of OpenCL, and it seems to work pretty well in CPU mode. Unfortunately, I can't test the GPU mode as it requires a very powerfull graphic card (with at least 46kB private memory per compute unit, because the algorithm needs at least 4096*64 static bytes to store an entire plot).

Here is a preview you can test for now :
gpuPlotGenerator-src-1.0.0.7z : https://mega.co.nz/#!bcF2yKKL!3Ud86GaibgvwBehoxkbO4UNdiBgsaixRx7ksHrgNbDI
gpuPlotGenerator-bin-win-x86-1.0.0.7z : https://mega.co.nz/#!HJsziTCK!UmAMoEHQ3z34R4RsXoIkYo9rYd4LnFtO_pw-R4KObJs

I will build another release in the end of the day with some minor improvements (threads per compute unit selection, output of OpenCL error codes, improvement of the Makefile to generate the distribution directly).
I will also try to figure out another mean to dispatch the work between the GPU threads to reduce the amount of private memory needed by the program.

For the windows people, you can use the binary version directly.
For the linux people, just download the source archive, make sure to modify the OpenCL library and lib path in the makefile (and maybe the executable name), and build the project via "make". To run the program, you need the "kernel" and the "plots" directories beside the executable.

The executable usage is : ./gpuPlotGenerator <address> <start nonce> <nonces> <stagger size>
The parameters are the same as the original plot generator, without the threads number.

If you find bugs or if you want some new features, let me now.

If you want to support me, here are my Bitcoin and Burst addresses :
Bitcoin: 138gMBhCrNkbaiTCmUhP9HLU9xwn5QKZgD
Burst: BURST-YA29-QCEW-QXC3-BKXDL

Regards

Unfortunately, I can't test the GPU mode as it requires a very powerfull graphic card (with at least 46kB private memory per compute unit, because the algorithm needs at least 4096*64 static bytes to store an entire plot).

It's nice to see someone else working on this, since I seem to have failed in it.

Private memory is actually part of global on AMD cards, so storing it in private isn't any better than just using global for everything; it's local that needs to aimed for for the massive speedup. No AMD cards have more than 64KB local per workgroup, which makes storing it all in local impossible however.

I haven't tried your implementation yet, but on my own first attempt, I also used global on everything also, and the result was faster than the java plotter, but slower than dcct's c plotter. My 2nd attempt used a 32KB local buffer I rotated through for storing the currently being hashed stuff, however I couldn't figure out how to get it copied also to global fast enough, and the local -> global copy killed the performance.

You might be interested in those kernels here: https://bitcointalk.org/index.php?topic=731923.msg8695829#msg8695829

Thanks, I will look at your kernels to see if I can find a better solution.

Here is the new version. I reduced the amount of memory used from 40KB to about 1KB per unit. The only drawback is that it requires twice the global memory as before. I will search a mean to reduce this overhead later.
In CPU mode, it all goes pretty well (when no graphic card is detected).
The GPU mode is still kind of buggy on my graphic card (an old GeForce 9300M GS), don't know the exact reason yet. Sometimes it works, sometimes not. I will try to fix this issue tomorrow.

Here are the files :
gpuPlotGenerator-src-1.1.0.7z : https://mega.co.nz/#!iYFWAL5B!BvtmRQ5qGq4gGwjDglFNtDtNIX4LDaUvATBtClBdTlQ
gpuPlotGenerator-bin-win-x86-1.1.0.7z : https://mega.co.nz/#!aBVGBBQD!tBsRtb8VrHR12_anrFTrl41U0fPQu_OqFnxyi5nCyBY

For the linux users, the Makefile has a new target named "dist" that builds and copy/paste all the necessary files to the "bin" directory.

The executable usage is : ./gpuPlotGenerator <path> <address> <start nonce> <nonces> <stagger size> <threads>
<path> : the path to the plots directory
<threads> : number of parrallel threads for each work group

Found the "randomness" cause. NVIDIA is caching the kernel after the first build and rebuild it from time to time. By cleaning the cache, I can force the kernel build and speed up the debugging process.
I will notify you as soon as the crash cause is found and corrected.

Bad news guys. There is no actual "bug" in the implementation. Seems like the graphic card is beeing streesed too much by the shabal core, thus the driver is shutting down the kernel (there is a watch-dog timer for this purpose hard coded in the display driver to ensure that the display don't freeze too much). I will try to improve the whole algorithm and memory consumption to the needed graphic card power.

In the meantime, I found this thread (http://stackoverflow.com/questions/12259044/limitations-of-work-item-load-in-gpu-cuda-opencl) that speak about this particular issue. The available options are :
- If you have more than one graphic card, you can launch the plotter on the one that does not hold the display. There is still no option to select the graphic card in the plotter, but I will code it soon so that you can test it in a multi-GPU environment.
- You can try to turn-off the watchdog timer by following the provided link, but be CAREFUL, you may experience terrible display lags, or even full black screens until the plotter process finishes its work.

[newuser01]

Ok there is tested config for 280x:

Code:

gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you.

You put 64 instead of 256?

I'll try 64 to see if i got more too

Replaced the openCL dll for the error - now Everytime - 'Display driver has stopped responding'. All at stock settings - no OC.

FUCK man this is bullshit.

I don't understand how a 280X works, but a 7970 and 7990 don't work. They are virtually the same core, minus a couple of minor differences.

Totally agree - Its the fucking AMD drivers I bet - Constant problems, one thing fixed, something else unknown gets broken.

What version of Catalyst is everyone using who has to WORKING 100%?

14.6

yea but you have a 290x no? better to write that since we are talking about 280X... and they are NOT the same..

If someone with 280x want to try to downgrade to 13.xx that might be a temporarily fix.

Hey guy, you are not alone, so calm down, if you're not happy, try to resolve the problem yourself

Better yet, everyone should help each other to resolve this issue. I'm semi-confused why this wouldn't work on 7970, since the 280x just has a couple little more feature and better ram structure. But there are still the same process and mostly the same main core technologies.

I dont know if anyone has got it working on 280x yet.. he has 290x but for some reason he isn't saying that and its confusing a lot of people.. and then he goes whining at me because I correct him

sigh

[alphateam]

Ok there is tested config for 280x:

Code:

gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you.

You put 64 instead of 256?

I'll try 64 to see if i got more too

Replaced the openCL dll for the error - now Everytime - 'Display driver has stopped responding'. All at stock settings - no OC.

FUCK man this is bullshit.

I don't understand how a 280X works, but a 7970 and 7990 don't work. They are virtually the same core, minus a couple of minor differences.

Totally agree - Its the fucking AMD drivers I bet - Constant problems, one thing fixed, something else unknown gets broken.

What version of Catalyst is everyone using who has to WORKING 100%?

14.6

yea but you have a 290x no? better to write that since we are talking about 280X... and they are NOT the same..

If someone with 280x want to try to downgrade to 13.xx that might be a temporarily fix.

Hey guy, you are not alone, so calm down, if you're not happy, try to resolve the problem yourself

Better yet, everyone should help each other to resolve this issue. I'm semi-confused why this wouldn't work on 7970, since the 280x just has a couple little more feature and better ram structure. But there are still the same process and mostly the same main core technologies.

I dont know if anyone has got it working on 280x yet.. he has 290x but for some reason he isn't saying that and its confusing a lot of people.. and then he goes whining at me because I correct him

sigh

Ok guy, if you see my previous post, when i test it i'm saying that i have 290x, if you know that i have one, if only because you see it. This is not my fault if people just read the last post, i want to help, but i'm not here to be the father of some, so if people don't want to take 5 min to learn some post before that's not my problem.

[redsn0w]

This command :

Code:

gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

doesn't work on my windows 8 64 bit , and the prompt give me this usage :

Code:

Usage: ./gpuPlotGenerator <path> <address> <start nonce> <nonces number> <stagge
r size> <threads>

Can you help me , please ? 

[HoldTheLine]

Ok there is tested config for 280x:

Code:

gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you.

You put 64 instead of 256?

I'll try 64 to see if i got more too

Replaced the openCL dll for the error - now Everytime - 'Display driver has stopped responding'. All at stock settings - no OC.

FUCK man this is bullshit.

I don't understand how a 280X works, but a 7970 and 7990 don't work. They are virtually the same core, minus a couple of minor differences.

Totally agree - Its the fucking AMD drivers I bet - Constant problems, one thing fixed, something else unknown gets broken.

What version of Catalyst is everyone using who has to WORKING 100%?

14.6

yea but you have a 290x no? better to write that since we are talking about 280X... and they are NOT the same..

If someone with 280x want to try to downgrade to 13.xx that might be a temporarily fix.

Hey guy, you are not alone, so calm down, if you're not happy, try to resolve the problem yourself

Better yet, everyone should help each other to resolve this issue. I'm semi-confused why this wouldn't work on 7970, since the 280x just has a couple little more feature and better ram structure. But there are still the same process and mostly the same main core technologies.

I dont know if anyone has got it working on 280x yet.. he has 290x but for some reason he isn't saying that and its confusing a lot of people.. and then he goes whining at me because I correct him

sigh

Ok guy, if you see my previous post, when i test it i'm saying that i have 290x, if you know that i have one, if only because you see it. This is not my fault if people just read the last post, i want to help, but i'm not here to be the father of some, so if people don't want to take 5 min to learn some post before that's not my problem.

There is a variable that we are overlooking here team. Something is preventing it from working on Tahiti & Malta GPUs.

[alphateam]

Ok there is tested config for 280x:

Code:

gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you.

You put 64 instead of 256?

I'll try 64 to see if i got more too

Replaced the openCL dll for the error - now Everytime - 'Display driver has stopped responding'. All at stock settings - no OC.

FUCK man this is bullshit.

I don't understand how a 280X works, but a 7970 and 7990 don't work. They are virtually the same core, minus a couple of minor differences.

Totally agree - Its the fucking AMD drivers I bet - Constant problems, one thing fixed, something else unknown gets broken.

What version of Catalyst is everyone using who has to WORKING 100%?

14.6

yea but you have a 290x no? better to write that since we are talking about 280X... and they are NOT the same..

If someone with 280x want to try to downgrade to 13.xx that might be a temporarily fix.

Hey guy, you are not alone, so calm down, if you're not happy, try to resolve the problem yourself

Better yet, everyone should help each other to resolve this issue. I'm semi-confused why this wouldn't work on 7970, since the 280x just has a couple little more features and better ram structure. But they are still the same process and mostly the same main core technologies.

Do you try with other threads value, and other stagger size?

[burstcoin]

Hi everyone,

After many hours of setup I finally made it. I have a 1Tb generation in progress and 3x100Gb already finished.
I would like to test the V2 pool but I haven't any BURST for now. Could someone send me 1 BURST to test it please ? Here is my address : BURST-YA29-QCEW-QXC3-BKXDL.

Regarding the plot generation, I found an OpenCL implementation of Shabal (https://github.com/aznboy84/X15GPU/blob/master/kernel/shabal.cl) that could be used to make a GPU version of the generator. I will try to work on it when I have some free time.

Regards

Hi everyone,

As promised I have been working on a GPU plot generator on the last few days. I made a little program built on top of OpenCL, and it seems to work pretty well in CPU mode. Unfortunately, I can't test the GPU mode as it requires a very powerfull graphic card (with at least 46kB private memory per compute unit, because the algorithm needs at least 4096*64 static bytes to store an entire plot).

Here is a preview you can test for now :
gpuPlotGenerator-src-1.0.0.7z : https://mega.co.nz/#!bcF2yKKL!3Ud86GaibgvwBehoxkbO4UNdiBgsaixRx7ksHrgNbDI
gpuPlotGenerator-bin-win-x86-1.0.0.7z : https://mega.co.nz/#!HJsziTCK!UmAMoEHQ3z34R4RsXoIkYo9rYd4LnFtO_pw-R4KObJs

I will build another release in the end of the day with some minor improvements (threads per compute unit selection, output of OpenCL error codes, improvement of the Makefile to generate the distribution directly).
I will also try to figure out another mean to dispatch the work between the GPU threads to reduce the amount of private memory needed by the program.

For the windows people, you can use the binary version directly.
For the linux people, just download the source archive, make sure to modify the OpenCL library and lib path in the makefile (and maybe the executable name), and build the project via "make". To run the program, you need the "kernel" and the "plots" directories beside the executable.

The executable usage is : ./gpuPlotGenerator <address> <start nonce> <nonces> <stagger size>
The parameters are the same as the original plot generator, without the threads number.

If you find bugs or if you want some new features, let me now.

If you want to support me, here are my Bitcoin and Burst addresses :
Bitcoin: 138gMBhCrNkbaiTCmUhP9HLU9xwn5QKZgD
Burst: BURST-YA29-QCEW-QXC3-BKXDL

Regards

Unfortunately, I can't test the GPU mode as it requires a very powerfull graphic card (with at least 46kB private memory per compute unit, because the algorithm needs at least 4096*64 static bytes to store an entire plot).

It's nice to see someone else working on this, since I seem to have failed in it.

Private memory is actually part of global on AMD cards, so storing it in private isn't any better than just using global for everything; it's local that needs to aimed for for the massive speedup. No AMD cards have more than 64KB local per workgroup, which makes storing it all in local impossible however.

I haven't tried your implementation yet, but on my own first attempt, I also used global on everything also, and the result was faster than the java plotter, but slower than dcct's c plotter. My 2nd attempt used a 32KB local buffer I rotated through for storing the currently being hashed stuff, however I couldn't figure out how to get it copied also to global fast enough, and the local -> global copy killed the performance.

You might be interested in those kernels here: https://bitcointalk.org/index.php?topic=731923.msg8695829#msg8695829

Thanks, I will look at your kernels to see if I can find a better solution.

Here is the new version. I reduced the amount of memory used from 40KB to about 1KB per unit. The only drawback is that it requires twice the global memory as before. I will search a mean to reduce this overhead later.
In CPU mode, it all goes pretty well (when no graphic card is detected).
The GPU mode is still kind of buggy on my graphic card (an old GeForce 9300M GS), don't know the exact reason yet. Sometimes it works, sometimes not. I will try to fix this issue tomorrow.

Here are the files :
gpuPlotGenerator-src-1.1.0.7z : https://mega.co.nz/#!iYFWAL5B!BvtmRQ5qGq4gGwjDglFNtDtNIX4LDaUvATBtClBdTlQ
gpuPlotGenerator-bin-win-x86-1.1.0.7z : https://mega.co.nz/#!aBVGBBQD!tBsRtb8VrHR12_anrFTrl41U0fPQu_OqFnxyi5nCyBY

For the linux users, the Makefile has a new target named "dist" that builds and copy/paste all the necessary files to the "bin" directory.

The executable usage is : ./gpuPlotGenerator <path> <address> <start nonce> <nonces> <stagger size> <threads>
<path> : the path to the plots directory
<threads> : number of parrallel threads for each work group

Found the "randomness" cause. NVIDIA is caching the kernel after the first build and rebuild it from time to time. By cleaning the cache, I can force the kernel build and speed up the debugging process.
I will notify you as soon as the crash cause is found and corrected.

Bad news guys. There is no actual "bug" in the implementation. Seems like the graphic card is beeing streesed too much by the shabal core, thus the driver is shutting down the kernel (there is a watch-dog timer for this purpose hard coded in the display driver to ensure that the display don't freeze too much). I will try to improve the whole algorithm and memory consumption to the needed graphic card power.

In the meantime, I found this thread (http://stackoverflow.com/questions/12259044/limitations-of-work-item-load-in-gpu-cuda-opencl) that speak about this particular issue. The available options are :
- If you have more than one graphic card, you can launch the plotter on the one that does not hold the display. There is still no option to select the graphic card in the plotter, but I will code it soon so that you can test it in a multi-GPU environment.
- You can try to turn-off the watchdog timer by following the provided link, but be CAREFUL, you may experience terrible display lags, or even full black screens until the plotter process finishes its work.

You don't need to improve it to avoid this issue, just split it. One kernel for first half, one kernel for second half.

[newuser01]

Better yet, everyone should help each other to resolve this issue. I'm semi-confused why this wouldn't work on 7970, since the 280x just has a couple little more features and better ram structure. But they are still the same process and mostly the same main core technologies.

nobody has gotten it to work on 280x.. that is what we're working on

[SpeedDemon13]

Ok there is tested config for 280x:

Code:

gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

I'm getting arround 15k per minute. Great job. Thank you.

You put 64 instead of 256?

I'll try 64 to see if i got more too

Replaced the openCL dll for the error - now Everytime - 'Display driver has stopped responding'. All at stock settings - no OC.

FUCK man this is bullshit.

I don't understand how a 280X works, but a 7970 and 7990 don't work. They are virtually the same core, minus a couple of minor differences.

Totally agree - Its the fucking AMD drivers I bet - Constant problems, one thing fixed, something else unknown gets broken.

What version of Catalyst is everyone using who has to WORKING 100%?

14.6

yea but you have a 290x no? better to write that since we are talking about 280X... and they are NOT the same..

If someone with 280x want to try to downgrade to 13.xx that might be a temporarily fix.

Hey guy, you are not alone, so calm down, if you're not happy, try to resolve the problem yourself

Better yet, everyone should help each other to resolve this issue. I'm semi-confused why this wouldn't work on 7970, since the 280x just has a couple little more features and better ram structure. But they are still the same process and mostly the same main core technologies.

Do you try with other threads value, and other stagger size?

Yes, I've tried combo's of 1024 to 4096 staggers sizes. 64 to 256 threads values and all end up the same still. Maybe because the Hawaii has 4GB ram could be why it work, I might be wrong. The 7970 has only 3GB and 7970 is 3GB per gpu.

[alphateam]

So, because some blame me here is my full config for this computer

Windows 8.1 64
core I5
16gb ram
ATI 14.6

3 R9 290X in the computer (not oc)

Config that works :

Code:

gpuPlotGenerator.exe plots myaccountid 68847637 18500000 4096 256

9400 nonces minutes

gpuPlotGenerator.exe plots myaccountid 68847637 18500000 4096 128

14500 nonces minutes

gpuPlotGenerator.exe plots myaccountid 68847637 18500000 4096 64

14500 Nonces minutes

[alphateam]

This command :

Code:

gpuPlotGenerator.exe plots myaccount 68847637 18500000 4000 64

doesn't work on my windows 8 64 bit , and the prompt give me this usage :

Code:

Usage: ./gpuPlotGenerator <path> <address> <start nonce> <nonces number> <stagge
r size> <threads>

Can you help me , please ? 

Do you replace the myaccount in the command line by you real id?

[newuser01]

So, because some blame me here is my full config

Windows 8.1 64
core I5
16gb ram
ATI 14.6

3 R9 290X in the computer (not oc)

Config that works :

Code:

gpuPlotGenerator.exe plots myaccountid 68847637 18500000 4096 256

9400 nonces minutes

gpuPlotGenerator.exe plots myaccountid 68847637 18500000 4096 128

14500 nonces minutes

gpuPlotGenerator.exe plots myaccountid 68847637 18500000 4096 64

14500 Nonces minutes

nobody is blaming you.. you have confirmed it working for 290x multiple times and thats great..

now we(me) are working on 280x.. all I am asking is dont reply to questions regarding 280x when you have a 290x card because they are not the same and its not helping at all.

I feel like we can let this go now?

Im interested in hearing if there are any other gpus working or is 290x the only card capable of gpu plotting?