Overwriting default registry keys

  • Thread starter Thread starter Franz Leu
  • Start date Start date
F

Franz Leu

Hi group

I want to overwrite some default registry keys for i.e. doubleclickspeed,
power configuration setting .... at either CD level or as extra reg key in
TD.
What built order do I have to set for these to take effect?
Is there something else I need to take care?

Thank and best regards
Franz
 
Hi Franz Leu,
Use FBA Registry Migrate key, Any keys that are under this
key will be migrated into the registry during FBA
Set the registry key under the following path,
HKLM\System\FBA\RegMigrate
 
Nyquist,
Thanks for your hint.
However, I could not find any documentation on this topic.
Do you have a link ?
Franz
 
Franz,

RegMigrate is a nice but undocumented feature of FBA.
You can search this NG archive and find some hints about it.

There is also a recent blog from Microsoft product folks on the topic:
http://blogs.msdn.com/embedded/archive/2005/04/25/411763.aspx


Btw, another way for you to have the values set properly in TD is to either
find out what components hold particular reg.entries and set the build older
above those, or change the values in those components registry sections
directly.

KM
 
Hi KM,

Thanks for your help.
I tried to add it as extra registry data with a built order of 8501.
It's regarding the power policies and I added it to the HK_CU and the
HK_U\.DEFAULT
However, it does not take effect.
I tried to completely disable Display Powersave, since the setting "Always
On" in TD still includes a Display power save of 20min.
I alspo tried to preset the doubleclickspeed and some other setting the same
way, without success.
What am I doing wrong?

Thanks and best regards
Franz
 
Franz,

Did you try setting (changing) the values at runtime? Did it work?
The settings might get overwritten by some component install during FBA so you want to set them in late FBA phase.

KM
 
KM

I tried everything :-||. I just dont get what I am doing wrong.
I created a component which has only Registry Data. The string I add(!) to
the registry are OK. However, the strings I try to override some default
settings of windows like these:
HKEY_CURRENT_USER\Control Panel\PowerCfg\PowerPolicies\3
HKEY_USERS\.DEFAULT\Control Panel\PowerCfg\PowerPolicies\3
just dont take effect. They keep their original value.
Setting at runtime works perfect. I tried different setting for build order.
What value do you suggest?

(It makes me nuts)
Thanks for your help
Franz
 
Franz,
I tried everything :-||. I just dont get what I am doing wrong.
I created a component which has only Registry Data. The string I add(!) to the registry are OK. However, the strings I try to
override some default settings of windows like these:
HKEY_CURRENT_USER\Control Panel\PowerCfg\PowerPolicies\3
HKEY_USERS\.DEFAULT\Control Panel\PowerCfg\PowerPolicies\3
just dont take effect. They keep their original value.
Setting at runtime works perfect.
Click to expand...

That's the hope. It works at runtime, so you can automate it.
I tried different setting for build order.
Click to expand...

That won't help since the settings get overwritten at runtme during FBA by a system component.
What value do you suggest?
Click to expand...

You need to set the settings at runtime during FBA at very late FBA phase (>8500 or >12000). You can use FBA Generic command to
import a .reg file or use reg.exe utility.
Although I'd prefer a little bit different implementation if you happen to include Explorer shell. Just create a selfcleaning
(selfdeleting) batch file that will import .reg file or use reg.exe to import the values. Put the .bat file in All User\StartUp
items and that's it.

KM
 
Back
Top