Here's the fix folks straight from FS and it works here, and to be honest this means that if you have not made modifications to your script files then there should not be a problem. I have reported that currently sitting here is a friend's system with jaws 13 running in demo mode and it is working perfectly which makes sense given the answer I was given to the current problem.
From: Eric Damery David and others. We have investigated the reported issue and the following should help to explain it. The bottom line is that if you have a default.jsb file (related to default scripts) in your User Directory, removing it will resolve the issue. Below is the more detailed explanation. We are working on something that will help avoid this in the future. We would like you to be able to modify your default scripts, but still allow us to make improvements in this area during updates. Regards, Eric The offending function is "getListViewFieldInfo." This function was added to our default script set during the April hotfix timeline. The function is called from Braille.jss and say.jss. Meanwhile, any user who has in any way modified their default.jss file prior to the patch, has the modified default.jsb from 13.0.718 in their user folder. Each time JAWS loads, it finds and loads the modified default.jsb instead of the new default.jsb released with 13.0.852. Therefore, whenever the call to getListViewFieldInfo comes to the modified default from Braille or say.jss, the unknown function call manifests. The customer solution is to remove default.jsb from their user folder and re-incorporate their customizations into the new default.jss from 13.0.852. To be safe, they should also remove default.jsd, default.jkm, and default.jss from their user folder. For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/
