I’m going to ask the unasked question: Why are we doing this at all? LOTW and EQSL status are provided by JTAlertX, and a simple, easy to use update mechanism is available for that. It seems to me that having LOTW status in WSJT-X is an unnecessary duplication of features, and one that is now causing problems for the developers and users. None of the options listed below are likely to work well for the average WSJT-X user. Ordinary users messing about with DLLs is just asking for trouble.
Or, Simply provide instructions on how to download and install a LOTW CSV file if the user wants to use the feature. If the user doesn’t want the feature, then simply don’t do it. It is very simple to download the file using a browser. The user downloads the file, then runs WSJT-X and points a dialog box to the file. The program copies the file to the place it wants it and we’re done. Note that JTAlertX has this working, and note that the program does not do the updating. JTAlertX users get a notification that the LOTW user list is out of date and are pointed to small installer, provided by the developer, that has the updated file inside it. Also note that DXLABS does essentially the same thing. When their copy of the LOTW database is out of date, they provide an updated version as part of their already well-oiled update mechanism. In all of these cases, the program itself does not do the updating. There is probably a reason for that. Dave / NX6D ________________________________ From: Bill Somerville <g4...@classdesign.com> Sent: Wednesday, October 17, 2018 12:25:30 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT-X v2.0.0 RC3 LotW Users Data File errors On 17/10/2018 18:23, Bill Somerville wrote: Open a Command prompt window (*not* Administrator mode), type the following command at the prompt: where libeay32.dll and report back the results printed. Thanks all for the reports. As expected the problem is that some users have no OpenSSL libraries installed and others have a variety of versions supplied with various other packages. There is no perfect solution to this, for example: 1) It would be great to package the right OpenSSL libraries with WSJT-X but US state and local legislation about strong cryptography software prevents us from doing that easily. 2) We could recommend that users install the OpenSSL libraries separately and copy them into the WSJT-X bin directory but this will cause problems for the WSJT-X uninstaller when later upgrading. 3) We could recommend that users install the OpenSSL libraries separately and add their location to the PATH environment variable but other applications are likely to undo that by doing the same with the version of OpenSSL they need. 4) We could recommend that users install the OpenSSL libraries separately and let the installer copy them to the system directory, this is not usually recommended as it may break other applications. So I am going to go with the least bad of the above options which I think is (4). Instructions below. By the way, the reason OpenSSL is required is that the ARRL web server will not respond to insecure requests (http) and only serves secure URLs (https). If an http request is made then it redirects to an https equivalent. Those experiencing LotW download errors can try the following: Download the OpenSSL installer for Windows from here: https://slproweb.com/products/Win32OpenSSL.html<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fslproweb.com%2Fproducts%2FWin32OpenSSL.html&data=02%7C01%7C%7C2f57ee2a2dd1467559d408d6346706d9%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636754014437293050&sdata=LWk6MvIJxhjXp2WH3%2FQ9%2FQzEbacG4vHmAIBNOZIQ2tw%3D&reserved=0> , specifically the "Win32 OpenSSL v1.0.2p Light" version. Note that this is the right version even if you are running 64-bit Windows. Download link is https://slproweb.com/download/Win32OpenSSL_Light-1_0_2p.exe<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fslproweb.com%2Fdownload%2FWin32OpenSSL_Light-1_0_2p.exe&data=02%7C01%7C%7C2f57ee2a2dd1467559d408d6346706d9%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636754014437293050&sdata=g93jko4ceudGhBeY169gwJeusxWnjRSQU3pEFRbWgTU%3D&reserved=0> . Run the downloaded installer taking default options and accept the option to install the libraries into the Windows system directory. Please report back on if this solves the issues? You will probably need to restart WSJT-X. For those that have tried copying random OpenSSL DLLs into their WSJT-X bin directory, you will need to remove them as well. 73 Bill G4WJS.
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
