Ability to change the size of image-backed RAM disks

Two thing that would be improvements for RAM Disk:

1.The ability to change the size of a RAM disk with an image.

Currently if I need to change the size of a RAM disk with an image, I have to create a RAM disk and image of the new size, mounting both RAM disks, and copying or moving the data from the old RAM disk to the new RAM disk, then unmounting both, changing the drive letters, and remounting one or both.
Couldn't a new size be set, and the image file updated to the new size, with the condition, that the new size is larger than the amount of data currently on the RAM disk?

2. The ability to change the creation state.

In the above example, it's necessary to delete the old RAM disk to stop it being mounted at boot time. Being able to set it's creation state to manual would mean it could be left in place, so if the new size was unnecessary, it could be made active again.

Of course, if 1 was implemented, then 2 wouldn't be needed, but it would be good to have it anyway (since the manual option has been added).

Also, are there any plans to create Linux versions of RAM Disk or NetGenius?

We'll look into this. In theory, resizing of RAM disks and image files is possible, with expansion being easier than shrinking, so we'll likely explore that first.

As for Linux versions of RAM Disk and NetGenius, there are no plans at this stage. Both products rely heavily on custom drivers tightly coupled to a specific operating system. That may change in the future if Linux market share grows significantly and such efforts in software development become economically viable.

While it would be good if it was possible to do this while the RAM disk is mounted (I assume that's what you meant when you said live resizing), it would good if reducing the RAM disk size was possible, even if unmounting the RAM disk first, was necessary.

What about the ability to change the creation state to At Startup, At Login or Manual, for existing RAM Disks?

We've implemented live disk resizing that works in all scenarios: image files on their own, volatile RAM disks, and persistent RAM disks backed by an image file. The only requirements are that the new size must be larger than the current size and the file system must be NTFS.

However, at the moment there is an issue with Microsoft's Hardware Portal for driver signing. Once that's resolved we'll be able to publish the new release: