Thank you very much for you cool miner.

I using v.9.3. for dual mining ETH+Pasc and notice this strange behavior:


I.  In the log I see some enonce but miner send to pool other one:

11:30:46:478   10f0   PASC: put share nonce 30909ba enonce 275
11:30:46:497   10f0   PASC round found 1 shares
11:30:46:515   330    PASC: 05/28/17-11:30:46 - SHARE FOUND - (GPU 2)
11:30:46:515   330   send: {"params": ["yfife5.wm", "1002", "3237643030303030", "592A8AB3", "ba090903"], "id": 4, "method": "mining.submit"}

Here enonce= "275" but send "27d00000" (if convert to ASCII).  And it happens all time. Send "enonce + 8" (275+8 = 27d)

II. But the worth thing is when enonce growth out of 3 digit. The miner continue send (and calculate) only first 3 digit:

11:34:03:392   139c   PASC: put share nonce 30909ba enonce 27c8
11:34:03:392   139c   PASC round found 1 shares
11:34:03:408   330    PASC: 05/28/17-11:34:03 - SHARE FOUND - (GPU 0)
11:34:03:408   330   send: {"params": ["yfife5.wm", "1002", "3237643030303030", "592A8AB3", "ba090903"], "id": 4, "method": "mining.submit"}

You can see here the same nonce as in previous example, but enonce must be "27c8" but sending the same "27d00000". (actually miner works correct 27c8+8 = 27d0, but when adding "0000" it looks like "27d" + "00000").

So can you add "0" before enonce, like this "000027d0". It will increase real hashrate by 1/16 (6.25%), because now we calculate the same hashes for different enonce (each hash for enonce "xx" equal hash for enonce "xx8").

Also, will be good, to add solo mining mode for Pascal.