2.5.2 was announced on the beta list...supposedly fixes this problem.
2.5.2 is available for download
http://hamapps.com/dnl/JTAlert/HamApps_JTAlert_2.5.2_Setup.exe
>From the release notes...
Changes:
- JTAlert in JT65HF mode will now wait for JT65-HF (and Comfort by
DL3VCO)
to be running before continuing its startup.
- "Test Sound Card" menu will warn that Sounds are OFF and not play the
test.
Fixes:
- WSJT-X decoded.txt file check method changed to prevent WSJT-X Fortran
error message during very busy band decodes.
- WSJTX.dat and JT65HF.dat configuration files moved from Common AppData
directory to users Local AppData directory to avoid permission
issues.
-----Original Message-----
From: Paul DU2/WA8UGN [mailto:keat...@msn.com]
Sent: Saturday, November 15, 2014 11:03 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] WSJT-X v1.4.0-rc2 Error Report
I use JTAlertX with WSTJ-X. Believe there may be an interaction issue
between WSJT-X and the latest version of JTAlertX or with its associated
application JTMacrosX.
Installed JTAlertX update 11/15/2014; now using JTAlertX 2.5.1.
Settings involving WSJT-X interface with JTAlertX include:
* Auto-Start/Close of wsjtx.exe;
* Auto-Start/Close of JTMacrosX 2.5.1;
* Auto-clear JTAlert callsigns when WSTJ-X decodes cleared; and
* Waterfall follow WSJT-X minimize and restore.
WSJT-X has, on occasion, displays an error pop-up window during Decode,
citing:
"Fortran runtime error. Cannot write to file opened for READ"
Waterfall display is unaffected; Decode button stays illuminated (blue) and
all activity in both Band Activity and Rx Frequency windows is halted. No
other symptoms are apparent. Closing and re-starting programs clears error
and returns operation back to normal.
I have not experienced this error situation using prior versions of
JTAlertX. I am running additional on-air tests, using different
permutations of the JTAlertX settings, the use of JTMacros, and the use of
JTAlertX itself. Initial testing with JTAlertX closed (off) results in
continuous, error-free operation; pointing towards an interaction issue.
WSTJ-X settings employed are:
* Mode: JT9+JT65
* Decode: Deepest
* Tx: TxJT65 #; Tx odd; Lock Tx=Rx
I have attempted registration in and am awaiting entrance to the "HamApps by
VK33AMA" Yahoo Group to make similar report. There appears to be
conversation about similar and other issues experienced by others who
upgraded to JTAlertX 2.5.1. Cannot, as of yet, post my error report to that
group.
Best 73,
Paul DU2/WA8UGN
----------------------------------------------------------------------------
--
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
------------------------------------------------------------------------------
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
