[nvda] Re: Intro and a Question

Hi. Sorry for the delay in replying but I've been busy as of late. I could not 
find any log file for NVDA. I checked in the Control Panel to make sure all 
versions of NVDA were uninstalled and they are. I still have the setup file for 
R2728 so I installed that and ran it. System Access to Go was in memory when I 
downloaded the file, but I shut down SA to Go once I was ready to run Setup. I 
still got the ding from my system though. I've searched through all my 
directories and can't find any log file. 
Jake
  ----- Original Message ----- 
  From: Michael Curran 
  To: nvda@xxxxxxxxxxxxx 
  Sent: Saturday, February 21, 2009 4:32 PM
  Subject: [nvda] Re: Intro and a Question


  Hi,

  We really need a log file if possible. Try running NVDA and then when the 
error occures, find nvda.log in your %temp% directory.

  However, when you uninstall a previous version of NVDA, check that it really 
did uninstall, by going to where ever you installed it (e.g. c:\program 
files\nvda) and making sure that directory is really gone.

  Mick



  On 22/02/2009 3:24 AM, Jake Joehl wrote: 
    Hi everyone. My name is Jake and I have used NVDA off and on ever since the 
project first started. I love it and think it has extraordinary market 
potential. In addition to using it here on my home PC, I have it installed on 
two computers at work. Recently though, I've been experiencing a rather strange 
problem. I've been using the snapshots for version 0.6p2, and this problem 
began with revision 2672 or thereabouts. Whenever I download NVDA now, I get 
the intro music but then my system bongs at me followed by complete silence. 
Funny thing is, I already have eSpeak installed for use with the betas of 
Klango version 2.1. This problem happened even before I installed the separate 
eSpeak. I have uninstalled all prior trunks and full versions of NVDA. I am 
using Windows Vista on a Dell Inspiron desktop PC, and I have System Access to 
Go loaded right now. What I don't understand here is that NVDA worked just fine 
up until this problem began occurring. Any help greatly appreciated. Thanks.
    Jake

Other related posts: