Hello,
I'm trying to install NVDA on a new machine
running Windows 10 pro 1909.
I'm running the installation file as
administrator. I'm getting the message that installing NVDA has
failed.
Please also see the log included below.
Does anyone know what the problem might be
and how to solve it??
Thanks.
Cheers
Sandra
toggle quoted messageShow quoted text
INFO - __main__ (13:56:46.002) -
MainThread (10924):
Starting NVDA version 2019.3.1
INFO - core.main (13:56:46.082) - MainThread (10924):
Config dir: C:\Users\sandr\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (13:56:46.082) -
MainThread (10924):
Loading config: C:\Users\sandr\AppData\Roaming\nvda\nvda.ini
INFO - core.main (13:56:46.122) - MainThread (10924):
Using Windows version 10.0.18363 workstation
INFO - core.main (13:56:46.122) - MainThread (10924):
Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14
2019, 23:09:19) [MSC v.1916 32 bit (Intel)]
INFO - core.main (13:56:46.122) - MainThread (10924):
Using comtypes version 1.1.7
INFO - core.main (13:56:46.122) - MainThread (10924):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (13:56:46.402) - MainThread
(10924):
Loaded synthDriver oneCore
INFO - core.main (13:56:46.402) - MainThread (10924):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six
version 1.12.0
INFO - brailleInput.initialize (13:56:46.407) - MainThread
(10924):
Braille input initialized
INFO - braille.initialize (13:56:46.407) - MainThread (10924):
Using liblouis version 3.10.0
INFO - braille.initialize (13:56:46.407) - MainThread (10924):
Using pySerial version 3.4
INFO - braille.BrailleHandler.setDisplayByName (13:56:46.412)
- MainThread (10924):
Loaded braille display driver noBraille, current display has 0
cells.
INFO -
brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__
(13:56:46.464) - braille._BgThread (11016):
Found Easy Braille connected via hid
(\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
INFO - braille.BrailleHandler.setDisplayByName (13:56:46.472)
- braille._BgThread (11016):
Loaded braille display driver handyTech, current display has
40 cells.
INFO - core.main (13:56:46.582) - MainThread (10924):
Java Access Bridge support initialized
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:56:46.582) -
_UIAHandler.UIAHandler.MTAThread (11020):
UIAutomation: IUIAutomation6
INFO - core.main (13:56:46.762) - MainThread (10924):
NVDA initialized
ERROR - RPC process 8756 (nvda_slave.exe) (13:57:05.773) -
Dummy-1 (10840):
__main__.main:
slave error
Traceback (most recent call last):
File "nvda_slave.pyw", line 47, in main
File "installer.pyc", line 454, in install
File "installer.pyc", line 261, in registerInstallation
File "installer.pyc", line 58, in createShortcut
File "comtypes\client\lazybind.pyc", line 218, in
__setattr__
File "comtypes\automation.pyc", line 729, in _invoke
_ctypes.COMError: (-2147352567, 'Ausnahmefehler aufgetreten.',
(None, None, None, 0, None))
ERROR - gui.installerGui.doInstall (13:57:05.793) - MainThread
(10924):
Installation failed: 1
|
|
Hello Sandra, the installation failed because NVDA was unable to create its desktop shortcut, for reasons I cannot begin to guess. I can think of two options: 1. Install without creating a desktop shortcut, then create one manually. 2. Sometimes, switching the NVDA language to English before installing fixes this problem. If you feel comfortable doing this, it may be the cleaner option. Hope this helps, Felix
Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra Pilz <sandra914481@gmail.com>:
toggle quoted messageShow quoted text
Hello,
I'm trying to install NVDA on a new machine running Windows 10 pro 1909.
I'm running the installation file as administrator. I'm getting the message that installing NVDA has failed.
Please also see the log included below.
Does anyone know what the problem might be and how to solve it??
Thanks.
Cheers
Sandra
INFO - __main__ (13:56:46.002) - MainThread (10924): Starting NVDA version 2019.3.1 INFO - core.main (13:56:46.082) - MainThread (10924): Config dir: C:\Users\sandr\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (13:56:46.082) - MainThread (10924): Loading config: C:\Users\sandr\AppData\Roaming\nvda\nvda.ini INFO - core.main (13:56:46.122) - MainThread (10924): Using Windows version 10.0.18363 workstation INFO - core.main (13:56:46.122) - MainThread (10924): Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)] INFO - core.main (13:56:46.122) - MainThread (10924): Using comtypes version 1.1.7 INFO - core.main (13:56:46.122) - MainThread (10924): Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (13:56:46.402) - MainThread (10924): Loaded synthDriver oneCore INFO - core.main (13:56:46.402) - MainThread (10924): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0 INFO - brailleInput.initialize (13:56:46.407) - MainThread (10924): Braille input initialized INFO - braille.initialize (13:56:46.407) - MainThread (10924): Using liblouis version 3.10.0 INFO - braille.initialize (13:56:46.407) - MainThread (10924): Using pySerial version 3.4 INFO - braille.BrailleHandler.setDisplayByName (13:56:46.412) - MainThread (10924): Loaded braille display driver noBraille, current display has 0 cells. INFO - brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__ (13:56:46.464) - braille._BgThread (11016): Found Easy Braille connected via hid (\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) INFO - braille.BrailleHandler.setDisplayByName (13:56:46.472) - braille._BgThread (11016): Loaded braille display driver handyTech, current display has 40 cells. INFO - core.main (13:56:46.582) - MainThread (10924): Java Access Bridge support initialized INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:56:46.582) - _UIAHandler.UIAHandler.MTAThread (11020): UIAutomation: IUIAutomation6 INFO - core.main (13:56:46.762) - MainThread (10924): NVDA initialized ERROR - RPC process 8756 (nvda_slave.exe) (13:57:05.773) - Dummy-1 (10840): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw", line 47, in main File "installer.pyc", line 454, in install File "installer.pyc", line 261, in registerInstallation File "installer.pyc", line 58, in createShortcut File "comtypes\client\lazybind.pyc", line 218, in __setattr__ File "comtypes\automation.pyc", line 729, in _invoke _ctypes.COMError: (-2147352567, 'Ausnahmefehler aufgetreten.', (None, None, None, 0, None)) ERROR - gui.installerGui.doInstall (13:57:05.793) - MainThread (10924): Installation failed: 1
|
|
Hi Felix,
Thanks for your help. Unfortunately setting the NVDA language to English didn't help. The failed installation not only faild to create the desktop shortcut, but also didn't create NVDA entries in the start menu. I installed NVDA 2019.1 first and then updated to 2019.3.1, that did the trick.
Best
Sandra
Am 04.03.2020 um 13:22 schrieb Felix G.:
toggle quoted messageShow quoted text
Hello Sandra, the installation failed because NVDA was unable to create its desktop shortcut, for reasons I cannot begin to guess. I can think of two options: 1. Install without creating a desktop shortcut, then create one manually. 2. Sometimes, switching the NVDA language to English before installing fixes this problem. If you feel comfortable doing this, it may be the cleaner option. Hope this helps, Felix
Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra Pilz <sandra914481@gmail.com>:
Hello,
I'm trying to install NVDA on a new machine running Windows 10 pro 1909.
I'm running the installation file as administrator. I'm getting the message that installing NVDA has failed.
Please also see the log included below.
Does anyone know what the problem might be and how to solve it??
Thanks.
Cheers
Sandra
INFO - __main__ (13:56:46.002) - MainThread (10924): Starting NVDA version 2019.3.1 INFO - core.main (13:56:46.082) - MainThread (10924): Config dir: C:\Users\sandr\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (13:56:46.082) - MainThread (10924): Loading config: C:\Users\sandr\AppData\Roaming\nvda\nvda.ini INFO - core.main (13:56:46.122) - MainThread (10924): Using Windows version 10.0.18363 workstation INFO - core.main (13:56:46.122) - MainThread (10924): Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)] INFO - core.main (13:56:46.122) - MainThread (10924): Using comtypes version 1.1.7 INFO - core.main (13:56:46.122) - MainThread (10924): Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (13:56:46.402) - MainThread (10924): Loaded synthDriver oneCore INFO - core.main (13:56:46.402) - MainThread (10924): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0 INFO - brailleInput.initialize (13:56:46.407) - MainThread (10924): Braille input initialized INFO - braille.initialize (13:56:46.407) - MainThread (10924): Using liblouis version 3.10.0 INFO - braille.initialize (13:56:46.407) - MainThread (10924): Using pySerial version 3.4 INFO - braille.BrailleHandler.setDisplayByName (13:56:46.412) - MainThread (10924): Loaded braille display driver noBraille, current display has 0 cells. INFO - brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__ (13:56:46.464) - braille._BgThread (11016): Found Easy Braille connected via hid (\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) INFO - braille.BrailleHandler.setDisplayByName (13:56:46.472) - braille._BgThread (11016): Loaded braille display driver handyTech, current display has 40 cells. INFO - core.main (13:56:46.582) - MainThread (10924): Java Access Bridge support initialized INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:56:46.582) - _UIAHandler.UIAHandler.MTAThread (11020): UIAutomation: IUIAutomation6 INFO - core.main (13:56:46.762) - MainThread (10924): NVDA initialized ERROR - RPC process 8756 (nvda_slave.exe) (13:57:05.773) - Dummy-1 (10840): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw", line 47, in main File "installer.pyc", line 454, in install File "installer.pyc", line 261, in registerInstallation File "installer.pyc", line 58, in createShortcut File "comtypes\client\lazybind.pyc", line 218, in __setattr__ File "comtypes\automation.pyc", line 729, in _invoke _ctypes.COMError: (-2147352567, 'Ausnahmefehler aufgetreten.', (None, None, None, 0, None)) ERROR - gui.installerGui.doInstall (13:57:05.793) - MainThread (10924): Installation failed: 1
|
|
When you originally went to install, did you get the UAC prompt from Windows itself about installing the program? You get that for any program you install, but sometimes it pops up and doesn't get focus so you aren't alerted to it and even visually it's not obvious. If you don't answer Yes to the UAC prompt within about 20 seconds, it times out and denies the program from installing.
The only other thing I was thinking was if you had controlled folder access set, it will install NVDA but not create the desktop shortcut. If that was the issue though, it wouldn't have worked any better with NVDA 2019.1 than 2019.3.
Regards
Quentin.
toggle quoted messageShow quoted text
Hi Felix,
Thanks for your help. Unfortunately setting the NVDA language to English
didn't help. The failed installation not only faild to create the
desktop shortcut, but also didn't create NVDA entries in the start menu.
I installed NVDA 2019.1 first and then updated to 2019.3.1, that did the
trick.
Best
Sandra
Am 04.03.2020 um 13:22 schrieb Felix G.:
> Hello Sandra,
> the installation failed because NVDA was unable to create its desktop
> shortcut, for reasons I cannot begin to guess. I can think of two
> options:
> 1. Install without creating a desktop shortcut, then create one manually.
> 2. Sometimes, switching the NVDA language to English before installing
> fixes this problem. If you feel comfortable doing this, it may be the
> cleaner option.
> Hope this helps,
> Felix
>
> Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra Pilz <sandra914481@...>:
>> Hello,
>>
>>
>> I'm trying to install NVDA on a new machine running Windows 10 pro 1909.
>>
>>
>> I'm running the installation file as administrator. I'm getting the message that installing NVDA has failed.
>>
>>
>> Please also see the log included below.
>>
>>
>> Does anyone know what the problem might be and how to solve it??
>>
>>
>> Thanks.
>>
>>
>> Cheers
>>
>>
>> Sandra
>>
>>
>> INFO - __main__ (13:56:46.002) - MainThread (10924):
>> Starting NVDA version 2019.3.1
>> INFO - core.main (13:56:46.082) - MainThread (10924):
>> Config dir: C:\Users\sandr\AppData\Roaming\nvda
>> INFO - config.ConfigManager._loadConfig (13:56:46.082) - MainThread (10924):
>> Loading config: C:\Users\sandr\AppData\Roaming\nvda\nvda.ini
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using Windows version 10.0.18363 workstation
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using comtypes version 1.1.7
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using configobj version 5.1.0 with validate version 1.0.1
>> INFO - synthDriverHandler.setSynth (13:56:46.402) - MainThread (10924):
>> Loaded synthDriver oneCore
>> INFO - core.main (13:56:46.402) - MainThread (10924):
>> Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0
>> INFO - brailleInput.initialize (13:56:46.407) - MainThread (10924):
>> Braille input initialized
>> INFO - braille.initialize (13:56:46.407) - MainThread (10924):
>> Using liblouis version 3.10.0
>> INFO - braille.initialize (13:56:46.407) - MainThread (10924):
>> Using pySerial version 3.4
>> INFO - braille.BrailleHandler.setDisplayByName (13:56:46.412) - MainThread (10924):
>> Loaded braille display driver noBraille, current display has 0 cells.
>> INFO - brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__ (13:56:46.464) - braille._BgThread (11016):
>> Found Easy Braille connected via hid (\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
>> INFO - braille.BrailleHandler.setDisplayByName (13:56:46.472) - braille._BgThread (11016):
>> Loaded braille display driver handyTech, current display has 40 cells.
>> INFO - core.main (13:56:46.582) - MainThread (10924):
>> Java Access Bridge support initialized
>> INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:56:46.582) - _UIAHandler.UIAHandler.MTAThread (11020):
>> UIAutomation: IUIAutomation6
>> INFO - core.main (13:56:46.762) - MainThread (10924):
>> NVDA initialized
>> ERROR - RPC process 8756 (nvda_slave.exe) (13:57:05.773) - Dummy-1 (10840):
>> __main__.main:
>> slave error
>> Traceback (most recent call last):
>> File "nvda_slave.pyw", line 47, in main
>> File "installer.pyc", line 454, in install
>> File "installer.pyc", line 261, in registerInstallation
>> File "installer.pyc", line 58, in createShortcut
>> File "comtypes\client\lazybind.pyc", line 218, in __setattr__
>> File "comtypes\automation.pyc", line 729, in _invoke
>> _ctypes.COMError: (-2147352567, 'Ausnahmefehler aufgetreten.', (None, None, None, 0, None))
>> ERROR - gui.installerGui.doInstall (13:57:05.793) - MainThread (10924):
>> Installation failed: 1
>>
>>
>>
>
>
-- Quentin Christensen Training and Support Manager
|
|
Hi. I would like to add something about the UAC prompt on windows from 7 and up I think. When the UAC prompt appears, focus is on the no button. By pressing enter or space without tapping around first, people just activate the no button and the installation cannot be completed.
I saw many people just pressing enter all the time during installation without exploring the dialogues first. Usually the enter activates the next button but not on the UAC prompt.
Also the shortcut alt+Y works on the UAC prompt for activating the yes button. Nikos
toggle quoted messageShow quoted text
On Thu, 5 Mar 2020 at 07:20, Quentin Christensen < quentin@...> wrote: When you originally went to install, did you get the UAC prompt from Windows itself about installing the program? You get that for any program you install, but sometimes it pops up and doesn't get focus so you aren't alerted to it and even visually it's not obvious. If you don't answer Yes to the UAC prompt within about 20 seconds, it times out and denies the program from installing.
The only other thing I was thinking was if you had controlled folder access set, it will install NVDA but not create the desktop shortcut. If that was the issue though, it wouldn't have worked any better with NVDA 2019.1 than 2019.3.
Regards
Quentin.
Hi Felix,
Thanks for your help. Unfortunately setting the NVDA language to English
didn't help. The failed installation not only faild to create the
desktop shortcut, but also didn't create NVDA entries in the start menu.
I installed NVDA 2019.1 first and then updated to 2019.3.1, that did the
trick.
Best
Sandra
Am 04.03.2020 um 13:22 schrieb Felix G.:
> Hello Sandra,
> the installation failed because NVDA was unable to create its desktop
> shortcut, for reasons I cannot begin to guess. I can think of two
> options:
> 1. Install without creating a desktop shortcut, then create one manually.
> 2. Sometimes, switching the NVDA language to English before installing
> fixes this problem. If you feel comfortable doing this, it may be the
> cleaner option.
> Hope this helps,
> Felix
>
> Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra Pilz <sandra914481@...>:
>> Hello,
>>
>>
>> I'm trying to install NVDA on a new machine running Windows 10 pro 1909.
>>
>>
>> I'm running the installation file as administrator. I'm getting the message that installing NVDA has failed.
>>
>>
>> Please also see the log included below.
>>
>>
>> Does anyone know what the problem might be and how to solve it??
>>
>>
>> Thanks.
>>
>>
>> Cheers
>>
>>
>> Sandra
>>
>>
>> INFO - __main__ (13:56:46.002) - MainThread (10924):
>> Starting NVDA version 2019.3.1
>> INFO - core.main (13:56:46.082) - MainThread (10924):
>> Config dir: C:\Users\sandr\AppData\Roaming\nvda
>> INFO - config.ConfigManager._loadConfig (13:56:46.082) - MainThread (10924):
>> Loading config: C:\Users\sandr\AppData\Roaming\nvda\nvda.ini
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using Windows version 10.0.18363 workstation
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using comtypes version 1.1.7
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using configobj version 5.1.0 with validate version 1.0.1
>> INFO - synthDriverHandler.setSynth (13:56:46.402) - MainThread (10924):
>> Loaded synthDriver oneCore
>> INFO - core.main (13:56:46.402) - MainThread (10924):
>> Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0
>> INFO - brailleInput.initialize (13:56:46.407) - MainThread (10924):
>> Braille input initialized
>> INFO - braille.initialize (13:56:46.407) - MainThread (10924):
>> Using liblouis version 3.10.0
>> INFO - braille.initialize (13:56:46.407) - MainThread (10924):
>> Using pySerial version 3.4
>> INFO - braille.BrailleHandler.setDisplayByName (13:56:46.412) - MainThread (10924):
>> Loaded braille display driver noBraille, current display has 0 cells.
>> INFO - brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__ (13:56:46.464) - braille._BgThread (11016):
>> Found Easy Braille connected via hid (\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
>> INFO - braille.BrailleHandler.setDisplayByName (13:56:46.472) - braille._BgThread (11016):
>> Loaded braille display driver handyTech, current display has 40 cells.
>> INFO - core.main (13:56:46.582) - MainThread (10924):
>> Java Access Bridge support initialized
>> INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:56:46.582) - _UIAHandler.UIAHandler.MTAThread (11020):
>> UIAutomation: IUIAutomation6
>> INFO - core.main (13:56:46.762) - MainThread (10924):
>> NVDA initialized
>> ERROR - RPC process 8756 (nvda_slave.exe) (13:57:05.773) - Dummy-1 (10840):
>> __main__.main:
>> slave error
>> Traceback (most recent call last):
>> File "nvda_slave.pyw", line 47, in main
>> File "installer.pyc", line 454, in install
>> File "installer.pyc", line 261, in registerInstallation
>> File "installer.pyc", line 58, in createShortcut
>> File "comtypes\client\lazybind.pyc", line 218, in __setattr__
>> File "comtypes\automation.pyc", line 729, in _invoke
>> _ctypes.COMError: (-2147352567, 'Ausnahmefehler aufgetreten.', (None, None, None, 0, None))
>> ERROR - gui.installerGui.doInstall (13:57:05.793) - MainThread (10924):
>> Installation failed: 1
>>
>>
>>
>
>
--
Quentin Christensen Training and Support Manager
|
|
Hi Quentin,
You wrote:
When you originally went to install, did you get
the UAC prompt from Windows itself about installing the
program? You get that for any program you install, but
sometimes it pops up and doesn't get focus so you aren't alerted
to it and even visually it's not obvious. If you don't answer
Yes to the UAC prompt within about 20 seconds, it times out and
denies the program from installing.
Yes, I did see it, but the UAC prompt isn't the problem, I always
answer Yes using the alt Y or in my case alt+j shortcut (German
windows), and the installation continues. I don't wait for 20
seconds for something to happen.
The only other thing I was thinking was if you had
controlled folder access set, it will install NVDA but not
create the desktop shortcut. If that was the issue though, it
wouldn't have worked any better with NVDA 2019.1 than 2019.3.
No, I don't have controlled folder access set. I checked this
when it didn't work, because I knew it could be a problem. No,
it's not active.
I do think there is a problem with the installation of 2019.3
though, because a lady on the German NVDA list reported the same
problem. She's a very competent computer user and I'm sure she,
too, knows how to deal with UAC. Maybe it doesn't affect systems
where English is the default language... And maybe it wasn't
reported much, because many people using NVDA 2019.3 will have
updated an older version and won't have encountered this issue,
because the shortcut and start menu entries had already been
created by a previous installation of an older version of NVDA...
I, however, attempted a fresh install on a new machine.
Best
Sandra
Hi Felix,
Thanks for your help. Unfortunately setting the NVDA language
to English
didn't help. The failed installation not only faild to create
the
desktop shortcut, but also didn't create NVDA entries in the
start menu.
I installed NVDA 2019.1 first and then updated to 2019.3.1,
that did the
trick.
Best
Sandra
Am 04.03.2020 um 13:22 schrieb Felix G.:
> Hello Sandra,
> the installation failed because NVDA was unable to create
its desktop
> shortcut, for reasons I cannot begin to guess. I can
think of two
> options:
> 1. Install without creating a desktop shortcut, then
create one manually.
> 2. Sometimes, switching the NVDA language to English
before installing
> fixes this problem. If you feel comfortable doing this,
it may be the
> cleaner option.
> Hope this helps,
> Felix
>
> Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra Pilz
<sandra914481@...>:
>> Hello,
>>
>>
>> I'm trying to install NVDA on a new machine running
Windows 10 pro 1909.
>>
>>
>> I'm running the installation file as administrator.
I'm getting the message that installing NVDA has failed.
>>
>>
>> Please also see the log included below.
>>
>>
>> Does anyone know what the problem might be and how to
solve it??
>>
>>
>> Thanks.
>>
>>
>> Cheers
>>
>>
>> Sandra
>>
>>
>> INFO - __main__ (13:56:46.002) - MainThread (10924):
>> Starting NVDA version 2019.3.1
>> INFO - core.main (13:56:46.082) - MainThread (10924):
>> Config dir: C:\Users\sandr\AppData\Roaming\nvda
>> INFO - config.ConfigManager._loadConfig
(13:56:46.082) - MainThread (10924):
>> Loading config:
C:\Users\sandr\AppData\Roaming\nvda\nvda.ini
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using Windows version 10.0.18363 workstation
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b,
Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using comtypes version 1.1.7
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using configobj version 5.1.0 with validate version
1.0.1
>> INFO - synthDriverHandler.setSynth (13:56:46.402) -
MainThread (10924):
>> Loaded synthDriver oneCore
>> INFO - core.main (13:56:46.402) - MainThread (10924):
>> Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
with six version 1.12.0
>> INFO - brailleInput.initialize (13:56:46.407) -
MainThread (10924):
>> Braille input initialized
>> INFO - braille.initialize (13:56:46.407) - MainThread
(10924):
>> Using liblouis version 3.10.0
>> INFO - braille.initialize (13:56:46.407) - MainThread
(10924):
>> Using pySerial version 3.4
>> INFO - braille.BrailleHandler.setDisplayByName
(13:56:46.412) - MainThread (10924):
>> Loaded braille display driver noBraille, current
display has 0 cells.
>> INFO -
brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__
(13:56:46.464) - braille._BgThread (11016):
>> Found Easy Braille connected via hid
(\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
>> INFO - braille.BrailleHandler.setDisplayByName
(13:56:46.472) - braille._BgThread (11016):
>> Loaded braille display driver handyTech, current
display has 40 cells.
>> INFO - core.main (13:56:46.582) - MainThread (10924):
>> Java Access Bridge support initialized
>> INFO - _UIAHandler.UIAHandler.MTAThreadFunc
(13:56:46.582) - _UIAHandler.UIAHandler.MTAThread (11020):
>> UIAutomation: IUIAutomation6
>> INFO - core.main (13:56:46.762) - MainThread (10924):
>> NVDA initialized
>> ERROR - RPC process 8756 (nvda_slave.exe)
(13:57:05.773) - Dummy-1 (10840):
>> __main__.main:
>> slave error
>> Traceback (most recent call last):
>> File "nvda_slave.pyw", line 47, in main
>> File "installer.pyc", line 454, in install
>> File "installer.pyc", line 261, in
registerInstallation
>> File "installer.pyc", line 58, in createShortcut
>> File "comtypes\client\lazybind.pyc", line 218, in
__setattr__
>> File "comtypes\automation.pyc", line 729, in
_invoke
>> _ctypes.COMError: (-2147352567, 'Ausnahmefehler
aufgetreten.', (None, None, None, 0, None))
>> ERROR - gui.installerGui.doInstall (13:57:05.793) -
MainThread (10924):
>> Installation failed: 1
>>
>>
>>
>
>
--
Quentin
Christensen
Training and Support Manager
|
|
Hi Sandra,
Thanks for following up, I appreciate the clarification.
Setting my system language to German, I can replicate this. We'll look into it.
Quentin.
toggle quoted messageShow quoted text
Hi Quentin,
You wrote:
When you originally went to install, did you get
the UAC prompt from Windows itself about installing the
program? You get that for any program you install, but
sometimes it pops up and doesn't get focus so you aren't alerted
to it and even visually it's not obvious. If you don't answer
Yes to the UAC prompt within about 20 seconds, it times out and
denies the program from installing.
Yes, I did see it, but the UAC prompt isn't the problem, I always
answer Yes using the alt Y or in my case alt+j shortcut (German
windows), and the installation continues. I don't wait for 20
seconds for something to happen.
The only other thing I was thinking was if you had
controlled folder access set, it will install NVDA but not
create the desktop shortcut. If that was the issue though, it
wouldn't have worked any better with NVDA 2019.1 than 2019.3.
No, I don't have controlled folder access set. I checked this
when it didn't work, because I knew it could be a problem. No,
it's not active.
I do think there is a problem with the installation of 2019.3
though, because a lady on the German NVDA list reported the same
problem. She's a very competent computer user and I'm sure she,
too, knows how to deal with UAC. Maybe it doesn't affect systems
where English is the default language... And maybe it wasn't
reported much, because many people using NVDA 2019.3 will have
updated an older version and won't have encountered this issue,
because the shortcut and start menu entries had already been
created by a previous installation of an older version of NVDA...
I, however, attempted a fresh install on a new machine.
Best
Sandra
Hi Felix,
Thanks for your help. Unfortunately setting the NVDA language
to English
didn't help. The failed installation not only faild to create
the
desktop shortcut, but also didn't create NVDA entries in the
start menu.
I installed NVDA 2019.1 first and then updated to 2019.3.1,
that did the
trick.
Best
Sandra
Am 04.03.2020 um 13:22 schrieb Felix G.:
> Hello Sandra,
> the installation failed because NVDA was unable to create
its desktop
> shortcut, for reasons I cannot begin to guess. I can
think of two
> options:
> 1. Install without creating a desktop shortcut, then
create one manually.
> 2. Sometimes, switching the NVDA language to English
before installing
> fixes this problem. If you feel comfortable doing this,
it may be the
> cleaner option.
> Hope this helps,
> Felix
>
> Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra Pilz
<sandra914481@...>:
>> Hello,
>>
>>
>> I'm trying to install NVDA on a new machine running
Windows 10 pro 1909.
>>
>>
>> I'm running the installation file as administrator.
I'm getting the message that installing NVDA has failed.
>>
>>
>> Please also see the log included below.
>>
>>
>> Does anyone know what the problem might be and how to
solve it??
>>
>>
>> Thanks.
>>
>>
>> Cheers
>>
>>
>> Sandra
>>
>>
>> INFO - __main__ (13:56:46.002) - MainThread (10924):
>> Starting NVDA version 2019.3.1
>> INFO - core.main (13:56:46.082) - MainThread (10924):
>> Config dir: C:\Users\sandr\AppData\Roaming\nvda
>> INFO - config.ConfigManager._loadConfig
(13:56:46.082) - MainThread (10924):
>> Loading config:
C:\Users\sandr\AppData\Roaming\nvda\nvda.ini
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using Windows version 10.0.18363 workstation
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b,
Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using comtypes version 1.1.7
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using configobj version 5.1.0 with validate version
1.0.1
>> INFO - synthDriverHandler.setSynth (13:56:46.402) -
MainThread (10924):
>> Loaded synthDriver oneCore
>> INFO - core.main (13:56:46.402) - MainThread (10924):
>> Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
with six version 1.12.0
>> INFO - brailleInput.initialize (13:56:46.407) -
MainThread (10924):
>> Braille input initialized
>> INFO - braille.initialize (13:56:46.407) - MainThread
(10924):
>> Using liblouis version 3.10.0
>> INFO - braille.initialize (13:56:46.407) - MainThread
(10924):
>> Using pySerial version 3.4
>> INFO - braille.BrailleHandler.setDisplayByName
(13:56:46.412) - MainThread (10924):
>> Loaded braille display driver noBraille, current
display has 0 cells.
>> INFO -
brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__
(13:56:46.464) - braille._BgThread (11016):
>> Found Easy Braille connected via hid
(\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
>> INFO - braille.BrailleHandler.setDisplayByName
(13:56:46.472) - braille._BgThread (11016):
>> Loaded braille display driver handyTech, current
display has 40 cells.
>> INFO - core.main (13:56:46.582) - MainThread (10924):
>> Java Access Bridge support initialized
>> INFO - _UIAHandler.UIAHandler.MTAThreadFunc
(13:56:46.582) - _UIAHandler.UIAHandler.MTAThread (11020):
>> UIAutomation: IUIAutomation6
>> INFO - core.main (13:56:46.762) - MainThread (10924):
>> NVDA initialized
>> ERROR - RPC process 8756 (nvda_slave.exe)
(13:57:05.773) - Dummy-1 (10840):
>> __main__.main:
>> slave error
>> Traceback (most recent call last):
>> File "nvda_slave.pyw", line 47, in main
>> File "installer.pyc", line 454, in install
>> File "installer.pyc", line 261, in
registerInstallation
>> File "installer.pyc", line 58, in createShortcut
>> File "comtypes\client\lazybind.pyc", line 218, in
__setattr__
>> File "comtypes\automation.pyc", line 729, in
_invoke
>> _ctypes.COMError: (-2147352567, 'Ausnahmefehler
aufgetreten.', (None, None, None, 0, None))
>> ERROR - gui.installerGui.doInstall (13:57:05.793) -
MainThread (10924):
>> Installation failed: 1
>>
>>
>>
>
>
--
Quentin
Christensen
Training and Support Manager
-- Quentin Christensen Training and Support Manager
|
|
toggle quoted messageShow quoted text
Hi Sandra,
Thanks for following up, I appreciate the clarification.
Setting my system language to German, I can replicate
this. We'll look into it.
Quentin.
Hi Quentin,
You wrote:
When you originally went to install, did
you get the UAC prompt from Windows itself about
installing the program? You get that for any program
you install, but sometimes it pops up and doesn't get
focus so you aren't alerted to it and even visually it's
not obvious. If you don't answer Yes to the UAC prompt
within about 20 seconds, it times out and denies the
program from installing.
Yes, I did see it, but the UAC prompt isn't the problem,
I always answer Yes using the alt Y or in my case alt+j
shortcut (German windows), and the installation continues.
I don't wait for 20 seconds for something to happen.
The only other thing I was thinking was if you had
controlled folder access set, it will install NVDA but
not create the desktop shortcut. If that was the
issue though, it wouldn't have worked any better with
NVDA 2019.1 than 2019.3.
No, I don't have controlled folder access set. I checked
this when it didn't work, because I knew it could be a
problem. No, it's not active.
I do think there is a problem with the installation of
2019.3 though, because a lady on the German NVDA list
reported the same problem. She's a very competent computer
user and I'm sure she, too, knows how to deal with UAC.
Maybe it doesn't affect systems where English is the
default language... And maybe it wasn't reported much,
because many people using NVDA 2019.3 will have updated an
older version and won't have encountered this issue,
because the shortcut and start menu entries had already
been created by a previous installation of an older
version of NVDA...
I, however, attempted a fresh install on a new machine.
Best
Sandra
Hi Felix,
Thanks for your help. Unfortunately setting the NVDA
language to English
didn't help. The failed installation not only faild to
create the
desktop shortcut, but also didn't create NVDA entries
in the start menu.
I installed NVDA 2019.1 first and then updated to
2019.3.1, that did the
trick.
Best
Sandra
Am 04.03.2020 um 13:22 schrieb Felix G.:
> Hello Sandra,
> the installation failed because NVDA was unable
to create its desktop
> shortcut, for reasons I cannot begin to guess. I
can think of two
> options:
> 1. Install without creating a desktop shortcut,
then create one manually.
> 2. Sometimes, switching the NVDA language to
English before installing
> fixes this problem. If you feel comfortable doing
this, it may be the
> cleaner option.
> Hope this helps,
> Felix
>
> Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra
Pilz <sandra914481@...>:
>> Hello,
>>
>>
>> I'm trying to install NVDA on a new machine
running Windows 10 pro 1909.
>>
>>
>> I'm running the installation file as
administrator. I'm getting the message that installing
NVDA has failed.
>>
>>
>> Please also see the log included below.
>>
>>
>> Does anyone know what the problem might be
and how to solve it??
>>
>>
>> Thanks.
>>
>>
>> Cheers
>>
>>
>> Sandra
>>
>>
>> INFO - __main__ (13:56:46.002) - MainThread
(10924):
>> Starting NVDA version 2019.3.1
>> INFO - core.main (13:56:46.082) - MainThread
(10924):
>> Config dir:
C:\Users\sandr\AppData\Roaming\nvda
>> INFO - config.ConfigManager._loadConfig
(13:56:46.082) - MainThread (10924):
>> Loading config:
C:\Users\sandr\AppData\Roaming\nvda\nvda.ini
>> INFO - core.main (13:56:46.122) - MainThread
(10924):
>> Using Windows version 10.0.18363 workstation
>> INFO - core.main (13:56:46.122) - MainThread
(10924):
>> Using Python version 3.7.5
(tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC
v.1916 32 bit (Intel)]
>> INFO - core.main (13:56:46.122) - MainThread
(10924):
>> Using comtypes version 1.1.7
>> INFO - core.main (13:56:46.122) - MainThread
(10924):
>> Using configobj version 5.1.0 with validate
version 1.0.1
>> INFO - synthDriverHandler.setSynth
(13:56:46.402) - MainThread (10924):
>> Loaded synthDriver oneCore
>> INFO - core.main (13:56:46.402) - MainThread
(10924):
>> Using wx version 4.0.3 msw (phoenix)
wxWidgets 3.0.5 with six version 1.12.0
>> INFO - brailleInput.initialize (13:56:46.407)
- MainThread (10924):
>> Braille input initialized
>> INFO - braille.initialize (13:56:46.407) -
MainThread (10924):
>> Using liblouis version 3.10.0
>> INFO - braille.initialize (13:56:46.407) -
MainThread (10924):
>> Using pySerial version 3.4
>> INFO -
braille.BrailleHandler.setDisplayByName (13:56:46.412)
- MainThread (10924):
>> Loaded braille display driver noBraille,
current display has 0 cells.
>> INFO -
brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__
(13:56:46.464) - braille._BgThread (11016):
>> Found Easy Braille connected via hid
(\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
>> INFO -
braille.BrailleHandler.setDisplayByName (13:56:46.472)
- braille._BgThread (11016):
>> Loaded braille display driver handyTech,
current display has 40 cells.
>> INFO - core.main (13:56:46.582) - MainThread
(10924):
>> Java Access Bridge support initialized
>> INFO - _UIAHandler.UIAHandler.MTAThreadFunc
(13:56:46.582) - _UIAHandler.UIAHandler.MTAThread
(11020):
>> UIAutomation: IUIAutomation6
>> INFO - core.main (13:56:46.762) - MainThread
(10924):
>> NVDA initialized
>> ERROR - RPC process 8756 (nvda_slave.exe)
(13:57:05.773) - Dummy-1 (10840):
>> __main__.main:
>> slave error
>> Traceback (most recent call last):
>> File "nvda_slave.pyw", line 47, in main
>> File "installer.pyc", line 454, in install
>> File "installer.pyc", line 261, in
registerInstallation
>> File "installer.pyc", line 58, in
createShortcut
>> File "comtypes\client\lazybind.pyc", line
218, in __setattr__
>> File "comtypes\automation.pyc", line 729,
in _invoke
>> _ctypes.COMError: (-2147352567,
'Ausnahmefehler aufgetreten.', (None, None, None, 0,
None))
>> ERROR - gui.installerGui.doInstall
(13:57:05.793) - MainThread (10924):
>> Installation failed: 1
>>
>>
>>
>
>
--
Quentin
Christensen
Training and Support
Manager
--
Quentin
Christensen
Training and Support Manager
|
|
Hi Quentin,
Thank you for trying it on your system. Hopefully this bug can be fixed soon.
Regards
RegardSandra
Sandra
Von meinem iPhone gesendet
toggle quoted messageShow quoted text
Am 06.03.2020 um 00:19 schrieb Quentin Christensen <quentin@...>:
Hi Sandra,
Thanks for following up, I appreciate the clarification.
Setting my system language to German, I can replicate this. We'll look into it.
Quentin.
Hi Quentin,
You wrote:
When you originally went to install, did you get
the UAC prompt from Windows itself about installing the
program? You get that for any program you install, but
sometimes it pops up and doesn't get focus so you aren't alerted
to it and even visually it's not obvious. If you don't answer
Yes to the UAC prompt within about 20 seconds, it times out and
denies the program from installing.
Yes, I did see it, but the UAC prompt isn't the problem, I always
answer Yes using the alt Y or in my case alt+j shortcut (German
windows), and the installation continues. I don't wait for 20
seconds for something to happen.
The only other thing I was thinking was if you had
controlled folder access set, it will install NVDA but not
create the desktop shortcut. If that was the issue though, it
wouldn't have worked any better with NVDA 2019.1 than 2019.3.
No, I don't have controlled folder access set. I checked this
when it didn't work, because I knew it could be a problem. No,
it's not active.
I do think there is a problem with the installation of 2019.3
though, because a lady on the German NVDA list reported the same
problem. She's a very competent computer user and I'm sure she,
too, knows how to deal with UAC. Maybe it doesn't affect systems
where English is the default language... And maybe it wasn't
reported much, because many people using NVDA 2019.3 will have
updated an older version and won't have encountered this issue,
because the shortcut and start menu entries had already been
created by a previous installation of an older version of NVDA...
I, however, attempted a fresh install on a new machine.
Best
Sandra
Hi Felix,
Thanks for your help. Unfortunately setting the NVDA language
to English
didn't help. The failed installation not only faild to create
the
desktop shortcut, but also didn't create NVDA entries in the
start menu.
I installed NVDA 2019.1 first and then updated to 2019.3.1,
that did the
trick.
Best
Sandra
Am 04.03.2020 um 13:22 schrieb Felix G.:
> Hello Sandra,
> the installation failed because NVDA was unable to create
its desktop
> shortcut, for reasons I cannot begin to guess. I can
think of two
> options:
> 1. Install without creating a desktop shortcut, then
create one manually.
> 2. Sometimes, switching the NVDA language to English
before installing
> fixes this problem. If you feel comfortable doing this,
it may be the
> cleaner option.
> Hope this helps,
> Felix
>
> Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra Pilz
<sandra914481@...>:
>> Hello,
>>
>>
>> I'm trying to install NVDA on a new machine running
Windows 10 pro 1909.
>>
>>
>> I'm running the installation file as administrator.
I'm getting the message that installing NVDA has failed.
>>
>>
>> Please also see the log included below.
>>
>>
>> Does anyone know what the problem might be and how to
solve it??
>>
>>
>> Thanks.
>>
>>
>> Cheers
>>
>>
>> Sandra
>>
>>
>> INFO - __main__ (13:56:46.002) - MainThread (10924):
>> Starting NVDA version 2019.3.1
>> INFO - core.main (13:56:46.082) - MainThread (10924):
>> Config dir: C:\Users\sandr\AppData\Roaming\nvda
>> INFO - config.ConfigManager._loadConfig
(13:56:46.082) - MainThread (10924):
>> Loading config:
C:\Users\sandr\AppData\Roaming\nvda\nvda.ini
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using Windows version 10.0.18363 workstation
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b,
Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using comtypes version 1.1.7
>> INFO - core.main (13:56:46.122) - MainThread (10924):
>> Using configobj version 5.1.0 with validate version
1.0.1
>> INFO - synthDriverHandler.setSynth (13:56:46.402) -
MainThread (10924):
>> Loaded synthDriver oneCore
>> INFO - core.main (13:56:46.402) - MainThread (10924):
>> Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
with six version 1.12.0
>> INFO - brailleInput.initialize (13:56:46.407) -
MainThread (10924):
>> Braille input initialized
>> INFO - braille.initialize (13:56:46.407) - MainThread
(10924):
>> Using liblouis version 3.10.0
>> INFO - braille.initialize (13:56:46.407) - MainThread
(10924):
>> Using pySerial version 3.4
>> INFO - braille.BrailleHandler.setDisplayByName
(13:56:46.412) - MainThread (10924):
>> Loaded braille display driver noBraille, current
display has 0 cells.
>> INFO -
brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__
(13:56:46.464) - braille._BgThread (11016):
>> Found Easy Braille connected via hid
(\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
>> INFO - braille.BrailleHandler.setDisplayByName
(13:56:46.472) - braille._BgThread (11016):
>> Loaded braille display driver handyTech, current
display has 40 cells.
>> INFO - core.main (13:56:46.582) - MainThread (10924):
>> Java Access Bridge support initialized
>> INFO - _UIAHandler.UIAHandler.MTAThreadFunc
(13:56:46.582) - _UIAHandler.UIAHandler.MTAThread (11020):
>> UIAutomation: IUIAutomation6
>> INFO - core.main (13:56:46.762) - MainThread (10924):
>> NVDA initialized
>> ERROR - RPC process 8756 (nvda_slave.exe)
(13:57:05.773) - Dummy-1 (10840):
>> __main__.main:
>> slave error
>> Traceback (most recent call last):
>> File "nvda_slave.pyw", line 47, in main
>> File "installer.pyc", line 454, in install
>> File "installer.pyc", line 261, in
registerInstallation
>> File "installer.pyc", line 58, in createShortcut
>> File "comtypes\client\lazybind.pyc", line 218, in
__setattr__
>> File "comtypes\automation.pyc", line 729, in
_invoke
>> _ctypes.COMError: (-2147352567, 'Ausnahmefehler
aufgetreten.', (None, None, None, 0, None))
>> ERROR - gui.installerGui.doInstall (13:57:05.793) -
MainThread (10924):
>> Installation failed: 1
>>
>>
>>
>
>
--
Quentin
Christensen
Training and Support Manager
-- Quentin Christensen Training and Support Manager
|
|
Hi Kostadin,
Are you sure it's the same bug? If it was and if it has been there five years, installing NVDA 2019.1 shouldn't have worked either. But I was able to install that version successfully.
Regards
Regard
Sandra
Von meinem iPhone gesendet
toggle quoted messageShow quoted text
Am 06.03.2020 um 07:47 schrieb Kostadin Kolev <k.kolev1985@...>:
Hello Quentin,
If I'm not mistaking, this is a known bug in NVDA. I've reported
this almost 5 years ago and it still occurs. Here is the bug: NVDA
installation may fail with an error if system UI language and
language for non-unicode programs don't match · Issue #5166.
______
Best wishes,
Kostadin Kolev
На 6.3.2020 г. в 1:19, Quentin
Christensen написа:
Hi Sandra,
Thanks for following up, I appreciate the clarification.
Setting my system language to German, I can replicate
this. We'll look into it.
Quentin.
Hi Quentin,
You wrote:
When you originally went to install, did
you get the UAC prompt from Windows itself about
installing the program? You get that for any program
you install, but sometimes it pops up and doesn't get
focus so you aren't alerted to it and even visually it's
not obvious. If you don't answer Yes to the UAC prompt
within about 20 seconds, it times out and denies the
program from installing.
Yes, I did see it, but the UAC prompt isn't the problem,
I always answer Yes using the alt Y or in my case alt+j
shortcut (German windows), and the installation continues.
I don't wait for 20 seconds for something to happen.
The only other thing I was thinking was if you had
controlled folder access set, it will install NVDA but
not create the desktop shortcut. If that was the
issue though, it wouldn't have worked any better with
NVDA 2019.1 than 2019.3.
No, I don't have controlled folder access set. I checked
this when it didn't work, because I knew it could be a
problem. No, it's not active.
I do think there is a problem with the installation of
2019.3 though, because a lady on the German NVDA list
reported the same problem. She's a very competent computer
user and I'm sure she, too, knows how to deal with UAC.
Maybe it doesn't affect systems where English is the
default language... And maybe it wasn't reported much,
because many people using NVDA 2019.3 will have updated an
older version and won't have encountered this issue,
because the shortcut and start menu entries had already
been created by a previous installation of an older
version of NVDA...
I, however, attempted a fresh install on a new machine.
Best
Sandra
Hi Felix,
Thanks for your help. Unfortunately setting the NVDA
language to English
didn't help. The failed installation not only faild to
create the
desktop shortcut, but also didn't create NVDA entries
in the start menu.
I installed NVDA 2019.1 first and then updated to
2019.3.1, that did the
trick.
Best
Sandra
Am 04.03.2020 um 13:22 schrieb Felix G.:
> Hello Sandra,
> the installation failed because NVDA was unable
to create its desktop
> shortcut, for reasons I cannot begin to guess. I
can think of two
> options:
> 1. Install without creating a desktop shortcut,
then create one manually.
> 2. Sometimes, switching the NVDA language to
English before installing
> fixes this problem. If you feel comfortable doing
this, it may be the
> cleaner option.
> Hope this helps,
> Felix
>
> Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra
Pilz <sandra914481@...>:
>> Hello,
>>
>>
>> I'm trying to install NVDA on a new machine
running Windows 10 pro 1909.
>>
>>
>> I'm running the installation file as
administrator. I'm getting the message that installing
NVDA has failed.
>>
>>
>> Please also see the log included below.
>>
>>
>> Does anyone know what the problem might be
and how to solve it??
>>
>>
>> Thanks.
>>
>>
>> Cheers
>>
>>
>> Sandra
>>
>>
>> INFO - __main__ (13:56:46.002) - MainThread
(10924):
>> Starting NVDA version 2019.3.1
>> INFO - core.main (13:56:46.082) - MainThread
(10924):
>> Config dir:
C:\Users\sandr\AppData\Roaming\nvda
>> INFO - config.ConfigManager._loadConfig
(13:56:46.082) - MainThread (10924):
>> Loading config:
C:\Users\sandr\AppData\Roaming\nvda\nvda.ini
>> INFO - core.main (13:56:46.122) - MainThread
(10924):
>> Using Windows version 10.0.18363 workstation
>> INFO - core.main (13:56:46.122) - MainThread
(10924):
>> Using Python version 3.7.5
(tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC
v.1916 32 bit (Intel)]
>> INFO - core.main (13:56:46.122) - MainThread
(10924):
>> Using comtypes version 1.1.7
>> INFO - core.main (13:56:46.122) - MainThread
(10924):
>> Using configobj version 5.1.0 with validate
version 1.0.1
>> INFO - synthDriverHandler.setSynth
(13:56:46.402) - MainThread (10924):
>> Loaded synthDriver oneCore
>> INFO - core.main (13:56:46.402) - MainThread
(10924):
>> Using wx version 4.0.3 msw (phoenix)
wxWidgets 3.0.5 with six version 1.12.0
>> INFO - brailleInput.initialize (13:56:46.407)
- MainThread (10924):
>> Braille input initialized
>> INFO - braille.initialize (13:56:46.407) -
MainThread (10924):
>> Using liblouis version 3.10.0
>> INFO - braille.initialize (13:56:46.407) -
MainThread (10924):
>> Using pySerial version 3.4
>> INFO -
braille.BrailleHandler.setDisplayByName (13:56:46.412)
- MainThread (10924):
>> Loaded braille display driver noBraille,
current display has 0 cells.
>> INFO -
brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__
(13:56:46.464) - braille._BgThread (11016):
>> Found Easy Braille connected via hid
(\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
>> INFO -
braille.BrailleHandler.setDisplayByName (13:56:46.472)
- braille._BgThread (11016):
>> Loaded braille display driver handyTech,
current display has 40 cells.
>> INFO - core.main (13:56:46.582) - MainThread
(10924):
>> Java Access Bridge support initialized
>> INFO - _UIAHandler.UIAHandler.MTAThreadFunc
(13:56:46.582) - _UIAHandler.UIAHandler.MTAThread
(11020):
>> UIAutomation: IUIAutomation6
>> INFO - core.main (13:56:46.762) - MainThread
(10924):
>> NVDA initialized
>> ERROR - RPC process 8756 (nvda_slave.exe)
(13:57:05.773) - Dummy-1 (10840):
>> __main__.main:
>> slave error
>> Traceback (most recent call last):
>> File "nvda_slave.pyw", line 47, in main
>> File "installer.pyc", line 454, in install
>> File "installer.pyc", line 261, in
registerInstallation
>> File "installer.pyc", line 58, in
createShortcut
>> File "comtypes\client\lazybind.pyc", line
218, in __setattr__
>> File "comtypes\automation.pyc", line 729,
in _invoke
>> _ctypes.COMError: (-2147352567,
'Ausnahmefehler aufgetreten.', (None, None, None, 0,
None))
>> ERROR - gui.installerGui.doInstall
(13:57:05.793) - MainThread (10924):
>> Installation failed: 1
>>
>>
>>
>
>
--
Quentin
Christensen
Training and Support
Manager
--
Quentin
Christensen
Training and Support Manager
|
|
Hi, this one was gone for some time but it has a way of reappearing. If I'm not mistaken, it's a string which got translated when it shouldn't have been. Best, Felix
Am Fr., 6. März 2020 um 08:36 Uhr schrieb Sandra Pilz <sandra914481@gmail.com>:
toggle quoted messageShow quoted text
Hi Kostadin,
Are you sure it's the same bug? If it was and if it has been there five years, installing NVDA 2019.1 shouldn't have worked either. But I was able to install that version successfully.
Regards
Regard
Sandra
Von meinem iPhone gesendet
Am 06.03.2020 um 07:47 schrieb Kostadin Kolev <k.kolev1985@gmail.com>:
Hello Quentin,
If I'm not mistaking, this is a known bug in NVDA. I've reported this almost 5 years ago and it still occurs. Here is the bug: NVDA installation may fail with an error if system UI language and language for non-unicode programs don't match · Issue #5166.
______ Best wishes, Kostadin Kolev
На 6.3.2020 г. в 1:19, Quentin Christensen написа:
Hi Sandra,
Thanks for following up, I appreciate the clarification.
Setting my system language to German, I can replicate this. We'll look into it.
Quentin.
On Thu, Mar 5, 2020 at 11:10 PM Sandra Pilz <sandra914481@gmail.com> wrote:
Hi Quentin,
You wrote:
When you originally went to install, did you get the UAC prompt from Windows itself about installing the program? You get that for any program you install, but sometimes it pops up and doesn't get focus so you aren't alerted to it and even visually it's not obvious. If you don't answer Yes to the UAC prompt within about 20 seconds, it times out and denies the program from installing.
Yes, I did see it, but the UAC prompt isn't the problem, I always answer Yes using the alt Y or in my case alt+j shortcut (German windows), and the installation continues. I don't wait for 20 seconds for something to happen.
The only other thing I was thinking was if you had controlled folder access set, it will install NVDA but not create the desktop shortcut. If that was the issue though, it wouldn't have worked any better with NVDA 2019.1 than 2019.3.
No, I don't have controlled folder access set. I checked this when it didn't work, because I knew it could be a problem. No, it's not active.
I do think there is a problem with the installation of 2019.3 though, because a lady on the German NVDA list reported the same problem. She's a very competent computer user and I'm sure she, too, knows how to deal with UAC. Maybe it doesn't affect systems where English is the default language... And maybe it wasn't reported much, because many people using NVDA 2019.3 will have updated an older version and won't have encountered this issue, because the shortcut and start menu entries had already been created by a previous installation of an older version of NVDA...
I, however, attempted a fresh install on a new machine.
Best
Sandra
Regards
Quentin.
On Thu, Mar 5, 2020 at 2:43 AM Sandra Pilz <sandra914481@gmail.com> wrote:
Hi Felix,
Thanks for your help. Unfortunately setting the NVDA language to English didn't help. The failed installation not only faild to create the desktop shortcut, but also didn't create NVDA entries in the start menu. I installed NVDA 2019.1 first and then updated to 2019.3.1, that did the trick.
Best
Sandra
Am 04.03.2020 um 13:22 schrieb Felix G.:
Hello Sandra, the installation failed because NVDA was unable to create its desktop shortcut, for reasons I cannot begin to guess. I can think of two options: 1. Install without creating a desktop shortcut, then create one manually. 2. Sometimes, switching the NVDA language to English before installing fixes this problem. If you feel comfortable doing this, it may be the cleaner option. Hope this helps, Felix
Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra Pilz <sandra914481@gmail.com>:
Hello,
I'm trying to install NVDA on a new machine running Windows 10 pro 1909.
I'm running the installation file as administrator. I'm getting the message that installing NVDA has failed.
Please also see the log included below.
Does anyone know what the problem might be and how to solve it??
Thanks.
Cheers
Sandra
INFO - __main__ (13:56:46.002) - MainThread (10924): Starting NVDA version 2019.3.1 INFO - core.main (13:56:46.082) - MainThread (10924): Config dir: C:\Users\sandr\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (13:56:46.082) - MainThread (10924): Loading config: C:\Users\sandr\AppData\Roaming\nvda\nvda.ini INFO - core.main (13:56:46.122) - MainThread (10924): Using Windows version 10.0.18363 workstation INFO - core.main (13:56:46.122) - MainThread (10924): Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)] INFO - core.main (13:56:46.122) - MainThread (10924): Using comtypes version 1.1.7 INFO - core.main (13:56:46.122) - MainThread (10924): Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (13:56:46.402) - MainThread (10924): Loaded synthDriver oneCore INFO - core.main (13:56:46.402) - MainThread (10924): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0 INFO - brailleInput.initialize (13:56:46.407) - MainThread (10924): Braille input initialized INFO - braille.initialize (13:56:46.407) - MainThread (10924): Using liblouis version 3.10.0 INFO - braille.initialize (13:56:46.407) - MainThread (10924): Using pySerial version 3.4 INFO - braille.BrailleHandler.setDisplayByName (13:56:46.412) - MainThread (10924): Loaded braille display driver noBraille, current display has 0 cells. INFO - brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__ (13:56:46.464) - braille._BgThread (11016): Found Easy Braille connected via hid (\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) INFO - braille.BrailleHandler.setDisplayByName (13:56:46.472) - braille._BgThread (11016): Loaded braille display driver handyTech, current display has 40 cells. INFO - core.main (13:56:46.582) - MainThread (10924): Java Access Bridge support initialized INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:56:46.582) - _UIAHandler.UIAHandler.MTAThread (11020): UIAutomation: IUIAutomation6 INFO - core.main (13:56:46.762) - MainThread (10924): NVDA initialized ERROR - RPC process 8756 (nvda_slave.exe) (13:57:05.773) - Dummy-1 (10840): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw", line 47, in main File "installer.pyc", line 454, in install File "installer.pyc", line 261, in registerInstallation File "installer.pyc", line 58, in createShortcut File "comtypes\client\lazybind.pyc", line 218, in __setattr__ File "comtypes\automation.pyc", line 729, in _invoke _ctypes.COMError: (-2147352567, 'Ausnahmefehler aufgetreten.', (None, None, None, 0, None)) ERROR - gui.installerGui.doInstall (13:57:05.793) - MainThread (10924): Installation failed: 1
-- Quentin Christensen Training and Support Manager
NVDA 2019.3 rc2 now available for testing: https://www.nvaccess.org/post/nvda-2019-3rc2-now-available-for-testing/
Web: www.nvaccess.org Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess
-- Quentin Christensen Training and Support Manager
NVDA 2019.3 rc2 now available for testing: https://www.nvaccess.org/post/nvda-2019-3rc2-now-available-for-testing/
Web: www.nvaccess.org Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess
|
|
We've had a look into this one and it appears the German translators have translated the string for the shortcut key to start NVDA, which actually should not have been translated. I will chase up with the translators so it can be fixed for 2020.1.
Regards
Quentin
toggle quoted messageShow quoted text
Hi,
this one was gone for some time but it has a way of reappearing. If
I'm not mistaken, it's a string which got translated when it shouldn't
have been.
Best,
Felix
Am Fr., 6. März 2020 um 08:36 Uhr schrieb Sandra Pilz <sandra914481@...>:
>
> Hi Kostadin,
>
> Are you sure it's the same bug? If it was and if it has been there five years, installing NVDA 2019.1 shouldn't have worked either. But I was able to install that version successfully.
>
> Regards
>
>
>
>
> Regard
>
> Sandra
>
> Von meinem iPhone gesendet
>
> Am 06.03.2020 um 07:47 schrieb Kostadin Kolev <k.kolev1985@...>:
>
>
>
> Hello Quentin,
>
> If I'm not mistaking, this is a known bug in NVDA. I've reported this almost 5 years ago and it still occurs. Here is the bug: NVDA installation may fail with an error if system UI language and language for non-unicode programs don't match · Issue #5166.
>
> ______
> Best wishes,
> Kostadin Kolev
>
> На 6.3.2020 г. в 1:19, Quentin Christensen написа:
>
> Hi Sandra,
>
> Thanks for following up, I appreciate the clarification.
>
> Setting my system language to German, I can replicate this. We'll look into it.
>
> Quentin.
>
> On Thu, Mar 5, 2020 at 11:10 PM Sandra Pilz <sandra914481@...> wrote:
>>
>> Hi Quentin,
>>
>>
>> You wrote:
>>
>> When you originally went to install, did you get the UAC prompt from Windows itself about installing the program? You get that for any program you install, but sometimes it pops up and doesn't get focus so you aren't alerted to it and even visually it's not obvious. If you don't answer Yes to the UAC prompt within about 20 seconds, it times out and denies the program from installing.
>>
>>
>> Yes, I did see it, but the UAC prompt isn't the problem, I always answer Yes using the alt Y or in my case alt+j shortcut (German windows), and the installation continues. I don't wait for 20 seconds for something to happen.
>>
>>
>> The only other thing I was thinking was if you had controlled folder access set, it will install NVDA but not create the desktop shortcut. If that was the issue though, it wouldn't have worked any better with NVDA 2019.1 than 2019.3.
>>
>> No, I don't have controlled folder access set. I checked this when it didn't work, because I knew it could be a problem. No, it's not active.
>>
>>
>> I do think there is a problem with the installation of 2019.3 though, because a lady on the German NVDA list reported the same problem. She's a very competent computer user and I'm sure she, too, knows how to deal with UAC. Maybe it doesn't affect systems where English is the default language... And maybe it wasn't reported much, because many people using NVDA 2019.3 will have updated an older version and won't have encountered this issue, because the shortcut and start menu entries had already been created by a previous installation of an older version of NVDA...
>>
>>
>> I, however, attempted a fresh install on a new machine.
>>
>>
>> Best
>>
>>
>> Sandra
>>
>>
>> Regards
>>
>> Quentin.
>>
>> On Thu, Mar 5, 2020 at 2:43 AM Sandra Pilz <sandra914481@...> wrote:
>>>
>>> Hi Felix,
>>>
>>>
>>> Thanks for your help. Unfortunately setting the NVDA language to English
>>> didn't help. The failed installation not only faild to create the
>>> desktop shortcut, but also didn't create NVDA entries in the start menu.
>>> I installed NVDA 2019.1 first and then updated to 2019.3.1, that did the
>>> trick.
>>>
>>>
>>> Best
>>>
>>>
>>> Sandra
>>>
>>> Am 04.03.2020 um 13:22 schrieb Felix G.:
>>> > Hello Sandra,
>>> > the installation failed because NVDA was unable to create its desktop
>>> > shortcut, for reasons I cannot begin to guess. I can think of two
>>> > options:
>>> > 1. Install without creating a desktop shortcut, then create one manually.
>>> > 2. Sometimes, switching the NVDA language to English before installing
>>> > fixes this problem. If you feel comfortable doing this, it may be the
>>> > cleaner option.
>>> > Hope this helps,
>>> > Felix
>>> >
>>> > Am Mi., 4. März 2020 um 14:11 Uhr schrieb Sandra Pilz <sandra914481@...>:
>>> >> Hello,
>>> >>
>>> >>
>>> >> I'm trying to install NVDA on a new machine running Windows 10 pro 1909.
>>> >>
>>> >>
>>> >> I'm running the installation file as administrator. I'm getting the message that installing NVDA has failed.
>>> >>
>>> >>
>>> >> Please also see the log included below.
>>> >>
>>> >>
>>> >> Does anyone know what the problem might be and how to solve it??
>>> >>
>>> >>
>>> >> Thanks.
>>> >>
>>> >>
>>> >> Cheers
>>> >>
>>> >>
>>> >> Sandra
>>> >>
>>> >>
>>> >> INFO - __main__ (13:56:46.002) - MainThread (10924):
>>> >> Starting NVDA version 2019.3.1
>>> >> INFO - core.main (13:56:46.082) - MainThread (10924):
>>> >> Config dir: C:\Users\sandr\AppData\Roaming\nvda
>>> >> INFO - config.ConfigManager._loadConfig (13:56:46.082) - MainThread (10924):
>>> >> Loading config: C:\Users\sandr\AppData\Roaming\nvda\nvda.ini
>>> >> INFO - core.main (13:56:46.122) - MainThread (10924):
>>> >> Using Windows version 10.0.18363 workstation
>>> >> INFO - core.main (13:56:46.122) - MainThread (10924):
>>> >> Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]
>>> >> INFO - core.main (13:56:46.122) - MainThread (10924):
>>> >> Using comtypes version 1.1.7
>>> >> INFO - core.main (13:56:46.122) - MainThread (10924):
>>> >> Using configobj version 5.1.0 with validate version 1.0.1
>>> >> INFO - synthDriverHandler.setSynth (13:56:46.402) - MainThread (10924):
>>> >> Loaded synthDriver oneCore
>>> >> INFO - core.main (13:56:46.402) - MainThread (10924):
>>> >> Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0
>>> >> INFO - brailleInput.initialize (13:56:46.407) - MainThread (10924):
>>> >> Braille input initialized
>>> >> INFO - braille.initialize (13:56:46.407) - MainThread (10924):
>>> >> Using liblouis version 3.10.0
>>> >> INFO - braille.initialize (13:56:46.407) - MainThread (10924):
>>> >> Using pySerial version 3.4
>>> >> INFO - braille.BrailleHandler.setDisplayByName (13:56:46.412) - MainThread (10924):
>>> >> Loaded braille display driver noBraille, current display has 0 cells.
>>> >> INFO - brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__ (13:56:46.464) - braille._BgThread (11016):
>>> >> Found Easy Braille connected via hid (\\?\hid#vid_1fe4&pid_0044#7&7f9a61d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
>>> >> INFO - braille.BrailleHandler.setDisplayByName (13:56:46.472) - braille._BgThread (11016):
>>> >> Loaded braille display driver handyTech, current display has 40 cells.
>>> >> INFO - core.main (13:56:46.582) - MainThread (10924):
>>> >> Java Access Bridge support initialized
>>> >> INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:56:46.582) - _UIAHandler.UIAHandler.MTAThread (11020):
>>> >> UIAutomation: IUIAutomation6
>>> >> INFO - core.main (13:56:46.762) - MainThread (10924):
>>> >> NVDA initialized
>>> >> ERROR - RPC process 8756 (nvda_slave.exe) (13:57:05.773) - Dummy-1 (10840):
>>> >> __main__.main:
>>> >> slave error
>>> >> Traceback (most recent call last):
>>> >> File "nvda_slave.pyw", line 47, in main
>>> >> File "installer.pyc", line 454, in install
>>> >> File "installer.pyc", line 261, in registerInstallation
>>> >> File "installer.pyc", line 58, in createShortcut
>>> >> File "comtypes\client\lazybind.pyc", line 218, in __setattr__
>>> >> File "comtypes\automation.pyc", line 729, in _invoke
>>> >> _ctypes.COMError: (-2147352567, 'Ausnahmefehler aufgetreten.', (None, None, None, 0, None))
>>> >> ERROR - gui.installerGui.doInstall (13:57:05.793) - MainThread (10924):
>>> >> Installation failed: 1
>>> >>
>>> >>
>>> >>
>>> >
>>> >
>>>
>>>
>>>
>>
>>
>> --
>> Quentin Christensen
>> Training and Support Manager
>>
>> NVDA 2019.3 rc2 now available for testing: https://www.nvaccess.org/post/nvda-2019-3rc2-now-available-for-testing/
>>
>> Web: www.nvaccess.org
>> Training: https://www.nvaccess.org/shop/
>> Certification: https://certification.nvaccess.org/
>> User group: https://nvda.groups.io/g/nvda
>> Facebook: http://www.facebook.com/NVAccess
>> Twitter: @NVAccess
>
>
>
> --
> Quentin Christensen
> Training and Support Manager
>
> NVDA 2019.3 rc2 now available for testing: https://www.nvaccess.org/post/nvda-2019-3rc2-now-available-for-testing/
>
> Web: www.nvaccess.org
> Training: https://www.nvaccess.org/shop/
> Certification: https://certification.nvaccess.org/
> User group: https://nvda.groups.io/g/nvda
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess
>
>
-- Quentin Christensen Training and Support Manager
|
|