There’s a beefy blog piece on Superbase. Looks a bit too complicated for a simple QSO DB stored to disk or tape.
Maybe even a BASIC program could do the job but would probably be very slow to import a large ADI and also for lookups.
Worth investigating though. Perhaps a clever person has written something more recently that might be super fast. Sure C64 software is still being written today. The computer that will never die! 
Recently I found a TRS-80 Model 100 in a storage closet at my work…go look it up, I will wait 
Amazingly it still works great, and is very easy to program in Basic. I wrote a simple SOTA logging program for it - it saves the entered log in a text file in FLE format. After you are done logging you just connect the M100 to another computer via null modem (serial) cable, fire up the built-in Terminal program, and send the file.
The M100 has a fantastic keyboad, runs for 24 hours on a couple of AA cells, and the display is pretty good. For a computer from the 80’s, it is amazingly usable in 2026. One of these days I will take it out on a summit and try to make a YouTube video about it.
On my to-do list is to use something like an ESP32 that would interface to the M100 via serial and allow me to leverage the WiFi and processing power of the ESP32 to do cool stuff… like a text interface to SOTAData so I can use it like it’s a BBS from the 80’s.
I still have my Atari ST that ran a packet thingy in the early 90’s . I Still have the PK88 controller somewhere too.
Also in the collection a C64 and BBC micro (or 4) which could do CW and SSTV as well as various other 8bit computer of the age which mainly had morse trainer programs and the like (not that I used any of them 
).
I think even the zx81 had a RTTY decoder at some point with the sound injecting from the cassette tape interface. I assume transmit was done the same way (but in reverse).
Ian
Connect it to a Cardputer or an M5Stick C 3.
Disco.
C64 SSTV!? 
Oh yeah, I also wrote a simple Morse trainer for the M100 too. It uses the built in speaker to send code, then waits for you to enter the word it sent you. The words it sends come from a text file (the M100 has a built-in text editor that is decent) and will randomize the order it sends to you. Interesting factoid: Bill Gates wrote all the software for the M100.
That would work, but I was going to make something very small that could stay plugged in to the M100. I already have some tiny ICs that do the TTL/CMOS logic level shift, so that isn’t a problem.
Will have to wait until next winter because the WX is getting good here finally, and I’d rather be outside hiking and playing radio.
I had a very quick attempt at a BASIC QSO logger. It crashes after date entry though. Y2K?
10 CL$=CHR$(147):W$=CHR$(5):U$=CHR$(95)
20 PRINT CL$;W$;"*** C64 ADIF QSO LOGGER ***"
30 OPEN 15,8,15
40 PRINT "ENTER FILENAME (E.G. LOG.ADI)"
50 INPUT F$
60 PRINT "1. ADD NEW QSO"
70 PRINT "2. VIEW LOG FILE"
80 PRINT "3. EXIT"
90 INPUT "CHOICE";C
100 IF C=1 THEN GOSUB 1000:GOTO 60
110 IF C=2 THEN GOSUB 2000:GOTO 60
120 CLOSE 15:END
1000 PRINT CL$;"--- NEW QSO ENTRY ---"
1010 INPUT "CALLSIGN";CA$
1020 INPUT "DATE (DDMMYYYY)";DA$
1030 IF LEN(DA$)<>8 THEN PRINT "BAD DATE FORMAT":RETURN
1040 INPUT "TIME (HHMM)";TI$
1050 INPUT "BAND";BA$
1060 INPUT "MODE";MO$
1070 INPUT "RST SENT";RS$
1080 OPEN 2,8,2,F$+",S,A"
1090 GOSUB 3000:IF ER>0 AND ER<>62 THEN PRINT "DISK ERROR":CLOSE 2:RETURN
1100 REM --- WRITE DATA USING SAFE SUBROUTINE ---
1110 V$=CA$:GOSUB 4000:PRINT#2,"<CALL:";L$;">";V$;
1120 L$="8":PRINT#2,"<QSO";U$;"DATE:";L$;">";MID$(DA$,5,4);MID$(DA$,3,2);MID$(DA$,1,2);
1130 V$=TI$:GOSUB 4000:PRINT#2,"<TIME";U$;"ON:";L$;">";V$;
1140 V$=BA$:GOSUB 4000:PRINT#2,"<BAND:";L$;">";V$;
1150 V$=MO$:GOSUB 4000:PRINT#2,"<MODE:";L$;">";V$;
1160 V$=RS$:GOSUB 4000:PRINT#2,"<RST";U$;"SENT:";L$;">";V$;
1170 PRINT#2," <EOR>"
1180 CLOSE 2:PRINT "RECORD SAVED.":RETURN
2000 OPEN 2,8,2,F$+",S,R"
2010 GOSUB 3000:IF ER<>0 THEN PRINT "FILE NOT FOUND":RETURN
2020 PRINT CL$;"--- LOG ENTRIES ---"
2030 GET#2,A$:IF ST<>0 THEN 2060
2040 PRINT A$;
2050 GOTO 2030
2060 CLOSE 2:PRINT:INPUT "PRESS ENTER";X$:RETURN
3000 INPUT#15,ER,EM$,ET,ES:RETURN
4000 REM --- SAFE LENGTH TO STRING CONVERSION ---
4010 N=LEN(V$):IF N=0 THEN L$="0":RETURN
4020 S$=STR$(N):L$="":FOR I=1 TO LEN(S$)
4030 T$=MID$(S$,I,1):IF T$<>" " THEN L$=L$+T$
4040 NEXT I:RETURN
PRINT statements aside it’s mostly vibe coded just to see what would be thrown up then try to fix it.
The idea is to save to an ADI and import from disk after it is saved.
Not an expert on the C64 but a quick look through the open command suggest the format should be
OPEN 2, 8,2, F$+“,SEQ,R”*
open sequential file for reading*
OPEN 2, 8,2, F$+“,SEQ,W”
open sequential file for writing
SO a modification of line 1080 to
1080 OPEN 2,8,2,F$+“,S,W”
may solve that issue.
EDIT: I think I found the A mode too (for Append - cos they named things properly back then) , so that isnt it. I think I got confused from the flashbacks on seeing 1980’s basic code on screen
I have mine from 1985, still working but there two lines of pixels that are dead, probably a connection issue. As you say runs forever on AA cells and the keyboard is sublime. Mine needs a good burst of typing to clean up the contacts. But the feel is so good. Not too heavy either. I used it as a terminal and had a whole raft of RS-232 cables for it. I made good money sorting out RS-232 handshaking issues back in the 80s. Oh the memories of dealing with Qume, Juki and Diablo daisywheels and the fun of ageing CP/M 80 and PIP.COM. It was always upper case, who remembers things like PIP LST:=MYDOC.PRN and forgetting to type a ctrl-C when changing disk. That and MS-DOS 1.25 on a Sirius. The TRS80 100 made it easy to test everything. The case has gone an interesting yellow colour. There are some on eBay the same colour. Wow £150 asking price!!! I need to get it sold and spend the money on hookers and drugs!
A real trip down memory lane with all those pre-PC microcomputers. I was a big fan of the Nascom II, a Z80A system that came with a whopping 16k bytes of dynamic RAM. It had interpreter Basic but for anything other than dead simple stuff that was far too slow, so I did most of my coding in Z80 Assembler, which worked very well.
I wrote my first sunrise/sunset and great circle distance code in Z80 Assembler some time in the early 80s. Later I ported it to Pascal, still on the Z80 and that eventually ended up running on a PC under Borland Pascal, then Delphi. Just a few months ago I was looking at that code that I wrote 40-odd years ago thinking that I really should rewrite it in the modern coding style. But, ya know what… it’s still working a treat in my homebrew logging program. It ain’t broke, so in the end I decided not to fix it.
I did some Z80 asm coding, and 6502 back in the day. Been a LONG time since I looked at any of that stuff!
Man, we really went off on a tangent here!
I had one of them with the memory expansion board that had memory plague. That was when the SRAM for the main board became unobtanium, much like DDR5 now! Nascom gave away a 16K DRAM board. But being Nascom it lacked decoupling and the power rails where just the right lengths and thickness to cause much ringing and such nonsense and make them very unreliable. Mine need several buckets of 10uF electrolytics, 100nF and 10nF plastering everywhere and 16SWG copper wire soldering on top of the power lines. I could have 32K working at 4MHz and 1 waitstate or 2MHz and no waitstates. I also found some of the 2K SRAMs later and had 40K of memory. The keyboard had an amazing feel too.
My code was first written in the mid-90s in Zortech C for x86. The same code was careful crafted into C# for the SOTA database in 2010 - 2012. Andrew converted it from “Dino-crap language” into Rust I think recently for the SOTA DB API. Added to the DB codebase at the same time as adding Maidenhead locator to/from lat&long.
I feeling quite pleased today… some Windows 11 horror-show code I’ve been faffing with on and off over the last 18 months sort of started working today after I found a away to clean out installed device drivers. It’s all so simple on *nix derived OS. But maybe I’ll finish it before I retire. Anyway I was so pleased I decided to complete my move to the darkside and order a Mac Neo 512GB but they’re all on at least 5 week lead times. Should have bought it when I first saw it. I only want one because it’s supremely shiny.
We are buying boatloads of them here. By far the best $500 USD (we get EDU discount) computer available. I think Apple just shat upon the Chromebook market 
I played with a Neo last week in the Apple store in Edinburgh. Last Mac I used was a G3 iMac in Apple’s reception in Cupertino in 2003 when I did some work with their iPad team. It was hard to accept just how swish everything ran for a damn phone processor running a full laptop!
I’ve been laughing myself silly at the “influencer reviews” on Youtube. “Oh it’s only got 8GB of RAM so you will need to …” These youngsters haven’t got a clue. We ran 48+ simultaneous terminal sessions on our Prime 750 with only 4MW of core and 500MB of washing machine sized disks in 1980 and we thought it was a snappy multiuser system.
I have a 5.5year old Dell 7490 laptop here (i7 8650U, 16G/256G) and the battery is still good for 6hrs. I run Debian 13 and it’s brilliant for what I need a laptop for. Bit of SQL console work, email, browsing , walking maps and GPS admin when away from home. It works so well considering it cost about $275US refurbished 2.5 years back. I could do all of that and run my walking maps software natively on a Neo instead of having a (spit) Win10 VM running now. And the battery would give me 16hrs. Not sure about a Yellow one or Silver. Compared to what Windows pish you get in the UK for same money, it’s an absolute no brainer. So much so I may just buy one for Mrs. LLD and me. Then I’ll have no keeping Windows working admin pish to deal with.
I would not like to be a Chromebook or bottom end Windows laptop maker because the only reason they’re still selling product is there are no Neos to buy. If Apple drop the price and accept a lower profit margin, in exchange for market share, then some x86 laptop makers will have zero market to sell into 
I mean I had Chromium fired up for a work thing and looked at the output from top and it had allocated 1.4TB (yes, terabytes) of virtual memory and had a good 6-7GB of that resident in memory at any point in time. So, yeah, 8G isn’t going to be enough for the vibe coded crap coming down the pipe but I do miss the days of a 32K BBC Micro
I got one about then, too. Remember having to add so many capacitors. Later updated it to 64k. Once I got tired of basic I played quite a bit with ZEAP to get the beast to do things…
…I use Winlog32 on windows10 for all my logging. Never used qrz log.I am looking for a logger to use with Linux OS as I over using Microsoft o/s (anything); any advice/ suggestion are welcome.
Geoff vk3sq
I tried QLog once and it seemed good. Google would suggest that CQRLog is ‘the worlds best’ 
98% of my QSOs are SOTA, and I log them via SOTAWatch. For other random QSOs, I do actually use the QRZ log book. When I ‘hunt’ POTA, I don’t log anything… the POTA op does that for me!
I have qrz.com as one of my standard page tabs in my browser, and it has been fine - no problems here - is the problem perhaps with the api used by programs to connect to it, or just the logbook function (which I don’t use)? The standard type-in callsign and hitting the search button on the website is working fine here today and was also fine yesterday.
73 Ed.
Oh yes.