I went back to page 2 and did not locate your solution to the logbook.Undr what caption is it listed?Thanks Frank

>[email protected]>>Someone listed above posted an logbook editor for FSX. I>have not tried it because I have yet to use the logbook in>FSX.>>This file could be an answer to your problems.>>file is:>>logbookedit-2310061902>>Hmmm, actually there seems to be an updated version already. I have logbookedit-0411062225.zip on my system. Look for that one. :D

Does this program allow you to fix corrupted log books or is this just an editor?If not, is it possible to just delete the log file(s) and let FS X create a new one (obviously losing the data it contained)?

What is the point of the FS logbook? I didn't even know it had one- I remember one years and years ago, but the only one I'm concerned about it my real one. Why not get a real (they are cheap) and fill out for real- It's much more satisfying to flip through your accomplishments then.

You can use FSX Logbook Recovery v1.1 to analyze your logbook and recover a corrupt logbook.After using the recovery tool (ONLY AFTER RECOVERING THE CORRUPT LOGBOOK) you can then use Log Book Manager to edit any entries in your logbook.As always make backups of your orginals prior to any editing just in case.I also routinely use the Logbook Recovery tool to analyze my logbook and regularly make backups of my logbook and rewards files.

>Thank you Gypsy Baron! :-)>>You just saved me from having to reinstall FSX (again).I simply don't understand this fetish many folks seem to have about reinstalling FS (any version).I installed FS2002 nearly eight years ago, once.I installed FS2004 nearly six years ago, once.I installed FSX nearly a year ago, once.Folks, 99 times out of 100, reinstalling any FS version will not solve your problem(s)......because none of the multiple .cfg files are ever touched, which is where most problems occur.I'm constantly tinkering with scenery, aircraft, et cetera, but I am careful to maintain daily backups of the multiple .cfg files... ;)

>Don't know how long it's been messed up but my logbook is>way wrong. I have entries from 2005!>>I had several hangs of FSX (old video driver) when I first>started it up. Now there are duplicate entries, etc. Do not>have half of the flights listed either. The rewards stuff>looks ok.I have these too. I think they are from running the missions. I have noticed that if you start a flight today and then finish it 2 weeks from now, it will have today's date entered. So I think the mission have an old date tagged to them.

>I'm constantly tinkering with scenery, aircraft, et cetera,>but I am careful to maintain daily backups of the multiple>.cfg files... ;)Bill, could you suggest which files we should backup?

>>I'm constantly tinkering with scenery, aircraft, et cetera,>>but I am careful to maintain daily backups of the multiple>>.cfg files... ;)>>Bill, could you suggest which files we should backup?At a minimum?fsx.cfgcamera.cfgterrain.cfgscenery.cfglogbook.bin

>Thank you Gypsy Baron! :-)>>You just saved me from having to reinstall FSX (again).>>I took a look through my logbook.bin with a hex editor and>specifically looked for that byte counter after the "05 byte",>but my last log entry looked like it had the right byte count.> So just to try something what I did was delete the last 05>byte (using a hex editor) and everything after it, so I>basically deleted my last log entry.>>I then launched FSX and it didn't lock up! My 'rewards' were>intact, and my logbook was intact! The only thing I lost was>my last flight, so I'd say it's worth sacrificing one flight>to the Microsoft Corruption God to save the rest of the>records. :-)>>>PlaidAvengerI use XVI32 Freeware hex editor and Logbook Edit 2 from AVSIM.Use this for specific sized entries. O5 starts at the very first byte after your last aircraft entry. Count the bytes from and including 05 to the last character in the aircraft type. Typical size is 61 bytes for most of the default