FBA phase 12000+

[Guest]

I have a component (configured to reseal-phase 12500) that I don't want
instantiated before the XPe image is moved to the clone machine, but the XPe
image i going through all the FBA phases on the master machine before it is
cloned and before I have executed FBreseal.exe.

I have set the System Cloning Tool components cmiResealPhase to 0 in Target
Designer.

Have I misunderstod how it should work?

If I set the cmiResealPhase to 12000 the XPe image is automatically resealed
and and my custom component is instantiated at phase 12500 as it is supposed
to, but I need to do some installation before the XPe image is resealed!

I would apreciate any help very much.

Thanks,
Lasse K. Christensen

 

[KM]

Lasse,

IIRC (but you better search Google archive), there is a known issue that if you set to manual reseal (cmiResealPhase=0), all the
commands with FBA phase >= 12000 will be executed before the Cloning phase.

I think you better off automating all the manual operations (theoretically, there is nothing you cannot automate) and have them run
before the Reseal phase. And you can have the default cmiResealPhase=12000. Then you can still have some commands with later phases.

 

[Guest]

Thanks KM, then it's not me that are crazy...

Lasse,

IIRC (but you better search Google archive), there is a known issue that if you set to manual reseal (cmiResealPhase=0), all the
commands with FBA phase >= 12000 will be executed before the Cloning phase.

I think you better off automating all the manual operations (theoretically, there is nothing you cannot automate) and have them run
before the Reseal phase. And you can have the default cmiResealPhase=12000. Then you can still have some commands with later phases.

 

[Guest]

KM,

Do you know if this is still an issue with current SP2 build of XP Embedded?
I am observing this exact behavior. I have tried setting the phase of my
FBA Generic command to 65000, 12001, and 12000 (all with cmiResealPhase=0),
and in ALL cases, the command executes ONLY after first boot, but NEVER after
manually resealing the image with "fbreseal.exe".

If this mechanism is broken, can you recommend a workaround? Not having
this capability is very problematic for what I am doing.

Thanks,

Brian

 

[KM]

Brian,

I didn't have enough time to test the issue on SP2 and dig out details.
Although, I haven't heard of any fix in this or related areas of FBA.

The workaround is probably still the same: automate everything you need to do manually after reseal and run it during FBA.
This way you don't have to set cmiResealPhase=0.

Another experiment you may want to try is to add "fba.exe" launch code to BootExecute
([HKLM\SYSTEM\CurrentControlSet\Control\Session Manager]) manually after you ran fbreseal.
You can see how the fba.exe needs to be called from BootExecute if you explore the system registry hive of pre-FBA image.