Archived

This topic is now archived and is closed to further replies.

northridge

3Gb switch - which Windows XP version?

Recommended Posts

Short flight with system crashes on final all seem to have been caused by multiple Afcads.I am still getting OOMs at the end of long fllights so it looks like I really do need the 3Gb switch.But - I see in the Wikipedia entry that the switch only works with XP Pro or higher. Is this right? Has anyone done it with Home (SP3) ?

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Short flight with system crashes on final all seem to have been caused by multiple Afcads.I am still getting OOMs at the end of long fllights so it looks like I really do need the 3Gb switch.But - I see in the Wikipedia entry that the switch only works with XP Pro or higher. Is this right? Has anyone done it with Home (SP3) ?
HelloWorked fine for me when I was on XP32 home sp3Just download the file below to patch your exe if you are running FS9 or FSX pre SP2Then add /3GB /userva=2560 to your boot.inihere is mine, yours my differ depending on how your disks are configuredmulti(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Home" /fastdetect /3GB /userva=2560 /NoExecute=OptInhttp://www.ntcore.com/4gb_patch.php4GB PatchDate: 29/11/2007 Author: Daniel PistelliThis very little tool patches x86 executables in order to let them have 4GB (instead of only 2) of virtual memory on x64 platforms. This tool comes very handy for applications which need a great amount of virtual memory like games, 3D renderization, multimedia etc. To gain these 2GB, you just have to use this tool to patch the executable (*.exe file) of the software you want to have these additional GBs of virtual memory. It can be used by clicking on it and choosing the file or through command line (e.g.: "4gb_patch file.exe"). It automatically creates a backup copy of the original executable.

Share this post


Link to post
Share on other sites

FSX SP2/Acceleration automatically set the memory switch as appropriate.Since you should fly with SP2 or Accel anyway, there is no need to ever set the memory switch yourself.Cheers,- jahman.

Share this post


Link to post
Share on other sites
FSX SP2/Acceleration automatically set the memory switch as appropriate.Since you should fly with SP2 or Accel anyway, there is no need to ever set the memory switch yourself.Cheers,- jahman.
HelloFSX SP2/Accel are as you rightly pointed out already >2gb awareBut if you read the OP he is specifically asking about XP32 home which does need the boot.ini switch in order to see the memory above3.25 gb, the two go together.Cheers,

Share this post


Link to post
Share on other sites
FSX SP2/Acceleration automatically set the memory switch as appropriate.Since you should fly with SP2 or Accel anyway, there is no need to ever set the memory switch yourself.Cheers,- jahman.
If you are running on a 32bit OS, you must set the memory switch manually as described by mad dog. SP2/Acceleration does not set the 3GB switch within the OS. In SP2/Acceleration the fsx.exe was changed and a flag set which allows FSX to address >2GB of RAM. Originally FSX was only allowed to address 2GB of RAM.

Share this post


Link to post
Share on other sites

mad dog, sargeski,My apologies! Indeed it is as you say.I have run FSX on Vista-64 for many moons so I tend to forget others may still be using a 32-bit OS.Cheers,- jahman.

Share this post


Link to post
Share on other sites

And I have to apologise to you all - I should have said and didn`t - FS9 SP1.The Wikipedia article said that some users had trouble with the system not booting after installing the switch, and recommended putting a second instance of the OS in the .ini file: on startup it will always give me the two choices so if the switched OS doesnt boot I can always fall back on the original. Have you done that?Interesting though how so many presumed I ran FSX. Nicholas

Share this post


Link to post
Share on other sites
And I have to apologise to you all - I should have said and didn`t - FS9 SP1.The Wikipedia article said that some users had trouble with the system not booting after installing the switch, and recommended putting a second instance of the OS in the .ini file: on startup it will always give me the two choices so if the switched OS doesnt boot I can always fall back on the original. Have you done that?Interesting though how so many presumed I ran FSX. Nicholas
HelloI have put in more than one instance when I was testing the USERVA value.set the time out to a reasonable value to give yourself a chance to select the line you want.Here is what I ended up with[boot loader]timeout=2default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS[operating systems]C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdconsmulti(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Home" /fastdetect /3GB /userva=2560 /NoExecute=OptIn

Share this post


Link to post
Share on other sites

Thanks for replying so fast - are you in my timezone or just a non-sleeper? (North East Brasil)Just to get this straight before I try anything:I copy and paste the section that is already there, and alter the second instance to include the switch and the timeout.My timeout currently is at 30.Nicholas

Share this post


Link to post
Share on other sites
Thanks for replying so fast - are you in my timezone or just a non-sleeper? (North East Brasil)Just to get this straight before I try anything:I copy and paste the section that is already there, and alter the second instance to include the switch and the timeout.My timeout currently is at 30.Nicholas
Helloyes copy the section, the timeout at the second line of boot.ini is global, the boot screen will just wait 30s for you to choose.Also change the text in second entry WINDOWS="Windows XP Home" to reflect the difference ie WINDOWS="Windows XP Home 3GB switch"then you will know which one to choose.****MUST READ*****Some useful info here on how to do all of this from within windows including setting the timeout and default operating systemhttp://vlaurie.com/computers2/Articles/bootini.htm

Share this post


Link to post
Share on other sites

Just run the 4Gb patch and get this result: a file which reads 4Gb_patch.exe Backup and a dialogue saying "Couldn`t open executable".Is this right?Nicholas

Share this post


Link to post
Share on other sites
Just run the 4Gb patch and get this result: a file which reads 4Gb_patch.exe Backup and a dialogue saying "Couldn`t open executable".Is this right?Nicholas
Hello Nicholas make sure that your FS9.exe is not read only : right click > properties > general tab

Share this post


Link to post
Share on other sites

4GB PatchDate: 29/11/2007 Author: Daniel PistelliThis very little tool patches x86 executables in order to let them have 4GB (instead of only 2) of virtual memory on x64 platformsAre we on the right track here?I am confused as to why this is the 4 GB patch and not the 3 GB.Also my system is 32bit.Has there been some mixup of thinking?Nicholas

Share this post


Link to post
Share on other sites
4GB PatchDate: 29/11/2007 Author: Daniel PistelliThis very little tool patches x86 executables in order to let them have 4GB (instead of only 2) of virtual memory on x64 platformsAre we on the right track here?I am confused as to why this is the 4 GB patch and not the 3 GB.Also my system is 32bit.Has there been some mixup of thinking?Nicholas
HelloThese modifications have nothing to do with normal memory as such, rather they address the problems of insufficient virtual address space.Out of 4GB 32bit apps (FS9) can normally address the Low 2GB while the HIGH 2GB is reserved for the system.The 3GB boot.ini entry allows 32bit apps (FS9) to address the LOW 3GB with the HIGH 1GB reserved for the system, so more address space for FS9.But not just yet.In order for FS9 to access this extra address space it needs its header modified to mark it as >2gb aware in order to access the addresses >2GB until the 3GB mark everything above is reserved for the system.Now all that being said your graphics card Vram is also mapped into this LOW 3GB and this is where the USERVA setting comes inThese mods are what many of us have had to do to address the OOM errorsA 64bit OS does not need the 3GB boot.ini edit but will still need the FS9.exe marking >2GB aware.Your 32 bit OS needs both.Please read this from Phil Taylor Ex ACES and DirectX teams.http://blogs.msdn.com/ptaylor/archive/2007...ress-space.aspxThen download CFexplorer from the same site as the previous toolcopy FS9.exe to your desktop and open it in CFexplorer the make the exe >2gb aware

Share this post


Link to post
Share on other sites

Good daySuccessfully patched the .exe file and added a new instance to the .ini file thus:[boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS[operating systems]multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect[boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS[operating systems]multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition 3gb switch" /noexecute=optin /fastdetect/3GB /userva=2560 /NoExecute=OptInbut - didn

Share this post


Link to post
Share on other sites
Good daySuccessfully patched the .exe file and added a new instance to the .ini file thus:[boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS[operating systems]multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect[boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS[operating systems]multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition 3gb switch" /noexecute=optin /fastdetect/3GB /userva=2560 /NoExecute=OptInbut - didn

Share this post


Link to post
Share on other sites

Thank you so much for your patience in explaining these steps. I see that you are also helping out another user in another post with the same problems in understanding how this thing works.I was hoping to bring you good news this morning after a 7 hour flight but no such luck. I have "awared" the .exe file and got the .ini file right and have 30 seconds to choose the boot, so set off from KJFK in the MD11 to LSZH, just me, the plane and the scenery on the Server pc and ASA, RC, REX and FSCommander on the Client laptop. The first flight ended after two hours because I am an idiot: I closed FS by mistake! I mean - honestly!On the second flight I had just been passed over to Gander when "bong", a whole long load (really, endless) of scenery cache errors: just endless obscure files missing from payware sceneries, in Canada, Brasil, Mallorca, Tunisia - which is where I gave up clicking on each error message and unplugged the pc.Thing is, I messed with my FS between the two flights - installing DBS Airport GPS onto the Server, which involves running a database, and which I later saw in forums has caused some users some problems. Of course I am not saying that this is what caused the problem. I should have left things alone before trying a new flight. And no, I didnt create a restore point: I am one of the millions of self-taight pc users who found out things the hard way and never learned the right routines.But - putting the 3GB switch apart for a moment - have you any idea what might cause these scenery cache errors? And they were silly files - docking, grass etc - a couple in one scenery, lots in another. I have never ever had this error before.

Share this post


Link to post
Share on other sites
Thank you so much for your patience in explaining these steps. I see that you are also helping out another user in another post with the same problems in understanding how this thing works.I was hoping to bring you good news this morning after a 7 hour flight but no such luck. I have "awared" the .exe file and got the .ini file right and have 30 seconds to choose the boot, so set off from KJFK in the MD11 to LSZH, just me, the plane and the scenery on the Server pc and ASA, RC, REX and FSCommander on the Client laptop. The first flight ended after two hours because I am an idiot: I closed FS by mistake! I mean - honestly!On the second flight I had just been passed over to Gander when "bong", a whole long load (really, endless) of scenery cache errors: just endless obscure files missing from payware sceneries, in Canada, Brasil, Mallorca, Tunisia - which is where I gave up clicking on each error message and unplugged the pc.Thing is, I messed with my FS between the two flights - installing DBS Airport GPS onto the Server, which involves running a database, and which I later saw in forums has caused some users some problems. Of course I am not saying that this is what caused the problem. I should have left things alone before trying a new flight. And no, I didnt create a restore point: I am one of the millions of self-taight pc users who found out things the hard way and never learned the right routines.But - putting the 3GB switch apart for a moment - have you any idea what might cause these scenery cache errors? And they were silly files - docking, grass etc - a couple in one scenery, lots in another. I have never ever had this error before.
HelloGlad you got the boot.ini sorted out, you now have the safety net of your original settings to boot too and CFF explorer or the 4GB tool (whichever you used) has made a backup of your FS9.exe so any issues you can at least revert back.With your problems on your recent flight I would start by renaming the dbs.aptGPS9.dll in the \modules folderthat will take DBS gps out of the equation.The only way to track down these errors is by a process of elimination, these are just a few things to try one by oneRe fly the flight again using a different aircraft, if you have the same errors then pull up task manager and check FS9's memory usage at this point.If it has risen by a large amount then suspect a scenery file is causing a problem.Scan for duplicate Afcads using ScanAFD.Check for any sceneries that may have an empty texture folder.Turn off all sceneries that are not needed for the flight, I have my sceneries ordered by geographical area's and use SCM2004 (a great tool) to enable/disable these and even cut and paste whole sections out of the scenery.cfg when diagnosing errors.Sceneries giving errors can literally be hundreds of miles away from the area you are in at the moment of crash.http://library.avsim.net/esearch.php?CatID...&DLID=45936Using windows search scan for all Scenery.dat files and delete them, the will be rebuilt next time you run the simTurn off your Ai to test , a missing texture on an ai aircraft can cause no end of problems.Always be suspicious of landclass files, disable them and test.If your video card has a large amount of memory you may have to tune the USERVA setting for best results the 2560 setting is for cards with 768mbAdd more lines to your boot.ini so you can test different settings256MB /userva=3072 (ie, 3GB)512MB /userva=2816768MB /userva=25601024MB /userva=2304All this will take a lot of time and patience but its great fun (isn't it?)

Share this post


Link to post
Share on other sites

I removed Airport GPS and that particular problem has not re-ocurred. That program will get sorted out - or not - when the bigger picture is resolved.Alas I am still unable to report a sucessful long flight with complex plane and scenery. The last two attempts were spoilt by CTDs - the first when I was still taxiing nd the second after four hours of flight, with a g3dll error (at least thats what I managed to glean from the Msoft gobbldygook that showed up). Prolly a scenery or Afcad error cos it said it was submitting the FS9 and scenery .cfgs.Yawn Are you getting tired of this? I am. RegardsNicholas

Share this post


Link to post
Share on other sites
I removed Airport GPS and that particular problem has not re-ocurred....Yawn Are you getting tired of this? I am.
Check you have Airport GPS v. 1.3, as it might solve some of your problems.I agree, me too am getting tired of all the bugs, CTDs, lack of FSX updates, Videocard bugs etc. as I tend to spend more time maintaining my FSX setup than flying,and whenever I want to show a friend how this stuff works, well, it doesn't work.Cheers,- jahman.

Share this post


Link to post
Share on other sites

After walking away from FS for more than a month I finally bit the bullet and set myself a long flight, and I am glad to report that I sucessfully completed LSZH-SBGL in the MD11 without a hitch.It looks like the 3Gb switch is doing its job and I thank all of you who contributed to helpng me out in this and a previous post. :( Nicholas

Share this post


Link to post
Share on other sites