I came across with this old thread: [GRUB4DOS] Any alternate solution to map 7GB.vhd.GZ on RAM? and while I am not looking to compress my RAM disk for loading into RAM, but found Wonko the Sane, reply seems interesting.
I cannot even imagine WHY exactly one would want/need an 8 Gb image loaded in RAM , but the "right" approach IMHO is to separate the setup in a small, efficient image dedicated to boot the system and another smallish image mounted with IMDISK and expanded to the size you need it.
You can use a mount point and thus the "system" drive will be as large as you need it.
This sounds like the solution what I am looking for. I have tried pooling the RAM disk (Firadisk booted) in attempt to make C: bigger by expanding it to another RAM disk using Softperfect RAM disk (a clean disk). However pooling made another drive letter with both drives compined, and this does not work as most software install parts of itself in system drive regardless which drive you chose to install the program in. I could create one big firadisk image and have grub4dos load the intire thing in RAM, but that seems like a waste of disk space, espicially if most the image will contained free (empty spaces) not ideal when wanting 64 to 128GB of RAM disk space.
So my question is there a tutorial or could a tutorial be written to allow expanding the C: drive using a smallest possible FiraDisk, to boot the system, and then expanding the partition to take up other RAM disk like IMDISK or such? Windows does not like to be installed on Dynamic disk, so cannot spann it's partition over to the next disk.
Edited by RandomUser, 14 May 2015 - 01:10 AM.