Logbook question.

[Sbob]

Is there a maximum number of entries you can make in a standard FS9 logbook?

I've got something like 900 logged hours that I've carried over since FS2002 and today FS said "no mas" to my standard logbook.LOG.
I have my logbook (located in Win10 documents folder) backed up and I'm trying out a new file named logbook2, which I can edit to keep my total hours.
Has anyone else had to deal with this? Its possible FSIUP had a hiccup because I've been getting an error message when I quit FS that my logbook no longer exists.

 

[Sbob]

Some handy (but really old) info:

Logbook Error When Exiting FS2004 - Flight Simulator 2004: A Century of Flight (FS2004 General)

Question titled "Logbook Error When Exiting FS2004 - Flight Simulator 2004: A Century of Flight (FS2004 General)" posted in the FS2004 General forum at Fly Away Simulation.

forum.flyawaysimulation.com

To wit:

"I tried reloading the sim and it did not lose anything. It also did not fix the problem. I then backed up all my aircraft, add on scenery, etc directories and uninstalled the sim using the disk. This left behind a group of files and directories under the fs9 directory. I deleted the whole directory and all of the files and re-installed.

When I tried to re-set my settings in FS9, they were already there just like before I un-installed. This told me there was something else left somewhere. When I tried the sim again, the same problem occured.

I then remembered that there was another place where the program puts files.

c:\documents and settings\[user name]\application data\microsoft\fs9

In that folder is a file named fs9.cfg along with others. When I opened the file in notepad, I found a parameter "log_file=A++++++++++++++++". I then deleted just the file name and left the "log_file=" then restarted the program.

After a short flight, I closed the program and the logbook worked normally. I then opened the cfg file again and the entry read "log_file=logbook" as it should. The old logbook file itself was intact and none of the prior information was lost.

If this problem occurs, the first thing to try is to open the cfg file and change this setting and re-try. It takes about 2 minutes to do and you don't need to re-install anything."

Just keep in mind that this post dated back to 2004. You might need to do some exploring to find FS9.cfg.

 

[jgf]

I don't know of any entry limits, but the logbook is easily corrupted (by what I've no idea) so I back mine up periodically. You can also save it as a txt file and just keep adding new log data to that.

The name can be corrupted so FS cannot find it but the data is still there, or the contents can get corrupted (lines and lines of gibberish interspersed with the data), which can be saved but it's a tedious process.

 

[Sbob]

I'm pretty sure I know what happened. I did almost a three hour carrier flight on my virtual WESTPAC and logged the hours. I forgot to include the carrier (AC22) in the comment line and later edited the entry in FS.

BTW, finding FS9.cfg in Win10 is pretty easy once you know where to start.

C: > USERS > {YOUR NAME} > APP DATA > ROAMING > MICROSOFT > FS9 > FS9.cfg

Note that APP DATA will be "grayed out" and you'll need to have "all folders" access set up in advance.
If you edit FS9.cfg with NOTEPAD, it will be saved as FS9.cfg.txt and you'll need to RENAME it to drop the .txt part.

I haven't checked it on the Win11 machine yet. I'm guessing it will be similar, like C: > COMMONER > NSA > M$ INFORMER > {YOUR NAME AND SHOE SIZE} > NO-PROFIT-FOR-US > REALLY REALLY OLD SOFTWARE > FS9 > FS9.cfg.

 

[zswobbie1]

Even easier..
Use 'Everything' from https://www.voidtools.com

It's a desktop search engine that finds whatever you are looking for, as you type.

 

[Sbob]

Yeah, but what fun is that??


BTW, I consider it "good house keeping" to have back-up copies of FS9.cfg, logbook.log, and scenery.cfg plus a short text file on how to find the originals.
In Win10 your logbook.log file can be found in your Win10 "DOCUMENTS" main folder.

Since FS2002 is so primitive, all of these files can be found in the (GASP!) FS2002 folder.

 

[jgf]

Since FS2002 is so primitive, all of these files can be found in the (GASP!) FS2002 folder.

Which is where they logically should be. I despise Micro$oft's "all your eggs in one basket" concept of putting everything - documents, images, videos, game mods, saved games, etc. - into one folder; especially when I use a separate partition, if not a separate drive, just for the OS. I now use symbolic links and put these folders where I want them, not where MS wants them.