In my unhumble opinion, stick with 3.2 for now.

As to your authorization problem, if this is a new SMA for you, you
should also have received a file named JFW plus your serial number
plus .ATH which you need to copy to a floppy for when Dr. JAWS gets to
the authorization update section.  I feel this is a flaw in the JFW
installation--the .ATH file should be able to be located anywhere on
your system, and Dr. JAWS should be able to find it by itself.

As for not knowing where your authorization disk is, in JFW 2.0 and
3.0, it was a separate disk with the braille label reading
"authorization disk".  I don't know how it was labeled in print, if at
all.  But if you're still running on the key you got with 2.0, I'd be
extremely surprised if that key still worked and didn't need either
replacing or updating with a .ATH file.

Ho0pe this helps.

On Sun, 06 Jun 1999 13:25:09 -0700, you wrote:

>I have gone from JFW 2.00.29 to 3.0 to 3.2 and I am now holding the
disk
>for 3.3.  I have watched the list and read some of the problems, and
>frankly I am wondering if I should install 3.3 when my 3.2 on W95 is
>working fine.  Update to JFW never seems to go smoothly for me,
especially
>when it comes to wanting more than a key click.  My wife and I
started to
>install 3.3 and Dr. Jaws talked his way through and all seemed fine
until
>we got to the authorization key area.  I have no idea where that disk
might
>be nor do I know how it is labeled by HJ-- it is not labeled
"authorization
>disk".  My wife ran 3.3 and the first thing I noted was that my 3.2
>settings did not merge. What have I done wrong?  Why, as a subscriber
with
>an SMA isn't the update disk set to work with my serial number.
Again, as
>a happy 3.2 camper, what does 3.3 give me that is better?  Is i/e 5
really
>better than 4.01?  Sorry if these are simple questions, but I am a
turn-key
>guy who does not have time to fix little problems.  Thanks for any
suggestions!
>David
>
>[EMAIL PROTECTED]
>Office (619) 531-3020

-
Visit the jfw ml web page: http://jfw.cjb.net

Reply via email to