Subject: From: Date:

Re: [ECS] VOICE-INTERFACE-C error Mark Gilmore Sun, 10 Jan 1999 09:30:26 -0800

---

ECS only uses the BLASTER env-var in checking for IRQ and
address conflicts.
I thought this was required for all SB's.
On 2nd thought, may I should leave it in ???
Comments ?

Clay Jackson wrote:
> 
> Hey, Kevin -
> 
> I just went through this myself.  To be honest; I'm not 100% sure what I did
> that made that message stop - but I THINK it was setting the it to
> "Connected"; after making REALLY sure that Windoze did in fact "recognize"
> the card (Start Menu->Settings->Control Panel->System to check that).
> 
> Just as an FYI - I'm having pretty good luck with the MS Speech Engine on a
> 486/66.
> 
> Clay Jackson
> clayj@nwlink.com
> 
> > -----Original Message-----
> > From: Kevin Keast [mailto:libertyc@prodigy.net]
> > Sent: Saturday, January 09, 1999 1:47 PM
> > To: ECS
> > Subject: [ECS] VOICE-INTERFACE-C error
> >
> >
> > Why would I get the following error with voice-interface-c?
> >
> > BLASTER env-var not set (Item "Voice-Interface-C")
> >
> > I thought voice-interface-c worked with any sound card that could
> > play .wav
> > files.
> >
> > .wav files are playing fine everywhere else.
> >
> > Kevin
> >
> >

-- 
Mark Gilmore
Omnipotence (ECS home automation software)
omnip@usit.net
http://www.usit.com/omnip

---