Comment 1 by briang1 on 2011-01-06 09:37
OK, I certainly cannot duplicate this on xp sp3 here at all, so can you perhaps get a log file of what actually goes on when you use nvda/q?
Do the falling tones occur when you exit or not?
I'm also assuming you know that the nvda service stays running if you exit in any case, though the executable terminates. Was this on a portable version or an installed one?

What I'd suggest for the log is that you get someone sighted to copy the log file somewhere out of the way, so you can get at it and it will not be overwritten when you start the new instance. Normally even if nvda does get stuck as can occur if an application crashes, eventually a new instance loads up.

Could there be anything running on your machines that is out of the ordinary that may be intercepting the closing of the program I wonder?

Comment 2 by briang1 on 2011-01-06 19:27
Just in case its of help, this little batch file I find invaluable to get a look at the log if things go wrong. Note the need to change the patth though. Just m paste it into notepad and save it in the root of the drive as rebootnvda.bat and shove a shortcut to int on the desktop with a convenient key.
@echo off

rem, note this batch file is set up for xp.
rem alter the line below to reflect the location of the log file on your machine.
cd "\Documents and Settings\brian\Local Settings\Temp"
rem This and the one lower down are different on Windows 7
start /WAIT c:\progra~1\nvda\nvda.exe -q

start notepad.exe nvda.log
rem, this line just kicks its heels for a bit to make sure the log is loaded into rem notepad before rebooting nvda.
ping -n 5 127.0.0.1>nul
start c:\progra~1\nvda\nvda.exe

exit

Comment 3 by Rughead on 2011-01-07 00:42
I am using the installed version 2010.2 on both computers, one running Win7
Ultimate, and the other running XP Pro SP3. The only two similar programs
that both computers run that I can think of is iTunes and Windows Defender.
That is beyond the default OS programs of course. Both computers are built
quite differently with very different hardware. Yes, the falling tones do
occur when quitting NVDA.

Here is the log file from the XP computer produced right after quitting
(before trying a restart). nvda.log:

INFO - nvda (16:00:45):
Starting NVDA
INFO - core.main (16:00:45):
Config dir: C:\Documents and Settings\Curtis Hall\Application Data\nvda
INFO - core.main (16:00:45):
NVDA version 2010.2
INFO - core.main (16:00:45):
Using Windows version sys.getwindowsversion(major=5, minor=1, build=2600,
platform=2, service_pack='Service Pack 3')
INFO - core.main (16:00:45):
Using Python version 2.7 (r27:82525, Jul 4 2010, 09:01:59) v.1500 32
bit (Intel)
INFO - core.main (16:00:45):
Using comtypes version 0.6.2
INFO - synthDriverHandler.setSynth (16:00:49):
Loaded synthDriver eloquence
INFO - core.main (16:00:49):
Using wx version 2.8.11.0 (msw-unicode)
INFO - braille.initialize (16:00:49):
Using liblouis version 2.1.1
INFO - braille.BrailleHandler.setDisplayByName (16:00:49):
Loaded braille display driver noBraille
WARNING - core.main (16:00:50):
UIA not available
INFO - core.main (16:00:50):
NVDA initialized
INFO - core.main (16:01:02):
Exiting
INFO - config.save (16:01:02):
Configuration saved
INFO - nvda (16:01:03):
NVDA exit

_end log file_

Also, here is an interesting part of the nvda.exe.log file that I noticed:

Traceback (most recent call last):
File "nvda.pyw", line 123, in
File "logHandler.pyo", line 224, in initialize
File "logging__init__.pyo", line 819, in init
File "logging__init__.pyo", line 840, in _open
File "codecs.pyo", line 865, in open
IOError: 22 invalid mode ('wtb') or filename:
'c:\windows\system32\config\system1\locals1\temp\nvda.log'

_end nvda.exe.log_

This was also from the XP system.

Note also, after quitting NVDA, and then trying to launch JAWS. When I go
into Processes under Task Manager, the moment I terminate the NVDA process,
JAWS immediately starts.

Curtis

Comment 4 by nvdakor on 2014-08-27 10:41
Hi Curtis and others,
Does this happen with 2014.2 under Windows 7 or 8.x? At least in 8.x, I can launch JAWS after I quit NVDA and vice versa.

Probably OK to close this one because the software involved has changed quite a bit since thereport and no new mention was made of it since 2011.