[svn-r17896] Description:

	Bring r17546:17895 from trunk to revise_chunks branch.  Changes to
fixed and extensible array dataset chunk indexing code to accommodate changes
to private APIs in those interfaces.  Also, other adjustments to source code
and expected output in response to changes on the trunk.

Tested on:
        FreeBSD/32 6.3 (duty) in debug mode
        FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode
        Linux/32 2.6 (jam) w/PGI compilers, w/default API=1.8.x,
                w/C++ & FORTRAN, w/threadsafe, in debug mode
        Linux/64-amd64 2.6 (smirom) w/Intel compilers, w/default API=1.6.x,
                w/C++ & FORTRAN, in production mode
        Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
                w/szip filter, in production mode
        Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
                in production mode
        Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in debug mode
        Linux/64-amd64 2.6 (abe) w/parallel, w/FORTRAN, in production mode
        Mac OS X/32 10.6.2 (amazon) in debug mode
        Mac OS X/32 10.6.2 (amazon) w/C++ & FORTRAN, w/threadsafe,
                in production mode

4 files changed, 89 insertions, 327 deletions

diff --git a/release_docs/INSTALL_Windows.txt b/release_docs/INSTALL_Windows.txt
index d20c35f..a24e1d5 100644
--- a/release_docs/INSTALL_Windows.txt
+++ b/release_docs/INSTALL_Windows.txt
@@ -35,10 +35,9 @@ Contents:
 Preconditions:
 
    1. Installed Microsoft Visual Studio.  This document is written for Visual
-      Studio 2005, although we also support Visual Studio .NET 2003 and Visual
-      Studio 2008 as well.  Most of the instructions are the same, although some
-      features are unsupported in Visual Studio .NET.  For simple Visual Studio 
-      .NET instructions, see the document INSTALL_Windows_NET.TXT.
+      Studio 2005, although we also support Visual Studio 2008 as well.  Most 
+	  of the instructions are the same. We no longer support building HDF5 
+	  using Microsoft Visual Studio .NET 2003.
    
    2. (Optional) Installed Intel Compiler 9.1 or 10.1 if you want to build HDF5 
       Fortran libraries.
@@ -164,11 +163,8 @@ Notes:
       directory, run copy_hdf.bat first and then open all.sln under 
       hdf5/windows/proj/all to start building process.
 
-   2. Visual Studio 6.0 will not be supported in HDF5 1.8 or later release.
-
-   2. Users who prefer to use Visual Studio .NET can follow instructions in 
-      INSTALL_Windows_Short_Net.txt.  Note, however,  HDF5 Fortran product
-      will not be supported in HDF5 1.8 release with Visual Studio .NET.
+   2. Visual Studio 6.0 is no longer supported in HDF5 1.8 or later releases.
+      Visual Studio .NET is no longer support in HDF5 1.8.4 or later releases.
 
    3. For users who want to quickly build HDF5 library or do not want to know 
       HDF5 building and installation details, please read the 
@@ -1123,7 +1119,6 @@ Notes:  1. For Intel Compiler users, Intel fortran Compiler 9.1 and 10.1 are
         2. The Compaq Fortran Compiler is no longer supported for HDF5 1.8.
 
         3. Intel Fortran 9.1 works only under Visual Studio 2005 environments.
-           Building Fortran libraries under Visual Studio .NET is unsupported.
            Visual Studio 2008 is supported only with Intel Fortran 10.1.
         
         4. Parallel builds should be disabled.  To do so: Go to  Tools > 
@@ -1393,51 +1388,7 @@ Notes:  1. For Intel Compiler users, Intel fortran Compiler 9.1 and 10.1 are
 Notes: In Visual Studio 2005, the Single-threaded runtime libraries have been
        depreciated, and Multi-threaded is built by default.  Therefore, no extra
        work needs to be done to build Multi-threaded libraries in Visual Studio
-       2005.  This section applies only to Visual Studio .NET
-
-       Preconditions and Section I also apply to this section. Users who
-       want to build Multi-threaded version of HDF5 library, please read
-       those two sections carefully before go to the following part.
-
-       
-In Visual Studio .NET, users have the option of building multi-threaded
-libraries by manipulating the project settings.  Otherwise, the build process
-is very much the same.  Therefore, follow the instructions below, and refer
-to the earlier sections of this document for details on building and testing.
-
-
-1. Open the solution file
-
-    Refer to previous sections to open the appropriate solution file,
-    depending on whether you are building with or without Fortran libraries.
-        
-2. Change Project Settings
-
-    a) In Visual Studio, go to "Projects->Properties".
-
-    b) Make sure in the "Configuration" box, "Release" is selected.
-    
-    c) Select all of the static project file in the main window by holding 
-       the "Ctrl" key while clicking the project file name.
-       
-    d) In the "Properties" window, choose "C/C++", and then "Code
-       Generation".
-       
-    e) Under "Run-time Library", "Single-Threaded" should appear. If it is 
-      blank inside this box, check if you highlight some DLL project files. 
-      
-    d) Change "Single-Threaded" to "Multithreaded".
-
-    e) In the "Configuration" box, change to "Debug", keeping the static
-       projects selected.
-
-    f) Under "Run-time Library", change "Debug Single-Threaded" to "Debug 
-       Multithreaded".
-
-3. Build as Normal
-
-    Refer to previous sections to build and test the HDF5 libraries
-    and tools.
+       2005.  
     
     
 ========================================================================
@@ -1620,10 +1571,7 @@ to the earlier sections of this document for details on building and testing.
             Section IX: How to build HDF5 for 64-bit Windows
 ========================================================================
 
-HDF5 can be built for 64-bit Windows in Visual Studio 2005 or 2008.  Visual 
-Studio .NET has very primative 64-bit support, but it is very difficult to 
-set up, and debugging is not supported.  Therefore, we recommend all users 
-switch to Visual Studio 2005 or 2008 for 64-bit builds.  
+HDF5 can be built for 64-bit Windows in Visual Studio 2005 or 2008.  
 
 Notes:
   
@@ -1680,14 +1628,9 @@ some minor changes.  Therefore, follow the build instructions above, with the
 following considerations:
 
     1. Only Visual Studio 2005 and 2008 is currently supported on Windows Vista.
-       This is because Microsoft has ended their support for and .NET.
-       
-    2. Building Fortran libraries has not been tested, and is therefore also
-       unsupported.  You may attempt to build Fortran libraries following the
-       instructions above, but they should be considered experimental and used
-       for testing only.
+       This is because Microsoft has ended their support for .NET.
        
-    3. Elevated security permissions are required to test the HDF5 libraries.
+    2. Elevated security permissions are required to test the HDF5 libraries.
        This is because DLLs are installed in the system directory.  To enable
        elevated security:
        
diff --git a/release_docs/INSTALL_Windows_From_Command_Line.txt b/release_docs/INSTALL_Windows_From_Command_Line.txt
index 053ae72..c35fdbf 100755
--- a/release_docs/INSTALL_Windows_From_Command_Line.txt
+++ b/release_docs/INSTALL_Windows_From_Command_Line.txt
@@ -4,12 +4,13 @@
 ************************************************************************
 Note: This instruction is written for users who would like to build HDF5
       libraries and tools from the HDF5 source code package on command
-      line.
+      line. We no longer support building HDF5 using Microsoft Visual 
+	  Studio .NET 2003.
          
       Currently, we support:
       
       1. Building and testing HDF5 C/C++/Fortran libraries on command line with 
-         Microsoft Visual Studio .NET, 2005 or 2008 for 32- or 64-bit Windows.
+         Microsoft Visual Studio 2005 or 2008 for 32- or 64-bit Windows.
       
       For all other Windows development tools, HDF5 should be built in
       the development environment.  Please refer to INSTALL_Windows.txt
@@ -42,8 +43,7 @@ notes in INSTALL_Windows.txt before starting below procedures.
     
         C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\
         
-    If you are using Visual Studio .NET, replace "vs80comntools" with
-    "vs71comntools".  For Visual Studio 2008, use "vs90comntools"
+    If you are using Visual Studio 2008, use "vs90comntools"
       
    1.2 Run batch file copy_hdf.bat.
 
