MOSS Memory Management Simulator
Installation on Windows 95/98/Me/NT/2000 Systems

Purpose

This document provides instructions for the installation of the MOSS Memory Management Simulator on Microsoft Windows operating systems. This procedure should be the same or similar on Windows 95, 98, Me, NT, and 2000 systems. The MOSS software is designed for use with Andrew S. Tanenbaum, Modern Operating Systems, 2nd Edition (Prentice Hall, 2001). The Memory Management Simulator was written by Alex Reeder (alexr@e-sa.org). This installation guide was written by Ray Ontko (rayo@ontko.com).

This installation guide only provides information about installing the software and testing the configuration for Windows operating systems. To install on Unix-like operating systems, please read the Installation Guide for Unix/Linux/Solaris/HP-UX Systems. For more detailed information about the simulator, please read the User Guide.

Requirements

The following software components are required to install and use the MOSS Memory Management Simulator.

Microsoft Windows 95, 98, Me, NT, or 2000
Java Development Kit (JDK) 1.0 or greater
Text program editor (e.g., notepad)

Pre-Installation

Before installation, you should verify:

that you have a working java runtime environment,
that you have a working java development environment, and
that the working directory is in the classpath for the runtime environment.

If you're using a standard command-line java compiler, the following instructions will help determine if your environment is configured correctly.

Verify that you have java installed and configured in your environment.
```
C:\WINDOWS> java -version
```
You should see a message like this with possibly a different version number.
```
java version "1.1.8"
```
If you get a message like:
```
Bad command or file name
```
Then java may not be installed on your system, or may not be configured for your use.
If you think that Java may already be installed on your system but may not be in your "path", you can find it by choosing Start -> Find -> Files or Folders and enter "java.exe" in the "Named:" field and click the Find Now button. If found, make note of the directory folder in which it resides (e.g., "C:\jdk1.1.8\bin").
While you're at it, also seach for javac.exe to see if the Java compiler is installed and whether it's in the same directory as the java.exe file.
If Java isn't available on your system, you should check with your instructor or system administrator. If you administer your own system, then you should be able to find a copy of Java for your operating system.
If you find that java is installed but not configured for your use, then perhaps you need to add it to your path. Consult your instructor or system administrator if you need help adding this to your path.
Verify that the java compiler is installed and configured in your environment.
```
C:\WINDOWS> javac
```
If you're using a standard java command-line compiler, you should see a message similar to this.
```
use: javac [-g][-O][-debug][-depend][-nowarn][-verbose][-classpath path][-nowrite][-deprecation][-d dir][-J] file.java...
```
If you get a message like:
```
Bad command or file name
```
then the java compiler may not be installed on your system, or may not be configured for your use. Consult your instructor or system administrator.
Verify that that the current directory is in your classpath.
```
C:\WINDOWS> echo "%CLASSPATH%"
```
You should see a list of directories separated by semi-colons (";") or possibly just "". If you don't see the directory "." (a single period, which stands for the current directory), then you should add it to the classpath.
```
C:\WINDOWS> set CLASSPATH=.;%CLASSPATH%
```

If you have a working java runtime environment, a working java compiler, and the current directory is in your path, then you're ready to proceed with the installation.

Installation

Installation of the software can be accomplished with these simple steps:

Create a directory folder in which you wish to install the simulator (e.g., "C:\moss\memory"). You can do this using the Windows explorer, or from the MS-DOS prompt. To create the directory from the MS-DOS prompt:
```
C:\WINDOWS> cd \ 
C:\> mkdir moss
C:\> cd moss
C:\moss> mkdir memory
C:\moss> cd memory
C:\moss\memory>
```
Download the self-extracting ZIP archive (memory.exe) into the directory folder. The latest release for this file can always be found at http://www.ontko.com/moss/memory/memory.exe.
Double-click on the file you downloaded (memory.exe), or invoke it using Start -> Run..., or invoke it from an MS-DOS command prompt:
```
C:\moss\memory> memory.exe
```

Files

The directory should now contain the following files:

Files	Description
memory.exe	Self-extracting ZIP archive which contains all the other files.
Common.java ControlPanel.java Instruction.java Kernel.java MemoryManagement.java PageFault.java Page.java Virtual2Physical.java	Java source files (*.java)
Common.class ControlPanel.class Instruction.class Kernel.class MemoryManagement.class PageFault.class Page.class Virtual2Physical.class	Compiled Java class files (*.class)
commands	Sample input command file
memory.conf	Sample configuration file
install_unix.html install_windows.html user_guide.html user_guide_1.gif	Documentation and associated images
copying.txt	Gnu General Public License: Terms and Conditions for Copying, Distribution, and Modification

Compilation

The distribution includes compiled class files as well as the source java files. You should not need to recompile unless you decide to change the code. If you wish to compile the code, the following commands should work if you're using a Java compiler that accepts the normal "javac" command line.

C:\moss\memory> javac -nowarn *.java

The -nowarn flag supresses warning messges, of which there may be several. For backward compatability we use only those features of Java which have been present from the beginning, some of which are deprecated and are usually reported by the compiler with warning messages.

Test

To test the program, enter the following command line.

C:\moss\memory> java MemoryManagement commands memory.conf

The program will display a window allowing you to run the simulator. When the window presents itself, click on the Run button. You should see the program "execute" 7 memory operations, about one per second. When the simulation completes, click the Exit button.

The memory operation commands are read from a file called "commands", and the initial configuration and various options are specified in the file "memory.conf". The program also produces a log file called "tracefile" in the working directory.

The "commands" file looks something like this:

// Enter READ/WRITE commands into this file
// READ <OPTIONAL number type: bin/hex/oct> <virtual memory address or random>
// WRITE <OPTIONAL number type: bin/hex/oct> <virtual memory address or random>
READ bin 100
READ 19
WRITE hex CC32
READ bin 10000000000000000
READ bin 10000000000000000
WRITE bin 11000000000000001
WRITE random

If things are working correctly, the "tracefile" should look something like this:

READ 4 ... okay
READ 13 ... okay
WRITE 3acc32 ... okay
READ 10000000 ... okay
READ 10000000 ... okay
WRITE c0001000 ... page fault
WRITE 1ff82cdc ... okay

The program and its input and output files are described more fully in the MOSS Memory Management Simulator User Guide.

Please send suggestions, corrections, and comments to Ray Ontko (rayo@ontko.com).

Last updated: July 28, 2001

MOSS Memory Management Simulator Installation on Windows 95/98/Me/NT/2000 Systems