I showed you everything I've got. The log file ends abruptly. The file shrinks. There is nothing more. That's part of the problem. Hard to track down a problem with so little to go on.Yet you don't show any *proof*, I'd just remove the "PROVEN" in your title, it is misleading.
That's how I do all my new wallets, it's repetitive but it means I can keep an eye on my shit.1: Run wallet.
2: Quit wallet.
3: Make copy of wallet.dat
4: Start wallet again. wallet.dat corrup? Delete it and Goto 1:
5: Quit wallet
6: make a diff of your backup wallet.dat with the actual one
7: diff shows a difference (means one of your wallet.dat files is corrupt: Goto 1:
8: diff shows no differnce -> voila
But you're right, exporting the key is the more straightforward approach.
I understand your anger, but a bit more information would help tracking this one down tremendously:I showed you everything I've got. The log file ends abruptly. The file shrinks. There is nothing more. That's part of the problem. Hard to track down a problem with so little to go on.
That's a very convenient piece of busted RAM... It manages to cause a problem with wallet.dat of darkcoin-qt 2 times in exactly the same way, and the system runs perfectly stable in every other way...Never said to ignore the issue. You simply state that its PROVEN, while the only claim is your own experience in your own words.
Were you able to replicate it on the *same* machine? This is likely an operation relying mostly on ram, as coingun said it could be a bad stick.
I have doubts about this, but you could be out of memory, ending up with the system killing the wallet at some point during it's shutdown?
Well, it's not common to include things that don't happen... It didn't rain today. Weird, right?I understand your anger, but a bit more information would help tracking this one down tremendously:
- which operating system/version
- fresh install or did you already install other software packets. If so,which ones
- did the computer and other software ran stable before or were there already other crashes
With this information it would be at least possible to find someone with a similar configuration and try to reproduce it.
All media currently involved is magnetic. 2x USB hard drives, internal hard drive...I understand your anger, but a bit more information would help tracking this one down tremendously:
eth1 made a good point, USB sticks ARE very insecure, I had already a couple of them doing nasty things...
I've said this myself. I know it's not much to go on. If I had more I'd give you more. If I had more, I'd probably figure it out my damn self!you have to understand that you are not giving us anything to work with.
You're absolutely right! Never should have posted it.arguing here is moot.
I should know better than to think I'd find anything other than pumptrolls acting like complete assholes, then calling me the asshole...stop being an ass.
i can't help it... LMAO...
I have proven it. No matter what proof I present, it will be ignored and "more" proven will be needed...No one attacked you because you have the issue. You got jumped on cuz you claim you have something proven when you do not.
I have proven it. No matter what proof I present, it will be ignored and "more" proven will be needed...If you here to just report is state so and not claim you have a proof it happens.
I left BCT because I am the only stable, rational adult I could find there. Seems I'm finding a theme...Anyway am out, you're too unstable for my liking.
Try pywalletDump is in hexdeci slash delimieted I think... Still not human readable... working... Lots of key entries. Just can't read them. It's probably in here.
python pywallet.py --datadir=/home/YourUserName/.darkcoin/ --dumpwallet --otherversion=76 > wallet.txt
I was already on that route when I stopped. Noticed the jj fork...Try pywallet
you can try it in separate VBoxI was already on that route when I stopped. Noticed the jj fork...
When I went to install the pywallet deps, apt-get wanted to uninstall everything berkleydb related... So, yeah, I stopped there...
I encrypt my entire drive, so, encrypting the wallet seems redundant and adds difficulty in such fiddling. At least this much I'm prepared for, lols.
Yep. Did that. It tells me the file is corrupt and it won't do anything with it. lols...you can try it in separate VBox
It's pretending that the file is open... Which adds credence to my theory that something is going wrong with the wallet.dat dump when the client fails out of RAM... Looks like a copy-while-qt-is-running, but that is absolutely not true.fail said:ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
Did it ever come to your mind that this issue could arise from yourself and your cockiness rather than yourself being the only rational adult?I left BCT because I am the only stable, rational adult I could find there. Seems I'm finding a theme...