WSJT-X v2.0.0 by K1JT released - not compatible to earlier versions!

Sorry, wrong answer.

 

Which is why Microshaft now force upgrades their OS. Too much "hodgepodge." Hopefully the author could put a nag screen in it to remind to upgrade.

 

when they get some issues worked out and bugs fixed i will download and install 2.0 until then i will wait, if necessary i just won't operate ft8 until then.

 

I have downloaded the new Version 2.0.0 program , the problem is that I can not go with my computer the button that I have with a red pencil on the radio Kenwood ts-940s

 

That is 2.0 RC3. You will need to go to the WSJT-X web site and download the newest release from Dec. 10th.

 

The update was easy and all but my color scheme remained the same.

 

Does anyone know how to get it to recognize the ADF file I export from N3FJP Amateur Contact log correctly?

I get an error of "Error Scanning ADIF Log" " Invalid ADIF record starting at:"

 

This was a poorly thought out decision on the part of the WSJT-X team.

People who make the early switch get penalized as most of the FT8 traffic won't decode. This slows the migration to the new version. Many users won't upgrade until there is sufficient traffic with the new protocol to justify the change. In the meantime, everyone loses out on potential QSOs due to the different versions of the software.

A smarter approach would be to have the new version decode both the new and the old protocols. That removes the penalty for early adopters, and hastens the switch. Once the strong majority of users are using the new software, the team can remove the old protocol from the engine and force the last holdouts to upgrade.

Just my two cents.

 

I was just about to climb on to the WSJT bandwagon. I'm sort of glad I didn't drink the Kool Aid. I'll just get back to trying PSK and perhaps look into WSJT or whatever takes it's place next month. My thoughts are to walk before I run...then maybe I'll try flying or whatever the next hot digital mode offers.

 

You simply won't copy them if they are in the incompatible 'other' mode. The data 'package' is different.

 

My workaround for the lack of backwards compatibility was to install 2.0 into a different directory thus enabling me to run whichever version I want. I'll run 2.0 for a while then switch to 1.9. Cumbersome? A little but I get the best of both worlds until 1.9 fades away.

 

Can't do. You can't make an orange an apple. They really should have presented it as a totally different mode rather than an upgrade. That little aspect is apparently confusing a lot of people.
That said...my results tonight running with 2.0 are considerably better than even last night. I think the scale has tilted enough for me to use 2.0 as my default.

 

The graphic waterfall will show all signals. Its the decode list that will seem sparse.