Subject: Re: msconfig command
Date: Fri, 30 Apr 2004 13:55:46 -0600
Greetings --
Well....., In a way, it _is_ that Win2K doesn't truly support
MSConfig.exe.
If you copy the Win98 version of MSConfig.exe to a Win2K machine,
it'll run and do pretty much as intended, but with error messages that
must be by-passed.
If you copy WinXP's version of MSConfig.exe to a Win2K machine,
it'll normally run without error messages, and appear to function
properly, but will often leave orphaned registry entries, because
Win2K lacks the registry keys to properly deal with all of MSConfig's
options.
And this ignores the fact that whomever initially provides the
MSConfig executable, whichever version, is apparently violating the
respective OS's EULA by separately distributing OS components. Or can
we assume, as you post as a Microsoft employee, that you've checked
with Microsoft's legal department about the "legitimacy" of
distributing Microsoft OS components to people who may well not have a
license to use the OS from which the component originates?