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'...
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.
Feature request: save content to img file when shutdown/unmount