Date   

Re: Elecraft K4 ...

Bob
 

Mike, which one, there are dozens of them. Some as old as two years ago. I have watched a couple, without actually learning anything other that it's a 'game changer', and 'it's better than sliced bread'. I have Googled extensively, but have not found a single hit that includes K4 and CESSB or K4 and predistortion. SeventyThree(s).

On 09/06/2020 10:26 AM Michael Harris via groups.io <mike.harris=horizon.co.fk@groups.io> wrote:


See the K4 presentation on the Elecraft You tube channel.

Regards,

Mike VP8NO

On 06/09/2020 10:56, Bob wrote:
Either no-one knows, or no-one cares. OK, let's try this - Does the K4
have/support CESSB or predistortion linearization? SeventyThree(s).


Re: Elecraft K4 ...

Michael Harris
 

See the K4 presentation on the Elecraft You tube channel.

Regards,

Mike VP8NO

On 06/09/2020 10:56, Bob wrote:
Either no-one knows, or no-one cares. OK, let's try this - Does the K4 have/support CESSB or predistortion linearization? SeventyThree(s).


Re: Elecraft K4 ...

Bob
 

Either no-one knows, or no-one cares. OK, let's try this - Does the K4 have/support CESSB or predistortion linearization? SeventyThree(s).

On 09/04/2020 6:17 PM Bob <k4cy@...> wrote:


I can't help but notice that Elecraft continues to ratchet up their marketing efforts for the already over-hyped K4x model (soon to be available with a non trivial deposit, at an unknown final price, and unknown delivery date).

Bernie Madoff would be proud of them ... 

But, what do I know? They have a significant cult following, so why not exploit it? I really don't care. But, as I have an enquiring mind, does anyone know how/what the CAT interface will be? Is it as before, K3 like, or will it be a direct ethernet API driven interface? SeventyThree(s).






Re: Logger 32 quits shortly after launch

DamianM0BKV
 

Sorry, Bob, for butting in, your help is probably easier to understand. I use 400 words When 40 will do (so I'm told)

Damian


Re: Logger 32 quits shortly after launch

DamianM0BKV
 

Some users of the logging program have carried out the update and the program disappeared either immediately or at the next bootup. This has happened recently to many users because many virus checkers think the new version has a virus and instead of asking you what to do they delete the main file 'Logger32.exe' from the main folder C:// Logger32/, This problem of virus checkers treating a file as a virus is called a FALSE NEGATIVE in the plumbing trade.
I have had the problem with McAfee virus checker a while back. Numerous others have also since.

To recover the lost program you have to roll back and find an earlier version of the Logger32.exe main program file and paste it to your logger folder. Find one in one of the 10 Rollback folders stored in your 'C://Logger32/' folder in Windows Explorer. OR run Logger32Rollback.exe this looks at all subdirectories in the C://Logger32/ folders pick one and run it.


This gets Logger32 going. Then with McAfee virus checker  BEFORE updating to the new version of Logger32, paste the new version file (logger32.exe) to the exception page of McAfee firewall To do this you must again download the latest version of Logger32 that was deleted by your virus checker. Update the Firewall before doing the update. I reported the problem to the McAfee helpdesk and haven't had the problem and haven't had to do this paraphernalia since. Other virus checkers may need to be contacted about the problem. Bob, I think, has sorted it out with Microsoft and their virus checker. Don't do another update before doing the above and getting the problem sorted. Other programs may have the same issue BTW..


Re: Logger 32 quits shortly after launch

Bob
 

Steve, interesting problem. You say you have reinstalled Logger32 but you can't update. I assume you are now on version 3.50.0, and you're attempting to update to 3.50.422.

First off, check that Logger32 is configured to run with administrator privileges. Look in the \Logger32 directory for the Logger32.exe. Right click on the icon, click Properties. Select the Compatibility tab. Is the Run this program as administrator option checked?

If that doesn't help, then you could try something a little more drastic. First, make sure you have your logbook safely stored away in ADIF format. Look in the \Logger32 directory for folders called Updatefiles for ver 3.50.xxx. Copy the contents of the newest folder (I haven't counted them, but there is probably 15 files) into the \Logger32 directory. What you have done is upgrade Logger32 ver 3.50.0 to the release version prior to the one you were running on August 26.

Good luck, 73.

On 09/06/2020 5:57 AM Steve <g4uhm@...> wrote:


I have never posted to Groups.io before, so apologies if I have done this wrong...

 

I have used Logger 32 for years without serious issues but this one has stumped me.

 

I run the latest version of Win 10 64bit (kept updated) & have up to date antivirus.

 

On 26th August I clicked on the link to open Logger as usual. The program opened, loaded the logbook (about 5000 entries) and then the program closed.

 

Since then I have re-installed the program but as soon as I click ‘yes’ to updating, Logger quits.

 

The program works perfectly on my Win 10 64bit laptop, so it is something peculiar to my desktop. I hadn’t changed anything or installed any  new programmes and am out of ideas.

 

Anyone else had the same issue, if so what is the fix?

 

Any help gratefully received.

 

Steve G4UHM

 

 


Logger 32 quits shortly after launch

Steve
 

I have never posted to Groups.io before, so apologies if I have done this wrong...

 

I have used Logger 32 for years without serious issues but this one has stumped me.

 

I run the latest version of Win 10 64bit (kept updated) & have up to date antivirus.

 

On 26th August I clicked on the link to open Logger as usual. The program opened, loaded the logbook (about 5000 entries) and then the program closed.

 

Since then I have re-installed the program but as soon as I click ‘yes’ to updating, Logger quits.

 

The program works perfectly on my Win 10 64bit laptop, so it is something peculiar to my desktop. I hadn’t changed anything or installed any  new programmes and am out of ideas.

 

Anyone else had the same issue, if so what is the fix?

 

Any help gratefully received.

 

Steve G4UHM

 

 


Re: Logbook page dissappeared

Peter Eckersberger
 

Hi Bob,

Did as you suggested. Found it as "Logbook Page Index= 0". Changed it to "Logbook Page Index=0". After starting Logger32 nothing had changed. Decided to do something different. Deleted the "Logger32.INI" and started Logger32. All the basics came up. Included the Logbook page. That proved that the frog was hiding somewhere in the "INI"-file. Fortunately I've all that HAM-stuff on a second "ZBOX" which is one of those tiny mini PCs by ZOTAC
https://www.zotac.com/us/product/mini_pcs/overview. I used that in the past at my 2nd QTH and use it now for back up purposes.

Well, I copied the "Logger32.ini" from the "ZBOX" to the Logger32-folder, changed a few link-settings within the "Utility program" setup and EUREKA! I'm back to business.

Anyway, tnx a lot for giving me a hand on that matter. Wish you a nice and relaxing Sunday.

73 de Peter, OE3EPW






Avast logo

Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
www.avast.com



Re: A can of worms?

Bob
 

Graham, you are a subscriber to this lowly reflector? We're honored/humbled with your interest/presence. Your words of wisdom are appreciated.

A couple of weeks ago I was (anonymously) made aware of the ARRL/LoTW representation to the the ADIF Meisters to include FST4 as a new MFSK submode. My reply to my source is unprintable Sir, don't shoot the messenger. I call it like I see it. No hidden agenda.

The ADIF meisters decree a new submode for MFSK. So be it. Logger32 (as pathetic as it is) now accepts FST4 as an MFSK submode.

Who am I supposed to question about this very questionable mandate? Those that promulgate the directive, (or those that with their heads up their ass) that pressured (because of their totally undeserving omnipotence} you to do it?

Graham, call me out if you like, I have no problem with that, but to hide behind the wishes of the ARRL/LoTW for your decrees/mandates is not acceptable.

Once again you (and your merry men) blew it. Admit it. SeventryThree(s)







On 09/05/2020 8:35 PM Graham G3ZOD <g3zodna@...> wrote:


Save the sarcasm for the ARRL and K1JT and take it up with them if it is unsatisfactory.

"The current beta version of WSJT-X (2.3.0) includes a new mode, FST4.  ARRL has been discussing this release with K1JT, who has agreed to use "MODE=MFSK, SUBMODE=FST4" for QSOs using that new encoding scheme."

73 de  Graham G3ZOD


Re: A can of worms?

Graham G3ZOD
 

Save the sarcasm for the ARRL and K1JT and take it up with them if it is unsatisfactory.

"The current beta version of WSJT-X (2.3.0) includes a new mode, FST4.  ARRL has been discussing this release with K1JT, who has agreed to use "MODE=MFSK, SUBMODE=FST4" for QSOs using that new encoding scheme."

73 de  Graham G3ZOD


Re: Logbook page dissappeared

Bob
 

Peter, open the Logger32.INI file with NotePad (it is a simple text file). Look for the section heading

[wndLogbookPage Settings]

look for the line somewhere below it like this. 

Logbook Page Index= 0

if it is not = 0 or =0, then change it to =0 save the change, and load Logger32 again. Any change? 73.

On 09/05/2020 12:42 PM Peter Eckersberger <oe3epw@...> wrote:


Hi Bob,
Thank you for your quick response. But unfortunately your advise was the very first action done by myself. Didn't help at all. Here again the pics of my actions ...


1. When starting Logger32 I see this one ...



