Each individual program in a Windows environment (and in other environments as well) can access two kinds of memory; System Memory and User Memory.<\/p>\nngg_shortcode_0_placeholder\n
System Memory<\/strong> (red in schema) contains the program code and various settings and tables handled by Windows. In this memory area, only Windows can read as well as write (to load the program), while the program itself in that area can read only. This is to protect systems against viruses, against self-modifying code and against other potential threatening program behavior.<\/p>\n User Memory<\/strong> (blue in schema) is the area where the program itself is allowed to read and write, to store and retrieve it\u2019s intermediate values and results from user actions. When the program is up to something massive, this area is blown to pieces.<\/p>\n While each 32-bit program \u2013 without any exception \u2013 can deal with a maximum 4Gb of memory in total, most programs are created in such a way that 2Gb is the maximum amount of user memory they can handle, even when they are assigned more bij Windows. See the top Exe in the schema, blue and red areas equal in size.<\/p>\n Unless the program is made \u201cLarge Address Aware\u201d (or: LAA) in which case those kinds of limits are off. see the bottom two programs in the schema, the blue is larger than the red one.\u00a0 This can be done at creation time, by the supplier, and happens more and more. It can also be done at production time, by you on your PC, and requires a special piece of software, like \u201cLaaTiDo\u201d.<\/p>\n This program makes slight changes to your software. As this has some risks involved, you make copies of the original first, of course. An issue is, that each time a new version (update, service pack, \u2026) of that software is installed (from upgrading or whatever), you have to deal with the new executable all over again.<\/p>\n The following programs<\/p>\n are known to be LAA, and do not require further treatment, while<\/p>\n and known NOT to be LAA and do require this enhancement. I\u2019ve no knowledge yet on Poser 7 and before, Daz Studio 2, Photoshop CS4 \/ Elements 8 and before and the latest PaintShopPro X3. Anyway, for Poser, Daz Studio and Carrara upgrading is a recommended alternative for fiddling with the program\u2019s executable.<\/p>\n First of all, you have to make sure you need this kind of solution. Is the problem you\u2019re facing caused by the 2Gb User Memory boundary indeed? Read the previous Monitoring User Memory section about it.<\/p>\n To continue, you’ll need the LaaToDo program. Download <\/a>the LaaTiDo service program discussed in this tutorial, as well as this tutorial in PDF format (4Mb).<\/p>\n Second, you\u2019ve to locate all the relevant executables in your Program Files folder, and copy (not move!) them to a place to work them, like a new folder in your Temp directory.<\/p>\nngg_shortcode_1_placeholder\n This is because you (and Windows) don\u2019t want LaaTiDo or any other application to write in your Program Files directly.<\/p>\n Third, start LaaTiDo and open one of those executables for inspection (1), then click the [Check] button (2). Is it Large Address Aware (LAA)?<\/p>\nngg_shortcode_2_placeholder\n If so, you\u2019re done, just test other executables. You may find that when a supplier made the program LAA, all relevant executables are so already. When the supplier did not, non of those are and you have to make them so.<\/p>\nngg_shortcode_3_placeholder\n Forth, for non-LAA executables (1), you [Check] (2), then [backup] (3) and then click the [Enable] button 94). That\u2019s it, and you\u2019re almost done. Repeating the previous Check (5) will show you that the new executable is LAA aware indeed now.<\/p>\nngg_shortcode_4_placeholder\n Finally, you move the adjusted executables AND their respective unchanged copies (!) back to the Program Files environment, overwriting the existing ones. This is manual action, and Windows will ask you for confirmation.<\/p>\nngg_shortcode_5_placeholder\n Now you can test your adjusted program, in simple conditions. Does it seem to work? Then you\u2019re fine. Does it fall apart instantly? Then you have to step back, and transfer your backed up unaltered copies onto the altered ones or so, as the LAA progress is not working for them. That means end of the road indeed, stepping towards all 64-bit software is the only way to go now.<\/p>\n When is does seem to work, and you\u2019re in a 64-bit Windows environment, or a 32-bit environment which is set ready before, then you\u2019re done indeed. If not, then all you\u2019ve got to do is to adjust your 32-bit Windows as well. The next section tells you how.<\/p>\n Next ><\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Raising Large Address Awareness Each individual program in a Windows environment (and in other environments as well) can access two kinds of memory; System Memory and User Memory. System Memory (red in schema) contains the program code and various settings and tables handled by Windows. In this memory area, only Windows can read as well … Continue reading “Breaking the 2Gb Barrier? (3 Awareness)”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[6],"tags":[135],"series":[15],"class_list":["post-116","post","type-post","status-publish","format-standard","hentry","category-system","tag-system","series-running-out-of-memory"],"_links":{"self":[{"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=\/wp\/v2\/posts\/116","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=116"}],"version-history":[{"count":10,"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=\/wp\/v2\/posts\/116\/revisions"}],"predecessor-version":[{"id":3042,"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=\/wp\/v2\/posts\/116\/revisions\/3042"}],"wp:attachment":[{"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=116"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=116"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=116"},{"taxonomy":"series","embeddable":true,"href":"http:\/\/www.book.artbeeweb.nl\/index.php?rest_route=%2Fwp%2Fv2%2Fseries&post=116"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
How to proceed?<\/h2>\n