I was wondering if anybody has got this error before "Faield to read from file" ?and what it means, as I now get it on every flight. I am almost at rope's ends (after trying a myriad of things, and with no clear reason why it happens. It seems to me it has to do with storage capacity, but it is not clear of what, as it not exclusive to scenery or aircraft textures, many thing seem to trrigger it. A full discussion of all the things I've looked at is too long, but was hoping somebody might give a light on what may be causing this and how I may hope to fix this. Any help would be appreciated and many thanks in advance,regards,Macs P.S.: I have a Pentium 4, 3.00 GHz machine with 1 GB Memory, with an ATI Radeon HD 4550 G.C.

MacsOk, I'm new to your problem, so forgive me if you've answered these questions before. 1. Why am I looking at a fraps window? You're really running fraqps at FS9 startup?b. Alacrity PC can't find it's own folder?3. Have you tried running FS9 without those two programs? Both of them have been known to cause problems for some people.I used to run FS9 on a P4 2.4 ghz, 1.5 gb ram,ati agp 9550 gpu. Not as good as your rig , I'd say. I ran with most settings maxed, although I did not run many addons. FS9 ran good without shutting down services. I did have to shut off AV.Good luck.Bob

Macs Ok, I'm new to your problem, so forgive me if you've answered these questions before. 1. Why am I looking at a fraps window? You're really running fraqps at FS9 startup? b. Alacrity PC can't find it's own folder? 3. Have you tried running FS9 without those two programs? Both of them have been known to cause problems for some people. I used to run FS9 on a P4 2.4 ghz, 1.5 gb ram,ati agp 9550 gpu. Not as good as your rig , I'd say. I ran with most settings maxed, although I did not run many addons. FS9 ran good without shutting down services. I did have to shut off AV. Good luck. Bob

Bob, Thanks for your input. The screen you see there is what I get after the crash. The reason for them is that I run Alacrity and had recently added Fraps to the start up as a test. I really do not run Fraps every time, but it just happens that I forgot to delete it from start up config on Alacrity. Anyway, the error happens regardless of Fraps being part of it, or Alacrity itself for that matter. The error can happen at the beginning of the flight or the end or the middle or at whatever stage, there is no clear pattern. I have also noticed that textures for the airplane on spot view, go transparent for some reason. One thing is for sure, it is tied to graphics load, but what part? I was hoping somebody had encountered this error message before and found a way to fix it. Thanks anyway for your help, regards, Macs :)

Bob, Thanks for your input. The screen you see there is what I get after the crash. The reason for them is that I run Alacrity and had recently added Fraps to the start up as a test. I really do not run Fraps every time, but it just happens that I forgot to delete it from start up config on Alacrity. Anyway, the error happens regardless of Fraps being part of it, or Alacrity itself for that matter. The error can happen at the beginning of the flight or the end or the middle or at whatever stage, there is no clear pattern. I have also noticed that textures for the airplane on spot view, go transparent for some reason. One thing is for sure, it is tied to graphics load, but what part? I was hoping somebody had encountered this error message before and found a way to fix it. Thanks anyway for your help, regards, Macs :)

I've seen that error in conjunction with a corrupt .bgl or texture file...could be a scenery, or an AI plane, for example. Using an AI plane made for FSX in FS9 or vice versa can cause it.You might try running the freeware utility FileMon in the background...it should give you a clue as to what FS9 is accessing when it blows up.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Yeah, the colonel's right. FileMon works great but it has been superseded by ProcessMon these days. I use it all the time, that is, when I'm writing recursive threading in hopes of catching memory leaks. It works just fine monitoring file accesses as well. FS9.exe is the process you'd be monitoring by setting that name as a filter and then further refining the filter on disk accesses. The whole monitoring operation can be written to a log and then read back at a later time.Process Monitor is available here...http://technet.microsoft.com/en-us/sysinte...s/bb896645.aspxMark

Thanks to all for the input. I'll keep on checking with the process monitors. regards,Macs :)

Hi, After running filemon and FS9 successfully, and experiencing another crash, (but no "failed to read from file" this time) I found these entries that look suspicious. I did not include a bunch of "RANGE NOT LOCKED" entries as I ran out of space to copy the images, but they did appear. Any ideas? I can see on some of them how it had trouble finding files, as they are not there, but who told FS9.exe to look in there for those files in the first place? I know the scenery folders for that particular airport are not missing files (NAURU005) from the installation originals, and I know those weird named ones do not belong there. What does buffer overflow mean in this case? What does "range not locked means"? Is a "NOT FOUND" message necessarily relating to a failure and thus possibly related to a crash? Also, why go look at the Desktop.ini file? Is there any place I can find where the source of these instructions come from? I am not expert on this, so am really in the dark. Many thanks for your help in advance, regards, Macs :)