Microsoft Windows 98 Year 2000 Update Readme File Contents

• Microsoft Windows 98

SUMMARY

This article contains a copy of the information in the Y2kinfo.txt file included in the Microsoft Windows 98 Year 2000 Update.

MORE INFORMATION

************************************************************************

Microsoft Windows 98 Year 2000 Update README File November 1998

CONTENTS

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

If You Reinstall Windows 98

I. Installation Notes

You need 20 MB free disk space to install 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.

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.

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

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

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 (vmy2k.exe) 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.
   
   
   • Click Product Guide.
   
   
   
   • In Compliance Information for Microsoft Products, select Microsoft OLE DB. Under Data Access, select Microsoft OLE DB.
   
   
   
   • Click Search, and the latest compliance documentation will be displayed.
   
   
   

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.

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

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/

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

Additional query words: 98

Keywords          : kbreadme kb2000 win98 
Version           : WINDOWS:
Platform          : WINDOWS 
Issue type        : kbinfo 

Last Reviewed: June 16, 1999