Re: [Dx4win] eQSL import question
Thanks Mel,
Yes, this will work, but it has the (slight) downside that if I do like this, I
will *never* import anything to
the notes field. For example, the first time I import a (new) confirmation from
eQSL, there will not be any
additional grid square information imported, even if that information would
have been accurate and useful.(To acheive this it seems I would need to check
each QSO manually and only add the " skrev:
The example was wrong
Before:
SM0JT20110712084640MSSB59YEYJO89UIAfter:
SM0JT20110712084640MSSB59YEYJO89UI
Den tors 11 feb. 2021 kl 16:44 skrev Claes "Mel" Carneheim :
Hello Mats
Open the exported ADIF-fil in a text editor e.g. Notepad.
Change all SM0JT20110712084640MSSB59YEYJO89UIAfter:
SM0JT20110712084640MSSB59YEYJO89UI
Den ons 10 feb. 2021 kl 21:48 skrev Mats Naslund via DX4WIN
:
Hello,
When exporting confirmed QSO:s from eQSL, there only seems to be one option
supported by
eQSL: to export the whole log/inbox as ADIF each time. That is, unlike LotW,
there is AFAICT no
option in eQSL to only download new QSLs, received after the most recent
download.
Thus, when importing this to DX4WIN ("Confirm using ADIF") there will be
re-imports of eQSL:s that
have already been imported. This, as such, is no problem since DX4WIN handles
“dupes” during
import. However, if there is a conflict between the imported QSO and the QSO in
the log (for example,
the Grid-square values differ), then DX4WIN will add this in the "Notes for
this QSO" field.
As far as I can tell, if I import the same QSO/eQSL again, then DX4WIN adds
yet another note, with
precisely the same content. I checked, and this does seem to be the case. For
example, I have a
QSO with a Finish OH-station with the following content in the QSO-notes field:
"Import:{Grid=KP20af} Import:{Grid=KP20af} Import:{Grid=KP20af}",
apparently coming from eQSL imports confirming the same QSO three times.
Arguably, this is a shortcoming of the eQSL export feature, but I am curious if
there is a way to configure
DX4WIN so that it does not add an new import note which is identical to one
that already exists?
73 + TNX
/Mats, SM3LGO
__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] eQSL import question
Hello,
When exporting confirmed QSO:s from eQSL, there only seems to be one option
supported by
eQSL: to export the whole log/inbox as ADIF each time. That is, unlike LotW,
there is AFAICT no
option in eQSL to only download new QSLs, received after the most recent
download.
Thus, when importing this to DX4WIN ("Confirm using ADIF") there will be
re-imports of eQSL:s that
have already been imported. This, as such, is no problem since DX4WIN handles
“dupes” during
import. However, if there is a conflict between the imported QSO and the QSO in
the log (for example,
the Grid-square values differ), then DX4WIN will add this in the "Notes for
this QSO" field.
As far as I can tell, if I import the same QSO/eQSL again, then DX4WIN adds
yet another note, with
precisely the same content. I checked, and this does seem to be the case. For
example, I have a
QSO with a Finish OH-station with the following content in the QSO-notes field:
"Import:{Grid=KP20af} Import:{Grid=KP20af} Import:{Grid=KP20af}",
apparently coming from eQSL imports confirming the same QSO three times.
Arguably, this is a shortcoming of the eQSL export feature, but I am curious if
there is a way to configure
DX4WIN so that it does not add an new import note which is identical to one
that already exists?
73 + TNX
/Mats, SM3LGO
__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] Cannot start after update
Hi, I have been running v9.03 for a while but decided to try an update today. After update, DX4WIN won't start at allThe bug report says "EAssertion failed", and "Unknown IOTA OC297". Any suggestion?(I am pasting the report below.) 73, TNX /Mats ---date/time : 2020-04-30, 19:48:48, 961ms computer name : DESKTOP-I44JCRQ user name : sm3lg registered owner : admin operating system : Windows NT New x64 build 9200 system language : Swedish system up time : 1 hour program up time : 202 milliseconds processors : 4x Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz physical memory : 5171/8102 MB (free/total) free disk space : (C:) 355,84 GB display mode : 1366x768, 32 bit process id : $16dc allocated memory : 114,24 MB executable : dx4win.exe exec. date/time : 2020-04-30 19:33 version : 9.0.9.1259 compiled with : Delphi 7 madExcept version : 3.0n dx4win.exe.mad : $00037cc8, $b2644f86, $bd9b08ff callstack crc : $f0bc175a, $64c35f5e, $64c35f5e exception number : 1 exception class : EAssertionFailed exception message : TIOTASbyPrefix: unknown IOTA=OC297 for prefix=FO (C:\dx4win_src\trunk\prefs.pas, line 1890). main thread ($2da8): 006a9c98 +3f0 dx4win.exe segment%381 public%15606 006a6f18 +2f0 dx4win.exe segment%381 public%15546 00671921 +14d dx4win.exe segment%344 public%14685 004d83d9 +031 dx4win.exe segment%72 public%6332 004d8040 +124 dx4win.exe segment%72 public%6327 76ecd374 +034 user32.dll SetWindowTextA 004df8ad +031 dx4win.exe segment%72 public%6595 006c23c6 +06e dx4win.exe segment%401 public%16227 772c6357 +017 KERNEL32.DLL BaseThreadInitThunk thread $33a8: 772c6357 +17 KERNEL32.DLL BaseThreadInitThunk thread $1c24: 772c6357 +17 KERNEL32.DLL BaseThreadInitThunk thread $1588: 772c6357 +17 KERNEL32.DLL BaseThreadInitThunk cpu registers: eax = 097fabe0 ebx = ecx = 0019f0a8 edx = 006a9c98 esi = 0061 edi = 00670b64 eip = 006a9c98 esp = 0019f07c ebp = 0019fc14 stack dump: 0019f07c 98 9c 6a 00 de fa ed 0e - 01 00 00 00 07 00 00 00 ..j. 0019f08c 90 f0 19 00 98 9c 6a 00 - e0 ab 7f 09 00 00 00 00 ..j. 0019f09c 61 00 00 00 64 0b 67 00 - 14 fc 19 00 ac f0 19 00 a...d.g. 0019f0ac 98 9c 6a 00 1c fc 19 00 - c8 50 40 00 14 fc 19 00 ..j..P@. 0019f0bc 64 0b 67 00 10 aa ac 02 - 3c 5c 50 00 00 00 00 00 d.g.<\P. 0019f0cc 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f0dc 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f0ec 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f0fc 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f10c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f11c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f12c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f13c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f14c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f15c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f16c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f17c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f18c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f19c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 0019f1ac 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 disassembling: [...] 006a9c62 lea edx, [ebp-$700] 006a9c68 call -$2a41e1 ($405a8c) ; segment%0.public%292 (dx4win.exe) 006a9c6d push dword ptr [ebp-$a48] 006a9c73 lea eax, [ebp-$a40] 006a9c79 mov edx, 4 006a9c7e call -$2a40db ($405ba8) ; segment%0.public%299 (dx4win.exe) 006a9c83 mov eax, [ebp-$a40] 006a9c89 mov ecx, $762 006a9c8e mov edx, $6a9ec0 ; 'C:\dx4win_src\trunk\prefs.pas' 006a9c93 call -$2a4524 ($405774) ; segment%0.public%275 (dx4win.exe) 006a9c98 > jmp loc_6a9cb8 006a9c9a inc dword ptr [ebp-8] 006a9c9d mov edx, [ebp-8] 006a9ca0 shl edx, 2 006a9ca3 lea eax, [ebp-4] 006a9ca6 call -$2a718b ($402b20) ; segment%0.public%95 (dx4win.exe) 006a9cab mov eax, [ebp-4] 006a9cae mov edx, [ebp-8] 006a9cb1 mov ecx, [ebp-$24] 006a9cb4 mov [eax+edx*4-4], ecx 006a9cb8 lea esi, [ebx+1] [...] __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] DX4WIN failed to start - Bug report is available - Need advice
Hi I had the same "fail to start" symptoms and discovered why (it may not be the same reason as others encountered though). I am logging on two separate PC:s (two QTHs) and therefore sometimes copy the most recent log manually from PC1 to PC2. Last night, on PC1, I had manually made a country exception for one logged station. I then moved the updated log over to PC2. On PC2, DX4WIN failed to start with the externally updated log. If I however manually make the same country exception on PC2, it starts OK. 73 /Mats, SM3LGO __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net Message delivered to arch...@mail-archive.com This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
