Originally Posted by Unit Igor
You should throw here some non-enterprise benchmarks.
That test system is definitely something i like to have man,those 128GB of DDR3.I dont understand that somebody cant invent how to install OS on those 128GB DDR3.
That's an interesting idea, installing an OS on a RAM disk. With more boards and Windows versions that support even 32GB of memory, installing an OS on 24GB could be possible.
How about software that is run as an option in the BIOS/UEFI, or as an Option ROM during POST. RAID Option ROMs create RAID volumes from SATA disks, they aren't formatted but Windows formats them during the installation. Given the capabilities of UEFI firmware beyond BIOS firmware, that has 64bit addressing, and UEFI firmware's add ons or extensions features, that might be possible.
Here's part of the trick and problem with a RAM disk for an OS; a RAM disk is part of the Windows NTFS file system, correct? It has a drive letter, we can create folders and store files on it just like a HDD or SSD. But is the RAM disk part of the SATA interface?
No, it's not
part of the SATA interface, and does not use the SATA controller or its driver, such as IRST. The RAM disk software on my ASRock board creates an entry in Storage Controllers in Device Manager, and uses its own driver. So to create a RAM disk outside of an OS, its driver would need to be executed before it could be created. A Windows installation allows us to load drivers, but after the target drive is selected. But it seems like this could be done... somehow.
There are large RAM disk devices that exist for enterprise use, are they used for an OS? I don't know, but it seems in order to create a RAM disk before an OS exists, access to a board's firmware (UEFI) is necessary, and perhaps support from the OS installation process.