Hi Bill and Joe et al, I posted a much longer version of what is below to moon-net in the wee hours [I posted there because I posted by "replying" to another user report on this software version] but probably should have posted it here so you coding experts could see it. So here it is:
On Windows 10 system (64 bit) using Linrad fed by WSE to provide NETWORK input to MAP65: MAP65 v2.7 r7541 installs without error. Starts with error on the report window saying: QIODevice::read: device not open The other windows [wide graph, band map, messages, main user interface, astronomical data] all appear OK, but I did not have an array at home to point at the Moon (nor any files at home to feed to it in lieu of an off-the-air signal) so there were no decodes of course. Restarting MAP65 gives this same result each time. The behavior is always as described above with the error given in the report window, but with the windows that together form the GUI appearing fine. After running for some time (10-15 minutes) the signal from Linrad disappeared on one occasion and at that time killing/restarting Linrad did not cause the signal to reappear on the map65 signal bars. I had to kill/restart map65 to get the signal back. Linrad appears to be fine when this happens. I then ran the system for 4.5 hours while I slept and MAP65 still seems to be fine with no further errors. As far as the QIODevice error (which I am guessing is a streaming or file read/write error): I have set PTT port in MAP65 to none so there is no chance for a device error there. I am confident it is not a NETWORK error as that would give a message box "UDP" error in my experience with MAP65. I am running an NVIDIA GeForce GTX 960 display adapter. Finally, I noted that: I've used my machine for a lot of development on non map65 projects so it is possible that if there is a critical file missing that is causing some folks to have trouble getting map65 to run at all, that my machine doesn't have that problem because that critical file is already on my machine due to my other activities. I have one other report of a MAP65 error ultimately caused by my 3am-induced-stupor but which you may still want to know about in order to improve error trapping: If one uses the wrong band in Linrad such as using a 40 Meter frequency like 7.025, then MAP65 will eventually give a Fortran error message such as: "Fortran runtime error: Index '-2809519' of dimension 1 of array 'ca' outside of expected range(1:5376000)". And at the moment that the Fortran error message box appears, the MAP65 reporting window has a new message displayed beneath the QIODevice error that says: QDialog::exec:Recursive call detected. The exact number given as the index value in the Fortran error message seems to depend on exactly what frequency I am using in Linrad. I've seen as low as "-2304" for a value, and not all values are negative. It takes a variable interval for this appear (I'd estimate the interval ranges from 1-10 minutes but that is a guess). On one occasion when this error appeared MAP65 locked up and my other windows froze too. I was able to escape by getting to Task Manager with Ctl-Alt-Del and the killing MAP65. I restarted it and all was well. When this error occurs the Decode button turns Light BLue as it does when decoding and it never shuts off, even if the frequency is changed to the correct 2M band range, even if one clicks "Stop" or starts transmitting, which works fine even under these error conditions. I have not yet had the Decode button stick in the "On" state when Linrad is in the right frequency band. This error is caused by user stupidity, but you might want to trap it, especially since it can cause the program to lock up. There is another consequence of this error caused by being on the wrong band in Linrad. The first few times I started MAP65 using the wrong band on Linrad, the MAP65 Band Map window was frozen and much narrower than normal; there was just room for the Globe, the "-" and the "X" at the top. It could not be resized and it could not be moved about the desktop. But I could still minimize it by clicking on the "-". But after I figured out that Linrad wasn't in the 2M band and put the Linrad frequency on 144.125, the Band Map worked fine and after that even if I entered a 40M frequency the band map size and mobility and resizability all remained normal (but the Fortran error would still eventually occur if Linrad were in the 40M band). Thanks Joe for doing this and thanks to everyone on the development team for helping! Hope that the above helps. I will post further problem reports if any other problems occur to this list. 73, Roger W3SZ On 1/20/2017 7:44 AM, Bill Somerville wrote: > On 20/01/2017 12:19, Bill Somerville wrote: >> I don't have a machine without a Qt development package installed so it >> will work for me. I will download and have a look. > Hi Joe, > > a couple of minor issues. > > 1) The control panel programs and features table shows it as v2.5 rather > than v2.7, > > 2) It doesn't un-install cleanly as files get created in the > installation directory (fftwf_wisdom.dat and maybe others), this would > also preclude installing in "Program Files" or "Program Files (x86)". > > 73 > Bill > G4WJS. > > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
