Reply to thread

Message

<blockquote data-quote="funkstar" data-source="post: 532029" data-attributes="member: 14311">Well obviously there are things you do need that have been stripped out, if MP didn't need them you wouldn't be getting errors <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />A good one to start with is adding IE back in. Although IE is a browser, it isn't self contained like FF or Opera, it makes its components available to anything else that wants to use them. this is a good thing. Why have a dozen different implimentation of the same HTTP component (for example) on a system when the one bundled with Windows works? Saves developers a lot of time. A good example of how it can work is the MP installer could just tell Windows &quot;get me this XML file&quot; so Windows goes to the now non-existant IE components to ge tthe file. We get an error. Say that worked though, the MP installer would then tell Windows to &quot;parse this XML file&quot;, well the XML engine could have been an IE component you removed. We get an error.You can see a pattern emerging here. This is why the MP developers don't support anything other than a fully patched Windows install, it just becomes a nightmare and a waste of their time. If other forum members want to pitch in and help out then thats different. But like getting MP installed on Windows server 2003/2008, forum members are on their own with non-standard installations.</blockquote>

[QUOTE="funkstar, post: 532029, member: 14311"] Well obviously there are things you do need that have been stripped out, if MP didn't need them you wouldn't be getting errors :) A good one to start with is adding IE back in. Although IE is a browser, it isn't self contained like FF or Opera, it makes its components available to anything else that wants to use them. this is a good thing. Why have a dozen different implimentation of the same HTTP component (for example) on a system when the one bundled with Windows works? Saves developers a lot of time. A good example of how it [I]can[/I] work is the MP installer could just tell Windows "get me this XML file" so Windows goes to the now non-existant IE components to ge tthe file. We get an error. Say that worked though, the MP installer would then tell Windows to "parse this XML file", well the XML engine could have been an IE component you removed. We get an error. You can see a pattern emerging here. This is why the MP developers don't support anything other than a fully patched Windows install, it just becomes a nightmare and a waste of their time. If other forum members want to pitch in and help out then thats different. But like getting MP installed on Windows server 2003/2008, forum members are on their own with non-standard installations. [/QUOTE]

Verification