• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Large Address Aware

It has to be done on whatever executable is calling the DLL.
 
FordGT90Concept said:
It has to be done on whatever executable is calling the DLL.
Click to expand...
but the executable is already LAA (LAA native)

actually, the DLL file is a VST plugin for the executable (digital audio workstation)
not sure if that makes any difference...
 
If the executable is LAA then it can access the full 4 GiB (assuming 32-bit executable) of RAM no matter what DLLs it loads.
 
FordGT90Concept said:
If the executable is LAA then it can access the full 4 GiB (assuming 32-bit executable) of RAM no matter what DLLs it loads.
Click to expand...
But some people said the DLL is 31bit addressing, it recognizes up to 2gb ram only. (practically 2gb ram is enough )

And my PC has more than 2gb ram of coz
so it keeps poping out "low memory" warning dialog whenever it loads audio files, and that's why i asked (thats very annoying)

in short, i just want to make it recognizes ram correctly so that it wont pop up any dialog anymore....

Thanks for you time :)
 
VMS said:
But some people said the DLL is 31bit addressing, it recognizes up to 2gb ram only. (practically 2gb ram is enough )

And my PC has more than 2gb ram of coz
so it keeps poping out "low memory" warning dialog whenever it loads audio files, and that's why i asked (thats very annoying)

in short, i just want to make it recognizes ram correctly so that it wont pop up any dialog anymore....

Thanks for you time :)
Click to expand...

This sounds like you are actually running out of physical memory, which is a separate issue.
 
R-T-B said:
This sounds like you are actually running out of physical memory, which is a separate issue.
Click to expand...
no, there's still plenty of ram left
it is a well known problem for that plugin
 
Executables allocate memory, not libraries. If the library is doing something explicit to memory management that is outside the scope of the operating system, only rewriting the DLL would fix that (in other words, nothing you can do about it).

How much memory does the system have installed? When running a 32-bit program, the ideal set up is having at least 6 GiB of system RAM and a 64-bit operating system. So long as too much isn't running in the background, it should be able to allocate the full 4 GiB to the program. If you have a 32-bit operating system and/or only 4 GiB of RAM, Windows will only grant it memory Windows itself doesn't need (e.g. OS needs 1 GiB so program only gets 3 GiB).

This "low memory" warning could be related to your page file settings rather than RAM. If you disabled page file, for example, it could trigger a warning like that.

There could also be a memory leak or poor garbage collection in that plugin.
 
  • Like
Reactions: VMS
FordGT90Concept said:
Executables allocate memory, not libraries. If the library is doing something explicit to memory management that is outside the scope of the operating system, only rewriting the DLL would fix that (in other words, nothing you can do about it).

How much memory does the system have installed? When running a 32-bit program, the ideal set up is having at least 6 GiB of system RAM and a 64-bit operating system. So long as too much isn't running in the background, it should be able to allocate the full 4 GiB to the program. If you have a 32-bit operating system and/or only 4 GiB of RAM, Windows will only grant it memory Windows itself doesn't need (e.g. OS needs 1 GiB so program only gets 3 GiB).

This "low memory" warning could be related to your page file settings rather than RAM. If you disabled page file, for example, it could trigger a warning like that.

There could also be a memory leak or poor garbage collection in that plugin.
Click to expand...
i tested that on 32gb ram, 8gb ram, 4gb ram machines
page file settings is untouched, i left that as default, will check that out tmr
thanks :)
 
Then I have to assume it's some shoddy coding in that plugin. You've done everything you can from the hardware (adequate RAM, 64-bit OS) and software (enable LAA for the executable) standpoint.
 
Hi All,

I have Windows 10 64Bit (Anniversary) and try to use the LAA in Mass Effect cause freeze with black screen when i try a new game or Load a save. I don't have idea where is the problem, becase (not crash) remaning in black screen. If i provide with task manager is present, already i try logout and ok, or reboot and ok but the game instance remaning black screen.

So i think or is the OS cause problem or my hw configuration.

as hw I have.
CPU I7 4960x
64Gb DDr3
Video Card Nv Gtx1080

Now i think the much problem is possible cause by the a lot of memory I have, or the core? Because i dont' think the problem is the video card, because without LAA the game work.

Please can you help me for that?
 
It just means the game is not compatible with the LAA fix.
 
FordGT90Concept said:
Then I have to assume it's some shoddy coding in that plugin. You've done everything you can from the hardware (adequate RAM, 64-bit OS) and software (enable LAA for the executable) standpoint.
Click to expand...
ok, i confirm that page file setting is unrelated to this issue

the DLL was released ~2003-2004
appearently the programmers hadn't thought of >2gb ramenvironment
so yea...
i guess i will just leave it as it is

thanks for everyone tried to help :)
 
I realize this is old, but:
1. You can remove "Warmane" from the list as it's a game server, not the actual game itself. For world of warcraft just put in "World of Warcraft - up to v3.3.5a". Yes, it does work and solves a lot of memory-related crashes.
2. You can add Assassin's Creed (2008) v1.02

Assuming OP or a mod reads this post.
Ty.
 
OP has left the forum, sadly, but thank you for sharing that! :)
Maybe try tagging here or sending an IM to the OP to see if he can (or is interested) in updating the thread.
 
Last edited:
Considering this isn't an issue with modern software and operating systems, updating lists of software is pretty low priority
The tool/guide here really helped in the early x64 days but it's been 12 years, outside of retro programs this issue fortunately faded away.

@FordGT90Concept are you interested in updating anything here? We could get one of the supermods to unlock the OP if needed
 
thank You for "LAA_2_0_4_NETFRAMEWORK_4_5.ZIP" right now from Germany ! :)
 
shhnedo said:
I realize this is old, but:
1. You can remove "Warmane" from the list as it's a game server, not the actual game itself. For world of warcraft just put in "World of Warcraft - up to v3.3.5a". Yes, it does work and solves a lot of memory-related crashes.
2. You can add Assassin's Creed (2008) v1.02

Assuming OP or a mod reads this post.
Ty.
Click to expand...
Thanks and done. Dead images removed too.
 
I tried using this on SFM but it keeps crashing after using 3gb of Ram, any way to fix this?
 
Hail all:

I have an issue with a program, which refuses to change the LAA from False to True.
It is stuck in False.

Any way to overcome this, please?

Thank you.
 
You may not be doing this on a supported exe file? It's not going to work on native 64 bit programs, for example
 
Mussels said:
You may not be doing this on a supported exe file? It's not going to work on native 64 bit programs, for example
Click to expand...
Thank you for responding.

It is a base x86 executable.
That it is not to be used on a native x64 file seems obvious.
Why, btw, would anyone DOWNGRADE a program?
Seems illogical.
 
You must log in or register to reply here.
Back
Top