how to update new image

  • Thread starter Thread starter KM
  • Start date Start date
K

KM

If you create a new image, you have to deploy it again (unless you want to do hell of work updating components at run time).
Just delete the CF content you got (don't reformat or etc.) and copy the new build. Then run through FBA.

If you plan to have a few image build iterations, this may not be a good idea to run through FBA on CF. You may want to do deploy
on HDD first and then copy post FBA image to CF.

I guess that was what you asked in earlier thread and got replies there.
 
Since the FBA process is slow anyway, I wouldn't consider the time you spent FBA'ing your image on the target device as a critical
factor.

However, FBA process does a lot of writes to the storage media. You don't want that on CF, otherwise you wear it out pretty fast.
 
Hello all,

I copy image to CF and after run FBA, my CF can run XPE normally, but
I need add more components to it, so I make a new image.

My question is, how can I update it to CF, do I have to redo FBA again or
there are some other shortcuts???

Thank you very much!
 
Thanks a lot for the help.

Why it's better deploy to HDD first, not CF, faster?


KM said:
If you create a new image, you have to deploy it again (unless you want to
Click to expand...
do hell of work updating components at run time).
Just delete the CF content you got (don't reformat or etc.) and copy the
Click to expand...
new build. Then run through FBA.
If you plan to have a few image build iterations, this may not be a good
Click to expand...
idea to run through FBA on CF. You may want to do deploy
 
FBA to a CF first and make sure the EWF works.
Then test new versions on HDD if you wish.
Later when HDD is working FBA on a CF and prep for cloning.
WRITE DOWN EVERYTHING YOU DO AFTER FBA and update it every time you change
something.
I also suggest you back up your slx file and keep saving it as a differnt
name so you have copes (unless you already are checking it in and out of
sourc safe.
I also cut and past out the TD build list which lists all the components and
I keep a hard copy.
This helped when I moved TD to another computer and wanted to make sure I
had all the QFEs loaded.

KM said:
Since the FBA process is slow anyway, I wouldn't consider the time you
Click to expand...
spent FBA'ing your image on the target device as a critical
factor.

However, FBA process does a lot of writes to the storage media. You don't
Click to expand...
want that on CF, otherwise you wear it out pretty fast.
 
Thank you all very much for the help!

David Ditch said:
FBA to a CF first and make sure the EWF works.
Then test new versions on HDD if you wish.
Later when HDD is working FBA on a CF and prep for cloning.
WRITE DOWN EVERYTHING YOU DO AFTER FBA and update it every time you change
something.
I also suggest you back up your slx file and keep saving it as a differnt
name so you have copes (unless you already are checking it in and out of
sourc safe.
I also cut and past out the TD build list which lists all the components and
I keep a hard copy.
This helped when I moved TD to another computer and wanted to make sure I
had all the QFEs loaded.


spent FBA'ing your image on the target device as a critical don't
want that on CF, otherwise you wear it out pretty fast.
Click to expand...
 
Back
Top