@@ -81,8 +81,7 @@ notes in INSTALL_Windows.txt before starting below procedures.
          from command line.
 
         hdf5bt file takes the following options:
-              /vs7              Build HDF5 using Visual Studio .NET 2003 
-                                Note: Default is Visual Studio 2005
+              /vs8              Build HDF5 using Visual Studio 2005
               /vs9              Build HDF5 using Visual Studio 2008
                                 Note: Default is Visual Studio 2005
               /fort             Build and test HDF5 with Fortran libraries
@@ -112,8 +111,7 @@ notes in INSTALL_Windows.txt before starting below procedures.
             tools from command line.
 
         hdf55build takes the following options:
-              /vs7              Build HDF5 using Visual Studio .NET 2003 
-                                Note: Default is Visual Studio 2005
+              /vs8              Build HDF5 using Visual Studio 2005
               /vs9              Build HDF5 using Visual Studio 2008
                                 Note: Default is Visual Studio 2005
               /fort             Build HDF5 with Fortran libraries
diff --git a/release_docs/INSTALL_Windows_Short_NET.TXT b/release_docs/INSTALL_Windows_Short_NET.TXT
index 1f2aa74..db144d1 100755
--- a/release_docs/INSTALL_Windows_Short_NET.TXT
+++ b/release_docs/INSTALL_Windows_Short_NET.TXT
@@ -3,176 +3,7 @@
 *                     with Windows XP (Short Version)                  *
 ************************************************************************
 
-Notes: This short instruction is written for users who want to quickly
-       build HDF5 library and tools from the HDF5 source code package
-       with Microsoft Visual Studio .NET 2003 but do not want to know 
-       HDF5 building and installation details on Windows XP.
-       
-       Visual Studio .NET 2003 is NOT supported on Windows Vista, as Microsoft
-       has ended their support.  Also, we do not support building 64-bit
-       libraries or Fortran libraries with Visual Studio .NET 2003.  If you
-       need any of these features, please upgrade to Visual STudio 2005.
-         
-       For detailed HDF5 build and install information, or if you have
-       trouble following any steps in the instructions, please refer to
-       INSTALL_Windows.txt for further information.
-      
-       For users who would like to build and test HDF5 package from the
-       command line, please refer to
-       INSATLL_Windows_From_Command_Line.txt.  Note, however, that building
-       from the command line requires Visual Studio 2005.
-
-WARNINGS:
-
-Please read CAREFULLY about HDF5 build and install preconditions and 
-notes in INSTALL_Windows.txt before starting below procedures.
-
-
-========================================================================
-                            Preconditions                                                           
-========================================================================                          
-
-   1. Set up path for external libraries and headers                     
-                                                                         
-      Skip this part if you don't want to use ANY compression features     
-      provided by HDF5.  Please do read Section V in INSTALL_Windows.txt.                         
-                                                                         
-      You have to read this part even if you want to only use Zlib         
-      or Szip.  You also need to read Section V in INSTALL_Windows.txt.                           
-                                                                         
-      Invoke Microsoft Visual C++ .Net and go to "Tools" and select             
-      "Options". In the left pane of  "Option" window poped up,
-      choose and expand "Projects", Click on "VC++ Directories".
-      In the right pane, Find the box "Show directories for", choose                          
-      "Include files", if you can not find your Zlib and Szip              
-      header path                                                          
-      (for example, c:\zlib123\include, c:\szip\include)                   
-      from the directory list, add the header path                         
-      (c:\zlib123\include, c:\szip\include) to the                         
-      included directories.                                                
-                                                                         
-      Find the box "Show directories for", choose "Library files",         
-      If you cannot find your Zlib and Szip library path                   
-      (for example, c:\zlib123\dll, c:\szip\dll)                           
-      from the directory list, add the library path                        
-      (c:\zlib123\dll, c:\szip\dll) to the library directories.            
-
-========================================================================
-                Building HDF5 C/C++ Libraries with VS .NET
-========================================================================
-
-   1. Run batch file copy_hdf.bat
-
-      Go to  c:\MyHDFstuff\hdf5\windows and run copy_hdf.bat. This process will 
-      copy all the necessary batch files, windows specific source codes and 
-      text files saved under c:\MyHDFstuff\hdf5\windows directory to the 
-      corresponding directories under hdf5.
-
-   2. Invoke Microsoft Visual Studio compiler
-
-      Invoke Microsoft Visual Studio.  From the main menu, go to "File" and 
-      select the "Open Solution" option. Then open the
-      c:\MyHDFstuff\hdf5\windows_vnet\proj\all\all.dsw workspace.
-
-      You should find Windows project files listed as "all", "big", etc. on the
-      left.
-
-   3. (Optional) Disable HDF5 C++ and High level C++
-   
-      In HDF5 1.8, C++ and HL C++ libraries are built by default.  To opt-out,
-      you must explicitly disable them.
-
-      4.1 Skip this step if you do want to build HDF5 High-Level C++ libraries
-
-          Go to "Project" and select "Project Dependencies".  Select "all", and 
-          disable all of the following projects:
-
-            hdf5_hl_cpp
-            hdf5_hl_cppdll
-            hl_test_table_cpp
-            hl_test_table_cppdll
-      
-      4.2 Skip this step if you do want to build HDF5 High-Level libraries
-
-          Go to "Project" and select "Project Dependencies".  Select "all", and 
-          disable all of the project files listed in the previous step, as well
-          as the following projects:
-
-             hdf5_hl
-             hdf5_hldll
-             hl_test_image
-             hl_test_imagedll
-             hl_test_lite
-             hl_test_litedll
-             hl_test_table
-             hl_test_tabledll
-             hl_test_ds
-             hl_test_dsdll
-             hl_test_packet
-             hl_test_packetdll
-   
-   Click on "OK", From the main menu, choose "Build"-> "Build" or  
-   "Rebuild ALL" to build both release and debug version of HDF5   
-   Libraries.                                                                                           
-             
-
-   4. Select "Build", then Select "Configuration Manager".
-
-      5.1 To build debug static libraries, debug multithreaded DLLs, and tests:
-
-      In "Active Solution Configuration", select "Debug". Select "Close". 
-      Select "Build" -> "Build Solution" or "Rebuild Solution" to build debug 
-      version of project "all".
-
-      5.2 To build release static libraries, multithreaded DLLs and tests:
-
-      In "Active Solution Configuration", select "Release". Select "Close". 
-      Select "Build" -> "Build Solution" or "Rebuild Solution" to build release 
-      version of project "all".
-
-      Both debug and release versions must be built.
-
-      Warning messages can be ignored.
-             
-========================================================================
-               Testing HDF5 C/C++ Libraries with VS .NET
-========================================================================
-
-HDF5 libraries and tools should be tested to make sure that they were
-built correctly. c:\MyHDFstuff\hdf5\hdf5check.bat was provided to test
-HDF5 libraries and tools.
-
-hdf5check.bat has the following options:
-   
-   hdf5check                     test HDF5 C library and tools only
-      
-   hdf5check enablecpp           test HDF5 C/C++ libraries and tools
-
-
-Invoke a command prompt window and run hdf5check with appropriate option.
-Users are encouraged to pipe the test output into a file.  You should find
-no "*FAILED*" marks.
-
-If you want to test HDF5 libraries and tools one by one, please refer to
-Section II, step 2 in INSTALL_Windows.txt.
-
-
-========================================================================
-                    Installing HDF5 C/C++ Libraries
-========================================================================
-
-Run the batch file c:\MyHDFstuff\hdf5\installhdf5lib.bat to install 
-all HDF5 libraries and tools into c:\MyHDFstuff\hdf5\hdf5lib directory.
-
-========================================================================
-               Building HDF5 Examples and Applications
-========================================================================
-
-Building HDF5 Examples is Optional. Please read Section II, step 4 and 
-the following part in INSTALL_Windows.txt for detailed information.
-
-
-
+Notes: We no longer support building HDF5 using Microsoft Visual Studio .NET 2003.
 ************************************************************************
 
 Need further assistance, send email to help@hdfgroup.org
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index 0d9289b..e122005 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -1,4 +1,4 @@
-HDF5 version 1.9.47-FA_a4 currently under development
+HDF5 version 1.9.51-FA_a4 currently under development
 ================================================================================
 
 
