FORGET /3GB switch, Landclass and everything else - if you have problems with scenery crashing you sim, this won't help, but if you have "Flight Simulator has run out of memory"-type error, then this is THE way. I just wonder, after zillion posts around forums, everyone forgets one and only thing:Has FS9.exe been CHANGED to be LARGEADDRESSAWARE?What Opa posted is correct, though it applies to FSX, not FS9 and also only to 32bit OS.What I figured out of these posts, you already have 64bit windows, doesn't matter which version, then do following, if you didn't do it already:1) Download http://www.ntcore.co...plorerSuite.exe2) File/Open...fs9.exe3) Click "File Header"4) On the right side, Click here (in blue)5) Check "App can handle >2GB address space", OK...6) File->Save, ExitRun FS9.Now, an short explanation: FS9 can by default use 2GB of VAS. FSX by default 4GB. This change allows FS9 also to use up to 4GB of VAS. VAS is NOT physical or swap memory, has absolutely nothing to do with your RAM.If you keep getting this error after making this change, then you have to start observing VAS usage with Process Explorer... I'll explain that if it comes to that.Enjoy.

Erm, Word Not Allowed... You do realize that whatever you said in your post is all done automatically by the utility I linked to, yes? The utilty makes FS9 large adress aware. So, you can't really say that "everybody forgot" about it. For the rest I can't argue on what you say about VAS and RAM. I always got it explained as FS9 not being able to access all 4GB of RAM on your system (because it is not large adress aware), and the 3GB switch enables that (for 32bit systems it will be max 3GB, 64bit systems 4GB).vortex777: when you click "start FS" within ActiveSky, Activesky then calls for FS9.exe to be run. In other words, it does not matter how you start up FS9.exe. If you run FS2004, you use FS9.exe, simple as that. Now, simply patch FS9.exe using the utility I linked to and see if it works. If not, too bad, if yes, be happy and fly ;-) But, in any case, just try it. As I said, it can do no harm, but I do recommend backing up FS9.exe, just to be on the safe side.

Erm, Word Not Allowed... You do[i/] realize that whatever you said in your post is all done automatically by the utility I linked to, yes? The utilty makes FS9 large adress aware, and for as far as I understand it, that's the whole trick of the 3GB switch. HOWEVER, on 32bit os's, you can't make it work with 4GB, it will max out on 3GB. On 64bit, this is no problem, and then FS9 will be able to use the full 4GB, if you have it in your computer.vortex777: when you click "start FS" within ActiveSky, Activesky then calls for FS9.exe to be run. In other words, it does not matter how you start up FS9.exe. If you run FS2004, you use FS9.exe, simple as that. Now, simply patch FS9.exe using the utility I linked to and see if it works. If not, too bad, if yes, be happy and fly ;-) But, in any case, just try it. As I said, it can do no harm, but I do recommend backing up FS9.exe, just to be on the safe side.

I patched it. I flew around frankfurt a lot. It didn't crashed :) Now I will fly in Kai Tak with scenery and will see. I think it will help :)

I patched it. I flew around frankfurt a lot. It didn't crashed :) Now I will fly in Kai Tak with scenery and will see. I think it will help :)

Good! As I said, it worked for more. Like a wonder, the crashing stopped, and thanks to that utility applying the patch is as easy as walking down the street.

Good! As I said, it worked for more. Like a wonder, the crashing stopped, and thanks to that utility applying the patch is as easy as walking down the street.

I also flew with Airsimmer witch is famouse with crashing xD and it didn't crashed.

Erm, Word Not Allowed... You do realize that whatever you said in your post is all done automatically by the utility I linked to, yes? The utilty makes FS9 large adress aware. So, you can't really say that "everybody forgot" about it. For the rest I can't argue on what you say about VAS and RAM. I always got it explained as FS9 not being able to access all 4GB of RAM on your system (because it is not large adress aware), and the 3GB switch enables that (for 32bit systems it will be max 3GB, 64bit systems 4GB).vortex777: when you click "start FS" within ActiveSky, Activesky then calls for FS9.exe to be run. In other words, it does not matter how you start up FS9.exe. If you run FS2004, you use FS9.exe, simple as that. Now, simply patch FS9.exe using the utility I linked to and see if it works. If not, too bad, if yes, be happy and fly ;-) But, in any case, just try it. As I said, it can do no harm, but I do recommend backing up FS9.exe, just to be on the safe side.

