-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, May 07, 2004 at 01:56:34PM +0200, Hynek Hanke wrote: > If you want to experiment with timing issues, please do so. The most > logical order is this: > > 1) load speakup-sftsyn (as this has nothing to do with the next step, > loading Speech Dispatcher, but is necessary for speechd-up) > 2) load speech-dispatcher (necessary for speechd-up) > 3) now you have to ,,wait'' till both speakup-sftsyn and speech-dispatcher > are up and running > 4) run speechd-up > > Note that speechd-up should complain (return with an error code) if > either speakup-sftsyn or speech-dispatcher is not up and running when > it's being started. But there might be a bug somewhere. More info is welcomed. I never got such messages from speechd_up. I only get the log that was mentioned in previous messages on the list. I even went up to a 7 second sleep time before starting speechd_up. Same result. no speech and that funny message in speechd-up.log. It still works fantastically on my P120 laptop. - ----- Begin log ----- [Fri May 7 05:56:25 2004] speechd: Speechd-speakup starts! [Fri May 7 05:56:25 2004] speechd: ERROR: [y: this command is not supported] - ----- End speechd-up.log ----- I should also note that this log starts over with each new invokation of speechd_up. I don't know if that is intended or not but currently any past errors would be lost when you restart the program. - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAoqu6WSjv55S0LfERAjtQAKCXJctTz6/cXQ0AMGiuRGKKP4VYwACdG+bs 4H3XptwNQKSG/0Hbko48EiY= =DCqH -----END PGP SIGNATURE-----
