Hi again, I have been having a problem using the word processor in MS Works. If I start it running under the default scripts. I then open a new config file via INSERT+6 and set the say all mode in text processing to line, when say all gets to the bottom of the file, it takes about a half minute to release the cursor. You can hear the system beeps indicating the page bottom. If I change the say all mode to sentence, say all releases the cursor much faster, only about 5 seconds. However, if I maximize the works document window and use say all set to sentence mode, it is a guaranteed way of causing an Illegal operation. In Sentence mode, every time Jaws gets to the bottom of the page, I hear a beep and I get the infamous, "jfw has caused an illegal operation and will be closed down". Now, going back a bit. If I am using say all in sentence mode in a window that is not maximized, after the actual documents has been read and the system beeps are indicating the page bottom, jaws starts reading a long list of graphics. If I press a cursor key at this point, I will often get a context menu related to the zoom control at the bottom edge of the current window which, if I do not interrupt jaws is the last graphic spoken. So, If I go back to a maximized window and set Graphic Verbosity to none, I no longer get the illegal operation but I still can get the context menu by pressing the cursor keys while the system still is beeping. And, after say all is finished reading the cursor flies up to the top of the page and the document cursors up about 50 lines. As a last note, Graphics mode being checked or not checked does not change the above situation. This is JFW 3.30.25 using Access 32 It is always something. I have also sent a message to HJ but I thought I would ask here as well. Thanks, Daine - Visit the jfw ml web page: http://jfw.cjb.net
