I had been playing FSX 30 minutes at a time for the last couple weeks 'cause I was holding off on activation due to expected upgrades of all my vital parts (and I didn't have a lot of time to play any way). I got tired of this routine yesterday and took the plunge with activation. Now after everything was running fine (or as well as can be expected), FSX just hangs on the title screen. I was playing some missions and thought FSX was acting a little sluggish so I shut it down for a restart. Upon the restart, it began to hang. I've tried restarting the PC but that didn't help. Watching Task Manager when FSX starts, the application changes to "Not Responding" within a few seconds of starting. On the Process tab, it shows a steady 45 - 50% of my processor (P4 EE OC'd to 3.2GHz) and memory usage climbs to between 80 - 90 Mb (1.5Gb installed) but doesn't go any higher. I've let this go on for over 30 minutes. I've closed all unnecessary applications including Windows Vista's (RC1, build 5600) Sidebar. The event viewer is no help as it only shows that I shut it down. I hate to think about uninstall-reinstall because that will be one of my activations down the drain (after 36 hours of activation) but I don't know what else to do. Thanks in advance for any other suggestions?Dan

Probably a corrupted logbook. It has happened to many of us. Search the forum for "corrupt logbook" and you will find the solution. I'm not good at explaining how to fix it.FLMach1

You're probably right! I had practically forgotten that I deleted some logbook entries some time before that last shutdown. I'll search for the fix and report back if it worked. Thanks a lot!Dan

That was it, alright. I found a supposed fix in this thread: http://forums.avsim.net/dcboard.php?az=sho...74412&mode=full. However, lc0277's little logbook editor didn't find or open my logbook. My guess is that it was too corrupt. I ended up renaming the corrupted file and let FSX create a new one upon next startup. It worked but I obviously lost the logbook entries I had up to that point. That new logbook design is a bad choice in my opinion. Why something that can corrupt so easily and bring FSX to a screeching halt was implemented is a mystery.Thanks again for a quick and correct resolution. I'm going back to my flying now.Dan

That's great to hear that you got it working again. It took me a week to finally find out how to fix it. It's definitely a frustrating problem. FLMach1