I know of two things that can cause an automatic emergency exit from BX: 1. Something taking too long, usually over five seconds, to execute. If you press a key and don't get a response for over five seconds, that's probably it, and something on your computer is very busy or slow. 2. A keyboard conflict between BX and the current application. This happens when an application's scripts do not properly chain the KeyPressedEvent, meaning the scripts fail to call the default KeyPressedEvent when finished with any special processing. If you are experiencing automatic emergency exits that seem to fit item 1 above, the best approach is to figure out what's slowing things down. If your exits do not seem to fit item 1, and if they happen all the time when this application is in focus, not just sometimes, they might fit item 2. The solutions for that are as follows: 1. If you control the scripts for the application, edit the KeyPressedEvent to make sure the default event is called any time the scripts don't have a reason not to do so. If done properly, this will fix the problem and allow both BX and all application scripts to work at the same time. 2. If for some reason that is not practical, such as if you're dealing with application scripts that come with JAWS itself or from a third party, you'll have to edit bx.jcf and alter the way BX handles the keyboard. Unfortunately, this must be done manually at this time. Follow the example of the last sections already in bx.jcf. If your application is called MyApp.exe, add this to bx.jcf: [MyApp.exe BX Options] controlFlags=1 This will make BX override the application scripts when BX is on, thus circumventing the application scripts' failure to chain the event. Any keys scripted by the application scripts will not work normally while BX is actually on however. This should not matter unless you are in the habit of using application scripts while in a BX map that allows them, such as Cursor Navigation or Object Examination. Hth. On Wed, Jun 03, 2009 at 03:48:21PM +0200, Johannes Grib wrote: Hello to all you clever script writers, A little puzzle. When trying to navigate with bx toolbox in a custom .net application, I get the following error: "automatic emergency exit". BX seems to be working in all other apps. Any ideas on this please? Thanking you and kind regards Johannes Grib SOFTWARE DEVELOPER / A.T. SPECIALIST Barone, Budge & Dominick (PTY) LTD Tel: +27 11 532 8670 Fax: +27 11 532 8300 Mobile: +27 82 358 2500 Email: johannesg@xxxxxxxxx Web: www.bbd.co.za __________? 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