You use its COM interface eg paste these 2 lines into notepad, save with a
..vbs extension, turn on your speakers, and click on it

Set spVoice = CreateObject("SAPI.spvoice")
spVoice.Speak("New process spotted CAAntiSpyware")


You can do something similar in your app.

--
Jon


"AlexB" <alexb@comcast.net> wrote in message
news:eoEEH2ZeIHA.5208@TK2MSFTNGP02.phx.gbl...
> If there is no API I will have to do all the programming from scratch. It
> will be a long way. This dll has not valid CLR header and therefore cannot
> be disassembled. Neither Ildasm.exe nor Lutz Disassembler gave me
> anything.
>
> This dll is rather small. it has only 4 functions. They are all generic.
> They do not seem to have anything to do with speech by the sound of them.
> I mean, they certainly do, otherwise they won't be there but they are not
> something you can call at first call.
>
> The Dependency Walker opened it up. It does not care about CLR headers.
>
> It is all of course sort of irrelevant for this NG. But I hoped somebody
> could have had direct experience with speech recognition and shed some
> light on what interests me.
>
> Thanks a lot for the pointer.
>
> "Jon" <Email_Address@SomewhereOrOther.com> wrote in message
> news:e0oNQHYeIHA.4852@TK2MSFTNGP05.phx.gbl...
>> Try
>>
>> %SystemRoot%\System32\Speech\Common\sapi.dll
>>
>> --
>> Jon
>>
>>
>> "alexB" <alexb@comcast.net> wrote in message
>> news:e61uWBXeIHA.3756@TK2MSFTNGP06.phx.gbl...
>>>I want to use TextToSpeech feature in my app. It is just a very raw idea.
>>>I am not sure if it is going to work for me the way I want to use it.
>>>
>>> Number one, I need an API for it, not UI. I need an exec. I will be able
>>> to find it on my own (if one exists) but I will appreciate if someone in
>>> the know will offer a helpful hand.
>>>
>>> Again, for me to use it I need an API, an executable file somewhere in
>>> Windows\System32 directory or elsewhere.
>>>
>>> The second question is much more important. I do not want this API to
>>> read simple texts. What I have in mind is the following. I've had a part
>>> of one of my applications monitoring Systems.Processes. Any executable
>>> running in the background is caught and its name is put in an Sql table.
>>> When this executable appears for the first time the date is recorded and
>>> placed in a separate field. Daily updates of this table are made.
>>>
>>> So far I have been examining this table only occasionally but I am
>>> planning to pay more attention to it. Also I want to write a piece of
>>> code which will catch the first appearance of a new guy and give me an
>>> audible message. I can make a generic message with SoundRecorder.exe but
>>> it would be fanciful to go one step further. I want this file name to be
>>> pronounced. An example: "A new exec has appeared. 'Its name is
>>> CAAntiSpyware."
>>> So, my question is (for a person with any experience): will it be able
>>> to handle gibberish like this? Some cases may be even worse.
>>>
>>> This is a somewhat primitive design but eventually I will monitor all
>>> sockets and do the same in terms of storing the names of who uses them
>>> and why. Over there analysis is more complicated and I want to have more
>>> control over the monitoring with audible messages.
>>>
>>>
>>> BTW, CAAntiSpyware.exe guy gives me creeps. I refused to renew their
>>> subscription when I switched to Vista. For those who followed I've
>>> explained my decision since I felt that Vista plus SB S&D offer
>>> sufficient protection. Somehow this guy ended up in my system anyway. On
>>> top of that it is not listed among programs what I can uninstall. I
>>> remember vaguely that a popup showed up saying that I was delinquent on
>>> their wonderful subscription and if I wanted to renew it. I clicked NO.
>>> Apparently CA knew in advance what to expect since their sales perhaps
>>> have gone down. They left no option for their cra*p to be rejected. Now
>>> I will have to deal with this scam. Spybot S&D did not recognize it as
>>> malware and MS Malicious Software Removal Tool seemed to have ignored it
>>> too.
>>>
>>>
>>> Thanks.
>>>
>>>
>>
>