Pete Jackson

@w77 Many thanks for the hotfix & further info and hint about RamDyn.exe! :) I now successfully use on boot: RamDyn.exe R: 67108864 -1 1 20 /fs:ntfs RamDisk 4096 1 which creates the drive without an ntfs usn journal - also with correct permissions to manually enable/disable the journal if needed via fsutil.exe While i'm personally happy with this solution, i feel like the inaccessible ntfs usn journal i described in my previous post when using the GUI "Launch at Windows Startup" checkbox still could...

@w77 Many thanks for the hotfix & further info and hint about RamDyn.exe! :) I now successfully use on boot: RamDyn.exe R: 67108864 -1 1 20 /fs:ntfs RamDisk 4096 1 which creates the drive without an ntfs usn journal - also with correct permissions to manually enable/disable the journal if needed via fsutil.exe While i'm personally happy with this solution, i feel like the inaccessible ntfs usn journal i described in my previous post when using the GUI "Launch at Windows Startup" checkbox still could...

@w77 Many thanks for the hotfix & further info and hint about RamDyn.exe! :) I now successfully use on boot: RamDyn.exe R: 67108864 -1 1 20 /fs:ntfs RamDisk 4096 1 which creates the drive without an ntfs usn journal - also with correct permissions to manually enable/disable the journal if needed via fsutil.exe While i'm personally happy with this solution, i feel like the inaccessible ntfs usn journal i described in my previous post when using the GUI "Launch at Windows Startup" checkbox still feels...

@w77 Many thanks for the hotfix & further info and hint about RamDyn.exe! :) I now successfully use on boot: RamDyn.exe R: 67108864 -1 1 20 /fs:ntfs RamDisk 4096 1 which creates the drive without an ntfs usn journal - also with correct permissions to manually enable/disable the journal if needed via fsutil.exe While i'm personally happy with this solution, i feel like the inaccessible ntfs usn journal i described in my previous post when using the GUI "Launch at Windows Startup" checkbox still feels...

Thanks for the very useful hint. (Rights to access the journal might be bullseye) Follow-up: I'd have no problems to create the drive manually myself shortly after boot via (automated) command line aim_ll.exe -a -o rem -s 64G -S 4096 -m R: -p "/fs:ntfs /q /y /v:RAMdisk" Main issue with this for me is that "Memory releasing"/TRIM seemingly does not work when the dynamic drive is created via "aim_ll.exe". Any idea or unknown parameter about that? Thanks again Also: Do i understand correctly that the...

Thanks for the very useful hint. (Rights to access the journal might be bullseye) Follow-up: I'd have no problems to create the drive manually myself shortly after boot via (automated) command line aim_ll.exe -a -o rem -s 64G -S 4096 -m R: -p "/fs:ntfs /q /y /v:RAMdisk" Main issue with this for me is that "Memory releasing"/TRIM seemingly does not work when the dynamic drive is created via "aim_ll.exe". Any idea or unknown parameter about that? Thanks again Also: Do i understand correctly that the...

Thanks for the useful hint. Follow-up: I'd have no problems to create the drive manually myself shortly after boot via (automated) command line aim_ll.exe -a -o rem -s 64G -S 4096 -m R: -p "/fs:ntfs /q /y /v:RAMdisk" Main issue with this for me is that "Memory releasing"/TRIM seemingly does not work when the dynamic drive is created via "aim_ll.exe". Any idea or unknown parameter about that? Thanks again Also: Do i understand correctly that the latest mounting-improvements using the API are only...

Thanks for the useful hint. Follow-up: I'd have no problems to create the drive manually shortly after boot via (automated) command line aim_ll.exe -a -o rem -s 64G -S 4096 -m R: -p "/fs:ntfs /q /y /v:RAMdisk" Main issue with this for me is that "Memory releasing"/TRIM seemingly does not work when the dynamic drive is created via "aim_ll.exe". Any idea or unknown parameter about that? Thanks again Also: Do i understand correctly that the latest mounting-improvements using the API are only usable...