Re: Dectalk PC driver

["James R. Van Zandt" <jrv vanzandt mv com>]

Ryan -

It is usually not possible to figure out what went wrong from a
description.  Please assemble evidence we can look at.  For example: 

Type "script /tmp/log" to start logging everything.  Then build the
driver, install it with insmod, try to use it, do an "ls -l /dev/d*",
etc.  Add anything else you think might be relevant.  Include "uname
-a" to show what version kernel you are running, and "cat
/proc/modules" to show what modules are installed.  Afterwords, type
control-D to finish the script.  You can edit the script to eliminate
useless stuff and false starts.  Then, include it in your message.

This process does several things.  First, it demonstrates you have
made a real effort to solve it yourself.  Second, it gives someone
else a chance to spot the problem.  (It is almost always something
that you would not have included in your description, because you did
not think it significant.)  Finally, the logical process may let you
solve the problem yourself.  (This happens to me about half the time.)

		  - Jim Van Zandt

>Resent-Cc: recipient.list.not.shown:;@
>MBOX-Line: From blinux-list-request redhat com  Tue Jul 27 10:25:37 1999
>Date: Tue, 27 Jul 1999 07:25:35 -0700 (PDT)
>From: Ryan Shugart <ryan lothlorien nfbcal org>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>Resent-From: blinux-list redhat com
>Reply-To: blinux-list redhat com
>X-Mailing-List: <blinux-list redhat com> archive/latest/1999
>X-Loop: blinux-list redhat com
>Precedence: list
>Resent-Sender: blinux-list-request redhat com
>
>Hi all, I think I've made some progress with the Dectalk driver, but have 
>once again hit a snag.  I learned that the problems have been because one 
>cannot take a .tgz file and use Winzip to make it a .zip file, for some 
>reason that's why it was not installing.  I took the tgz file and put it 
>into a dirrectory of
>/home/ryan/dectalk.  When I untared it I got
>/home/ryan/dectalk/dtpc-0.95.  
>I went into this dirrectory and did make and make dev.  By the way, I was 
>root when i did all of this.  So far so good.  I then ran te insmod 
>dtpc.o command, and again it appeared to work.  it said it found the 
>Dectalk PC.  I ran ./dtstart, and heres where i ran into some problems.  
>It said that it could not find dtload.  So I executed ./dtload at the 
>command prompt and it said that it couldn't find speech device, check 
>usage or the dtpc variable.  My best guess here is I'm not puting it in 
>the right dirrectories, bu the manual didn't say which dirrectory to 
>install it into so I figured I was good wherever.  Where do these drivers 
>need to go?  I'm also assuming the firmware files need to go into the 
>same dirrectory?  
>Ryan