|
Extremez-ip 2 readme version 2x166 July 19, 2011
|
| bet | 41/96 | | Sana | 21.03.2017 | | Hajmi | 275,22 Kb. | | #971 |
| BUG FIXES:
* Fixed problem where applications such as Photoshop, InDesign and Quark could give errors when saving to an existing file. This problem could cause errors in the application itself, and could cause the file to disappear from the Finder. This issue was present in the ExtremeZ-IP 5.0.1x07 hotfix only. [#7923] [5.0.1x09]
* Fixed problem where server could become unresponsive and connected clients could disconnect, requiring a restart of the service. This issue was present in ExtremeZ-IP 5.0 only. [#7913] [5.0.1x08]
* Fixed problem where ExtremeZ-IP would fail to fully enumerate the contents of a folder, causing files and folders to be invisible to the Finder or other applications. This problem was most likely to occur on gigabit networks, and when using applications such as Rampage that enumerate items in large blocks (32 at a time) compared to the Finder (20 items at a time). This issue was present ExtremeZ-IP 5.0 only. [#7886] [5.0.1x05]
* Fixed problem where idle OS 9 clients could be disconnected from the server. This issue was present in ExtremeZ-IP 5.0 only. [#7905] [5.0.1x08]
* Fixed problem where ExtremeZ-IP would return the wrong error code when a client attempted to perform a byte-range lock on a section of a file that already contained a byte-range lock from that client. This could cause some applications (such as Microsoft Word running in Classic mode) to incorrectly open a file in read-only mode. This issue was present in all versions of ExtremeZ-IP through 5.0. [#7732] [5.0.1x01]
* Fixed problem where ExtremeZ-IP Server name would not match the Network Name dependency on a cluster, but would have "IP" appended to it. This issue was present in ExtremeZ-IP 5.0 only. [#7887] [5.0.1x05]
* Fixed problem where selecting an existing extension in the Type and Creator window of the Administrator would fail to cause the corresponding type/creator to become selected. This issue was present ExtremeZ-IP 5.0 only. [#7888] [5.0.1x06]
* Fixed problem where a "ghosted" session could be left in "Waiting For Reconnect" state after a client reconnected to the server. This issue was present in ExtremeZ-IP 5.0 only. [#7795] [5.0.1x08]
* Fixed problem certain files could fail to have their Finder information migrated from their corresponding dot underscore files. This issue was present in ExtremeZ-IP 5.0 only. [#7883] [5.0.1x08]
* Changed behavior so that modifications to .DS_Store files do not cause the volume's modification time to be updated. This issue was present in all versions of ExtremeZ-IP from 4.0 through 5.0. [#3437] [5.0.1x01]
* Added code to gracefully handle situation when client asks for deprecated "launch limit" parameter. This issue was present in all versions of ExtremeZ-IP 4.0 through 5.0. [#3281] [5.0.1x01]
* Fixed problem where clients could fail to mount a volume containing an 8-character volume password. This issue was present in all versions of ExtremeZ-IP through 5.0. [#7612] [5.0.1x01]
* Fixed problem where the ExtremeZ-IP Administrator would fail to refresh the display of the number of locks for an opened file in the Files Window. Previously, the window would have to be closed and reopened for the value to properly update. This issue was present in all versions of ExtremeZ-IP through 5.0. [#7740] [5.0.1x01]
|
| |
