https://www.swisslogforwindows.com/forum/ Sun, 06 Sep 2026 22:45:30 +0000 MyBB https://www.swisslogforwindows.com/forum/showthread.php?tid=1378 Sun, 06 Sep 2026 15:14:09 +0000 EA3GCV]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1378
I have released a beta including the following improvements (latest changes highlighted in boldface):

• NEW: French Regions: Swisslog will automatically fill out the French Region field in all QSO with French stations (DXCC = F) where user has set the DDFM number (French Departament)
  
• Corrected: QSO Entry > Station tab: Notes field was displayed empty when adding a new QSO with a previously worked station having notes in the C_NOTE field.
  
• Corrected: QSO Entry > Station tab: Note field Unicode characters were displayed as ???.
  
• Corrected: Band Maps: double clicking on a spot, if one of the actions was Log QSO and the spot contained award info such as WFF, SOTA, DME, etc. these fields were not set in the QSO Entry window.
  
• Corrected: Dx Alerts: position and size were not restored after closing Swisslog.
  
• Corrected: Telnet server window: now accented latin characters are displayed properly
  
• Corrected: Routine to process Pendient Log QSO Requests: often one or some QSO were lost during the process of the queue of Pending Log QSO requests. Now the routine has been improved and it checks if the QSO has been really saved before deleting it from the queue. In case it's not saved the routine will process next queued QSO leaving this pending QSO in the queue to be processed later.
  
• Corrected:  Routine to process Pendient Log QSO Requests: BETA from 20th August had a queue limit of 20 instead of 3000.  Also QSOs were saved twice under certain setups.
  
• Corrected: DEE info table: DME where not imported properly resulting with no leading zero in DME. Example: instead of 01001 was imported as 1001.
  
• Optimized: Transceiver control for TCI and Flex Radio: reduced traffic drastically improving overall performance
  
• Corrected: Logbook view: Manual tab: when selecting a MyQTH the following error message appears: Parameter L_MyQTHID has no default value.
  
• Corrected: Import ADIF QSO: selecting option "QSL action based on QSL Received/sent" fields didn't work and a blank QSL Action was set despite user assigned a value in the QSL-Action field.
  

]]>
I have released a beta including the following improvements (latest changes highlighted in boldface):

• NEW: French Regions: Swisslog will automatically fill out the French Region field in all QSO with French stations (DXCC = F) where user has set the DDFM number (French Departament)
  
• Corrected: QSO Entry > Station tab: Notes field was displayed empty when adding a new QSO with a previously worked station having notes in the C_NOTE field.
  
• Corrected: QSO Entry > Station tab: Note field Unicode characters were displayed as ???.
  
• Corrected: Band Maps: double clicking on a spot, if one of the actions was Log QSO and the spot contained award info such as WFF, SOTA, DME, etc. these fields were not set in the QSO Entry window.
  
• Corrected: Dx Alerts: position and size were not restored after closing Swisslog.
  
• Corrected: Telnet server window: now accented latin characters are displayed properly
  
• Corrected: Routine to process Pendient Log QSO Requests: often one or some QSO were lost during the process of the queue of Pending Log QSO requests. Now the routine has been improved and it checks if the QSO has been really saved before deleting it from the queue. In case it's not saved the routine will process next queued QSO leaving this pending QSO in the queue to be processed later.
  
• Corrected:  Routine to process Pendient Log QSO Requests: BETA from 20th August had a queue limit of 20 instead of 3000.  Also QSOs were saved twice under certain setups.
  
• Corrected: DEE info table: DME where not imported properly resulting with no leading zero in DME. Example: instead of 01001 was imported as 1001.
  
• Optimized: Transceiver control for TCI and Flex Radio: reduced traffic drastically improving overall performance
  
• Corrected: Logbook view: Manual tab: when selecting a MyQTH the following error message appears: Parameter L_MyQTHID has no default value.
  
