AIM toolkit

The other files were changed to update the version string. MSVC 2019 adds this dependence, I could have linked all files statically but that would increase the file size significantly, and I'm not going to use some old VS version to avoid that dependency most users will have an up to date MSVC runtime installed anyways.

The file is based on the ImDiskTk-x64.zip from the latest 20250206 release for 64 bit systems, but I doped the suffix as its the only release, I see how this can be confusing.
EDIT: I have renamed the file on github to ImDiskTk-x64.zip

So if I would provide also a 32 bit driver you would continue the development of the toolkit?

I will consider that.

EDIT: To make it clear the goal of this release was to fix the windows 11 issue, nothing more nothing less, on older systems people can keep using the older drivers.
If there is a benefit for the users in having also the 32 bit version (if anyone actually is still using a 32 bit windows) of the driver I can do that, and I can sign all the user mode files.

 

It seems extremely difficult to find a correct compiler nowadays... MinGW also brings major issues since a few years. I don't care about C standards, I want something that works, something that do not create dependences or increase the size of executables.

Yes, I was mistaken, I did not check all files.

The development, no. It was only a matter of integrating the driver.
Maintaining ImDisk Toolkit has become very difficult and I cannot focus properly on several projects at the same time. There are now too much differences between this and AIM.
Besides, I have new points to develop that can be done only with AIM. ImDisk will soon become ridiculous in comparison.

 

So should I now be using your fork rather than original even if I have no problems running it on Win 11 24H2? I see there is a toolkit version; thank you for that.

 

That depends on: what for.
My intention for the fork is to maintain it as a Addon to Sandboxie and a utility for Major Privacy.
If you want to mount disk images or just use a ramdisk for other purposes I guess AIM Toolkit will continue to be developed and get new functionality which may be useful for other use cases.

 

I only use a ramdisk for SB, it was why I started in the first place and quite a few years ago.

So it makes sense to switch to your fork,and I'll get around to it once I recover from the pain of setting up my new pc from scratch

 

It's always an adventure where you might learn something new or correct anything you were doing wrong, so don't look at it as a pain