Re: vanishing edsharp
- From: "qubit" <lauraeaves@xxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Wed, 13 Jul 2011 13:18:56 -0500
So are you saying edSharp is currently not working at all on 64 bit when
using nvda?
Jaws and WE work however, right?
I use jaws most, followed by nvda to rescue me from jaws when it crashes,
then window eyes.Thx.
--le
----- Original Message -----
From: "Jamal Mazrui" <empower@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Cc: "Ken Perry" <whistler@xxxxxxxxxxxxx>
Sent: Wednesday, July 13, 2011 9:29 AM
Subject: Re: vanishing edsharp
Yes, there is a LoadLibrary function of the Windows API. However, I do
not think there is a managed version of that function, so it would have
to be called via PInvoke techniques of C#. doing that dynamically and
marshalling appropriate data types through low-level code is a tough way
to go compared to declaring bindings through attributes in source code.
In any case, I was not able to get the 64-bit NVDA DLL to work even
when the EdSharp version targeted Win64 specifically.
Thanks,
Jamal
On 7/13/2011 9:26 AM, Ken Perry wrote:
> Hmm I thought you could load a dll at runtime in fact I think I did it
> with my Yahtzee program so that it would work on either regular windows or
> compact flash. I will have to go dig up that source.
>
> ken
>
> -----Original Message-----
> From: programmingblind-bounce@xxxxxxxxxxxxx
> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui
> Sent: Wednesday, July 13, 2011 7:40 AM
> To: programmingblind@xxxxxxxxxxxxx
> Cc: Hrvoje Katić
> Subject: Re: vanishing edsharp
>
> Unfortunately, I was not able to get the 64-bit version of that DLL to
> work (no speech resulted from NVDA on Win64). Another problem was that,
> even if I had gotten it to work, I did not know of a clean way to use
> either the 32-bit DLL or the 64-bit DLL in the EdSharp code, depending
> on the client platform. I think bindings to a DLL occur when a program
> first launches.
>
> I know the NVDA developers are resistant to developing a COM server
> version of the API, partly because they understandably want to make a
> completely portable version of NVDA possible, and a COM server requires
> entries in the Windows registry. There is a drawback with standard
> DLLs, however, when trying to achieve both 32 and 64-bit compatibility
> (although both 32 and 64 bit COM servers are needed, the same code can
> be used by an application, and Windows automatically routes the COM
> calls to the appropriate server).
>
> With that said, if anyone can provide me with C# code that solves the
> problem I experienced with the NVDA API, I would welcome it.
>
> Jamal
>
>
> On 7/12/2011 1:30 PM, Hrvoje Katić wrote:
>> Hello Jamal,
>>
>> NVDA Controller Client Library is also available in 64-bit variant, as
>> far as I know.
>>
>> Hrvoje
>>
>> Web stranica: www.hkatic.co.cc
>> Mobitel: 0921412665
>> Skype: hrvojekatic
>> Facebook: www.facebook.com/hrvix
>> Twitter: www.twitter.com/hkatic
>> MSN: hrkatic@xxxxxxxxxxx
>>
>>
>> On 12.7.2011. 14:51, Jamal Mazrui wrote:
>>> Tyler is right that if default compiler settings were used,
>>> EdSharp.exe would run as either a 32 or 64-bit executable, depending
>>> on the client platform and .NET Framework installed. Unfortunately,
>>> however, I found that only a 32-bit executable would work well with
>>> all screen reader APIs on Win64. In particular, I could not get the
>>> NVDA API to work from a 64-bit process. I suspect that System Access
>>> would have the same problem because its API uses a standard DLL rather
>>> than a COM server like JAWS or Window-Eyes can do.
>>>
>>> So, for reliability reasons, EdSharp.exe targets Win32 specifically. I
>>> think JAWS or Window-Eyes users can use EdSharp64.exe, however which
>>> targets Win64 instead. I doubt that performance differences will be
>>> noticeable, but welcome any feedback from folks interested in
>>> comparing behavior of those executables (I do not have Win64 yet to
>>> test with, myself).
>>>
>>> Jamal
>>>
>>> On 7/11/2011 3:05 PM, qubit wrote:
>>>> Greetings all --
>>>> Some time this week my system started failing to load edsharp for text
>>>> files, like I had selected, but for expedience I just told it to use
>>>> notepad. Today however I found out why edsharp is not running: it is
>>>> missing. There is the edsetup program and even ed64.exe, in program
>>>> files\edsharp, but no edsharp.exe.
>>>>
>>>> Either I have a system problem or I just accidently clobbered it
>>>> without
>>>> realizing it.
>>>> Can anyone think how this could happen? I haven't touched the
>>>> installation
>>>> folder for many months.
>>>>
>>>> Also, have the 32 vs 64 bit version problems been worked out? I have
>>>> both 32
>>>> and 64 bit machines and would like to put edsharp on all of them. I
>>>> thought
>>>> I skimmed past a thread on where to get 64 bit compiled versions, but I
>>>> missed the final determination of where to download what.
>>>>
>>>> Thanx.
>>>> --le
>>>>
>>>> Where do I get what?
>>>>
>>>>
>>>> __________
>>>> View the list's information and change your settings at
>>>> //www.freelists.org/list/programmingblind
>>>>
>>> __________
>>> View the list's information and change your settings at
>>> //www.freelists.org/list/programmingblind
>>>
>> __________
>> View the list's information and change your settings at
>> //www.freelists.org/list/programmingblind
>>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
>
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
