This document contains an overview and download information for Apple's Update 1 for WebObjects release 4.5 on Windows 2000 and Windows NT. This update is required to use WebObjects 4.5 on Windows 2000 and addresses some issues on Windows NT 4, but has been superseded by WebObjects 4.5 Update 2 .

The WebObjects Current Patch List, article 70037 , contains information on all available updates and workarounds for all versions of WebObjects, including EOF updates. Please read this document if you're not sure which updates you need on your system.

1. Download WO45WinUpdate1.exe , the update installer for Windows NT and Windows 2000.

2. Log in as a user with Administrator privileges.

3. Make sure that there are no WebObjects, OPENSTEP or EOF applications running.

4. Double-click on the installer, WO45WinUpdate1.exe, to start the install process.

5. A screen will appear with some information about this update. After you have read it, click "Next" to continue.

6. The license agreement for this update will appear. To agree to the license and continue the installation, click "Yes".

7. The update will now be installed on your system and you will be asked if you want to reboot. Select "Yes, I want to restart my computer now" to reboot your Windows system. The WinZip self-extractor will automatically quit and remove the temporary installation in about 20 seconds.

Issues Addressed

Corrected in WebObjects 4.5 Update 1

[[NSHost currentHost] name] on Windows 2000 returns an uppercase name
Apple reference #2446389

ISSUE:
Windows 2000 will report an uppercase hostname unless you specify a lowercase one in the System control panel. This can cause Monitor to fail to start applications with an "Invalid host name" error.

RESOLUTION:
Monitor and wotaskd are now case insensitive for hostnames. With the version of Monitor that shipped with the 4.5 release it was possible to add the same host more than once using different capitalizations of the name. This would create multiple entries in the configuration file for the host. The patched version of Monitor will only display one name for the host even though there may be more than one entry in the configuration file. In this case deleting a host will only delete one entry from the configuration, so it will be necessary to delete the host multiple times to remove all references.

wotaskd periodically exits its listen thread
Apple reference #2446401

ISSUE:
On Windows 2000, recvfrom() sometimes returns with error status. This could cause wotaskd to enter an unusable state.

RESOLUTION:
The observed errors returned from recvfrom() are transient conditions, so wotaskd on the Windows platform has been modified to retry the recvfrom(). If many consecutive tries return errors, wotaskd will exit and restart. Any errors encountered will be logged, and a log is written if wotaskd exits. Additionally, wotaskd has been modified to wait 10 seconds before starting any application instances, to allow time to collect lifebeats from running processes.

Deferred faulting raises if destination entity class is in a java package
Apple reference #2448175

ISSUE:
Deferred faulting raises an exception if the destination entity class is in a java package, because EOAccess incorrectly looks up a class by name.

RESOLUTION:
EOAccess has been changed to properly look up the class.

Interface Builder fails to save on every second try
Apple reference #2452069

ISSUE:
Saving a .nib file on a Windows 2000 volume fails the second time the file is saved. The .nib wrapper contains no files. This happens because when InterfaceBuilder saves a .nib, it first writes the .nib to a temporary location named <myNib>.nib.~+~, where <myNib> is the name of your .nib file.

RESOLUTION:
This issue is the result of unexpected behavior from the Windows 2000 filesystem. Interface Builder has been modified to use <myNib>.~+~ as the temporary name rather than <myNib>.nib.~+~ on Windows platforms to work around this issue.

NSInvalidArgumentException while removing configured Monitor apps
Apple reference #2464806

ISSUE:
In Monitor, if you delete an application when there is more than one instance of that application is running, an exception is raised. Half of the running instances are removed, but the application is not deleted.

RESOLUTION:
Monitor now properly deletes all running instances when removing an applicaion.