This patch is now obsolete. Please see the OPENSTEP Current Patch List, TIL article 70033 , for information on the most current patches for OPENSTEP and Enterprise Objects Framework. This obsolete patch is provided here as a convenience to our customers who have not yet upgraded to the most current patch level.

About This Patch

This patch is obsolete; please see the OPENSTEP Current Patch List, TIL article 70033 , for information on the most current patches for OPENSTEP and Enterprise Objects Framework. This patch contained a number of important bug fixes, including corrections for some Year 2000 problems. See the "Problems Fixed" section below for details.

Installing OPENSTEP 4.2 Enterprise Patch 2 on Solaris or HP-UX

1. Download the Solaris version or the HP-UX version of this patch from Apple's FTP servers at ftp.info.apple.com. The files are located at:

/Apple_Support_Area/Apple_Software_Updates/MultiCountry/Enterprise/openstep/

patches/4.2Solaris_Patch2.TAR.Z

and

/Apple_Support_Area/Apple_Software_Updates/MultiCountry/Enterprise/openstep/

patches/4.2HPUX_Patch2.TAR.Z

Also download the installer script, "patcher.sh" from:

/Apple_Support_Area/Apple_Software_Updates/MultiCountry/Enterprise/openstep/

patches/patcher.sh

2. Log in as root . If you're not sure how to log in as root, see your system administrator.

3. Change to the directory containing the patch and the patch installer, "patcher.sh".

4. Type the following at the shell prompt (make sure that there are no EOF applications running first):

patcher.sh -install 4.2Solaris_Patch1.TAR.Z

or

patcher.sh -install 4.2HPUX_Patch1.TAR.Z

For more information on using the "patcher.sh" program, type the following at the command prompt:

patcher.sh -help

5. Reboot your Unix system

Problems Fixed

Corrected in OPENSTEP 4.2 Enterprise Patch 2 for Solaris and HP-UX

NSDateFormatter interprets year "00" as "Current Year"
Apple reference # 2278598

PROBLEM:
NSCalendarDate would interpret year "0" or "00" as "current year", rather than "2000", which was inconsistent with the interpretation of two-digit years in UNIX and not Year 2000 compliant.

RESOLUTION:
NSCalendarDate now interprets "0" or "00" year values as "2000"

Date formatter handles two digit year inappropriately
Apple reference # 2290369

PROBLEM:
NSCalendarDate would treat any two-digit year as a 20th century year.

RESOLUTION:
NSCalendarDate now treats two-digit year values less than 30 as 21st century years.