Laurie,
How about this then:
taskkill /IM /T jtalert.exe
That is supposed to not forcefully terminate but issue a WM_CLOSE followed
by telling any Child Process started by the JTA program to also close.
Is that safe? Or what is the proper command line to tell JTALERT.EXE to
close "properly" ?
Ok, I'll look at another way to close it.
Tnx tip, 73, N0AN
Hasan
On Tue, Jul 30, 2019 at 3:53 PM Laurie, VK3AMA <_vk3a...@vkdxer.net> wrote:
>
> On 31/07/2019 2:03 am, Hasan al-Basri wrote:
>
> Put this in a batch file: (use notepad to create)
>
> taskkill /F /IM jtalert.exe
>
>
> NO, don't do
On 31/07/2019 2:03 am, Hasan al-Basri wrote:
Put this in a batch file: (use notepad to create)
taskkill /F /IM jtalert.exe
NO, don't do this!
Force killing the JTAlert process, rather than a managed shutdown,
*doesn't close any of the JTAlert plugin processes or the Decodes
History process
re or
> is it gone?
>
>
>
>
>
>
>
> I had in the past also some (other) troubles with JTAlert, but it turned
> out that some files on my computer must have been corrupted. Uninstalled
> JTAlert completely, removed all remaining files manually and the
> reinsta
li 2019 12:33
An: WSJT software development
Betreff: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present
First of all, no, the cause is not clock error.
I have found the "proximate" cause, however, after weeks of hunting. I worked
with W9MDB and tested/considered m
(other) troubles with JTAlert, but it turned
> out that some files on my computer must have been corrupted. Uninstalled
> JTAlert completely, removed all remaining files manually and the
> reinstalled JTAlert again, and all the errors were gone. Maybe also worth
> to try…
>
>
>
>
e errors were gone. Maybe also worth to try…
73 de Uwe, DG2YCB
Von: Hasan al-Basri [mailto:hbasri.schie...@gmail.com]
Gesendet: Dienstag, 30. Juli 2019 12:33
An: WSJT software development
Betreff: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present
First of all, no, the cause
rth
>> to try…
>>
>>
>>
>> 73 de Uwe, DG2YCB
>>
>>
>>
>> *Von:* Hasan al-Basri [mailto:hbasri.schie...@gmail.com]
>> *Gesendet:* Dienstag, 30. Juli 2019 12:33
>> *An:* WSJT software development
>> *Betreff:* [wsjt-devel] Loss o
some files on my computer must have been corrupted. Uninstalled
> JTAlert completely, removed all remaining files manually and the
> reinstalled JTAlert again, and all the errors were gone. Maybe also worth
> to try…
>
>
>
> 73 de Uwe, DG2YCB
>
>
>
> *Von:* Hasan
de Uwe, DG2YCB
Von:
Hasan al-Basri [mailto:hbasri.schie...@gmail.com]
Gesendet: Dienstag, 30. Juli 2019 12:33
An: WSJT software development
Betreff: [
0. Juli 2019 12:33
An: WSJT software development
Betreff: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present
First of all, no, the cause is not clock error.
I have found the "proximate" cause, however, after weeks of hunting. I worked
with W9MDB and tested/considered
aining files manually and the
> reinstalled JTAlert again, and all the errors were gone. Maybe also worth
> to try…
>
>
>
> 73 de Uwe, DG2YCB
>
>
>
> *Von:* Hasan al-Basri [mailto:hbasri.schie...@gmail.com]
> *Gesendet:* Dienstag, 30. Juli 2019 12:33
> *An:* WSJ
12:33
An: WSJT software development
Betreff: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present
First of all, no, the cause is not clock error.
I have found the "proximate" cause, however, after weeks of hunting. I worked
with W9MDB and tested/considered many potent
First of all, no, the cause is not clock error.
I have found the "proximate" cause, however, after weeks of hunting. I
worked with W9MDB and tested/considered many potential causes. I even
thought I had found it several times. In all those cases there was a
confounding variable, which I have now i
14 matches
Mail list logo
