›

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links

Does this program really convert 32bit exe's to 4 gb?

filmoretfilmoret Member EpicPosts: 4,906
in General Gaming
This program claims to alter exe's so they use 4 gb of memory instead of 2.  Not sure if I'm getting this correctly and it looks like you can just patch any exe that is 32 bit and cause it to use more memory.  Just wondering if the theory is even possible.
Are you onto something or just on something?

Comments

  • filmoretfilmoret Member EpicPosts: 4,906
    Oh crap forgot to link the program's page.

    http://www.ntcore.com/4gb_patch.php
    Are you onto something or just on something?
  • k61977k61977 Member EpicPosts: 1,526
    While it may be possible to flag a 32 bit program to run as a 64 bit, I wouldn't try it myself.  There are more differences than just the memory size of the executable between the two.
  • GdemamiGdemami Member EpicPosts: 12,342
    It's nonsense.

    32bit Windows will allocate 2GB addressing space for 32bit executable.
    64bit Windows will allocate full 4GB addressing space for 32bit executable.

    Whole description of the app is bollocks.
  • H0urg1assH0urg1ass Member EpicPosts: 2,380
    I can't imagine the need for such a thing.  A program designed to run as 32 bit is designed around being able to resource that much memory, and shouldn't require any additional memory to operate properly.

    Not only that, but the vast majority of programs these days come with the option to install either 32 or 64 bit?

    So I guess the question is, what program are you desperately needing to up-convert to 64 bit?
  • ZombieCatZombieCat Member UncommonPosts: 55
    It is possible for 32 bit processes to access 4 GB of memory on 64 bit systems assuming that Physical Address Extension is enabled (which I believe it has been by default since Win 7) and the exe has been flagged as Large Address Aware. The LAA flag is usually set before compiling an exe.

    Since the the page you linked does not describe what it does my assumption would be it is setting the LAA flag on what ever file it "patches". It has been a long long time since I have messed with that and I remember the results being mixed. Some exe worked flawlessly others not so much.

  • doragamesdoragames Member UncommonPosts: 15
    I don't think so that the 32 bit couldn't allocate 4 GB memory .
  • CleffyCleffy Member RarePosts: 6,414
    A native 64-bit application will run more detail than a 32-bit. Its one of the main reasons why consoles look good despite using hardware that looks bad on paper.
  • barasawabarasawa Member UncommonPosts: 618
    There have been software methods to make more memory accessible all the way back to the 8-bit days (any earlier than that is before my time). So it's nothing new, but they tend to run as a driver, or in some cases as a wrapper. Something that 'patches' a program sounds odd and questionable to me. Of course, you are unlikely to find much in the way of improvement in most software simply because most of them were built with the expected limitations in mind, so making more memory available to a program that doesn't know how to use it won't achieve anything positive.

    I would suggest that if you are going to test with that, do it in a virtual machine or on a test box only. That doesn't eliminate risks, but it does usually reduce them.

    Lost my mind, now trying to lose yours...

  • Stuka1000Stuka1000 Member UncommonPosts: 955
    filmoret said:
    Oh crap forgot to link the program's page.

    http://www.ntcore.com/4gb_patch.php
    It simply adds the 'LargeAddressAware' flag to the executable, which isn't recommended if you have less than 3Gb of ram.  Note that while it works for many 32 bit executables others will crash so back up the original before altering it.
  • filmoretfilmoret Member EpicPosts: 4,906
    Stuka1000 said:
    filmoret said:
    Oh crap forgot to link the program's page.

    http://www.ntcore.com/4gb_patch.php
    It simply adds the 'LargeAddressAware' flag to the executable, which isn't recommended if you have less than 3Gb of ram.  Note that while it works for many 32 bit executables others will crash so back up the original before altering it.
    Some were saying that this feature is automatic since windows 7.  Does anyone know that is true?
    Are you onto something or just on something?
  • filmoretfilmoret Member EpicPosts: 4,906
    Ok I'm starting to understand this a little more.  The 32 bit programs are designed to run on a system that cannot use more then 4 gb of memory.  So they limit that memory because they cannot take 100% because that will crash the system.  This program supposively makes it so the 32 bit applications will use all of the 4gb without reserving any of it for anything else.  So the program is completely capable of using all of that memory if it is allowed to.  It doesn't have to be recoded for such a process.
    Are you onto something or just on something?
  • filmoretfilmoret Member EpicPosts: 4,906
    Gdemami said:
    It's nonsense.

    32bit Windows will allocate 2GB addressing space for 32bit executable.
    64bit Windows will allocate full 4GB addressing space for 32bit executable.

    Whole description of the app is bollocks.
    Even though windows will attempt to recognize that there is a 32 bit exe.  Not all of them allow windows to use them so this LargeAddressAware has to be added to the exe if it isn't.
    Are you onto something or just on something?
  • CleffyCleffy Member RarePosts: 6,414
    The 32-bit limitation on memory has to do with how many bytes it can create an address for. It goes into programming where each byte of information is addressable in ram so it can be fetched when needed. The maximum addresses you can get out of 32-bits addresses 4GB. This also needs to be used by the system, so the OS limits it to 2. The reason why there is LargeAddressAware option is for 64-bit systems that don't need the reserve space for the OS. You can still only address 32-bits, but you can allocate the maximum amount of space.

    To make a true 64-bit application, you need to design it that way from the outset. Otherwise you aren't making use of what having a 64-bit wide WORD can do aside from address more memory. There is also some syntax and library changes when you go from 32-bit to 64-bit.
    If you have a 32-bit application, it's best to keep it 32-bit since Windows can emulate it.
Sign In or Register to comment.