This is a port to Windows of GROMACS 3.3 obtained GROMACS on December 1, 2005.

This package has been modified both for compatibility with Windows and
to fix bugs that were found during the port.

Questions and comments about this Windows version of GROMACS 3.3 should
be directed to BioApps@tc.cornell.edu.

The package is available as a Microsoft Installer (.msi) file.  It will
install the source code, html help files, and a Microsoft Visual Studio
2003 solution and projects from which executables may be built.

The solution: gromacs-3.3\win32\gromacs\gromacs.sln is configured to place
the user programs it builds in gromacs-3.3\bin.  Inside that subdirectory
will be separate folders for single- and double-precision builds, and in-
side those folders, there will be further folders for debug (unoptimized)
and release (optimized) builds.  The solution comes with four build
configurations: Debug and Release (unoptimized and optimized single-precision
builds) and DoubleDebug and DoubleRelease (unoptimized and optimized
double-precision builds).  Visual Studio copies the appropriate config-
uration file to config.h in the same directory at the beginning of the
build, so the src directory must be writable.

Some of the configuration options are in configuration files: gromacs-3.3\
src\config.win-single-sse and .\config.win-double-sse2.  Other config-
uration information is in the Visual C/C++ project files.  The package is
configured to use the Intel Math Kernel Library for BLAS and FFT routines.
You should make sure that the include and library paths in Visual Studio
contain the appropriate Intel MKL directories.  If you choose to use
different libraries, the project link settings must be changed to
substitute the appropriate library names.

There is a Perl script gromacs-3.3\share\tutor\gmxdemo\demo.pl that can be 
used to test your installation.  It provides brief descriptions of what it
will be doing in a command window as it takes you through the process of
building the input files for GROMACS and running a short demo.  You must 
customize the script for your installation by placing the full path of
cpp.exe on line 7.  Also make sure that the directory in which you run the
test is writable.