Hi, KM
(responses between paragraphs below)
KM said:
Leszek,
The first idea that comes to my mind - a dirty quick fix - change the value at run time (or at very late FBA phase) and reboot. This
should fix the problem.
Of course, I can do it (even many times) but I guess this problem
(overwriting registry entries) would occur in another components too, so it
would be worth to find out the source of problem. And so you try to do. Thank
you
Now lets find out the source of the problem.... A few things that you can do to debug the problem:
- Check your Configuration Extra Regsitry section if it changes the Start_ShowSearch.
Yes, I added there explicite setting this key. But I set it to 1.
Unfortunatly it doesn't help. :-(
- Verify that cmiShowSearch extended property of the "User Interface Core" component is set to True.
Yes, it is.
- Remove "User Interface Core" component, Turn off TD Autoresolve Dependency option, build the image and check the registry offline:
is the Start_ShowSearch value set?
Very interesting! After removing this component (and without the dependency
checking - did you suggest this way?) the registry value is 1. After adding
it again and setting the Show Search option everything goes wrong again. I
checked the image before the FBA phase.
- If you go to
www.xpefiles.com, you can find there (Development Utilities/Main folder) XPeTools package. It includes
DependencyExplorer component that will allow you to create and use a filter by a registry key and value name. If you search by
Start_ShowSearch, you can find your own custom component in XPe db that ay change the value.
I hoped it would be great tool. And probably it is, but another problem
occured. :-( When I chose the Registry Value Name, entered Start_ShowSearch
and clicked Apply after several minutes it finds no component. (User
Interface Core was included in the configuration but it wasn't listed too).
That was a few times. I tried also to choose Registry Key Path and to enter
the path but the error occured (I don't remember now, it was surely cmi error
or something.) What do I do wrong?
I checked the Save Filter to use in TD checkbox too. When I restarted the
Target Designer and choose the new filter, no components was found. Then I
tried to enter the Filter Manager and everything hanged. :-(
Regards,
Leszek.
--
Regards,
KM, BSquare Corp.
I checked it. It looks like 2 problems. First: in the image in the DEFAULT
hive before FBA there was value 0. I set the Start_ShowSearch entry to 1 in
the image (I exited regedit and run again to ensure it really changed), then
I copied it to the boot partition and rebooted. FBA completed, second boot
completed and the icon is still hidden! The initial value before was bad and
the final value after FBA was bad too! Have you any more idea?
Regards,
Leszek
KM said:
Leszek,
After you built the image, go and load the DEFAULT hive offline and check if the following registry value is set:
[HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced], "Start_ShowSearch"=dword:1
Also, double check this registry value at run time in the post FBA image. If it is not set there, or set to 0 - some component(s)
overwrites the value in your image during FBA.
--
Regards,
KM, BSquare Corp.
Thank you.
It helped me when I added the Search Assistant English Language Support.
And what about the first point? Why the Search icon is initially hidden? I
added the corresponding registry entry to the "Extra Registry Data" later but
it didn't help too.
Regards,
Leszek
:
Just to add to that.
If you have only #1 (Explorer) but do not include all other components from the list below, you will still have a search engine
in
place (Explorer includes it) but not the Search Companion Assistant.
--
Regards,
KM, BSquare Corp.
I also had trouble with Search Assistant for a long time.
I found I needed 4 components in all.
1. Explorer Shell (obviously)
2. Search Assistant User Interface (of course)
3. Search Assistant Characters (Yes, even if you don't plan to use the
critters)
4. Search Assistant English Language Support (Yes, even if not using MUI)
If you have all 4 of these, your item #2 should be resolved.
Andrew
I have 2 problems with the search menu item.
1. I enable the Search icon on the Start Menu by checking the "Show Search
on Start Menu" checkbox in the "User Interface Core" component in the
Target
Designer. It doesn't work - icon is not shown. It is with or withot the
standard menu component included.
2. If I turn the Search icon on manually in the target system and I click
it
I get the error message "A file that is required to run Search Companion
cannot be found. You may need to run setup."
How can I solve these problems? I use the Windows XPE Evaluation SP2.
