Date   

locked Re: file write error v1.4.0 rc2

Michael Black
 

What operating system?

And is that the exact error message you got?  I don't see that string "file write error" anywhere inside JTAlert or WSJT-X

Can you do a screen grab if you see it again?

And that's a pretty lousy error message if that's what you're seeing.  I used to knock my students down a grade for doing such a thing….the old "can't find DLL" windows error being a prime example.  Tell me the file and real error is mandatory and isn't hard to do at all.

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Saturday, November 15, 2014 8:43 AM
To: wsjtgroup@...
Cc: HamApps@...
Subject: [HamApps] file write error v1.4.0 rc2

 

 

Joe

Running 1.4.0 rc2 and have received this error a couple of times today.

I had closed and reopened WSJT-X in between occurrences.

 

JTAlertX 2.4.1 also running but no other applications. Wondering if this program opens for read only and doesn’t close it in time for the next cycle.

 

 

 

Any thoughts?

 

73

Charlie

www.G4EST.me.uk

 

 


locked file write error v1.4.0 rc2

chas cartmel
 

Joe

Running 1.4.0 rc2 and have received this error a couple of times today.

I had closed and reopened WSJT-X in between occurrences.

 

JTAlertX 2.4.1 also running but no other applications. Wondering if this program opens for read only and doesn’t close it in time for the next cycle.

 

 

 

Any thoughts?

 

73

Charlie

www.G4EST.me.uk

 

 


locked Re: New - JTAlert 2.5.0 available

KB3TC <kb3tc1@...>
 

Laurie,
You now are confusing me.
Previously, as most people do, you were responding to questions ABOVE the email but now you are responding BELOW the email.
For those of us who have been following this and other forums, it became quite confusing when you reply below the question. In smaller screens you have to scroll down to see YOUR answer whereas before your answer was the first line.
Can you please go back to the way you were doing previously?
Tim, KB3TC

On 11/14/2014 5:20 AM, 'Laurie, VK3AMA' groups06@... [HamApps] wrote:
�

On 14/11/2014 9:10 PM, 'chas cartmel' chas@... [HamApps] wrote:

Laurie

Thanks for the latest version and for the work you put in to benefit us all.

�

Just a minor point which may confuse others as it did me for a while. I have my WSJT-X window hard against the right hand edge of the window and after running JT-Alert wondered where the Macro�s where. I� tried opening them manually and was told it was a second instance. I then noticed a �shadow� against the RH edge of the wsjt window and lo-and-behold the macros were there. I opened the macros config and moved them to the LH edge and all was back to normal.

�

Knowing this may help others who have lost them...

�

73

Charlie

www.G4EST.me.uk

Charlie,

I don't know why JTMacrosX should have docked to the right hand side when it had previously been docked to the left. It may be a misconfigured setting after the 2.5.0 upgrade (there were many changes).

If you see JTMacrosX incorrectly docking to the right again, please post a message.

de Laurie VK3AMA
���


locked Re: 2.5.0 bug

Ed Wilson
 

Laurie,

I might have an explanation for needing to restart the PC after installing v. 2.5.0, although I do not fully understand what is happening.

I was running the 2.4 version when I decided to update to v. 2.5.0 I closed v. 2.4 with the X at the top right of the window. I then installed the new version by double-clicking on the icon from the download. I did not seem to have any problems with the installation, but when I started the new version, it would not respond to any mouse clicks. The top part of the JTAlert window was off the top of the screen (I cannot remember how I finally managed to drag it down; the settings lock it to WSJT-X). I then restarted and tried to run it again and it appeared to be working normally.

Sometime after that I invoked the Windows 7 Task Manager for a different reason. I closed down JTAlert and noted that the "Process" JTAlert.exe continued to run. My theory is that somehow the new JTAlert 2.5.0 tried to run with the old process, thus causing the observed behaviour (Aussie spelling?). The shut down killed the old process and apparently the subsequent start-up allowed the new process to run.

I have noticed something else with the 2.5.0 version. If I close it down with the X in the upper right corner of the window, the JTAlert process continues to run and if I then start JTAlert from the shortcut icon, it asks me if I want to start a second instance of JTAlert. I guess that this is really not a bug, but I have not seen this before. I always operate with a single instance of WSJT-X and JTAlert-X.

I will install 2.5.1 soon and report any problems that I might encounter.

Thanks for the software...as always!
 
Ed, K0KC


From: Ed Wilson
To: "HamApps@..." Sent: Friday, November 14, 2014 3:38 PM
Subject: Re: [HamApps] 2.5.0 bug

Laurie,

I am using Avast and JTAlert seemed to install fine today, although I had to add the .exe file to the Avast exclusions list the last time a new version of JTAlert came out and it should still be there.
 
Ed, K0KC




From: "'Laurie, VK3AMA' groups06@... [HamApps]"
To: HamApps@...
Sent: Friday, November 14, 2014 3:16 PM
Subject: Re: [HamApps] 2.5.0 bug

 
On 15/11/2014 7:05 AM, Ed Wilson ed.wilson@... [HamApps] wrote:

I had a similar problem when I first installed this new version. I restarted the computer and all is well (so far).
 
Ed, K0KC
Tnx Ed,

I don't have an explanation on why a PC restart would be needed. There is nothing in the JTAlert code that would require that.
What Virus/Malware software are you running?

de Laurie VK3AMA
   





locked Re: : Callsigns Not Populating

afa1yy
 

I installed V.2.5.1. Boxes get populated FB.  I noticed the band activity box was not active so I went into settings
everything from wanted callsigns down through manage settings was greyed out. This includes contact support.

Art  K0AY


locked Halt after TX Button

Scott
 

I cannot find where I can move that button to the left hand side of the JT-Alert window. I know there was a way to move it in the prior version I had.


Thanks - Scott

KN3A


locked Re: version 2.5.0 delay in populating boxes

chas cartmel
 

Laurie

Just installed 2.5.1 so will monitor that. Hopefully no issues.

 

73

Charlie

www.G4EST.me.uk

 

From: HamApps@... [mailto:HamApps@...]
Sent: 15 November 2014 11:35
To: HamApps@...
Subject: RE: [HamApps] version 2.5.0 delay in populating boxes

 

 

Will do.

 

Thanks

 

73

Charlie

www.G4EST.me.uk

 

From: HamApps@... [mailto:HamApps@...]
Sent: 14 November 2014 20:15
To: HamApps@...
Subject: Re: [HamApps] version 2.5.0 delay in populating boxes

 

 

On 15/11/2014 12:57 AM, 'chas cartmel' chas@... [HamApps] wrote:

Laurie

Since the update to 2.5 I have noticed a lag in the population of the boxes in JTAlert-X, sometimes going as much as 4 seconds into the next receive cycle. It seems intermittent as on similar numbers of decodes it can be over at the 57 second mark.

I have observed the decode times in WSJT-X and these seem done by 55 seconds latest in the period.

Kit here has plenty of processing power and memory so would not have thought it was a CPU driven lag.

 

Also could you clarify what the numbers in the tx and rx columns of the band activity signify please? If 21 stations are being received then I would have thought that at least 21 stations are transmitting.

 

73

Charlie

www.G4EST.me.uk

Charlie,

Next time you observe a slow population of callsign slots, especially if it runs into the new minute, take a note of the UTC time and then send a support email with a note of the slowdaown time (makes it much easier to locate the correct session text in several thousand lines of data).

de Laurie VK3AMA
   

No virus found in this message.
Checked by AVG -
www.avg.com
Version: 2015.0.5577 / Virus Database: 4213/8572 - Release Date: 11/14/14

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5577 / Virus Database: 4213/8573 - Release Date: 11/14/14


locked Re: version 2.5.0 delay in populating boxes

chas cartmel
 

Will do.

 

Thanks

 

73

Charlie

www.G4EST.me.uk

 

From: HamApps@... [mailto:HamApps@...]
Sent: 14 November 2014 20:15
To: HamApps@...
Subject: Re: [HamApps] version 2.5.0 delay in populating boxes

 

 

On 15/11/2014 12:57 AM, 'chas cartmel' chas@... [HamApps] wrote:

Laurie

Since the update to 2.5 I have noticed a lag in the population of the boxes in JTAlert-X, sometimes going as much as 4 seconds into the next receive cycle. It seems intermittent as on similar numbers of decodes it can be over at the 57 second mark.

I have observed the decode times in WSJT-X and these seem done by 55 seconds latest in the period.

Kit here has plenty of processing power and memory so would not have thought it was a CPU driven lag.

 

Also could you clarify what the numbers in the tx and rx columns of the band activity signify please? If 21 stations are being received then I would have thought that at least 21 stations are transmitting.

 

73

Charlie

www.G4EST.me.uk

Charlie,

Next time you observe a slow population of callsign slots, especially if it runs into the new minute, take a note of the UTC time and then send a support email with a note of the slowdaown time (makes it much easier to locate the correct session text in several thousand lines of data).

de Laurie VK3AMA
   

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5577 / Virus Database: 4213/8572 - Release Date: 11/14/14


locked New - JTAlert 2.5.1 available - Defect fixes

Laurie, VK3AMA <groups06@...>
 

JTAlert 2.5.1 is available for download. This corrects all the defects identified since the 2.5.0 release

From the Release Notes...
JTAlert Version History:
--------------------------------------------------------------------------------
 
  Fixes:
    - WSJT-X 1.40 multi-instance support broken when WSJT-X install directory
       contains an "-r".
    - Unable to close QSO History popup after visiting the Settings window.
    - Missing WSJTX.dat or JT65HF.dat files prevent startup.
    - Missings text on HamSpots.net spotting request dialog window.
    - JTAlert hang when closing, needing to be killed by taskmanager (Win XP).

  Changes:
    - Finetuning of new decodes detection to help reduce callsign population time.


===========================================================================
 Online virus/malware scanner results can be viewed using the link below.

    virusscan.jotti.org : passed by 22 scan engines. Results

 File Information:
  Size:    4578276 bytes
  MD5:     6fe5ecaad6c9d9ada14dcd3ccef58b5b
===========================================================================

Visit the HamApps.com web page for the direct download link.

de Laurie VK3AMA


locked DEFECT Confirmed - JTAlert 2.5.0 under Win XP

Laurie, VK3AMA <groups06@...>
 

There is a defect with 2.5.0 where JTAlert doesn't close properly and needs to be killed using taskmanager.

I have only been able to reproduce this defect under Windows XP.

de Laurie VK3AMA
   


locked Re: : JTAlert 2.5.0 shut down problem

Laurie, VK3AMA <groups06@...>
 

On 15/11/2014 7:26 PM, vk7cej@... [HamApps] wrote:
Hello Laurie, thanks for your reply.   I tested it around 15 times and it was consistent, doing it every time.  I have now uninstalled 2.5.0. and gone back to 2.4.20.

73
John

John,

Ignore my last email. I have been able to reproduce the effect your observing. I tested on a different XP VM and I get the hang you describe. I'll post a new version once I have identified the defect in the code.

de Laurie VK3AMA
   


locked Re: : JTAlert 2.5.0 shut down problem

Laurie, VK3AMA <groups06@...>
 

On 15/11/2014 7:26 PM, vk7cej@... [HamApps] wrote:

Hello Laurie, thanks for your reply.   I tested it around 15 times and it was consistent, doing it every time.  I have now uninstalled 2.5.0. and gone back to 2.4.20.

73
John

Pity you have uninstalled, I was going to ask you to test the exit menu entries "Alerts -> Exit JTAlert" and "Settings -> Exit JTAlert" to see if they produced the same result as the Close button.

de Laurie VK3AMA
   


locked Re: : JTAlert 2.5.0 shut down problem

vk7cej@y7mail.com
 

Hello Laurie, thanks for your reply.   I tested it around 15 times and it was consistent, doing it every time.  I have now uninstalled 2.5.0. and gone back to 2.4.20.

73
John



locked Re: JTAlert 2.5.0 shut down problem

Laurie, VK3AMA <groups06@...>
 

On 15/11/2014 5:06 PM, vk7cej@... [HamApps] wrote:

Using here Windows XP Pro SP3.   When I shut down JTalert 2.5.0 using the red X in the top right corner of its window, it actually stays as an active application in Task Manager/Processes.   I discovered this when I shut the program down and then tried to restart.  Restart brings up a "Waiting for WSJT-X to start [2nd Instance]" error message which I have to then cancel/quit, open task manager, manually end the JTalert process and then restart JTalert.

John

John,

I can't reproduce that behaviour here in my XP test VM. I always use the Close button (Red "X" on right of window, not to be confused with the Red "X" icon) and have never seen this happen.

Does this consistently happen every time, or does this only occur at random times?

de Laurie VK3AMA
   


locked JTAlert 2.5.0 shut down problem

vk7cej@y7mail.com
 

Using here Windows XP Pro SP3.   When I shut down JTalert 2.5.0 using the red X in the top right corner of its window, it actually stays as an active application in Task Manager/Processes.   I discovered this when I shut the program down and then tried to restart.  Restart brings up a "Waiting for WSJT-X to start [2nd Instance]" error message which I have to then cancel/quit, open task manager, manually end the JTalert process and then restart JTalert.


John


locked Re: JTAlert 2.5.0 Not Working with WSJT-X v1.4.0-rc3

John P.
 

Hi Jim,

Yes I have the solution and it is now working.

Thanks for taking the time to reply

73
John - WA2HIP

--------------------------------------------

On Sat, 11/15/14, 'Jim - N4ST' newsgroup@jimpricejr.com [HamApps] <HamApps@yahoogroups.com.au> wrote:

Subject: RE: [HamApps] JTAlert 2.5.0 Not Working with WSJT-X v1.4.0-rc3
To: HamApps@yahoogroups.com.au
Date: Saturday, November 15, 2014, 4:08 AM


 









John,



Did you read the previous post/solution to this same
problem?



____

73,

Jim - N4ST



From: HamApps@yahoogroups.com.au
[mailto:HamApps@yahoogroups.com.au]

Sent: Friday, November 14, 2014 22:05

To: HamApps@yahoogroups.com.au

Subject: [HamApps] JTAlert 2.5.0 Not Working with WSJT-X
v1.4.0-rc3



Hi,



It appears that JTAlert 2.5.0 is not working here with
WSJT-X v1.4.0-rc3



Version 2.4.20 works, but when I install 2.5.0 there is
ABSOLUTELY NOTHING that shows in the JTAlert callsign
boxes.



I have uninstalled, gone back to 2.4.20 and it works there.
But installing 2.5.0 and again there is nothing in the
JTAlert.



I have for now gone back to the previous version of JTAlert
(2.4.20).



Maybe I am missing something here



John - WA2HIP













#yiv5297586014 #yiv5297586014 --
#yiv5297586014ygrp-mkp {
border:1px solid #d8d8d8;font-family:Arial;margin:10px
0;padding:0 10px;}

#yiv5297586014 #yiv5297586014ygrp-mkp hr {
border:1px solid #d8d8d8;}

#yiv5297586014 #yiv5297586014ygrp-mkp #yiv5297586014hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px
0;}

#yiv5297586014 #yiv5297586014ygrp-mkp #yiv5297586014ads {
margin-bottom:10px;}

#yiv5297586014 #yiv5297586014ygrp-mkp .yiv5297586014ad {
padding:0 0;}

#yiv5297586014 #yiv5297586014ygrp-mkp .yiv5297586014ad p {
margin:0;}

#yiv5297586014 #yiv5297586014ygrp-mkp .yiv5297586014ad a {
color:#0000ff;text-decoration:none;}
#yiv5297586014 #yiv5297586014ygrp-sponsor
#yiv5297586014ygrp-lc {
font-family:Arial;}

#yiv5297586014 #yiv5297586014ygrp-sponsor
#yiv5297586014ygrp-lc #yiv5297586014hd {
margin:10px
0px;font-weight:700;font-size:78%;line-height:122%;}

#yiv5297586014 #yiv5297586014ygrp-sponsor
#yiv5297586014ygrp-lc .yiv5297586014ad {
margin-bottom:10px;padding:0 0;}

#yiv5297586014 #yiv5297586014actions {
font-family:Verdana;font-size:11px;padding:10px 0;}

#yiv5297586014 #yiv5297586014activity {
background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

#yiv5297586014 #yiv5297586014activity span {
font-weight:700;}

#yiv5297586014 #yiv5297586014activity span:first-child {
text-transform:uppercase;}

#yiv5297586014 #yiv5297586014activity span a {
color:#5085b6;text-decoration:none;}

#yiv5297586014 #yiv5297586014activity span span {
color:#ff7900;}

#yiv5297586014 #yiv5297586014activity span
.yiv5297586014underline {
text-decoration:underline;}

#yiv5297586014 .yiv5297586014attach {
clear:both;display:table;font-family:Arial;font-size:12px;padding:10px
0;width:400px;}

#yiv5297586014 .yiv5297586014attach div a {
text-decoration:none;}

#yiv5297586014 .yiv5297586014attach img {
border:none;padding-right:5px;}

#yiv5297586014 .yiv5297586014attach label {
display:block;margin-bottom:5px;}

#yiv5297586014 .yiv5297586014attach label a {
text-decoration:none;}

#yiv5297586014 blockquote {
margin:0 0 0 4px;}

#yiv5297586014 .yiv5297586014bold {
font-family:Arial;font-size:13px;font-weight:700;}

#yiv5297586014 .yiv5297586014bold a {
text-decoration:none;}

#yiv5297586014 dd.yiv5297586014last p a {
font-family:Verdana;font-weight:700;}

#yiv5297586014 dd.yiv5297586014last p span {
margin-right:10px;font-family:Verdana;font-weight:700;}

#yiv5297586014 dd.yiv5297586014last p
span.yiv5297586014yshortcuts {
margin-right:0;}

#yiv5297586014 div.yiv5297586014attach-table div div a {
text-decoration:none;}

#yiv5297586014 div.yiv5297586014attach-table {
width:400px;}

#yiv5297586014 div.yiv5297586014file-title a, #yiv5297586014
div.yiv5297586014file-title a:active, #yiv5297586014
div.yiv5297586014file-title a:hover, #yiv5297586014
div.yiv5297586014file-title a:visited {
text-decoration:none;}

#yiv5297586014 div.yiv5297586014photo-title a,
#yiv5297586014 div.yiv5297586014photo-title a:active,
#yiv5297586014 div.yiv5297586014photo-title a:hover,
#yiv5297586014 div.yiv5297586014photo-title a:visited {
text-decoration:none;}

#yiv5297586014 div#yiv5297586014ygrp-mlmsg
#yiv5297586014ygrp-msg p a span.yiv5297586014yshortcuts {
font-family:Verdana;font-size:10px;font-weight:normal;}

#yiv5297586014 .yiv5297586014green {
color:#628c2a;}

#yiv5297586014 .yiv5297586014MsoNormal {
margin:0 0 0 0;}

#yiv5297586014 o {
font-size:0;}

#yiv5297586014 #yiv5297586014photos div {
float:left;width:72px;}

#yiv5297586014 #yiv5297586014photos div div {
border:1px solid
#666666;height:62px;overflow:hidden;width:62px;}

#yiv5297586014 #yiv5297586014photos div label {
color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

#yiv5297586014 #yiv5297586014reco-category {
font-size:77%;}

#yiv5297586014 #yiv5297586014reco-desc {
font-size:77%;}

#yiv5297586014 .yiv5297586014replbq {
margin:4px;}

#yiv5297586014 #yiv5297586014ygrp-actbar div a:first-child {
margin-right:2px;padding-right:5px;}

#yiv5297586014 #yiv5297586014ygrp-mlmsg {
font-size:13px;font-family:Arial, helvetica, clean,
sans-serif;}

#yiv5297586014 #yiv5297586014ygrp-mlmsg table {
font-size:inherit;font:100%;}

#yiv5297586014 #yiv5297586014ygrp-mlmsg select,
#yiv5297586014 input, #yiv5297586014 textarea {
font:99% Arial, Helvetica, clean, sans-serif;}

#yiv5297586014 #yiv5297586014ygrp-mlmsg pre, #yiv5297586014
code {
font:115% monospace;}

#yiv5297586014 #yiv5297586014ygrp-mlmsg * {
line-height:1.22em;}

#yiv5297586014 #yiv5297586014ygrp-mlmsg #yiv5297586014logo {
padding-bottom:10px;}


#yiv5297586014 #yiv5297586014ygrp-msg p a {
font-family:Verdana;}

#yiv5297586014 #yiv5297586014ygrp-msg
p#yiv5297586014attach-count span {
color:#1E66AE;font-weight:700;}

#yiv5297586014 #yiv5297586014ygrp-reco
#yiv5297586014reco-head {
color:#ff7900;font-weight:700;}

#yiv5297586014 #yiv5297586014ygrp-reco {
margin-bottom:20px;padding:0px;}

#yiv5297586014 #yiv5297586014ygrp-sponsor #yiv5297586014ov
li a {
font-size:130%;text-decoration:none;}

#yiv5297586014 #yiv5297586014ygrp-sponsor #yiv5297586014ov
li {
font-size:77%;list-style-type:square;padding:6px 0;}

#yiv5297586014 #yiv5297586014ygrp-sponsor #yiv5297586014ov
ul {
margin:0;padding:0 0 0 8px;}

#yiv5297586014 #yiv5297586014ygrp-text {
font-family:Georgia;}

#yiv5297586014 #yiv5297586014ygrp-text p {
margin:0 0 1em 0;}

#yiv5297586014 #yiv5297586014ygrp-text tt {
font-size:120%;}

#yiv5297586014 #yiv5297586014ygrp-vital ul li:last-child {
border-right:none !important;
}
#yiv5297586014


locked Re: JTAlert 2.5.0 Not Working with WSJT-X v1.4.0-rc3

John P.
 

HI,

Yes my directory is named "wsjtx4-RC3-r4576" (no quotes)

You can see the "-r" in that.

This WSJT-X version is an update to better support my Icom 7200 CAT commands and its setup of the rig.

I followed your instructions and now it is working very well.

It is a most interesting "quirk" !!


While I have the opportunity, I want to thank you for this STELLAR add-on for WSJT-X. You have certainly earned many people's (including mine) for your efforts.

73
John - WA2HIP
http://wa2hip.com




--------------------------------------------

On Sat, 11/15/14, 'Laurie, VK3AMA' groups06@vkdxer.com [HamApps] <HamApps@yahoogroups.com.au> wrote:

Subject: Re: [HamApps] JTAlert 2.5.0 Not Working with WSJT-X v1.4.0-rc3
To: HamApps@yahoogroups.com.au
Date: Saturday, November 15, 2014, 3:50 AM


 












On 15/11/2014 2:04 PM,
'John P.'
jpetrocxme@yahoo.com
[HamApps] wrote:



Hi,


It appears that JTAlert 2.5.0 is not working here with
WSJT-X v1.4.0-rc3


Version 2.4.20 works, but when I install 2.5.0 there is
ABSOLUTELY NOTHING that shows in the JTAlert callsign boxes.


I have uninstalled, gone back to 2.4.20 and it works
there. But installing 2.5.0 and again there is nothing in
the JTAlert.


I have for now gone back to the previous version of
JTAlert (2.4.20).




Maybe I am missing something here


John - WA2HIP


John,



Does your WSJT-X install directory contain the text
"-r" ? There
is a defect with 2.5.0 that produces the results you
described if
the directory contains "-r".



A fix was posted several hours ago, titled "FIX
for WSJT-X 1.40
and JTAlert 2.5.0".



From that message...


Download... http://HamApps.com/dnl/Fixes/2.5.0/JTAlert.exe



Stop JTAlertX and replace the existing JTAlert.exe in
your JTAlert
install directory.



This is a replacement file, not a setup or upgrade
executable.


 de Laurie VK3AMA

   














#yiv0683156024 #yiv0683156024 --
#yiv0683156024ygrp-mkp {
border:1px solid #d8d8d8;font-family:Arial;margin:10px
0;padding:0 10px;}

#yiv0683156024 #yiv0683156024ygrp-mkp hr {
border:1px solid #d8d8d8;}

#yiv0683156024 #yiv0683156024ygrp-mkp #yiv0683156024hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px
0;}

#yiv0683156024 #yiv0683156024ygrp-mkp #yiv0683156024ads {
margin-bottom:10px;}

#yiv0683156024 #yiv0683156024ygrp-mkp .yiv0683156024ad {
padding:0 0;}

#yiv0683156024 #yiv0683156024ygrp-mkp .yiv0683156024ad p {
margin:0;}

#yiv0683156024 #yiv0683156024ygrp-mkp .yiv0683156024ad a {
color:#0000ff;text-decoration:none;}
#yiv0683156024 #yiv0683156024ygrp-sponsor
#yiv0683156024ygrp-lc {
font-family:Arial;}

#yiv0683156024 #yiv0683156024ygrp-sponsor
#yiv0683156024ygrp-lc #yiv0683156024hd {
margin:10px
0px;font-weight:700;font-size:78%;line-height:122%;}

#yiv0683156024 #yiv0683156024ygrp-sponsor
#yiv0683156024ygrp-lc .yiv0683156024ad {
margin-bottom:10px;padding:0 0;}

#yiv0683156024 #yiv0683156024actions {
font-family:Verdana;font-size:11px;padding:10px 0;}

#yiv0683156024 #yiv0683156024activity {
background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

#yiv0683156024 #yiv0683156024activity span {
font-weight:700;}

#yiv0683156024 #yiv0683156024activity span:first-child {
text-transform:uppercase;}

#yiv0683156024 #yiv0683156024activity span a {
color:#5085b6;text-decoration:none;}

#yiv0683156024 #yiv0683156024activity span span {
color:#ff7900;}

#yiv0683156024 #yiv0683156024activity span
.yiv0683156024underline {
text-decoration:underline;}

#yiv0683156024 .yiv0683156024attach {
clear:both;display:table;font-family:Arial;font-size:12px;padding:10px
0;width:400px;}

#yiv0683156024 .yiv0683156024attach div a {
text-decoration:none;}

#yiv0683156024 .yiv0683156024attach img {
border:none;padding-right:5px;}

#yiv0683156024 .yiv0683156024attach label {
display:block;margin-bottom:5px;}

#yiv0683156024 .yiv0683156024attach label a {
text-decoration:none;}

#yiv0683156024 blockquote {
margin:0 0 0 4px;}

#yiv0683156024 .yiv0683156024bold {
font-family:Arial;font-size:13px;font-weight:700;}

#yiv0683156024 .yiv0683156024bold a {
text-decoration:none;}

#yiv0683156024 dd.yiv0683156024last p a {
font-family:Verdana;font-weight:700;}

#yiv0683156024 dd.yiv0683156024last p span {
margin-right:10px;font-family:Verdana;font-weight:700;}

#yiv0683156024 dd.yiv0683156024last p
span.yiv0683156024yshortcuts {
margin-right:0;}

#yiv0683156024 div.yiv0683156024attach-table div div a {
text-decoration:none;}

#yiv0683156024 div.yiv0683156024attach-table {
width:400px;}

#yiv0683156024 div.yiv0683156024file-title a, #yiv0683156024
div.yiv0683156024file-title a:active, #yiv0683156024
div.yiv0683156024file-title a:hover, #yiv0683156024
div.yiv0683156024file-title a:visited {
text-decoration:none;}

#yiv0683156024 div.yiv0683156024photo-title a,
#yiv0683156024 div.yiv0683156024photo-title a:active,
#yiv0683156024 div.yiv0683156024photo-title a:hover,
#yiv0683156024 div.yiv0683156024photo-title a:visited {
text-decoration:none;}

#yiv0683156024 div#yiv0683156024ygrp-mlmsg
#yiv0683156024ygrp-msg p a span.yiv0683156024yshortcuts {
font-family:Verdana;font-size:10px;font-weight:normal;}

#yiv0683156024 .yiv0683156024green {
color:#628c2a;}

#yiv0683156024 .yiv0683156024MsoNormal {
margin:0 0 0 0;}

#yiv0683156024 o {
font-size:0;}

#yiv0683156024 #yiv0683156024photos div {
float:left;width:72px;}

#yiv0683156024 #yiv0683156024photos div div {
border:1px solid
#666666;height:62px;overflow:hidden;width:62px;}

#yiv0683156024 #yiv0683156024photos div label {
color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

#yiv0683156024 #yiv0683156024reco-category {
font-size:77%;}

#yiv0683156024 #yiv0683156024reco-desc {
font-size:77%;}

#yiv0683156024 .yiv0683156024replbq {
margin:4px;}

#yiv0683156024 #yiv0683156024ygrp-actbar div a:first-child {
margin-right:2px;padding-right:5px;}

#yiv0683156024 #yiv0683156024ygrp-mlmsg {
font-size:13px;font-family:Arial, helvetica, clean,
sans-serif;}

#yiv0683156024 #yiv0683156024ygrp-mlmsg table {
font-size:inherit;font:100%;}

#yiv0683156024 #yiv0683156024ygrp-mlmsg select,
#yiv0683156024 input, #yiv0683156024 textarea {
font:99% Arial, Helvetica, clean, sans-serif;}

#yiv0683156024 #yiv0683156024ygrp-mlmsg pre, #yiv0683156024
code {
font:115% monospace;}

#yiv0683156024 #yiv0683156024ygrp-mlmsg * {
line-height:1.22em;}

#yiv0683156024 #yiv0683156024ygrp-mlmsg #yiv0683156024logo {
padding-bottom:10px;}


#yiv0683156024 #yiv0683156024ygrp-msg p a {
font-family:Verdana;}

#yiv0683156024 #yiv0683156024ygrp-msg
p#yiv0683156024attach-count span {
color:#1E66AE;font-weight:700;}

#yiv0683156024 #yiv0683156024ygrp-reco
#yiv0683156024reco-head {
color:#ff7900;font-weight:700;}

#yiv0683156024 #yiv0683156024ygrp-reco {
margin-bottom:20px;padding:0px;}

#yiv0683156024 #yiv0683156024ygrp-sponsor #yiv0683156024ov
li a {
font-size:130%;text-decoration:none;}

#yiv0683156024 #yiv0683156024ygrp-sponsor #yiv0683156024ov
li {
font-size:77%;list-style-type:square;padding:6px 0;}

#yiv0683156024 #yiv0683156024ygrp-sponsor #yiv0683156024ov
ul {
margin:0;padding:0 0 0 8px;}

#yiv0683156024 #yiv0683156024ygrp-text {
font-family:Georgia;}

#yiv0683156024 #yiv0683156024ygrp-text p {
margin:0 0 1em 0;}

#yiv0683156024 #yiv0683156024ygrp-text tt {
font-size:120%;}

#yiv0683156024 #yiv0683156024ygrp-vital ul li:last-child {
border-right:none !important;
}
#yiv0683156024


locked Re: JTAlert 2.5.0 Not Working with WSJT-X v1.4.0-rc3

Jim - N4ST
 

John,

Did you read the previous post/solution to this same problem?

____
73,
Jim - N4ST


From: HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
Sent: Friday, November 14, 2014 22:05
To: HamApps@yahoogroups.com.au
Subject: [HamApps] JTAlert 2.5.0 Not Working with WSJT-X v1.4.0-rc3


Hi,

It appears that JTAlert 2.5.0 is not working here with WSJT-X v1.4.0-rc3

Version 2.4.20 works, but when I install 2.5.0 there is ABSOLUTELY NOTHING that shows in the JTAlert callsign boxes.

I have uninstalled, gone back to 2.4.20 and it works there. But installing 2.5.0 and again there is nothing in the JTAlert.

I have for now gone back to the previous version of JTAlert (2.4.20).

Maybe I am missing something here

John - WA2HIP


locked Re: JTAlert 2.5.0 Not Working with WSJT-X v1.4.0-rc3

Laurie, VK3AMA <groups06@...>
 

On 15/11/2014 2:04 PM, 'John P.' jpetrocxme@... [HamApps] wrote:
Hi,


  It appears that JTAlert 2.5.0 is not working here with WSJT-X v1.4.0-rc3


  Version 2.4.20 works, but when I install 2.5.0 there is ABSOLUTELY NOTHING that shows in the JTAlert callsign boxes.


  I have uninstalled, gone back to 2.4.20 and it works there. But installing 2.5.0 and again there is nothing in the JTAlert.


  I have for now gone back to the previous version of JTAlert (2.4.20).




  Maybe I am missing something here


John - WA2HIP
John,

Does your WSJT-X install directory contain the text "-r" ? There is a defect with 2.5.0 that produces the results you described if the directory contains "-r".

A fix was posted several hours ago, titled "FIX for WSJT-X 1.40 and JTAlert 2.5.0".

From that message...
Download... http://HamApps.com/dnl/Fixes/2.5.0/JTAlert.exe

Stop JTAlertX and replace the existing JTAlert.exe in your JTAlert install directory.

This is a replacement file, not a setup or upgrade executable.

 de Laurie VK3AMA
   


locked JTAlert 2.5.0 Not Working with WSJT-X v1.4.0-rc3

John P.
 

Hi,


It appears that JTAlert 2.5.0 is not working here with WSJT-X v1.4.0-rc3


Version 2.4.20 works, but when I install 2.5.0 there is ABSOLUTELY NOTHING that shows in the JTAlert callsign boxes.


I have uninstalled, gone back to 2.4.20 and it works there. But installing 2.5.0 and again there is nothing in the JTAlert.


I have for now gone back to the previous version of JTAlert (2.4.20).




Maybe I am missing something here


John - WA2HIP