Jacob, I don't have the exact return codes in front of me but they appeared to be from viavoice library functions which were probably displayed by the cmdline demo programs. I'll have to go in a compile the kernel module for my soundcard and try it to see whether it works with the "real" oss. A friend of mine speculated that I may have a different pthread library, but plugging in a different soundcard module should be easy to do. Have you used viavoice with anything other than the demo programs? Chris On Wed, Apr 11, 2001 at 04:17:28PM -0400, Jacob Schmude wrote: > Hi > Well that's exactly what mine does. Speaks a few phrases and halts with > some odd errors, including a speech device initialization problem. OSS mods > are loaded. Odd thing is that it works fine with non-alsa drivers. The > errors don't seem to indicate a shared library problem outside of ViaVoice, > the return errors seem to come from ViaVoice-specific libraries alone, > though I'm not sure how relevant this is. What are the errors you are > getting, exactly? > > I doubt seriously that it's a shared C library problem. If it was, it > would have probably failed with a segmentation fault or would have > complained about a missing shared object. > > > > > On Wed, Apr 11, 2001 at 07:19:19AM -0500, w1gm at sdf.lonestar.org wrote: > > Jacob, > > I've gotten viavoice to speak one or two phrases before it prints some > > return codes on the screen and must be stopped with a ctrl-c. Make sure > > your oss modules are loaded by doing an lsmod as root. I suspect what is > > going on is viavoice was tested with a certain set of shared > > libraries. Unfortunately, I can't find documentation on what specific > > libraries are needed. > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Chris The Moon is Waning Gibbous (78% of Full)
