Very grateful for this! Even when i was a little too late to get the funds off before the hard fork, the wallet was still online and my transfer arrived home safely. Ty!

I noticed that the wallet is sometimes 'hanging'
When i have it open and browse around in the menu, or settings, it would suddenly become unresponsive. Immediately the connected clients stop mining, as they cannot rech the wallet anymore. But after a little while, it gets going again and clients normally resume mining.
Never encountered a crash or something. (AMD FX990 chipset/Win7 64 bit)

Strange, the coins that went to auto-stake went back to normal balance now,and added up with the amount that was there.
Is this because the coins still had to blend in the new fork?

"blocks" : 1600658,
"difficulty" : 0.03911764,

Things are progressing further, the chain advanced 21 blocks, and difficulty dropped with a whopping 0.04827646 in about 4h 20m

edit:
"blocks" : 1600669,
"difficulty" : 0.01605555,

And this happened in roughly 45 minutes!

"blocks" : 1600637,
"difficulty" : 0.08739410,

Solo'ing i actually found a block early this morning ... yay!
And also received about 67 coins of staking reward.

I did notice that my balance has moved to become a stake, which i haven't done myself.
I wanted to sit out the difficulties, and avoid my coins getting stuck... but how on earth did they move to become Stake by themselves?
I don't mind anymore now things are getting back on track,just looking for an explanation ;-)

yay!
"blocks" : 1600313
difficulty" : 0.09907569

"difficulty" : 0.37677652

1600295

Same here

I have been hashing there and this is how it looks;

[2015-11-08 17:51:50] accepted: 566/568 (99.65%), 5527.25 H/s yes!
[2015-11-08 17:51:51] Stratum connection interrupted
[2015-11-08 17:51:54] Stratum connection interrupted
[2015-11-08 17:51:57] Stratum connection interrupted
[2015-11-08 17:51:59] Stratum connection interrupted
[2015-11-08 17:52:02] Stratum connection interrupted
[2015-11-08 17:52:05] Stratum connection interrupted
[2015-11-08 17:52:08] Stratum connection interrupted
[2015-11-08 17:52:10] Stratum connection interrupted
[2015-11-08 17:52:13] Stratum connection interrupted
[2015-11-08 17:52:16] Stratum connection interrupted
[2015-11-08 17:52:18] Stratum connection interrupted
[2015-11-08 17:52:21] Stratum connection interrupted
[2015-11-08 17:52:24] Stratum connection interrupted
[2015-11-08 17:52:26] Stratum connection interrupted
[2015-11-08 17:52:29] Stratum connection interrupted
[2015-11-08 17:52:31] GPU #0: ASUS GTX 780 Ti, 5475.62 H/s
[2015-11-08 17:52:31] accepted: 567/569 (99.65%), 5523.77 H/s yes!
[2015-11-08 17:52:32] Stratum connection interrupted
[2015-11-08 17:52:35] Stratum connection interrupted
[2015-11-08 17:52:37] pool1.tumblingblock.com:2222 scrypt-jane block 1511046
[2015-11-08 17:52:38] Stratum connection interrupted
[2015-11-08 17:52:41] Stratum connection interrupted
[2015-11-08 17:52:43] Stratum connection interrupted
[2015-11-08 17:52:46] Stratum connection interrupted

[2015-11-08 17:54:03] thread 3: 1639 hashes, 62 hash/s
[2015-11-08 17:54:03] thread 1: 1914 hashes, 73 hash/s
[2015-11-08 17:54:03] thread 2: 2110 hashes, 80 hash/s
[2015-11-08 17:54:03] thread 4: 1871 hashes, 71 hash/s
[2015-11-08 17:54:03] thread 7: 1691 hashes, 64 hash/s
[2015-11-08 17:54:03] thread 6: 542 hashes, 20 hash/s
[2015-11-08 17:54:03] thread 5: 1653 hashes, 63 hash/s
[2015-11-08 17:54:03] thread 0: 16 hashes, 31 hash/s
[2015-11-08 17:54:10] thread 2: 518 hashes, 66 hash/s
[2015-11-08 17:54:11] accepted: 150/150 (100.00%), 454 hash/s (yay!!!)
[2015-11-08 17:54:19] thread 3: 1050 hashes, 65 hash/s
[2015-11-08 17:54:19] accepted: 151/151 (100.00%), 458 hash/s (yay!!!)
[2015-11-08 17:54:22] thread 6: 1245 hashes, 65 hash/s
[2015-11-08 17:54:25] Network diff set to 15
[2015-11-08 17:54:25] Stratum detected new block
[2015-11-08 17:54:25] thread 7: 1535 hashes, 69 hash/s
[2015-11-08 17:54:25] thread 5: 1486 hashes, 67 hash/s
[2015-11-08 17:54:25] thread 3: 371 hashes, 60 hash/s
[2015-11-08 17:54:25] thread 1: 1579 hashes, 71 hash/s
[2015-11-08 17:54:25] thread 2: 1103 hashes, 77 hash/s
[2015-11-08 17:54:25] thread 4: 834 hashes, 37 hash/s
[2015-11-08 17:54:25] thread 6: 157 hashes, 55 hash/s
[2015-11-08 17:54:25] thread 0: 1599 hashes, 72 hash/s
[2015-11-08 17:54:55] thread 4: 2270 hashes, 75 hash/s

