If your program wants to distinguish IVI-COM and IVI-C drivers you are using, you can access the IVI Config Store contents through the IviConfigServer DLL. Here is a VC++ example that identifies the IVI driver type (COM or C) from a given Logical Name - "MyInstr" in this case.
// Add this line in the stdafx.h
#import "C:\Program Files\IVI\Bin\IviConfigServer.dll" no_namespace named_guids
...
IIviConfigStorePtr spCs;
hr = ::CoCreateInstance(
CLSID_IviConfigStore,
NULL,
CLSCTX_ALL,
IID_IIviConfigStore,
(void**)&spCs);
try {
// Load the master config XML
spCs->Deserialize( spCs->MasterLocation);
// Get interface for the logical name "MyInstr"
IIviLogicalNamePtr spLn = spCs->LogicalNames->Item[L"MyInstr"];
// Get interface for the driver session
IIviDriverSessionPtr spDs = spLn->Session;
// Get interface for the software module
IIviSoftwareModulePtr spSm = spDs->SoftwareModule;
// Acquire the prefix, module-path, progID strings
_bstr_t strPrefix = spSm->Prefix;
_bstr_t strModulePath = spSm->ModulePath;
_bstr_t strProgID = spSm->ProgID;
}
catch( _com_error e) {
}
When IVI-C, you can get a valid ModulePath string such as "<prefix>_32.DLL" and an empty ProgID. When IVI-COM, you can get a valid ProgID string such as "Agilent.<componentidentifier>" and an empty ModulePath. Through the IIviSoftwareModule interface, you can acquire more useful information about the software module associated with the given Logical Name.
このメッセージは 10-07-2005 10:28 AMに Makoto が編集しています。
このメッセージは 10-07-2005 10:28 AMに Makoto が編集しています。
