[jawsscripts] Re: Issues when scripting for 64-bit Windows versions
- From: "Donald Marang" <donald.marang@xxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Sat, 21 Nov 2009 11:45:25 -0500
Jamal, has the JAWS Script Exchange (JSX) application been changed to
address this issue to resolve installing scripts on a 64 bit system in
general? Are there additional steps required that I may not be performing?
Thanks Doug for verifying most of my assumptions and that I understood your
previous message.
Don Marang
----- Original Message -----
From: "Doug Lee" <doug.lee@xxxxxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Friday, November 20, 2009 10:26 AM
Subject: [jawsscripts] Re: Issues when scripting for 64-bit Windows versions
> You have the right line of code and in the right ISS section, but I
> can't tell you about how JSX puts things together from there. You do
> need to rebuild your exe file(s) after making that change though.
>
> On Tue, Nov 17, 2009 at 03:16:11PM -0500, Donald Marang wrote:
> Hi Doug,
>
> I have several scripts which I use JSX to package for distribution. I
> currently do not have access to a 64 bit computer, but I wanted to create
> my
> JSX packages so they would work on 64 bit systems as well. I added the
> following line you previously suggested toward the bottom of the [Setup]
> section of my Scripts.iss file within the C:\JSX directory.
> ArchitecturesInstallIn64BitMode=x64 ia64
>
> I am told this is not working. Previously, the only changes I have made
> to
> this file has been to set constants for version, developer, copyright, and
> so on. I have had to only edit this file to make it use these constants.
> Is this the correct file to update for 64 bit? Does the placement within
> the section matter? Are there more steps required, such as compiling? Is
> a
> new version of JSX required that has made this change, compiled, and
> redistributed?
>
> Clearly, I am missing something here. Since I can not test the 64 bit
> installer for our VMware scripts, Chris Hallsworth will test it out on his
> Windows 7 64 bit system.
>
> Don Marang
>
>
> ----- Original Message -----
> From: "Doug Lee" <doug.lee@xxxxxxxxxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: Saturday, October 03, 2009 3:30 PM
> Subject: [jawsscripts] Issues when scripting for 64-bit Windows versions
>
>
>> This is probably old news to some out there, but in case not...
>>
>> I have spent this week working out a few issues with JAWS scripts on
>> 64-bit Windows versions. One issue I ran into was that Inno Setup
>> installers for such scripts could not find the JAWS registry entries
>> indicating where to install scripts for the various compatible JAWS
>> versions on a 64-bit machine.
>>
>> In summary, it turns out that you have to add something like the
>> following line to the [Setup] section of your .iss file:
>>
>> ArchitecturesInstallIn64BitMode=x64 ia64
>>
>> Without that line, Inno Setup will always have the installer run in
>> 32-bit mode. This is a problem on a 64-bit Windows version because
>> JAWS itself, being a 64-bit process there, will not list itself in the
>> 32-bit version of the system registry. For an Inno Setup installer to
>> find the registry entries for JAWS, it has to run in 64-bit mode and
>> use the 64-bit version of the registry. (I suppose it might be
>> possible to access the 64-bit version of the registry from a 32-bit
>> process, but this method of solving the problem seems easier than
>> working that out in a way that doesn't break compatibility with 32-bit
>> Windows versions.)
>>
>> Another issue I encountered was that some objects that exist on 32-bit
>> Windows do not exist on 64-bit Windows. Most prevalent in my work
>> among these is the MSScriptControl.ScriptControl object, which comes
>> from c:\windows\system32\MSScript.ocx. According to my research,
>> there is no 64-bit version of this object available or planned by
>> Microsoft. I doubt many scripters have used this, but I have on a few
>> occasions. Since Microsoft encouraged dynamic scripting of this sort
>> for years, I was quite stunned to discover that they are apparently
>> dropping support for this one.
>>
>> Any further input from JAWS scripters working with 64-bit Windows
>> versions is welcome indeed.
>>
>>
>> --
>> Doug Lee, Senior Accessibility Programmer
>> SSB BART Group - Accessibility-on-Demand
>> mailto:doug.lee@xxxxxxxxxxxxxxxx http://www.ssbbartgroup.com
>> "While they were saying among themselves it cannot be done,
>> it was done." --Helen Keller
>> __________
>> Visit and contribute to The JAWS Script Repository http://jawsscripts.com
>>
>> View the list's information and change your settings at
>> //www.freelists.org/list/jawsscripts
>>
>
> __________?
> Visit and contribute to The JAWS Script Repository http://jawsscripts.com
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
> --
> Doug Lee, Senior Accessibility Programmer
> SSB BART Group - Accessibility-on-Demand
> mailto:doug.lee@xxxxxxxxxxxxxxxx http://www.ssbbartgroup.com
> "While they were saying among themselves it cannot be done,
> it was done." --Helen Keller
> __________
> Visit and contribute to The JAWS Script Repository http://jawsscripts.com
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
__________
Visit and contribute to The JAWS Script Repository http://jawsscripts.com
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
Other related posts:
