I apologize for not making it clear that my reports from "last night" were using the MAP65 Windows Installer version. I did not know that the new version was also on the svn.
Posts to this list today make it clear that the new version is also available as source code, so I have installed and will do all further tests with the versions from the svn unless you folks direct me otherwise. I have now installed 2.7 r7546 from source using JTSDK and it installs and runs without errors so far. With this version I also get the Fortran error when I have Linrad set to 40 M band instead of 2M, where it belongs. The error is as I reported before. Verbatim the error I just created now by putting Linrad on 40M is: "Fortran runtime error: Index '-2809519' of dimension 1 of array 'ca' outside of expected range (1:5376000)" With Linrad set to 7.025 this is identical to the error message I reported before with Linrad also set to 7.025 at that time. The error still causes MAP6's Decode button to be stuck in light blue decoding mode. I understand that this is not "usual" use of MAP65. I report it for the reasons detailed in my previous post. Double-left-clicking on a signal on the zoomed lower portion of the Wide Graph display will also cause MAP65 to be stuck in Decode mode. Again, this is not "usual" use of the program. Once MAP65 has receive a full sequence's worth of data and done its own first automatic decode, double-lef-clicking in the lower zoomed portion of the Wide Graph display does not cause problems. MAP65 attempts to decode and then the Decode button returns to gray background color state. This test is on another computer than the one I used for "last night's" testing; this one is at my station and so when the moon rises I will have a chance to see how it decodes. I will be able to run it vs multiple instances of WSJT-X to do a comparison of decoding at some point, but that won't get done this weekend given that the ARRL Jan VHF contest will be running and I will be busy with that. The OS is still 64 bit Windows 10. One last point. In his initial posting about the Windows installer version, Joe said that he preferred discussion occur on MoonNet. That makes sense for comments regarding decoding performance, GUI bugs/glitches/complaints, etc. But do you really want comments regarding install issues, coding/error trapping issues, etc. to occur on Moon Net rather than here? That seems less than optimal to me in at least 2 ways [1] many MoonNet users won't understand or give a hoot about these technical and more esoteric issues and [2] while Joe monitors MoonNet carefully, I am not sure that all of the other developers do so. I will follow your preference on this, just let me know what it is. The most logical choice to me is to triage the email to one list or the other depending upon its content. There is also the issue that there are still a few "digital haters" on the MoonNet list, so it would be prudent not to flood that list with MAP65 bug reports, I think. Thanks and keep up the great work as well as your spirits! 73, Roger W3SZ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
