NZFF

Well, Guys,
Thanks for the warm welcome and answers to my post two days ago. I then received and enjoyed the September newsletter, downloaded and had fun flying the new CT-4E for an hour or so. I turned off and went to bed.
Now tonight I have a problem: I opened FSX BUT, no go. I have tried a "Repair" from the DVDs twice. I have tried an uninstall and re-install including re-activation (how many times will Microsoft let me do that I wonder).
The symptoms are simple - the usual splash screen starts, the hard drive works hard - a progress bar runs "installing scenery" etc (come to think of it - it didn't used to do that). That completes. The HD stops eventually and just the hour glass runs and runs and runs - the spalsh screen remains forever!
A Ctrl-Alt-Del + Applications shows just one program - FSX "Not responding". Nothing else is running. I have run FSX for the past 2 months without a hitch.
My hardware is a new machine with an Intel Core 2 Duo, 4Gb Ram, 3Ghz CPU, XP SP2, 512 Mb Video.
Any thoughts anyone?
How do I un-install the CT-4E (not that I blame that but I can't think of anything else at this stage).
Help!
Phil

Phil - you may have to deleted all saved flights from the 'My Documents, Flight Sim X ' folder .

Ian
My first reaction - this is too simplistic!
But, did I detect an aire of quiet confidence in your brief message? IT WORKED!
Thank you so much for this suggestion. I'm now half an hour late for work but who cares.
Have a great day and thanks again.
Phil

Ian Warren wrote:

QUOTE (Ian Warren @ Sep 2 2008, 02:37 AM) <{POST_SNAPBACK}>

Phil - you may have to deleted all saved flights from the 'My Documents, Flight Sim X ' folder .

how does that stop fsx working? good to here you got it fixed!! shot Ian

I think the main problem with FSX is a damaged Logbook.bin. If you remove this, then FSX can rebuild it and start ok. However you will lose all your logbook entries.
With FS2004, a similar problem happened if your default flight was damaged. Removing the .flt file would normally fix this.

Thanks toprob (and Ian again). Binary files can be probmatical but I would never have thought of the removal of one as a fix for this disaster.
Loss of a logbok and saved flights is neither here nor there - recovery of FSX is mission critical.
I guess my concern now is what caused this to happen in the first place.
Hope this is helpful to others as well.
Phil

Phil wrote:

QUOTE (Phil @ Sep 2 2008, 05:18 PM) <{POST_SNAPBACK}>

Thanks toprob (and Ian again). Binary files can be probmatical but I would never have thought of the removal of one as a fix for this disaster.
Loss of a logbok and saved flights is neither here nor there - recovery of FSX is mission critical.
I guess my concern now is what caused this to happen in the first place.
Hope this is helpful to others as well.
Phil

Google 'corrupt logbook' and you'll see that this is a very common problem. There are even tools around these days that'll backup your logbook automatically so that you won't lose everything in the event of a problem.