Ans. Yes! The SMS Release 2.0 is Y2K compliant. The product has been developed to take care of the Y2K compliance, following which no two digit year entry for dates are acceptable in the system.

Longer answer: Tcl 7.5 and 7.6p0/1 had bugs that caused them to be noncompliant with regard to how POSIX defines 2-character years. If your scripts use 2-character years, you should upgrade to a modern version of Tcl. If your scripts use 4-character years, than you have nothing to worry about.

Not fully. Don't worry, you will still be able to play Kool-Aid Man on January 1, but if Mattel were still developing games for Intellivision, they'd have a problem: the routine that draws the standard Mattel Electronics presents title screen uses two digits to input the year. So in 2000, new games would display the copyright line: Copr @ 1900 Mattel.

Crashing: None of TeX, Metafont or MetaPost can themselves crash due to any change whatever in the date of any sort. Timestamps: In the original sources, a 2-digit year was stored as the creation time for format files and that value is printed in logfiles. These items should not be of general concern, since the only use of the date format file is to produce the log output, and the log file is designed for human readers only.

This is a confusing issue. The simplest explanation is that Y2K compliant means that the system will AUTOMATICALLY roll over to the year 2000 after 12/31/99 at 11:59:59. Systems that are Y2K capable can be RESET to function in the new century after 12/31/99 at 11:59:59. In other words, these systems require manual intervention and/or operating system patches or special application software to provide the correct date.

Q3.2: Why do I receive an "out of memory" message when trying to save a file to a network drive. It still allows Save As, but will not allow Save.

Yes it is. This question may seem out-dated to some, but there are still companies struggling with DOS products that have this problem. As you may already know, "Y2K" is not really a virus, or "bug", but a widely used and accepted programming shortcut that indicated years with two digits instead of four.

Apache-SSL does not add any date processing to the underlying components, so does not affect the overall compliance of your system. The main component, Apache, has this to say on the matter. You should also check your operating system, hardware and any other modules you include.

Actually, the Flag Code doesn't say the flag should always be positioned to the left of a stage, etc. Rather, it's quite specific, saying only that if the flag is displayed with other flags at the same height, or next to a (human) speaker on a platform, the flag should be to the left of the other flags or speaker (from the audience's perspective — the flag's "own right" from its perspective). Since DeskFlag does not draw other flags or speakers, it is using proper flag etiquette.

Beginning with version 1.8d, LISTSERV is Year 2000 Compliant under all supported architectures except for VM, contingent on operating system support for Year 2000. LISTSERV 1.8d for VM has the code for Year 2000 compliance but has not yet (as of 1 March 1999) been certified Year 2000 compliant. Testing to-date has not revealed any problems, but is not completed on VM.

Beginning with version 1.1b, LSMTP is Year 2000 Compliant under Windows NT, contingent on operating system support for Year 2000.

Beginning with version 1.2d, LMail is Year 2000 Compliant, contingent on operating system support for Year 2000.

The product will not terminate unexpectedly on January 1, 2000 or on February 29, 2000 due to incorrect date manipulation. Functions that use date ranges including dates on either side of these two dates will work as expected. Functions that accept date parameters using a 2-digit year format will make an appropriate assumption about the 4-digit year represented. Not necessarily. It uses 4-digit years for all the user-friendly displays, inside log files, etc.

However, different date/time related problems might occur starting in 2010, 2099 and 2924 (should you be so lucky to be alive, with a functioning Newton). These problems are discussed here: http://members.home.net/saweyer/newton/newtscape/exs/times.htm#Description

Yes, SpearMail has been tested for Y2K. It will not produce errors in processing date data in connection with the year change from December 31, 1999 to January 1, 2000. This is provided all other software and/or hardware products exchange date data with the SpearMail properly.

MB-System is Y2K compliant as of the final release of version 4.6. Surprisingly, a number of data formats associated with current commercial products still use two digits to represent the year. MB-System treats two digit year values as being in the 1900's if the year value is greater than or equal to 62, and in the 2000's if the year value is less than 62.

MetaQuest Software Inc. has conducted Y2K tests for Census and found that it performs as originally designed.

Starting from 5400 series (including 6100, 6200, 6300, 7200, 1100 series, 2100 series, 8800 series), all these models are Y2K compliant. Provided that you have the latest BIOS installed.

Yes. Extensive in-house testing as well as independent testing have revealed no Y2K problems. None of our customers have reported any Y2K problems.

Answer: Because it is a free software, I will not guarantee that it is Y2K compliant, but I'm confident that it is. The program uses system time and date routines.

Out of the box, all versions of Q&A are ready for the Year 2000 and beyond. However, Y2K compliance is assured only if you format all date fields in your databases to display the full four-digit year instead of the abbreviated two-digit year. (Press F10 from the database design screen until you reach the Global Format Options Screen, then select a date with a four-digit year.) With Q&A 4.0 and 5.

However, there are at least 2 MPI functions that report the time/date: MPI_Wtime() and MPI_Wtick(). These functions directly report whatever the underlying operating system tells them is the current date and time. Hence, if the underlying OS is not Y2K compliant, these two functions may report inaccurate information. LAM cannot do anything to fix this. Also, the LAM tracing mechanism depends on the time (as reported by the underlying operating system).

Yes. Webmin does very little date processing, and all that it does will continue to work properly after 1/1/2000. However, be aware that some of the servers that Webmin manages (such as Apache, Sendmail, etc..) may not be Y2K compliant if you are using older versions.

In general: SGI can not guarantee the Y2K compliance of these packages since they are not written nor maintained by SGI. Also, we have no resources to do Y2K testing as we do for IRIX. If this issue is critical to you we recommend you devote the resources to scan the included source and report bugs to the original maintainers (not SGI). See also Q5.1. Thanks very much for the offer. This is highly appreciated.

Yes, to the degree that the underlying database it is reading from is Y2K compliant. The DTL reads into the standard ODBC timestamp structure. Since DTL does not manipulate this date in any way, the resulting time strucutre will be correct as long as it comes from the database correctly. In addition, DTL provides date math functions through the use of an optional jtime_c structure. These functions will process dates both before and after the year 2000 correctly. See jtime_c for details.

Yes and no. Yes, some software programs that run at boot time can correct the operating system clock and allow you to provide the correct date and time to application programs. However, if ANY application programs makes a call DIRECTLY to the hardware clock, it will get the wrong date. NOTE - most applications use the software clock.