Yes. TimeWise's data structures are 100% Year 2000 compatible, so all information in TimeWise will be useful into the next millenium, without any hiccups. TimeWise 6 for Windows and TimeWise for Macintosh have an interface designed for use in the months leading up to the year 2000 and the years beyond. For a full statement on TimeWise year 2000 compliance, read our TimeWise Year 2000 Disclosure.

Yes! GAGEtrak is compliant with the millennium change. Just set the year value to be 4-digits in your Windows control panel and the program will honor the setting. Actually, all date formats are supported (i.e., "2004/11/02", "11/02/2004", etc.) and can even be run in a mixed mode on a network (i.e., if some users prefer dates to be displayed one way and other users prefer their dates in another way).

Apache internally never stores years as two digits. On the HTTP protocol level RFC1123-style addresses are generated which is the only format a HTTP/1.1-compliant server should generate. To be compatible with older applications Apache recognizes ANSI C's asctime() and RFC850-/RFC1036-style date formats, too. The asctime() format uses four-digit years, but the RFC850 and RFC1036 date formats only define a two-digit year.

Whew! After a long delay, I am returning to the FAQ. A lot of information has been out-of-date for some time, so I felt I had to at least get us back in place. I have noticed a growing number of sites out there that have copied all or part of my FAQ. While I should be angered at what is clearly a violation of copyright, I'll choose to be understanding and a little flattered. Honestly, people, you could at least mention that it's my work, you know.

Yes. GMT is written in ANSI C and is POSIX and Y2K compliant. Furthermore, it can read time-series data that are "Y2K-challenged" (i.e., 2-digit years only).

H1. Update: WIth the release of Version 5, information on rolling regressions has been included in the RATS documentation See pages 118 and 251 in the RATS User's Guide for details. For those of you using an older version, or who want more information, please refer to the following: This is very easy in RATS, if you remember that RATS allows you to use dates as loop indexes, and in expressions of the form "entry plus integer" or "date plus integer" (e.g.

Yes. All REALHAMSTER software and firmware has been thoroughly checked and verified for Year 2000 compliance. You may bugger REALHAMSTER anytime, safe in the knowledge that it won't suddenly forget your willy size at the start of the new millenium

Yes. Even though QuestView is a database file access utility, it has been designed to be Y2K Compliant. Yes. There is a conversion utility provided within the latest release versions. The instructions are available with the installation instructions. The latest release is 7.4/8.4. The command is STRVIEWCVN.

We offer now a solution to install a Windows 2000 driver under Windows XP for all Scanners (not for Cameras). After choosing your language there is shown a dialog box. In this dialog box please choose the driver you downloaded from internet and follow the instructions on the screen If you have a Windows 2000 driver on a CD-ROM, please insert the CD-ROM into your CD-ROM drive and cancel the automitic running installation on language selection.

Yes, HAI automation controllers are year 2000 compliant. There is no necessary action to be taken when the calendar rolls over to the year 2000.

WISP Version 4.2.00 and later are Year 2000 compliant. However, the applications migrated by WISP may not be. See the document "WISP Toolkit Year 2000 Compliance" for a complete description.

Yes! The only thing File-Ex does with dates is display them in its "Information" line, and it gets these dates directly from the operating system.

The answer to this question can be found in the OpenDX license, which is included in the OpenDX distribution in the file LICENSE. You can also find it on the Web at <http://www.research.ibm.com/dx/srcDownload/license.html>.

Whew! After a long delay, I am returning to the FAQ. A lot of information has been out-of-date for some time, so I felt I had to at least get us back in place. I have noticed a growing number of sites out there that have copied this forum and my ideas. Fuck them. While I should be angered at what is clearly a violation of copyright, I'll choose to be understanding and a little flattered.

Yes. The AquaCalc is not dependent on the year value for any of its calculations and is therefore not affected internally by the Y2K problem. The current date format of the AquaCalc output is MM/DD/YY and when the clock turns over at midnight on December 31, 1999 the AquaCalc date will be 01/01/00. The AquCalc can be purchased with two different versions of firmware: The Basic (G) series, and the more advanced Plus (H) (formerly known as the Professional Series).

DBI has no knowledge of understanding of what dates are. Therefore, DBI itself does not have a Year 2000 problem. Individual drivers may use date handling code internally and therefore be potentially susceptible to the Year 2000 problem, but this is unlikely. The Perl5 Database Interface is FREE software. IT COMES WITHOUT WARRANTY OF ANY KIND. See the DBI README for more details. However, some organizations are providing either technical support or training programs on DBI.

DS12C887 Year 2000 compliant devices are available for world-wide shipment. For complete information about the DS12C887 and the devices it will replace, see Dallas Semiconductor Devices.

The short answer is, yes! For more details, please see our compliance statement at: http://www.elsop.com/linkscan/year2000.html.

lt;P>All date and time information is stored internally as a 32-bit UNIX&reg; time value which will roll over early in 2038. When date information is displayed or logged, a 4-digit year is generated using the standard UNIX date and time functions.

far as we know screen has no Y2K problem, but as the GPL says, even if there is a problem, WE ARE NOT LIABLE and THERE IS NO WARRANTY. See also the y2k-article that Tom Christiansen wrote for perl5. Much of it applies to screen as well. shell -$SHELL to your ~/.screenrc file. this makes the shells think that they are login shells and have to do full initialisation. For csh-like shells this means, that both .login and .cshrc files will be loaded.