Wrong, look what MDGx did with WMP 10 from WinXP. Some files are compatible and some are NOT. What is it you didn''t grasp. The files inside SP are compatible and the ones that are not, are not included. So think before you open your trap. This is why SP is built with NT files that DO NOT rely on KernelEx. Now don't you look and feel stupid as usual?
No, I'm not wrong. I said some NT files may work under certain conditions and not work under others. Some may work perfectly. Some may not.
If an NT file works some or most of the time, that's great. You act as if I'm against using any NT files. I'm not, and I said so above. The point is:There is NO WAY TO BE 100% SURE an NT file works under ALL conditions. There are too many variables.
An NT file may work fine for X program, but not for Y program. An NT file may work fine for programs A, B, C, D, and E, but not for program F. It is physically impossible to test all programs that depend on a given file. Such things require extensive testing beyond what one person can do. I know this, I'm a "project author" too.
I hope that every single NT file
you have in your SP works under ALL
conditions. But there is no way to be certain of that.
Now, you may not have seen any problems. There may not be problems. All the files you have added may work fine until another variable is added to the equation.
What variable? Lets take KernelEx for example.
KernelEx was designed to run on a standard Windows 98/ME installation. It expects certain conditions to exist. If those conditions have been changed by the addition of another Unofficial file, then KernelEx may not work properly.
Is this your fault? NO.
Is it the KernelEx developer's fault? NO.
It is simply a side-effect of mixing two unofficial packages.
And as usual you revert to personal attacks. Which means you are unable to debate the real issue.