Last updated: 18 Sep 2008 bw/rl/hs
(To check for possible updates to this document,
please see http://www.spec.org/mpi2007/Docs/)
Contents
The SPEC MPI2007 suite has been tested under Unix, Linux, and Windows Server 2003 systems. Your DVD can be installed under many operating systems.
Reminder: the SPEC license allows you to install on multiple systems as you may wish within your institution; but you may not share the software with the public.
This document covers the installation procedure for SPEC MPI2007 under Microsoft Windows.
Note: Unless otherwise specified, refererences to "Windows" in this document apply to Windows XP, and Windows Server 2003. Later and/or earlier versions of Windows/NT-based systems (such as Windows 2000) might also work, but have not been tested. Windows/98 and Windows/Me will definitely not work.
The installation procedure for Windows is as follows:
Review the hardware and software requirements, in system-requirements.html
Note: links to SPEC MPI2007 documents on this web page assume that you are reading the page from a directory that also contains the other SPEC MPI2007 documents. If by some chance you are reading this web page from a location where the links do not work, try accessing the referenced documents at one of the following locations:
Note: the steps that follow assume that your DVD drive is on the same system as where you wish to install. If it is on a different system, please see the appendix.
Open a Command Prompt windows (formerly known as an "MSDOS Window"). Typically, this is done by
selecting:
Start-->All Programs-->Accessories-->Command Prompt.
Adjust the properties to allow you to see plenty of lines scrolled off the top (for example, 9000). Click the upper left corner of the Command Prompt window, scroll down to "Properties", click the "Layout" tab, and in the section labelled "Screen Buffer Size" enter a new value for "Height".
Check to see whether or not the temp environment variable points to a directory that can be used to hold for temporary files.
C:\> echo %temp%
%temp%
If it's unset (just prints %temp%), you should set it to the full path (with drive letter) to a directory that can be used as scratch space. For example, if George would like to use a temporary directory underneath his directory on drive K:, he could type:
C:\> set temp=K:\GEORGE\TEMP
Decide where you want to install the MPI2007 suite. You should make sure that your chosen destination disk has at least 25GB free. (For more information on disk usage, see system-requirements.html.) For the following examples, we will assume that your destination is on drive D:, in the directory \mpi2007.
Change to the DVD directory. For the following examples, we'll assume that your DVD is mounted on drive E:.
You're now ready to run the installer. The format for this command is
install.bat destination_drive destination_directory
For example, if your DVD is in drive E:, and you want to install MPI2007 on drive D:, you could type:
C:\> E:
E:\> install.bat D: \mpi2007
Please notice the space between D: and \mpi2007. It's very important.
You should see a message similar to the following:
The environment variable SPEC should point to the source of the
SPEC distribution (as an absolute path). I will now try to set
the variable for you...
SPEC is set to E:\
If this is NOT what you want, press control-C
Press any key to continue . . .
If you see a message similar to the above, just press return. If you receive an error message such as:
Access is denied
then please verify that %temp% is defined (see above).
If you see the message
First parameter must be in the form c:
make sure that you included the space between the drive name and the directory. If you did, and you still see the message, then make sure that your path includes the usual system directories. If it doesn't, you may be able to fix it by typing:
E:\> set path=%systemroot%\;%systemroot%\system32;%path%
If all goes well, you'll see several messages indicating that files are being unpacked. Please be patient - although only a few messages are printed, thousands of files are installed.
The installation will consume around 1.0GB on your destination disk.
After this step completes, you will find yourself in the destination directory that you selected.
Read the comments to the file
shrc.bat
and make the appropriate edits for your compiler paths. Caution: you may find that the lines are not correctly formatted (the text appears to be all run together) when you edit this file. If so, see the section below: Using Text Files on Windows.
Set the environment, using your edited shrc. For example:
D:\mpi2007> shrc.bat
Test that you can build a benchmark using the config file supplied for your system. Example config files can be found in %SPEC%\config. (For an introduction to config files, see "About Config Files" in runspec.html.)
In the example below, "^" (often called "hat" or "carat") indicates line continuation:
D:\mpi2007> runspec --action=build --tune=base ^
More? --config=hpmpi-win-amd64-pgi7.cfg 122.tachyon
The --tune=base indicates that we want to use only the simple tuning, if the file contains more than one kind of tuning.
Test that you can run a benchmark, using the minimal input set - the "mtest" workload. For example:
D:\mpi2007> runspec --size=mtest --iterations=1 --noreportable ^
More? --config=hpmpi-win-amd64-pgi7.cfg 122.tachyon
The --noreportable ensures that the tools will allow us to run just a single benchmark instead of the whole suite.
Test that you can run a benchmark using the real input set - the "reference" workload. For example:
D:\mpi2007> runspec --size=mref --config=hpmpi-win-amd64-pgi7.cfg ^
More? --iterations=1 --noreportable 122.tachyon
Have a look at runspec.html to learn how to do a full run of the suite.
There are many files in the SPEC MPI2007 kit that contain text. Unfortunately, Unix systems and Windows systems have different conventions for storing text files. Sometimes, a text file formatted for Windows will appear on Unix as if it has extra Control-M characters. Sometimes, a text file formatted for Unix will appear on Windows as if all the lines were joined together.
There are at least three ways for Windows users to correctly view and edit text files that originated on a Unix system:
Use WordPad. WordPad can commonly be found by
Start-->All Programs-->Accessories-->WordPad
Use a Command Prompt and type "Edit". This alternative works only if the file has a short name with 8 characters or fewer, a dot, and then 3 characters or fewer. If you are trying to use Edit with a longer file name, you can discover that there is an "8 dot 3" synonym for it by typing: "dir /x".
Use the editor "vi". Although vi originated on Unix systems, it is also often found on Windows systems. For example:
There is a free ("charityware") version with some non-traditional features known as "Vi IMproved" (at http://www.vim.org/).
There is a version with the traditional Unix features in the MKS Toolkit (http://www.datafocus.com/products/tk/).
Also, there was a version with a subset of the traditional Unix vi features in the "Microsoft Windows Windows Workstation 4.0 Resource Kit" (information available at http://mspress.microsoft.com); perhaps later resource kit versions also have it, but this has not been checked.
Note that mention of these versions of vi is not intended as an endorsement by SPEC.
Here is a complete Windows installation, with commentary. We assume that Steps 1 and 2 are already done (from the list of Installation Steps earlier in this document).
Step 3: Check the temp environment variable.
C:\>echo %temp% C:\TEMP
Step 4: Create a place for the suite, and check space.
C:\>D:
D:\>mkdir mpi2007
D:\>cd mpi2007
D:\mpi2007>dir
Volume in drive D has no label
Volume Serial Number is F843-4C63
Directory of D:\mpi2007
06/01/2007 06:05 PM <DIR> .
06/01/2007 06:05 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 6,964,436,992 bytes free
Note that we have about 7GB of space on the destination drive, which is a bit smaller than recommended. This is enough space to demonstrate an installation, but would quickly fill up for actual "reportable" runs.
Step 5: change to the drive where the DVD is mounted
D:\mpi2007>e:
Step 6: Actually do the installation. Note the presence of a space in between "D:" and "\mpi2007".
E:\>install.bat D: \mpi2007 The environment variable SPEC should point to the source of the SPEC distribution as an absolute path. I will now try to set the variable for you... SPEC is set to E:\ If this is NOT what you want, press control-C Press any key to continue . . . Installing from "E:\" Depending on the speed of the drive holding your installation media and the speed of your destination disk, this may take more than 5 minutes. Please be patient. Unpacking MPI2007 base files (7 MB) ... Checking the integrity of your source tree... Depending on the amount of memory in your system, and the speed of your destination disk, this may take more than 10 minutes. Please be patient. Unpacking tools binaries Setting SPEC environment variable to D:\mpi2007 Checking the integrity of your binary tools... Installation completed!
Step 7: Edit shrc.bat. This was done in a notepad session, which is not shown, but the "fc" command is used below to compare the original shrc.bat to our modified copy:
D:\mpi2007>copy shrc.bat shrc.bat.as-distributed
1 file(s) copied.
D:\mpi2007>notepad shrc.bat
D:\mpi2007>fc shrc.bat.as-distributed shrc.bat
Comparing files shrc.bat.as-distributed and SHRC.BAT
***** shrc.bat.as-distributed
rem the line that follows (just remove the word 'rem').
rem set SHRC_COMPILER_PATH_SET=yes
rem
***** SHRC.BAT
rem the line that follows (just remove the word 'rem').
set SHRC_COMPILER_PATH_SET=yes
rem
*****
Step 8: set the environment
D:\mpi2007>shrc PATH=^ "D:\mpi2007\bin";^ D:\PROGRA~1\PGI\win64\6.2-1\bin;^ D:\Program Files\Microsoft Platform SDK\bin\win64\x86\AMD64;^ D:\WINDOWS\system32;^ D:\WINDOWS D:\mpi2007>pgcc -V pgcc 6.2-1 64-bit target on x86-64 Windows Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved. Copyright 2000-2007, STMicroelectronics, Inc. All Rights Reserved.
Step 9. Use runspec to do a test build:
D:\mpi2007>runspec --action=build --tune=base --config=hpmpi-win-amd64-pgi7.cfg 122.tachyon runspec v4283 - Copyright 1999-2007 Standard Performance Evaluation Corporation Using 'windows-i386 ' tools Reading MANIFEST... 18018 files Loading runspec modules............... Locating benchmarks...found 13 benchmarks in 16 benchsets. Locating output formats: ASCII, config, CSV, flags, html, mail, PDF, PostScript, raw, Screen, Submission Check Reading config file 'D:/mpi2007/config/hpmpi-win-amd64-pgi7.cfg' Benchmarks selected: 122.tachyon Compiling Binaries Building 122.tachyon test base win64-pgi default: (build_base_win64-pgi.0000) Build successes: 122.tachyon(base) Build Complete The log for this run is in D:\mpi2007/result/MPI2007.005.log runspec finished at Thu Jun 1 19:11:37 2007; 80 total seconds elapsed D:\mpi2007>
At this point, we've accomplished a lot. The SPEC tree is installed, and we have verified that a benchmark can be compiled using the installed C compiler.
Step 10. Now try running a benchmark, using the minimal mtest workload. The mtest workload runs in a tiny amount of time and does a minimal verification that the benchmark executable can at least start up:
D:\mpi2007>runspec --size=mtest --iterations=1 --noreportable --config=hpmpi-win-amd64-pgi7.cfg 122.tachyon
runspec v4283 - Copyright 1999-2007 Standard Performance Evaluation Corporation
Using 'windows-i386 ' tools
Reading MANIFEST... 18018 files
Loading runspec modules...............
Locating benchmarks...found 13 benchmarks in 16 benchsets.
Locating output formats: ASCII, config, CSV, flags, html, mail, PDF, PostScript, raw, Screen, Submission Check
Reading config file 'D:/mpi2007/config/hpmpi-wind-amd64-pgi7.cfg'
Benchmarks selected: 122.tachyon
Compiling Binaries
Up to date 122.tachyon mtest base win64-pgi default
Parsing Flags
Looking at 122.tachyon base win64-pgi default: done
Flag Parsing Complete
Setting Up Run Directories
Setting up 122.tachyon mtest base win64-pgi default: created (run_base_mtest_win64-pgi.0000)
Running Benchmarks
Running 122.tachyon mtest base win64-pgi default
Success: 1x122.tachyon
Producing Reports
mach: default
ext: win64-pgi
size: mtest
set: medium
format: raw -> D:/mpi2007/result/MPI2007.006.mtest.rsf
format: flags -> D:/mpi2007/result/MPI2007.006.mtest.flags.html
format: ASCII -> D:/mpi2007/result/MPI2007.006.mtest.txt
format: PDF -> D:/mpi2007/result/MPI2007.006.mtest.pdf
The log for this run is in D:\mpi2007/result/MPI2007.006.log
runspec finished at Thu Jun 1 19:14:47 2007; 75 total seconds elapsed
Notice about 15 lines up where it says "Success: 1x122.tachyon". That is what we want to see.
Step 11. So, let's try running 122.tachyon with the real workload. This is going to take a while - on the system used for the sample installation, about an hour.
D:\mpi2007>runspec --size=mref --iterations=1 --noreportable --config=hpmpi-win-amd64-pgi7.cfg 122.tachyon
runspec v4283 - Copyright 1999-2007 Standard Performance Evaluation Corporation
Using 'windows-i386 ' tools
Reading MANIFEST... 18018 files
Loading runspec modules...............
Locating benchmarks...found 13 benchmarks in 16 benchsets.
Locating output formats: ASCII, config, CSV, flags, html, mail, PDF,
PostScript, raw, Screen, Submission Check
Reading config file 'D:/mpi2007/config/hpmpi-win-amd64-pgi7.cfg'
Benchmarks selected: 122.tachyon
Compiling Binaries
Up to date 122.tachyon mref base win64-pgi default
Parsing Flags
Looking at 122.tachyon base win64-pgi default: done
Flag Parsing Complete
Setting Up Run Directories
Setting up 122.tachyon mref base win64-pgi default: created (run_base_mref_win64-pgi.0000)
Running Benchmarks
Running 122.tachyon mref base win64-pgi default
Success: 1x122.tachyon
Producing Reports
mach: default
ext: win64-pgi
size: mref
set: int
format: raw -> D:/mpi2007/result/MPI2007.008.mref.rsf
format: flags -> D:/mpi2007/result/MPI2007.008.flags.html
format: ASCII -> D:/mpi2007/result/MPI2007.008.mref.txt
format: PDF -> D:/mpi2007/result/MPI2007.008.mref.pdf
The log for this run is in D:\mpi2007/result/MPI2007.008.log
runspec finished at Thu Jun 1 20:36:30 2007; 3434 total seconds elapsed
Success with the real workload! So now let's look in the result directory and see what we find:
D:\mpi2007>cd result
D:\mpi2007\result>dir
Volume in drive D is has no label
Volume Serial Number is F843-4C63
Directory of D:\mpi2007\result
06/01/2007 08:36 PM <DIR> .
06/01/2007 08:36 PM <DIR> ..
06/01/2007 07:14 PM 6,680 MPI2007.006.mtest.flags.html
06/01/2007 07:14 PM 51,828 MPI2007.006.mtest.pdf
06/01/2007 07:14 PM 7,026 MPI2007.006.mtest.rsf
06/01/2007 07:14 PM 7,748 MPI2007.006.mtest.txt
06/01/2007 07:38 PM 6,680 MPI2007.007.mtest.flags.html
06/01/2007 07:38 PM 51,821 MPI2007.007.mtest.pdf
06/01/2007 07:38 PM 7,024 MPI2007.007.mtest.rsf
06/01/2007 07:38 PM 7,748 MPI2007.007.mtest.txt
06/01/2007 08:36 PM 6,680 MPI2007.008.mref.flags.html
06/01/2007 08:36 PM 52,341 MPI2007.008.mref.pdf
06/01/2007 08:36 PM 6,952 MPI2007.008.mref.rsf
06/01/2007 08:36 PM 7,588 MPI2007.008.mref.txt
06/01/2007 07:05 PM 6,425 MPI2007.001.log
06/01/2007 07:06 PM 7,268 MPI2007.002.log
06/01/2007 07:07 PM 7,474 MPI2007.003.log
06/01/2007 07:10 PM 1,488 MPI2007.004.log
06/01/2007 07:11 PM 9,795 MPI2007.005.log
06/01/2007 07:14 PM 3,889 MPI2007.006.log
06/01/2007 07:38 PM 3,887 MPI2007.007.log
06/01/2007 08:36 PM 5,166 MPI2007.008.log
06/01/2007 07:39 PM 5 MPI2007.lock
06/01/2007 06:46 PM <DIR> images
21 File(s) 265,513 bytes
3 Dir(s) 4,489,633,792 bytes free
Notice the log files from our runspec commands. Those runspec commands are easily extracted with "findstr":
D:\mpi2007\result>findstr /C:"runspec --" *.log MPI2007.005.log:runspec: runspec --action=build --tune=base --config=hpmpi-win-amd64-pgi7.cfg 122.tachyon MPI2007.005.log:runspec = D:\\mpi2007\\bin\\runspec --action=build --tune=base --config=hpmpi-win-amd64-pgi7.cfg 122.tachyon MPI2007.006.log:runspec: runspec --size=mtest --iterations=1 --noreportable --config=hpmpi-win-amd64-pgi7.cfg 122.tachyon MPI2007.008.log:runspec: runspec --size=mref --iterations=1 --noreportable --config=hpmpi-win-amd64-pgi7 122.tachyon
Let's look at our results, in the ".txt" file:
D:\mpi2007\result>type MPI2007.008.mref.txt
##############################################################################
# INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN #
# #
# 'reportable' flag not set during run #
# 137.lu base did not have enough runs! #
# 132.zeusmp2 base did not have enough runs! #
# 126.lammps base did not have enough runs! #
# 127.wrf2 base did not have enough runs! #
# 121.pop2 base did not have enough runs! #
# 115.fds4 base did not have enough runs! #
# 129.tera_tf base did not have enough runs! #
# 130.socorro base did not have enough runs! #
# 107.leslie3d base did not have enough runs! #
# 128.GAPgeofem base did not have enough runs! #
# 113.GemsFDTD base did not have enough runs! #
# 122.tachyon base did not have enough runs! #
# 104.milc base did not have enough runs! #
# Unknown flags were used! See #
# http://www.spec.org/auto/mpi2007/Docs/runspec.html#flagsurl #
# for information about how to get rid of this error. #
# #
# INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN #
##############################################################################
SPEC MPIM2007 Summary
-- --
Mon Mar 19 20:16:41 2007
MPI2007 License #0
Test sponsor: -- Tester: --
Test date: -- Hardware avail: -- Software avail: --
Estimated Estimated
Base Base Base Peak Peak Peak
Benchmarks Ref. Run Time Ratio Ref. Run Time Ratio
-------------- ------ --------- --------- ------ --------- ---------
104.milc NR
107.leslie3d NR
113.GemsFDTD NR
115.fds4 NR
121.pop2 NR
122.tachyon 2797 3616 0.773 S
126.lammps NR
127.wrf2 NR
128.GAPgeofem NR
129.tera_tf NR
130.socorro NR
132.zeusmp2 NR
137.lu NR
==============================================================================
104.milc NR
107.leslie3d NR
113.GemsFDTD NR
115.fds4 NR
121.pop2 NR
122.tachyon 2797 3616 0.773 S
126.lammps NR
127.wrf2 NR
128.GAPgeofem NR
129.tera_tf NR
130.socorro NR
132.zeusmp2 NR
137.lu NR
Est. SPECmpiM_base2007 --
Est. SPECmpiM_peak2007 Not Run
In the table above, most of the results are blank, because we only ran 1 of the 12 integer benchmarks.
Notice that the values for SPECmpiM_base2007 and SPECmpiM_peak2007 are "--" and "Not Run"; these would be filled in if we did a "reportable" run; for information, please see "--reportable" in runspec.html
There are also lots of dashes for the various portions of the system description, both at the top of the page and in the section that follows. These dashes indicate that we have not filled in the fields that describe the hardware and software that we are testing. For information about these fields, please see config.html
HARDWARE
--------
CPU Name: --
CPU Characteristics:
CPU MHz: --
FPU: --
CPU(s) enabled: -1 cores, -1 chips, -1 cores/chip, -1 threads/core
CPU(s) orderable: --
Primary Cache: --
Secondary Cache: --
L3 Cache: --
Other Cache: --
Memory: --
Disk Subsystem: --
Other Hardware: --
SOFTWARE
--------
Operating System: --
Compiler: --
Auto Parallel: --
File System: --
System State: --
Base Pointers: --
Peak Pointers: --
Other Software: --
Base Unknown Flags
------------------
122.tachyon: "mpicc -mpicc pathcc" (in CC) "mpicc -mpicc pathcc" (in LD)
"-mcpu=auto -Ofast -LANG:copyinout=OFF" (in COPTIMIZE)
Base Compiler Invocation
------------------------
C benchmarks:
122.tachyon: No flags used
Base Portability Flags
----------------------
C benchmarks:
122.tachyon: No flags used
Base Optimization Flags
-----------------------
C benchmarks:
122.tachyon: No flags used
Base Other Flags
----------------
C benchmarks:
122.tachyon: No flags used
All brand and product names appearing in this result are trademarks or
registered trademarks of their respective holders.
##############################################################################
# INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN #
# #
# 'reportable' flag not set during run #
# 137.lu base did not have enough runs! #
# 132.zeusmp2 base did not have enough runs! #
# 126.lammps base did not have enough runs! #
# 127.wrf2 base did not have enough runs! #
# 121.pop2 base did not have enough runs! #
# 115.fds4 base did not have enough runs! #
# 129.tera_tf base did not have enough runs! #
# 130.socorro base did not have enough runs! #
# 107.leslie3d base did not have enough runs! #
# 128.GAPgeofem base did not have enough runs! #
# 113.GemsFDTD base did not have enough runs! #
# 122.tachyon base did not have enough runs! #
# 104.milc base did not have enough runs! #
# Unknown flags were used! See #
# http://www.spec.org/auto/mpi2007/Docs/runspec.html#flagsurl #
# for information about how to get rid of this error. #
# #
# INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN #
##############################################################################
-----------------------------------------------------------------------------
For questions about this result, please contact the tester.
For other inquiries, please contact [email protected].
Copyright 2007 Standard Performance Evaluation Corporation
Generated on Mon Mar 19 21:17:13 2007 by SPEC MPI2007 ASCII formatter v607
Done. The suite is installed, and we can run at least one benchmark for real.
If the title of this section describes your situation, you basically have two choices.
You might be able to mount the DVD on one system and use network services to make it available on other systems.
Please note that the SPEC MPI2007 license agreement does not allow you to post the DVD on any public server. If your institution has a SPEC MPI2007 license, then it's fine to post it on an internal server that is accessible only to members of your institution.
Whether you attempt a network mount will probably depend on:
If your network environment allows easy cross-system mounting, you can use a network mount for the installation. Otherwise, you can fall back on the tar file.
Note: if you insert the DVD on a system running Unix or Linux, you may need to share it using nfs commands. This Windows installation guide does not attempt to give hints about how to do Unix nfs commands, although you will find some hints in the corresponding appendix of install-guide-unix.html. Instead, let's assume that you are using two Windows systems. System A is a Windows system with a DVD drive; System B is a Windows system where you would like to do the installation.
To do the installation:
At System A, insert the DVD.
Then, bring up a Windows Explorer window (for example, by double clicking on the My Documents icon). Click the plus sign next to My Computer and you should see the DVD drive. Let's suppose that it is drive F:.
Right-click on the DVD drive and select "Sharing and Security..."
In the box that comes up, under the "Sharing" tab, you may see a warning To protect your computer from unauthorized access, sharing the root of a dive is not recommended. If you understand the risk but still want to share the root of the drive, click here. This most informative warning is displayed for your consideration and you can proceed to consider it. If you decide that it is safe to share your DVD drive, then click where indicated.
Select "Share this folder"
Now, move to System B.
Bring up a Windows Explorer window (for example, by double clicking on the My Documents icon). Select Tools -> Map Network Drive. The Drive letter may offer a default, such as Z:. In the box for Folder, type two backslashes, the name of system A, a backslash, and its shared drive letter - for example \\SystemA\F
Continue with Step 2 above. When you get to Steps 5 and 6, remember to use the drive letter as it is known on System B - from the dialog box of a moment ago - for example
D:\Documents and Settings\Saturos\> Z: Z:\> install.bat C: \mpi2007
If the DVD drive is on a system other than the one where you wish to do the installation, and if you do not wish to try to get a network mount working, then the final fallback is to use the compressed tarfile. If you choose this option, please carefully observe the warnings.
Go to the system with the DVD drive ("System A"). Insert the SPEC MPI2007 DVD.
From a command window (aka terminal window), cd to the top level directory on the DVD.
You are going to retrieve five things from the DVD. First, find the large tarfile and its corresponding md5 file:
cd original.src dir mpi2007.tar.bz*
or, if System A is a Unix system, then:
cd original.src ls -l mpi2007.tar.bz*
In either case, you should see one moderately large file > 450MB, mpi2007.tar.bz2, and a small file associated with it that contains a checksum, mpi2007.tar.bz2.md5.
If you don't see the above files, try looking for cpu*tar*. The name might change if, for example, a maintenance update of MPI2007 changes the name slightly to indicate an updated version.
Do whatever is required in order to transfer both files intact to the system where you wish to do the installation ("System B"). If you use ftp, do not forget to use image (binary) mode. For example:
ftp> bin <-------- important
200 Type set to I.
ftp> put mpi2007.tar.bz2
ftp> put mpi2007.tar.bz2.md5
Please note that the SPEC MPI2007 license agreement does not allow you to post the above file on any public ftp server. If your institution has a SPEC MPI2007 license, then it's fine to post it on an internal server that is accessible only to members of your institution.
Next, you are going to retrieve specbzip2.exe, specmd5sum.exe, and spectar.exe from the DVD.
Please do not use Windows Zip utilities, as these will not preserve line endings and will cause difficult-to-diagnose benchmark miscompares.
Please do not use other tar utilities, as these may not handle long path names. Many commonly-supplied tar utilities cannnot.
If you have GNU tar and the genuine bzip2, then you can use those; otherwise, look around on the DVD to find the SPEC-supplied versions, like so:
C:\> F:
F:\> cd tools
F:\tools> cd bin
F:\tools\bin> dir
Volume in drive F is SPEC_MPI2007v097
Volume Serial Number is 8A74-DF2E
Directory of F:\tools\bin
07/18/2007 01:37 PM <DIR> .
04/04/2007 09:48 PM <DIR> ..
12/23/2005 11:56 PM <DIR> aix5L-ppc
05/30/2007 08:30 PM <DIR> freebsd54-ia32
05/30/2007 08:30 PM <DIR> freebsd60-ia32
01/28/2007 06:54 PM <DIR> hpux-11iv2-ipf
01/27/2007 07:10 PM <DIR> hpux-11iv2-parisc
01/04/2007 11:36 AM <DIR> irix6.5-mips
12/18/2005 01:59 AM <DIR> linux-redhat62-ia32
01/11/2007 10:30 AM <DIR> linux-rhas3r2-ia64
06/27/2007 10:26 PM <DIR> linux-suse101-AMD64
07/18/2007 01:37 PM <DIR> linux-suse101-i386
12/18/2005 02:44 PM <DIR> linux-ydl20-ppc
12/18/2005 02:44 PM <DIR> macosx-ppc
01/03/2007 10:28 PM <DIR> macosx-x86
05/30/2007 08:30 PM <DIR> netbsd21-ia32
05/30/2007 08:30 PM <DIR> openbsd38-ia32
01/03/2007 10:41 AM <DIR> sles9-glibc23-ia64
12/18/2005 01:59 AM <DIR> solaris-sparc
12/18/2005 01:59 AM <DIR> solaris-x86
05/30/2007 08:30 PM <DIR> tru64-alpha
04/24/2007 09:41 AM <DIR> windows-i386
0 File(s) 0 bytes
22 Dir(s) 0 bytes free
F:\tools\bin> cd win*
F:\tools\bin\windows-i386> dir
Volume in drive Z is SPEC_MPI2007v097
Volume Serial Number is 8A74-DF2E
Directory of Z:\tools\bin\windows-i386
04/24/2007 09:41 AM <DIR> .
07/18/2007 01:37 PM <DIR> ..
04/22/2007 07:54 PM 10,767,231 mpi2007tools-windows-i386.tar.bz2
04/22/2007 07:54 PM 131,072 specbzip2.exe
04/22/2007 07:54 PM 65,536 specmd5sum.exe
04/22/2007 07:54 PM 189,440 spectar.exe
4 File(s) 11,153,279 bytes
2 Dir(s) 0 bytes free
Once you've found these versions of specbzip2, specmd5sum, and spectar, transfer them to system B using the same methods that you used for the big tarfile.
On system B, use specmd5sum to check that the file transfer worked correctly. In this example, we assume that you have placed all 5 of the files mentioned above in the \kits\ directory on drive C::
C:\kits\> specmd5sum -c mpi2007.tar.bz2.md5 mpi2007.tar.bz2: OK
Pick a disk with 16GB free, go there, and unpack the tarfile, like so:
C:\kits\> H: H:\> mkdir mpi2007 H:\> cd mpi2007 H:\mpi2007\> C:\kits\specbzip2 -dc C:\kits\mpi2007.tar.bz2 | C:\kits\spectar -xf -
Be patient: it will take bit of time to unpack! It might take 15 minutes, depending on the speed of your processor and disks. Go for a coffee break.
Now, type install, without any arguments afterwards. That is, unlike the instructions in step 6 above, you do not need to mention a device or directory if you are installing from the tarfile. You will see output similar, though not identical, to that shown in the example installation -- the messages about Unpacking xxxx are not printed, because you already did the unpacking with your spectar command.
Continue with step 7, above.
Copyright © 1999-2010 Standard Performance Evaluation Corporation
All Rights Reserved