• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning

FSX Logbook - a reminder

Naismith

Charter Member
Last night I went to bed thinking "groan! am I going to have to reinstall this damned thing again" I had been unable to get it to run all day. I tried deleting the fsx.cfg. backed up the exe.xml and dll.xml at various times during the day and still it would not run. I ran the Acceleration fixes, and the whole CD fix. Nothing. By nightfall I thought I had exhausted all the tricks to get it up and running and gave up thinking today would be a slog doing the whole reinstall thing and never mind the MS activation process - all such a drag.

I woke this a.m. and remembered I had cut a few entries in the logbook the previous day, and had mistakenly edited one out of sequence. Eureka moment! I deleted the Logbook.bin file and praise be to (insert your favoured deity here) it ran.

Such a minor and innocuous file yet it can wreak havoc.
 
There are so many ways to ground FSX. I had forgotten this one. There is a freeware FSX logbook editor (logbookeditor-0.3) that fixes log book problems and allows editing any entry. That has helped me fix some of these before.
 
Last night I went to bed thinking "groan! am I going to have to reinstall this damned thing again" I had been unable to get it to run all day. I tried deleting the fsx.cfg. backed up the exe.xml and dll.xml at various times during the day and still it would not run. I ran the Acceleration fixes, and the whole CD fix. Nothing. By nightfall I thought I had exhausted all the tricks to get it up and running and gave up thinking today would be a slog doing the whole reinstall thing and never mind the MS activation process - all such a drag.

I woke this a.m. and remembered I had cut a few entries in the logbook the previous day, and had mistakenly edited one out of sequence. Eureka moment! I deleted the Logbook.bin file and praise be to (insert your favoured deity here) it ran.

Such a minor and innocuous file yet it can wreak havoc.

You did the thing that has helped solve almost all of my most vexing Flight simulation problems. Going to bed before I did anything as drastic as a reinstall. Sleeping on the problem. When my frustration rises to a fever pitch, its time to go to bed. You are a smart man., Naismith.

JP
 
Back
Top