• Corrected: Import ADIF QSO: selecting option "QSL action based on QSL Received/sent" fields didn't work and a blank QSL Action was set despite user assigned a value in the QSL-Action field.
  

]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1377 Thu, 03 Sep 2026 17:11:59 +0000 dl1daw]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1377 https://www.swisslogforwindows.com/forum/showthread.php?tid=1375 Fri, 28 Aug 2026 17:59:33 +0000 EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1375
It has one new definition: MB has been added for G England. Swisslog will prompt to update soon.

This prefix was used at WRTC but did not have a DXCC assignment in Swisslog.

This leaves the issue of existing log entries for MB calls that you worked. These, unless you made a manual entry, will not have a DXCC allocated. Some Swisslog users made a large number of MB QSOs and to avoid a lot of manual editing of your logbook, please use a solution below.

Jordi has prepared a SQL script. Download it from www.swisslogforwindows.com/Download/Fix-MB-QSO.zip

Unzip it in the SCRIPTS folder. Open Swisslog and go to Tools>For Experts Only> Execute SQL script and pick your saved file. Swisslog will execute the script and the database will refresh.

Note: Jordi would like to remind everyone that Swisslog implements a very powerful and useful function to Set DXCC from Club Log in the Tools > Club Log menu. Not only will it fix these QSOs but will probably fix many other wrong allocations.]]>
It has one new definition: MB has been added for G England. Swisslog will prompt to update soon.

This prefix was used at WRTC but did not have a DXCC assignment in Swisslog.

This leaves the issue of existing log entries for MB calls that you worked. These, unless you made a manual entry, will not have a DXCC allocated. Some Swisslog users made a large number of MB QSOs and to avoid a lot of manual editing of your logbook, please use a solution below.

Jordi has prepared a SQL script. Download it from www.swisslogforwindows.com/Download/Fix-MB-QSO.zip

Unzip it in the SCRIPTS folder. Open Swisslog and go to Tools>For Experts Only> Execute SQL script and pick your saved file. Swisslog will execute the script and the database will refresh.

Note: Jordi would like to remind everyone that Swisslog implements a very powerful and useful function to Set DXCC from Club Log in the Tools > Club Log menu. Not only will it fix these QSOs but will probably fix many other wrong allocations.]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1374 Thu, 20 Aug 2026 16:12:52 +0000 DH1PS]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1374
I have no Problems to run the Kenwood TS-990 and the ICOMs IC-705, IC-7300 and IC-9700 with Swisslog 5.118.
But with the ICOM IC-7300MK2 it is not possible to put in the right Hex-Adress B6.

See Picture below:

[attachment=634] 

All the other HAM-Radio-Applications, like UCX-Log, WSJT-X, JTDX, etc. run very well with the IC-7300MK2.

Do you have a solution for this error?

Thanks in advance]]>
I have no Problems to run the Kenwood TS-990 and the ICOMs IC-705, IC-7300 and IC-9700 with Swisslog 5.118.
But with the ICOM IC-7300MK2 it is not possible to put in the right Hex-Adress B6.

See Picture below:

[attachment=634] 

All the other HAM-Radio-Applications, like UCX-Log, WSJT-X, JTDX, etc. run very well with the IC-7300MK2.

Do you have a solution for this error?

Thanks in advance]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1372 Fri, 14 Aug 2026 11:22:34 +0000 EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1372
Definition updates are as follows:

9M4GKS and 9M4LHD = 9M6 East Malaysia

GB2CG and G5RRR = GM Scotland

G0X = GW Wales

KK7RSM = KH8 American Samoa

KG5NSU = KP2 Virgin Is

K4A, WQ2N and K1PT are KP4 Puerto Rico

VI9POL = VK Australia

VK2LHW = VK9L Lord Howe Is


Swisslog will prompt to update soon.


73 de Erik EI4KF.]]>
Definition updates are as follows:

9M4GKS and 9M4LHD = 9M6 East Malaysia

GB2CG and G5RRR = GM Scotland

G0X = GW Wales

KK7RSM = KH8 American Samoa

KG5NSU = KP2 Virgin Is

K4A, WQ2N and K1PT are KP4 Puerto Rico

VI9POL = VK Australia

VK2LHW = VK9L Lord Howe Is


Swisslog will prompt to update soon.


