[Jsonar] Control surface problem with JSonar 7.1, Sonar 7.02 and Windows Vista SP 1

[Brian Olesen]

hi,
no no no.
please downgrade to windows 3.1. lol

What about a serious advice?

Brian
----- Original Message ----- 
From: "Phil Muir" <philmuir1 at hotmail.com>
To: "JSonar -- JAWS Scripts for Sonar list" <jsonar at jsonar.org>
Sent: Thursday, October 09, 2008 7:28 PM
Subject: Re: [Jsonar] Control surface problem with JSonar 7.1,Sonar 7.02 and 
Windows Vista SP 1


> Get a downgrade to Windows XP.  Your system will run way faster under XP 
> anyway and everything will work as advertised.
>
> Regards, Phil Muir
>
> P J Muir Productions,
> Music And Audio Production
> Telephone: US (615) 713-2021
> UK+44-1747-821-794
> Mobile: UK +44-7968-136-246
> E-mail:
> info at philmuir.com
> URL:
> www.philmuir.com/
> ----- Original Message ----- 
> From: "Chris Nestrud" <ccn at panix.com>
> To: <jsonar at jsonar.org>
> Sent: Thursday, October 09, 2008 2:45 PM
> Subject: [Jsonar] Control surface problem with JSonar 7.1,Sonar 7.02 and 
> Windows Vista SP 1
>
>
>>
>> Hello list,
>>
>> I'm using JSonar 7.1 for Cakewalk Sonar 7.02 and Windows Vista SP 1
>> along with JFW 9.0.2169. The JSonar control surface is installed and
>> appears in the Controlers/Surfaces dialog. I have run through the
>> recommended configuration steps in the FAQ. However it looks like the
>> goJSonar object is not successfully created. The CreateObject statement
>> always returns false.
>>
>> Here's what I've already tried:
>>
>> I removed the JSonar control surface and recreated it, making sure that
>> both ports were set to none.
>> I then restarted Sonar. The goJSonar object was not created (the object
>> was still null immediately after the CreateObject statement in
>> sonarsrfutil.jsl). I next removed the entry for the surface that I had
>> created and restarted Sonar. Of course it asked to run the setup wizard
>> since the surface was not installed. I ran the wizard, then checked in
>> the control surface dialog and found that the surface had been added by
>> the JSonar scripts. The name was "JSonar Control Surface
>> - 1" and both ports were set to none. The goJSonar object was not
>>  successfully created.
>>
>> I'd appreciate any suggestions you may have, and
>> would be happy to provide any additional information that you think
>> might be helpful.
>>
>> Chris
>>
>>
>> _______________________________________________
>> Jsonar mailing list
>> Jsonar at jsonar.org
>> http://jsonar.org/mailman/listinfo/jsonar_jsonar.org
>>
>
>
> _______________________________________________
> Jsonar mailing list
> Jsonar at jsonar.org
> http://jsonar.org/mailman/listinfo/jsonar_jsonar.org