Scribd
Upload
3 views1 page

Vixwrapper Config

The document provides a mapping of product version specifications to their corresponding Vix implementations, detailing the format for each entry. It includes examples for different versions of Workstation and Player, specifying provider type, API version, IPC type, product version, and implementation directory. The configuration allows for multiple locations, with the latest entry being prioritized for use.

Uploaded by

keikolyke
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
3 views1 page

Vixwrapper Config

The document provides a mapping of product version specifications to their corresponding Vix implementations, detailing the format for each entry. It includes examples for different versions of Workstation and Player, specifying provider type, API version, IPC type, product version, and implementation directory. The configuration allows for multiple locations, with the latest entry being prioritized for use.

Uploaded by

keikolyke
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

#@Version-Info

#
# VixAllProducts revision mapping
#
# This file translates product version specifications into the appropriate Vix
# implementations.
#
# Each @Version-Info line has 5 white-space seperated entries:
#
# provider-type: ws, esx, viserver, etc
# apiVersion: the apiVersion supported, as passed in from VixHost_Connect()
# ipc-type: none, vmdb, vmodl, cim
# product-version: the product version string
#
# implementation-directory: the path to the library that implements the
# version described by the first 4 parameters
#
#
# The configuration is based on the first 4 fields, which describe
# the product. The 5th field is the location. To force it to try
# multiple location, the same configuration can be repeated. Note that
# list is built in LIFO order, so the latest entry in the configuration
# will be the first used. If for some reason that value fails, it will
# continue through any other matches.

# Workstation 17.0.0
ws 19 vmdb 17.0.0 Workstation-17.0.0
player 19 vmdb 17.0.0 Workstation-17.0.0

# Workstation 17.6.0
ws 19 vmdb 17.6.0 Workstation-17.0.0
player 19 vmdb 17.6.0 Workstation-17.0.0

# latest un-versioned
ws 19 vmdb e.x.p Workstation-17.0.0
player 19 vmdb e.x.p Workstation-17.0.0

# EOF

You might also like