IM Hibernation and IM Reservation - Advanced Invisible Memory Features
This section describes the advanced Invisible Memory features along with OS Invisible Memory Support: IM Hibernation and IM Reservation. When users tick the Enable OS Invisible Physical Memory checkbox at the Options Tab, a dialog pops up to set the advanced options.
Because OS doesn't manage the Invisible Memory, the data on the ramdisk which uses the Invisible Memory is lost when entering the hibernation. (You may find that some data on the ramdisk still can be accessed after resume from hibernation, this is because Windows Cache Manager has cached this portion of data into the visible memory.)
The IM Hibernation feature makes the data in the Invisible Memory be saved to the physical hard disk when going into hibernation and be restored when resuming from hibernation. This feature creates a file named "imhiberfil.sys" in drive C and stores all valid data in the Invisible Memory to this file. So users need to check if there is enough free space in drive C for this file.
Some users may encounter OS freeze or erratic display issues with
Invisible Memory enabled. These issues occurs possibly because of
the conflicts between the VSuite Ramdisk and the video drivers or other
programs. Some video drivers, especially for on-board video
adapter, also use the Invisible Memory. Here are two examples:
1. Gigabyte GA-MA78GM-S2H motherboad, on-board video adapter, with the Frame Buffer Location (FB Location) in the BIOS set to "Above 4G". The video driver uses Invisible Memory for its frmae buffer.
2. Abit F-I90HD motherboard with Video Adapter ATI Radeon HD 3850 (1GB video memory). The video driver with ATI Hypermemory technology uses the first 512MB Invisible Memory.
The IM Reservation featue helps to solve these problems. It can reserve the first portion of Invisible Memory for other programs and do not write any data in this region. This method avoids both the VSuite Ramdisk and the video driver writing data to the same region. Consider the above first example, if the Frame Buffer (or Share Memory) is set to 256MB, users may reserve the first 256MB Invisible Memory to avoid the conflict. In this example, before reservation the OS Invisible Memory that can be used by the VSuite Ramdisk is 4604MB, and after reservation it reduces to 4348MB which means 256MB Invisible Memory is reserved.
Some drivers or programs use Invisible Memory starting from the end. For these cases, users may just limit the total amount of Invisible Memory used to avoid the conflict, because the VSuite Ramdisk uses Invisible Memory starting from the front.
It is easy to change the advanced IM settings after OS Invisible Memory is enabled. Press the Change IM Settings button, a dialog pops up allowing to change the settings.
if currently no any Invisible Memory is used by the ramdisks, the changes takes effective immediately. Otherwise users need to reboot the computer to make the changes effective.