Oh, It sounds like Linux is very fiddly. I had a friend who was having a
friend fix her windows computer. He wanted to put it on her computer. But
she had to heavily convince him that it was not usable for blind people. I'm
glad you use it for a hobby. I don't know it. But if you like it use it as
your hobby. I thought it was an old old program that hardly nobody uses.

-----Original Message-----
From: Shaun Everiss [mailto:sm.everiss@...]
Sent: March-27-16 11:21 AM
To: nvda@groups.io
Subject: Re: [nvda] danger, danger nvda

Hmmm.
Well I havn't touched linux for a while.
When I went to school it was fedora 4 or was it 3 I forget.
I had an old synth then, the sound stuff started after school.
I fiddled with grml for a bit, then ran vinux 3 then ubuntu shell.
I fiddled with arch while I was sick but never got it working again and
due to my system I used it for not being active for a while its stopped
working I guess my time is out of date.
My plan is to use sonar but to be honest linux is a hobby for me.
I am a primarily windows user, and so is just about everyone on the
network both remote and local so right now I don't use linux.
Its been a fiddle here and there nothing serious.



On 28/03/2016 7:08 a.m., Pete wrote:

Hi Shaun

Multiple versions of dot net behave better. Some games wanted dot
net 2.0 to run and a t i and intel install managers use dot net 2.0. My
old x p computer had dot net 1.1 2.0 3.0 3.5 and 4.0 installed. I need
to figure out a way to capture the info for the visual c + + errors to
present them here. Not sure how to do this. Some of the v c messages
are in a dialog box but the latest things I am talking about I think are
in a balloon or some thing that disappears. The message was about
conflicting instances of some v c dot d l l being loaded.
What dist & ver of Linux are you using?
Pete


On 3/26/2016 12:36 AM, Shaun Everiss wrote:

Well, I have a multipul installs of dotnet from 3.5 to 4.6 here on 7
win10 has 5 and does not run other versions.
v3.5 works on v2, and v4 on v3 the latest dotnets should work as far
back as 2.
As for visual c, they shouldn't conflict as such because certain
programs need certain libraries.
Now, my only wish would be that windows does what linux does.
The libs don't take up that much space but even so.
I'd prefur say you install something or try to do something.\
Say I want to run x program but its missing y z dll.
Windows is unable to start this program because *.dll is not loaded
please reinstall.
To avoid this I load just about every library I can to stop that error.
It happens with codecs.
If I am using linux, I type in something to install, it says this
needs such and such component, do you want to install it or it tells
you what to do.
I have often installed programs for ssh and a few things on linux, and
got messages like this program is not installed, or this program is
part of another install for servers, or in deed, unable to start
because this thing is missing.
However in linux you can then install it because it basically tells
you what to install.
If ms would do the same at least with its libs then we wouldn't have
this issue better still with linux it tells you what is needed, what
could be nice, what is not but if you need it it would be nice or
simply whatever.
In windows, I have slim dx, java latest, klite codec, visual c 2005sp1
2008sp1 2010 2012 2013 2015 2016 and their 64 bit equivilants.
On the subject of python, both 3x and 2x are still supported 2.7x is
the version a lot of stuff uses however its a good point a lot of
stuff has moved on from the older releases.



On 26/03/2016 2:29 a.m., Pete wrote:

Hi
The proliferation of the famous Microsoft Visual C + + redistributable
packages is dangerous to nvva.
Windows loads multiple instances of the d l l s and not all instances
are the same version or even the correct version for a given program
causing untraceable bugs in nvda along with other programs like explorer
or the w10 file manager.
There doesn't seem to be backward compatibility say from visual c + +
2015 to earlier versions.
A second dangerous trend is the proliferation of multiple versions of
dot net frame work.
Again here no apparent backward compatibility seems to exists.
So one has his or her windows computer cluttered up with multiple
versions in most cases taking up hard drive real estate and causing
conflicts.
A lot of the nvda bugs possibly can be linked to miss matched
versions of d l l s being loaded by windows.
A third concern is the old version of python being used. If it's
time to upgrade from say visual c + + 2008 it should be time to update
to a newer version of python.
Shouldn't it?
Pete




.