[jaws-uk] JAWS Error 6 Re-activation request - New Test Utility for JAWS Users who Work with MIDI and Audio Gear

If you have audio or MIDI equipment and JAWS 6 or 7, you
might be interested in the following.=20

The developers, Freedom Scientific, are trying, but while
they have plenty of complaints, good feedback is pretty
scant.

George.


        Dancing Dots and Freedom Scientific are asking any
JAWS user who has
encountered the JAWS Error 6 (reactivation request) after
adding a new piece
of audio or MIDI gear to their set up to perform the steps
below to provide
some real-world data to the developers at Freedom
Scientific.  The lady who
developed this test and who asked us to ask you to try it,
recently wrote to
me to say that she's had almost no response yet.  So,
please, take about 7
minutes and generate some data she can use.  Many thanks!

BTW, I'm resending text of a note I first sent on Sep. 9,
2006.  If you have
already responded to that note by sending in some test
results, no need to
do it again.

Also, you definitely do not need to have our CakeTalking
scripts installed
to participate.

Steps for Collecting Data=20

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
** To leave the list, click on the immediately-following link:-
** [mailto:jaws-uk-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** jaws-uk-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:jaws-uk-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to 
** jaws-uk-request@xxxxxxxxxxxxx with the Subject:- faq

Other related posts: