Quote from: cr1776 on November 13, 2013, 07:06:48 PM

Whatever you do, keep copies of the recovered wallet.dat files indefinitely. Just because you can't get it now (unless you end up being able to), doesn't mean you might not be able to do so in the future.

For example, depending upon what has been recovered from each, you MIGHT be able to combine the two into a working one. Likewise, you might be able to recover part of your private key (or even all of it) eventually. Or, tools may improve. Either way, if you are not able to successfully recover something now, doesn't mean you won't be able to do so in the future.

The suggestion of talk to jackjack is a good one as is being careful about who you send information to.

Thanks for the advice!

I tried running pywallet --recover on just the "recovered-wallet.dat" file. It actually finds 306 keys, but it stops at importing 20/306.

Code:

Importing key 20/306:
Traceback (most recent call last):
File "C:\Users\Name\AppData\Roaming\Bitcoin\pywallet.py", line 4910, in <
module>
importprivkey(db, sec, "recovered: %s"%sec, None, True)
File "C:\Users\Name\AppData\Roaming\Bitcoin\pywallet.py", line 2622, in i
mportprivkey
pkey = EC_KEY(str_to_long(sec.decode('hex')))
File "C:\Users\Name\AppData\Roaming\Bitcoin\pywallet.py", line 1056, in _
_init__
self.pubkey = Public_key( generator, generator * secret )
File "C:\Users\Name\AppData\Roaming\Bitcoin\pywallet.py", line 1000, in _
_init__
raise RuntimeError, "Generator point has x or y out of range."
RuntimeError: Generator point has x or y out of range.

The dat file with only 19 keys actually works loading with the bitcoin client. Is there anyway to check if it contains any money without having to sync the bitcoin client?