开云体育

I have searched the Hamlogger messages, the Logger32 manual, the FTdx10 manual, the FTdx10 Google Group, multiple Google searches, watched several YouTube videos . . . and I'm stumped.? I'm trying to

Halten Sie nicht den Atem an und warten Sie auf Ver?nderungen DJ0AW

Jan, it's not that tragic. Let's see what happens and Bob takes care of my mini problem, hi! Thanks for the chat, 73 all the best Günter DL3XM

Yes, I'm an old bone and still keep a paper log at the same time! It happens from time to time with the time correction!

Günter I see what you mean. This was in the relaese notes: /Version 4.0.328// //Fixes a comma decimal separator bug when logging QSOs after midnight /So that solution for some hams made it worse for

Hi Jan, That's right! But if I have to change the time afterwards, then it gets awkward! That's actually my mini problem, hi! That's why I would like to have the setting like in 325 back! There it is

Günter If you choose 23:59:59 and don't use the show seconds you will have the time as 23:59 like the one you where using before the update 73 Jan PA4JJ Op 12-11-2024 om 09:26 schreef Guenter, DL3XM

Hello friends, I miss the old setting from version 325 for the time format in the new version 329. See the attached pictures. Would this setting be possible again in the current version? This

If you use the point with Windows, then Logprint must also use the point If you use the comma with Windows, then Logprint must also use the comma F5SZY / Yves

Try this. if you use the comma as decimal separator, then change for the point. To do this, go to Windows settings My windows is configured with the point and in my logprint.ini file I use the point.

Looking for some help with LogPrint error. Any time I preview any changes to the Label Setup I get a Run-time error as in the attachment. Thanks in advance.

QSL § TU De : [email protected] <[email protected]> De la part de Bob via groups.io Envoyé : lundi 11 novembre 2024 11:28 ? : [email protected] Objet : Re: [hamlogger] QSO not accoounted for

SeventyThree(s).

Paul, if that qso was via QO-100 I think it should not show under 13cm in the Worked/Confirmed Table but appear in the SAT row I mentioned earlier. To quote Gary from the help file; "Give your QO-100

For terrestrial 13cm statistics, look at the DXCC-MIXED award. For 13cm satellite contacts look at the DXCC-SATELLITE award. We have been over this again and again. One more time, I will send you

On the DXCC awards window, select the DXCC_SATELLITE option. SeventyThree(s).

Well, that's what I wuld like to know , but I know the 1 that shows on 13cm is wrong ! De : [email protected] <[email protected]> De la part de Paul F6EXV via groups.io Envoyé : lundi 11 novembre

John I guess I must look into that more deeply, thank you 73 Paul De : [email protected] <[email protected]> De la part de John Munton - G7SSE via groups.io Envoyé : lundi 11 novembre 2024 10:15

How many countries worked/confirmed on satellite De : [email protected] <[email protected]> De la part de Bob via groups.io Envoyé : lundi 11 novembre 2024 10:41 ? : [email protected] Objet :

What stats are you referring to? SeventyThree(s).