This update you are talking about, is it another fork, or a wallet update?

Solo'ing, i have been having nothing but orphans since early this morning. Hope it will straighten out!

What would one need to do/change/update in order to succesfully solo-mine the new UTC2 fork?
Obviously update the wallet,but what else? Does the .conf need changes? Do i have to toss out all the peers,and add others? Change the port number? rpcport number?

What would one need to do/change/update in order to succesfully solo-mine the new fork?
Obviously update the wallet,but what else? Does the .conf need changes? Do i have to toss out all the peers,and add others? Change the port number? rpcport number?

Superb work once again!
I did notice though,that the DJM edition performs up to 500 KH/s better for the Lyra2v2 algo...on 780Ti's with identical intensity set(20)

Would like to request a Windows compilation for CCminer 1.6.6 pretty please!

Dear Epsylon, i was thrilled you;
Planned support for
    scrypt-jane (YaCoin, CopperBars, Pennies, Tickets, etc..)

Any idea about when to expect this? Can't wait tot see the improved speeds in these coins!
Keep up the good work ;-)

Open the console from within the Wallet and type "setgenerate true" to start mining.
(cpu mining,not sure if the mining automatically  restarts if you restart the wallet)
For stake minting just tick 'enable stake minting' in the overview. I checked for a command to do this but didn't notice one...

Ok...too bad. The UTC founders even recommend -s 1, which works fine for cudaminer...it's still catching blocks just fine, so no need to study them for so long.
Scrypt-Jane  seems profitable for somewhat older cards though, and CCminer is more capable to keep performance high. I wish it would work for UTC  
By the way, the same problem exists for your compilations of the CPU miner,it just cannot do UTC  
I'll give it a rest now...just hoping you can fix it someday... thanks for the swift support!

Edit:original CPUminer is also unable to mine UCT. Trying out yacminer for it,and this one does it flawless!
I figured it might have something to do with this timestamp thing?

Edit2:Pooler stated that is miner does not support UTC. So i guess that any fork without adding specific support,won't work.

When i tried -D i noticed something today... is the -s 10 supposed to be directly after my login name?
POOL 0: 127.0.0.1:44101 USER x -s 10
I would guess it is a scantime flag,but no matter what i set it to,the s 10 persists to be there.
And also,if i use the -s flag,the actual scantime does not change at all.

I'm not sure what to look for in the debug.log...
These are my CC and Cudaminer stats. CC was up yesterday all afternoon, Cuda was up last night.
Comparing the the yay and boo rates; i think something is going wrong somewhere!
I don't have a clue what to do/try to get this working properly.

CC

[2015-06-01 19:59:16] GPU #0: n=88220
[2015-06-01 20:00:37] found => 0008dd26 26dd0800
[2015-06-01 20:00:37] GPU #0: GeForce GTX 660, 303.77 H/s
[2015-06-01 20:00:37] accepted: 0/7 (0.00%), 607.15 H/s booooo
[2015-06-01 20:00:37] job 556c9dc2 target change: 91743000000 (11.0)
[2015-06-01 20:00:37] GPU #0: start=00000000 end=000fffff range=000fffff

Cuda
[2015-06-02 08:41:02] accepted: 11/11 (100.00%), 0.38 khash/s (yay!!!)

edit:
past 6 hour tryout using CC
[2015-06-02 14:44:22] found => 0000a4f6 f6a40000
[2015-06-02 14:44:22] GPU #0: GeForce GTX 660, 269.62 H/s
[2015-06-02 14:44:23] accepted: 0/13 (0.00%), 541.01 H/s booooo
[2015-06-02 14:44:23] GPU #0: start=00000000 end=000fffff range=000fffff

and another 6 hour tryout using Cuda coming up.