[jawsscripts] Re: Migrating Jaws 14 scripts from Windows 32-bit to 64 bit
- From: Artur Räpp <rtr@xxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Tue, 21 Oct 2014 09:38:35 +0300
Hello,
I guess that the problem is in communication between 64bit - 32bit process.
64bit process (JAWS) can't communicate with 32bit Java (guess)
I know that such problem exists between 64bit JAWS and 32bit SAPI4 (SAPI4 is
only in 32bit version), 64bit JAWS can'tuse SAPI4 synths.
If you can use 64bit Java application instead, this might solve your problem.
HTH
Artur
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Bruce Alsup
Sent: Tuesday, October 21, 2014 2:02 AM
To: program-l@xxxxxxxxxxxxx; Jaws Script List; 'program-java';
Jawsscriptlang@xxxxxxxxxxxx; jawsscripting@xxxxxxxxxxxx
Cc: Rick J. Bunch
Subject: [jawsscripts] Migrating Jaws 14 scripts from Windows 32-bit to 64 bit
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Hello to all those interested in and adept at Jaws scripting and programming
for screen readers in general. I have experienced an issue trying to upgrade
from Windows 32-bit to Windows 64-bit that has me stuck and am hoping some
smart folks can help. Any comments and suggestions you make will be heartily
appreciated. Just so you know, the jobs of 7 people are at stake.
ISSUE: Using Jaws For Windows version 14.0.9006, we have custom scripts for a
proprietary Java-based 32-bit application that work in Windows Enterprise
32-bit, but will not work in Windows Enterprise 64-bit. We are using the
default voice Eloquence in all environments.
BACKGROUND: The custom JFW scripts were created using JFW 13.0.303 on a
Windows Enterprise 32-bit machine. The scripts were tested extensively and all
worked as expected. The compiled binary file (.jsb) was loaded into JFW
14.0.9006 when the update was installed. In the 32-bit OS, the custom scripts
worked as expected.
These custom scripts were built to support QIK, a Java-based 32-bit
application. Java Access Bridge was installed using steps from both Freedom
Scientific and Oracle support sites. We have tested the Windows 32-bit
installation on several machines and all of the custom scripts function as
expected. Java Access Bridge was also installed on the 64-bit, per the
instructions provided by Oracle. We have checked to ensure the appropriate
.dlls are in the WOW64 AND WIN32 directories.
We are currently migrating to Windows Enterprise 64-bit operating
environment. After installing JFW 14.0.9006 x64, the custom .jsb was added
to the shared files directory in the same manner used on the 32-bit machine.
The customization did not work in the 64-bit environment. Specifically at issue
are the Java table functions: NavigateJavaTable (int UnitMovement) and
Function ActiveItemChangedEvent (handle curHwnd, int curObjectId, int
curChildId, handle prevHwnd, int prevObjectId, int prevChildId). The default
functions for JFW 13.0.303 was used to build the custom script that supplied
additional instructions for the QIK application. Again, these scripts function
properly in the 32-bit environment..
TECHNICAL INFORMATION:
Windows Enterprise 32-bit Environment (Jaws custom scripts work well in this
environment)
Java version jre1.6.0_21 (required for our version of Qik)
Java Access Bridge version 2.0.2
JFW 14.0.9006 32-bit
Windows Enterprise 64-bit Environment (Jaws custom scripts DO NOT work in this
environment)
Java version jre1.6.0_21 (required for our version of Qik)
Java Access Bridge version
JFW 14.0.9006 64-bit
Bruce Alsup
Rehab Engineer
OSET, Inc.
Applying Technology to Mitigate Blindness and Visual Impairment
Phone: (904)219-4799
Website: <http://oset.com/> http://oset.com
__________ļæ½
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
Other related posts: