I get the same error when run as administrator. My ProgramData and ProgramFiles Environment Variables are defined on this computer. *Don Marang* Vinux Package Development Coordinator - vinuxproject.org <http://www.vinuxproject.org/> On 3/28/2013 9:21 AM, Jamal Mazrui wrote: > Thanks for that specific example. In case it makes a difference, can you try > running JSX as admin? > -----Original Message----- > From: jawsscripts-bounce@xxxxxxxxxxxxx > [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Don Marang > Sent: Wednesday, March 27, 2013 8:55 PM > To: jawsscripts@xxxxxxxxxxxxx > Subject: [jawsscripts] Re: JSX with JAWS 14.0 and Win64 > > I have not been able to install scripts with JSX ever since I upgraded to > Windows 8 standard 64 bit this past weekend. Whether running as a service > (in System Tray upon startup) or restarting JAWS, I get the following error: > Alert > Cannot find directory > \Freedom Scientific\JAWS\14.0\Settings\Enu OK > > This appears that the Environment Variables for the standard Windows > directories are not defined! At least, they are not getting substituted. > *Don Marang* > Vinux Package Development Coordinator - vinuxproject.org > <http://www.vinuxproject.org/> > > On 3/27/2013 4:45 PM, Jamal Mazrui wrote: >> Well, now I just tried without reloading JAWS, and JSX also worked >> then. So, if anyone can give me a specific JAWS/Windows combination >> where JSX is failing to find the user script directory, please let me know. >> >> Jamal >> On 3/27/2013 3:22 PM, Doug Lee wrote: >>> To my knowledge, JAWS does not run as a service under Windows >>> versions after XP, so this problem should not apply to >>> JAWS-compatible 64-bit Windows versions. If I'm wrong, I'd sure like >>> to know it. :) >>> >>> On Wed, Mar 27, 2013 at 02:35:47PM -0400, Jamal Mazrui wrote: >>> Some people have reported a problem where JAWS Script Exchange does >>> not find the user script directory with JAWS 14.0 on 64-bit Windows. >>> I have been investigating this and have at least found a workaround, >>> which probably applies to other JAWS/Windows combinations as well. >>> >>> I do not understand this fully, but JSX seems to work properly if >>> JAWS is running as a user process rather than as a system service. If >>> JAWS was loaded automatically at Windows startup, then it may be >>> running as a system service. So, unload and then reload JAWS to make >>> it run as a user process. >>> >>> Jamal >>> >>> __________??? >>> >>> View the list's information and change your settings at >>> //www.freelists.org/list/jawsscripts >>> >> __________ >> >> View the list's information and change your settings at >> //www.freelists.org/list/jawsscripts >> > > > __________ > > View the list's information and change your settings at > //www.freelists.org/list/jawsscripts > > __________� > > View the list's information and change your settings at > //www.freelists.org/list/jawsscripts > __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts