Re: [wsjt-devel] WSPR SegFault on Decode

Hi Russ, I'm assuming you are comping from source here. How did you install the build and runtime package dependencies for WSPR? 73's Greg On 02/08/2016 08:55 AM, Russ Woodman wrote: > Hi, > > Just built WSPR 4.0r6470 from the SVN on my Linux machine running Debian > Jessie. I can start

Re: [wsjt-devel] running wsjtx on another computer

To generate the Win32 installer from JTSDK on Windows, In JTSDK-QT, type: build-wsjtx package That should generate an installer from the development branch ( ^/branches/wsjtx v1.7.0 ) using the Defaults from CMakeLists.txt 73's Greg, KI7MT On 02/08/2016 06:59 AM, Bill Somerville wrote: > On

[wsjt-devel] running wsjtx on another computer

Hello, First of all, I'm not a programmer. I downloaded JTSDK on a windows 10 x64, installed both omnirig and ruby etc.. And tried to compile the wsjtx 1.7 with (JTSDK-QT 5.2 ) C:\JTSDK)build-wsjtx rinstallparameter. It compiled the file fine.

[wsjt-devel] JTSDK-NIX 2.0.19

I've installed and run JTSDK-NIX 2.0.19 and successfully generated HAMLIB and WSJT-10 r6470 I've come across 2 (related) problems: If I try a station look-up, I get "Error when searching CALL3.TXT, or no such file present" in the terminal and

Re: [wsjt-devel] running wsjtx on another computer

On 08/02/2016 11:40, Oguzhan Kayhan wrote: > I copied the bin directory to the computer that i use for my ham > activities.. > And i got the following error msg. > > This application failed to start because it could not find or load the > Qt platform plugin "windows" > > > So, i don't wanna

Re: [wsjt-devel] JTSDK-NIX 2.0.19

Hi Peter, Sticking with the original problem reported and using the latest sources from SVN (6470), I cannot reproduce either of the errors on Ubuntu or Mint. I've tried using both the Lookup and Add functions, and I've removed both the source and install directories before rebuilding, neither

Re: [wsjt-devel] JTSDK-NIX 2.0.19

Peter try setting "autorun" in the options menu I just built and ran wsjt10 with the autorun check from the jtsdk menu and it built and ran no problems with call.txt also changed the call sign and forced a look up... no problem Running mint 17.3 64 bit On Mon, 8 Feb 2016 17:45:51 +0100 Peter

Re: [wsjt-devel] WSPR SegFault on Decode

Greg, I installed them as needed out of the Debian repos. I didn't use the JDK because I didn't know about it until after I did the build. It looks like it only provides hamlib3 support? Are there some versions I should compare between my system libraries and the JDK? 73, Russ - K5TUX

Re: [wsjt-devel] WSPR SegFault on Decode

Hi Russ, There is no pressing need to use JTSDK to build WSJT, WSPR or WSJT-X on Linux. All of the apps can be built natively provided the build and runtime dependencies have been met. WSJT-X has a special requirement of passing a locally built version of Hamlib3, but that is easy enough to deal

Re: [wsjt-devel] JTSDK-NIX 2.0.19

Hi Peter, > Has the CALL3.TXT file changed content format at some point (if so, I > must have missed the announcement)? There's been no formal release of WSJT since v10.0 r6088, thus no announcement. Your working from the Development Branch ( work in progress ). > It seems that when I let the

Re: [wsjt-devel] JTSDK-NIX 2.0.19

Den 08-02-2016 kl. 18:20 skrev KI7MT: > Hi Peter, > > Sticking with the original problem reported and using the latest sources > from SVN (6470), I cannot reproduce either of the errors on Ubuntu or Mint. > > I've tried using both the Lookup and Add functions, and I've removed > both the source

Re: [wsjt-devel] running wsjtx on another computer

seems like i needed to copy whole install folder (including the plugins folder) to have qtwindows plugin. otherwise qt.conf cant find the necessary pluing now i works. On Mon, Feb 8, 2016 at 6:20 PM, KI7MT wrote: > To generate the Win32 installer from JTSDK on Windows, >

Re: [wsjt-devel] WSPR SegFault on Decode

Hi Russ, Thanks for the feedback. Glad things are working as expected. 73's Greg, KI7MT On 02/08/2016 03:10 PM, Russ Woodman wrote: > Greg, > > I read through the special information you provided below. I removed the > python3-pil and python3-pil.imagetk packages from my system and built

Re: [wsjt-devel] WSPR SegFault on Decode

Greg, I read through the special information you provided below. I removed the python3-pil and python3-pil.imagetk packages from my system and built them using the procedure outlined in the docs. Apparently that was the trouble as WSPR is now fully functional and my spots are showing up on

Re: [wsjt-devel] Watchdog not working

On 08/02/2016 23:18, Michael Black wrote: > It appears that the watchdog is not working when in rig split mode. > > When entering the qsy() function the split frequency is in m_dialFreq > and f > contains the non-split frequency so it always is false and always resets > the watchdog counter. > >

[wsjt-devel] Watchdog not working

It appears that the watchdog is not working when in rig split mode. When entering the qsy() function the split frequency is in m_dialFreq and f contains the non-split frequency so it always is false and always resets the watchdog counter. Do we need another variable to remember this? RRR Mike