[section31]

I hope this is correct to put my question in here as I've a similar problem of Calibre simply not starting. I had downloaded and installed 0.7.54 2 days ago, installed and it ran fine. Last night, Calibre prompted me that 0.7.55 was out and so I downloaded and installed. I installed over the program instead of removing 0.7.54 first, but I found nothing suggesting against this. Upon have installed 0.7.55 I launched it and it started fine. I then began to migrate files to the new 0.7.55 from another drive to Calibre from and old Calibre C:\Windows\User\Calibre\Library on an hard drive that was smaller then the new drive where the new install of 0.7.55 is. It transferred only 2 books, then crashed. Now it simple will not start, it immediately crashes. He is a listing according to to what I've done as per the Calibre frequently asked questions.

1. The program is not as far as I know being used by another program. But I did:
A. Uninstalled Calibre
B. Rebooted my computer
C. I re-installed, and did not start from the installation wizard.
D. I temporarily disabled my antivirus, and disconnected from the internet
E. There is no file named metadata.db. I looked in all files and found
nothing.
F. I started Calibre
G. It again now immediately crashes with Windows calibre.exe has stopped working. Checking for solution, with no answer.

2. No error about Python function.
3. I've left the library where it is C:\Users\Lesley\Calibre Library. No non english characters. The program also ran fine the first time but now subsequently is when it crashes.
4. I've assigned it to run as administrator
5. I'm running Windows 7 64bit
6. I've attempted both disabling my antivirus and its firewall off. I don't see how to turn off Norton 360.
7. I have started the cmd.exe and run a calibre-debug -g and it just immediately just crashes and shows the same Windows Program failed box that shows when I start Calibre from the shortcut or in the programs directory.

I will do what it takes to use this. Very nice program and I used it before, and it did all the same things. I just thought perhaps it was due to problems I was having with an old hard drive. But this installation is on a brand new hard drive and a fresh install of Windows 7 64bit.

Thanks for any help and again I look forward to any help