to be honest, I don't think that last fork went very well. It was supposed to make everything more stable, but I see the exact opposite happening; wallets on all my computers/nodes are constantly falling off and it doesn't help with a reboot, but a full chaindownload including 15-20 Syncd restarts every time. Conf or no Conf, really doesn't matter or so it seems.
Every wallet recompiled up to 1.0.2.0, seemed to help in the beginning, but then I was back to being forktrapped again.
I see that the block explorer follows, this makes me a bit suspicious.. am I being poisoned by some notoriously bad nodes?
How about you guys, do you have any/different problems today or is it only me?
no Problems here and on 5machines either - staking and syncing - i alway clean the registry after de3leting something - although cleaning conf-file shuoldnt have an effect on this - but it works
Linux doesn't use that thing and Windows shouldn't be affected either, at least not when it comes to the blockchain.
I ended up using getpeerinfo from the machine I got up to where blockexplorer is, then I handpicked the updated peers and turned off 'listen' in the config. Like this:
listen=0
server=1
daemon=1
rpcport=24240
addnode=162.243.157.49
addnode=188.226.243.136
addnode=162.243.103.7
addnode=69.164.173.234:29374
addnode=93.86.88.215:22660
i still had to restart the clients twice, but now it seems to work and I have enabled 'listen' again, in hopes that the bad nodes won't come back to haunt us
