Noted thanks. Will take it up with Alex. Regards, Mike VP8NO

Hi, Win10/64 Pro, L32 4.0.294 I thought I had worked around the problem of the fatal interaction when L32 launches Ham CAP. Ham CAP will populate the screen with the map with a white background and th

Will forward info next time it happens. Regards, Mike VP8NO

Join the club. I regularly see this and indeed also for USA and JA stations. All I do is edit the LoTW report in Notepad by deleting any reference to STATE or county or whatever is causing the nausea,

NCDXF beacons map, splendid. My your FG never run out. Win10/64 Pro updated last night. No issues using CW machine, albeit software only no WinKey. Regards, Mike VP8NO

Hi, I look forward to it. Regards, Mike VP8NO

Further to my first email. NCDXF also lists the beacon at CP38gh Inuvik NT Regards, Mike VP8NO

Hi, The beacon is incorrectly located on the L32 NCDXF beacons map. From the Northern Alberta Radio Club web site: <snip> The beacon was destined to be installed at CFS Alert, at the northern tip of E

Agreed. When I'm backing up my log to the Netbook PC it is much quicker to just throw the whole log at it than it is to delete the old one and reinstall. That way I also get the updated confirmations.

John, Do you launch HamCap stand alone or from the button in L32? I've not had any problems with stand alone. Launching with L32 has the advantage of passing log window call sign entry data and automa

Are we perhaps thinking of the "log entry pane"? If so then from the menu View > Show Logbook Entry, the sixth choice in the drop down list. To which page 130 of the help file details. Regards, Mike V

Thank you. Regards, Mike VP8NO

Backup is currently every 5 QSOs and there may be a link here. The last failure was at the time of logging STX 065 and subsequently backing up, appending maybe, the 39,000 lines of log detail. The "pr

Hi, Win10/64 Pro, L32 v.290 This has happened three time in the past 24 hours. S&P in the CQ WPX RTTY contest running MMTTY along with 2Tone. All the failures have happened immediately upon logging a

I wonder if anyone else has an issue with launching Ham Cap from within L32? I have been using Ham Cap for quite a few years now in conjunction with Iono Probe which passes the latest 90 day averaged

Good news John, thanks for putting your hand up. Too many raise a big fuss about something, get loads of advice and then vanish leaving everyone in the dark as to the cause and cure. Regards, Mike VP8

John, What is the setting for your Time Format? Mine is 53:59. The time regularly shows start and finish as the same with say a snappy CW exchange or FT8. You can test this by entering a dummy call in

Talisker for me. The peat smoke aroma reminds me of Stanley when I passed through 47 years ago on my way to Antarctica when most houses had peat fuelled Rayburn cookers. Also, my wife has Isle of Skye

I see that a lot. Just look at the BAD.ADI report and using something like notepad delete the CNTY data, save it as is, copy and rename to something like NEW.adi and offer it to L32. I certainly don't

I've got 34000 Q and no problems. 12y old PC, Win 10/64 Pro. Been running FT8 wsjtx, UDP bandmap, auto logging. No Worked/Confirmed window. Not needed at the sharp end. Regards, Mike VP8NO