Uh, sorry, must've missed your post. I went through the whole thread and read about landclass, and /3gb patch. I didn't read THAT carefully :( But can't argue about how often this subject has been recycled around here :( In that case, it should have been solved for him, if the error is indeed OOM.

Uh, sorry, must've missed your post. I went through the whole thread and read about landclass, and /3gb patch. I didn't read THAT carefully :( But can't argue about how often this subject has been recycled around here :( In that case, it should have been solved for him, if the error is indeed OOM.

I thought the 3GB switch would be your procedure Word Not Allowed, at least what I read in other discussion. So what is the 3gb switch in your opinion?I referred to the procedure which allow Fs9.exe to increase more than 2GB.

I thought the 3GB switch would be your procedure Word Not Allowed, at least what I read in other discussion. So what is the 3gb switch in your opinion?I referred to the procedure which allow Fs9.exe to increase more than 2GB.

No, 3GB switch is a trick that allows FS9 to use 3GB of VAS on a 32bit system, and leave 1GB for a system, since 32bit OS addesses max. of 4GB. You CAN'T give FS9 4GB under 32bit system. There is no opinion on this, it does that and only that.Under 64bit, you can give it full 4GB, since 64bits support way more... someone educate me exactly how much :(

Uh, sorry, must've missed your post. I went through the whole thread and read about landclass, and /3gb patch. I didn't read THAT carefully :( But can't argue about how often this subject has been recycled around here :( In that case, it should have been solved for him, if the error is indeed OOM.

True, so true. The switch can make many headaches disappear, but often you don't see it mentioned. I say we set up a local campaign

Thralni,Is there a simular utility for Windows XP 32 bit systems? Thanks

Thralni,Is there a simular utility for Windows XP 32 bit systems? Thanks

You can use the same utility. However, because it is a 32bit OS, the gain will not be as big as on a 64bit OS. On 64bit, you can make FS9 use 4GB instead of 2, while on a 32bit OS it will be 3GB instead of 2. Still, it's worthwhile to use the patch.

Thralni,Is there a simular utility for Windows XP 32 bit systems? Thanks

You do not need this for 32Bit. 32Bit doesn't allow to have more 3.50 GB. And softwere uses more then 2 GB. I think so lol :D

Thanks for the reply. Is there a utility for FSX as well?Regards.

Thanks for the reply. Is there a utility for FSX as well?Regards.

The utility should work for any[/y] program, because all programs are the same in that respct: they all have to be made large adress aware before they can utilize more than 2GB. So yes, it works for FS9, FSX, on Windows XP 32bit, 64bit, Windows 7, Vista, whatever, it could always work. However, I do not guarabntee anything! Make a backup, just to be on the safe side!Vortex777: see my reply just before yours: the patch is also useful on 32 bit OS's, because the program can use more than 2GB even on a 32bit OS. However, it will not use more than 3GB. On 64bit it can use more than that. Still, an increase of 1GB still is quite a lot and is always worth a try in my opinion.

One possibility is that your paging file is corrupt. FSX will generate this message for one of four reasons - 1 You don't have enough physical RAM - however, FSX can't address more than 3GB anyway even if you are running Win7 64bit and most modern system have at least 4GB - so this is unlikley2 Windows has run out of disk space - which means you either have a small disk or a very full one and need to clear stuff out4 Your Graphics setting are too high for your Graphics card/processor and FSX Config settings to cope with - unlikely if this message has come out of the blue but could be a result of USEPOOLS setting (se below) 5 You page.sys file is corrupt. This can happen when FSX aborts/crashesBecause of the memory limitations of FSX (32 bit application and all that), it handles all those lovely add- on airports textures etc by using an area of your hard disk as a virtual memory store where it swaps things in and out. If this area is corrupt it can't swap things in and out and runs out of memory pretty damn quickly.You could start by rebuilding your page file - easy - under windows 7 log onto an account with admin privileges - go to control panels and select 'SYSTEM & Security' select 'system' and click on 'advanced system settings' On the 'advanced tab' look for 'performance' and click on the 'settings button' Now go to the 'Adanced' tab and you will see a heading for 'virtual memory' click on the change button and then click 'custom size' enter 0 in both the maximum and minimum boxes click on 'set' and OK. Ignore the error message. Now reboot you PC and go through exactly the same procedure again. When you reboot for the second time you will get an option to overwrite the paging file - select yes. Job done.If this doesn't work - check your FSX config file (you can do this the easy way by downloading fsx config edit from Tweak FS (freeware) - check that the entry for 'usepools' is set to 1 (the zero entry will only work if you have a mega PC with a stonkingly good graphics card) sometimes the Usepools setting get set back 0 as a result of FSX corruption and CTDs - I know not why. If these suggestions fail turn your graphics setting in FSX down If all of the above fail you are probably in spending money land.Hope this helpd you and anyone else with same problem.

One possibility is that your paging file is corrupt. FSX will generate this message for one of four reasons - 1 You don't have enough physical RAM - however, FSX can't address more than 3GB anyway even if you are running Win7 64bit and most modern system have at least 4GB - so this is unlikley2 Windows has run out of disk space - which means you either have a small disk or a very full one and need to clear stuff out4 Your Graphics setting are too high for your Graphics card/processor and FSX Config settings to cope with - unlikely if this message has come out of the blue but could be a result of USEPOOLS setting (se below) 5 You page.sys file is corrupt. This can happen when FSX aborts/crashesBecause of the memory limitations of FSX (32 bit application and all that), it handles all those lovely add- on airports textures etc by using an area of your hard disk as a virtual memory store where it swaps things in and out. If this area is corrupt it can't swap things in and out and runs out of memory pretty damn quickly.You could start by rebuilding your page file - easy - under windows 7 log onto an account with admin privileges - go to control panels and select 'SYSTEM & Security' select 'system' and click on 'advanced system settings' On the 'advanced tab' look for 'performance' and click on the 'settings button' Now go to the 'Adanced' tab and you will see a heading for 'virtual memory' click on the change button and then click 'custom size' enter 0 in both the maximum and minimum boxes click on 'set' and OK. Ignore the error message. Now reboot you PC and go through exactly the same procedure again. When you reboot for the second time you will get an option to overwrite the paging file - select yes. Job done.If this doesn't work - check your FSX config file (you can do this the easy way by downloading fsx config edit from Tweak FS (freeware) - check that the entry for 'usepools' is set to 1 (the zero entry will only work if you have a mega PC with a stonkingly good graphics card) sometimes the Usepools setting get set back 0 as a result of FSX corruption and CTDs - I know not why. If these suggestions fail turn your graphics setting in FSX down If all of the above fail you are probably in spending money land.Hope this helpd you and anyone else with same problem.

You do realize you made couple of really wrong statements?1) Physical RAM has nothing to do with the fact how much FS9 or FSX can address2) Physical RAM has nothing to do with virtual space either sim occupies3) FSX and FS9 both can address 4GB, not 3GB, and yet, nothing to do with the RAM you have in your computer4) Erm, BUFFERPOOLS have nothing to do with sim crashing with not enough memory problem - it will crash if you overload it, but with all other errors, except OOM5) It's not page.sys but pagefile.sys, and corrupted pagefile.sys is old WinXP error (not that I ever had or heard anyone have the problem), not relevant in W7 I believe, nor have I ever heard sim crashing because of that - but hey, if it happens, your solution is definitely a good way to solve it!I'm sure your intentions were all for the best, but I'd suggest you get into the matter a bit more before trying to help the wrong way.And btw. reading through the post would've revealed to you that the problem has been solved, I believe. Since the original poster didn't say a thing any more.