Thanks, a solution would be great. I'll experiment a bit myself and see if anything pops out.
Best wishes, Bryan----- Original Message ----- From: "Jamal Mazrui" <empower@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx> Sent: Tuesday, November 13, 2007 4:26 AM Subject: Re: JAWS Script Exchange, a bug?
Indeed, that is a current limitation of jSX. The Inno Setup code looks for a .zip archive with the same name as the executable except for a .zip rather than .exe extension. During development, I recall not having a way to know the name of the zip archive packed inside the installer, so adopted that convention. When I get a chance, I'll revisit the code and see if another solution occurs to me. Jamal On Mon, 12 Nov 2007, Bryan Garaventa wrote:Date: Mon, 12 Nov 2007 14:48:33 -0800 From: Bryan Garaventa <bgaraventa11@xxxxxxxxxxxxxx> Reply-To: programmingblind@xxxxxxxxxxxxx To: programmingblind@xxxxxxxxxxxxx Subject: JAWS Script Exchange, a bug?I'm not sure if this is a bug, but hopefully there is a way to get around it.When you create a script installer, and the ScriptInstaller.exe is generated, the scripts install correctly as usual.However, if you provide the installer as a web download, and someone renames the installer to something that makes more sense to the user, (such as ScriptName.exe), an error occurs during the installation, and the scripts cannot be installed.So far, I've had to warn people who are downloading the installer to not rename the file, which doesn't seem like the best solution.Any ideas why it is doing this? Thanks, Bryan__________ 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
