The issue you describe (about jaws not reading tab pages) sounds like a
video driver/video intercept issue. Unfortunately, sometimes video intercept
issues can't be fix except by a reinstall of the system if you are dealing
with certain drivers. This at least has been my experience. 
What video card/graphics adapter do you have?
Are you using an x86 or x64 system?
Also, have you modified window titles? I sometimes have to edit the hsc sets
if I change the main window title for a synth using the plugIn manager...

HTH, D!J!X!

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Cameron
Sent: Friday, September 24, 2010 11:56 PM
To: 'JSonar -- JAWS Scripts for Sonar discussion list'
Subject: [Jsonar] hsc build 198 did not fix my issue and I am still not
ableto read certain things in sonar.

Hello everyone.  I installed hsc build 198 this evening and it did not fix
my issue.  I am still getting the window not found, hot spot failed message
whenever I try to use hsc sets with any of the soft synths included with
sonar 8.5 producer.  I made sure the proper hsc set was loaded, and I also
tried picking things from the list instead of using the hsc command and I
just get the same error message.

On Sunday, I'm going to have a friend help me install a seperat partition on
my system drive that will be for sonar only.  until then, is anyone else
experiencing this?

I don't get it.  I'm using the latest hsc sets, latest version of jsonar,
latest version of jaws ten, all my display settings are correct, yada yada
yada...  and there don't appear to be any dialogue boxes etc blocking the
dimension pro window for example, at least nothing that the virtual viewer
or jaws cursor can see.

I can see the presets box with the jaws cursor and the pc cursor in
dimension pro, rapture le, etc so why doesn't the virtual mouse click that
hsc does work?

Also, for some reason, jaws is not reading things in lists and it's not
reading page tabs in dialogue boxes etc.  it just says tab, when it should
say general or drivers etc.

This is only happening in sonar though, even after a total reinstall of
everything.

Anyone have any explanations or further suggestions?

This happens with both JSonar and the latest version of ct.  I've tried
both.

Thanks,

Cameron.


_______________________________________________
Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org.

Jsonar mailing list
[email protected]
http://jsonar.org/mailman/listinfo/jsonar_jsonar.org


_______________________________________________
Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org.

Jsonar mailing list
[email protected]
http://jsonar.org/mailman/listinfo/jsonar_jsonar.org

Reply via email to