racoon wrote: > On 04.05.2016 01:06, Uwe Stöhr wrote: >> Am 22.04.2016 um 16:24 schrieb racoon: >> >>>> we found out that your Windows system is heavily "fragmented". >>> >>> I am not sure whom you mean by "we" who found out that my Windoes system >>> is "heavily fragmented". Do you mean you and me? >> >> Hi Daniel, >> >> Yes. >> >> If so, then count me >>> out of this since I am not convinced. There is no other noticeable >>> problem with my system. Or is there some kind of common agreement among >>> LyX developers or community that my system is "fragmented"? Would be >>> nice to know. >> >> You told me about many installations of the same VC runtimes. This is a >> problem and also strange. One only needs one VC runtime for every MSVC >> version and not 4 times the same. The probability is high that they >> interfere with each other.
Many VC runtimes for the same VC version are not uncommon. They could be installed in different directories for example (I have seen several packages that bring their on VC redistributable installers), but still show up in the list of installed packages under a generic name. In most cases, removing one of these version will result in one of the installed programs no longer working correctly, likely in a non-obvious way. Furthermore, the VC redistributables do require flash.ocx as much as LyX does (i. e. not at all), so this cannot be a problem in this case. > I guess checking problems on other PCs would be helpful. Unfortunately, > I don't have a second PC on which this is easily done. On the other > hand, while it might be a nice information to have, I don't think that > this should be a necessary condition for a bug report. There was this > bug in Qt that became *obvious* due to some special setting on my PC. > (http://www.lyx.org/trac/ticket/10017) Now this bug is being fixed in > Qt. If I had not reported it, because I did not have the problem on > another PC, this bug might have gone unnoticed for some more time and > maybe turned out only later. But I guess in general it is better to know > bugs earlier rather than later. One can still decide whether it is worth > doing something about it or not. Your reports are very helpful, please continue. However in this specific case I believe as well that the reason for the problem is independent of LyX, but I'll comment in trac separately with something you could try. Georg
