A Mugen community that specializes in stage, screenpack creation, and graphics.

You are not connected. Please login or register

Mugen 1.0 (NTCore 4GB Patch)

Go down  Message [Page 1 of 1]

1Tool Mugen 1.0 (NTCore 4GB Patch) on Fri Mar 02, 2018 3:39 am

Vermilion Spy


This is not an official M.U.G.E.N 1.0 patch or build.

M.U.G.E.N 1.0 patched with NTCore's 4GB Patch
for more info visit NTCore's Homepage

About the patch

This patch removes the 32bit application 2GB system Memory allocation limit - extending it to a theoretical 4GB.
Although it is stated as a "4GB patch", the maximum RAM allocated to M.U.G.E.N may vary depending on individual system specs etc.

This will address many crashing issues, out of memory errors, and resource loading errors when running mugen at resolutions above 640x480.
It will assist with the handling of multiple simultaneous large sprites larger than 640x480px in 16/32bit png when OpenGL Rendering mode enabled.
It will assist you in using much higher values for AfterImageMax / LayeredSpriteMax / ExplodMax / SysExplodMax / HelperMax / PlayerProjectileMax.

This was first discovered and applied to Winmugen Plus in 2008 by PhantomGs.

Authors Notes:
4GB Patch
Current Version:

I originally wrote this tool for a friend of mine who needed it. This 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.

Why things are this way on x64 is easy to explain. On x86 applications have 2GB of virtual memory out of 4GB (the other 2GB are reserved for the system). On x64 these two other GB can now be accessed by 32bit applications. In order to achieve this, a flag has to be set in the file's internal format. This is, of course, very easy for insiders who do it every day with the CFF Explorer. This tool was written because not everybody is an insider, and most probably a lot of people don't even know that this can be achieved. Even I wouldn't have written this tool if someone didn't explicitly ask me to.

About NTCore

NTCore is the result of many years of experience. The main purpose of this project is to investigate about system internals and software security, in order to build the best software of its kind for developers and companies. In addition to a good number of free tools, NTCore offers (hopefully) the best (and sometimes the first) technical information about related topics to its products. For direct contact write at:

NTCore started as something very small and mainly for commercial reasons. I needed a name that could be used to work with companies and other developers. It even started as a team. Again, for commercial reasons. However, through the years it became more and more clear to me that I wanted NTCore to become more personal and less commercial. NTCore is now the place where I release my articles and my software, and I hope that you'll find this material useful for you and/or your company.

Daniel Pistelli


Back to top  Message [Page 1 of 1]

Permissions in this forum:
You cannot reply to topics in this forum