Re: Windows 7 32 bit or 64 bit
Lisle, Ted (CHFS DMS)
Interestingly, my choice of a 64-bit machine and a 32-bit OS had no sidetoggle quoted messageShow quoted text
effects at all. XP Media Center ran flawlessly, as did everything from
JAWS 7-10, and upgrading to Office 2007 proved to be a good move. Only
with 11 did problems occur. If you've been around a while, you heard
the tragic story of JAWS 11-12 and Access, so we won't go there anymore.
Suffice it to say 10 was the last XP-friendly edition, so that's where
I'm staying for now.
[mailto:email@example.com] On Behalf Of Richard Holloway
Sent: Monday, August 01, 2011 12:39 PM
To: The Jaws for Windows support list.
Subject: Re: Windows 7 32 bit or 64 bit
2006 sounds about like the right timeframe. I may have mentioned the
wrong NFB convention, it could have been Atlanta. It was going back-and
forth between Atlanta and Dallas back then.
It was a real nightmare for those of us to which it happened, and the
people at Freedom were disappointingly unconcerned about solving the
problem on their end. I do not exaggerate when I tell you they said "we
have no plans to support 64-bit hardware", and they made it clear they
meant with JAWS 9 or any future releases. Obviously, they got past their
hesitation, but it would have been quite a wait to get a 64-bit version
of JAWS back then; a year or more, I suppose.
It isn't like this hasn't happened before with similar migrations from
8-bit to 16-bit to 32-bit, and with all of the other major changes like
drive access limitations, RAM limits, etc., but maybe that was the first
time it happened with a Freedom Product? Vista had just come out and
there were like 6 different versions of that as well, so there was much
confusion in the marketplace. Actually, I think Vista came out in
January of 2007, so I expect this was Summer 2007.
We had already ordered a PAC Mate so there would be seamless use of JAWS
on both platforms and so we could use the braille display from the PAC
Mate on the computer, etc., so we were feeling awfully committed to this
financially and then all of the mis-info began to catch up with us. Had
we just spent that many thousands of dollars for a solution that was
effectively "broken" before it even arrived at our home?
All I know was I was a sighted and rather braille-needs-clueless parent
of a blind child, just coming of age to start having computer needs and
it turned into a really expensive and time-consuming fiasco. I've dealt
with computers professionally for over 20 years now, but in this
situation I was entirely at their mercy-- basically the only game on
town (or the only real "player"), especially based on what was available
and the information we had back then.
My level of concern is probably less warranted with today's technology
situation, but it is hard not to advise others to be really careful
about assuming it is a simple as tossing something into a special folder
and the problem will solve itself.
Richard Holloway, Vice President
Georgia Organization of Parents of Blind Children
On Aug 1, 2011, at 12:03 PM, Lisle, Ted wrote:
I guess it all worked out. I'd have been royally hacked if I'd boughta
64-bit OS, only to find I couldn't use JAWS, which would have been theeasily
32-bit programs, and the other way around. Mostly that was due to thein
mind. Most of those issues have been worked out where they can be,with
the(specificallydata; literally 32 or 64 pieces of information at a time
athat many ones or zeros at a time-- that's what a "bit" is, a one or
theyzero in binary computing. Multiple bits comprise a byte. Enough bytesmakea "k", then megs, gigs, etc.)Applications
had<firstname.lastname@example.org>no intention of supporting 64 bit machines in the future. Once mostnewmachines started going 32 bit, they changed their tune a bit. (Punboth
Jfw mailing list