Release 1.1 - 10/11/99

• Support for Windows 2000 guest operating system.
• Support for bidirectional parallel ports. See this note for more details.
• Support for kernel versions 2.2.10 and later.
• Support for large memory systems.
• Improved support for raw disk file configuration (/dev/hda through /dev/hdl) via the Configuration Wizard.
• Improved support for raw disk file configuration via the Configuration Editor. See this note for more details.
• Improved support for upgrading Linux kernels and for uninstalling the product.
• Experimental support for rpm installations.
• Improved SMP performance in kernel versions 2.2.8 and later.
• Improved built-in help.
• Y2K bug fixes.
• Modifications to VMware's PCI vendor ID.

  IMPORTANT: By default the product will be installed into /usr/bin. Prior versions of the product were installed into /usr/local/bin.

  IMPORTANT: PLEASE READ if upgrading from Released version 1.0.x -- New change regarding VMware for Linux

  The PCI vendor ID for the VMware virtual display adapter has changed in this release.

  When users of the released version (1.0.x) upgrade to this release, the PCI vendor ID change will affect how Plug and Play aware guest operating systems will behave the first time they boot. The instructions below explain how to configure the guest operating system to properly match a driver to the new vendor ID.

  When Windows 95, Windows 98 and Windows 2000 detect the ID change, they will prompt you to install a driver for the new virtual PCI/Plug and Play device:

  1. Click the Cancel button to allow the operating system to boot completely.
  2. Double click on the Add/Remove Programs icon from the Control Panel.
  3. Remove the VMware Tools for Windows software package.
  4. Re-install the same VMware Tools for Windows package originally installed or download the latest VMware Tools from here.

  Once the VMware SVGA display driver included in the VMware Tools package is installed you will have to reboot the virtual machine. The next time the virtual machine boots, the operating system will sense the previously detected vendor ID and not prompt for a new driver.