Windows Network Operation Installation Instructions

VM Labs SDK Internal Release 0.86.2
June 14
, 2001


Note: These instructions have been tested on Windows 98 only. They ought to work on Windows NT 4.x and Windows 2000, but I haven't tried it yet.

  1. Map \\mammoth\NUON\ to a network drive on your machine (we'll use N:\ in these instructions).
  2. Edit your autoexec.bat to include the following lines:
    set VMLABS=N:\SDK
    s
    et PATH=%VMLABS%\bin;%VMLABS%\bin\windows;%PATH%
  3. If you have any lines in autoexec.bat referencing a previous SDK location, remove them, removed the SDK references, or REM them out at this time.
  4. Restart your system

You are now ready to use the VM Labs SDK.

Optional Procedure

The following actions are highly recommended, but are not required to use the SDK on Windows based systems.

Execute these steps to create a home for any local SDK components that you may update. This is a highly recommended practice that will help ensure SDK consistency among the engineering team.

  1. Create a C:\VMLabs-Local folder.
  2. Edit your autoexec.bat file to include the following lines:
    set VMLABS_LOCAL=C:\VMLabs-Local
    set PATH=%VMLABS_LOCAL%\bin;%VMLABS_LOCAL%\bin\windows;%PATH%

Starting with the 0.82 release, the VM Labs makefiles reference the VMLABS_LOCAL variable support installation of components into a local "shadow" SDK in order to prevent smashing of the installed SDK.

You may define a different directory name or drive for this folder. If you do, substitute the path to that drive/directory for C:\ or C:\VMLabs-Local in the preceding instructions.



Please email comments or questions to SDK-Release@vmlabs.com

This page © Copyright 2001 VM Labs, Inc. Mountain View, CA. All rights reserved.