You can check whether the installation was successful by running the MDSEdit utility. There should be exactly one H Layer record; if there are no records, installation was unsuccessful or incomplete. If there are more than one, then somehow two different versions of the framework are installed, and very likely to cause conflicts.
Usage: mds_install [-u] -s file [-d path] -u Uninstall the module. -s file Source file to install; no extension if installing, file name only when uninstalling or refreshing -d path Destination path; required for install.
The source files must include a path to the DLL to install, if it is not in the current directory. The destination of MDS must be in the search path, typically the system directory (e.g. C:\Windows\System\ or C:\Winnt\System32\).
See the contents of the batch files for examples of how to use this in practice.
Usage: mod_install [-fiur] -s file [-d path] -f Unused option reserved for future use. -i Install the module. -u Uninstall the module. -r Refresh the installation information. ** Options -i, -u, and -r are mutually exclusive. ** -s file Source file to install; no extension if installing, file name only when uninstalling or refreshing -d path Destination path; required for install.
The source files must include a path to the DLL to install, if it is not in the current directory. The destination of the framework (bioapi100.dll) must be in the search path. The destination of a BSP may be anywhere; MDS remembers where, and the framework uses this to locate and load the BSP at runtime.
See the contents of the batch files for examples of how to use this in practice.
mod_install does its work partly by calling the installation function in your BSP. See the BSP section of Use.htm for more details on how to create a BSP.