i tried that and it doesnt even atart omni rig 01/02/2023 09:57:56 - OmniRig: Connecting to OmniRig... 01/02/2023 09:57:57 - Error: Starting OmniRig: Unable to cast COM object of type 'System.__ComObject' to interface type 'OmniRig.OmniRigX'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{501A2858-3331-467A-837A-989FDEDACC7D}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)). at VarAC.VarAC.StartOmniRig() 01/02/2023 09:57:57 - OmniRig: Unable to connect OmniRig. 01/02/2023 09:57:57 - OmniRig event: Rig: 1 Params:4 HexParams: 4 but even if i start omnirig manually it still doesnt see it. if i manually start omnirig it pops the omnirig window up which has the correct rig information in. but still refuses to connect with the following error: 01/02/2023 09:59:36 - OmniRig: Connecting to OmniRig... 01/02/2023 10:00:06 - Error: Starting OmniRig: Retrieving the COM class factory for component with CLSID {74E87CF5-F8CE-4C38-82AE-1673839DB15F} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)). at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at VarAC.VarAC.StartOmniRig() 01/02/2023 10:00:06 - OmniRig: Unable to connect OmniRig. 01/02/2023 10:00:06 - OmniRig event: Rig: 1 Params:4 HexParams: 4 as for "installation" you have no option when you install omnirig as to where it puts it (program files\afreet) - that's a personal pet peeve of mine as i would rather keep it on a different drive, but hey, shouldn't matter right. again... other programs work fine as i can subsequently connect another program to that running instance of omnirig without an issue. Charlie

tried that... omnirig is running as log4om is connected to it, i did notice that it does try and start another instance which may be where the issue is. there is no need to run another instance as it's already there

like i said.. it works perfectly fine for log4om, wsjtx, and other programs

version 1.2