Santronics Software
Year 2000 Software Compliance Statement
Last Update: January 2, 2000

An issue of growing concern to our many customers is how well their investment in software and data will be protected when the year 2000 dawns.  Santronics Software Incorporated (SSI) shares this concern and will perform everything possible to make sure our own products are compliant for operations during the new century.

Y2K Definition:

Y2K has become a "broad term".  In general, the layman will consider anything wrong with a date whether it is displayed wrong, inputted wrong, calculated wrong, to be a Y2K related problem.   In many cases, a date problem has nothing to do the Year 2000 or beyond.  It may be simply a regular programming bug.    Hence it is very important that a "base line" definition is established for both Y2K and NON-Y2K date related problems as it relates to our products:

• Y2K DATE BUG: A bug which is related to the misrepresentation or mis-use of a time or date in dealing with dates on or into the next century.  This bug could be a display bug.  For example,  the actual year is 2001, and the displayed year is neither 01 or 2001. The bug could be a calculation. For example, the difference of years between 2001 and 1998 should be 3 years.  A false calculation could yield -97.   In general, the Y2K bugs are caused by faulty algorithms either used by Santronics or by the Compilers used to create our products or Operating System.  Typically, the dates problems are "conversion" problems between a YY formatted date into a YYYY formatted date. So the conversion of 98 can be 1998 or 2098 or is it 1798?   Depending on the binary date storage method used, the reference point is very important.  For example, Microsoft DOS dates begin at 1980. However, internal storage is 2 digits.  So a date of 01, should be read as 2001.  Not 1901.

• NON-Y2K DATE BUG:  A bug which is not related to Y2K whatsoever.   This bug could be a typo or bad usage of perfectly valid date algorithms.   This bug could be a display bug. For example, the month index of 1 could internally represent the month January or February depending on either the index is base 0 or 1.   This would have nothing to do with Y2K.

Testing for Y2K or NON-Y2K Date Operations

Santronics has performed both Y2K and NON-Y2K Date testing on all current product lines..  While older obsolete products were tested by Mustang Software, Santronics did not include the obsolete products in the test suites.

The Y2K test suite was designed to establish that :

• Date-sensitive routines in all programs correctly handle the century change without loss of data.
• Date calculations are accurate and appropriate for each circumstance,
• Date and time displays contain meaningful information both before and after the century change.

The NON-Y2K test suite was designed to establish that:

• Internal date calculations are correct
• Date and time displays were correct in all instances.

Test Results:

