Re: removing authorization key, putting it back later

From: "Rick Harmon" <rharmon@xxxxxxxxxxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Date: Wed, 31 Jan 2007 13:16:40 -0500
Hi,

You most likely can backup your JAWS cd or ILM cd just like you can backup 
an Office or XP cd but this doesn't effect the ILM key on the pc.  There is 
a way to backup the ILM key but once you make a hardware change it really 
doesn't matter since your locking code will have changed making the key 
void.

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: "Sean McMahon" <smcmahon@xxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Wednesday, January 31, 2007 12:53 PM
Subject: Re: removing authorization key, putting it back later


hmm..  Just a thought, does the authorization scheme of fs and soon, vista,
violate the concept of fair use?  I'm not a legal person, but just 
wondering.
For example, if you've ever read a user lisence aggreement for MS Word it 
says
that you can make one backup coppy for personal use.  We can't effectibely 
do
this with Jaws.
----- Original Message ----- 
From: "Robert S. Batchelor" <leehigh73@xxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Tuesday, January 30, 2007 5:01 PM
Subject: RE: removing authorization key, putting it back later


>I can name one, now that you asked!
>
> VISTA  will be doing the very same thing....coming to a store near you 
> soon!
>
>
>
> ---------------------------------------------------------------------
> Eliminate annoying spam!
>
> My mailbox is protected by iHateSpam, the #1-rated spam buster.
> http://www.ihatespam.net
>
>
> -----Original Message-----
> From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf
> Of John Heim
> Sent: Tuesday, January 30, 2007 4:45 PM
> To: jfw@xxxxxxxxxxxxx
> Subject: Re: removing authorization key, putting it back later
>
> Geez! I already explained what is my problem with it.  It's damn
> inconvenient to have to get a new authorization code every time you do
> something as minor as swap out a CD-ROM drive oraa video card. That's
> ridiculous. No other piece of software that I know of requires anything 
> like
>
> that. And knowing about it doesn't make it any better. it's still stupid.
>
> You say you don't have a problem  with it. Why not? Can you tell me of 
> other
>
> licensed software that has such a draconian authorization scheme? Isn't 
> jaws
>
> authorization scheme *the* very worst? Can you name one that is worse?
>
> From: "Rick Harmon" <rharmon@xxxxxxxxxxxxxxxxxxx>
> To: <jfw@xxxxxxxxxxxxx>
> Sent: Tuesday, January 30, 2007 2:59 PM
> Subject: Re: removing authorization key, putting it back later
>
>
>> So what's the big deal??? You had to wait till the next morning?  FS
>> clearly
>> states if you have one ILM left you should call and have it reset.  FS
>> asks
>> no questions and I feel it's a acceptable practace for the most part.
>>
>> 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 3:51 PM
>> Subject: Re: removing authorization key, putting it back later
>>
>>
>> It was a Sunday night so I didn't get reauthorized until the next day.
>>
>> The real problem is that when stuff like this happens, it looks bad. It
>> makes me look like a burden to my  employer and it makes me angry with 
>> FS.
>> When something as simple as swapping out a CD-ROM drive becomes a 
>> half-day
>> ordeal, it makes me look incompetant. I shouldn't have to go through 
>> that.
>> Like a lot of techies, Monday morning is busy for me. It is unacceptable
>> for
>> my PC to be popping up messages saying I have to reboot in 3 minutes. 
>> I'm
>> supposed to be *fixing* computers, not struggling to keep my own working.
>>
>>
>>
>> ----- Original Message ----- 
>> From: "Lisle, Ted (CHFS DMS)" <Ted.Lisle@xxxxxx>
>> To: <jfw@xxxxxxxxxxxxx>
>> Sent: Tuesday, January 30, 2007 12:07 PM
>> Subject: RE: removing authorization key, putting it back later
>>
>>
>>> That is a bit much, although it's just a technicality. Did St.
>>> Petersburg have you up and running again quickly?
>>>
>>> Ted
>>>
>>> -----Original Message-----
>>> From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On
>>> Behalf Of John Heim
>>> Sent: Tuesday, January 30, 2007 11:49 AM
>>> To: jfw@xxxxxxxxxxxxx
>>> 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/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: //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: //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: //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: //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: //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: //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: //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: //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: //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: //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: //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
Follow-Ups:
- Re: removing authorization key, putting it back later
  - From: Sean M McMahon
References:
- RE: removing authorization key, putting it back later
  - From: Lisle, Ted \(CHFS DMS\)
- Re: removing authorization key, putting it back later
  - From: John Heim
- Re: removing authorization key, putting it back later
  - From: Rick Harmon
- Re: removing authorization key, putting it back later
  - From: John Heim
- RE: removing authorization key, putting it back later
  - From: Robert S. Batchelor
- Re: removing authorization key, putting it back later
  - From: Sean McMahon
Re: removing authorization key, putting it back later

Other related posts:
