========================================================================== The checksum's (found through sum -r) of the files that you have received (other than this README) are as follows: 56111 3 patchSG0001596 52364 2053 patchSG0001596.desktop_eoe_sw 58313 3 patchSG0001596.idb ========================================================================== - 1 - 1. Patch_SG0001596_Release_Note This release note describes patch SG0001596 to IRIX 5.3. Patch SG0001596 replaces patches SG0000292, SG0000447, SG0001093 and SG0001164. 1.1 Supported_Hardware_Platforms This patch contains bug fixes for all. The software cannot be installed on other configurations. 1.2 Supported_Software_Platforms This patch contains bug fixes for IndigoMagic Desktop (version 1021572033) on a system running IRIX 5.3. The software cannot be installed on other configurations. 1.3 Bugs_Fixed_by_Patch_SG0001596 This patch contains fixes for the following bugs in IRIX 5.3. Bug numbers from Silicon Graphics bug tracking system are included for reference. o Bug #431565: On editing iconbook or searching for files using searchbook, the files thus created in /.desktop-/iconbook and .desktop-/ searchbook had 666 permissions. This security hole is fixed by this patch. o Bug #351120: The filemanager was reporting 'disk full' when copying large files on a big disk ( > 4Gig ), which is not full. This was occuring due to an internal overflow. This patch fixes this bug. o Bug #253508: Under 5.2, fm (and dirview) used to take -geometry. Under 5.3, it did not. Running fm -geometry 1000x1000 would give a message like "can't open 1000x1000". Running with just -geometry gave no error at all. o Bug #203058: In some cases, the FileManager was not properly restoring shelf geometry. In particular, shelves were sometimes restored to their default size, even if the user had previously specified a different size. There were also cases where a shelf was incorrectly restored depending upon the geometry of the shelf previously being viewed in that FileManager window. - 2 - o Bug #253306: The FileManager sometimes continued to display files in a directory view even after said files had been removed via other means (e.g. temporary compiler files). o Bug #255491: When a user changed directories in the Indigo Magic Desktop directory view, the desktopManager didn't set the environment variable PWD to the corresponding directory. This could cause the default directory in a Motif FileSelectionBox used by an application launched from that directory to not be the corresponding directory. o Bugs 246869 and 226390: Custom Open and AltOpen FTR rules for directories weren't working quite right. In particular, if an FTR specified launching an application rather than opening the directory, a dirview on the directory would be opened and the application often wouldn't be launched. o Unfiled bug: IconPanels were attaching categories to the defaultDataMonitor, even if the client asked for no data monitoring via IconPanel::registerCategory(name, FALSE) or IconPanel::registerAllCategories(FALSE). o Bug #208688: Alt-open of a directory on the shelf creates a separate window instead of "tunnelling" into the current window. o Bug #270385: The command "dirview -o dir1 dir2" doesn't work. In pre-5.3 releases, it causes a the dirview looking at dir1 to tunnel to look at dir2. This has been fixed with the following caveat: If more than one filemanager window is open for dir1, which window is used is non-deterministic. However, the filemanager itself is able to use coordinate information to locate the proper window if the dirview -o was launched as a result of a filemanager operation. Hence, the non- deteminism only applies when dirview is launched from the command line. o Bug #308116: Dragging icons on X displays that do not have overlay planes would cause severe color map flashing. The programs that use the icon panels (dirview, iconcatalog, and the desktop) have been changed to not install a custom color map on X displays that do not have overlay planes. This eliminates the flashing. o Enhancement: The FTR rules have been enhanced to support the display of icons as images while in gallery - 3 - view. By defining the FTR variable "ImageIcon", the user can specify an icon to be used for a gallery image. The form of the command is 'SETVAR ImageIcon '. The can either be absolute or relative to the file/directory to which the FTR is being applied. When the FTR is applied to a file, a relative image path is resolved relative to the directory containing the file. When applied to a directory, a relative image path is resolved relative to that directory. o Enhancement: The FTR dircontains() MATCH rule now understands shell-style pattern matching. It uses the same pattern matcher as the glob() rule. 1.4 Subsystems_Included_in_Patch_SG0001596 This patch release includes these subsystems: o patchSG0001596.desktop_eoe_sw.dso 1.5 Installation_Instructions Because you want to install only the patches for problems you have encountered, patch software is not installed by default. After reading the descriptions of the bugs fixed in this patch (see Section 1.3), determine the patches that meet your specific needs. If, after reading Sections 1.1 and 1.2 of these release notes, you are unsure whether your hardware and software meet the requirements for installing a particular patch, run inst. The inst program does not allow you to install patches that are incompatible with your hardware or software. Patch software is installed like any other Silicon Graphics software product. Follow the instructions in your Software Installation Administrator's Guide to bring up the miniroot form of the software installation tools. Follow these steps to select a patch for installation: 1. At the Inst> prompt, type install patchSGxxxxxxx where xxxxxxx is the patch number. - 4 - 2. Initiate the installation sequence. Type Inst> go 3. You may find that two patches have been marked as incompatible. (The installation tools reject an installation request if an incompatibility is detected.) If this occurs, you must deselect one of the patches. Inst> keep patchSGxxxxxxx where xxxxxxx is the patch number. 4. After completing the installation process, exit the inst program by typing Inst> quit 1.6 Patch_Removal_Instructions To remove a patch, use the versions remove command as you would for any other software subsystem. The removal process reinstates the original version of software unless you have specifically removed the patch history from your system. versions remove patchSGxxxxxxx where xxxxxxx is the patch number. To keep a patch but increase your disk space, use the versions removehist command to remove the patch history. versions removehist patchSGxxxxxxx where xxxxxxx is the patch number. 1.7 Known_Problems