diff options
Diffstat (limited to 'release_docs')
| -rwxr-xr-x | release_docs/INSTALL_Windows_Short_NET.TXT | 16 | ||||
| -rwxr-xr-x | release_docs/INSTALL_Windows_Short_VS2005.TXT | 16 |
2 files changed, 6 insertions, 26 deletions
diff --git a/release_docs/INSTALL_Windows_Short_NET.TXT b/release_docs/INSTALL_Windows_Short_NET.TXT index 4b5855a..c60021c 100755 --- a/release_docs/INSTALL_Windows_Short_NET.TXT +++ b/release_docs/INSTALL_Windows_Short_NET.TXT @@ -150,19 +150,9 @@ hdf5check.bat has four options: Notes: Users who only build HDF5 C/C++ libraries ONLY have the first two options. -Invoke a command prompt window and run hdf5check with appropriate -options. - -Test results are saved in two files: - - c:\MyHDFstuff\hdf5\tests_results.txt - - c:\MyHDFstuff\hdf5\check_results.txt. - -In general, you only need to check tests_results.txt. If all the -tests passed, then you do not have to check check_results.txt. -If some tests failed, check check_results.txt can help you -figure out what was wrong. +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. diff --git a/release_docs/INSTALL_Windows_Short_VS2005.TXT b/release_docs/INSTALL_Windows_Short_VS2005.TXT index 957e7c1..c205852 100755 --- a/release_docs/INSTALL_Windows_Short_VS2005.TXT +++ b/release_docs/INSTALL_Windows_Short_VS2005.TXT @@ -149,19 +149,9 @@ hdf5check.bat has four options: Notes: Users who only build HDF5 C/C++ libraries ONLY have the first two options. -Invoke a command prompt window and run hdf5check with appropriate -options. - -Test results are saved in two files: - - c:\MyHDFstuff\hdf5\tests_results.txt - - c:\MyHDFstuff\hdf5\check_results.txt. - -In general, you only need to check tests_results.txt. If all the -tests passed, then you do not have to check check_results.txt. -If some tests failed, check check_results.txt can help you -figure out what was wrong. +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. |