[PREVIOUS] [NEXT] - [Home] [Installation [Configurations] [Problems and Limitations]

Configurations Supported by Visual Modeler 2.0

Configurations Supported by Visual Modeler 2.0

Visual Modeler 2.0 System Requirements

To install and run Visual Modeler 2.0 successfully on Windows, you need:

Item Requirement

Computer

Personal computer with an 80486- or Pentium-compatible processor, or Digital Alpha/Windows NT personal workstation

Memory

At least 32 MB of RAM is recommended

Disk space

25 MB for Visual Modeler, plus 1-3 MB for each model; Visual Modeler data files require about twice the space used by the source code files

Disk drive

CD-ROM drive for installation

Display

VGA-compatible graphics card and monitor; 256 or more colors recommended

Mouse

Any pointing device with at least two buttons

Printer

Any standard PostScript or PCL5 printer (optional)

Printing Visual Modeler files requires no additional printer setup. If you have printer problems, try one of the following:

Operating system

Microsoft© Windows 95 or Windows NT 4.0

Swap Files

When working with large model files, Visual Modeler runs faster with a permanent swap file. You can set this from the Windows Control Panel. If Visual Modeler reports "low memory" during normal operation, increase the size of permanent virtual memory.

Video Cards and Drivers

Visual Modeler was tested with a number of video cards and drivers. The Diamond Viper Pro Video card required the driver be updated to driver 3.5 v1.2 on Windows NT. If you experience display problems with other video card and driver combinations, check with the video card vendor to see if an updated driver is available that may correct the problem.

Visual Modeler uses the current font size, among other factors, to determine the optimal size of a class icon when autosizing it. If your video driver supports large and small fonts, you may notice that a class that was autosized and saved with small fonts does not appear autosized correctly when read in using large fonts, and vice-versa. You can correct this by either:

Printers and Printer Drivers

If you experience printing problems with other printer and driver combinations, check with the printer vendor to see if an updated driver is available that may correct the problem.

Windows 95 Mouse Driver

The EM_EXEC.exe mouse driver file on some Windows 95 PCs-especially laptops-that interferes with Visual Modeler. (The typical symptom is a crash while you are entering a class name directly on a class diagram, but Visual Modeler may also crash at other times with varying frequency.)

This mouse driver file must be deleted or renamed for Visual Modeler to function properly:

  1. Start your PC in command prompt mode. (Press F5 during boot and select command prompt start.)
  2. Go to the C:\mouse\system directory.
  3. Delete or rename the file EM_EXEC.exe. This should not impact any Windows 95 performance.
  4. Do a normal reboot.

To install a newer version of the driver, which does not interfere with Visual Modeler:

  1. Contact Logitech to get an update. The update can be found at ftp://ftp.logitech.com/TechSupport/MOUSE. The name of the file is mw7aol.exe, May 3, 1996 101k.
  2. When you execute that file, it will be expanded into several other files, including a later version of EM_EXEC.exe which should work together with Visual Modeler.

Another mouse product that may interfere with Visual Modeler is the Microsoft IntelliMouse, which comes with a mouse driver called Point32.exe. To solve this problem, bring up the task list in Windows and end the task called "point32".

[PREVIOUS] [NEXT] - [Home] [Installation] [Configurations] [Problems and Limitations]