73 de Erik EI4KF.]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1370 Sat, 25 Jul 2026 18:40:01 +0000 EA8BPI]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1370 HE CONECTADO LA EMISORA KENWOOD TS-690S AL PROGRAMA SWISSLOG. EN PRINCIPIO TODO FUNCIONA CORRECTAMENTE. DE REPENTE UNAS VECES ANTES Y OTRAS MAS TARDE COMIENZA A PRESENTAR UN CUADRO DE DIALOGO DE ERROR: " ES UN VALOR ENTERO INCORRECTO"  Y VA SALIENDO ESTE CUADRO DE DIALOGO UNA VEZ TRAS OTRA BLOQUEANDO CUALQUIER ACTIVIDADA EN EL PROGRAMA TENIENDO QUE ACUDIR AL ADMINISTRADOR DE TAREAS DE WINDOWS PARA PODER CERRAR EL PROGRAMA.
N
  Captura de pantalla 2026-07-25 192548.png (Size: 260,05 KB / Downloads: 5) ]]> HE CONECTADO LA EMISORA KENWOOD TS-690S AL PROGRAMA SWISSLOG. EN PRINCIPIO TODO FUNCIONA CORRECTAMENTE. DE REPENTE UNAS VECES ANTES Y OTRAS MAS TARDE COMIENZA A PRESENTAR UN CUADRO DE DIALOGO DE ERROR: " ES UN VALOR ENTERO INCORRECTO"  Y VA SALIENDO ESTE CUADRO DE DIALOGO UNA VEZ TRAS OTRA BLOQUEANDO CUALQUIER ACTIVIDADA EN EL PROGRAMA TENIENDO QUE ACUDIR AL ADMINISTRADOR DE TAREAS DE WINDOWS PARA PODER CERRAR EL PROGRAMA.
N
  Captura de pantalla 2026-07-25 192548.png (Size: 260,05 KB / Downloads: 5) ]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1369 Sat, 25 Jul 2026 04:31:47 +0000 F6DKQ]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1369
So far, I have been printing my QSL cards on 10 × 15 cm card stock, which fits perfectly in my printer's lower paper tray.

Unfortunately, following our recent TM25TFR operation, I now have to deal with professionally printed standard 9 × 14 cm QSL cards.
With this size, I can only use the manual feed slot, one card at a time!  (Brother HL-L2375DW Laser printer)
Does anyone have a Swisslog QSL printing form set up for 9 × 14 cm cards, and if so, what printer/page settings do you use?

add : I think I found one : QSL9x14 A4_EA5VK.rpt  prints on my brother from the upper tray, without any mod
......but only prints a SINGLE qso......any idea to print more ...say 4 or 5 ...?
add : found how to group qso's, but only can display 3     the 10x15 format allows me 5 qso's....never mind.....

73 de Guy F6DKQ]]>
So far, I have been printing my QSL cards on 10 × 15 cm card stock, which fits perfectly in my printer's lower paper tray.

Unfortunately, following our recent TM25TFR operation, I now have to deal with professionally printed standard 9 × 14 cm QSL cards.
With this size, I can only use the manual feed slot, one card at a time!  (Brother HL-L2375DW Laser printer)
Does anyone have a Swisslog QSL printing form set up for 9 × 14 cm cards, and if so, what printer/page settings do you use?

add : I think I found one : QSL9x14 A4_EA5VK.rpt  prints on my brother from the upper tray, without any mod
......but only prints a SINGLE qso......any idea to print more ...say 4 or 5 ...?
add : found how to group qso's, but only can display 3     the 10x15 format allows me 5 qso's....never mind.....

73 de Guy F6DKQ]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1368 Fri, 24 Jul 2026 15:16:57 +0000 EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1368
Please see video at https://youtu.be/7UjtpWRsfxk

This is not an email for help as its not a Swisslog error I believe. I do wonder though if you have any idea why it happens. Its on every station called / worked on JTDX. The callsign comes to the Entry of QSOs window and then switches in and out. Nothing actually goes wrong, the callsign is logged.

