To be correct, in JTDX Fox was never implemented. Maybe in future will be done. There 2 different things 1. using Dxpd commands (RR73 to one report to other) 2. using multistream tx. Why not...
Liked On: 26.10.2025, 15:29
To be correct, in JTDX Fox was never implemented. Maybe in future will be done. There 2 different things 1. using Dxpd commands (RR73 to one report to other) 2. using multistream tx. Why not...
Liked On: 26.10.2025, 15:18
Yep clone from jtdx 159, also tci, only bad thing, nowhere mentioned that it is taken from jtdx. Expected some credentials. Stupid from their side.
Liked On: 17.09.2025, 09:45
Yep clone from jtdx 159, also tci, only bad thing, nowhere mentioned that it is taken from jtdx. Expected some credentials. Stupid from their side.
Liked On: 17.09.2025, 09:36
Yep clone from jtdx 159, also tci, only bad thing, nowhere mentioned that it is taken from jtdx. Expected some credentials. Stupid from their side.
Liked On: 17.09.2025, 08:11
In general also ini file is compatible with different versions. Newer versions may add some new keys (or not using some old keys). At least I never deleted ini file. Sure when ini is somehow screwed...
Liked On: 15.09.2025, 19:58
Yes from 160-rc6
Liked On: 12.09.2025, 10:57
No, hash values are different.
Liked On: 11.08.2025, 10:22
This is 3-d option from bottom, but it is off. Try to enable and them move to other place and then disable.
Liked On: 14.07.2025, 22:54
Stupid nonstd callsign owner calling with report. - - - Добавлено - - - You had std callsign in DxCall field, but in other side was correspondent using call with /, it is essential to have...
Liked On: 02.07.2025, 19:43
problem found and fixed. Z68YL has hash value 0. Anyway this is only beauty problem.
Liked On: 29.05.2025, 06:02
problem found and fixed. Z68YL has hash value 0. Anyway this is only beauty problem.
Liked On: 28.05.2025, 22:27
Was able to repeat problem, as I always have Save on, TNX for pointing this out 173300 7 0.1 592 ~ ES1JA > RR73 173300 7 0.1 592 ~ SP8BU > +02
Liked On: 26.05.2025, 19:34
Tnx Nic for info JTDX does not have problem with wrong grid, jtdx has own method of checking call and grid. 1. for ap mask decodes filter check data against data from ALLCALL.TXT 2. additionally...
Liked On: 22.05.2025, 20:33
General rule, -26 decodes should be rare if not to say very rare. It depends mainly of qrm situation in qth. 1. To try is set QSO Rx freq sensitivity to low. If remember correctly medium is default...
Liked On: 22.05.2025, 16:22