Hi Doug Does the process for splitting user code from FS code you mentioned in the following e-mail involve the use of JSX or is it something that keeps the FS default.jsb out of the user settings folder? Thanks. -----Original Message----- From: jawsscripts-bounce@xxxxxxxxxxxxx [mailto:jawsscripts-bounce@xxxxxxxxxxxxx]On Behalf Of Doug Lee Sent: Friday, April 15, 2011 8:16 PM To: jawsscripts@xxxxxxxxxxxxx Subject: [jawsscripts] Re: weird error, "default script not found" but it's there That error does not mean the default script file was not found. It means the default file that is found does not look to JAWS like the default file that came with JAWS. This usually means either of two things, in my experience: 1. Somebody put a default file in your user folder that is a modified version of an older default.jss, from an older JAWS version. OR 2. Somebody changed the default.jss in your shared folder. As the error message indicates, this can indeed cause hard-to-trace problems. I recommend you check the size of the default.jss file in your user folder. If it is large and looks like a default.jss from JAWS itself, chances are it is an older one. If possible, such a file should be replaced with a shorter one that only contains the differences from normal JAWS behavior. The process of doing that is a little involved though. On Thu, Apr 14, 2011 at 09:48:46PM -0700, Jackie McBride wrote: I'm getting an error when starting jaws that my freedom scientific default script was not found. The weird thing is that it's both in the shared settings as well as in my user settings (same file) & opens in script manager when control shift d is pressed. The error warns that unpredictable results may occur, but everything actually works quite normally except for this *very* annoying error. Any1 got any ideas? Text of the error msg follows, for those interested: The Freedom Scientific default script file was not found while loading scripts. This may cause unpredictable results with this version of JAWS. It is recommended that the original script file be restored. OK I had a similar problem once when installing bx toolbox, except that nothing worked. Somehow an older version of a jaws script had gotten into my jaws folder & everything was royally messed up, e.g., I couldn't work. This isn't like that. I only have 1 version of Jaws on my machine (11) & everything works quite well, thanks very much, fs, for the warning of dire consequences sure to ensue. I'd say I somehow messed things up while scripting, except it appears that the default file really is there & intact--compiles successfully, etc. Very weird. Any thoughts welcome. -- Blame the computer--why not? It can't defend itself & occasionally might even be the culprit Jackie McBride Jaws Scripting training materials: www.screenreaderscripting.com homePage: www.abletec.serverheaven.net __________??? 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 __________o?= 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