Strange installation issues with VS X8: Haali & DotNetFXSP1

[tanguero]

I've installed VS X8 on my Windows XP system and it seems to be working fine in most things as far as I've tried it so far. However, I have questions on two strange (to me) installation quirks:

1. An undocumented "Haali Media Splitter" program group was installed with three entries:
- GDSMux (which, if you open it, brings up a small DS Mux window with 6 tabs, none of which is self-explanatory);
- Media Splitter Settings (which shows you various settings but doesn't let you change any, and is not self-explanatory to me either);
- Uninstall (which is indeed self-explanatory).
A Google search on Haali Media Splitter says that it's a "DirectShow splitter which offers support for almost all Matroska elements ...," but my question is: What function does it have in VS? If it is a library for Matroska processing used internally to VS, why is there a program group? If it's a standalone program (as suggested by the presence of the program group), what does it do and what would I used it for?

2. When installation the 3Bonus file, at the end of the installation a program DotNetFXSP1 (included in the Corel installation package) was automatically run as well, which offered to "restore Microsoft .NET framework 3.5 SP1 to its original state." What does this do and why is it necessary? "Original state" from what? What side effects can it have on other programs that use the .NET 3.5 framework? Why is Corel even touching these OS files, much less "reverting them to previous states"?

Any insight on this would be appreciated.

[Ken Berry]

No idea about 2, though I imagine it might be there in case you want to uninstall X8, and it can revert to an earlier NET framework should you want. But I imagine doing so would indeed affect other programs which rely on that updated NET framework version.

As to Haali, the Matroska codec .MKV is available in X8 for the first time. So clearly those files are associated with the ability of X8 to process MKV files. Beyond that, though, like 2, I have no idea what their specific function might be.

[tanguero]

No idea about 2, though I imagine it might be there in case you want to uninstall X8, and it can revert to an earlier NET framework should you want. But I imagine doing so would indeed affect other programs which rely on that updated NET framework version.

But the offer to "restore .NET framework to original state" is not made upon UNinstalling X8, but rather upon INSTALLING it, which brings up the question as to what "original state" even means in this context, and what possible "sabotage" is being done by the X8 installer. (I have not seen any immediate ill-effects, but of course this is not a reassurance that there isn't a hidden time-bomb in there somewhere.)

Corel tech support was zero help (surprise ...), either not understanding the issue at all, or pretending not to out of laziness in actually having to ask someone in the development team, saying only that (paraphrased), ".NET framework is a Microsoft product so go ask them," and when I pointed out (with the hope that the reply would go to another rep--it didn't ...) that my question was in fact why Corel was touching it and why, i.e., what Corel was doing with it, the answer was (and said rep took 3 days more to come up with this gem of a non-sequitor), "Please be advised that there is no information for disclosure regarding the decision on product features--the decision to retain or remove a product feature is under the prerogative of the product development team for VideoStudio Pro." Huh? (Yes, we know that you have one of your function keys programmed to spit out this text for all the complaints on removed features, but the normal procedure should be to read the question first, no?)

[tanguero]

OK, a second attempt with Corel Tech Support gave me good answers (a better strategy than replying to an old case where you're getting stonewalled is to create a new case if you get stuck with someone who doesn't really seem to understand, so you have a chance of getting someone who does). In this case "Austin" came through with very prompt, thorough and credible replies to both questions. Credit given where due! Here are the responses (with minor or no editing):

DotNetFXSP1 Issue:

"The .Net Framework will only configure the installed modules for the Videostudio Application. If the installer is reverting the components back to factory settings, then there is a section that was damaged or a misconfiguration was performed by another application, already installed. The installer doesn't modify any of the settings, but adds onto it. Approximately 83.5% of all written applications utilize the Microsoft .Net framework in it's operation. Each individual installation program will configure the component to compile a framework needed for that program. One of the core features of .Net or Visual C++, is that the base code can be configured to suit the applications needs. No modifications are done to these components, unless it's a governed Microsoft update which specifically targets a vulnerability or crash issue."

So as I understand it, the DotNetFXSP1.exe installation file basically configures the "local instance" of .NET Framework 3.5 needed by Video Studio and the "revert to initial setting" was apparently to repair the base .NET Framework installation prior to configuring the said local instance.

Haali Media Splitter Issue:

"The Haali Media Splitter, also known as Matroska Splitter, is a tool for separating the video and audio streams within a video file. It is often used by freeware video software, and may be automatically installed by that software when it is installed. In our case, this addition, allows Videostudio to read, decode, import and modify MKV file types. It does not though, allow for the export to this file type. It's a supplemental application which is used internally within Videostudio. Having it installed also, though, will allow you to play MKV files in Media Player. It's nothing more then a codec and its interface. Nothing to really adjust/alter settings-wise."

P.S. My faith in Corel Tech Support is partially restored. Some parts of it are actually pretty good, though there is a luck-of-the-draw component and sometimes some persistence required.