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" ? Once I have that, I can put it in the batch file and JTA will close gracefully and it can be restarted a few minutes later. Hasan On Tue, Jul 30, 2019 at 4:41 PM Hasan al-Basri <hbasri.schie...@gmail.com> wrote: > 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 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*, >> they are all still left running becoming zombie processes. >> >> Force killing JTAlert significantly increases the risk of corruption of >> the config.sqlite database file and the decodes database. >> >> de Laurie VK3AMA >> >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
