[Athen] authorization conflict between JFW and WYNN

Baker, Nick Nick.Baker at mso.umt.edu
Tue May 23 13:15:56 PDT 2006


James--
We have a multiple-seat site license for WYNN, which we
authorize locally via a serial number.
For our multiple-seat JAWS license, we have a block of authorization
codes, which we enter into the FS authorization web site for each
machine.

Nick Baker
Assistive Technology Coordinator
nick.baker at umontana.edu
406-243-2234 (Voice/TTY)
406-243-2663 (Voice only)

Disability Services for Students
The University of Montana
EL 154
32 Campus Drive
Missoula, MT 59812

-----Original Message-----
From: athen-bounces at athenpro.org [mailto:athen-bounces at athenpro.org] On
Behalf Of James Bailey
Sent: Tuesday, May 23, 2006 1:19 PM
To: Access Technologists in Higher Education Network
Subject: Re: [Athen] authorization conflict between JFW and WYNN

Thanks, Nick. Can you briefly decribe how the two programs get
authorized?
There seems to be mutiple ways to authorize these two products and my
suspicion is that the two (very different) schemes are in conflict. So,
were both WYNN and JFW locally authorized or do they both look to a
server
or is it a combo? Again, thanks for helping me sort this out.

James Bailey
Adaptive Technology Access Adviser, University of Oregon
1299 University of Oregon
Eugene, OR 97403-1299
Office: 541-346-1076
jbailey at darkwing.uoregon.edu

On Tue, 23 May 2006, Baker, Nick wrote:


> I have many machines with both JAWS and WYNN 4.0 and have never had a

> problem.

> Nick

>

> Nick Baker

> Assistive Technology Coordinator

> nick.baker at umontana.edu

> 406-243-2234 (Voice/TTY)

> 406-243-2663 (Voice only)

>

> Disability Services for Students

> The University of Montana

> EL 154

> 32 Campus Drive

> Missoula, MT 59812

> -----Original Message-----

> From: athen-bounces at athenpro.org [mailto:athen-bounces at athenpro.org]

On

> Behalf Of James Bailey

> Sent: Monday, May 22, 2006 11:07 AM

> To: Access Technologists in Higher Education Network

> Subject: [Athen] authorization conflict between JFW and WYNN

>

> I have discovered what may be a conflict between WYNN 4.0 and JFW 7.0

> authorization schemes. I tried to install a single user version of

WYNN

> 4.0 on a machine that has JFW 7.0 on it. The JFW get its

authorization

> from a server. In every other respect this JFW is handled as a local

> set-up, it just gets authorization from a server.

>

> I could not successfully "activate" the WYNN set-up. When one of the

> WYNN

> error messages mentioned the JFW authorization server by name, I

became

> highly suspicious. Three separate calls to FS help got the same

> response,

> "the two authorizations schemes will ignore each other."

>

> Finally, I commented out the JFW authorization by changing the name of

> the

> environmental variable, and (you know what's coming) WYNN started up

> just

> fine. Of course now JFW starts in the demo mode not being able to

> access

> the authorization.

>

> Has anyone else encountered and resolved this issue?

>

> - Thanks, James

>

> James Bailey

> Adaptive Technology Access Adviser, University of Oregon

> 1299 University of Oregon

> Eugene, OR 97403-1299

> Office: 541-346-1076

> jbailey at darkwing.uoregon.edu

>

>

> _______________________________________________

> Athen mailing list

> Athen at athenpro.org

> http://athenpro.org/mailman/listinfo/athen_athenpro.org

>

> _______________________________________________

> Athen mailing list

> Athen at athenpro.org

> http://athenpro.org/mailman/listinfo/athen_athenpro.org

>


_______________________________________________
Athen mailing list
Athen at athenpro.org
http://athenpro.org/mailman/listinfo/athen_athenpro.org




More information about the athen-list mailing list