Re: removing authorization key, putting it back later

Then don't buy it and use window eyes then.  I don't like everything FS does 
either but I do it or I use window eyes. I choose to use JAWS.

Rick


=======

Visit my webpage at www.blind-geek-zone.net

Here you will find Audio tutorials for popular programs, blindness related 
web links, blind mailing list links and documents for various things.

----- Original Message ----- 
From: "John Heim" <jheim@xxxxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Tuesday, January 30, 2007 9:22 PM
Subject: Re: removing authorization key, putting it back later


I don't think I should have to payan additional $45 just to maintain an
authorization when I already paid $1000 for the license itself. JFW wants
*me* to pay because their authorization scheme is broken.  As a matter of
principle, that strikes me as unfair.

And before you say, "Well, that's the rules" -- Yes, I know that those are
the rules. I'm saying the rules are stupid and unfair. I don't like the
rules.  That is just my opinion.  But I think my opinion is well grounded in
facts. No other software company I know of demands anything even close to
this. I think FS is going to drive customers away with this scheme. They're
sure driving me away.

Not only is it a matter of principle, but there is a ton of paper work in
buying something around here.  And worse than that, I have to go to my boss
and my boss's boss and explain that once again I need them to buy me
something because I'm disabled. I know it's not a huge deal. They are
legally obligated to do it, after all. But it's embarrassing.

I'm tellin' ya, it just ain't right.









----- Original Message ----- 
From: "Joseph Lee" <joseph.lee22590@xxxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Tuesday, January 30, 2007 4:07 PM
Subject: Re: removing authorization key, putting it back later