Pse take to your knowledge that the loading of the logbook is incomplete.


By clicking several times onto "OK" the logbook gets loaded but stays invisible. As soon as I click onto the black "DATE"-column it does not turn into red but that lousy "TEN_TEN" message shows up again.



Sorry, here I'm. I've no idea what to do. What hurts most is the fact that I can't use the fantastic "Cherry Picker" option together with the direct logging of JTDX & WSJTX Q's into "Logger32". This combo is really something special. Thanks a lot for your effort in providing the whole community wits all those candies.


73 de Peter, OE3EPW


Am 05.09.2020 um 16:54 schrieb Bob:
Make sure the selected column to sort the Logbook Page Window is the QSO DATE column. Click on it and it will be in red. 73.


On 09/05/2020 9:37 AM Peter Eckersberger <oe3epw@...> wrote:


Hello,

Name is Peter, call OE3EPW

Today something strange (at least for me) happened when trying to reduce the size of my Logger32 logbook page. After doing so all of a sudden the "1" error text popped up (see below).



When clicking on "OK", number "2" came up. Clicking here on "OK" shifts me to a loop between those 2 messages. After the fourth "OK" the messages disappear, Logger32 gets started but only one empty line of the logbook is visible. When ever trying bringing back the page to its normal size (in my case 12 lines) the whole procedure starts again from the beginning.


Additional info ...

1. I never had implemented the TEN_TEN field in my logbook setup / grid layout. It's still not there right now.

2. I tried to help myself by replacing all of the different "INI"-files stored within my LOGGER32BACKUP.ZIP to no avail. Some helpful advise what to do for bringing back normal functionality? TIA!!


73 de Peter, OE3EPW
<oe3epw@...>




Avast logo

Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
www.avast.com




Re: Logbook page dissappeared

Peter Eckersberger
 

Hi Bob,
Thank you for your quick response. But unfortunately your advise was the very first action done by myself. Didn't help at all. Here again the pics of my actions ...


1. When starting Logger32 I see this one ...



Pse take to your knowledge that the loading of the logbook is incomplete.


By clicking several times onto "OK" the logbook gets loaded but stays invisible. As soon as I click onto the black "DATE"-column it does not turn into red but that lousy "TEN_TEN" message shows up again.



Sorry, here I'm. I've no idea what to do. What hurts most is the fact that I can't use the fantastic "Cherry Picker" option together with the direct logging of JTDX & WSJTX Q's into "Logger32". This combo is really something special. Thanks a lot for your effort in providing the whole community wits all those candies.


73 de Peter, OE3EPW


Am 05.09.2020 um 16:54 schrieb Bob:

Make sure the selected column to sort the Logbook Page Window is the QSO DATE column. Click on it and it will be in red. 73.


On 09/05/2020 9:37 AM Peter Eckersberger <oe3epw@...> wrote:


Hello,

Name is Peter, call OE3EPW

Today something strange (at least for me) happened when trying to reduce the size of my Logger32 logbook page. After doing so all of a sudden the "1" error text popped up (see below).



When clicking on "OK", number "2" came up. Clicking here on "OK" shifts me to a loop between those 2 messages. After the fourth "OK" the messages disappear, Logger32 gets started but only one empty line of the logbook is visible. When ever trying bringing back the page to its normal size (in my case 12 lines) the whole procedure starts again from the beginning.


Additional info ...

1. I never had implemented the TEN_TEN field in my logbook setup / grid layout. It's still not there right now.

2. I tried to help myself by replacing all of the different "INI"-files stored within my LOGGER32BACKUP.ZIP to no avail. Some helpful advise what to do for bringing back normal functionality? TIA!!


73 de Peter, OE3EPW
<oe3epw@...>




Avast logo

Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
www.avast.com




Re: Logbook page dissappeared

Bob
 

Make sure the selected column to sort the Logbook Page Window is the QSO DATE column. Click on it and it will be in red. 73.


On 09/05/2020 9:37 AM Peter Eckersberger <oe3epw@...> wrote:


Hello,

Name is Peter, call OE3EPW

Today something strange (at least for me) happened when trying to reduce the size of my Logger32 logbook page. After doing so all of a sudden the "1" error text popped up (see below).



When clicking on "OK", number "2" came up. Clicking here on "OK" shifts me to a loop between those 2 messages. After the fourth "OK" the messages disappear, Logger32 gets started but only one empty line of the logbook is visible. When ever trying bringing back the page to its normal size (in my case 12 lines) the whole procedure starts again from the beginning.


Additional info ...

1. I never had implemented the TEN_TEN field in my logbook setup / grid layout. It's still not there right now.

2. I tried to help myself by replacing all of the different "INI"-files stored within my LOGGER32BACKUP.ZIP to no avail. Some helpful advise what to do for bringing back normal functionality? TIA!!


73 de Peter, OE3EPW
<oe3epw@...>




Avast logo

Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
www.avast.com



Logbook page dissappeared

Peter Eckersberger
 

Hello,

Name is Peter, call OE3EPW

Today something strange (at least for me) happened when trying to reduce the size of my Logger32 logbook page. After doing so all of a sudden the "1" error text popped up (see below).



When clicking on "OK", number "2" came up. Clicking here on "OK" shifts me to a loop between those 2 messages. After the fourth "OK" the messages disappear, Logger32 gets started but only one empty line of the logbook is visible. When ever trying bringing back the page to its normal size (in my case 12 lines) the whole procedure starts again from the beginning.


Additional info ...

1. I never had implemented the TEN_TEN field in my logbook setup / grid layout. It's still not there right now.

2. I tried to help myself by replacing all of the different "INI"-files stored within my LOGGER32BACKUP.ZIP to no avail. Some helpful advise what to do for bringing back normal functionality? TIA!!


73 de Peter, OE3EPW
<oe3epw@...>




Avast logo

Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
www.avast.com



Re: A can of worms?

Rick Ellison
 

It is being beta tested for an upcoming release of WSJTX.

73 Rick N2AMG

-----Original Message-----
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of KX2A
Sent: Friday, September 4, 2020 4:11 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] A can of worms?

Bob,

Sounds interesting to me. I would love to find out more about FSTing.

73,

Jan, KX2A





--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: A can of worms?

Mike
 

On Fri, Sep 4, 2020 at 10:10 PM, KX2A wrote:
Sounds interesting to me.  I would love to find out more about FSTing.
As google claims that lotsa lube is needed and goes smooth.
Mike


Re: Cherry picking

Bob
 

Was this helpful, did it address your query, or did I just waste the oxygen/bandwidth? SeventyThree(s).

On 09/02/2020 9:35 AM Bob <k4cy@...> wrote:


Steve, on the UDP BandMap. click CONFIG | CHERRY-PICKING OPTIONS. Two things to do here. Check CHERRY_PICK HIGHEST PRIORITY FIRST and UNcheck ENABLE SYMPATHY CALLS TO STATIONS CALLING CQ.  Now click CONFIG | APPEARACE | HIGHLIGHT & TEXT COLORS. UNcheck all Gridsquare options. Click APPLY. The Cherry-picker will now only call highlighted callsigns on the UDP BandMap. Right click on the DX Spots Window. Click SETUP | APPEARANCE | DX SPOT HIGHLIGHT COLORS. Here you design your own personal LGBTQ flag. Click APPLY. SeventyThree(s).

PS. There are several additional options that allow you to see only highlighted callsigns on the UDP BandMap, or only those not previously worked. The choice is yours.
On 09/02/2020 12:45 AM Steve G1XOW <steve@...> wrote:


Is there a way to configure cherry picking to ONLY pick new countries?  ....and not squares!

73 from Steve G1XOW
Life is complex - it has a real part and an imaginary part!



Elecraft K4 ...

Bob
 

I can't help but notice that Elecraft continues to ratchet up their marketing efforts for the already over-hyped K4x model (soon to be available with a non trivial deposit, at an unknown final price, and unknown delivery date).

Bernie Madoff would be proud of them ... 

But, what do I know? They have a significant cult following, so why not exploit it? I really don't care. But, as I have an enquiring mind, does anyone know how/what the CAT interface will be? Is it as before, K3 like, or will it be a direct ethernet API driven interface? SeventyThree(s).






Re: A can of worms?

KX2A
 

Bob,

Sounds interesting to me.  I would love to find out more about FSTing.

73,

Jan, KX2A


Re: Updatefiles not found by the Rollback command

Bob
 

Raymond, do it the easy way. Delete all the Updatefiles for Ver 3.50.xxx folders except the five newest ones. 73.

On 09/04/2020 11:12 AM F4FNT via groups.io <f4fnt@...> wrote:


Thank you Bob for your answer. But I’m still trying to find out which setup I need to change. I’ve looked at the authorizations to various  .exe files located in the c:\Loggeer32 folder: Logger32rollback.exe, autoinstaller.exe, Logger32autoinstaller.exe, but no success….


My current Logger32 version is 3.50.422. The existing Updatefiles for ver…. go from 3.50.334 to 3.50.420 (19 folders). My Logger32 is Always launched as  administrator, as recommended and I haven’t seen any Antivirus issue, although I’m using Norton.


Some ideas on the setup parameters I should investigate ?

Thank you

Raymond, FFNT


Provenance : Courrier pour Windows 10


2501 - 2520 of 83544