I seem to have gotten the error others have reported with respect to "FS out of memory" on start up, which, in reviewing past posts, may be caused by a corrupt page file. I can't seem to find my old page file in order to delete it, though, no matter what search terms I use. Does anyone know how/where to delete a page file that's become corrupt?Any help appreciated, thanks!Best,Joel

Hi Joel,You mean the paging file for the OS? As in what was formerly called the swap file? I'm assuming that you are running WinXP. A search won't reveal it. The closest thing I think you could do would be to tell the OS to not use one(esentially deleting it). Then make the OS create a new one. I'm very surprised that just the page file would be corrupt though. But, what you caould do is the following couple of things.1) Go to 'Control Panel' --> 'System' --> 'Advanced' --> 'Performance Settings' button --> 'Advanced' --> Virtual Memory Change' button --> Check the 'No paging file' bullet. Then before you reboot pull up a command prompt to tell the system to run a chkdsk(check disk). 'Start' --> 'Run' --> Type in 'cmd' and press enter. Then in the command prompt type in 'chkdsk /R'. Press enter. You'll see a message. Close the command prompt. Then reboot.2) Then go through the same process(sans the chkdsk) to create a new paging file. Only to create a new one you'll be checking either the 'Custom size' bullet or the 'System managed size' bullet.Hope that helps,Jim

Hi Again,Just wanted to let you know that what I actually meant to say was...Then before you reboot I recommend pull up a command prompt to tell the system to run a chkdsk(check disk).I left out the 'I recommend', as running a chkdsk is not neccesary to delete and create a new paging file. I only wanted to recommend it to you in order to try and ensure that there is not any problems with your WinXP filesystem in general.Jim

It is also a good idea to use the temporary absence of the page file to defragment the hard drive it is usually on. That way, when you re-create the pagefile you will have contiguous data, reducing the chances of further page file corruption.The memory error message can also be seen by certain systems when you listen to dimwits who suggest setting the computer to large cache (i.e. using the Control Panel-system-advanced-performance settings-advanced-memory usage-system cache). If you've done that, undo it by checking back to `programs` - and don't listen to idiots.Allcott

Hi Alcott,I'll give that a try, but don't have high hopes... this seems to have been caused (initially) by some sort of bad scenery install (I finally got around to loading up the San Diego Coronado bridge), which caused FS to go into a new scenery file creation on startup.Instead of taking about a minute, though, I knew something was wrong when it lasted like a half hour... on getting the "memory" warning I did a check on Avsim and sure enough found that I probably had some bad .bgl that caused the problem. But even on removing all possible offending files I still haven't been able to get FS to start...Best,Joel