Hello Ken,
Although the procedure you outlined is for running Audio Grabber with JFW,
I will give the steps I took to run Audio Catalyst which always causes a
GDI error for me. I left out the loading of Window-Eyes, although Audio
Catalyst works well with this screen reader. I started the computer
without a screen reader running. I then brought up Audio Catalyst. If I
wanted to do this often, I would create a shortcut and hot key for Audio
Catalyst. I next minimized my applications with Windows-M. I then loaded
JFW and Alt-Tabbed to Audio Catalyst. I received no error messages, and
Audio Catalyst worked fine with JFW 3.3. Some programs don't speak very
well when JFW is loaded after they are started, but this one did.
I don't think MSAA is causing the errors in the programs you mentioned.
GDI errors are caused by some sort of video conflict. Since JFW hooks into
the operating system at the video driver level, it seems to cause conflicts
with some video drivers when running certain applications. The problems it
causes even persist after JFW is unloaded, and this is why you need to
reboot the computer without JFW being run automatically. Other screen
readers that don't rely on video drivers to get data for their OSM don't
cause these errors. JFW should coexist peacefully with all applications,
but since it doesn't, maybe changing the loading order will help with some
of the conflicts it causes.
Gary, [EMAIL PROTECTED]
At 08:48 AM 6/6/99 -0400, you wrote:
>Hello listeners. I've been on a never ending crusade to understand why JFW
>doesn't work with various programs (Audio Catalyst, Audio Grabber, Black
>widow etc.). Think I've come up with the problem.
>
>It seems that JFW forces many applications to use the MSAA protocol. Some
>applications simply crash due to this fact. The thought behind my finds.
>
>I like many other JFW users had a problem using JFW 3.x with Audio
>Catalyst. Through word of mouth it was said... that Windows-Eyes doesn't
>have this problem. So for kicks, I downloaded the latest build of
>Windows-Eyes (V3.1 demo) and installed it. The installation was similar to
>that of JFW (Speech guide through sound card). I then re-booted the system
>as instructed. Once my system was re-booted, I ran the Windows-Eyes
>program. Explored some of its many menu choices in the main application
>window. I noticed one in particular under options "MSAA application
>(Off)). Said to myself, hmmmm.... I wonder. I then pro ceded to install
>the Audio Grabber v1.5 program.
>
>Audio Grabber worked flawlessly with Windows-Eyes. Just for another
>experiment, I removed the Windows-Eyes program from memory. Didn't remove
>Audio Grabber. Kept it loaded, but minimized to the tasks bar.
>
>Then I loaded good old JFW 3.3.025. No problem, JFw loaded without a
>hitch. Then I pro ceded to maximize the Audio Grabber program. Again, no
>problem. JFW worked with the program as if it was Windows-Eyes. Was able
>to use all components of the program without any conflicts.
>
>Now for the kicker. I then closed the Audio Grabber program, while JFw was
>still loaded in memory. Then I tried to re-load it. You guessed it, the
>program crashed with the same "GDI" error message. Even after closing both
>JFW and Audio Grabber, then re-loading them, the conflict still existed.
>
>So I tried to load Windows-Eyes, after unloading both programs. Of course
>Windows-Eyes didn't work either (It seem to conflict with Windows98
>itself). did the only thing I could think of next, and re-booted the
>system. Once my system re-booted, once again followed the initial
>procedures for getting the Audio Grabber program to work with JFW.
>
>1. Loaded Windows-Eyes into memory.
>2. Loaded Audio Grabber into memory.
>3. Unloaded Windows-Eyes from memory.
>4. Minimized the Audio Grabber program to the tasks bar.
>5. Loaded JFW into memory.
>
>Again, JFW worked with the program quite well.
>
>The above is a lot to go through just to use one program, but just wanted
>to learn more on the "GDI" Mystery. I must mention; After loading JFw
>after Windows-Eyes, my system seemed to run sluggishly. Had problems
>loading Eudora Pro (Needed to first unload JFW, before loading it). So
>overall, not sure if this program is worth the trade off for many of you.
>
>I'm sure JFW causes conflicts with many other programs due to it's use of
>the MSAA format. Maybe HJ can have an option in the "Configurations
>manager" that will allow you to turn off MSAA usage independently to a
>particular application. Hopefully, someone notices this post, and will
>make a note of it for a future patch.
>
>I guess you all can tell, I had a long night. Know the only thing left for
>me is bed (I'm tired as heck...). If someone can shed some light on the
>above premise, I'll be surely glad to converse with them.
>-
>Visit the jfw ml web page: http://jfw.cjb.net
>
>
-
Visit the jfw ml web page: http://jfw.cjb.net
