Steps to reproduce:
OK, it's not technically a crash.  But it is an infinite loop and GnuCash must be killed or have its demand for a disk in the drive be satisfied.
1. Start GnuCash
2. It displays the message "There is no disk in the drive.  Please insert a disk into drive F:.", window title "GnuCash: gnucash-bin.exe - No Disk", and with 3 buttons: Cancel, Try Again and Continue, all three of which lead directly back to this message, each of which I've clicked over 20 times in the hope that it might move on from this pointless message.
3. Without a disk there's no way out, except killing GnuCash with Task Manager


Stack trace:
n/a

Other information:
If I insert a disk into drive F then it runs.  But what file is it looking for?  If it's not looking for a file, why does it want a disk in drive F?  On two test runs I inserted two different disks with no filename common to both, and there was no "file not found" error in either case.

If I open the accounts file from within a running instance, without a disk in drive F, there is no error.  So it doesn't seem to be a configuration issue with the accounts file.

Maybe it's something I've done.  But 2.2.5 doesn't have this problem, and GnuCash shouldn't demand a disk in a drive to run.  If it's looking for a file then it should say what file it wants and give the user an option (a) not to run with that file or (b) to locate the file somewhere else.

I've uploaded three screenshots to http://picasaweb.google.co.uk/davethesax/Bugs.
One shows guile.exe throwing the error during installation.  The second shows the error described above during GnuCash startup.

The third shows the bug I'm hoping will eventually be fixed - this is how accounts always appear when GnuCash first runs and have done so since I started using GnuCash 2.2.1; the display is corrupted and does not correct itself for a while (at least until it is clicked, and sometimes even then it's not correct).  This bug can lead (and has done so) to confusion over what is actually going on in the account.

(Clarification: The bug is not the smaller blanked out rectangles; that's just me being paranoid about who's looking at my accounts.  The problem is the large greyed out rectangle above the 17/10/2008 transaction - you can see it has cut one line in half; all accounts appear like this, and accounts with less than a screen full of data are also initially corrupt until I've clicked on them and moved the cursor (with the keyboard) up and down the screen a few times.)