************************************************************************
                        Microsoft Windows 98 
                    Year 2000 Update README File
                          November 1998
************************************************************************

(c) Copyright Microsoft Corporation, 1998

This document provides complementary information to supplement the 
Microsoft Windows 98 documentation.

The Windows 98 Year 2000 Update provides Windows 98 updates to resolve 
known year 2000 issues with the Windows 98 operating system. 

For current year 2000 information regarding Microsoft products, visit 
the Microsoft Web site at http://www.microsoft.com/year2000 or call 
1-888-MSFT-Y2K or contact your local Microsoft subsidiary. 
Such information is generally available to all Microsoft customers for 
the sole purpose of assisting the planning for the transition to the 
year 2000. This document contains the information currently available 
concerning the date-handling behavior of Microsoft's products and is 
subject to change, at any time, without notice. We therefore recommend 
that you continue to check the information on the Microsoft Year 2000 
Web site regularly for any such changes.

NOTE: For the best readability, maximize the Notepad window. 

To print this file, open it in Notepad or another word processing 
program, and then click Print on the File menu.


========================================================================
CONTENTS
========================================================================
I.   Installation Notes
     A. System Requirements
     B. Downloading and Extracting the Windows 98 Year 2000 Update
     C. Before You Install the Windows 98 Year 2000 Update
     D. Useful Switches 

II.  Release Notes
     If You Reinstall Windows 98

III. What Are the Year 2000 Issues in Windows 98?

IV.  Additional Issues

V.   Microsoft Technical Support

========================================================================

I. Installation Notes
---------------------

A. System Requirements
   You need 20 MB free disk space to install the Windows 98 
   Year 2000 Update.

B. Downloading and Extracting the Windows 98 Year 2000 Update
   If you download the update from the Web site, be sure to read the 
   release notes completely before you extract and install the 
   Windows 98 Year 2000 Update. 

   After you download the Update, a compressed executable file called 
   Y2kw98.exe appears on your hard drive. This executable file contains 
   the files you need to update your system for the year 2000.

   >>> To extract the file and install the year 2000 updates:
   1. Click Start, and then click Run.
   2. In the Run dialog box, click Browse.
   3. Locate the Y2kw98.exe file on your hard drive.
   4. Click Open, and then click OK.
   5. Follow the instructions that appear on your screen.

   This Year 2000 Update  is for Windows 98 only. This Update is not 
   intended for use on and will not install on computers running 
   Windows 95,  Windows NT, or Windows 2000. For international versions 
   of Windows 98, download and install the appropriate language version 
   for your location.

C. Before You Install the Windows 98 Year 2000 Update 
   Because the Windows 98 Year 2000 Update updates your system files 
   and requires you to restart your computer during installation, you 
   should save and close all open documents and close all programs 
   before installing the Update.

D. Useful Switches
   There are several installation options available to advanced users 
   when installing the Windows 98 Year 2000 Update. You can view these 
   options at any time by clicking Start, clicking Run, typing 
   y2kw98.exe /? and then clicking OK.

   To use the optional installation parameters below, type
   y2kw98.exe <option>

   /Q - Quiet mode (skips all user prompts) - Useful for silent 
        installations in batch setups.
   /T: <full path> - Specifies a temporary working folder.
   /C - Extract files only to the folder when used also with /T - 
        Allows an administrator to download files into a specified 
        location.
   /C: <cmd> - Override install command defined by author - Not used 
        for this update.


II. Release Notes
-----------------

If You Reinstall Windows 98
If you have to reinstall the Windows 98 operating system, you will 
lose the benefits of the Windows 98 Year 2000 Update installation. 
Any time you have to reinstall Windows 98, run the Windows 98 Year 
2000 Update installation again.


III. What Are the Year 2000 Issues in Windows 98? 
-------------------------------------------------

The issues listed below are resolved by installing this Update.

1. Date/Time Picker (comctl32.dll). 
   Previously, when you set your Regional Settings in the Control 
   Panel to handle years as two digits, the Date/Time Picker function 
   did not correctly reflect the date.  This patch addresses that 
   issue.

2. Microsoft Wallet (actpmnt.ocx)
   When entering credit card information in versions of Microsoft 
   Wallet earlier than version 2.1.1383, you must enter the month, 
   day, and year for expiration dates beyond the year 2000. Otherwise, 
   information may not be handled as expected. 

   For example, entering a credit card with an expiration date of 5/01 
   is handled as May 1 of the current year. This behavior was changed 
   in Microsoft Wallet version 2.1.1383 and later.  

