trying this in vm

If you have pulled this mining before now, you will want to refresh your local copy. It was originally written as a V1 pool, but was having issues. It is now a V2 only pool.   Tested on http://burst-pool.cryptoport.io.

So, this is for V1 pool mining only or can it solo mine? What's the exact steps to compile this in Windows? Or will you compile it in the future? Does this have any optimizations for plotting and/or mining?

So for now the solution would be to run an instance for every drive and one master that would monitor all the other?

The threads will work at the file level, so if you have 2 threads it will process 2 plot files at the same time... If you just have 1 plot file for the miner having more than 1 thread wont do much.  But I wouldn't necessarily recommend having more than 1 thread, just because it will make your hard-drive go a little crazy with seeking, so might actually slow down the overall time of processing a block.

https://github.com/mrpsion/burst-mining-system/releases/tag/1.1

Here is a link to the "release" jar is attached.

So the {f4eb42d8-d1e4-3676-8a3f-5f9879758ca6} is the plot file id that lines up with the UUID you see in the UI... in hindsight i probably should have just left its representation as the usual address_noncestart_number_stagger id.

If a new block is announced before it has finished scanning the plot it will tell you it stopping mining the plot.

The pool situation is a bit of a mess.  Urays pool actually uses a completely different api and mining methodology, so currently the v1.1 jar only will mine urays. I am putting in some code to try and detect between the two types of pool, and switch mining modes accordingly.  If you had built from source earlier today its probably running the official pool version code I had in there, but after some testing i found that it might not actually be getting any shares accepted by the pool, even if the pool is returning the success message, so I pulled that code, and left in Urays, which actually tells you if you are being rejected.

The burst pool scene is a little chaotic at the moment, so I hope everyone bears with the community as we all try and adjust.

thanks for the good work

Ok. I recompiled with the revised version and now it works. The compiled version you pointed to does not want to work.

Yes. You just need to tell it to do so. In the readme you will find everything you need