0.3 almost ready -- please test the Mac version!

[satoshi]

I finished everything on my list to do for version 0.3.  The code on SVN is about ready to release.

Testing at this point is much appreciated.

[1713927065]

1713927065

[1713927065]

1713927065

[1713927065]

1713927065

[1713927065]

1713927065

[1713927065]

1713927065

[1713927065]

1713927065

[HostFat]

I'm just here

Windows 7 x64
4 GB RAM
Intel i7 860

[lachesis]

Very nice! There have definitely been some major improvements, including the hashmeter, RPC support, and a command-line daemon. It would be nice if the listtransactions RPC method were finished before the next release, though. Also, some code should be added to the JSON-RPC methods to list out dHashesPerSec.

Great work Satoshi!

[Xunie]

Whoohoo! Can't wait!

Note, is there somewhere I can get a devel build?
Maybe we can setup nightly builds or something...

[teppy]

Should we try for some publicity? Slashdot is good if we can get it.

I've had a number of submissions accepted, though always by one editor that no longer works there. Anyone else with a Slashdot connection?

[sirius]

Should we try for some publicity? Slashdot is good if we can get it.

I've had a number of submissions accepted, though always by one editor that no longer works there. Anyone else with a Slashdot connection?

We should try to get publicity, and focus the campaign on the time right after the release to get the maximum impact: simultaneously advertising on forums, irc, Youtube, Facebook, Google Ads and other places. Slashdot with its millions of tech-savvy readers would be awesome, perhaps the best imaginable! I just hope the server can stand getting "slashdotted" Maybe it should be upscaled beforehand just in case.

[satoshi]

It would be nice if the listtransactions RPC method were finished before the next release, though.

My fear is too many programmers would latch onto that for checking for received payments.  It can never be reliable that way.  The list/getreceivedbyaddress/label functions are the only way to do it reliably.

We shouldn't delay forever until every possible feature is done.  There's always going to be one more thing to do.

[satoshi]

Here's RC1 for windows for testing:
(removed, see RC2 below)

Please only download this if you're going to test and report back whether everything seems fine or not.  Make sure to look through the files in "c:\program files\bitcoin"

[Gavin Andresen]

I finished everything on my list to do for version 0.3.  The code on SVN is about ready to release.
Testing at this point is much appreciated.

I just finished creating a clean Amazon EC2 debian 5.0 machine image with everything I needed to compile bitcoind, and it compiled (using a variation of Laszlo's makefile.unix) and is running fine (just finished downloading the block chain).  I'll let you know if it misbehaves.

I had trouble compiling the gtk version, but I think that's because I did something wrong compiling wxWidgets.  I don't need no stinkin' graphics (and am not a wxWidgets expert), so I'm not going to bother trying to fix that.

[HostFat]

EXCEPTION: 22DbRunRecoveryException
DBENv::open: DB_RUNRECOVERY: Fatal error, run database recovery
C:\Program Files\Bitcoin\bitcoin.exe in OnInit()

I have the same problem :|

[satoshi]

EXCEPTION: 22DbRunRecoveryException
DBENv::open: DB_RUNRECOVERY: Fatal error, run database recovery
C:\Program Files\Bitcoin\bitcoin.exe in OnInit()

What operating system?

Normally when it does that it's because the directory where the data directory should go doesn't exist.  See if the "%appdata%" directory exists.

Do you get that error with 0.2 also?  It's hard to see how you could get that with 0.3 and not with 0.2 since there's nothing different in that regard.

[HostFat]

Windows 7 x64 ENG
4 GB RAM
Intel i7 860

I was using the v0.2.10 build by laszlo before yours.

[satoshi]

davidonpda, were you also running laszlo's build previously?

Check if the "%appdata%" directory exists, and "%appdata%\bitcoin"

Try:
 rename "%appdata%\bitcoin" bitcoin2

does it work then?

[HostFat]

Check if the "%appdata%" directory exists, and "%appdata%\bitcoin"

Both are existing

Try:
 rename "%appdata%\bitcoin" bitcoin2

does it work then?

Yes it works.

so I closed it, copied the walled.dat from the old folder to the new one, and now it's downloading blocks
Address book and old transfers seem ok, but there aren't anyone of old "generated coins" ... I just need to wait?
Anyway, I can just go back with the old v0.2.10

EDIT:
I did another thing.
Closed it, copied addr.dat / blk0001.dat / blkindex.dat from old folder to the new one.
Restarted bitcoin ( v0.30 ), and now it seems that everything is working. ( I can see also old generated coins now )
I just did NOT copied "log.0000000002" from the database folder ...

[satoshi]

You figured it out faster than I could post a reply.  

It looks like laszlo's build of Berkeley DB has database/log.* files that are not compatible with ours.  The .dat files are fine, their format shouldn't ever change.  All data is stored in the .dat files.  All your own data is stored in wallet.dat.  If you had waited for it to redownload the block chain, your missing transactions and generateds would have appeared as the block chain reached the point where those transactions were recorded.

When you copied the directory except log.0000000002, that's the best solution.  You should be good now.

The database/log.* files only contain temporary database data.  If you exited bitcoin normally the last time, not exited by forced terminating it or crashing, then the database/log.* files can normally be deleted safely.  They're only used so that if the database is in the middle of a transaction when the computer crashes or the program is killed or crashes, then it could recover without losing data.

Please keep running v0.3 if at all possible, don't go back to v0.2.10.

Anyone else who hits this problem, move the database\log.000000000* files somewhere else.  (if it works fine after that, you can delete them later)

I'm reluctant to make the installer delete or move those files.  If the previous run was stopped by crashing or killed, that would be the wrong thing to do.

[HostFat]

yes, I'm just using 0.30 by now.
Thank you!

[D҉ataWraith]

Runs fine under WINE. *rhymes*

It automatically switched the language to German, too. Now that I can see the translation in the client itself, I noticed a few things to improve, and will post a new .po file within the next two or so days.

[lachesis]

Yeah, 0.3.0 seems to have a performance increase over svn r84 with Laszlo's performance patch.

[satoshi]

Laszlo figured out that enabling some more optimisation increased performance about 20%, so 0.3 hashes 20% faster than 0.2.0, but I assume he used that in his own build.

30khash increase to what total rate?  (to figure the % increase)

[Vasiliev]

Much faster than Laszlo's build for me. Went from 600-700khash/s to 1000-1100khash/s on my Intel Core 2 Duo E8500. From 700-800khash/s on a laptop i7 to ~1100khash/s.

edit: Keeping the "Run Bitcoin" option checked in the installer seems to run it with admin privileges on the first launch. (in Win7)