LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Building application with microsoft agent

Can someone clarify if there is anything different that needs to be done while building a stand-alone application that includes VIs that use the MS agent voice VIs (for example MSagentTTS.llb) along with CGI VIs? I have been able to build applications with only CGI VIs but failed while adding MS agent VI functionality. Any help is greatly appreciated.

-Sheela
0 Kudos
Message 1 of 4
(3,198 Views)
"Belur" wrote in message
news:50650000000800000017690000-1031838699000@exchange.ni.com...
> Can someone clarify if there is anything different that needs to be
> done while building a stand-alone application that includes VIs that
> use the MS agent voice VIs (for example MSagentTTS.llb) along with CGI
> VIs? I have been able to build applications with only CGI VIs but
> failed while adding MS agent VI functionality. Any help is greatly
> appreciated.
>

You'll need to install the Microsoft Agent parts on the target computer.
They are:

MSAgent.exe - the core components
actcnc.exe - MS Speech Recognition Engine
tv_enua.exe - MS Text To Speech engine
Merlin.exe - or any of the available different voices

Theses are available for downl
oad from
http://www.microsoft.com/msagent/downloads.htm
0 Kudos
Message 2 of 4
(3,198 Views)
Thanks for your response. But I am just testing it on on my development system itself, without launching LabVIEW, on which these parts are already there and the VI itself works but not the stand-alone application built using the application builder.
0 Kudos
Message 3 of 4
(3,198 Views)
"Belur" wrote in message
news:506500000005000000E2B80000-1031838699000@exchange.ni.com...
> Thanks for your response. But I am just testing it on on my
> development system itself, without launching LabVIEW, on which these
> parts are already there and the VI itself works but not the
> stand-alone application built using the application builder.

You may have a "strip path" problem in your EXE and LV Agent is not finding
the path to the .acs file where the Character is loaded. Install a path
indicator in your EXE on the front panel and see if your built app is
finding the correct path to ..\LV61.acs (or what ever Character you are
using)
0 Kudos
Message 4 of 4
(3,198 Views)