Jerry, I would suggest taking a look at your keymap file manually within script manager or your development environment to make sure that all of your key assignments are there and that there are no blank lines within your keymap file. Additionally, make sure that all files related to your scripts are placed either in your shared settings or your user settings folder combining files if necessary. Once this has been done recompile using script manager. Try your scripts again. If this fails, turn on script utility mode and turn on script logging (WindowsKey+s). Then retry your scripts again. Next, go back to script utility mode and press (WindowsKey+u) to list any unknown function calls. Additionally, you may want to resynchronize your documentation (alt+f, y) within script manager. If all of this does not work, you might try compiling your scripts using SCompile. Open a command window within the settings folder that your scripts are in. next run scompile -d script-file_name. Note that unless scompile is in your path, that you may have to specify the full path. HTH, Jon. -----Original Message----- From: jawsscripts-bounce@xxxxxxxxxxxxx [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Jerry Posey Sent: Tuesday, July 13, 2010 11-46 AM To: jawsscripts@xxxxxxxxxxxxx Subject: [jawsscripts] Script stopped working I have this script for a program written in Cobol which looks like a dos program. I do a lot of searching for what's on the screen so I can tell where the curso is located. It's been working since at least January on several computers all with the same basic configuration. Now one of them has stopped working and only reads some of the information which it has been reading. I did a repair on the JAWS 11 that it was running with no effect. I then completely uninstalled JAWS and installed the latest version of JAWS 11 and reinstalled the scripts with a couple of minor changes but it still does the same thing it was doing before for the most part. The one thing that it was doing was when I hit a down arrow which closes out a ticket and moved down to another line, it was acting like the JAWS cursor was active but would stay on the same line when you hit another down arrow. I fixed that by doing an alt t instead which is another way the program uses to close the ticket. This is the only computer that this is happening on and I'm at a loss on where to go to try to resolve it. Would installing JAWS 10 tell me anything and if I do, should I uninstall JAWS 11 first? Thanks for any suggestions. Jerry __________� View the list's information and change your settings at http://www.freelists.org/list/jawsscripts __________� View the list's information and change your settings at http://www.freelists.org/list/jawsscripts