vbp 5.7 : visual build pro action spawns child with missing system macros?

[epu]

sometimes, even though I write out all the macros correctly (inspection of macros in notepad shows XDK, XEDK are there), when loading the macros they load truncated.

If I stuff this
<code>
<step action='Run Script' type='1'>
<Language>VBScript</Language>
<Script><![CDATA[Application.Macros(vbldMacroAll).Save "%PROJDIR%\" & vbld_FormatDateTime() & ".%PROJROOT%.ALL.macros"
Application.Macros(vbldMacroSystem).Save "%PROJDIR%\" & vbld_FormatDateTime() & ".%PROJROOT%.SYSTEM.macros"
Application.Macros(vbldMacroGlobal).Save "%PROJDIR%\" & vbld_FormatDateTime() & ".%PROJROOT%.GLOBAL.macros"]]></Script>
<description>for debug / troubleshooting</description>
<indent type='3'>1</indent>
<name>export all macros</name>
</step>
</code>
just before I call the chained project, and then into the failure step of the chained project, I can inspect and see that they don't match. I'll try to load them in the chained sample and reproduce.

The SYSTEM macros versions obviously differ in the failed step macros of the chained proj.

the chained project has no TEMP or TMP macro, but the parent proj has them as
<code>
<macro>
<name>TEMP</name>
<description>Environment variable</description>
<value>C:\DOCUME~1\Z-AXIS~1\LOCALS~1\Temp</value>
</macro>
<macro>
<name>TMP</name>
<description>Environment variable</description>
<value>C:\DOCUME~1\Z-AXIS~1\LOCALS~1\Temp</value>
</macro>
</code>

there's some additional missing vars. I'll attach the system macros for your perusal. maybe they can help?