I’m in the middle of rebuilding my PC and do not have any radio programs installed yet. In the Lookup Turn Debug on and you will get the same print out in the debuglog.txt file. Got bite by another

There was a bug fix in version 3.50.381 that specifically addresses this problem. It appears there is more work needed. I can not duplicate the problem which is going to make it difficult to fix, so

I am having a difficulty with the l32lookup utility under certain conditions in L32. 1. L32 set to use external lookup, Most recent lookup and update installed. Not using the internal lookup

Did I miss something? L32 supports OMNI-Rig now? I’ve been wanting this feature for ages. I’ll have a “play” later today. 73’ Pete, N5KD.

I have a great deal of difficulty believing that Logger32 is smart enough to know that COM1 is assigned to CAT control in N1MM or WSJT when N1MM and WSJT are not running. I suspect there's something

Thanks for your help. I will try this, but leaning towards N1MM program. Thanks ka5het -- Steve McDonald

All the CAT failures with my FT1000mp and Logger32 have come down the the selected COM port not being available. Usually this was because it was also assigned to N1MM or WSJTX even though they were

You could try SETUP | FREQUENCY and check the option to SHOW FREQUENCY DISPLAY & LOG FREQUENCY. SeventyThree(s).

I have my FT1000MP working properly with Logger32, on my desktop running Win10. And in the past I also had it working properly when I was running Win 7. I have acquired an older laptop which is

On behalf of all those involved in the Logger32 project. Many thanks, and thanks to all who have commented. Now please consider this thread closed. SeventyThree(s).

Tks to all developers of this excellent logger program. Logger32 is the best I always used. If my rig doesn't works with logger32 I sure change the rig and never change the L32. Really great. Tks.

On the PC that fails to show the cursor in/on the Callsign field after F11 - After the F11, type on the keyboard. Do the typed characters show in the Callsign field? SeventyThree(s).

I have checked the code. If the Data Window is closed and the Sound Card Data Window is closed and the DVK Window is closed and the Radio Control Panel is closed then the Logbook Entry Window is

Thanks for that info. Like I said I always use ALT+W Dave N8DC 73

Hi Dave, Yes I forgot to mention that alt+w works fine. Just not been in the habit of using it until recently. Regards, Mike VP8NO

I tend to use Ctrl+C for this with no problems. Dave, with the RCP open F11 corresponds to one of the macro buttons. John G7SSE

F-11 doesnt work for me . May be a setup deal but I have always used alt+W and the cursor stays no problemo . Dave N8DC

G'day all, I've noticed lately that if I enter a call in the logbook entry window call field and subsequently clear it with F11 without logging, the flashing cursor vanishes just leaving the call

Here I tried to suck up about a week ago and Bob gave me a rash of crap ;). Its all good though . All you guys like me that just love this program and have nothing good to say about it just remember

Hi all According to qrz.com, it seems I am using logger32. ;) Thanks Bob & team 73 Jose EA4AFP