WfW 3.11 Jahr 2000 Kompatibilität


Windows for Workgroups 3.11 (German) - 16-Bit Win

Product Summary
Product: Windows for Workgroups
Version: 3.11
Category: Compliant#
Operating System: 16-Bit Win
Language: German Release Date: 01 Nov 1993
Operational Range: 04 Jan 1980 - 31 Dec 2035
Prerequisites: None (optional WINFILE.EXE, see below)
Product Dependencies: Microsoft DOS version 6.22 (no updates available)
Clock Dependencies: System Clock
Last Updated: 18 May 1999

Product Details
Updates- There is an updated version of WINFILE.EXE.

Problembeschreibung:

Der Datei-Manager (Winfile.exe) von Windows für Workgroups 3.11 zeigt das Dateierstellungsdatum falsch an, wenn das Datum größer oder gleich 1.1.2000 ist.

Lösung:

Um das Problem zu beheben, tauschen Sie bitte die alte Winfile.exe im Windows-Verzeichnis (C:\WINDOWS) gegen diese neue Version aus.

Datei-Informationen:

   Datei:                     WINFILE.EXE
   Zuletzt geändert am:       20.03.97
   Dateigröße:                173,728 Bytes
   Dateiversion:              3.11

For more information see Knowledge Base article at http://www.microsoft.com/intlkb/germany/support/kb/d34/d34672.htm.

This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remain Compliant# with or without this update.

Description of how the product handles dates:
Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980.

2-digit shortcut handling:
This is a function of the underlying MS-DOS operating system.
More information on MS-DOS issues:

MS-DOS cannot display a 4-digit date using the DIR command (internal to COMMAND.COM).
MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "invalid date" error.
The MS-DOS DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date.

Product issues:
The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date.
Microsoft is investigating the Date/Time control panel issue. No fix is available at this time.

Common date usage errors:
Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine.

Testing guidelines and recommendations:
Test BIOS to ensure that it handles the rollover, using the following steps:

Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information.


 

Legend of Symbols:
* Indicates the product is compliant, with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document.
# Indicates the product is compliant, with acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality (ex: data integrity) or stability (ex: reliability) of the product.
+ Indicates the product is compliant, with pending software updates. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

 

Thursday, July 15, 1999

© 1999 Microsoft Corporation. All rights reserved. Terms of use.

This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act.