Writable Windows folder

Forgive the noob question - I'm still finding my way with WinBuilder...

When I first created my project using Win7PESE, the \Windows folder appeared in the RAM drive (B-drive), and I could install apps within the PE environment. Something has changed, and I cannot figure out what... but now the Windows folder is on X-drive (named 'Boot'), which is not writable.

Note: There's very good reasons for needing to install apps after the PE environment has fully loaded, rather than scripting them to install during the build process. This is mainly to do with setting unique install parameters each time a system is booted.

I have all the logging options turned on, so can provide logs if necessary - but I'm hoping this is just a tick-box somewhere that I've missed! How can I get a writable \Windows folder?!
Thanks

Check under "Main Configuration" that you have set "build model" to "In RAM (boot.wim)"

Thanks for the quick reply, JFX. However I must be missing something obvious. I am (and have always been) using the "In RAM (boot.wim)" option, but still I get a \Windows in an x-drive named "Boot". If I completely nuke my WinBuilder folder, and start again with a clean install, the first build always works fine (\Windows in a RAM-drive). Subsequent builds fail - even if I use the "Clean Temporary Files" option under "Main Configuration".

I've put log files up at the link below:
log_20130528_131100_Win7PESE_Support.7z
log.html

Any suggestions gratefully received. Tks.

I notice a warning from the log file: Reference to undefined variable: [%CurrentVersionVar.7600%Ultimateen-US]

First question is: should I worry about warnings* - and do I need to fix this? Second question is: Since the following line in the log is trying to evaluate whether the current version is "Enterprise", should I be concerned that I am using Win7 Ultimate as my source? I need to use Ultimate or Enterprise, as I require Bitlocker support, but the install.wim file from the source DVD only contains indexes for "Starter", "Home Basic", "Home Premium", "Professional" or "Ultimate". No "Enterprise" sources :/

*There are other undefined variables in the error log, including %ProgramExe" from the MSI Installer script, and 1 or 2 others.

First question is: should I worry about warnings*

Yes, assuming you are using default builder settings ( see you play with log settings, which means not default !!!)

and do I need to fix this?

No, you should report with a log file (if builder have default settings)

*There are other undefined variables in the error log, including %ProgramExe" from the MSI Installer script, and 1 or 2 others.

after such tidy report they would be fixed in time

Second question is: Since the following line in the log is trying to evaluate whether the current version is "Enterprise", should I be concerned that I am using Win7 Ultimate as my source? I need to use Ultimate or Enterprise, as I require Bitlocker support, but the install.wim file from the source DVD only contains indexes for "Starter", "Home Basic", "Home Premium", "Professional" or "Ultimate". No "Enterprise" sources :/

Do not use modified sources, there are links provided on main screen of Win7PE SE that gives you standart sources..

If edition you have contains BitDefender, BitDefender plugin will work, else it will not work but only give a warning on log saying
"BitLocker was not found in the current source"

**
Back to subject,
Win7PE SE as default always have X:\Windows and writable X: since the begining of project,
  in realiy IF what you wrote (Ram-Drive\Windows) happens without your interaction (as far as I know there is no such setting inside project), that is the trouble,
    well since you are the only one who reports "X:\Windows - not writable" 
      maybe you play too much with settings or custom additions....  or whatever ??? let us know after you figure out 

Thanks for your suggestions Lancelot. The source is a genuine MSDN DVD, and I really haven't been messing with settings that much. I even did a couple of rebuilds of the whole WinBuilder install and sources.

What I have been doing however, is dropping large files in the 'Additional Files' section. Large enough that they filled the RAM drive. In fact the error actually stated 'insufficient space', but I've seen the same when using a hardware forensic write-blocker on a drive... so I just assumed... And we all know that assumption is the mother of all f*"k-ups.

So, FBWF cache increased to 512mb, and all is now working normally.

My face is in my palm, while I eat humble-pie.
-
c

Total available ram always forgotten, especially when Additional Files used since log small ;)
As a result, .wim fits ram but no more available ram to run .....
or in some cases, with additional things 256 MB fbwf become not enough at boot....

Maybe Chris may implement an optional (but also default) fbwf setting

Additional Tip:
Win7PESE\Tweaks\"Imdisk Ramdisk" (or any ram disk) can help using ram beyond fbwf limitations etc. especially for %temp% usages leaving system writable area (fbwf) alone...





@Chris

As you know Gena\Finals\2 Create Image\"Create ISO" -> have RamStatus.exe that can also be used checking available free ram at boot up,
if it is under a limit, than give warning...

Since it runs with batch, I feel it will work on minimal conditions where au3 not work but .wim boots (to a level)....

idea is adding a checkbox at
\Win7PESE\Build\"2 - Shell & Config"
saying "RamCheck at boot" which runs a batch, and if smaller than blabla size cmd screen stays on screen giving info..
( increase fbwf or increase ram ... etc.)
hence experienced (advanced) users knowing this fbwf-ram things can disable checkbox if they like....