> John,
> Then the best option is to get a dongle.
>
>> ----- Original Message -----
>>From: "John Heim" <jheim@xxxxxxxxxxxxx
>>To: <jfw@xxxxxxxxxxxxx
>>Date sent: Tue, 30 Jan 2007 16:01:07 -0600
>>Subject: Re: removing authorization key,
> putting it back later
>
>>Look, I've already said several times that I
> understand how it works.
>>Please stop explaining to me *why* it works
> the way it does.  That isn't
>>going to change my opinion.  First of all, I
> understand how it works.
>>Second, I don't care.
>
>>I don't care about the technical explanation.
> Why would I?The bottom line is
>>that I can't swap out my CD-ROM drive if it
> fails without phoning FS.
>
>>In my opinion, the authorization scheme shows
> a huge amount of arrogance on
>>the part of FS.  Either that or foolishness.
> I don't think they can afford to
>>anger their customers right about now.  Not
> with VoiceOver and orca
>>breathing down their necks (not to mention
> Windo-eyes).
>
>>Maybe this is OT for this list.  Is the
> future of JFW a valid topic? If so, I
>>am saying that I am not happy.  I have
> actively begun looking for
>>alternatives.  VoiceOver looks very
> promising.  I'd probably have switched by
>>now except it has one killer defect, it
> doesn't read the terminal window
>>text unless you use the cursor keys.  It's
> like you have to use the jaws
>>cursor and arrow around in the window.
> Several of us VO users have entered
>>bug reports with Apple about this.  I'm
> hoping it's fixed in the next release
>>of the MacOS.  If so, I'm outta here and FS
> has blown a $1000 re-licensing
>>fee.
>
>>Of course, they'd probably lose me as a
> customer anyway as soon as either
>>VoiceOver or orca get to be good enough to be
> used every day for real work.
>>Maybe they realize that and figure JFW has a
> limited life anyway.  That would
>>explain why they're so draconian about
> licensing.  Maybe they're trying to
>>get as much out of it as they can before it's
> obsolete.
>
>
>>----- Original Message -----
>>From: "Joseph Lee"
> <joseph.lee22590@xxxxxxxxxxxx
>>To: <jfw@xxxxxxxxxxxxx
>>Sent: Tuesday, January 30, 2007 3:16 PM
>>Subject: Re: removing authorization key,
> putting it back later
>
>
>>> John,
>>> Part of the auth code is the computer's
> hardware fingerprint.  This is
>>> crucial when activating JAWS.  If you
> chaarge a hardware (for example,
>>> CD-ROM or adding additional memory (which
> I've done), the next time JAWS
>>> starts, it will find that the hardware is
> different from what it is used
>>> to.  When you look at the locking code
> (hardware fingerprint), you'll
>>> notice that it has changed.  At that
> pointeay'll need to reactivate JAWS.
>>> Locate your Auth CD and activate your
> software.  If you remember your auth
>>> code (20 alph-numeric string), type it in
> the auth box.
>>> Cheers,
>>> Joseph
>
>>>> ----- Original Message -----
>>>>From: "John Heim" <jheim@xxxxxxxxxxxxx
>>>>To: <jfw@xxxxxxxxxxxxx
>>>>Date sent: Tue, 30 Jan 2007 10:49:23 -0600
>>>>Subject: Re: removing authorization key,
>>> putting it back later
>
>>>>I don't know which way is better.  A couple
>>> of weeks ago, my CD-ROM drive
>>>>died.  I swapped in a new one and lost my
>>> jaws authorization.  Now, that is
>>>>bogus.  Why in the world would I have to
>>> reauthorize a license for anything
>>>>just because I swapped out a CD-ROM drive?
>>> Oh, I know there is a good
>>>>*technical* explanation.  But from a customer
>>> service standpoint, that is
>>>>truly bogus.
>
>>>>When you pay $1000 for a piece of software,
>>> you expect better service than
>>>>that.
>
>>>>From: "Lisle, Ted (CHFS DMS)"
>>> <Ted.Lisle@xxxxxx
>>>>To: <jfw@xxxxxxxxxxxxx
>>>>Sent: Tuesday, January 30, 2007 6:58 AM
>>>>Subject: RE: removing authorization key,
>>> putting it back later
>
>
>>>>> This is really not as big a hassle as it
>>> seems.  In a lot of ways, ILM's
>>>>> are less trouble than their predecessors.
>>> You no longer have to worry
>>>>> about an optimization program trashing your
>>> key.  Furthermore, if you do
>>>>> need a fresh supply, getting replacements is
>>> far easier than it used to
>>>>> be.  The old process involved either reset
>>> codes, which did not always
>>>>> work, or waiting for a fresh disc to arrive.
>
>>>>> Ted
>
>>>>> -----Original Message-----
>>>>> From: jfw-bounce@xxxxxxxxxxxxx
>>> [mailto:jfw-bounce@xxxxxxxxxxxxx] On
>>>>> Behalf Of Leonard Salinas
>>>>> Sent: Tuesday, January 30, 2007 12:30 AM
>>>>> To: jfw@xxxxxxxxxxxxx
>>>>> Subject: re: removing authorization key,
>>> putting it back later
>
>
>>>>> not only that, if you change any hardware in
>>> your system the ilm
>>>>> authorization is render invalid.
>
>
>>>>> Legend has it that on Monday 1/29/2007 11:23
>>> PM, Joseph Lee said:
>>>>>>Patricia,
>>>>>>ILM is different from Quela authorization.
>>>>>>If you have Quela autherization (JAWS 5.1 or
>>> earlier), use HJAUTH
>>>>>>utility to save the auth key back to the
>>> diskette and install it
>>>>>>later.  With ILM, you can indeed remove auth
>>> code, but you cannot
>>>>>>install it later.
>>>>>>You'll need to activate it again (ILM looks
>>> for the hardware
>>>>>>fingerprint in order for it to work).  If the
>>> drive is changed (for
>>>>>>example, formatted), then it will ask you to
>>> reactivate it.
>>>>>>Cheers,
>>>>>>Joseph
>
>>>>>>>----- Original Message -----
>>>>>>>From: "Patricia" <bcsarah.fan@xxxxxxxxx
>>>>>>>To: <jfw@xxxxxxxxxxxxx
>>>>>>>Date sent: Mon, 29 Jan 2007 21:21:52 -0800
>>>>>>>Subject: removing authorization key, putting
>>>>>>it back later
>
>>>>>>>is there a way that you can remove your
>>>>>>authorization key (sauy for formatting your
>>> computer) and then
>>>>>>putting it back later so that you don't have
>>> to redo your keys
>>>>>>thereby losing another key? I don't see any
>>> way of doing this, and
>>>>>>am asking on a friend's behalf but I think
>>> that if there ins't a way
>>>>>>there should be because then people wouldn't
>>> have to constantly call
>>>>>>FS or fill out the form online.
>
>>>>>>>Patricia
>
>>>>>>>e-mail: bcsarah.fan@xxxxxxxxx
>>>>>>>msn: bc_sarah_fan@xxxxxxxxxxx
>>>>>>--
>>>>>>JFW related links:
>>>>>>JFW homepage:
>>> http://www.freedomscientific.com/
>>>>>>Scripting mailing list:
>>>>>>http://lists.the-jdh.com/listinfo.cgi/scripto
>>> graphy-the-jdh.com
>>>>>>JFW List instructions:
>>>>>>To post a message to the list, send it to
>>> jfw@xxxxxxxxxxxxx
>>>>>>To unsubscribe from this mailing list, send a
>>> message to
>>>>>>jfw-request@xxxxxxxxxxxxx with the word
>>> unsubscribe in the subject
>>>>> line.
>>>>>>Archives located at:
>>> http://www.freelists.org/archives/jfw
>
>>>>>>If you have any concerns about the list, post
>>> received from the
>>>>>>list, or the way the list is being run, do
>>> not post them to the
>>>>>>list.  Rather contact the list owner at
>>> jfw-admins@xxxxxxxxxxxxxx
>
>>>>> --
>>>>> JFW related links:
>>>>> JFW homepage:
>>> http://www.freedomscientific.com/
>>>>> Scripting mailing list:
>
>>>
> http://lists.the-jdh.com/listinfo.cgi/scripto
>>> graphy-the-jdh.com
>>>>> JFW List instructions:
>>>>> To post a message to the list, send it to
>>> jfw@xxxxxxxxxxxxx
>>>>> To unsubscribe from this mailing list, send
>>> a message to
>>>>> jfw-request@xxxxxxxxxxxxx with the word
>>> unsubscribe in the subject line.
>>>>> Archives located at:
>>> http://www.freelists.org/archives/jfw
>
>>>>> If you have any concerns about the list,
>>> post received from the list, or
>>>>> the way the list is being run, do not post
>>> them to the list.  Rather
>>>>> contact the list owner at
>>> jfw-admins@xxxxxxxxxxxxxx
>>>>> --
>>>>> JFW related links:
>>>>> JFW homepage:
>>> http://www.freedomscientific.com/
>>>>> Scripting mailing list:
>
>>>
> http://lists.the-jdh.com/listinfo.cgi/scripto
>>> graphy-the-jdh.com
>>>>> JFW List instructions:
>>>>> To post a message to the list, send it to
>>> jfw@xxxxxxxxxxxxx
>>>>> To unsubscribe from this mailing list, send
>>> a message to
>>>>> jfw-request@xxxxxxxxxxxxx with the word
>>> unsubscribe in the subject line.
>>>>> Archives located at:
>>> http://www.freelists.org/archives/jfw
>
>>>>> If you have any concerns about the list,
>>> post received from the list, or
>>>>> the way the list is being run, do not post
>>> them to the list.  Rather
>>>>> contact the list owner at
>>> jfw-admins@xxxxxxxxxxxxxx
>
>
>
>>>>--
>>>>JFW related links:
>>>>JFW homepage:
>>> http://www.freedomscientific.com/
>>>>Scripting mailing list:
>>>
> http://lists.the-jdh.com/listinfo.cgi/scripto
>>> graphy-the-jdh.com
>>>>JFW List instructions:
>>>>To post a message to the list, send it to
>>> jfw@xxxxxxxxxxxxx
>>>>To unsubscribe from this mailing list, send a
>>> message to jfw-request@xxxxxxxxxxxxx with
> the word unsubscribe in the
>>> subject line.
>>>>Archives located at:
>>> http://www.freelists.org/archives/jfw
>
>>>>If you have any concerns about the list, post
>>> received from the list, or the way the list
> is being run, do not post them
>>> to the list.  Rather contact the list owner
> at jfw-admins@xxxxxxxxxxxxxx
>>> --
>>> JFW related links:
>>> JFW homepage:
> http://www.freedomscientific.com/
>>> Scripting mailing list:
>>>
> http://lists.the-jdh.com/listinfo.cgi/scripto
> graphy-the-jdh.com
>>> JFW List instructions:
>>> To post a message to the list, send it to
> jfw@xxxxxxxxxxxxx
>>> To unsubscribe from this mailing list, send
> a message to
>>> jfw-request@xxxxxxxxxxxxx with the word
> unsubscribe in the subject line.
>>> Archives located at:
> http://www.freelists.org/archives/jfw
>
>>> If you have any concerns about the list,
> post received from the list, or
>>> the way the list is being run, do not post
> them to the list.  Rather
>>> contact the list owner at
> jfw-admins@xxxxxxxxxxxxxx
>
>
>
>>--
>>JFW related links:
>>JFW homepage:
> http://www.freedomscientific.com/
>>Scripting mailing list:
> http://lists.the-jdh.com/listinfo.cgi/scripto
> graphy-the-jdh.com
>>JFW List instructions:
>>To post a message to the list, send it to
> jfw@xxxxxxxxxxxxx
>>To unsubscribe from this mailing list, send a
> message to jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the
> subject line.
>>Archives located at:
> http://www.freelists.org/archives/jfw
>
>>If you have any concerns about the list, post
> received from the list, or the way the list is being run, do not post them
> to the list.  Rather contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> --
> JFW related links:
> JFW homepage: http://www.freedomscientific.com/
> Scripting mailing list:
> http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com
> JFW List instructions:
> To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> To unsubscribe from this mailing list, send a message to
> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
> Archives located at: http://www.freelists.org/archives/jfw
>
> If you have any concerns about the list, post received from the list, or
> the way the list is being run, do not post them to the list. Rather
> contact the list owner at jfw-admins@xxxxxxxxxxxxxx
>
>

--
JFW related links:
JFW homepage: http://www.freedomscientific.com/
Scripting mailing list: 
http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com
JFW List instructions:
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to 
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: http://www.freelists.org/archives/jfw

If you have any concerns about the list, post received from the list, or the 
way the list is being run, do not post them to the list. Rather contact the 
list owner at jfw-admins@xxxxxxxxxxxxxx 

--
JFW related links:
JFW homepage: http://www.freedomscientific.com/
Scripting mailing list: 
http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com
JFW List instructions:
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to 
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: http://www.freelists.org/archives/jfw

If you have any concerns about the list, post received from the list, or the 
way the list is being run, do not post them to the list. Rather contact the 
list owner at jfw-admins@xxxxxxxxxxxxxx

Other related posts: