Quote:
Originally Posted by pete6055
Hello,
Heads up...When Diskeeper 16 is loaded on my PC, Sigil v09.8 will not open. Once Diskeeper is uninstalled, Sigil works as expected. I've reported the software conflict to Conduciv Technologies and I'll share the reply I receive from them.
Kevin and company: would a memory dump or anything else help resolve this, or perhaps someone else has reported this problem to you? Though, I think it's up to Conduciv to resolve.
Thanks,
Pete
|
I'll be interested to see what they're doing. Even if their software puts its own Qt libraries in the system path, it shouldn't affect Sigil. The only thing I can think of that would cause problems is if their installation software sets some Qt-specific environment variables system-wide. That would be bad.
We used to have problems with incompatible versions of OpenSSL being on the system path, but we stopped compiling OpenSSL support into Sigil's Qt on Windows to avoid that.
What would probably help the most is profiling a Sigil launch with Dependency Walker.
Thanks for the heads-up though.
P.S. I wonder if the evaluation copy of Diskeeper Home would exhibit the problem? There are no "gotchas" with installing/uninstalling the software is there? I don't want to have to setup a new virtual Windows machine just to do a little testing.