Re: Results popup missing when using Desktop Search

Tech-Archive recommends: Speed Up your PC by fixing your registry

Shawn, I already have that "Search As I Type" box checked.

FWIW if I type a search into the entry box in the larhe Desktop
Search Window then it too does not search as I type. I don't know if
the "Search As I Type" setting is supposed to work with this text-
entry box too. Is it supposed to?

To sort this out, I uninstalled WDS and then did a reinstall. This
second time without installing Windows Desktop Live.

But it is just the same.

What WDS programs should get run at boot time (assuming you want WDS
to be running)?

Thank you - Andy.



On 26 Aug, s keene <ShawnKeene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Actually it's not a Windows Live issue.

- Open the full search results window for "Windows Desktop Search."
- On the right end of the blue bar, there's a icon that looks like
a folder icon with a down arrow, click that, then go to Desktop
Search Options.
- Go to the "Deskbar" options on the left, and make sure it's set
to "search as I type"

If that doesn't do the trick, let me know.

- skeene



"Kelly" wrote:

Andy

This has to do with Windows Live:
http://www.google.com/search?l=en&q=Windows+Desktop+Search+toolbar
+&btnG=Google+Search --

Kelly (MS-MVP/DTS&XP)




"Andy" <nomail@xxxxxxxxxx> wrote

I used to get a nice popup window when I entered a search
into the Windows Desktop Search toolbar (the one which is
in the taskbar).

I don't get that any more. Can't find an option to
re-enable it.

I used to select "MORE ..." in this popup and get the
complete Desktop Search window (looks like Windows Explorer).

----

Now if I enter a search in the toolbar, I immediately get
the complete desktop Search Window.

What do I do to get the popup back?

.

Relevant Pages

  • Re: Executable enty points incorrectly documented
    ... All these things are correct but this is more specific and related to the .NET Framework than to Windows API and the C++ linker and does not mention the actual entry point signatures either. ... The documentation problem to which you allude is that it is the CRT entry point that calls one of the versions of main / WinMain that is defined in your program. ... This is the signature of the managed entry point that has nothing to do with native executables/DLLs. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Event ID 26
    ... Every time I log off or shut down Windows, a message box pops up briefly ... Application popup: dwwin.exe - DLL Initialization Failed: The application ... System Log entry, but that's stopped happening. ... Help and Support only offers the suggestion to reinstall the application, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Executable enty points incorrectly documented
    ... You wrote that WinMain is not a starting function in CRT, but an user-defined entry point for a Windows application. ... I believe that the fact that this function is called by the C/C++ runtime clearly backs my opinion that WinMain has nothing to do with the operating system. ... Even if WinMain documentation remains in Windows SDK it would be wise to explicitly state that support for this entry point is provided by the C/C++ runtime rather than Windows itself. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Executable enty points incorrectly documented
    ... I was speaking about Windows SDK not MSDN Library entirely, but even if Windows SDK conatins C/C++ documentation I believe that main/WinMain belong to C/C++ documentation rather than Windows API documentation. ... It's correct about the default entry point names used by the linker and also correct about what those entry points call and because this is the ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Executable enty points incorrectly documented
    ... The function signature is there though ... belong to C/C++ documentation rather than Windows API documentation. ... As for the entry point signature: ...
    (microsoft.public.win32.programmer.kernel)