Flex Radio SmartSDR software, due to the company's regressive policy toward its customers that now mean a subscription is required to get latest new features, has come under competition. A superb alternative has emerged called AetherSDR. All software that works with SmartSDR also works with AetherSDR. One of its features is that I can open a second panorama and connect to a KIWI SDR. So I can have Slice 1 locally on 21074 for example and be using JTDX and I have Slice 2 connected to a KIWI and use WSJTx to receive either same band or other band. 

Swisslog does not like this! My UDP link is only to JTDX (as far as I know) but somehow the WSJTx instance interferes. As soon as I close WSJTx or the second Slice, the problem stops. The UDP is solid and remains green.

It is not "end of the world" but I wonder if there might be a solution.

73 de Erik EI4KF]]>
Please see video at https://youtu.be/7UjtpWRsfxk

This is not an email for help as its not a Swisslog error I believe. I do wonder though if you have any idea why it happens. Its on every station called / worked on JTDX. The callsign comes to the Entry of QSOs window and then switches in and out. Nothing actually goes wrong, the callsign is logged.

Flex Radio SmartSDR software, due to the company's regressive policy toward its customers that now mean a subscription is required to get latest new features, has come under competition. A superb alternative has emerged called AetherSDR. All software that works with SmartSDR also works with AetherSDR. One of its features is that I can open a second panorama and connect to a KIWI SDR. So I can have Slice 1 locally on 21074 for example and be using JTDX and I have Slice 2 connected to a KIWI and use WSJTx to receive either same band or other band. 

Swisslog does not like this! My UDP link is only to JTDX (as far as I know) but somehow the WSJTx instance interferes. As soon as I close WSJTx or the second Slice, the problem stops. The UDP is solid and remains green.

It is not "end of the world" but I wonder if there might be a solution.

73 de Erik EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1365 Sun, 12 Jul 2026 19:49:49 +0000 EA3GCV]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1365
I have just released version 5.118 implementing VERY IMPORTANT CORRECTIONS detected in version 5.117.

Please UPGRADE when asked and read the full list of corrections HERE. 

IMPORTANT!! All users executing Swisslog as administrator will lose this setting after upgrade. Remember to set it again in the Swisslog icon to avoid undesired issues.

Best 73]]>
I have just released version 5.118 implementing VERY IMPORTANT CORRECTIONS detected in version 5.117.

Please UPGRADE when asked and read the full list of corrections HERE. 

IMPORTANT!! All users executing Swisslog as administrator will lose this setting after upgrade. Remember to set it again in the Swisslog icon to avoid undesired issues.

Best 73]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1364 Wed, 24 Jun 2026 16:40:58 +0000 JW6VDA]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1364
Tom ex JW6VDA, now OH6VDA]]>
Tom ex JW6VDA, now OH6VDA]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1363 Wed, 17 Jun 2026 07:08:34 +0000 DG7RO]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1363
when I delete some QSO in the database - here 8k QSOs - next time I start swisslog the new qso sequence number can be assigned.
This takes here hours: 10 QSOs per second!  Is there a possibility to speed up this?

Torsten, dg7ro]]>
when I delete some QSO in the database - here 8k QSOs - next time I start swisslog the new qso sequence number can be assigned.
This takes here hours: 10 QSOs per second!  Is there a possibility to speed up this?

Torsten, dg7ro]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1361 Fri, 12 Jun 2026 21:53:50 +0000 EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1361
In the update I reviewed and identified some of the UK callsigns where the licensee has elected to drop the regional identifier (GD, GI, GJ, GM etc). This is now allowable per a recent change from OFCOM.

The following definitions were added. It is by no means an exhaustive list, merely some of the most active stations.


M8TSH, M9SMC and M9WGP are all Northern Ireland, GI

M8DOI, M8HZR, M8IYV, M8LAO, M8NEG, M8SNT, M8UAT, M8XZA, M9DEL, M9SNW, M9SRU and M9STM are all Scotland, GM

M8CYE, M8ENA, M8FBB, M8PVZ, M8RBW, M9LPZ, M9MMB, M9MWZ, M9SAE and M9TGX are all Wales, GW


