As part of earlier changes, I noticed that many dialog resources still use keywords that are specific to the 16 bit memory manager. This change removes those to help keep the code cleaner and easier for new readers to understand.
In the 16 bit model, individual resources specify whether they can be loaded lazily, discarded if not in use, or moved around in memory when not in use. In the 32 bit model, resources exist in a single memory mapped section, so they are loaded and retained based on memory pressure and cannot individually specify behavior since they reside on the same pages.
As part of earlier changes, I noticed that many dialog resources still use keywords that are specific to the 16 bit memory manager. This change removes those to help keep the code cleaner and easier for new readers to understand.
In the 16 bit model, individual resources specify whether they can be loaded lazily, discarded if not in use, or moved around in memory when not in use. In the 32 bit model, resources exist in a single memory mapped section, so they are loaded and retained based on memory pressure and cannot individually specify behavior since they reside on the same pages.