BLIND-HAMS Archives

For blind ham radio operators

BLIND-HAMS@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lou Kolb <[log in to unmask]>
Reply To:
For blind ham radio operators <[log in to unmask]>
Date:
Mon, 22 Dec 2014 11:23:54 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (93 lines)
Good news, Tom! And thanks for publicizing FS's good job in this instance. 
Nice to hear positive stuff about tech support, for a change. 73. Lou 
WA3MIX
Lou Kolb
Voice-over Artist:
Radio/TV Ads, Video narrations
Messages On-hold:
www.loukolb.com
----- Original Message ----- 
From: "Tom Behler" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, December 22, 2014 11:02 AM
Subject: Off Topic: Jaws incorrect version Instalation Mystery Solved


> Hi, everyone.
>
>
>
> You may remember that last week, Jaws 13 inadvertently got installed on my
> new work laptop, instead of Jaws 16, which I thought would be directly
> installed from the Jaws 16 CD.
>
>
>
> It turns out that the fault was on this end, not with Freedom Scientific.
>
>
>
> Here's my analysis of what happened and why:
>
>
>
> Yesterday, I was nosing around on the desktop  of my new work laptop, and
> found an executable file for Jaws 13.  It was called j13.0.92   4 64 bit. 
> I
> checked the file properties, and the file was dated Monday: December 15 
> and
> was time stamped at 10:09 a.m.  This is significant, because this was the
> time when the University's I T people were in my office, and had 
> transferred
> a bunch of stuff from the hard drive of my old Windows 7 desktop to the 
> new
> work laptop.
>
>
>
> I think that what happened was this:  Since I had no visual assistance
> available when it came time to install Jaws 16, I used Windows narrator to
> find what I thought was the Jaws 16 instalation package on the Jaws 16 CD,
> and somehow ended up inadvertently choosing the Jaws 13 executable file.
>
>
>
> Apparently, I'm not very good at using Windows Narrator in situations like
> this, although I do find Narrator to not be as verbose as I would like. 
> In
> addition, it also would have been nice to have visual assistance around, 
> so
> that I wouldn't have had to use Windows Narrator to begin with, and could
> have gotten the correct file right from the new CD.
>
>
>
> The really frustrating part of all of this is that, even though I
> uninstalled Jaws 13 from the new laptop, and installed Jaws 16, something
> got corrupted with the install, and I had to spend quite a bit of time 
> late
> last week with FS Tech support to do a major Jaws repair.
>
>
>
> All and all, though, I think I'm now ok, and will certainly keep this in
> mind for the future.  I also have sent a rather strongly-worded e-mail to
> our IT folks, stressing the need for visual assistance with new adaptive
> technology instalations, and also stressing the need for IT people to let 
> us
> know what files they are transferring onto any new computer that we might
> use.
>
>
>
> In closing, I want to sincerely thank Ron Miller and the folks at Freedom
> Scientific for all of their help in working through this issue.  Ron, in
> particular, went above and beyond the call of duty to help me figure out
> what was going on, and that has been truly appreciated.
>
>
>
> Tom Behler: KB8TYJ
>
> 

ATOM RSS1 RSS2