BUG: Text in Files with "unknown" extensions Associated with Wordpad do not search. Article 309173 is invalid.

[Guest contributor]

BUG: Text in Files with "unknown" extensions Associated with Wordpad do not search. Article 309173 is invalid.

 

I have found that if you associate a file with Wordpad, the text within a

file search option doesn't work.

 

It is necessary to associate them with Notepad for them to be searchable via

the text within them, even if they are merely text files.

 

I've followed the instructions explicitly in the Article

http://support.microsoft.com/default.aspx?scid=kb;en-us;309173 and it

doesn't work.

[Guest Vera Noest [MVP]]

Re: BUG: Text in Files with "unknown" extensions Associated with Wordpad do not search. Article 309173 is invalid.

 

Re: BUG: Text in Files with "unknown" extensions Associated with Wordpad do not search. Article 309173 is invalid.

 

This newsgroup is about Terminal Services issues.

 

The best way to make your comments known is to use the "Feedback"

form on the KB article itself.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"contributor" <DONOTSPAM@msn.com> wrote on 25 jul 2007 in

microsoft.public.windows.terminal_services:

> I have found that if you associate a file with Wordpad, the text

> within a file search option doesn't work.

>

> It is necessary to associate them with Notepad for them to be

> searchable via the text within them, even if they are merely

> text files.

>

> I've followed the instructions explicitly in the Article

> http://support.microsoft.com/default.aspx?scid=kb;en-us;309173

> and it doesn't work.

[Guest contributor]

Re: BUG: Text in Files with "unknown" extensions Associated with Wordpad do not search. Article 309173 is invalid.

 

Re: BUG: Text in Files with "unknown" extensions Associated with Wordpad do not search. Article 309173 is invalid.

 

1.) MS doesn't read those.

2.) This is an application/usage issue that likely would only affect people

who use Server as a Workstation, as in the case of Terminal Services users.