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
Since I'm replacing this AMD computer with an Intel Core I5 in a short
while, I don't want to invest a ton of time chasing down this problem if it
only affects me and a couple others. It will go away when I change
computers, as I have this same combo running on another machine with no
issues.
In t
When it happens again do the WWV recording with Audacity and note the time you
shut down JTAlert in the recording time indication.It has to be doing something
to the sound recording --
Having both the Audacity and WAV files would be of use.
On Tuesday, July 30, 2019, 08:21:29 AM CDT, Hasan
Hi Mike
Never. The monitor (Hi-Sense TV) is on until I go to bed, then I turn the
TV off. Ever since I found out that there was a JTA > X interaction that
was causing the problem, I have looked carefully in the morning when I come
down to the shack to see if X is still decoding...and it is, except
Does your monitor go to sleep? JTAlert should only be hooking up to the
playback device so not sure how it could affect recording. Possible that the
JTAlert package does passively hook up to recording...that would explain why a
restart might have an effect on recordingperhaps changing the
Bobby,
That has always been my setting. (not checked)
tnx, 73, N0AN
Hasan
On Tue, Jul 30, 2019 at 8:03 AM Bobby Chandler wrote:
> Hasan,
>
> Try this:
>
> On wsjtx go to settings, General. Make sure 'Start new period decodes at
> top' is not ticked.
>
> Bobby/N4AU
> On 7/30/2019 7:26 AM, Hasan
Totally different sound cards. JTA uses my HDMI monitor seen as an Nvidia,
X uses my USB sound dongle. I've changed dongles, ...no difference. I've
chased the sound card potential issue from several angles...that's not it.
...and Windows system uses the internal sound card of the computer.
Hasan
Hasan,
Try this:
On wsjtx go to settings, General. Make sure
'Start new period decodes at top' is not ticked.
Bobby/N4AU
On 7/30/2019 7:26 AM, Hasan al-Basri
wrote:
Uwe,
I just
changed both those setting
What do you have for the soundcard setting in JTAlert and WSJT-X?
On Tuesday, July 30, 2019, 07:30:17 AM CDT, Hasan al-Basri
wrote:
Uwe,I just changed both those settings you recommended. Now, I'll have to
wait, up to a couple days to see if it accomplished anything.
Unfortunately t
Uwe,
I just changed both those settings you recommended. Now, I'll have to wait,
up to a couple days to see if it accomplished anything.
Unfortunately the onset of the problem is random, and can take 2 or 3 days
or only a few hours. Curing it is easy. I'll report back as I'm watching
it. For sure
Hi Hasan,
An interesting observation! What if you uncheck the boxed “Color Band
Activity…” and/or “Highlight Band Activity…”? Is the error still there 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
13 matches
Mail list logo
