Is it possible to run FBA registry commands after first boot

[Guest]

I am trying to upgrade a run-time image with a few components that have FBA
registry entries. I would like to run these commands on top of a
pre-existing image, to save some time and effort. Is there a document that
explains all the possible FBA entries and how to convert it into a format
that can be run as a script at runtime? Is this even feasible? I've looked
through MSDN, but none of the resources seem to have an in depth coverage of
this topic. Preferably, I would like to perform this task such that I can
choose some components and store their corresponding files, run the normal
registry settings using regsvr32 and finally run the FBA commands using a
script of some sort. Thanks in advance for any help.

 

[KM]

Himanshu,

What do you call by "FBA registry settings"? What's special about the FBA?

Assuming your components dependencies are already in the image (you will have to make sure this is true).
You can:
- create a new empty SLX project
- include the new components that you will need to deploy in the project
- run build
- open the new image's registry hives offline and capture all the entries appeared (you can export .reg and then replace the
root key name)
- then you will just need to use regedit to install the .reg on your existing and already deployed image
- add all the component files to the proper directories

If you deal with software components that are not huge, the above instructions should work.
For the hardware PnP components, just copy the files to appropriate directories and PnP Manager will do the job.

Most of the FBA Resources are easy to translate to a script using regedit, regsvr32, etc..

 

[Guest]

Hi KM,
I had exported the components associated registry entries after build in
target designer, but before first boot. Looking at these registry entries, I
noticed that there were keys in
[hkey_local_machine\system\controlset001\control\windowsembedded\fba\.].
Most of the these were registering dlls, which I can use regsvr32, but some
were COM registration and service registration, which I'm not too sure about.
Your suggestion seems like the right way to go, so I'll try and see how that
works for me.
Thanks,
Himanshu

 

[KM]

Himanshu,

Well.. Personally I prefer creating proper registering commands rather than grabbing the result registry.

But in your case, since you are going to grab the pre-FBA registry, you will need to translate FBA commands (the key you saw) to a
script to run on your image.
For the COM registration you can use the same regsvr32.
Service registration is sometimes done through the registry directly or some service implementations have the self-registration code
(usually command line switches like "/i").

--
Regards,
KM, BSquare Corp.

Hi KM,
I had exported the components associated registry entries after build in
target designer, but before first boot. Looking at these registry entries, I
noticed that there were keys in
[hkey_local_machine\system\controlset001\control\windowsembedded\fba\.].
Most of the these were registering dlls, which I can use regsvr32, but some
were COM registration and service registration, which I'm not too sure about.
Your suggestion seems like the right way to go, so I'll try and see how that
works for me.
Thanks,
Himanshu

Himanshu,

What do you call by "FBA registry settings"? What's special about the FBA?

Assuming your components dependencies are already in the image (you will have to make sure this is true).
You can:
- create a new empty SLX project
- include the new components that you will need to deploy in the project
- run build
- open the new image's registry hives offline and capture all the entries appeared (you can export .reg and then replace the
root key name)
- then you will just need to use regedit to install the .reg on your existing and already deployed image
- add all the component files to the proper directories

If you deal with software components that are not huge, the above instructions should work.
For the hardware PnP components, just copy the files to appropriate directories and PnP Manager will do the job.

Most of the FBA Resources are easy to translate to a script using regedit, regsvr32, etc..