NZFF

This is my first time posting here and I was hoping one of you guys may be able to help.

A friend has purchased FSX and it comes with the addon expansion programme accelleration.He also purhased VLC.The Sim installs and loads up okay at first,however after a few days it stops working ie freezes, when checking the Pilot records section.Then after that it will not load up.All that happens is the splash screen appears.

So not really sure whats going on here.The sim has been uninstalled and reinstalled several times , always eventually freezing after checking the Pilot Notes, having just finished flying as you do.So I thought this sounds like the registry has got a problem somewhere and we decided to wipe the hard drive and start again.This did not resolve the issue. As you can imagine this is starting to become annoying.Have run out of ideas and have come to tech help for some advice please

System specs are: Processessor AMD Athlon 64 3.5ghz, Memory 2047mb , GPU Nvidea 9800 Geforce GT, OS. XP service pack 3.Using Direct X 9.0c

I realise this is possibly not going to be anything obvious , we would certainly appreciate any advice that could help resolve this issue.

As the owner of the machine keeps reminding me the only reliable thing on his computer is the Clock

Don't know if this will work but it's worth a try.

Make a backup copy of Logbook.BIN first then delete it and paste it to the desktop. It should be located in C:\Users\User\Documents\Flight Simulator X Files.

Start FSX and it should not freeze and should work. But if this doesn't work then Im out of ideas.

I've heard of this problem before, and think Eddy's solution was the one offered. Do some BINGing or Googling as well. If you can't sort it by Eddy's method, I'd say you might want to also look at corrupt memory (so you'll need to run the DOS version of MemTest - at least 8 passes) or possible hard drive errors (at the very least, schedule a full scan from Windows). Note also that even though you've done a full uninstall, its possible that there are leftover files in the Documents & Settings folder in hidden places, or even in the Documents folder of the main user.

You can also rebuild the FSX cfg by deleting it and starting up the sim to rebuild another ,that file is found C:\Users\mike\AppData\Roaming\Microsoft\FSX

creator2003 wrote:

QUOTE (creator2003 @ Dec 2 2010, 07:17 PM) <{POST_SNAPBACK}>

You can also rebuild the FSX cfg by deleting it and starting up the sim to rebuild another ,that file is found C:\Users\mike\AppData\Roaming\Microsoft\FSX

But what if your name isn't Mike??

Thanks you guys for your help .Will report any finding, good, bad or otherwise.

Cheers,

Dinga

creator2003 wrote:

QUOTE (creator2003 @ Dec 2 2010, 07:17 PM) <{POST_SNAPBACK}>

You can also rebuild the FSX cfg by deleting it and starting up the sim to rebuild another ,that file is found C:\Users\mike\AppData\Roaming\Microsoft\FSX

Since he's on XP, it will be "documents and settings" at the front of that address, not "Users". He'll also need to have "show hidden files and folders" enabled.

Did you -

1. Install form the DVD, fire up the sim and let it complete the install and then boot the default flight.

2. Close the sim

If you have the Deluxe version and want the SDK installed, install it off the DVD now.

3. Reboot the computer

4. Install Acceleration which will install SP2 automatically. Boot the sim and allow it to complete the install and boot the default flight.

5. Close the sim

If you want the Acceleration SDK install it from the disk.

6. Reboot the computer



a ton of tweaking and other info can be found here http://www.simforums.com/Forums/topic29041.html

Thanks everyone for taking the time to reply and for pointing us in the right direction.All good info from everyone.The Logbook.bin file seems to be part of the problem alright.The file has been renamed.This allows you to get the sim working again.At this stage it seems to be working ie recording flts in the Log BookThanks NZ Eddy.I am now wondering why the Logbook.bin file is causing this ,as it may well become an issue again.Have checked the memory with mem check awhile ago and found no problems.Will post back here when we have done more checking.

Well renaming the logbook.bin has sorted that problem. .