Re: New JFW Update Coming This Afternoon

Now I have a question. Why didn't jaws4.51 count against your SMA?
Troy
----- Original Message ----- 
From: "Pickrell, Rebecca M." <rebecca.pickrell@xxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Friday, March 12, 2004 10:12 AM
Subject: RE: New JFW Update Coming This Afternoon


> I think of an update as needing to have the origional JFW 5.0 on your
> machine and a full upgrade as needing to not have it. I.E. a full version,
> you can install from scratch and once authorized, will run properly.
>
> Does that help any?
>
> -----Original Message-----
> From: Bruce Toews [mailto:coke_drinker@xxxxxxxx]
> Sent: Friday, March 12, 2004 10:08 AM
> To: 'jfw@xxxxxxxxxxxxx'
> Subject: RE: New JFW Update Coming This Afternoon
>
>
> I'm not sure how you're distinguishing the two. Sorry.
>
> Bruce
>
> -- 
> Bruce Toews
> E-Mail and MSN/Windows Messenger: coke_drinker@xxxxxxxx
> Web Site (including info on my weekly commentaries): http://www.ogts.net
> For the best oldies anywhere go to http://www.treasureislandoldies.com
>
> On Fri, 12 Mar 2004, Pickrell, Rebecca M. wrote:
>
> > Is this an update or a full upgrade?
> >
> > -----Original Message-----
> > From: Bruce Toews [mailto:coke_drinker@xxxxxxxx]
> > Sent: Thursday, March 11, 2004 12:59 PM
> > To: jfw@xxxxxxxxxxxxx
> > Subject: New JFW Update Coming This Afternoon
> >
> >
> > The following is from Eric at FS. The download link will be available on
> > the FS main page shortly.
> >
> > There will be a new version of JAWS posted this afternoon. The new
version
> > is 5.00.844.
> >
> > Fixes since the JAWS 5.00.812 February update.
> >
> > Since posting the 5.00.812 February Update, it was discovered that while
> > installation with other DCM products was working as designed, there were
> > other interoperability issues that in some cases caused system
instability
> > if JAWS 5.00.812 was installed and run on a computer with other Vendors
> > products. As a result of Dolphin support informing us, we have made the
> > minor adjustments and tested this latest March update of JAWS and the
new
> > MAGic 9.0 update with the other DCM products installed with no such
> > instability issues.
> >
> > Our testing did uncover one problem that still remains (and did so in
the
> > 5.0 release last October as well). If JAWS and SuperNova are both
> installed
> > on a W2K or Windows XP machine, use of the JAWS cursor may cause text to
> no
> > longer properly read. This does not require SuperNova be running, just
> > installed. We will be working closely with Dolphin during the next two
> > months to resolve this issue as soon as possible.
> >
> > As always, we suggest that you use caution when installing multiple
> > accessibility products from various manufacturers on the same system.
> >
> > DCM or not, you should always consult with those manufacturers prior to
> > installing to determine what testing may have been done.
> >
> > While resolving the incompatibility issues with the other products, we
> > continued to make fixes in JAWS and have included these fixes as part of
> > this free update for all JAWS 5.0 customers.
> >
> > The fixes include:
> >
> > * We resolved some long standing issues regarding disappearing
> >
> > text, especially in Microsoft Word 2000, XP, and 2003. Anyone using MS
> Word
> > should notice significant improvements in this area.
> >
> > * Fixed a Braille issue of display not updating too include cursor
> >
> > when typing past the end of the display with the Configuration Manager
> > setting of Positioning Mode set to Fixed Positioning.
> >
> > * Fixed a reported crash on
> >
> >  <http://www.minidisc.org/equipment_browser.html>
> > http://www.minidisc.org/equipment_browser.html
> >
> > < <http://www.minidisc.org/equipment_browser.html>
> > http://www.minidisc.org/equipment_browser.html> when navigating by
> > paragraph.
> >
> > * Fixed a problem found in Triple Talk and other synthesizers that
> >
> > may use a 0 as a rate or pitch. This fix should allow users to now hear
> the
> > pitch change for capital letter indications. There is still an issue for
> > Triple Talk PCI if its global pitch is set to 0. Setting it to 1 will
> > resolve that problem.
> >
> > * Fixed a minor problem reported when JAWS with Braille and MAGic
> >
> > were run together. The error was an unknown function call when shutting
> down
> > MAGic.
> >
> > * Fixed a problem when doing a Spell Line (SayLine command pressed
> >
> > twice quickly) on a line that includes punctuation, such as an email
> address
> > or web address. Spelling Speech Rate would speed up once you encountered
> the
> > punctuation on the line. This is now working as expected.
> >
> > * In Adobe Reader, fixed K and Shift K commands so they now
> >
> > properly navigate to any JAWS PlaceMarkers you may have created for your
> PDF
> > document.
> >
> > * Added updated Scripts for AOL Instant Messenger (AIM) 5.5.
> >
> > * Resolved issue on International Operating Systems where trying
> >
> > to set up application specific individual voice settings was failing.
> >
> > * Fixed menu reading/navigating problems reported in Java
> >
> > Applications.
> >
> > * Fixed space bar, toggle on and off script for WinAmp.
> >
> > * Fixed a reported issue in MS Word where the SayLine command
> >
> > would fail if the file name included the word "Customize".
> >
> > * Fixed reported issues of text failing to read correctly with the
> >
> > JAWS cursor on Web Pages that contain Flash.
> >
> > * Thanks to help from our creative and talented Private Beta
> >
> > Testers, we fixed a problem found in the scripts causing problems in MS
> > Power Point Presentations.
> >
> > End of fixes.
> >
> > We will be bringing hundreds of the new 5.00.844 version to CSUN and
> handing
> > it out to any JAWS 5.0 customer or Dealers that wish to get it for free.
> > Just stop by the FS booth and ask for a copy of the latest 5.0 Release,
> not
> > the demo version.
> >
> > Regards,
> >
> > Eric Damery
> >
> > JAWS Product Manager
> >
> >
> >
> > --
> > 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.
> >
> > 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
> > --
> > 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.
> >
> > 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
> >
> >
> --
> 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.
>
> 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
> --
> 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.
>
> 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
>
--
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.

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: