Search the Community
Showing results for tags 'fs9 memory alert'.
Found 1 result
Officially, this tweak only works with systems that are 2GB or more aboard. But there are a lot of feedback that it should also work with less RAM - you can try it out safely, more than a blue screen, it will not be, and the change can be made at any time easily reversed. Should also be installed Directx 9c, otherwise it may cause display errors. Nevertheless, and very clear: everyone tried here at your own risk! The conversion is done in two steps. Step one tells Windows XP to allocate more than 2GB of virtual memory available. Step Two tells the individual applications, as the request for more VM can provide the operating system without having this panic closes the "bag". One or the other will already have read about something, but I have not really come complete with instructions, especially not in German language. Step 1: Download the program "4GB patch" http://ntcore.com/4gb_patch.php Make a backup copy of the file fs9.exe Then open the downloaded fs9.exe the tool and patch. This tool is foolproof, and absolutely self-explanatory! The FS is now known that he may ask for more virtual memory and how to do it. Now you have Windows XP will need to know that such a request can come from programs and it should not be alarmed: Step 2: Give Windows XP with a "Run" sysdm.cpl and confirm with OK. Then click the Advanced tab, then on Settings under Startup and Recovery. Then, under System startup, click Edit. Then the file is opened for editing in Notepad. Here appears a text which should be here very similar to this, perhaps he is also identical: [boot loader] timeout=30 default=multi(0)disk(1)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(1)rdisk(0)partition(1)\WINDOWS="Windows XP Professional" /fastdetect In the green line looks at Windows startup to determine how it should be started. There are multiple operating systems installed, or multiple versions of an operating system, so they appear here in the form of several such lines. So that Windows no longer scared now, when a program cries out for more virtual memory, add the green line to the red text. NOTmistype! [boot loader] timeout=30 default=multi(0)disk(1)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(1)rdisk(0)partition(1)\WINDOWS="Windows XP Professional" /fastdetect /3GB /userva=2560 Save the file closes all windows and start the computer. IMPORTANT Who uses Cloud9 products can currently do not use it during the Tweak active. The true but ONLY for the modified fs9.exe. To use a FS session Coud9 a product that needs to be changed fs9.exe FS9.mod and renamed the unmodified backup will be copied into the root directory of FS. Will you use any Cloud9 products, the file must be disabled bglman.dll in the Modules directory with a name change in bglman.off for the session. He has informed Cloud 9 about it and they introduced him to the prospect of dealing with the problem. Subsequent addition: A similar problem as Cloud9 with it unfortunately just with the Yak-40 from Suprunovdesign. This one feels has copy protection within the Gaugefolder that jokes unfortunately also by the changed blocks and address ranges for the use of the aircraft - with the note, the key is wrong. This state exists but ONLY if the FS is started with the modified *. exe file. If you start the FS fs9.exe again with the unchanged, the Yak is working again as usual. A re-entry of keys is not necessary. <The thread is not mine, but it had only translated for better understanding. If possible.> <otherwise, the thread can also be deleted.> Source: http://www.flightx.d...d&threadID=3840 Make a backup copy before and do not mistype !.