From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dukecmmtar04.coxmail.com (dukecmmtar04.coxmail.com [68.99.120.47]) by speech.braille.uwo.ca (Postfix) with ESMTP id 9432A10BF1 for ; Thu, 30 Apr 2009 06:56:27 -0400 (EDT) Received: from [192.168.0.29] (really [70.166.17.50]) by dukecmmtar04.coxmail.com (InterMail vM.7.05.02.00 201-2174-114-20060621) with ESMTP id <20090430104832.LPRN14184.dukecmmtar04.coxmail.com@[192.168.0.29]> for ; Thu, 30 Apr 2009 06:48:32 -0400 Message-ID: <49F98433.1000406@baechler.net> Date: Thu, 30 Apr 2009 03:57:55 -0700 From: Tony Baechler User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: "Speakup is a screen review system for Linux." Subject: Re: Trying to get a Dell Enspiron Laptop to Talk References: <200904282052.n3SKqTac093300@dc.cis.okstate.edu> <49F830C3.5060301@baechler.net> <20090429195026.GA21091@localhost.localdomain> In-Reply-To: <20090429195026.GA21091@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.12 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Apr 2009 10:56:28 -0000 Hi, You might be right, I'm not sure. I was using the 7.10 or 8.04 live CD, so hopefully the problem is fixed in newer versions. However, the sighted help said that Orca wasn't running and I certainly had no speech. When I launched it manually, I saw no indication of two copies running. I think it was a bug in the CD though because it worked fine on a different machine with more memory and the instructions for booting with speech were wrong. As I say, I'm sure the problem is fixed in 9.04 but I went with grml instead which I later converted into Debian unstable. I would still like to try Ubuntu again, perhaps in a virtual machine. Gregory Nowak wrote: > FYI, I've found that when running with 256M of ram, and having orca > set to > launch after login, it does in fact launch, even though it seems not > to have launched. My solution is to login, wait a few minutes, do an > insert+q, tab over to the quit button, or whatever it is called, hit > enter, wait maybe half a minute, and restart orca. You should find > that the machine is more responsive with only one instance of orca > running, instead of 2. Note that even though the orca docs say that > orca will kill any previously running copies of itself when another > copy is launched, this isn't the case for me when running under 256M of > ram, thus the need to use insert+q to get out of orca, instead of just > starting it up right there. This is my experience on 256M of ram, and > your results may of course vary. >