The ramdisk software 5.3.1.x was not conceived to be managed within a non-administrative account. Some settings may be changed within a user account session , although , they may not come into effect since the ramdisk cannot be restarted ( disabled/enabled ). Currently , the "periodic backup" at interval/fixed times and the manually saving of the RAMDisk content do not work either within a user session , due to denied access to the functions within the RAMDisk Device Driver software.
To solve these anomalies , a bunch of changes were necessary within the configuration software i.e. RAMDriv.dll that provides the "RAMDriv Properties" control , and RAMDiskImage.exe that provides the control of the Image File configuration.
Since it is a common practice that any configuration is not allowed when running within a non-priviledged account ( non - administrative account ) , all configuration settings within the "RAMDriv Properties" are now disabled when running as user/guest. The user is still allowed to start up the "Image Configuration" utility. In analogy , all configuration settings within the "Image Configuration" utility are disabled , except for the manually saving of the ramdisk content. Once configured within an administrative account session , the timely backup at interval/fixed times will also work now within a user account session.
These changes are now incorporated into the new variant 5.3.2.*.
How ?
The "Image Configuration" utility creates and launches a service when it is started for the first time. This service ( RAMDrivService ) is then started automatically at boot time , even when logged on as non-administrative user. It serves as lock between the application and the Device Driver which otherwise is not accessible from applications that run in user account context. The effect can be viewed within Task Manager as two different "RAMDiskImage.exe" processes. One of them runs with the SYSTEM account. Data between the RAMDiskImage.exe process running in the user account and the RAMDiskImage.exe service is exchanged via paged memory that uses a file "RAMDiskImage.data" of about 32 MB. This "RAMDiskImage.data" paging file resides in the same folder where the RAMDiskImage.exe resides. Notice that paging of this communication area may slow down the RAMDiskImage.exe execution , especially on systems with less amount of physical RAM.