I'm noticing that sometimes RAM disk file is not being updated with latest contents upon PC shutdown.
How do I debug the problem and monitor the issue? I haven't find anything in Windows Event Viewer.
I'm using latest version 3.4.5 on Windows 8.1 x64. RAM disk is 1 GB, saved inside D:\RAMdisk1.svi. D:\ is an SSD drive.
SoftPerfect RAM Disk
RAM disk not always being saved
Started by Andrew-guest
Andrew-guest
RAM disk not always being saved 09 July 2014, 14:44 |
Re: RAM disk not always being saved 09 July 2014, 15:47 |
Admin Registered: 18 years ago Posts: 3 519 |
Andrew-guest
Re: RAM disk not always being saved 09 July 2014, 18:42 |
Andrew-guest
Re: RAM disk not always being saved 14 July 2014, 17:38 |
Well, I've just noticed that I can't really confirm my original described problem.
I could see many times that after another reboot RAM disk file still has an old modification date, and I always thought it means that last save attempt failed.
However recently I've checked the actual content of the RAM disk and found out that it still contains the files from the last day, meaniing their creating/modification date were later than modification date of the RAM disk itself. Due to the nature of the content inside (I'm using RAM disk as a folder for browser and its cache) I can't always say what data and how much of it has been lost, because it always gets regenerated quite fast (feeds are being updated with all lost content automatically, logged-in statuses/cookies are quickly fixed by logging in with saved passwords etc). It also can be affected by browser crashes.
I'll look more closely next time something like this happens to better identify the issue, and report back if I find it was really the case of RAM disk save failure.
I could see many times that after another reboot RAM disk file still has an old modification date, and I always thought it means that last save attempt failed.
However recently I've checked the actual content of the RAM disk and found out that it still contains the files from the last day, meaniing their creating/modification date were later than modification date of the RAM disk itself. Due to the nature of the content inside (I'm using RAM disk as a folder for browser and its cache) I can't always say what data and how much of it has been lost, because it always gets regenerated quite fast (feeds are being updated with all lost content automatically, logged-in statuses/cookies are quickly fixed by logging in with saved passwords etc). It also can be affected by browser crashes.
I'll look more closely next time something like this happens to better identify the issue, and report back if I find it was really the case of RAM disk save failure.