[WT-support] Observations during SAC

[Laurent HAAS - F6FVY]

Hi Marko

marko.holmavuo at dnainternet.net a écrit :

> Other thing what I noticed is: If you have hamcap installed without voacap, 
> you will get error message every time you load the logfile, even you have 
> disabled the hamcap interfacing (but tried to enable the interface in past). 
> 
> This feature popped up when I forget to install voacap, but I installed 
> hamcap. I activated the hamcap interface, but noticed errormessages that 
> voacap is missing, after that I disabled the interface, but still got errors 
> when loading the log file. Don't know if this is normal or not.

It's "normal" (even if it sound weird or not desirable).

This is how it works : On every initialisation (= startup or file 
loading), WT starts (or tries to start) HamCAP in the background, to be 
more responsive during its use. If you're curious enough you can open 
the task manager after a log loading and find a HamCAP process running, 
even if you disabled the interface.

The thing becomes tricker if HamCAP is corrupted or so : The HamCAP 
process is launched (and working), but if voacap is not installed etc... 
  it generates an error, as you noticed.

The correct way to use HamCAP with WT is to install it and to *check* it 
works on a standalone basis. Most of the time, the users don't even read 
the installation procedure (as usual) given by VE3NEA, which describes 
how to install voacap etc... Once everything is OK with HC (alone), 
start WT : It will be automagically usable from the log.

73

Larry - F6FVY