Cannot start gnuCash after win7 lockup

[Len Goddard]

On 06/09/2013 01:59, Derek Atkins wrote:
> Hi,
>
> On Thu, September 5, 2013 4:45 pm, Len Goddard wrote:
>> A couple of days ago several apps on my Win 7 system locked up.  I
>> killed what I could but I couldn't clear the logjam so I rebooted.
>> Windoze locked during shutdown and I had eventually to force a
>> powerdown.  Several applications (innocent bystanders) were affected -
>> uTorrent lost its configuration and the encrypted KeePass database was
>> corrupted.  gnuCash seems to have faired the worst.  When I attempt to
>> start it, either via the icon or by clicking a .gnucash file, the splash
>> screen and tips screen come up, then go away.  I looked through some
>> similar but old threads on this list but nothing seemed to help.  In
>> particular,  I have
>> 1. reinstalled
>> 2. uninstalled, deleted everything that the uninstall left behind then
>> installed
>> 3. run gnucash-launcher.cmd from a command prompt
>>
>> All this gave the same result, splash+tips then nothing.
>>
>> Then I ran gnucash-launcher.cmd from a Cygwin bash shell and it gave me
>> the new user wizard.  I declined to create a new account and opened the
>> old one from the menu which worked fine.  So, the code appears to be
>> working and the data file appears to be intact.  I am guessing that
>> somewhere there is a corrupt config file somewhere which is bypassed
>> when I run it under Cygwin - any suggestions?
>>
>> I really hate windows.  Long term gnuCash will be migrated to a linux
>> machine but that is not practical in the short term.
> Sorry to hear about your issues.  You can also try to clear out  your
> %HOME%/.gnucash and .gconf* directories, which contain a bunch of gnucash
> metadata.  You'll lose all your settings, but it should get gnucash
> running again.  Then you'll just need to File -> Open your data file to
> get gnucash to remember it.
>
> Good Luck,
>
>> Thanks,
>> Len
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
> -derek
>
Thanks for the prompt reply.  That sorted the problem.  I knew there had 
to be something that needed deleting, just didn't know what! Lost 
settings appear to be time/date preference and position of data file, 
both of which are easily fixed.