Hello Wonko !
Thanks for the links.
[...] I don't understand the idea of the bootable disk image, you want to boot to *something* (let's say grub4dos), then dd copy the image (residing on some mass storage device) to this unmanaged RAM area and then boot from it?
Then most probably you want to try grub4dos+Firadisk
Well... for the last 10 years I've been systematically running heavily modded and slimmed down versions of Windows XP in ramdisk mode on ALL my machines, using ramdisk.sys or Grub4DOS and WinVblock.
I frequently use modified versions of the IMG_XP package to set up my machines, and I love multitasking and pushing my machines to their limits.
Sometimes I run a web browser with 20+ tabs open, while encoding video and batch downloading YouTube videos and executing other resource intensive tasks, most of the time without using a pagefile, so I need all the available RAM I can get !
Ramdisks are the best thing since the invention of sliced bread !
I can't live without them, but unfortunately they gobble up precious RAM, and XP can theoretically only see and manage 4 GB of RAM, so just adding an extra 4 or 8 GB of RAM to the motherboard will do nothing to solve this problem when one is using "standard" ramdisk drivers like WinVblock or ramdisk.sys.
On my daily driver the C drive running in the managed RAM gobbles up 700 MB (XP, + drivers + Sandboxie's sandbox folder (containing a web browser, email client and other internet facing applications).
I want my system drive and sandbox to be running in RAM for performance and security reasons (every reboot a nice clean slate; "autowipe" cookies, browser cache, and potential malware files, and in the worse case scenario getting rid of malicious system modifications in case something evil manages to escape the sandbox prison)
It would be nice to push this bootable image in the unmanaged RAM using a different ramdisk driver, so I can recuperate the 700 MB, and make it available to applications.
Currently I've got 4 GB of RAM installed, and XP can only see 3.2 GB of that (in filedisk mode).
Hopefully it's possible to stick the bootable image in the section of RAM that XP can't see, or alternatively I could add another RAM module to my motherboard.
It is <the current year> and nowadays motherboards support way more than just 4 GB, so it makes sense to try to use the capabilities the hardware to the fullest extent in order to improve the user eXPerience of good ol' 5.1.
Hopefully there are easy and simple point-and-click methods to accomplish this, but if I have to I am willing to spend countless sleepless nights messing around hex editing binaries, or editing .inf, and .reg files...
Edited by NT Five, 23 April 2019 - 05:34 PM.