Quote from: joblo on December 19, 2017, 02:37:17 PM

Quote from: joblo on December 19, 2017, 02:46:36 AM

Quote from: 4ward on December 18, 2017, 07:17:38 AM

One thing I couldn't resolve is that neoscrypt always fails to run (same in My9bot's version)

I can look into this now.

I suspect the neoscrypt problem is related to its use of asm. It is controlled by a NOASM
compile flag. I didn't find any hooks for Windows so it should compile the same as Linux.

It works with the old mingw environment used to build previous binaries. The only obvious
difference is the mingw host, The old way was built on a Windows host, the new ones cross
compiled on a Linux host. I don't know if that makes any difference.

Digging deeper will be very time consuming and considering neoscrypt performance on CPU
it's hardly worth the effort, especially if the result is to disable ASM and performance drops.

An easy test would be to recompile with -DNOASM and see if it works and how the performance
compares with the old mingw build. I'll leave it up to you if you're interested. The results will
help determine how to proceed.

-DNOASM didn't solve the issue, it still fails.

Code:

[2017-12-19 18:11:05] 4 miner threads started, using 'neoscrypt' algorithm.
[2017-12-19 18:11:05] Starting Stratum on stratum+tcp://neoscrypt.mine.zpool.ca:4233
[2017-12-19 18:11:05] Binding thread 0 to cpu 0 (mask 1)
[2017-12-19 18:11:05] Binding thread 1 to cpu 1 (mask 2)
[2017-12-19 18:11:05] Binding thread 2 to cpu 2 (mask 4)
[2017-12-19 18:11:05] Binding thread 3 to cpu 3 (mask 8)
[2017-12-19 18:11:07] Stratum session id: 67d8d8d809e8d6ce65058b9626f51cf4
[2017-12-19 18:11:07] Stratum difficulty set to 512
[2017-12-19 18:11:11] DEBUG: job_id='347' extranonce2=00000000 ntime=123a395a
[2017-12-19 18:11:11] neoscrypt block 2011810, diff 110.548

But you are right, this algo is definitely not the best performer, so I don't know if its worth investing much time in it