IMDisk+Wimboot RAM Limitations.

i have a few questions about using IMDisk and wimboot on a pc with low ram...
here is the scenerio.

i have my IMDisk script set to use 50% of RAM (default)
i am also using wimboot to load my "I386" and "Program Files" Folder into my ramdrive - Boot (X:)
my I386 Folder is 144MB and my Program Files Folder is 90MB.
so i am loading exactly 234MB of data into my RAM.

here are my questions about the above scenerio.
1. would i be able to boot successfully if i was on a computer with 256MB RAM?

i ask this becuase of my IMDisk.script. it is set to use 50% of RAM. meaning, it needs 128MB in this scenerio....but i do not have 128MB to spare. (becuase my Program files and I386 Folder is using 234MB out of my available 256MB RAM)

2. What would happen if i tried to load my livexp CD on a pc with 128MB of RAM?

so, with the setup i have now, am i "handcuffing" myself to computers that have 512MB+?
meaning, if i try to run my livexp CD on a computer with anything below 512MB RAM - it would fail, right?

if i need to lower my IMDisk Space - what would be a safe % or size to set it at?

EDIT: Also, i had a question about how ImDisk works.
Does it take (by default) 50% of AVAILABLE FREE RAM or does it take 50% of Total RAM, no matter how much data has been loaded into ram already?

And just one more thought, how small can i get my I386 Folder? i have widdled my livexp build down to as minimal as i can. When my BootSDI.WIM is extracted to RAM - my I386 folder is 147MB. i would LOVE to make this smaller....is there an easy way of doing this? i would like to have my I386 folder at around 100MB

Hi dsolomon,

Simply, with 256MB or less RAM, stick with Create ISO builds

You're using a very large LiveXP which limits your options (and performance). Consider using a lighter build for these low RAM situations and keep the 'big dawg' on hand for when you really need it. I think you'll find the lighter build fits most of your needs.

--
EDIT: 50% of available RAM (not total). 147MB isn't bad; I have some 076 builds (later wb = bigger builds) with 75MB i386 (compressed), that still expands to 130MB in RAM. Difficult to trim more than this and still have things work the way you want.

Hi dsolomon,

Simply, with 256MB or less RAM, stick with Create ISO builds

You're using a very large LiveXP which limits your options (and performance). Consider using a lighter build for these low RAM situations and keep the 'big dawg' on hand for when you really need it. I think you'll find the lighter build fits most of your needs.

--
EDIT: 50% of available RAM (not total). 147MB isn't bad; I have some 076 builds (later wb = bigger builds) with 75MB i386 (compressed), that still expands to 130MB in RAM. Difficult to trim more than this and still have things work the way you want.

ok great to know!
so lets say i load 256MB of Data into my Ram. and i have a TOTAL of 512MB RAM.
my IMDisk will use 128MB. right?

Also, im going to try "Create ISO" option instead of Wimboot, like you suggested.
i am using Driver Import PE in my build. and it requires FBWF when i use Create ISO.
do i need IMDisk AND FBWF?
also, FBWF asks me for a percentage of RAM to use.

Wrong, you need to allow for OS usage which can be substantial; depending on your setup, maybe around 150MB. So in this scenario you might only end up with 50Mb or so left for IMDisk drive. Create ISO will use far less RAM but still allow for OS usage; you don't need IMDisk, just nice to have extra writable (temp) drive for use in PE. FBWF is similar to IMDisk in that it allocates a certain percentage of available RAM to be used as writable in PE. Remember, Create ISO build will run much more sluggish because it's running from CD instead of from RAM and you can't remove the CD as you can if completely run from RAM.

EDIT: Also, i had a question about how ImDisk works.
Does it take (by default) 50% of AVAILABLE FREE RAM or does it take 50% of Total RAM, no matter how much data has been loaded into ram already?

It makes the calculation based on available free ram.

But depending upon the amount of ram in the system, it may not actually generate a ramdrive that is 50% the size of available free ram. That's because the batch file is fed a parameter for what should be reserved for the system. By default that value is 64mb.

Hope this helps.

Regards,
Galapo.