Post by fritz » 17.12.2009 19:36:43
This is my third post regarding this "effect". It is definitely a Dexpot issue, for without it installed there is no problem. The problem is that when Dexpot is started (usually automatically at startup), several other programs are also invoked even though I have not asked for them in any way, explicitly, or through some config in Dexpot. The particular programs in my case are part of ESRI ArcGIS Desktop suite, v.9.3. They are memory hogs, so it is not with great glee I watch as they are launched without being beckoned by me. But the current release of Dexpot 1.5 seems somewhat improved over the beta versions that not only launched these programs spontaneously, seemingly at random, but also launched many many instances of them (after 10 or 12 instances launched I typically would abort the session, reboot, uninstall Dexpot and take 10 deep breaths before resuming the real work). Anyhow, for such a functional application, it would be a boon for the developers to at least investigate potential trouble spots, or maybe even post the source code?
fritz
This is my third post regarding this "effect". It is definitely a Dexpot issue, for without it installed there is no problem. The problem is that when Dexpot is started (usually automatically at startup), several other programs are also invoked even though I have not asked for them in any way, explicitly, or through some config in Dexpot. The particular programs in my case are part of ESRI ArcGIS Desktop suite, v.9.3. They are memory hogs, so it is not with great glee I watch as they are launched without being beckoned by me. But the current release of Dexpot 1.5 seems somewhat improved over the beta versions that not only launched these programs spontaneously, seemingly at random, but also launched many many instances of them (after 10 or 12 instances launched I typically would abort the session, reboot, uninstall Dexpot and take 10 deep breaths before resuming the real work). Anyhow, for such a functional application, it would be a boon for the developers to at least investigate potential trouble spots, or maybe even post the source code?
fritz