University of Illinois Graduate School of Library and Information Science ISRL
Please read these instructions before installing M2K 1.1.4. Improper installation of M2K 1.1.4 could result in files being overwritten or new modules not compiling properly.
1. Uninstall D2K. The easiest way is to just move the directory to a new location for backup.
2. Reinstall D2K. M2K installation goes more smoothly with a fresh install of D2K.
3. Run D2K once, then exit the program.
4. Unpack M2K 1.1.4 to a temp directory. You should see several folders and files, as well as the installer batch file, install.bat (Windows) or install.sh (Linux/MacOS).
If you installed D2K into the default location, you can skip the following step:
5. Edit build.properties so that d2k.dir is set to the directory where you installed D2K. For instance if you installed D2K into D:\MyStuff\D2KToolkit, build.properties should contain the line
d2k.dir=D:\MyStuff\D2KToolkit
This next issue only applies for users who compile their own M2K modules:
6. Set the JAVA_HOME variable.
In Windows, the JAVA_HOME variable can be set by opening a command prompt and typing (without the quotes): "set JAVA_HOME=C:\j2sdk1.4.2" where the directory that JAVA_HOME is assigned to is wherever you installed your SDK.
In Linux or MacOS, open a bash shell and type "export JAVA_HOME=usr/local/j2sdk1.4.2" (without the quotes).
7. Run the install file, install.bat (Windows) or install.sh (Linux/MacOS).
8. Copy your modified itineraries and binaries from your old D2K install to your new one.
If you have additional M2K install questions, please visit the M2K Installation issues Help Forum.
Maintained by: J. Stephen
Downie
Comments to: jdownie at uiuc dot edu
Last modified: 7 July 2005