I recently reinstalled my OS with Windows 7 32 bit and I installed Morrowind GOTY, but when I try to run the MGE-GUI it doesn't launch at all. I've read that it needs administrator privileges, so I changed the permissions but it still doesn't launch. I also changed the privileges of the others .exe files (as suggested in the web) and nothing happened. Sometimes I get an error message displaying "the application crashed".
Exactly: each separate .exe process in the OS has its own private VAS, and each one can allocate up to 2 or 3GB for itself under 32 bit Windows, and 2 or 4GB under 64 bit Windows. It's 2 or 3 and 2 and 4 depending if the .exe was compiled with the IMAGE_FILE_LARGE_ADDRESS_AWARE flag enabled.
Note that this space is not really "taken", because a large part of it is represented by Memory mapped files so, the number reported it's only an indication that Couatl.exe asked Windows to provide a "window" (MUCH smaller) over files that were read/written by Couatl for several reasons, but the actual memory allocated might be much less than that, because Windows will then arrange such requests with its own buffers.
And, Couatl.exe being a Python interpreter, it has its own internal memory manager with its own private heap, and there's really no way in Python to leak memory outside that heap, which makes Python a very safe language in regard with memory issues (exactly the opposite of C/C++), it's more similar to C# or Java in this regard.
That's why, it's technically impossible that Couatl.exe would cause an OoM in FSX, Couatl.exe can't even *see* the FSX memory, because they are entirely separate, if you had an OoM in FSX, it could only be caused by something internal to it, like a .DLL (not .EXE) module, either from FSX itself (like the g3d.dll) or from a 3rd party, and this includes also .GAU files for airplanes, which are just .DLL with a different name because the *combination* of all memory allocated by FSX and its .DLL/.GAU modules, exceeded the 3GB that FSX can allocate, since it's a 32 bit app with the IMAGE_FILE_LARGE_ADDRESS_AWARE flag.
This file is best read with word-wrap enabled, unless you are using a device which can display well over 1030 characters per line. :)Flights saved under a different version of FSCaptain cannot be restored. Please complete all outstanding flights before upgrading!The latest version of MakeRwys.exe is included and will be installed to your Flight Sim root folder as long as your current MakeRwys.exe is of an older version. This is a necessary change, as future versions of FSCaptain will use the newly acquired data for a much improved Runways Report. (Thanks as always to Pete Dowson for his diligence, enthusiasm and patience in dealing with multiple requests!))If the installer asks to overwrite existing files, please reply Yes. Some of the core configuration files are kept as read-only, and the installer needs your permission to update them.This version is intended solely to be installed into Prepar3D Version 4 - this version contains DLLs and Gauges compiled against Prepar3D Version 4 libraries.The FCDU.exe application relies on a 32-bit version of SimConnect to maintain compatibility with other SimConnect simulators. If you do not have 32-bit SimConnect installed on your PC, you can download the installer here - _61259.msi================================================================================================================If you are upgrading - to be safe always make a copy of your FSCaptain folder before installing any new version.Download a safe environment and a README from _Safe_Backup.zip================================================================================================================To install simply execute the enclosed exe. It may locate your simulator folder for you but you may browse to another folder if you wish.VERY IMPORTANT !!! When you first install FSCaptain by selecting a target folder manually or by browsing to it, you MUST select the root folder of your FS installation. For example if you have FSX installed in the folder D:\FSX\ then put that path in the target folder for the installer. DO NOT try to install into D:\FSX\FSCaptain\ or any other place. If you do this FSCaptain will not function properly. The installer will automatically find an existing \FSCaptain\ folder and the entire data structure for you in the folder that you specify.=============================================NOTE - Anti-virus programs and "new" Software=============================================Many anti-virus software packages react to new software they have never encountered before. Since you are about to be one of the first to install a new build of FSCaptain, your anti-virus software will be one of the first of its brand to see the new FSCaptain. Some anti-virus programs will flag this for your attention and your intent. Some anti-virus programs will pro-actively attempt to isolate (or quarantine) a new .EXE or .DLL. We have had a report of a widely-used anti-virus program going so far as to isolate text files (.XML and .CFG) that FSCaptain reads.Now it is up to each of us to keep our PCs safe. We can't advocate shutting down your anti-virus programs, but if you could put yours into "install mode" or switch off "live scanning" during the installation, then you may be able to avoid some problems.In general use, if you can have your anti-virus programs exclude your entire flight simulator installation from "real-time scanning," you will better your simulator's performance. Our simulators are constantly reading lots of tiny data files, and if your PC is following each read with having the anti-virus program ask, "What happened just now?" well you can imagine the constant resource drain.Finally, if your anti-virus program does detect FSCaptain and asks to submit it for closer examination by their technicians, by all means you should do so. The sooner that each version of FSCaptain is analyzed (and not just "patterned matched") the sooner it will be taken off their radar.Most Important 2b1af7f3a8