By far the vast majority of UK stations do wish to retain their country identity by sending the full prefix. However, should an accurate logbook be important, it is recommended that you review all UK calls worked and amend the DXCC where required.

If you encounter callsigns where Swisslog does not assign the correct DXCC, please post to this thread with the details.

73 de Erik EI4KF]]>
In the update I reviewed and identified some of the UK callsigns where the licensee has elected to drop the regional identifier (GD, GI, GJ, GM etc). This is now allowable per a recent change from OFCOM.

The following definitions were added. It is by no means an exhaustive list, merely some of the most active stations.


M8TSH, M9SMC and M9WGP are all Northern Ireland, GI

M8DOI, M8HZR, M8IYV, M8LAO, M8NEG, M8SNT, M8UAT, M8XZA, M9DEL, M9SNW, M9SRU and M9STM are all Scotland, GM

M8CYE, M8ENA, M8FBB, M8PVZ, M8RBW, M9LPZ, M9MMB, M9MWZ, M9SAE and M9TGX are all Wales, GW


By far the vast majority of UK stations do wish to retain their country identity by sending the full prefix. However, should an accurate logbook be important, it is recommended that you review all UK calls worked and amend the DXCC where required.

If you encounter callsigns where Swisslog does not assign the correct DXCC, please post to this thread with the details.

73 de Erik EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1360 Fri, 12 Jun 2026 21:47:53 +0000 EA3GCV]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1360
I have just released version 5.117 implementing VERY IMPORTANT NEWS AND CORRECTIONS.

Please UPGRADE when asked and read the full list of corrections HERE. 

IMPORTANT!! All users executing Swisslog as administrator will lose this setting after upgrade. Remember to set it again in the Swisslog icon to avoid undesired issues.

Best 73]]>
I have just released version 5.117 implementing VERY IMPORTANT NEWS AND CORRECTIONS.

Please UPGRADE when asked and read the full list of corrections HERE. 

IMPORTANT!! All users executing Swisslog as administrator will lose this setting after upgrade. Remember to set it again in the Swisslog icon to avoid undesired issues.

Best 73]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1359 Thu, 04 Jun 2026 21:08:38 +0000 EA3GCV]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1359
A new version of Trusted QSL v2.8.6 has been released. List of corrections / news can be found here.

You can download it in the Download section of the website or by clicking here.

It's VERY IMPORTANT to upgrade to the latest TQSL version to avoid issues in the LoTW synchronization!

Best 73]]>
A new version of Trusted QSL v2.8.6 has been released. List of corrections / news can be found here.

You can download it in the Download section of the website or by clicking here.

It's VERY IMPORTANT to upgrade to the latest TQSL version to avoid issues in the LoTW synchronization!

Best 73]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1358 Mon, 01 Jun 2026 14:03:06 +0000 EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1358
If I click a callsign in JTDX, in this version the call comes to the Statistic Overview window but then disappears and reappears, which has always happened before quite quickly but now is with a delay. If I click on a callsign in a DX Messages window, there is a delay before the call comes to Statistic Overview. 

The launching of Swisslog in this version takes longer than normal.

Register of QSL Cards: the window opens but is not immediately populated.

Prior to posting this report I had rebooted the computer and compacted my database to rule out extraneous factors. I also reverted to the 29 May beta and do not see this issue in that version.

I have attached a zipped video that may help visualise some of the problem.

Erik.


  SwisslV5_dDQmRbcLNh.zip (Size: 3,77 MB / Downloads: 1) ]]>
If I click a callsign in JTDX, in this version the call comes to the Statistic Overview window but then disappears and reappears, which has always happened before quite quickly but now is with a delay. If I click on a callsign in a DX Messages window, there is a delay before the call comes to Statistic Overview. 

The launching of Swisslog in this version takes longer than normal.

Register of QSL Cards: the window opens but is not immediately populated.

Prior to posting this report I had rebooted the computer and compacted my database to rule out extraneous factors. I also reverted to the 29 May beta and do not see this issue in that version.

I have attached a zipped video that may help visualise some of the problem.

Erik.


  SwisslV5_dDQmRbcLNh.zip (Size: 3,77 MB / Downloads: 1) ]]>