[ddots-l] Re: Soliciting Your Help to Correct Erroneous JAWS Reactivation Request (JAWS Error 6) [cross-posted]

  • From: "James Murphy" <maestro_22@xxxxxxxxxxxxx>
  • To: <ddots-l@xxxxxxxxxxxxx>
  • Date: Sun, 10 Sep 2006 15:10:13 -0400

Yes Damon,  Yes I guess your right.
We understand.
  ----- Original Message ----- 
  From: Damon Fibraio 
  To: ddots-l@xxxxxxxxxxxxx 
  Sent: Sunday, September 10, 2006 3:06 PM
  Subject: [ddots-l] Re: Soliciting Your Help to Correct Erroneous JAWS 
Reactivation Request (JAWS Error 6) [cross-posted] 


  Maybe they can't fix the problem without acquiring the information to figure 
out where the problem is. And since I highly doubt the folks at Freedom have 
the equipment we have, then they have to get that information from us before 
they can fix the problem. Come on, now. If you want the problem solved, let's 
get the information freedom needs to track down the bug and squash it.



------------------------------------------------------------------------------
  From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of James Murphy
  Sent: Sunday, September 10, 2006 2:47 PM
  To: ddots-l@xxxxxxxxxxxxx
  Subject: [ddots-l] Re: Soliciting Your Help to Correct Erroneous JAWS 
Reactivation Request (JAWS Error 6) [cross-posted] 


  Yes who's going to keep doing these steps," everytime you have to add new 
hardware??  That's ridiculous.  Just tell Freedom to get on the ball a fix this 
annoying  issue!!!!  An that's that.
    ----- Original Message ----- 
    From: William R. McCann 
    To: ddots-l@xxxxxxxxxxxxx ; midimag@xxxxxxxxxxx 
    Cc: 'NFBnet Music Talk Mailing List' ; 'This is for discussing music and 
braille literacy' 
    Sent: Saturday, September 09, 2006 5:12 PM
    Subject: [ddots-l] Soliciting Your Help to Correct Erroneous JAWS 
Reactivation Request (JAWS Error 6) [cross-posted] 


    N. B. Only run the Test described below if you have JAWS for Windows 
version 6.x or 7.x installed. Otherwise, you might actually invalidate your 
JAWS authorization! If you have JAWS 5.10 installed as well as a newer version 
like 6.x or 7.x, then it is fine to run this utility. Even if you do have 
multiple versions of JAWS installed on your system, you will only need to run 
the test once for each audio hardware device. 


    Background Information




    The people at Freedom Scientific are working to eliminate a pesky error 
that can result when JAWS users connect a new audio or MIDI device to their PC. 
Some customers have received the JAWS "error 6" message after installing a new 
piece of hardware. This message tells them that they must reactivate their unit 
of JAWS. It seems to occur on start up whenever the USB or firewire device is 
powered on or off.




    We'd appreciate your help to find a resolution to this problem. If you have 
received this error 6 message please perform the following instructions. Your 
voluntary participation will facilitate the implementation of a resolution for 
this problem.




    Instructions for Running the Test Custom Lock Utility




    In the following instructions, the word "device" refers to any USB or 
Firewire device you use to create audio with SONAR, Sound Forge or other 
digital audio software.   




    1. If, and only if,  you are running JAWS 6.x or 7.x, go to the following 
link to download the Test Custom Lock utility from Freedom Scientific:

    www.DancingDots.com/ct/TestCustomLock.exe




    Take careful note of the name of the folder where you save this utility for 
reference in the instructions below.




    2. With your Device not connected, run TestCustomLock.exe. It will create 
the log file MachineInfo.san in the same folder in which you saved the 
TestCustomLock.exe utility.




    3. Connect the Device. Run TestCustomLock.exe a second time. 




    4. Disconnect the Device. Run TestCustomLock.exe a third time. 




    5. Send the MachineInfo.san file to: 

    waishanl@xxxxxxxxxxxxxxxxxxxxx

    as an E-mail attachment.




    If you have more than one device, please rename the log file created for 
your first device to MachineInfo_DeviceName1.  Now run the steps above for your 
second device. After this test, rename the log file to MachineInfo_devicename2 
and send all log files to address above.  Of course, substitute the actual name 
for each device in the file names.



    For example, if you own a Frontier TranzPort and an FW 1884, your files 
would be called:



    MachineInfo_TranzPort

    MachineInfo_FW1884




    Thank you for your assistance.




    Bill McCann

    Founder & President of Dancing Dots since 1992

    http://www.dancingdots.com/




    P. S. For details on the TranzPort see

    http://www.dancingdots.com/prodesc/tranzport.htm and for more information 
on the TASCAM FW 1884 go to

    http://www.dancingdots.com/prodesc/tascamfw1884.htm.


     

    Dancing Dots...Where music meets technology for the blind!
    Request the GOODFEEL 3 Braille Music Translator demo from: 
http://www.dancingdots.com/demodl.htm


    www.dancingdots.com
    E-mail: info@xxxxxxxxxxxxxxx

    1754 Quarry Lane
    PO Box 927
    Valley Forge, PA 19482-0927

    Tel: 610-783-6692
    Fax: 610-783-6732

Other related posts: