On 12/11/2014 21:38, Joe Taylor wrote: > Hi John, Hi Joe & John, > > N6RCD wrote: >> I'm not using a shortcut to start WSPR. I double-click on wspr.bat in the >> build directory : >> >> c:\JTSDK-PY\wspr\wspr-r4522\wspr.bat > OK. You're using WSPR in a way that was not intended, or planned for, > but it should be possible to make it work. > > I copied the rigctl.exe (built with hamlib3) from > > C:\JTSDK-QT\hamlib3\mingw32\bin\rigctl.exe > > to > > C:\JTSDK-PY\wspr\wspr-r4522\rigctl.exe > > and then copied libwinpthread.dll from > > C:\JTSDK-QT\appsupport\runtime\libwinpthread.dll > > to > > C:\\JTSDK-PY\wspr\wspr-r4522\libwinpthread.dll John has a DLL version of hamlib 3 as he did a default build of their master branch, but that should work just the same so long as he also copies over libhamlib-2.dll (yes -2 is the correct number) from his hamlib 3 install folder. > > WSPR now runs OK including rig control via the hamlib3 version if > rigctl.exe. This is true both from the command prompt and by clicking > on C:\JTSDK-PY\wspr\wspr-r4522\wspr.bat in Windows explorer. I can't see any reason why that shouldn't work either. > > -- 73, Joe, K1JT 73 Bill G4WJS.
------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