3. Microsoft Virtual Machine
   Year 2000 issues have been reported in connection with Java virtual 
   machines based on the Sun Microsystems Java Development Kit 
   versions 1.1.1 through 1.1.5. Applications written in Java that 
   make use of the java.txt.SimpleDateFormat class library may handle 
   4-digit dates incorrectly.

   For example, if you have a Java applet or application that uses 
   SimpleDateFormat and you enter four digits for the year, the date 
   functions may truncate the year and use only the first two digits 
   (for example, 2000 might become 20).

4. Phone Dialer applet (dialer.exe)
   The Show View Call Log option doesn't display the date properly 
   after successful completion of a telephone call. If the system 
   date is adjusted to the year 2000, the date is displayed as 100,
   101,102, and so on. 

   For example, in the year 2000, you make a call using the Dialer 
   applet. The log file created or appended to after the completion 
   of the phone connection displays the year portion of the call date 
   incorrectly, such as 101, 102, 103, and so on.

5. Time and Date applet (timedate.cpl)
   When you select the date February 29 and change the year using the 
   up and down arrows in the Date/Time Properties dialog box, the 
   calendar displays February 29 every year, whether it's a leap year 
   or not. This is a display issue in the applet.

6. Document Properties (docprop.dll)
   When you view the properties of Microsoft WordPad or Microsoft Word 
   documents and set custom date information, the year 2000 is not 
   accepted as a valid entry when typed as "00." All two-digit dates 
   are assumed to be in the 20th century (that is, 19xx). In addition, 
   if the time zone is set to the Far East, the date properties lose a 
   day when you enter the year as 2000.

7. Boot Strap (io.sys)
   If the system is started at the precise instant that the system 
   Real Time Clock (RTC) date rolls over at midnight, the system 
   clock might display an inaccurate time/date. Restarting your 
   computer corrects this problem.

   For example, turn on your computer, and then restart it at the 
   exact same moment that your system's internal clock is changing 
   from 11:59:59 P.M. to 12:00:00 A.M. Your system might display an 
   incorrect day or year until the computer is restarted and the 
   internal clock resets itself. This is a test issue and not year 
   2000 related.

8. DHCP Virtual Driver (vdhcp.386)
   Winipcfg /all - IP Leases obtained on or after 3/01/2000 are 
   reported as being obtained the previous day. The system date is 
   displayed properly but the DHCP client reports a date one day 
   prior. 

   For example, if you log on to a LAN after March 1, 2000, and you 
   run Winipcfg /all from Start\Run or Ipconfig /all from a DOS VM, 
   the lease obtained date is one day behind. After 2/28/2000, the 
   lease obtained date is one day behind the expected date.

9. Microsoft Data Access (msdadc.dll, msadce.dll)
   The msdadc.dll file is part of the OLE DB core components and a 
   part of the Microsoft Data Access Components (MDAC). If you code 
   to ADO, and your ADO Recordset includes Date data types, such as 
   adDate, adDBDate, adFileTime, or adDBTimeStamp, and you're using a 
   date format in which periods are used instead of slashes for date 
   separator (for example, 01.01.98 instead of 01/01/98), and you 
   specify a year less than 60, then Data Convert (msdadc.dll) might 
   translate your date as a time. 
   For example, 01.01.01 (January 1, 2001) might be converted to 
   01:01:01 (December 30, 1899, 1:01:01A.M.).

   For more information about OLE DB compliance, visit the Microsoft 
   Web site at http://www.microsoft.com/year2000.

   1. Click Product Guide.
   2. In Compliance Information for Microsoft Products, select 
      Microsoft OLE DB. Under Data Access, select Microsoft OLE DB.
   3. Click Search, and the latest compliance documentation will be 
      displayed.

10.Microsoft Foundation Class Library (mfc40.dll)
   After the year 2000, programs that use the COleDateTime function 
   may improperly parse a date. To view an example of this after the 
   year 2000, from Programs\Accessories\System Tools run 
   System Information (msinfo32.exe) and save the file. Open this 
   .nfo extension file, and from the File menu select Properties. 
   The date stamp may display the improper date. For example, 
   02/05/2000 may display as 2/05/100.

11.DOS Xcopy (xcopy32.mod)
   When using xcopy in real mode with the optional parameter /D:date, 
   xcopy does not accept years entered as two digits, except for the 
   years 80 through 99. The message "Invalid date" is displayed. When
   using xcopy in protected mode (from within Windows) two-digit 
   dates are accepted but are recognized as being within the 20th 
   century (02/05/01 is seen as 02/05/1901).

   

IV. Additional Issues
---------------------

