Re: Error 106

  • From: "Farfar Carlson" <dgcarlson@xxxxxxxxxxxxx>
  • To: <jfw@xxxxxxxxxxxxx>
  • Date: Mon, 8 Nov 2010 19:37:50 -0800

Gary,

I agree. Your suggestion of the physical hard drive volume number is great, 
since it's unique, and who ever changes that component very often? And of 
course JAWS is usually installed on that drive, so it actually is "married" 
to the drive, wherever it goes.

So that notion would support the idea of having JAWS on a removable drive 
that you could attach to any computer, to make it talk.

Gee...now I think I just discovered the thumb drive version of JAWS.

Dave
Created in the Audio Recording and Mixing Studios, San Jose, California


----- Original Message ----- 
From: "Gary King" <w4wkz@xxxxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Monday, November 08, 2010 17:04
Subject: Re: Error 106


It's always seemed to me that FS could have come up with a scheme that would
be based on a permanent component of a computer such as the processor or C
drive.  A scheme based on the sum of the components of a modern computer
isn't going to work well since these components are constantly changing.

Gary King
w4wkz@xxxxxxxxxxxxx

----- Original Message ----- 
From: "Farfar Carlson" <dgcarlson@xxxxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Monday, November 08, 2010 6:12 PM
Subject: Re: Error 106


> Tom,
>
> Good sleuthing. Too bad you had to burn a key to find out. You took one
> for
> the list, so to speak.
>
> Agree completely on the key insanity. There must be better ways for FS to
> verify that JAWS is running on just one computer.
>
> Dave
> Created in the Audio Recording and Mixing Studios, San Jose, California
>
>
> ----- Original Message ----- 
> From: "Tom Lange" <trlange@xxxxxxxxxxx>
> To: <jfw@xxxxxxxxxxxxx>
> Sent: Monday, November 08, 2010 14:17
> Subject: Error 106
>
>
> Hi,
> After following a thread regarding the mysterious error 6 or 106 over the
> weekend, I finally ran into the problem just a couple of hours ago, on my
> Toshiba Satellite A505-6040 laptop running Windows 7 Home Premium and JAWS
> version 12.
> I was cold booting the laptop, when it suddenly occured to me that I
> needed
> to plug in the Pearl camera so that I could use Open Book, so I plugged it
> into the USB port.  When the login screen came up, JAWS told me that it
> had
> been authorized for an older version and that I needed to update the
> authorization.  . When I attempted to do so, I told the activation routine
> to use the Internet, as I knew that my
> wi-fi was up by then. The client activator failed with an error 106.  My
> hunch was that I'd lost my last activation key, so I checked fsactivate
> and
> confirmed this.  This was subsequently verified during a call to FS tech
> support.
>
> So, if you're still experiencing that error 106 during activation, check
> to
> see if you have any keys left.  You probably don't.
>
> Also, I guess on some machines like my laptop, it's best to insert USB
> devices either before powering up the machine or after the bootup process
> completes, to keep JAWS from getting  confused about the hardware
> footprint.
> It ticks me off that questionable timing cost me a key.  Like I said last
> Friday, this whole key business is a pain, and I won't hesitate to give FS
> a
> hard time about it when the opportunity presents itself.  Surely I'm not
> the
> only one who hates this sort of stuff.
>
> Tom
>
>
> --
> 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
> Alternative archives located at:
> http://n2.nabble.com/JAWS-for-Windows-f2145279.html
>
> 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
> Alternative archives located at:
> http://n2.nabble.com/JAWS-for-Windows-f2145279.html
>
> 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
Alternative archives located at: 
http://n2.nabble.com/JAWS-for-Windows-f2145279.html

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
Alternative archives located at: 
http://n2.nabble.com/JAWS-for-Windows-f2145279.html

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: