Cheez
Moderator
The quote from their website says it all. I can't say it better. Anybody keen to give it a go and see if it makes any difference?
---
"Although the maximum addressable memory in the 32-bit world is 4GB every process running in 32-bit Windows XP normally have access to at the most 2GB us memory for its own use not matter how much RAM memory there is in the machine as the other 2GB is locked away for the systems' internal use. The scenario in the music world where we're likely to encounter this limit is when using software samplers and plugin hosts hosting software samplers where lots of data needs to be loaded into RAM memory. Microsoft also acknowledged this problem and created a way to circumvent this problem, at least partially. By using a combination of an option in the boot configuration and an application capable of detecting this option if possible to push the limit to 3GB thus leaving 1GB to the system.
The boot option is easy to set by editing a simple file, but the problem is that not all applications we're using have support for the option. Due to the ingenious design of this feature however it's possible to make any application aware of this option without having access to the source code or having to rebuild the application.
There are a couple of tools out there that are capable of doing this, but they are all directed to developers and not end-users as end-users are not normally supposed to fiddle with these things. Nothing could be more wrong when it comes to the memory hungry music community! In order to provide an easy-to-use tool which contains some additional safety measures I wrote LaaTiDo, the LargeAddressAware Editor."
---
Link: http://www.musikbanken.se/TechLaaTiDo.aspx
---
"Although the maximum addressable memory in the 32-bit world is 4GB every process running in 32-bit Windows XP normally have access to at the most 2GB us memory for its own use not matter how much RAM memory there is in the machine as the other 2GB is locked away for the systems' internal use. The scenario in the music world where we're likely to encounter this limit is when using software samplers and plugin hosts hosting software samplers where lots of data needs to be loaded into RAM memory. Microsoft also acknowledged this problem and created a way to circumvent this problem, at least partially. By using a combination of an option in the boot configuration and an application capable of detecting this option if possible to push the limit to 3GB thus leaving 1GB to the system.
The boot option is easy to set by editing a simple file, but the problem is that not all applications we're using have support for the option. Due to the ingenious design of this feature however it's possible to make any application aware of this option without having access to the source code or having to rebuild the application.
There are a couple of tools out there that are capable of doing this, but they are all directed to developers and not end-users as end-users are not normally supposed to fiddle with these things. Nothing could be more wrong when it comes to the memory hungry music community! In order to provide an easy-to-use tool which contains some additional safety measures I wrote LaaTiDo, the LargeAddressAware Editor."
---
Link: http://www.musikbanken.se/TechLaaTiDo.aspx
