Hi, I'll try the scenery design forum also, since the problem is scenery related I believe. I've been getting this "FS9 Failed to Read from File Error" message quite regularly now. I get a CTD if I press the button to acknowledge the error, and loose all scenery data from that point on if I attempt to continue the flight without pressing on the little error "OK" button that pops up on a little warning window. I have been trying to take a look at what triggers this, with a nice little program called Filemon, but since I am not an expert on the subject, I am not sure what to look for. A few things I have been able to notice is that sometimes the error comes as FS9 is trying to access the FS9.cfg or Scenery.cfg configuration files, or at least it seems this way. Another file or program that seems to appear every time, which I have no idea what it is for is a file called Dxdiag.exe and dw15.exe also.I can provide a copy of the filemon file, but will not paste any samples here due to my ignorance on what parts are really important. Can anybody give me an idea of what to look for? I have Pentium 4, 3.00 GHz Sony Vaio. As you can see it is sort of old. I also have a Radeon X800 Graphics card with 256 mb memory. I run Windows XP 32 Home edition. I have never had these problems before and have been appearing relatively recently on all flights from any place of origin or destination. They are not consistent and sometimes appear short into a flight and sometimes late into it. Any help would be appreciated, thanks.regards,Macs :)

Hi, I'll try the scenery design forum also, since the problem is scenery related I believe. I've been getting this "FS9 Failed to Read from File Error" message quite regularly now. I get a CTD if I press the button to acknowledge the error, and loose all scenery data from that point on if I attempt to continue the flight without pressing on the little error "OK" button that pops up on a little warning window. I have been trying to take a look at what triggers this, with a nice little program called Filemon, but since I am not an expert on the subject, I am not sure what to look for. A few things I have been able to notice is that sometimes the error comes as FS9 is trying to access the FS9.cfg or Scenery.cfg configuration files, or at least it seems this way. Another file or program that seems to appear every time, which I have no idea what it is for is a file called Dxdiag.exe and dw15.exe also.I can provide a copy of the filemon file, but will not paste any samples here due to my ignorance on what parts are really important. Can anybody give me an idea of what to look for? I have Pentium 4, 3.00 GHz Sony Vaio. As you can see it is sort of old. I also have a Radeon X800 Graphics card with 256 mb memory. I run Windows XP 32 Home edition. I have never had these problems before and have been appearing relatively recently on all flights from any place of origin or destination. They are not consistent and sometimes appear short into a flight and sometimes late into it. Any help would be appreciated, thanks.regards,Macs :)

Others may help you better than me but common things are common. First, check your hard drive capacity. FS9 needs quite a lot of free space to run. Second. did you make any changes recently? If so undo them and uninstall any new programs one by one and re-boot each time. Third, are your graphics drivers up to date? They can get corrupted. I suggest you uninstall and remove all your graphics cards drivers. If you had other graphics cards/drivers before which you no longer use, make sure you remove every trace of these. Be careful not to remove any chipset drivers by mistake. Then, with a clean slate, install the latest Radeon ATI drivers for your graphics card for XP. Re-boot. Two other things: dxdiag.exe is a utility which allows you to check your system. If you go to Start then Run and type in dxdiag you will get some info and test options. It would be worth checking your sound card too using this - it's easy once you open the program. Last, why did you run Filemon if you cannot interpret the data it produces?

Last, why did you run Filemon if you cannot interpret the data it produces?

Good point beetlejuice. I am not sure, attempting to shoot int he dark I guess, :( . I actually had a method to the madness in that I could at least find at what point the program stopped working, but since the data file grows so quickly, it can be a tricky thing. This is how I found about the FS9 and scenery config files, which I may be totally wrong on. I will start by cleaning up my HD and checking my G.C. drivers as it is full and their old by now(never updated them). I'll update on my findings. Many thanks again for your help, Regards, Macs :(

Good point beetlejuice. I am not sure, attempting to shoot int he dark I guess, :( . I actually had a method to the madness in that I could at least find at what point the program stopped working, but since the data file grows so quickly, it can be a tricky thing. This is how I found about the FS9 and scenery config files, which I may be totally wrong on. I will start by cleaning up my HD and checking my G.C. drivers as it is full and their old by now(never updated them). I'll update on my findings. Many thanks again for your help, Regards, Macs :(

Hi Macs:You are referring of course to Mark Russinovich and Bryce Cogswell's excellent utility "FileMon" :http://technet.microsoft.com/en-us/sysinte...s/bb896642.aspxBe sure to set a filter for "FS9.exe" ONLY under Options > Filter/Highlight, or your log will be incomprehensibly huge.Then in the Results column watch for failed file "read" operations (Ex: "FILE NOT FOUND", "NO SUCH FILE" etc.) in the log as you scroll through it... that may give you some more leads to investigate.You do not likely need to attempt to run FileMon during a suspect flight location/time, as all default and add-on files which FS knows about are inventoried by FS during EVERY startup of the program before it even displays the main FS menu; this includes pertinent files in its own default folders, and those listed in Scenery.CFG (both when a scenery is set active or not!), as well as all those files in the Aircraft folder chain referenced by MDL and Aircraft.cfg files. Thus you should only need to run a FileMon session from the moment just before you start FS9 to the moment FS9's menu is displayed; use the "Magnifying Glass" toolbar icon to activate and pause the capture to log process.FYI: Usually the failure of a file read in FS9 is due to a missing or damaged texture file required by the 3d scenery object MDL inside a FS library BGL file (which has been called from a scenery object placement BGL based on aircraft navigation in the FS world's Lat/Lon coordinates).If it were due to a missing or damaged texture for an aircraft called by its MDL file, FS would likely crash as soon as the aircraft were picked in the selection menu.Hope this helps! :( GaryGB