1. I often ran into the need of pausing particular cache tasks which I created and only resume them under certain situation. However, every time the PC restarts, primo automatically resumes those tasks; and I have to manually pause them again. I am aware of the command line tools but that is only a workaround and it's not super convenient to do with large amount of tasks. It would been nice if there is an option or checkbox to have previously paused tasks continues to be paused after PC restarts; or if there are other workaround, please let me know.
2. I wonder if there is a way to truly "lock cache content" of either L1 or L2 cache. I am aware the "lock cache content" is available as L1 as an option to lock cache content and restore it upon windows boots; but I am looking for a feature that locks the cache content even during current windows session; so the primocache will not cache in new content(as if the cache task is paused), but only update existing cache blocks and still provide read benefits(as cache is not paused). (I often need the benefit of read cache to speed up the system, but sometimes I have to pause the cache to avoid primocache caching in large unwanted read / write activities; but during this time is often when I need primocache's cache the most during heavy disk activity, and those activity I do not want them to be cached.). Is it possible to keep the cache on and not caching in new content and only update the existing content?
3. I have ran into couple L2 cache issues; specifically creating L2 Cache storage. sometimes after a PC crash(bsod or similar), I would manually restore my OS with backup software in PE enviroment, and to ensure no "offline modification" or data corruption, I would remove the primocache tasks from PE via registry. (both vol and repo keys); I boot into the restored OS, opens primocache and it shows no cache tasks(as expected since i've deleted them via registry). However, when I try to create L2 cache. The previous L2 cache which has been assigned to a cache tasks is unavailable and as if it was still assigned to a "ghost tasks" that I deleted. I have to manually format the old L2 storage (which always fails to format if I assign a drivel letter to it), if I don't assign a drive letter and simply deletes it, and it works(but I want to assign a drive letter to better identify it). So in summery, It would be nice if the L2 storage automatically becomes available if the original task was deleted; and the formatting L2 storage back into a partition needs to be fixed as current it will attempt to format, and fails, and windows will ask you to format it again.
4. I have question regarding "offline modification". I am very careful when it comes to dual booting, and sometimes I do have the need to do so. Everytime I dual boot I have to delete primocache's tasks and rebuild the L2, which is tedious and bad for SSD's write cycle. One tedious way to prevent offline modification in dual boot enviroment is just to physically remove the disks which is associated with another OS. but that is very annoy and hard to do because of m.2s and GPUs(basically tearing entire pc apart). Although I could disable SATA controller in the bios, but there is no way to disable Nvme drives since it's PCIE based, not even in bios as far as I know
; and on top of that, sometimes I do need to access the disks which was associated with primocached OS(only need read access like file copy etc). I wonder if there is any way we can lock the disks from being accessed in another OS? Better yet if there is a way to mark the disk "read-only" it should also do the trick while providing the access and data to dual boot and prevent "offline-modification" to primocache if my understanding is correct(i am aware in windows diskpart can set read-only markers, but not sure how reliable it is). I also wonder if it is considered "safe" to just ONLY booting up into an PE enviroment in regard of primocache's L2 offline modification. Does simply booting into the PE will have risk of modifying or corrupting the L2 cache?(obviously the OS sees the drive and have access to it, which is worrysome for data integrity. If only booting into PE without user's action making any changes to the disks is safe, then would Diskpart "attributes disk read only set" command sufficient to prevent any offline modification if I need to "read" or "access" the data on the cached disk in an offline enviroment?5. I've created a dedicated partition just for my page file(so I can exclusively use primo cache on the page file without affecting other files). Even though I have 128GB of memory, sometimes page file is still being used under some circumstances(either because I actually ran out of 128GB ram, or my Machine learning AI script ran out VRAM(video memory) and is dumping VRAM into page file even my RAM is still available) regardless. I am aware in the old versions it is not recommended to cache page file with primocache since it can cause dead lock; but with new version 4.2.0, is it safe to use deferred write on page file with L1 cache? If it is safe, do I have any risk if my actual RAM usage is very high? say on the border of maxing out 127gb/128gb?
Many Thanks!