Product/Version	Y2K Issues	NON-Y2K Issues	Status	Solution
Wildcat!/DOS 1.0	Unknown	Unknown	Obsolete version	Upgrade to Wildcat!/DOS 4.2 or WINServer V5.3.447
Wildcat!/DOS 2.0	Unknown	Unknown	Obsolete version	Upgrade to Wildcat!/DOS 4.2 or WINServer V5.3.447
Wildcat!/DOS 3.9-4.1	Unknown	Unknown	Obsolete version.	Upgrade to Wildcat!/DOS 4.2 or WINServer V5.3.447
Wildcat!/DOS 4.2	SEMI-PASS, with unknowns	SEMI-PASS, with unknowns	Obsolete version. No further development.  Only Installation, Configuration, and Operation Technical support provided. Known Problems: There are a few problems with reading and displaying  MM/DD/YY formatted dates.  This is mostly with DOOR operations. In addition, there  might be a few non-door related Date Display Issues.	Wildcat/DOS is obselete and there is no further development with this product line.  However, there  are solutions: 1) The best recommendation for a 100% complete Y2K solution is to upgrade to WINSERVER v5.3.447.  This will be your ultimate solution. 2) For a partial Y2K solution which solves the DOOR problem for the next 15 years,  download the PATWC42.ZIP patch on the Santronics BBS Support Center.  In addition, you can minimize Y2K issues by using the YYYY format in MAKEWILD and  avoid using DOOR operations altogether.
Wildcat! v5.0 (original)	PASS	A few issues with displays of dates	Obsolete version. Technical Support still provided	Upgrade to WINServer V5.3.447
WINServer v5.0 Build less than 445	PASS	A few issues with displays of dates.	Technical Support provided	Upgrade to WINServer v5.3.447
WINServer v5.0.2 Build 446	PASS	A few issues with displays of dates	Technical Support provided	Upgrade to WINServer v5.3.447
WINServer v5.3.447.3 (base system)	PASS	PASS	Most Current Version.	Most Current Version
wcReports (v5.02.446)	PASS	SEMI-PASS	Current Version. Has some Conversion problems	Fixes will be available by October/1999.
wcEvents (All versions)	SEMI-PASS	PASS	Current Version. Has a Y2K re-scheduling bug.	Temporary solution: Make sure the event option [ ] Reschedule Event is checked on.   Permanent fix will be available by December 28 via AUP 448..
OLX/DOS v1 & 2,  OLX/WINDOWS v1.x	SEMI-PASS	SEMI-PASS, Has 02/29/2000 Leap year Problem.	Technical Support Provided. The  QWK mail format is not Y2K compliant, hence it is not possible to be 100% compliant.	None. Non-fatal problem. However Y2K issues are minor since Mail is a progressive data concept. Meaning, within a few days after January 1, 2000, all mail will be within the same century. One solution provided by a customer: "Set with OLX (Offline Express QWK Reader) 1.53 for DOS, run in a DOS Window under Windows 95...is to show that OLX is Y2K compliant. The only thing to show all the dates is to go to O)ptions, then P)references, then Dates...set the style to mm-dd-yyyy."
Silver Xpress (version 4.5 required)	PASS	PASS	Technical Support Provided.  Versions 4.4 and below have conversion to display problem.  The  QWK/OPX mail format is not Y2K complian, hence it is not possible to be 100% compliant.  However, there are NO ill effects with Y2K operations.	Silver Xpress v4.5 will be made available in December 29,  1999.  Check the Product Support section at Santronics Web site.
Platinum Xpress/DOS (V1.4 required) Platinum Xpress/WIN (V3.0pr3 required)	PASS	PASS	Technical Support Provided,	Updates are available for each DOS and WINDOWS versions on the Santronics Product Update Web Support page.   Note, The FIDO mail format is not Y2K compliant.  Y2K issues are minor since Mail is a progressive data concept. Meaning, within a few days after January 1, 2000, all mail will be within the same century.
iFTP v2.x	PASS	PASS	Current	Current

Overall, Customers can feel confident that there will be no untold effects on their software or data as a result of using any of the currently supported but not obsolete products mentioned in the above list, on or after December 31, 1999.   As noted above,  non-obselete product with any date related problem will be updated.  If the product is obsolete, you will need to upgrade to the most current version.   Note: Y2K issues is not a reason for "free upgrades".   Upgrades include many new features and enhancements, not just any Y2K issue addressed.

Before relying on WINServer operations in regards to dates, Santronics strongly recommends all customers to take steps to obtain similar assurances from the developers of all other hardware or software products they rely on or intend to use beyond the end of 1999.  This means you should make sure you have the latest updates for all the software you use.

Although, Santronics has done its absolute best to comply with both Y2K and NON-RELATED Y2K date issues, we retain the right by US LAW to address any unknown issues found by our customers.   The US Y2K-BILL states that if a Y2K bug solution is available in the form of a upgrade, and if you want to have the Y2K fix, then you must get the upgrade we offer. 

Important Disclaimer:  SSI accepts NO LEGAL RESPONSIBILITY for the Y2K operations of Microsoft's Windows Operating System and Software Development Tools, including other 3rd party Software Development Tools used by SSI.  The following companies are operating systems and software development tools used by Santronics: Microsoft's Windows 3.1, Windows 95a, Windows 95b, Windows NT 3.51, Windows 98, Windows NT 4.0,  Visual C++ 6.0 16/32 bit, Visual BASIC; Inprise (Formerly Borland) Delphi Pascal 3.0, Borland C++ 4.52, Borland C++ Builder 4.0.   All Y2K compliance concerns related to these systems and products should be directed at these companies (check their web sites).