Re: Problem trying to repair Jaws 18 before upgrading to V 2018
removingshared components won’t affect your key.
Coming in a bit late on this, but what’ the error you’re getting?
Sent: Thursday, October 26, 2017 5:11 AM
Subject: Re: Problem trying to repair Jaws 18 before upgrading to V 2018
Well… SO I first went back and clicked on the last October JFW .exe file I had and the prompt of Jaws made changes to your computer. Restart for changes to take affect etc. Came up. I thought… … … cool maybe it’ll work after all. The PC restarted and I got the notification to modify/repair of which I selected repair. I let it do its thing. Pressed the various OK buttons and after it restarted again… … … the same reply/forward bug appeared.
So I figured, I’ll go ahead and just install the new JFW 2018 released today and as was suggested, not migrate any settings. Did the whole song and dance. Restarted the machine. Went through the startup wizard and… … … Low-and-behold, I’ve got the reply/forward bug on this new JFW version as well.
This is the only real issue I’m encountering. And on this one machine. JFW 2018 on my HP Envy laptop is working perfectly fine. At least not getting that reply/forward bug on it. Unfortunately, this is a rather noticeable bug and present on my main work desktop. Both running Office 2016/Windows 10.
I guess I’ll have to try uninstalling and reinstalling next. That will have to be with more time though.
I think someone on one of these lists said to also try removing shared components. I don’t think I want to do that… I don’t recall at the moment, but does removing shared components mean you’ll then need an activation key? I’m fairly certain that I’m currently at zero keys.
Anyway, something to worry about for tomorrow.
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of Sieghard Weitzel
Why not just install Jaws 2018, I would say at this point to set it up from scratch and not merge your settings when asked just so you get the best possible experience which is not effected by possibly some problem in your user settings.
Jaws 2018 does not require you to repair Jaws 18, in fact you could completely uninstall Jaws 18 and it would make no difference to Jaws 2018.
[mailto:email@example.com] On Behalf Of Cristóbal
So, I’ve been dealing with this issue since Jaws 18 was put out on 9/26/17. Along with the Outlook address thing that later got fixed, I was having trouble when replying or forwarding message in Outlook. Arrowing down was not possible. Jaws would behave as though I was at the bottom of the screen. Even if I arrowed up once and then tried going back down to the line I was previously at, I’d encounter that same barrier. Navigating the message body of text with the read by paragraph or sentence commands, Jaws worked as always. It was just the read/navigate by line that was giving me problems.
VFO tech support emailed me instructing that I should try doing a Jaws repair. Do the copy path from my JFW .exe file and add the / type repair at the end in the run dialog box.
As I saw that Jaws 2018 came out today, I figured I’d try to get this resolved. I for one reason or another hadn’t had the chance to go through with the repair, but figured I should try addressing it before upgrading to JFW 2018.
In any event, I went through the repair process earlier today and along with all the other typical Jaws chatter when doing an installation (I was using a JFW.exe file from October that addressed the Outlook issue), I heard Jaws say something about a sentinel system driver not being copied. By the end of the process I then got the following error message:
The JAWS setup package could not install the required component
JAWSRepair. The process will now exit.
I already wrote VFO back about this, but as it’s Jaws 2018 release day, I don’t expect a follow up any time soon as I’m sure they’ll be dealing with all sorts of stuff related to that.
Anyone have an idea on what this is or how to fix it?