| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| MS-DOS 6.2 (Swedish) - DOS
| Product Summary |
Product: MS-DOS
Version: 6.2 |
Category: Compliant#
Operating System: DOS |
| Language: Swedish |
Release Date: 30 Sep 1993 |
| Operational Range: |
04 Jan 1980 - 31 Dec 2035 |
| Prerequisites: |
None |
| Product Dependencies: |
None |
| Clock Dependencies: |
PC BIOS |
| Last Updated: |
19 May 1999 | |
| Product Details |
|
Description of how the product handles dates:
MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly.
2-digit shortcut handling:
If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century.
The MS-DOS« DATE command does not correctly handle 2-digit dates from 00û79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000).
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.
Product compliance 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.
External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits.
MSBACKUP: Naming conventions do not recognize "tens" place.
MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different.
For example, the following series appeared on the DOS 6.2 system:
CC60829A.FUL (No Description) was created on 8/29/1996
CC60829B.FUL (No Description) was created on 8/29/2006
CC60829B.FUL (No Description) was created on 8/29/1996
The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format.
MSBACKUP does not recognize dates greater than 1999.
MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example,
"You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?"
When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ."
For example:
CC60829B.FUL = 8-29-CZ (system date = 8/29/2006)
CC60828A.FUL = 8-28-CZ (system date = 8/28/2006)
CC10829A.FUL = 8-29-AC (system date = 8/29/2001)
Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. |
Recommendations:
There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around.
Testing guidelines and recommendations:
Some PCs do have a problem that resets 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. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information
| |
Return to Search Screen
| Legend of Symbols: |
| * |
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. |
| # |
The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
| + |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT 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 TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, 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.
|
