Internet Explorer 6.0 Sp1 Component Update 3.0 for Windows 98
in [Internet Explorer 6]
|
From: 98 Guy on 18 Dec 2009 08:48 Full-quoter MEB wrote: > HEY STUPID2. they were DESIGNED FOR NT,,, NOT 9X And isin't it amazing that they function just fine on win-9x? To the point where you have to suggest that they *might* cause some imaginary vulnerability as the only weakness or caveat to their use? And you totally disregard the significantly greater likelyhood that they might *remove* one or several vulnerabilities as that was the purpose they were created for in the first place. > now what part of they aren't designed for 9X are you friggin > missing... You can only speculate that they are not FULLY OPERABLE AND COMPATIBLE on win-9x because Microsoft will not announce that fact at this point in time if it were true. You can't claim that they were designed ONLY for win-2K's version of IE6-SP1 since you are not a Microsoft programmer or employee so you have no inside information. It could easily be the case that Microsoft need not do anything differently when compiling these files for either platform. > Hey, how about we put some C code from Linux in Windows, > think it will work... Now you're making a distinction between code that works, and code that conveys a vulnerability. It's a known fact that these files work under win-9x - you've never disputed that before. Given the fundamental differences between NT/2K and 9X in SOME aspects of their construction, these files illustrate how IE6-SP1 is very similar as executed on both platforms.
From: 98 Guy on 18 Dec 2009 21:52 MEB wrote: > http://peoplescounsel.org/ref/gen/ie_XPfiles_errors.htm Your believe that Win-98 is fatally flawed when IE6 is installed into it, because you believe that IE6 was never properly "ported" to windows 98. That is the underlying reason why you believe these IE6 win-2k patches either are not fully compatible with win-98 or can mysteriously result in new vulnerabilities. You cite the above-mentioned output from dependency walker as proof. What you don't understand is that when one installs IE7 on Win XP, dependency walker finds the same types of unsatisfied dependencies, because IE7 was created to run both on XP and on Vista. And since both are NT-Family OSes, your central argument is therefore flawed. All these missing dependencies just show that dependency walker is not a very bright piece of software. It was created before these types of dual-use files even existed and it knows nothing about them - and hence it yields false positives. You partially realize this, because you claim that not even win-2k was made properly compatible with IE6, because those same dependency walker false positives also turn up on that platform as well. But therein lies the answer - that these files ARE dual use, on both Win-98 and 2K platforms, and that dependency walker is incapable of recognizing that it should not be reporting platform-dependent unsatisfied dependencies.
From: Sunny on 19 Dec 2009 01:06 "98 Guy" <98(a)Guy.com> wrote in message news:4B2C3FE9.1916C09C(a)Guy.com... > MEB wrote: > >> http://peoplescounsel.org/ref/gen/ie_XPfiles_errors.htm > > Your believe that Win-98 is fatally flawed when IE6 is installed into > it, because you believe that IE6 was never properly "ported" to windows > 98. Not according to Microsoft, their download page for IE6 says otherwise :-) "System Requirements Supported Operating Systems: Windows 2000; Windows 98; Windows ME; Windows NT; Windows XP Service Pack 1" I use IE6 on my Win98SE PC, and have done since it came out. http://www.microsoft.com/downloads/details.aspx?FamilyID=1e1550cb-5e5d-48f5-b02b-20b602228de6&DisplayLang=en > That is the underlying reason why you believe these IE6 win-2k patches > either are not fully compatible with win-98 or can mysteriously result > in new vulnerabilities. > > You cite the above-mentioned output from dependency walker as proof. > > What you don't understand is that when one installs IE7 on Win XP, > dependency walker finds the same types of unsatisfied dependencies, > because IE7 was created to run both on XP and on Vista. And since both > are NT-Family OSes, your central argument is therefore flawed. All > these missing dependencies just show that dependency walker is not a > very bright piece of software. It was created before these types of > dual-use files even existed and it knows nothing about them - and hence > it yields false positives. > > You partially realize this, because you claim that not even win-2k was > made properly compatible with IE6, because those same dependency walker > false positives also turn up on that platform as well. But therein lies > the answer - that these files ARE dual use, on both Win-98 and 2K > platforms, and that dependency walker is incapable of recognizing that > it should not be reporting platform-dependent unsatisfied dependencies. Wonder how MEB will take Microsoft to task for claiming IE6 is compatible with : (using MEB typespeak shouting) "WINDOWS 2000; WINDOWS 98; Windows ME; Windows NT; Windows XP Service Pack 1"
From: MEB on 19 Dec 2009 12:05 On 12/18/2009 09:52 PM, 98 Guy wrote: > MEB wrote: > >> http://peoplescounsel.org/ref/gen/ie_XPfiles_errors.htm > > Your believe that Win-98 is fatally flawed when IE6 is installed into > it, because you believe that IE6 was never properly "ported" to windows > 98. WRONG AS USUAL. The files of the supposed discussion ARE NOT DESIGNED FOR Win9X... That you and your like STILL don't get that shows your mental abilities to comprehend the world at large. > > That is the underlying reason why you believe these IE6 win-2k patches > either are not fully compatible with win-98 or can mysteriously result > in new vulnerabilities. > > You cite the above-mentioned output from dependency walker as proof. > > What you don't understand is that when one installs IE7 on Win XP, > dependency walker finds the same types of unsatisfied dependencies, > because IE7 was created to run both on XP and on Vista. And since both > are NT-Family OSes, your central argument is therefore flawed. All > these missing dependencies just show that dependency walker is not a > very bright piece of software. It was created before these types of > dual-use files even existed and it knows nothing about them - and hence > it yields false positives. > > You partially realize this, because you claim that not even win-2k was > made properly compatible with IE6, because those same dependency walker > false positives also turn up on that platform as well. But therein lies > the answer - that these files ARE dual use, on both Win-98 and 2K > platforms, and that dependency walker is incapable of recognizing that > it should not be reporting platform-dependent unsatisfied dependencies. No, stupid, as I have repeatedly advised, just as IE 5.5 was not completely compatible with Win95, IE6 was not designed nor compatible with Win98. It is the *transitional browser* created by Microsoft as a *show case* for the intended OS, XP. These are two entirely different platforms. ONE is an old DOS based [mostly from CP/M and BASIC coding languages]; where the other is a Posix hack [a Unix hack, like Linux]. The single commonality is the programming code in the latter years. That would generally be one of the Cs. However the code IS NOT cross platform, it is specifically coded to the workings of the intended OS. To make it cross-platform, the programmer MUST include the proper coding FOR THE INTENDED OSs in instances like this. Now do you see how I lead you right to this. You have already said installing Linux code into Win9X is NOT proper and would cause issues; yet you espouse upon doing so with THESE files, merely because these files can be installed. -- MEB http://peoplescounsel.org/ref/windows-main.htm Windows Info, Diagnostics, Security, Networking http://peoplescounsel.org The "real world" of Law, Justice, and Government ___---
From: 98 Guy on 19 Dec 2009 21:14
MEB wrote: > You forgot the era, AND the intent of creating the browser. Its a > transitional browser, as far as Microsoft was concerned, Win98 > was moving to EOL... What a joke. IE6 was released in August 2001, only 2 years after Win-98se. Only in your twisted mind could that time-frame be classified as "moving to EOL". The fact is that in Microsoft's eyes, every OS is moving toward EOL the day it's released. |