20250521 fails to "Run after mounting"

[Evil Quaint]

I am unsure if its only version 20250521 issue, but I'm having issues with running a simple script file with "Run after mounting" feature. I've attached my "RamDisk Configuration" settings.

I've thought it was a "SYSTEM" user issue or something, but no matter what I do, even running something simple as "notepad.exe" is not possible (I'd expect it to not be visible, but the process should exist, no?).

[v77]

Thanks for the report. After a quick test, it seems that the option works when used by the GUI, but not at Windows boot. I will check that.
It seems to be linked to the Mount Point option. No problem if I use a drive letter.

[Evil Quaint]

After a quick test, it seems that the option works when used by the GUI, but not at Windows boot.

By "GUI" you mean "RamDisk Configuration" GUI (The one in the screenshots)? If so, I couldn't get it to work using that either. The entire feature itself is simply not doing anything.

Anyways, I'm glad the issue is getting attention.

My use case for AIM Toolkit is to create a small, persistent across boots, RAM Disk to accelerate/contain some application cache reads/writes to RAM, so it doesn't deprive the SSD of I/O resources in performance critical paths. I'm using hard links from the RAM Disk to physical disk for linking and I encountered a problem where, the AIM Toolkit's load content from folder feature fails to copy already existing hard links. Instead, it simply creates an empty folder in that scenario. I made a script that would simply do this sort of work after mount point, but it seems the feature is broken

¯\ (ツ)/¯

[v77]

So the GUI fails for you?
Well, for now, I found nothing in the source. I hate this kind of bug... But it may hide something else, so I must find it.

[Evil Quaint]

In the "Advanced" tab, if I do unmount and then mount again. The feature, as I expect it, should work, but it doesn't. "Linker.cmd" doesn't run. If I set the path to "C:\Program Files\WindowsApps\Microsoft.WindowsNotepad_11.2501.31.0_x64__8wekyb3d8bbwe\Notepad\Notepad.exe" (either unquoted/quoted, doesn't matter) that wouldn't run either. No (invisible) process is being launched whatsoever.

--EDIT

Oh~! I wrote this simple script:

<# :
  @echo off
  powershell /nologo /noprofile /command "&{[ScriptBlock]::Create((cat """%~f0""") -join [Char[]]10).Invoke(@(&{$args}%*))}"
  exit /b
#>

Write-Host "Mount point loaded." > "D:\Ramdisk Cache\Sync\test.txt"

That seems to work. "test.txt" is getting created after mount/unmount, even though there's no content in it...

Write-Host "Mount point loaded." > test.txt

That was how I initially tested and it seemingly did nothing, but now that I know the issue is that due to "SYSTEM" account it defaults to C:\Windows\System32path ...

Regardless though, New-Item -ItemType Junction -Path $Path -Target $Target fails to work either -_-

-- EDIT

<# :
  @echo off
  set "SCRIPT_DIR=%~dp0"
  powershell /nologo /noprofile /command "&{[ScriptBlock]::Create((cat """%~f0""") -join [Char[]]10).Invoke(@(&{$args} ""%SCRIPT_DIR%"" %*))}"
  exit /b
#>

param(
    [string]$currentDirectory
)

"$currentDirectory" | Out-File -FilePath "${currentDirectory}\test.txt"

This seems to work just fine now. So, at least the mount/unmount works fine and launches the script properly when taking into account SYSTEM shenanigans. Going to test the windows boot now.

P.S Why notepad.exe example doesn't work is unknown though (and I don't really care at this point).

--EDIT

Alright, so I got the GUI part working just like you. However, I can confirm that "Run after mounting" doesn't work upon Windows boot.

[v77]

I have found why it does not work at system boot. The registry value is not copied like the others.
I will upload a fix very soon.

[Evil Quaint]

Looking forward to that!

[v77]

Please try the new release. Because of the missing registry value, you have to recreate the ramdisk: use the "Unmount" button of the second tab, and then recreate it with "OK".

[Evil Quaint]

Can confirm, the issue is fixed. Thanks!