#17 Feature request: save content to img file when shutdown/unmount

[arnesacnussem]

• The sync function not work that fine when i have a large amount file (e.g. my 3G ramdisk has 32191 files, which took about 10 min longer to shutdown).

• when using dynamic memory allocate, click the unmount button in RamDiskUI.exe do not promopt the save content to img dialog

• although paths on windows is not case sensitive, but the copy file by file mess up the folder's name when i have a folder renamed to lower/upper case.

[arnesacnussem]

but there's also a bug when i try to load a 8G img file (2.5G/8G used) withAllocate Memory Dynamically selected...

after a few secone it popup a dialog shows Error: the volume cannot be mounted.,meanwhile the RamDyn reading the img from disk,after a long time(about 5 min,do not colse RamDiskUI.exe),the volume being mounted with correct content in it.

[v77]

The sync function not work that fine when i have a large amount file (e.g. my 3G ramdisk has 32191 files, which took about 10 min longer to shutdown).

Yes, it can take some time with a large amount of files. For now, I have no idea for improving that.

when using dynamic memory allocate, click the unmount button in RamDiskUI.exe do not promopt the save content to img dialog

The driver reports whether the volume has been modified or not. This is not the case with RamDyn. But you're right, it's not very consistent. I put that on my list.

although paths on windows is not case sensitive, but the copy file by file mess up the folder's name when i have a folder renamed to lower/upper case.

Not sure there is something to do. File systems often have strange behaviors on this point. But I will check that.

but there's also a bug when i try to load a 8G img file (2.5G/8G used) withAllocate Memory Dynamically selected...
after a few secone it popup a dialog shows Error: the volume cannot be mounted.,meanwhile the RamDyn reading the img from disk,after a long time(about 5 min,do not colse RamDiskUI.exe),the volume being mounted with correct content in it.

I just checked the code, and yes, if RamDyn has not finished its startup soon enough (within 15 seconds), it can lead to that.
In this case, Temp folder is not created and parameters are not saved.
I will fix that for the next release. Thanks for the report.

[v77]

although paths on windows is not case sensitive, but the copy file by file mess up the folder's name when i have a folder renamed to lower/upper case.

About that issue, what are the used file systems in the source and the ramdisk?

[arnesacnussem]

Thanks for your reply.
ramdisk:NTFS source:img file or NTFS
there's a while i use folder on NTFS as source,and this happens so i switch to img,but still....
i thought it also can trigger on any file system cause all those fs on windows is case insensitive(according to this Case_sensitivity).
and with default settings in NTFS , the path is not case-sensitive, but case-preserving
here's a example, follow the actions below:

mkdir test
cd test
mkdir ABC

- create a new ramdisk with data copy from 'test' and sync on shutdown option checked
- navigate to ramdisk
- rename ABC to abc
- reboot

after reboot the folder name in ramdisk   is 'ABC'

[v77]

OK I understand. This behavior is a consequence of the method used to copy new files and folders.
I could try to fix that, but there would be a small performance penalty.