
Microsoft Year 2000 Readiness Disclosure & Resource Center |
 |
 |
 | OS/2 1.3 (English) - OS/2
Product Summary |
Product: OS/2 Version: 1.3 |
Category: Not Compliant Operating System: OS/2 |
Language: English |
Release Date: N/A |
Operational Range: |
- |
Prerequisites: |
None |
Product Dependencies: |
None |
Clock Dependencies: |
Functional RTC/BIOS |
Last Updated: |
13 Sep 1999 | |
Product Details |
This document summarizes the results of Year 2000 compliance tests for the OS/2 V1.3 Operating System software package.
How OS/2 version 1.3 handles dates:
OS/2 version 3.1 rolls over the date from 12-31-1999 to 1-1-2000, 2-28-2000 to 2-29-2000, and 2-29-2000 to 3-1-2000.
OS/2 version 3.1 Backup and Restore utilities:
- The /d option of the Backup utility does not accept "00" as a valid year.
- The combination of /b and /a (or /e) options of the Restore utility do not restore the necessary backup files when the range of years crosses the year 2000.
- The Backup and Restore utilities work as expected as long as no date & time options are specified in Backup and Restore command line arguments. For example, Backup *.* a: /s. or Restore a: c: /s.
The OS/2 File Manager SEARCH function does not work with æBEFOREÆ, æONÆ and æAFTERÆ criteria when given a search date of 1-1-2000 or 12-31-35:
When given 1-1-2000
- æBEFOREÆ search results donÆt include files with dates before 1-1-2000.
- æONÆ search results doesnÆt include files dated 1-1-2000.
- æAFTERÆ search results include files dated earlier than 2000.
When given 12-31-35
- æBEFOREÆ search results do not include all files dated before 12-31-35.
- æONÆ search results do not included files dated 12-31-35.
- æAFTERÆ search results include files dated before 12-31-2035.
On dual boot machines, the DOS boot does not keep the correct date & time from previous OS/2 date & time:
When the date in the OS/2 session is set to 12-31-99 and the time is set to 23:59:30 and then the system is booted to DOS, the date may not roll over to 2000 or the time may be incorrect.
The following systems produce expected results (i.e. no known issues):
Common date usage errors:
OS/2 v1.3 allows the user to make a fileÆs last modification date earlier than the fileÆs creation date. Also in OS/2 v 1.3, a fileÆs last access date can be made earlier than the fileÆs creation date.
General Testing guidelines:
Please Note: This information is provided to you as general information and not as an exhaustive testing plan for this product or any other product. The general guidelines are not requirements of Microsoft and are subject to the disclaimer as the end of this document. By providing these general guidelines, Microsoft does not assume any responsibility you may have for planning for the transition to the Year 2000 and makes no representation about what effect following or not following them will have on any liability that may be asserted to arise out of that transition
In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas can be looked at to verify date handling.
Timer rollover with Y2K problem PC bios
- Under OS/2 window, type date 12-31-99 and time 23:58:0, wait 4 minutes, and check that date & time rolls over to 1-1-2000.
- Under OS/2 window, type date 2-28-00 and time 23:58:0, wait 4 minutes, and check that date & time rolls over to 2-29-2000.
- Under OS/2 window, type date 2-29-00 and time 23:58:0, wait 4 minutes, and check that date & time rolls over to 3-1-2000.
- Under OS/2 Full screen mode, repeat step 1, 2, and 3 to check that date and time rolls over correctly.
- Under DOS session of OS/2, repeat step 1, 2, and 3 to check date & time rolls over correctly.
Test cases for OS/2 File manager under PM
The following dates are suggested for testing: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036
- æCreateÆ files with above dates
- æAssociateÆ e.exe to those files with above dates
- æMoveÆ those files with above dates on Hard disk (FAT16 and HPFS system), 5 ╝ floppy diskette, 3 ╜ floppy diskette
- æCopyÆ those files with above dates from hard disk to hard disk, 3 ╜, and 5 ╝ floppy diskette; from 5 ╝ floppy to hard disk, 3 ╜, and 5 ╝ floppy diskette; from 3 ╜ floppy diskette to hard disk, 3 ╜, and 5 ╝ floppy diskette.
- æChangeÆ flags (A, R) of files with above dates on hard disk, 3 ╜, and 5 ╝ floppy diskette.
- æRenameÆ those files with above dates on hard disk, 3 ╜, and 5 ╝ floppy diskette.
- æDeleteÆ those files with above dates on hard disk, 3 ╜, and 5 ╝ floppy diskette.
- æCreate DirectoryÆ those directories with above dates on hard disk, 3 ╜, and 5 ╝ diskette.
- æPropertiesÆ checking with those files with above dates on hard disk, 3 ╜, and 5 ╝ diskette.
- æSearchÆ those files with above dates on hard disk, 3 ╜, and 5 ╝ floppy diskette.
- æSortæ those files by last modification with above dates on hard disk, 3 ╜, and 5 ╝ floppy diskette
- æSortæ those files by created with above dates on hard disk, 3 ╜, and 5 ╝
- æSortæ those files by last access with above dates on hard disk, 3 ╜, and 5 ╝ floppy diskette floppy diskette
Note that æSearchÆ does not behave as expected on 1-1-2000.
Test cases for OS/2 File manager under PM
The following dates are suggested for testing: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036
- æDATEÆ command with 2 digit years from above dates
- æDATEÆ command with 4 digit years from above dates
- æDATEÆ command with 2 digit and 4 digit years fails on 2-29-2001
- æTIMEÆ command with 2 digit years from above dates
- æTIMEÆ command with 4 digit years from above dates
- æCOPY CONÆ command that can create files with above dates on Hard disk (FAT16 and HPFS system), 5 ╝ floppy diskette, 3 ╜ floppy diskette
- æChcpÆ command with above dates
- æChdirÆ command with above dates
- æClsÆ command with above dates
- æCreateDDÆ command with above dates
- æDetachÆ command with above dates
- æDirÆ command with above dates
- æDiskcacheÆ command with above dates
- æDiskcompÆ command with above dates
- æDiskcopyÆ command with above dates
- æDpathÆ command with above dates
- æEauitlÆ command with above dates
- æEdlinÆ command with above dates
- æLabelÆ command with above dates
- æExitÆ command with above dates
- æKeysÆ command with above dates
- æMkdirÆ command with above dates
- æModeÆ command with above dates
- æPathÆ command with above dates
- æPromptÆ command with above dates
- æRecoverÆ command with above dates
- æRmdirÆ command with above dates
- æSetÆ command with above dates
- æStartÆ command with above dates
- æSyslogÆ command with above dates
- æTreeÆ command with above dates
- æTypeÆ command with above dates
- æVerÆ command with above dates
- æVerifyÆ command with above dates
- æVolÆ command with above dates
- æCreateÆ files with above dates
- æMoveÆ those files with above dates on Hard disk (FAT16 and HPFS system), 5 ╝ floppy diskette, 3 ╜ floppy diskette
- æCopyÆ those files with above dates from hard disk to hard disk, 3 ╜, and 5 ╝ floppy diskette; from 5 ╝ floppy to hard disk, 3 ╜, and 5 ╝ floppy diskette; from 3 ╜ floppy diskette to hard disk, 3 ╜, and 5 ╝ floppy diskette.
- æRenameÆ those files with above dates on hard disk, 3 ╜, and 5 ╝ floppy diskette.
- æDeleteÆ those files with above dates on hard disk, 3 ╜, and 5 ╝ floppy diskette.
- æCreate DirectoryÆ those directory with above dates on hard disk, 3 ╜, and 5 ╝ diskette.
Test cases for OS/2 System Editor E.EXE
The following dates are suggested for testing: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036
- Invoke system editor e.exe to open the files that were created with above dates, and then modify the content of the files and use æsaveÆ/Æsave asÆ the files while system date is one of above date.
- Use associate to associate system editor e.exe to these files, and check whether it will invoke system editor e.exe when double clicks the file under file manager.
Test cases for OS/2 utilities under PM
The following dates are suggested for testing: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036
- Use æMOUSEÆ to change date
- Use æKeyboardÆ to change date
- Test random date on control panel
- æCopy Disk æ with above dates
- æCompare filesæ with above dates
- æLabelæ with above dates
- æFormatæ with above dates
- æCHKDSKæ with above dates
- Make sure that æCHKDSKæ with above dates will create .CHK files.
- æFixed Disk utilityæ with above dates
- æPrintÆ those pictures file with above dates
- æDisplayÆ those picture files with above dates
- æConvertÆ those picture files with above dates
- Added Font file under control panel
- Delete Font file under control panel
Test cases to verify the day of week under OS/2
- Verify day of week after 1-1-00, test following dates: 1/1/00, 1/2/00, 1/3/00, 1/4/00,1/5/00
- Verify day of week before 2-29-00, test following dates: 2/20/00, 2/21/00, 2/22/00, 2/23/00, 2/24/00, 2/25/00, 2/26/00, 2/27/00, 2/28/00, 2/29/00
- Verify day of week after 2-29-00, test following dates: 3/1/00, 3/2/00, 3/3/00
- Verify day of week before 1-1-01, test following dates: 12/27/00, 12/28/00, 12/29/00, 12/30/00, 12/31/00
- Verify day of week after 1-1-01, test following dates: 1/1/01, 1/2/01, 1/3/01, 2/1/01
Test cases for OS/2 toggles the boot up from DOS and OS/2
The following dates are sugegsted: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036
- Set date to be above date, then do boot /dos and c:\os2\boot /os2, à
- Under OS2, Set date to be 12-31-99 and time 23:59:30, then type boot /dos to switch boot from DOS. After boot up from DOS, then check the date and time
- Under DOS, Set date to be 12-31-99, and time 23:59:30, then type c:\os2\boot /os2 to switch boot from OS2. After boot up from OS2, then check the date and time
Note the following issue:
- When it switch boot up OS2 from DOS under dual boot, OS2 handles date and time correctly.
- When it switch boot up DOS from OS2 under dual boot, DOS did not handle date and time as expected. When date shall roll over from 12-31-99 to 1-1-2000, the result can be 1984 or 1-1-2000. When date is year 2000 such as 2001,or 2035.
Test cases for OS/2 backup and restore utilities
The following dates are suggested for testing: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036
- Backup and restore files on above dates in general
- Backup files on above dates with particular date with the combination of the following options: /d, /t, /s, and /l.
- Restore files on above dates with particular date with the combination of the following options: /b, /a, /e, /L,/m.
Note unexpected results.
The /d option of backup utility does not accept 00 as a valid year, but it does accept 01, 34, 2000, and any two digits except 00.
The combination of /b and /a (or /e) options of restore utility doesnÆt work correctly when the ranges of years cross year 2000. The restore utility does not restore those backup files that need to be restored.
Test cases for OS/2 Lan Manager V2.20 Client connected to Windows NT 4.0 Server
The purpose of this test is to verify whether the year 2000 flaw will exist when Lan Manager v2.20 runs on OS/2 v1.3 and is connected to Windows NT4.0 server. The networking card is INTEL EthernetExpress 16TP. The time was always set to be 23:59:00 so that it rolls over to the next date. The testing dates are suggested to be 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 2-28-2004, 2-28-2008, 2-28-2012, 12-31-2035, 1-1-2036, 1-1-2079.
- Logon and Logoff from the server (Windows NT 4.0) with setting above dates and times, see any problem?
- Logon at 12-31-1999 and 23:58:0, let it stay overnight, and check any problem?
- Logon server and run net.exeà
- Change passwords when date & times are set by above date & time cases, Check the status of userÆs account, see any time stamp problem on log files?
- Send out a message when date & time are set by above date & time, Check the messages and the sequences of messages in message log file and clear message file.
- Assign the serverÆs printer to be one of OS/2 queue and check whether the print works with the serverÆs printer.
- Test the rest functions of net.exe.
The File ManagerÆs æSEARCHàÆ does not work as expected with year 2000 date.
When a file has last modification date 2-04-92, the search all file with DATE after 1-1-2000. The file with last modification date 2-04-92 shows up on result list.
Steps to Reproduce:
- Create file with last modification date before year 2000.
- Go to File Manager, Click File menu item, and then click search à
- Select æDATEÆ under search on property, Press OK button
- Key in 1-1-2000 for last modification and check æAfterÆ radio button, then do search
- Check the result list, there are files with last modification date earlier than 2000 on the list.
The File ManagerÆs SEARCH does not work as expected on search file with æBEFOREÆ, æONÆ and æAFTERÆ CriteriaÆs
Given search dates with years 2000 date (i.e. 1-1-2000 or 12-31-2000), the æBEFOREÆ, æONÆ, and æAFTERÆ searches do not produce expected results.
- Given 1-1-2000 with æBEFOREÆ search, the result list of search didnÆt include those files that are dated before 1-1-2000.
- Given 1-1-2000 with æONÆ search, the result list of search didnÆt have those files that are dated on 1-1-2000.
- Given 1-1-2000 with æAFTERÆ search, the result list of search did include those files that are dated before 1-1-2000. (Such as files that have date 12-31-98, 12-31-99).
Steps to Reproduce:
- Create files dated 12-31-98, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 1-1-2004, 12-31-35, 12-31-36 under one DIRECTORY (for easily spot the result)
- Go to File Manager, Click File menu item, and then click search à
- Select æDATEÆ under search on property, Press OK button
- Key in 1-1-2000 for last modification, under correct search directory and check æBEFOREÆ radio button, do search, and then see æCannot files or directories that match the search criteriaÆ (PMV1070)
- Key in 1-1-2000 for last modification under correct search directory and check æONÆ radio button, do search, and then see æCannot files or directories that match the search criteriaÆ (PMV1070)
- Key in 1-1-2000 for last modification under correct search directory and check æAFTERÆ radio button, do search, and then the result list includes those files with dated before 1-1-2000 such as files with date 12-31-99, 12-31-98.
The File ManagerÆs SEARCH does not work as expected on search file with year 2035 date.
Given search date with years 12-31-35 date, the search function does not work on æBEFOREÆ, æONÆ, and æAFTERÆ.
- Given 12-31-2035 with æBEFOREÆ search, the result list of search just includes some of files that are dated before 12-31-35.
- Given 12-31-2035 with æONÆ search, It cannot find files with dated 12-31-35.
- Given 12-31-2035 with æAFTERÆ search, The result list of search did include those files that are dated before 12-31-2035.
Steps to Reproduce:
1. Create files with dated 12-31-98, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 1-1-2004, 12-31-35, 12-31-36 under one DIRECTORY (for easily spot the result)
2. Go to File Manager, Click File menu item, and then click search à
3. Select æDATEÆ under search on property, Press OK button
4. Key in 12-31-2035 for last modification, under correct search directory and check æBEFOREÆ radio button, do search, and then see result list that does not include all files with dated before 12-31-35 .
5. Key in 12-31-2035 for last modification under correct search directory and check æONÆ radio button, do search, and then see æCannot files or directories that match the search criteriaÆ (PMV1070)
6. Key in 12-31-2035 for last modification under correct search directory and check æAFTERÆ radio button, do search and then the result list include those files with dated before 12-31-2035.
The DOS boot wonÆt keep the correct of date & time from previous OS2 date & time.
When OS2 was installed as dual boot, in the OS2 Session, set the date to 12-31-99 and the time to 23:59:30. Then type boot /dos and respond Yes to boot from DOS. After DOS is up, check the date and time. Sometimes, it shows 1980 for the date. When date is right 1-1-2000, the time is wrong. It shows time 12:00:03a when the correct time is 00:00:03.
Steps to Reproduce:
1. Install OS2 under dual boot with DOS
2. Under OS/2 window or full screen mode, or DOS session, set date to be 12-31-99 and time 23:59:30 Type boot /dos and respond yes to boot from DOS
3. After Boot up from DOS, then check the date and time
4. Sometimes, it displays 1980; other times it displays 1-1-2000 for the date.
The Backup /D option command does not take 00 as legal year input parameter.
- The backup utility wonÆt accept 00 as valid year 2000, but it accepts 2000, 01, or any 2 digit except 00.
- The error message is "The system cannot accept the date entered"
Steps to Reproduce:
1. Create file with date after year 2000.
2. Under the OS/2 window or full screen mode, runs Backup *.* a: /D:1-1-00
3. OS/2 Backup utility does not accept æ00Æ as a valid year. The message " SYS1036: The system cannot accept the dated entered" was shown on screen.
The Restore /b and /e option command does not work as expected when backup files are mixed with the 19xx and 2000 dates.
The restore utility doesnot restore the correct files from backup files with /b and /e options.
Steps to Reproduce:
Create the following files with specified date and time.
Date: 12-31-99 time: 9:0:0 t9909.txt
Date: 12-31-99 time: 11:0:0 t9911.txt
Date: 12-31-99 time: 14:0:0 t9914.txt
Date: 12-31-99 time: 16:0:0 t9916.txt
Date: 1-1-2000 time: 9:0:0 t0009.txt
Date: 1-1-2001 time: 8:0:0 t0108.txt
Date: 1-1-2001 time: 14:0:0 t0114.txt
Backup all files into diskette by entering backup *.* a: /s
Run restore a: /b:1-1-2000 /e:11:0:0
Only files t0009.txt and t9909.txt are restored; t9911.txt, t9914.txt, and t9916.txt files are not restored.
| |
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.
|