Year 2000 technical summary
B   Windows 95/98 Y2K Issues << >>


   
B.0 Contents

  B.0     Contents  
  B.1     Windows 95/98 Y2K Issues  
  B.2     Windows 95 (English)  
  B.3     Windows 95 OSR1 (English)  
  B.4     Windows 95 OSR2 (English)  
  B.5     Windows 95 OSR2.1 (English)  
  B.6     Windows 95 OSR2.5 (English)  
  B.7     Windows 98  
   
B.1 Windows 95/98 Y2K Issues

  Only English versions of Windwos are discussed here. For information regarding non-English versions check Appendix F §F.1.1 (Vendors, Microsoft) for the complete list of Microsoft products and Y2K compliance information, and for information about obtaining patches.  
   
B.2 Windows 95 (English)

  This is the original August 1995 edition of Windows 95.
Non compliant issues:
File/Program Problem Notes
COMMAND.COM the DATE command does not function correctly workaround, use 4 digit years
WINFILE.EXE the File Manager fails to display and sort post Y2K dates correctly mostly cosmetic
SHELL32.DLL the File tab fails to display post Y2K dates correctly  
COMCTL32.DLL some functions fail if the default date format uses 2 digit years workaround, use 4 digit years
VDHCP.386 IP address lease expiry date misreported after 2000-03-01 display problem only
TIMDATE.CPL may fail to (not) display leap year days as appropriate  
DIALER.EXE assumes "19" prefix on years, displays "100" for 2000, "101" for 2001 etc.  
XCOPY.EXE fails to correctly interpret 2 digit years in the range [00-79]  
 
   
B.3 Windows 95 OSR1 (English)

  This is the original Windows 95, with Service Pack 1 applied. SP1 does not address any Y2K issues, and has the same Y2K problems as the original version. As Windows 95 OSR1 (English).  
   
B.4 Windows 95 OSR2 (English)

  As Windows 95 OSR1 (English).  
   
B.5 Windows 95 OSR2.1 (English)

  As Windows 95 OSR1 (English).  
   
B.6 Windows 95 OSR2.5 (English)

  This is Windows 95 with USB support.
Non compliant issues:
File/Program Problem Notes
COMMAND.COM the DATE command does not function correctly workaround, use 4 digit years
WINFILE.EXE the File Manager fails to display and sort post Y2K dates correctly mostly cosmetic
COMCTL32.DLL some functions fail if the default date format uses 2 digit years workaround, use 4 digit years
VDHCP.386 IP address lease expiry date misreported after 2000-03-01 display problem only
TIMDATE.CPL may fail to (not) display leap year days as appropriate  
DIALER.EXE assumes "19" prefix on years, displays "100" for 2000, "101" for 2001 etc.  
XCOPY.EXE fails to correctly interpret 2 digit years in the range [00-79]  
MSWALLET fails to deal correctly with input dates not containing a year  
JAVA VM the JDK may parse 4 digit dates incorrectly upgrade available
OLE database date coercion/conversion of year to 4 digits can behave erratically  
 
   
B.7 Windows 98

  Non compliant issues:
File/Program Problem Notes
COMCTL32.DLL some functions fail if the default date format uses 2 digit years workaround, use 4 digit years
VDHCP.386 IP address lease expiry date misreported after 2000-03-01 display problem only
TIMDATE.CPL may fail to (not) display leap year days as appropriate  
DIALER.EXE assumes "19" prefix on years, displays "100" for 2000, "101" for 2001 etc.  
XCOPY.EXE fails to correctly interpret 2 digit years in the range [00-79]  
MSWALLET fails to deal correctly with input dates not containing a year  
JAVA VM the JDK may parse 4 digit dates incorrectly upgrade available
MSDADC.DLL/OLE database date coercion/conversion of year to 4 digits can behave erratically  
MFC assumes "19" prefix on years, displays "100" for 2000, "101" for 2001 etc. in .NFO files  
IO.SYS can get an incorrect date by rebooting around midnight  
DOCPROP.DLL incorrectly deals with input dates with 2 digit years  
 

 

CONTENTS << PREV ^TOP^ NEXT >> INDEX