01-07-2016, 02:17 PM
(This post was last modified: 01-07-2016, 03:00 PM by madscientist565.)
I dont know how much capability you can really build into a bios or uefi... so i thought i would get the opinions from those that know more than I.
I think the best way to ask my question is to tell you what method i would like to use, and then you folks might can tell me what is , or is not possible.
machine: xeon 1650-3 workstation, 256gb ram, quadro gpu, 145gb operating system file size
step 1: create fully functioning workstation with all installed files, updates, antivirus, etc.
step 2: shut down pc (fully)
step 3: reboot machine
----------Bios will prompt a dual boot scenario
---------------- Boot 1) Standard windows 10 install
---------------- Boot 2) Ramdisk Version of install
Step 4: Select boot 2
------------Bios will then proceed to boot the pc.. it will recognize and initialize all components. Next (and before it loads the operating system,) the bios will allocate a ramdisk of 160GB. afterwards, the bios will execute a command to move the complete and full contents of the normal C: drive, to the ram disk.
------------Machine boots as normal into the ramdisk, that now functions just as if your normal drive does. the "normal drive" is isolated and is not usable, (actually its partitioned so part of it should be usable)
Use machine, save work on NAS, shut down when finished.. no reverse sync needed (yet)
ignoring the volatility. i WANT the volatility. when i shut down, it will not make any changes to the files on the normal drive. so any viruses, accidental changes to the file system, etc.. will be void. if i need to update or install new software I would use boot option 1, make my changes, and then move back to boot option 2.
Is this possible to do with the bios, or am I stuck using a hypervisor, or initial linux boot to accomplish this?
I have looked at PXE and winPE and they dont seem to be capable of doing this to the level of a entire windows 10 pc. they would be limited - in other words - in what they can actually do. While winPE booting to ramdisk is possible, and also breaks any handles associated with it, the method of installing programs, and making it functional its far more outside my relm of experience and in my opinion would be to much of a challenge. I am aware that several versions of linux use "initrd" and "initramfs" to run their entire os contents on ram (indistinguishably) and thats what i am trying to accomplish with windows 10.
any help in this is greatly appreciated.
I think the best way to ask my question is to tell you what method i would like to use, and then you folks might can tell me what is , or is not possible.
machine: xeon 1650-3 workstation, 256gb ram, quadro gpu, 145gb operating system file size
step 1: create fully functioning workstation with all installed files, updates, antivirus, etc.
step 2: shut down pc (fully)
step 3: reboot machine
----------Bios will prompt a dual boot scenario
---------------- Boot 1) Standard windows 10 install
---------------- Boot 2) Ramdisk Version of install
Step 4: Select boot 2
------------Bios will then proceed to boot the pc.. it will recognize and initialize all components. Next (and before it loads the operating system,) the bios will allocate a ramdisk of 160GB. afterwards, the bios will execute a command to move the complete and full contents of the normal C: drive, to the ram disk.
------------Machine boots as normal into the ramdisk, that now functions just as if your normal drive does. the "normal drive" is isolated and is not usable, (actually its partitioned so part of it should be usable)
Use machine, save work on NAS, shut down when finished.. no reverse sync needed (yet)
ignoring the volatility. i WANT the volatility. when i shut down, it will not make any changes to the files on the normal drive. so any viruses, accidental changes to the file system, etc.. will be void. if i need to update or install new software I would use boot option 1, make my changes, and then move back to boot option 2.
Is this possible to do with the bios, or am I stuck using a hypervisor, or initial linux boot to accomplish this?
I have looked at PXE and winPE and they dont seem to be capable of doing this to the level of a entire windows 10 pc. they would be limited - in other words - in what they can actually do. While winPE booting to ramdisk is possible, and also breaks any handles associated with it, the method of installing programs, and making it functional its far more outside my relm of experience and in my opinion would be to much of a challenge. I am aware that several versions of linux use "initrd" and "initramfs" to run their entire os contents on ram (indistinguishably) and thats what i am trying to accomplish with windows 10.
any help in this is greatly appreciated.