KLAUS -
The error message definitely sounds like a driver compatibility issue involving the COM server function within OmniRig. Since WSJT-X is required, and is written to run under Windows 10 OS, you have to resolve the conflict on the OmniRig side. 
1)  Is your version of OmniRig the most recent, and tested to be fully compatible with Windows 10? 
2)  You stated that "The in-place-upgrade went flawlessly. After the first start all hardware was recognized by Windows. Current drivers were installed and all installed programs were running fine and fast.".
How do you know that all the drivers you loaded after the MB change are both current and correct?  You cannot trust Microsoft's file selection for this point.  In particular, if you are using a USB to RS232 serial adaptor cable, you MUST lioad the exact driver file provided by that device's supplier.  MS too often installs a newer version that is not exactly matched to your hardware, and counterfeit chips are being used by some suppliers to build cheaper imitation cables.
3)  You did not mention what radio you are using that is apparently not suported by WSJT-X'S built-in direct CAT functions.  If your radio IS listed as having CAT support by WSJT-X, try using their CAT, even if it is not otherwise compatible in some ways with the MicroHam interface that you use for other operating modes in your station.
4)  I do understand that you want to stay with Windows 8.1 OS in order to avoid the Windows 10 OS updates periodically offered by Microsoft. This decision has significant long term negative impact, since nobody is still writing software for Windows OS8 or 8.1 and relying on forward compatibility is a high risk to your investment in the new motherboard.  It is probably wiser for you to install Win 10 and simply disable the automatic OS update process.  Then your station and computer will simply be frozen in time. 
--
Karl  WA8NVW  OH
WA8NVW@...
in WSJTX@groups.io

A local Amateur Radio friend of mine just installed RC4 on his Mac.

Yesterday I was walking him thru settings.
Whe3n I got to the decodes window, Tom told me that all he has for Decode choices is Fast/Normal/Deep.
Tom says there is noting below "Deep" .
I have only windows 10-Pro so I can't make a comment about it being there or not being there.

IS Enable-AP on the mac version of 2.4.0-rc4 ??

thanks

--
--
Bob KD7YZ in NE Kentucky

On 01/05/2021 12:18, Klaus wrote:

Hi all,
maybe someone here has encountered a similar problem and can point me towards a solution.

I had WSJT-X 2.3 64 Bit together with some other HAM software (HRD, HDSDR etc.) running perfectly on my PC.

For CAT control I'm using OmniRig together with the MicroHAM USB Interface III.
Everything was ok. The PC was/is running Windows 8.1 because on that machine I don't want the permanent forced updates of Windows 10.
CPU was an Intel Q9550 Core 2 with 4 GBytes of memory - the maximum limit of the motherboard.

But the PC sometimes was a little slow and since I want to do some HAM related software development on the machine too, I decided to do a hardware upgrade to get some more horse powers under the hood.

Last week I changed to a Gigabyte  GA-Z77-DS3H motherboard with an Intel Core i7 3770k quad core processor and 16 GBytes of RAM.
The in-place-upgrade went flawlessly. After the first start all hardware was recognized by Windows. Current drivers were installed and all installed programs were running fine and fast.

All, EXCEPT WSJT-X 2.3 64 Bit running together with OmniRig for CAT control.
Whatever I do, when starting WSJT-X it comes up with the CAT error dialog and if I click on details, it says:

"Failed to start OmniRig COM server"

WSJT-X itself is running fine and decoding. But useless without CAT.

No matter what I try, it won't work. I upgraded WSJT-X to the current version 2.3.1, uninstalled OmniRig and reinstalled.
No way.

What I find really strange: WSJT-X is the ONLY program refusing to work with OmniRig. All other programs don't have a problem. CAT configuration itself hasn't changed. The (virtual) COM ports are the same as before the upgrade.

So what's the difference "in the eyes" of WSJT-X? More memory (16 instead 4 GBytes), higher processor speed, 8 logical processor cores instead 4.

Nothing uncommon and probably found on millions of other PCs running.

Anybody here has got an idea?

TIA

Klaus / DF6NP

Hi Klaus,

which version of Omin-Rig are you using?

What happens if you click "Retry" when the error pops up in WSJT-X?

73
Bill
G4WJS.

Using some courtesy an operator could just switch their mode to FT4 and call CQ in the same segment as FT8 on 160M or 60M. KD0XD Rick

On Sun, May 2, 2021 at 3:15 AM Klaus <k.schroedl@...
<mailto:k.schroedl@...>> wrote:

Whatever I do, when starting WSJT-X it comes up with the CAT error dialog and if I click on details, it says:
"Failed to start OmniRig COM server"
WSJT-X itself is running fine and decoding. But useless without CAT.

Sounds like Onmi-Rig did not migrate correctly. Download a new copy
from <http://dxatlas.com/omnirig/> and reinstall it. Make sure it
is also configured to run at user level and not administrator.

73,

... Joe, W4TV

Dave,
thank you for answering.

Sorry, I forgot: The Rig is a TS-950SDX connected to the PC via a virtual COM port 5 using a MicroHam USB Interface III.
In parallel to WSJT-X I am using HDSDR for an IF based waterfall diagram and monitoring. The SDR used for this is a SDRPlay RSP2 which is connected to the 8,83 MHz IF out of the TS-950SDX.

HDSDR also supports OmniRig which allows multiple software programs accessing a Rig. The connection from HDR (which unfortunately doesn't support OmniRig)  to the Kenwood is done via HDSDR which offers  a virtual COM port configured to COM 10 (together with a virtual COM cable configured as a connector between COM10 and COM11), so that HDR can connect to the TS950 via COM11 -> Virtual cable COM 10 -> HDSDR -> OmniRig -> TS-950SDX.

This may sound a little weird or complicated. But before the hardware upgrade it worked flawlessly and I don't see another way to get the desired configuration running.

On the other hand I don't see a reason why this well tried and proven setup shouldn't work just because of changed  and even better hardware.
And the show stopping issue definitely is WSJT-X with itÄs error message coming up.

vy 73
Klaus / DF6NP

Hello
It looks like there is no recent updated to this topic.

I see the error mesage "Status File error" frequently using WSJTx V2.4.0-rc4 (and before rc3) .
This happens more often since I use two instances of WSJTx. - alos after some hours of passive monitoring.
(sleep mode and all Windows powersavings are OFF)

Every time i observe this error message I have to stop wsjt and restart.that instance of WSJTx
I am using a fast multicore CPU, Win64, Omnirig and JT-alert, seldom more than 15% CPU use

Regards
Charly, DF5VAE

PS: the problem with storing a single q65 frequenvy in WSJTx - which apperare as valid for all modes after a reboot- seems to have been solved.

I know here the topic has been discussed before - but without a real solution.
One issue that has been identified, was one of the programs running with elevated rights or in administrator mode.

This isn't the case here. WSJT-X and OmniRig both are running in standard user mode.

73s
Klaus

On 4/28/2021 7:59 AM, Dick- K9OM via groups.io wrote:

A substantial amount of Contesting takes place on 160m. during the winter months so FT4 should be allowed to join the mix.  FT4 occupies a lot less frequency than SSB.

I have several thoughts on this. First, the administrators of those contests establish the rules. Second, there is strong "moldy fig" resistance from OT 160M ops to ANY digital modes. Third, if ANY digital mode is to be promoted on 160M it should be FST4, which offers significant advantages in fighting the encroaching noise that has made 160M more and more difficult for weak signal work.

From my QTH in the mountains S of San Francisco, I've HEARD six CW signals from EU in five years, and two of them could hear me. I've made many QSOs using FT8, and added 20 EU countries in three seasons. And I've got a pretty good antenna farm!

73, Jim K9YC

All,

I am evaluating several antennas. Could someone identify the headings for the columns in the log.txt file so that I can get them into a table.

Thanks!!
KN4FLF
Hank Perkins

Would it be possible in a future release or update to allow an increase in the size of the font and the UP/DWN buttons for the TX & RX AF frequency fields?  As I am getting older, the very small numbers and very small buttons make these fields difficult to read and adjust.   It would appear that there is sufficient 'real estate' on that section of the main screen to allow them to be bigger.

I've looked in the Settings but I can't find a way to adjust these fields' size.

I think a lot of WSJT-X users would benefit from these fields and buttons being larger.

73 de Mike, K6MKF

Hi all,
maybe someone here has encountered a similar problem and can point me towards a solution.

I had WSJT-X 2.3 64 Bit together with some other HAM software (HRD, HDSDR etc.) running perfectly on my PC.

For CAT control I'm using OmniRig together with the MicroHAM USB Interface III.
Everything was ok. The PC was/is running Windows 8.1 because on that machine I don't want the permanent forced updates of Windows 10.
CPU was an Intel Q9550 Core 2 with 4 GBytes of memory - the maximum limit of the motherboard.

But the PC sometimes was a little slow and since I want to do some HAM related software development on the machine too, I decided to do a hardware upgrade to get some more horse powers under the hood.

Last week I changed to a Gigabyte  GA-Z77-DS3H motherboard with an Intel Core i7 3770k quad core processor and 16 GBytes of RAM.
The in-place-upgrade went flawlessly. After the first start all hardware was recognized by Windows. Current drivers were installed and all installed programs were running fine and fast.

All, EXCEPT WSJT-X 2.3 64 Bit running together with OmniRig for CAT control.
Whatever I do, when starting WSJT-X it comes up with the CAT error dialog and if I click on details, it says:

"Failed to start OmniRig COM server"

WSJT-X itself is running fine and decoding. But useless without CAT.

No matter what I try, it won't work. I upgraded WSJT-X to the current version 2.3.1, uninstalled OmniRig and reinstalled.
No way.

What I find really strange: WSJT-X is the ONLY program refusing to work with OmniRig. All other programs don't have a problem. CAT configuration itself hasn't changed. The (virtual) COM ports are the same as before the upgrade.

So what's the difference "in the eyes" of WSJT-X? More memory (16 instead 4 GBytes), higher processor speed, 8 logical processor cores instead 4.

Nothing uncommon and probably found on millions of other PCs running.

Anybody here has got an idea?

TIA

Klaus / DF6NP

Yes, I did not read the instruction on 2.3.1 which I did not know had been released.

73 de JH3SIF, Keith

Here in the midwest, we have been using 144.170 for Q65. Good luck with your activity night.

73 Jay KA9CFD

On May 1, 2021, at 07:19, Pete Ritter via groups.io <cpritter@...> wrote:

So if my QSOs partner's TX cycle is not decoded before my TX cycle begins, I'll just repeat my previous message.

Pete, I’ve seen mine change my outgoing message AFTER it has started to transmit, based on a late incoming decode. I was quite surprised by this, and very pleased.

Gary - AG0N