Robert Well, that did the trick with a strange oddity. The .bat file has to be run twice both for Eloquence and TripleTalk PCI. The first time, the processes are killed; the 2nd time, speech is restarted.
Thanks! The Bible was not given to increase our knowledge but to change our lives. D.L. Moody On Fri, 30 Sep 2011, Robert C wrote: > Or enclose the path in quotes. > > Quote of the nanosecond... > There is nothing to learn from someone who already agrees with you. > Robert & Dreamer Doll ke7nwn > E-mail- > [email protected] > Home Page- > http://webpages.charter.net/dog_guide/ > > > ----- Original Message ----- From: "Stephen Clower" <[email protected]> > To: "Mike Pietruk" <[email protected]> > Cc: <[email protected]> > Sent: Friday, September 30, 2011 8:51 AM > Subject: Re: Relaunching WE7.51 .bat file > > > > Mike, > > > > The spaces in the folder path are likely causing the command to fail. You > > can use the %wineyes% system variable in loo of the direct path to get > > around the problem. > > > > Regards, > > Steve > > > > > > > > > > On 9/30/2011 10:38 AM, Mike Pietruk wrote: > > > Hi! > > > > > > For the first time, I am installing WE on a machine using the new folder > > > structure rather than the classic c\wineyes folder. > > > I have some batch files used to kill WE and relaunch it with various > > > synthesizers. > > > > > > I am trying to rewrite them so that they will work with WE7.51 under the > > > new file structure. > > > The first line in the following batch kills the processes as need; it is > > > the 2nd line where the problem occurs as WE isn't relaunched. > > > Can someone look at the following and see what's wrong. This example is > > > for Eloquence. > > > > > > pskill wineyes.exe > > > C:\Program Files\GW Micro\Window-Eyes\wineyes.exe /seloq > > > > > > > > > > > > > > > > > > > > > The Bible was not given to increase our knowledge but to change our lives. > > > D.L. Moody > > > > > > > > > If you reply to this message it will be delivered to the original sender > > > only. If your reply would benefit others on the list and your message is > > > related to GW Micro, then please consider sending your message to > > > [email protected] so the entire list will receive it. > > > > > > GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can > > > manage your list subscription at http://www.gwmicro.com/listserv. > > > > -- > > Stephen Clower > > Product support specialist & App Development > > GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825 > > 260-489-3671 * gwmicro.com > > If you reply to this message it will be delivered to the original sender > > only. If your reply would benefit others on the list and your message is > > related to GW Micro, then please consider sending your message to > > [email protected] so the entire list will receive it. > > > > GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can > > manage your list subscription at http://www.gwmicro.com/listserv. > > > If you reply to this message it will be delivered to the original sender only. > If your reply would benefit others on the list and your message is related to > GW Micro, then please consider sending your message to [email protected] so > the entire list will receive it. > > GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage > your list subscription at http://www.gwmicro.com/listserv. > > If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
