Ramdisk Ult.6.3.1 reg: iCacls and ACLs...

FAQ, getting help, user experience about Primo Ramdisk
Post Reply
disker
Level 3
Level 3
Posts: 14
Joined: Sun Sep 02, 2012 5:56 pm

Ramdisk Ult.6.3.1 reg: iCacls and ACLs...

Post by disker »

Primo Ramdisk Ultimate v6.3.1 registered
Windows10 professional (x64)
64 Gbyte Ram
Ramdisk on X:

Hello,
there seems to be a problem while copying/ taking over ACL (access control lists) from standard directory to ramdisk. ACLs are not overtaken in proper manner, especially some setup programs do not find extracted files located in ramdisk drectory because of denied access.
Please compare:
compare.jpg
compare.jpg (62.36 KiB) Viewed 4131 times
Copying by TotalCommander with NTFS permissions activated didn't work. Even the manipulation of ACLs by icacls.exe didn't do the trick, there must be a difference between standard windows user directory and its 'clone' on ramdisk!?

How to put user's temp directory to ramdisk with proper ACLs?
C:\Users\user1\AppData\Local\Temp\ >> X:\1\Temp\

Thanks and best regards,
Chris
User avatar
Support
Support Team
Support Team
Posts: 3627
Joined: Sun Dec 21, 2008 2:42 am

Re: Ramdisk Ult.6.3.1 reg: iCacls and ACLs...

Post by Support »

Thank you for the bug report! We'll check this soon. How about using the FAT32/exFAT file system to temporarily overcome this issue?
disker
Level 3
Level 3
Posts: 14
Joined: Sun Sep 02, 2012 5:56 pm

Re: Ramdisk Ult.6.3.1 reg: iCacls and ACLs...

Post by disker »

Because of security reasons FAT32/exFAT seems not be be a good idea, cross access is possible... NTFS is needed.
Best regards!
User avatar
Support
Support Team
Support Team
Posts: 3627
Joined: Sun Dec 21, 2008 2:42 am

Re: Ramdisk Ult.6.3.1 reg: iCacls and ACLs...

Post by Support »

We checked Windows 10 default security settings for NTFS folders. There are only four group/user names: Authenticated Users, SYSTEM, Administrators and Users. The folders in C:\Users\[user]\AppData\Local\Temp is dedicated to the user account, so the security setting contains the [user] name. It is possible that there are multiple users in a Windows system, and they all may access the ramdisk. Primo Ramdisk cannot know who will access the ramdisk, so it just set up the default security settings.

A workaround for this problem is to enable the image feature for the ramdisk, and manually add the security setting for the specific user. After all settings are done, you may make remove all save modes in the ramdisk image settings, thus the image file is only be loaded from the Windows boot-up and will not be saved/updated.
Post Reply