imagex append -VS- another WIM altogether

[iamtheky]

C and D drive.

Currently i imagex capture the C and imagex append the D. Then split it into swms burn to disc and deploy. works nicely.

In the efforts of saving space I was attempting to capture c: (which is still split due to size) and d: into independent WIMs and then deploy, this results in a 0xc00000e, which bcdboot will fix.

Can anyone explain the difference between:

imagex /ref C:\zWIM\*.swm /apply C:\zWIM\Win7x86.swm 1 C:

imagex /ref C:\zWIM\*.swm /apply C:\zWIM\Win7x86.swm 2 D:

VS

imagex /ref C:\zWIM\*.swm /apply C:\zWIM\Win7x86.swm 1 C:

*Then delete the c:\zWim folder recursively, and copy the D drive Wim to that staging location and run

imagex /apply C:\zWIM\Win7x86.wim 1 D:

[allen2]

Did you tried doing the partitions layout first with diskpart then applying the D: image first then applying the C: drive ?

[iamtheky]

thats exactly what i tried (directly after c: first did not work), fantastic guess sir!

Edited June 16, 2011 by iamtheky