[Bug 18905] Nvda presumably doesn't work

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Jan 7 03:51:37 CST 2018


https://bugs.winehq.org/show_bug.cgi?id=18905

fiendishx at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fiendishx at gmail.com

--- Comment #10 from fiendishx at gmail.com ---
Currently it is possible to get NVDA to install (though not the latest
version). But it doesn't work well enough to be usable.

In a clean Windows 7 

First install at minimum:
winetricks -q ole32

Then to be able to speak the license screen:
winetricks -q  msftedit 

Beyond that, I think a few more winetricks dlls probably help with various
display and operation elements, but honestly I don't know what might help with
what. msscript maybe? riched20? riched30? vcrun####? No idea.

You definitely cannot install version 2017.4[0]; that installer terminates with
errors[1]. But previous versions[2] do install, with patience, once you have
the right dll bits installed from winetricks. 

The problem is that even if I get past the installation, it's mostly useless
for interaction with my application, maybe because the UI interfacing methods
are not implemented in Wine. So I can hear the title of an application window,
and I can hear whatever text is in certain kinds of interface text fields, but
not others, and messages and buttons in the installer read just fine, but none
of the menus or toolbar items read in my Win32 MFC app for instance, and I
can't seem to directly interface with NVDA either to programmatically send text
to its speech engine (using github.com/dkager/tolk or a similar interface
library). I can use Tolk to detect that NVDA is running and that speech is
available, but then sending text does nothing in a package that speaks properly
in Windows versions XP and up[3].

But anyway, once the winetricks bits are installed, then run the NVDA
installer. I'm going to use nvda_2017.3.exe, because it works but can be
annoying to get installed. I think 2016.4 might be less annoying?

First I run wine nvda_2017.3.exe, it plays some music, then a license screen
pops up, and it reads whatever is under the mouse. I click "I agree" and then I
click "Install NVDA on this computer". This will most likely fail, but I guess
that's ok. Once it fails, I go back to the terminal and Ctrl+C to exit and then
run the installer again. Usually this time it succeeds, though sometimes I have
to do it a third time. Now NVDA is already launched by the installer, so if you
want to test it out I guess you can. Often at this point it will say that it
has detected a newer version (2017.4) available. It won't work, so don't let it
try to update. Later I am then able to launch NVDA in gnome without going
through the installer.

But, like I said, after this point it's still basically useless for me because
of how much of my application interface it doesn't read.


[0] - https://www.nvaccess.org/download/nvda/releases/2017.4/nvda_2017.4.exe

[1] - 
wine nvda_2017.4.exe
003f:fixme:seh:_abnormal_termination (void)stub
...
0047:fixme:reg:RegOpenUserClassesRoot (0xb4, 0x0, 0x2000000, 0x118fbb8)
semi-stub
004c:fixme:msg:ChangeWindowMessageFilter 12 00000001
004c:fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial
stub.
004c:fixme:reg:RegOpenUserClassesRoot (0xd4, 0x0, 0x2000000, 0x33efe8)
semi-stub
004c:fixme:advapi:ParseStringSidToSid String constant not supported: L"wd"
wine: Call from 0x7bc4fe61 to unimplemented function
ole32.dll.CoGetApartmentType, aborting

[2] - https://www.nvaccess.org/download/nvda/releases/2017.3/nvda_2017.3.exe ,
https://www.nvaccess.org/download/nvda/releases/2017.2/nvda_2017.2.exe , etc.
The pattern is releases/YYYY.[1234]/nvda_YYYY.[1234].exe

[3] - If you unzip
https://github.com/fiendish/aardwolfclientpackage/releases/download/r1955/Aardwolf_MUSHclient_r1955_no_visuals_no_install.zip
and run the contained MUSHclient.exe on a Windows machine running NVDA, it
should start speaking to you. If NVDA is missing or not detected, it should
default to speaking through SAPI (installable in XP configurations of Wine with
winetricks -q speechsdk).

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list