Author Topic: Corrupted CouatlAddons.ini  (Read 3330 times)

paj

  • Newbie
  • *
  • Posts: 5
Corrupted CouatlAddons.ini
« on: March 17, 2012, 03:54:20 pm »
Ouch! My computer just experienced a BSOD as I was exiting FSX! Upon reboot I launched FSX only to be confronted with an array of errors from AivlaSoft EFB and SuperTrafficBoard. Once I dismissed these I found I also had no COUATL menu, no GSX functionality and no FSDT scenery buildings! Exiting FSX resulted in orphaned COUATL.exe processes running in memory which consumed CPU cycles, could not be killed by taskmanager and that kept writing to the COUATL.log file which was hundreds of megabytes in size!

Upon closer inspection I found the .INI files for EFB, STB and COUATL to all be corrupt: each was about 1K in size and filled only with zeros (hex).

I've deleted the corrupt .ini files for each product and recreated them. (For GSX and the FSDT sceneries the file I deleted was CouatlAddons.ini).

After a few minutes of testing these products now *seem* to be working fine! Wheph!

But I note the only content in my regenerated CouatlAddons.ini is a "liveupdate" section and an empty "common" section. Is this right? Are there likely to be other impacts for my FSDT products? Should I reinstall them?

Many thanks,
Peter.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51439
    • VIRTUALI Sagl
Re: Corrupted CouatlAddons.ini
« Reply #1 on: March 18, 2012, 11:27:25 am »
Ouch! My computer just experienced a BSOD as I was exiting FSX!

This was surely caused by a faulty driver (video, hard disk, power setting, etc) no FSX program can cause a blue screen on its own


Quote
Upon reboot I launched FSX only to be confronted with an array of errors from AivlaSoft EFB and SuperTrafficBoard. Once I dismissed these I found I also had no COUATL menu, no GSX functionality and no FSDT scenery buildings!

This can happen after a blue screen, if files were open when the crash happened, it's very likely they would end up corrupted.

Quote
Exiting FSX resulted in orphaned COUATL.exe processes running in memory which consumed CPU cycles, could not be killed by taskmanager and that kept writing to the COUATL.log file which was hundreds of megabytes in size!

This is also normal, after a crash. However, keep in mind that Couatl logging should be enabled ONLY for troubleshooting. It's NOT supposed to always run with logging on, our installer never turn it on by default, it can only be turned on manually so, after you don't need it anymore, it's best turning it off.

Quote
But I note the only content in my regenerated CouatlAddons.ini is a "liveupdate" section and an empty "common" section. Is this right? Are there likely to be other impacts for my FSDT products? Should I reinstall them?

That's normal, the live update section is created only AFTER a Live update, and the common section is created only if you change a setting in GSX, like which audio card to use.