"Small" FBA on new CF

Tech-Archive recommends: Fix windows errors by optimizing your registry

Dear all,

I've a general question on what is going on.
1.) What we do:
- Generate an Image with TD, copying it to a CF, running FBA on Reference
Hardware (making some post FBA changes).
- Copy the Image to a new (& different CF)
- Inserting it to the final device.

2.) What was happening up to know when we insert the second CF into the
final device:
- Windows detected that something changed and makes some kind of "small" FBA
where the EWF is not active.
(this boot lasts a little bit longer then the normal one)
- It asks the User to shutdown the system as new hardware was found. As FBA
is not running, changes are committed.
- On Reboot, EWF is up and running and the System is ready to use.
(from now on boot time is normal)

Unfortunately I now made a slightly different image with some changes and
after I plugg in the CF to the final
device this first boot lasts significantly longer (+80%) and afterwards
changes are committed but
still the normal boot requires a lot of time.
I must commit mannually a second time to get a normal running image.

Now three questions:

- What could be the reason for this behaviour ?
- Where could I look why XP needs so long before committed a second time ?
(setupapi.log shows nothing new, ntbtlog.txt doesn't help me)
- Is there a resource on how this procedure of image cloning is described to
follow the "official" manner ?


Many thanks in advance, Wolfgang



.

Relevant Pages

  • Re: FBA Generic command and EWF problem
    ... I remember that discussion thread where you were struggling with a script launch at FBA. ... Can you give us more details on what and how is failing to commit the EWF overlay? ...
    (microsoft.public.windowsxp.embedded)
  • Re: problem with system cloning tool
    ... "This property specifies at which FBA phase the reseal operation occurs. ... only the cloning tools will be copied to the run-time image and the ... >I think that fbreseal.exe is deleted only the second time ... >> starting during FIRST FBA start and delete fbreseal command from system. ...
    (microsoft.public.windowsxp.embedded)
  • Re: RAM EWF and boot failure
    ... > we were unfortunatlely running FBA on the CF which is a bad idea). ... >> I did a commit and rebooted. ...
    (microsoft.public.windowsxp.embedded)
  • Re: OWA in 2007
    ... I would try is to turn off Forms-based Authentication for the problem server ... That way you will at least know that if you can't get FBA working, ... the page does not even arrive at the log on session therefore ... the page a second time because you previously typed in the wrong ...
    (microsoft.public.exchange.connectivity)