From experience, rather than from actual knowledge, I believe that the script manager holds the .jkm & .jsd files in memory, thus causing these problems. If I am going to modify manually, either the .jkm or .jsd file, I like Don, close the script manager, then re open it to make the modifications & save the results, & being over cautious, close it again, re opening with the .jss file. Since I have been doing this, I haven't had issues with the script manager deciding for itself, that what I put in the .jkm or .jsd, should be something else. Sometimes I modify these files with Notepad, and make sure that the script manager is closed while I make the changes. Regards, Paul from Australia ----- Original Message ----- From: "Jim Snowbarger" <Snowman@xxxxxxxxxxxxxxxx> Subject: [jawsscripts] Re: Modifying Jaws script for navigating between landmarks I ran into this very same problem yesterday, As don describes, where script manager kept forcing the jkm back to the original assignment. I still can't figure out where the heck script manager is keeping that information. After getting my jkm scrambled several times, and having to fix it manually, I finally made a copy of it, in case it happened again, and started the practice Don describes. Does anybody know where the heck Script manager is storing that original assignment? I thought the JKM was the master. __________� View the list's information and change your settings at http://www.freelists.org/list/jawsscripts