I'm using 0.5 wallet on Windows 7 X64 it gives me error of loading blkindex.dat.
Move your wallet safely out of your
datadir then delete the contents of that folder. Resynch from scratch, wait until synced, stop client. Copy old wallet back into
datadir, restart client.
No, it's not specific to Slimcoin, here's a not-too-dissimilar report from Sterlingcoin:
Just opened the wallet again. It went up to 8 connections for a while and now it's down to 2 only. I'm also staking.
I suspect the other 6 nodes disconnected from you, perhaps for your wallet "misbehaving". This could be from your copy of the blockchain being in an unintentional fork or trying to submit incorrect block height PoS blocks. The new snapshot will solve this,
http://Sterlingcoin.org/SterlingcoinSnapshotAt746004.zip (~500 MB)
In the future, you may find it helpful to only enable staking after your wallet is fully synced. You can disable staking by leaving the wallet locked or using "staking=0" in your sterlingcoin.conf file.
You can disable staking in Slimcoin by setting
reservebalance=0 in your slimcoin.conf file or as a command line option.
At present
you cannot disable mint-by-proof-of-burn in Slimcoin which in all probability is having the same effect on syncing as does enabling mint-by-proof-of-stake, i.e. causing the client to generate a unique-to-it stake/burn block in mid-synch which then results in the client starting its own private fork and failing to sync further, so ...
Move your wallet safely out of your
datadir then delete the contents if the folder. Resynch from scratch, wait until synced, stop client. Copy old wallet back into
datadir, restart client.
Good luck in your mission Jim, should you choose to accept it.
Cheers
Graham
P.S. Yes, it
would be useful if Slimcoin had a nice, fresh convenient bootstrap.dat for people to download. I have added a
dumpbootstrap routine that I filched from CLAM:
https://github.com/slimcoin-project/Slimcoin/commit/c7adc1f652f7f8831c6373da48b68b77765a7b82(I was quite pleased with myself until I discovered that the Windows client, rather predictably and somewhat infuriatingly, just ignores the generated bootstrap.dat file. Ho hum, more work to do.)