Searched refs:Y2K (Results 1 – 18 of 18) sorted by relevance
6 been certified by AT&T Labs as part of the "Freeware Y2K 13 Year-2000 (Y2K) readiness that were not sufficiently certified16 public as a series of "Y2K Application Updates", one update23 taking any responsibility for repairing any Y2K problems25 "Y2K Application Update". All risk of using this Y2K30 AT&T's intent is to ensure these Y2K patches are freely33 the specific changes made by Y2K to the code. Any original 41 Various Y2K updates and tests provided by AT&T Labs.54 If you find any overlooked Y2K problems, or have other strictly Y2K62 including publishing in future Y2K related release notes,[all …]
45 3) Verified ntpd works on critical Y2K dates.54 not traditional Y2K errors, would break in the year 2000.59 the Y2K repairs.63 1) Some of the Y2K repairs were to reference clock drivers that75 Non-Y2K Problems Observed:92 NOTE: Author (falsely) stated Y2K is NOT a leap year when it 95 TRUTH: ACTS will go beyond Y2K: it uses FourDigitYear % 100 values
4960 * ntpq/ntpq.c: Y2K patches5745 * scripts/stats/summary.sh (CLOCK): allow for Y2K log files
5097 * Y2K patches from AT&T5142 * Y2K patches
3 code has been also visually inspected for Y2K compliance problems.
3 * Y2K
801 31. small Y2K fix [%y in prompt would be formatted as 10 not 00 at year 2000],
759 #define Y2K 946684800 macro771 ts->tv_sec = rtc + Y2K; in ps3_gettime()
162 * A Y2K statement.
112 Studio 6.0. Included a Y2K statement in the file Y2K_INFO. All other
10 1. Is zlib Y2K-compliant?
1369 - work around lame ftpd's that don't return a correct post-Y2K
1101 The Ultrix 4.5 Y2K patch (ULTV45-022-1) has changed the resolver
1276 >>>(0x1BC.s+8) ubyte&1 1 \b,Y2K-Fix
2282 Y2K runtime checks are no longer enabled by default. Add
2360 Y2K runtime checks are no longer enabled by default. Add
5264 A recent Compaq Ultrix 4.5 Y2K patch has broken detection
22108 8001 Fix2000 PCI Y2K Compliance Card