I just deleted the "txleveldb" folder (it's sitting in the trashcan, so it hasn't been permanently deleted), but now that the wallet is open, and downloading the blockchain again, it shows 0.00 HBN!!!  Will my balance return, or did I do the wrong thing?

No problem letting it go. It is always best to create your own index file rather then use someone else.

The reason is still a bit of a mystery to me. It has to deal with how leveldb closes and opens files, and when it flushes to disk. I have put code into HBN that knows when win shuts down gracefully and allows the wallet to do so as well. Are you sure it was a normal Win shutdown and not a power failure or other type of shutdown.

I've seen Windows update be anything BUT graceful several times, especially on laptops. Particularly Windows 8/8.1 (which were the inspiration for me moving on to Linux), but it caught me out a couple of times on 7 too. I have since made a rule of making updates NOT be automatic, regardless of how much Windows nags about it. Once started, the process will screw your computer up badly if interrupted, so I find it better to do it on my terms.

There are a lot of cool things about Windows. I used it for nearly it's whole history, and I won't bash it in general, but it seems that Microsoft recently has been out to screw over their users. Either that, or they lost all their talent to the competition. I've not bothered to look at 10, but judging by RT and Windows 8, they seem to want people to move on to Linux or (shudder) OSX. 

Hi, perhaps Tranz or someone else can enlight me

Checking my add on the explorer ( http://hbn.cryptocoinexplorer.com/address?address=ErmqaiunrcguMEhpDP5uqEQhRKmn3oViWv ) he show me 6706.15625
But on my wallet, only 6679.99642. Diff of around 28 HBN not showing on my wallet.

Did some coin get lost somewhere in my wallet or the block explorer reporting wrong number?  Wallet running fine for many month, update to 1.5 went without trouble.

Is there any way to rescan all my coin to recover/double check all my coin to see if some are wandering around ?


Edit:
2nd problem  
Just runned wallet with -salvage flag to check if it would find some of my ghost coin, but nothing more ^^

Now in debug windows (after the -salvage, and even restarted without the flag), with listtransactions it's only return receive coin, and no more all the POS generated.
Before, listtransaction did return every transations: receive/pos/send ...
PS. The GUI still show the pos transactions, and wallet keep minting without trouble.

Did I broke something else ?  


Edit 2:  (Promis, after this one I'll sleep ! )

Looks like after the salvage or repair, client did a backup a my wallet named somethings like wallet.number(timestamp perhaps?).bak and a wallet.dat (Don't worry, I did a backup myself too before trying  , just didn't tried to get my old wallet back ^^ )
Just renamed the wallet.dat to something else, and then renamed the wallet.number.bak to wallet.dat, restarted client, and now listtransations is working again, even for the 3 pos i got during this time  

Many things I've to learn still it seems

Can I simply archive the txleveldb folder, when it's done syncing, and simply use the latest copy the next time it gets munged up?  It's the only thing I deleted and my coins are all showing up again. Whew!

To save the block chain you backup txleveldb + blk001.dat.  The wallet uses wallet.dat and database.  Saving those 4 files, while the client is NOT running, is a great way to quickly backup.

The way I do it is before a windows update or other reason I know I am shutting down. I shut down the client and then create a backup_date folder and copy those 4 things mention above into that folder.  I only do it once in a while.

There is one for the wallet already, under file. I think adding one for the block chain is a good idea as well. It maybe tricky or not doable with txleveldb, and allowing the client to still be active.  But might be worth investigating.

Corruption on other OS is also possible. Less likely. But if you pull the disk out from under an application that is currently writing to it, you will get unpredictable results.