@@ -60,15 +60,17 @@ New Features
 
     Library:
     --------
+    - Added support for filtering densely stored groups.  Many of the API
+      functions related to filters have been extended to support dense groups
+      as well as datasets.  Pipeline messages can now be stored in a group's
+      object header. (NAF/QAK - 2009/10/8)
     - The embedded library information is displayed by H5check_version() if a
       version mismatch is detected.  Also changed H5check_version() to
       suppress the warning message totally if $HDF5_DISABLE_VERSION_CHECK is 2
       or higher. (Old behavior treated 3 or higher the same as 1, that is
       print a warning and allows the program to continue. (AKC - 2009/9/28)
-    - Added a new feature that have the library information in the file
-      libhdf5.settings embedded in the hdf5 library and statically linked
-      executables.  If a user does not care for the extra library information
-      in the executable, he may turn it off by --disable-embedded-libinfo
+    - If a user does not care for the extra library information insert
+      in the executables, he may turn it off by --disable-embedded-libinfo
       during configure. (AKC - 2009/9/15)
     - Corrected problem where library would re-write the superblock in a file
       opened for R/W access, even when no changes were made to the file.
@@ -173,6 +175,9 @@ New Features
      - h5diff: h5diff treats two INFINITY values different. Fixed by checking  (value==expect) 
             before call ABS(...) at h5diff_array.c This will make that (INF==INF) is true 
             (INF is treated as an number instead of NaN) (PC -- 2009/07/28)
+     - h5diff: add option "--use-system-epsilon" to print difference if (|a-b| > EPSILON)
+            Change default to use strict equality (PC -- 2009/09/12)
+
     
     High-Level APIs:
     ------
@@ -193,6 +198,13 @@ Bug Fixes since HDF5-1.8.0 release
 
     Library
     -------
+      - Fixed a bug where writing and deleting many global heap objects (i.e.
+            variable length data) would render the file unreadable.  Previously
+            created files exhibiting this problem should now be readable.
+            NAF - 2009/10/27 - 1483
+      - Fixed incorrect return value for H5Pget_preserve. AKC - 2009/10/08 - 1628
+      - Fixed an assertion failure that occurred when H5Ocopy was called on a
+            dataset using a vlen inside a compound. (NAF - 2009/10/02 - 1597)
       - Fixed incorrect return value for H5Pget_filter_by_id1/2 in H5Ppublic.h.
             (NAF - 2009/09/25 - 1620)
       - Fixed a bug where properties weren't being compared with the registered
@@ -315,11 +327,32 @@ Bug Fixes since HDF5-1.8.0 release
 
     Configuration
     -------------
+    - Removed the following config files, as we no longer support them:
+        config/dec-osf*, config/hpux11.00, config/irix5.x, 
+        config/powerpc-ibm-aix4.x config/rs6000-ibm-aix5.x config/unicos*
+      MAM - 2009/10/08
+    - Modified configure and make process to properly preserve user's CFLAGS
+      (and company) environment variables. Build will now properly use
+      automake's AM_CFLAGS for any compiler flags set by the configure
+      process. Configure will no longer modify CFLAGS directly, nor will 
+      setting CFLAGS during make completely replace what configure has set up.
+      MAM - 2009/10/08
+    - Support for TFLOPS, config/intel-osf1, is removed since the TFLOPS
+      machine has long retired. AKC - 2009/10/06.
+    - Added $(EXEEXT) extension to H5detect when it's executed in the 
+      src/Makfile to generate H5Tinit.c so it works correctly on platforms 
+      that require the full extension when running executables.
+      MAM - 2009/10/01 - BZ #1613
+    - Configure will now set FC and CXX to "no" when fortran and c++
+      are not being compiled, respectively, so configure will not run
+      some of the compiler tests for these languages when they are not
+      being used. MAM - 2009/10/01
     - The PathScale compiler (v3.2) was mistaken as gcc v4.2.0 but it fails to
       recognize some gcc options. Fixed. (see bug 1301). AKC - 2009/7/28 -
-    - The --enable-static-exec flag has been fixed and will now generate
-      static executables within the installed bin directory when used.
-      MAM - 2009/07/23 - BZ #1583
+    - The --enable-static-exec flag will now properly place the -static flag
+      on the link line of all installed executables. This will force the
+      executable to link with static libraries over shared libraries, provided
+      the static libraries are available. MAM - 2009/08/31 - BZ #1583
     - The --includedir=DIR configuration option now works as intended, and can
       be used to specify the location to install C header files. The default
       location remains unchanged, residing at ${prefix}/include. 
@@ -382,6 +415,10 @@ Bug Fixes since HDF5-1.8.0 release
 
     High-Level APIs:
      ------
+      - Fixed a bug where the H5TB API would forget the order of fields when
+          added out of offset order. (NAF - 2009/10/27 - 1582)
+      - H5DSis_attached failed to account for different platform types. Added a
+          get native type call. (ADB - 2009/9/29 - 1562)
       - Dimension scales: The scale index return value in H5DSiterate_scales was not always 
           incremented. (PVN - 2009/4/8 - 1538)
 
@@ -443,10 +480,6 @@ Platforms Tested
                                   g++ 4.2.1 20080123
                                   gfortran 4.2.1 20080123
 
-    IRIX64 6.5 (64 & n32)         MIPSpro cc 7.4.4m
-                                  F90 MIPSpro 7.4.4m 
-                                  C++ MIPSpro cc 7.4.4m
-				 
     Linux 2.6.9 (RHEL4)           Intel 10.0 compilers
     (abe.ncsa.uiuc.edu)
     Linux 2.4.21-47               gcc 3.2.3 20030502
@@ -461,16 +494,12 @@ Platforms Tested
           SMP ia64                Intel(R) C++ Version 9.0
     (cobalt)                      Intel(R) Fortran Itanium(R) Version 9.0 
                                   SGI MPI
-    SunOS 5.8 32,46               Sun WorkShop 6 update 2 C 5.3
-     (Solaris 2.8)                Sun WorkShop 6 update 2 Fortran 95 6.2
-                                  Sun WorkShop 6 update 2 C++ 5.3
-    SunOS 5.10                    cc: Sun C 5.8 
-    (linew)                       f90: Sun Fortran 95 8.2 
-                                  CC: Sun C++ 5.8 
-    Xeon Linux 2.4.21-32.0.1.ELsmp-perfctr-lustre
-    (tungsten)	                  gcc 3.2.2 20030222
-                                  Intel(R) C++ Version 9.0
-                                  Intel(R) Fortran Compiler Version 9.0
+    SunOS 5.10                    Sun C 5.9 SunOS_sparc 
+                                  Patch 124867-11 2009/04/30
+    (linew)                       Sun Fortran 95 8.3 SunOS_sparc 
+                                  Patch 127000-11 2009/10/06
+                                  Sun C++ 5.9 SunOS_sparc 
+                                  Patch 124863-16 2009/09/15
     IA-64 Linux 2.4.21.SuSE_292.til1 ia64
     (NCSA tg-login)               gcc 3.2.2
                                   Intel(R) C++ Version 8.1
@@ -486,8 +515,9 @@ Platforms Tested
     Windows Vista			
 			          Visual Studio 2005
 
-    MAC OS  10.4 (Intel)          gcc i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 
+    MAC OS  10.5 (Intel)          gcc i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 
                                   G95 (GCC 4.0.3 (g95 0.91!) Nov 21 2006)
+                                  GNU Fortran (GCC) 4.3.0 20070810
     Alpha Open VMS 7.3
 
 
@@ -504,12 +534,8 @@ Supported Configuration Features Summary
 
 Platform                          C        F90    F90      C++   zlib  SZIP
                                   parallel        parallel
-SunOS5.8 64-bit                    n        y      n        y     y     y
-SunOS5.8 32-bit                    n        y      n        y     y     y
 SunOS5.10 64-bit                   n        y      n        y     y     y
 SunOS5.10 32-bit                   n        y      n        y     y     y
-IRIX64_6.5 64-bit                  n        y      y        y     y     y
-IRIX64_6.5 32-bit                  n        n      n        n     y     y
 AIX-5.2  32-bit                    y        y      y        y     y     y
 AIX-5.2  64-bit                    y        y      y        y     y     y
 Cray XT3 (not tested
@@ -517,8 +543,7 @@ Cray XT3 (not tested
 Windows XP                         n        y(3)   n(3)     y     y     y
 Windows XP x64                     n        y(3)   n(3)     y     y     y
 Windows Vista                      n        n      n        y     y     y
-Mac OS X 10.4 PowerPC              n               n
-Mac OS X 10.4 Intel                n        y      n        y     y     y
+Mac OS X 10.5 Intel                n        y      n        y     y     y
 FreeBSD 6.2 32-bit                 n        n      n        y     y     y
 FreeBSD 6.2 64-bit
 RedHat EL4 2.6.9 i686 GNU        W y(2)     y(4)   y(2)     y     y     y
@@ -539,12 +564,8 @@ Alpha OpenVMS 7.3.2                n        y      n        y     n     n
 
 Platform                          Shared   Shared    Shared    static-  Thread-
                                   C libs   F90 libs  C++ libs  exec     safe
-SunOS 5.8 32-bit                    y        y         y         x        y
-SunOS 5.8 64-bit                    y        y         y         x        y
 SunOS 5.10 32-bit                   y        y         y         x        y
 SunOS 5.10 64-bit                   y        y         y         x        y
-IRIX64_6.5 32-bit                   y        n         y         x        y
-IRIX64_6.5 64-bit                   y        y         n         x        y
 AIX-5.2 32-bit                      n        n         n         x        n
 AIX-5.2 64-bit                      n        n         n         x        n
 Cray XT3 (not tested
@@ -552,7 +573,7 @@ Cray XT3 (not tested
 Windows XP                          y        y(3)      y         y        y
 Windows XP x64                      y        y(3)      y         y        y
 Windows Vista                       y        n         n         y        y
-Mac OS X 10.4 Intel Duo             y        y         y         x        n
+Mac OS X 10.5 Intel                 y        y         y         x        n
 FreeBSD 6.2 32-bit                  y        y         y         x        n
 FreeBSD 6.2 64-bit                  y        y         y         x        n
 RHEL4 2.6.9 i686 GNU              W y        y(4)      y         x        y
@@ -580,6 +601,17 @@ SuSe Linux 2.6.5
 
 Known Problems
 ==============
+* Parallel mode in AIX will fail some of the testcheck_version.sh tests where
+  it treats "exit(134) the same as if process 0 had received an abort signal.
+  This is fixed and will be available in the next release. AKC - 2009/11/3
+
+* Some tests in tools/h5repack may fail in AIX systems when -q32 mode is used.
+  The error is due to insufficient memory requested. Request a large amount
+  of runtime memory by setting the following environment variable for more
+  memory.
+     LDR_CNTRL=MAXDATA=0x20000000@DSA
+  AKC - 2009/10/31
+
 * The PathScale MPI implementation, accessing a Panasas file system, would
   cause H5Fcreate() with H5F_ACC_EXCL to fail even when the file is not
   existing. This is due to the MPI_File_open() call failing if the amode has
@@ -590,26 +622,6 @@ Known Problems
   collective abort of all ranks at t_posix_compliant / allwrite_allread_blocks
   with MPI IO. (CMC - 2009/04/28)
 
-* We discovered two problems when running collective IO parallel HDF5 tests 
-  with chunking storage on  ChaMPIon MPI compiler on tungsten, a linux 
-  cluster at NCSA.
-  Under some complex selection cases, 
-  1) MPI_Get_element returns the wrong value.
-  2) MPI_Type_struct also generates wrong derived data type and corrupt data
-     may be generated.
-  This only happens when turning on collective IO with chunking storage 
-  with some complex selections. We haven't found these problems on other
-  MPI-IO compilers. If you encounter these problems, you may use Independent IO
-  instead.
-
-  Change the following line in your code:
-  H5Pset_dxpl_mpio(xfer_plist, H5FD_MPIO_COLLECTIVE);
-
-  to
-  H5Pset_dxpl_mpio(xfer_plist, H5FD_MPIO_INDEPENDENT);
-
-  KY - 2007/08/24
-
 * For SNL, spirit/liberty/thunderbird: The serial tests pass but parallel
   tests failed with MPI-IO file locking message. AKC - 2007/6/25.
 * On Intel 64 Linux cluster (RH 4, Linux 2.6.9) with Intel 10.0 compilers use
@@ -619,9 +631,6 @@ Known Problems
   shared libraries (tested for 1.8.0-beta2)
 * For SNL, Red Storm: only paralle HDF5 is supported.  The serial tests pass
   and the parallel tests also pass with lots of non-fatal error messages.
-* For LLNL, uP: both serial and parallel pass.  Zeus: serial passes but
-  parallel fails with a known proglem in MPI.  ubgl: serial passes but
-  parallel fails. 
 * on SUN 5.10 C++ test fails in the "Testing Shared Datatypes with Attributes" test 
 * configuring with --enable-debug=all produces compiler errors on most
   platforms.  Users who want to run HDF5 in debug mode should use
@@ -641,11 +650,6 @@ Known Problems
   contribute no IO and the application asks to do IO with collective, we found
   that when using 4 processors, a simple collective write will be hung
   sometimes. This can be verified with t_mpi test under testpar.
-* On IRIX6.5, when C compiler version >7.4, the complicate MPI derived data type
-  code will work. However, the user should be aware to enlarge MPI_TYPE_MAX environment 
-  variable to some certian value in order to use collective irregular selection code.
-  For example, the current parallel HDF5 test needs to enlarge MPI_TYPE_MAX to 
-  200,000 to make the test pass.
 * The dataset created or rewritten with the v1.6.3 library or after can't 
   be read with the v1.6.2 library or before when Fletcher32 EDC(filter) is 
   enabled.  There was a bug in the calculating code of the Fletcher32 
@@ -683,16 +687,13 @@ Known Problems
   test again, change the port address in test/stream_test.c to one not
   being used in the host.
 
-* The --enable-static-exec configure flag fails to compile for Solaris
-  platforms. This is due to the fact that not all of the system
-  libraries on Solaris are available in a static format.
-
-  The --enable-static-exec configure flag also fails to correctly compile
-  on IBM SP2 platform for the serial mode. The parallel mode works fine
-  with this option.
-  
-  It is suggested that you don't use this option on these platforms
-  during configuration.
+* The --enable-static-exec configure flag will only statically link libraries
+  if the static version of that library is present. If only the shared version
+  of a library exists (i.e., most system libraries on Solaris, AIX, and Mac,
+  for example, only have shared versions), the flag should still result in a 
+  successful compilation, but note that the installed executables will not be 
+  fully static. Thus, the only guarantee on these systems is that the 
+  executable is statically linked with just the HDF5 library.
 
 * With the gcc 2.95.2 compiler, HDF 5 uses the `-ansi' flag during
   compilation. The ANSI version of the compiler complains about not being
@@ -702,17 +703,6 @@ Known Problems
   
   This warning is innocuous and can be safely ignored.
 
-
-* The Stream VFD was not tested yet under Windows. It is not supported
-  in the TFLOPS machine.
-
-
-* The ./dsets tests failed in the TFLOPS machine if the test program,
-  dsets.c, is compiled with the -O option.  The hdf5 library still works
-  correctly with the -O option.  The test program works fine if it is
-  compiled with -O1 or -O0.  Only -O (same as -O2) causes the test
-  program to fail.
-
 * Certain platforms give false negatives when testing h5ls:
     - Cray J90 and Cray T90IEEE give errors during testing when displaying
       some floating-point values. These are benign differences due to