Working closely with technology for an extended period of time has colored my views on computing. I’ve gone from full-on, build it all myself or die to using whatever works reliably and jettisoning anything that fails. I can trace the completion of that transition to the point where I had a little baby boy to care for and no more time in my day for compiling things or tweaking hardware.
That was 13 or so years ago. Since that time, I’ve kept myself mostly in the default use cases covered by MacOS and iOS. Why? Because it works for me 99.999% of the time. I don’t ever find myself having issues that other people hit. Part of this, I believe, is because I understand the use cases. The applications I use are good for what they do and I expect little else from them. That is to say, I have an application for my notetaking and journaling. I have one for music making and editing audio. I have one for browsing. I have one for mail…OK…that’s a lie. I go through mail clients like most people go through shows on Netflix. I hate all email clients for different reasons. They all suck. All of them. Even the one you love. It’s horrible and I can tell you why. At length. You will regret asking.
Anyway, I try to stick to applications that do what I need done and use them for their strengths. I do take the time to give them the respect of learning their primary use cases so that my expectations are in the right place. You won’t catch me keeping an address book in a spreasheet program, for instance. That said, if an addressbook app loses one piece of my data? It’s gone. And I won’t look back. To my mind, the app’s failure is complete and that I do not forgive.
When I started messing around with Ham Radio software, I learned quickly that the vast majority of it was built for Windows. I’ve made a lot of money in my lifetime developing software in Microsoft’s ecosystem, so it’s a stretch for me to complain too loudly. I will simply say that I don’t do Windows at home because of the poor driver support and the endless interventions required on my part to keep things running. This is no less true in the radio sphere as there is always a driver to install for any given cable or device. It’s a disappointment in 2020 that manufacturers can’t read a spec and provide a device that meets it without imposing on the user to add software to their systems. But I digress.
About 2 years ago, I purchased a WinBook TW110 at Microcenter. It has an Atom processor, a touch screen, and is a weird little multi-form-factor device. It also runs Windows 10 and weighs almost nothing with a pretty impressive battery life. I set it up with WSJT-X and some logging software and off I went. I used it primarily to program my radios as there is no Mac software for that outside of CHIRP and not every rig I have likes CHIRP. But then we hit that moment that I hit with every Windows tablet: I ran out of space to update Windows.
This hits me like clockwork. I’ve had some really cool tablets that did really well for my limited use cases that eventually hit this wall. My HP tablet for instance, had a single USB port that was also used to charge the unit. I needed to use a USB stick to hold the updates. The update took longer than the battery could survive. I tried a USB hub to no avail. Finally, it ended up in the parts drawer waiting for me to use the screen for something at a later date.
The real disappointment with the WinBook was that it is really, really lightweight and it charges off of a USB port with 5 volts in a pinch. It’s ideal for FT8 in the field. Having it fail like this made me sad. So my little WinBook was destined for a life as maybe a clock that showed timezones and the position of the sun or sattelites or something. But in the back of my head a voice said, “Just throw Linux on it. If it fails, the worst case is you reload Windows 10 and maybe have enough space.” So I grabbed a Mint image and it worked first shot.
Side note: I used Debian for YEARS. It was my OS of choice for everything and I was intimately familiar with every part of the system. I wrote device drivers for sound cards and had a lot of fun playing with it and learning how it worked. Note that all of that is past tense.
Naturally, the touchpad isn’t supported, but a Bluetooth mouse and a functional touchscreen mitigate that. The battery life is really good. And behold! The entire OS doesn’t really make a dent in the 32 GB of internal storage that this little beast has available. This might work!
Naturally, the current stable version of FT8 doesn’t have the IC-705 in it yet and thus requires spoofing as an IC-7300. The 705 is in the first release candidate for the next version. Which I’ll have to compile from source on this distro. Which will require some time to get dependencies in a row. Which…takes me back…to why I don’t do this anymore.
That said, maybe it’s time. My kids are fully functional and mostly self-sustaining on the weekends and after bedtime. Maybe I do have time a little time to wrestle with this and see if I remember anything from those long nights of compiling entire distributions from source so I could run a new soundcard. It could be that I might even have fun doing it. If I do get this WinBook working for FT8, I know that my back will thank me and my field operations will be easier and last longer.
This feeds my thesis that Ham Radio is the Old Magick and it will take its adherents back to the beginning of all things, in time.