>Currently, after visit M$ website,
>I wonder a BAD FACT!
>
>There is a 2nd patch for Win 98 on Y2K patch.. named Y2k2
>But it is English Version ONLY.
>The foreign country do NOT have download yet!!
>

You'll need to take that up with Microsoft; there's nothing anyone other than MS can do as far as making additional operating system patches available for different version of Windows.

>Since I have used both Chin Win 98 y2k patch and Chin Win 95 y2k patch,
>the fixed filename can be seened during installation!
>
>If there is a y2k2 patch,
>it seem that even the y2k2 patch for English Win 95 has NOT created...
>

The patch for Win98 may not be needed for Win95; the two pieces of code have diverged considerably from their common code base. The patch may apply to features only available within Win98.

>In the same way, There is ONLY English Office SR-1 to download,
>but foreign language not yet..

If you're talking about Office 97, SR-2a has been out for a considerable amount of time. Again, you'll need to contact Microsoft regarding foreign language versions of patches and enhancements. Again, some of the code for foreign language versions diverges afrom the base code for the US distribution, so patches and Service Releases are not identical.

Again, complaining here isn't going to address the problem; your best bet is to contact Microsoft's Tech Support. My experience is that they have been very responsive and informative regarding foreign language support for registered users (my company is owned by a Japanese firm, so we have some experience with supporting foreign language versions of Win9x. In our case, we elect to carry a full MSDN Universal Subscription with the Internation Pack II options, which includes the Far Eastern versions of products and patches as well as the US/English versions. The roughly $2000/year is a relatively small price to pay for being kept current AFA operating systems, development tools and Office products.)

You may not like the responses they give. There are alternatives to the MS product line if you feel that Microsoft's support is inadequate; in most cases, things like office suites have competitive upgrade deals that are very attractive as long as you're currently a registered owner of a competing package. Corel and Lotus both have office suites that compete head to head with MS Office, and they may be more willing to address your issues, since they'd really like to establish a foothold in the office automation business that MS can't erode. Their best chance is to address areas where the user community feels that MS is weak, and obviously, you feel that MS support for the foreign language office products is just that.

>>
>Okey, on the protective way, does anyone give good suggestion for the
>repair programming group in Y2k Emerengy Center!?
>In case, we can't get all the patch to fix y2k bugs on the M$ product,
>what should repair programming group do?!
>

At a minimum, I'd run compliance testing to see what issues have not been resolved. We had to undergo rigorous Y2K certification because of requirements from some of our large business partners; in meeting those requirements, we had to identify areas that couldn't be dealt with in-house, and describe detgailed wortkarounds. Since our Y2K efforts started nearly 18 months ago, and many of the patches were not available until very recently, we had to identify and find workarounds to many problems that have stopped being problems.

It's key to identify what your vulnerabilities are, and if you have liability for Y2K related problems, relying on outside vendors to fix the problems for you is probably not going to work.

>Because even have a good Y2k emerengy Center to maintain the basic
>service of a company, it still a temperately handler.
>The More important job is to ensure the repair programming group can
>fix the bugs as fast as possible especially at Jan 2000.
>This makes programmers really headache!!

If you have Y2K problems, I can assure you that they won't wait until January 1, 2000 to begin causing problems. We started encountering Y2K issues 2 years in advance of that date, since our budgeting process opened up issues as sson as the January 2000 budgets were being built. At this point, if you're just starting to develop your Y2K strategies, you're probably too late to avoid at least some of the potential issues. I'd recommend bringing in an outside firm to do a Y2K audit for you (we brought in Price Waterhouse, a large US accounting and consulting firm, since we had requirements to provide detrailed reporting to our large customers, some of whom would not place orders that would eithe be filled after January 1, 2000, or where bills would fall due after January 1, 2000. the audit was very expensive, but it did find a number of vulnerabilities that we had not anticipated, and getting the audit done early gave us time to correct the vulnerabilities that were found before they caused us grief. While the consutation and audit was expensive, the costof not having it done would've been much greater.)

I'd guess that most companies do not have the staff on-hand to do an adequate self-audit; that certainly proved to be the case for us.