by Michael S. Kaplan, published on 2006/07/11 14:31 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/07/11/662550.aspx
Well, as the Windows 98 page says officially:
July 11, 2006 will bring a close to Extended Support for Windows 98, Windows 98 Second Edition, and Windows Me as part of the Microsoft Lifecycle Policy. Microsoft will retire public and technical support, including security updates, by this date.
Existing support documents and content, however, will continue to be available through the Microsoft Support Product Solution Center Web site. This Web site will continue to host a wealth of previous How-to, Troubleshooting, and Configuration content for anyone who may need self-service.
Microsoft is retiring support for these products because they are outdated and can expose customers to security risks. We recommend that customers who are still running Windows 98 or Windows Me upgrade to a newer, more secure Microsoft operating system, such as Windows XP, as soon as possible.
It does leave the interesting question about support for the Microsoft Layer for Unicode on Windows 95, 98, and Me Systems (MSLU). Since it only ever runs on Win9x, which is no longer supported, can UnicoWS.dll be supported?
Well, to decide that, let's see what "support" means in this context.
We have not had any security bugs reported in years, and even periodic updates were not happening much any more. So the situation in those areas would unchanged.
The MSLU newsgroup (microsoft.public.platformsdk.mslayerforunicode) has not had much traffic, but it will probably still be around (and I still watch there).
Any time someone worked with Product Support Services with an MSLU question in the past, it usually found its way to me at some point. So even if you couldn't go through PSS, you could still come here or go to the newsgroup....
And certainly if someone asks a question about MSLU here in the Suggestion Box, I'd try to answer it. Especially if were an interesting question!
So, I guess you could say that MSLU is as supported as it has been for the last few years, with whatever meager level you can ascribe to my efforts.... :-)
This post brought to you by ꇘ (U+a1d8, a.k.a. YI SYLLABLE LYRX)
Yuhong Bao on 12 Jan 2011 11:05 PM:
"Any time someone worked with Product Support Services with an MSLU question in the past, it usually found its way to me at some point. So even if you couldn't go through PSS, you could still come here or go to the newsgroup...."
Reminds me of this:
What you think about this issue?
Michael S. Kaplan on 12 Jan 2011 11:37 PM:
I don't think it's really related to MSLU support, even conceptually. In the case of Google those ARE supported technolgies and products....
Yuhong Bao on 12 Jan 2011 11:47 PM:
I was not specifically talking about MSLU, I am taking about the "Any time someone worked with Product Support Services with an MSLU question in the past, it usually found its way to me at some point. " part and mentioned the other posting as another example and asking what do you think about this issue in general?
referenced by
2011/02/05 I serve at the pleasure of the customer (except maybe when they annoy me?)
2008/07/05 They weren't on crack; they were just on a new, unknown track!
2008/02/18 How to avoid that problem of never being 'up to date'
2007/12/24 The 9.0 instructions for building MFC and the CRT to use MSLU?
2007/08/02 Help prove that I am wrong, please
2007/04/28 Testing MSLU
2007/04/10 Win9x keyboard file source?
2007/01/13 Output on customer input on MSLU's ReadConsoleInputW
2007/01/11 Having problems with MSLU?
2006/08/22 'Unicode' doesn't corrupt, but 'ANSI' can corrupt, absolutely!
2006/08/03 MSLU: some back-story, some back-formations (and no backwash)
2006/07/26 It's great to have stuff in the top 10 (sort of)
2006/07/25 Is East Asian support installed?