it's infuriating trying to force unmount an image every time i accidentally close ram disk. having looked for several hours, i still have not yet once found how to actually use the command prompt to force unmount it.
why is this not an option within the program, and why is it that closing and reopening the program makes the program act as if it's a new user? neither of those is reasonable to me.
SoftPerfect RAM Disk
Option to force mount or unmount
Started by svnhddbst
svnhddbst
Option to force mount or unmount 24 December 2017, 05:25 |
Re: Option to force mount or unmount 24 December 2017, 10:44 |
Admin Registered: 12 years ago Posts: 5 643 |
Sorry it's not quite clear what you would like to achieve.
First of all, it's not easy to accidentally close the RAM disk app, since the [X] button sends it to the notification area, while keeping it running. To really close it, you would need to Choose File - Exit from the main menu or Exit from its pop-up menu in the notification area. And even when you do so, if there are any logon-time RAM disks that would be unmounted, the app will ask you if you want to continue closing it or not.
Secondly, only logon-time RAM disks are unmounted upon app's termination. This is because once the app was terminated, it would have no chance to unmount those disks on logoff, while by definition
logon-time disks were mounted on logon and must be unmounted on logoff. If you want RAM disks to stay even when the app is not running, you should create a boot-time RAM disk via Disk - Add Boot Disk in the main menu.
Thirdly, forced unmount is dangerous as the process forcibly closes all open file handles. This can result in a bunch of problems, from error pop-ups from programs that opened those files to system instability or even BSOD. We don't really want anyone to use this option unless they understand the repercussions.
First of all, it's not easy to accidentally close the RAM disk app, since the [X] button sends it to the notification area, while keeping it running. To really close it, you would need to Choose File - Exit from the main menu or Exit from its pop-up menu in the notification area. And even when you do so, if there are any logon-time RAM disks that would be unmounted, the app will ask you if you want to continue closing it or not.
Secondly, only logon-time RAM disks are unmounted upon app's termination. This is because once the app was terminated, it would have no chance to unmount those disks on logoff, while by definition
logon-time disks were mounted on logon and must be unmounted on logoff. If you want RAM disks to stay even when the app is not running, you should create a boot-time RAM disk via Disk - Add Boot Disk in the main menu.
Thirdly, forced unmount is dangerous as the process forcibly closes all open file handles. This can result in a bunch of problems, from error pop-ups from programs that opened those files to system instability or even BSOD. We don't really want anyone to use this option unless they understand the repercussions.