A. Docprop.dll and Microsoft Office 97 
   The updated file docprop.dll is included in this Update to fix 
   potential year 2000 problems when entering custom dates in document
   properties from Windows Explorer. However, you may still experience
   date-related issues when entering custom date properties from 
   within a Microsoft Office 97 program (for example, Word 97). 
   This is a issue specific to Microsoft Office 97 and 
   Office 97 Service Release 1. To resolve such issues, download the 
   Microsoft Office 97 Service Release 2 from the Microsoft Web site 
   at http://officeupdate.microsoft.com/ 

B.Microsoft Jet Database Engine 3.5 and Microsoft Office 97
   When you try to synchronize two members of a replica set that was 
   created before the year 2000, and the current date on your computer 
   is after the year 2000, a synchronization message might appear. 
   This is because of how the expression service mishandles date 
   entries in the MSysExchangeLog table in replicas. When a replica 
   set created before the year 2000 is compacted after the year 2000, 
   exchange information relating to synchronizations after the year 
   2000 is deleted from the MSysExchangeLog table. After this 
   information is deleted, the generation information in the 
   MSysExchangeLog table and the MSysGenHistory table does not match, 
   and the replicas cannot be synchronized. 
   To resolve this issue, download the latest Microsoft Office 97 
   Service Release from the Microsoft Web site at 
   http://officeupdate.microsoft.com/ 

   For example, you have a database replica set created in the year 
   1999 using Microsoft Access 97. When the replica set is used in the 
   year 2000 and the user types dates into a table, the date is not 
   handled properly: 2000 becomes 100. Then, when the database is 
   compacted, records with these dates are discarded because they 
   appear to exceed the replica's retention period. The next time a 
   synchronization is performed, the process does not complete and a 
   message appears because entries that the log table says should be 
   there no longer exist.


V. Microsoft Product Support Services
-------------------------------------

Technical support for this component is provided in the United States 
and Canada by calling (425) 635-7222, 6:00 A.M. to 6:00 P.M., 
Pacific time, Monday through Friday, excluding holidays. For help after 
hours, visit the Options topic at http://www.microsoft.com/support. 
For customers using text telephone (TDD/TTY), technical support for 
this component is available by dialing (425) 635-4948 in the 
United States and Canada, 6:00 A.M. to 6:00 P.M., Pacific time, Monday 
through Friday, excluding holidays. For support information outside the 
United States and Canada, contact your local subsidiary. Phone numbers 
for Microsoft Subsidiaries are subject to change. For the most recent 
listing, see the Support Online Web site at 
http://support.microsoft.com/support. If there is no Microsoft 
subsidiary office in your country, contact the vendor from which you 
purchased your Microsoft product. Microsoft's support services are 
subject to Microsoft's then-current prices, terms, and conditions, 
which are subject to change without notice. 

THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED TO YOU FOR THE 
SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO 
THE YEAR 2000. THIS DOCUMENT CONTAINS THE INFORMATION CURRENTLY 
AVAILABLE CONCERNING THE BEHAVIOR OF MICROSOFT'S PRODUCTS IN THE NEXT 
CENTURY AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. WE THEREFORE 
RECOMMEND THAT YOU CONTINUE TO CHECK THE INFORMATION LOCATED AT 
http://microsoft.com/year2000 REGULARLY FOR ANY CHANGES. CONSQUENTLY, 
THE INFORMATION IN THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY 
OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR 
IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 
A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS 
SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, 
INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE 
OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS 
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES 
DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR 
CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY 
NOT APPLY. THE INFORMATION IN THIS DOCUMENT IS INTENDED TO BE READ IN 
CONJUNCTION WITH OTHER INFORMATION LOCATED AT 
http://microsoft.com/year2000, INCLUDING BUT NOT LIMITED TO THE 
DEFINITION OF THE VARIOUS COMPLIANCE RATINGS AND MICROSOFT'S 
YEAR 2000 TESTING PRACTICES.  TO THE EXTENT THE INFORMATION CONTAINED 
IN THIS DOCUMENT CONFLICTS WITH THE INFORMATION LOCATED AT 
http://microsoft.com/year2000, THE INFORMATION LOCATED AT 
http://microsoft.com/year2000 SHOULD BE CONSIDERED MORE UP TO DATE. 

ANY STATEMENTS MADE TO YOU BY MICROSOFT OR CONTAINED HEREIN IN THE 
COURSE OF PROVIDING YEAR 2000 RELATED FIXES, YEAR 2000 DIAGNOSTIC TOOLS,
OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 
INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF 
A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF 
ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR 
TARIFF.