The list of DLLS, on which NVDA screen reader is strictly depend

[Mgr. Janusz Chmiel]

Dear developers of Reactos,

    As i promised in my previous E-mail, i AM sending You The list of dlls, on which NVDA
screen reader is strictly depend and without them will not work.

Thank You for any feetback provided.


   OLEAUT32.dll - C:\WINDOWS\system32\OLEAUT32.dll
   USER32.dll - C:\WINDOWS\system32\USER32.dll
   POWRPROF.dll - C:\WINDOWS\system32\POWRPROF.dll
   SHELL32.dll - C:\WINDOWS\system32\SHELL32.dll
   ole32.dll - C:\WINDOWS\system32\ole32.dll
   WINMM.dll - C:\WINDOWS\system32\WINMM.dll
   WSOCK32.dll - C:\WINDOWS\system32\WSOCK32.dll
   COMDLG32.dll - C:\WINDOWS\system32\COMDLG32.dll
   ADVAPI32.dll - C:\WINDOWS\system32\ADVAPI32.dll
   msvcrt.dll - C:\WINDOWS\system32\msvcrt.dll
   WS2_32.DLL - C:\WINDOWS\system32\WS2_32.DLL
   GDI32.dll - C:\WINDOWS\system32\GDI32.dll
   VERSION.dll - C:\WINDOWS\system32\VERSION.dll
   KERNEL32.dll - C:\WINDOWS\system32\KERNEL32.dll
   COMCTL32.dll - C:\WINDOWS\system32\COMCTL32.dll
   RPCRT4.dll - C:\WINDOWS\system32\RPCRT4.dll

Extracting all API calls from NVDA source code written in Python will not be easy task,
and extracting those calls from source code written in C language for several helper
libraryes will not be asy to.

[Andrew Faulds]

On 02/02/2010 20:33, Mgr. Janusz Chmiel wrote:
>   Dear developers of Reactos,
>      As i promised in my previous E-mail, i AM sending You The list of 
>  dlls, on which NVDA screen reader is strictly depend and without them 
>  will not work.
>  Thank You for any feetback provided.
>
>     OLEAUT32.dll - C:\WINDOWS\system32\OLEAUT32.dll
>     USER32.dll - C:\WINDOWS\system32\USER32.dll
>     POWRPROF.dll - C:\WINDOWS\system32\POWRPROF.dll
>     SHELL32.dll - C:\WINDOWS\system32\SHELL32.dll
>     ole32.dll - C:\WINDOWS\system32\ole32.dll
>     WINMM.dll - C:\WINDOWS\system32\WINMM.dll
>     WSOCK32.dll - C:\WINDOWS\system32\WSOCK32.dll
>     COMDLG32.dll - C:\WINDOWS\system32\COMDLG32.dll
>     ADVAPI32.dll - C:\WINDOWS\system32\ADVAPI32.dll
>     msvcrt.dll - C:\WINDOWS\system32\msvcrt.dll
>     WS2_32.DLL - C:\WINDOWS\system32\WS2_32.DLL
>     GDI32.dll - C:\WINDOWS\system32\GDI32.dll
>     VERSION.dll - C:\WINDOWS\system32\VERSION.dll
>     KERNEL32.dll - C:\WINDOWS\system32\KERNEL32.dll
>     COMCTL32.dll - C:\WINDOWS\system32\COMCTL32.dll
>     RPCRT4.dll - C:\WINDOWS\system32\RPCRT4.dll
>  Extracting all API calls from NVDA source code written in Python will 
>  not be easy task, and extracting those calls from source code written 
>  in C language for several helper libraryes will not be asy to.
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev 
All of these dlls, apart from one,
are already in ReactOS, just need 
work to make them more compatible.
msvcrt.dll isn't in ReactOS but you can download and install the Visual 
C++ 6.0 Runtimes for free from Microsoft's website.

-- 
Andrew Faulds (andrewweb)
http://andrew.duckgalaxy.com/
Sent from Mozilla Thunderbird

[Olaf Siejka]

Please try to run this application in ROS and open a bug report if it doesnt
work, providing all the necessary information. This is, including debug
logs.

W dniu 2 lutego 2010 21:33 użytkownik Mgr. Janusz Chmiel
<chmiel(a)deep.xn--cz>napisa-occapisał:

>    Dear developers of Reactos,
>
>      As i promised in my previous E-mail, i AM sending You The list of dlls,
>  on which NVDA screen reader is strictly depend and without them will not
>  work.
>
>  Thank You for any feetback provided.
>
>
>     OLEAUT32.dll - C:\WINDOWS\system32\OLEAUT32.dll
>     USER32.dll - C:\WINDOWS\system32\USER32.dll
>     POWRPROF.dll - C:\WINDOWS\system32\POWRPROF.dll
>     SHELL32.dll - C:\WINDOWS\system32\SHELL32.dll
>     ole32.dll - C:\WINDOWS\system32\ole32.dll
>     WINMM.dll - C:\WINDOWS\system32\WINMM.dll
>     WSOCK32.dll - C:\WINDOWS\system32\WSOCK32.dll
>     COMDLG32.dll - C:\WINDOWS\system32\COMDLG32.dll
>     ADVAPI32.dll - C:\WINDOWS\system32\ADVAPI32.dll
>     msvcrt.dll - C:\WINDOWS\system32\msvcrt.dll
>     WS2_32.DLL - C:\WINDOWS\system32\WS2_32.DLL
>     GDI32.dll - C:\WINDOWS\system32\GDI32.dll
>     VERSION.dll - C:\WINDOWS\system32\VERSION.dll
>     KERNEL32.dll - C:\WINDOWS\system32\KERNEL32.dll
>     COMCTL32.dll - C:\WINDOWS\system32\COMCTL32.dll
>     RPCRT4.dll - C:\WINDOWS\system32\RPCRT4.dll
>  Extracting all API calls from NVDA source code written in Python will not
>  be easy task, and extracting those calls from source code written in C
>  language for several helper libraryes will not be asy to.
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>

[Mgr. Janusz Chmiel]

Dear core developers,

    I would like to really intensively test The Reactos and i would really like to send
The debug logs. But first of all, i need to install The .sys driver for The Soundmax
integrated digital audio. I know about other screen reader, which could use less dlls and
is more simple, it's name is Pocked reader and this program has been programmed in The
Microsoft Visual Basic 6.0 professional edition and it uses it's own speech engine no
Espeak, but it's own algorithms for synthesizing speech, but only for Czech language.

I would use Pocked reader even while working with Wine, but without possibility to geeting
The necessary feetback for example, no menu items even from The Pocked reader internal
windows could not be retrieved. 

I know, that on Windows XP it is possible to use device manager and reinstall The driver,
but i do not know, if The device manager of Reactos can also use this feature. I know,
that The driver for The soundmax integrated digital audio can be installed without need to
use included setup program. My problem is, howto add device driver without feetback of The
screen reader.

Is there any possibility, for example, use complicated command line consists of rundll32
dll name and some procedures with The required paramethers?

I also have Tieman braille Voyager braille device, but i do not know, if adding The .sys
driver would be also possible for this device.

Thank You very much for any feetback and help provided. I think, that You would know, how
to bypass The add hardware or how to use it without required feetback.