Hi. If he has something like the dectalk express, it won't tell you the firmware version (maybe its printed somewhere I don't know). Another thing that could be happening is that the onboard memory is being flooded with the hardware messages and then its not clearing properly. If this is the case, then it could very well be a bug in the firmware. If new firmware is available for the synth I would say try to flash it. Explorer has caused a general protection fault in module kernel32.dll. I'm sick of Winblows! On Fri, 21 Jun 2002, Brian Buhrow wrote: > Hello. Although you don't say what kind of synthesizer you have, or > what it's firmware revision is, I'm presuming you're having a handshake > issue between your serial port and your synthesizer, either because your > serial port and synthesizer don't agree on the kind of handshaking to do, > or because your cable is not the right one to perform the handshaking > you've selected. I'm guessing a cable problem. > You can test this theory by following the other gentleman's suggestion of > hitting enter several times during the boot sequence to shut the synth up. > If, when you're done booting, after only letting the synth speak little > snippets of the boot messages, the synth still works at the prompt, then > this is definitely your problem, and the next task is to determine if it is > a cabling issue or whether the synthesizer you're using has a known bug in > its firmware. > So, try the test and report back to us, including whatsynth you're > using and what Speakup thinks its firmware revision is. > -Brian > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >
