Retro Fix: A Purgatory of TRS-80 Model 1 Repairs

As I've mentioned before, one of my favorite pastimes is vintage computing. I take particular interest in early connect-to-TV 8 bit microcomputers (including the short-lived Mattel Aquarius, for which I recently developed an extremely thorough, free modern online visual designer to assist fellow Aquarius artists and developers).

And while I'm mostly a software guy, the aging nature of these vintage electronics leads to inevitable hardware faults and necessary maintenance, therefore it is still vital to be skillful on the hardware side as well. I recently wrapped up the most strenuous restoration project to date — an original TRS-80 Model I computer from 1977 with all the bells and whistles from that era. I don't usually document or write about my repair projects or 8-bit endeavors since I do it purely for the fun of it and personal enjoyment, but this was such a long and convoluted journey of highs and lows that I figured I should write a blog while aspects of it are still fresh in my mind. There are a lot of resources for TRS-80 computers out there already, but perhaps my shared experience will be of value or help to others trying to diagnose their own sets. If you have any questions, please feel free to ask in the comments. Read Full Article

Coffee Break DIY: 4.5V Battery Replacement for Old CMOS Batteries

As a hobby, I do a lot of vintage electronics restoration and discovery. Due to time-constraints I rarely find the chance to document any such efforts, which has included everything from restoring a 1950s television set to factory new condition, to repairing old oscilloscopes and making them sing songs. But my main passion remains on retro computer systems, from the 1970s through 1990s. This past year I even developed an extraordinarily comprehensive online design tool called Aquarius Draw for the failed 8-bit Mattel Aquarius computer, which allows designing art and generating necessary code in BASIC and Z80 Assembly for transferring to the actual machine (talented users have made use of it as seen in the gallery).

But every so often I take a few photos of simple projects and figure it doesn't hurt to make a quick blog about it. Here's a fast DIY solution to replacing an old and depleted CMOS battery for a recently acquired Macintosh Performance 5400/180 computer using only random parts laying around. Read Full Article

Dual Boot Windows 11 and Windows XP in 2021: A Descent Into Madness

Years ago, I wrote a couple of guides on how to retain a fully functional Windows XP (32-Bit) and Windows 10 (64-Bit) on modern hardware, including integration into the then-latest NVIDIA Geforce 900-series cards, solid-state SATA drives and so on. Both of these articles proved much more popular than I ever imagined, given the increasing obscurity of their practical usefulness. My article about NVIDIA cards and XP, in particular, became heavily linked around the Internet and across many forum discussion threads from other XP diehards.

Now, in the year 2021 and on the cusp of Windows 11, is any of this still possible? In short, yes... But there are more caveats and quirks as modern hardware and software evolves in complexity and XP becomes increasingly obsolete. I should emphasize that if you really want to use XP these days, you are much better off using a standalone system with XP-era hardware as the basis. My convoluted modern dual boot approach is ill-advised unless you're an absolute mad man, and any attempt to do so is at your own peril.  Read Full Article

Apple Muncher Project Postmortem: Developing for Panasonic VIERA Connect SmartTV (Part 4)

This is the final part of a four-part series detailing my personal experience developing an indie game for Panasonic’s obscure VIERA Connect television app market years ago.

In the first part of the series, I detailed the pains of becoming a VIERA Connect third party developer and struggles of setting up the rigid development environment required by Panasonic. For the second part, I documented the development process of actually creating a game using the often restrictive VIERA Connect framework. The third part of the story focused on the obstacles of actually publishing the app to the market. This part discusses the aftermath. Read Full Article

How To Fix OBS Studio and ZoomIt for Screencasts (Double Cursor Bug)


If you have ever tried using OBS Studio in conjunction with any realtime magnification tools—such as the LiveZoom feature of the excellent and free ZoomIt utility by SysInternals—you'll find that there is quite a frustrating issue with it. While recording with OBS Studio, if you want to zoom into the mouse location using a magnifier app, you will get a second phantom mouse cursor that appears in the recording relative to the enlarged version. This is because OBS is still rendering the native system mouse relative to the display resolution, while the enlarged cursor is being simultaneously rendered to the screen relative to the zoomed in coordinates.

This problem has generated a number of discussions over the years and has been especially problematic to users wishing to create screencasts and related materials. There have been complaints, bug reports and suggestions on how OBS Studio could internally resolve the problem. However, to date there has not been any proper solution offered. The general counter-argument has been that this is a very isolated use case and that other commercial products like Camtasia ($249 USD) would be much better suited for this scenario. But for users already familiar with OBS or not wishing to invest time and money into other software products, I have found that professional screencasts can be created just fine via OBS as long as we can overcome the double cursor bug. Here is what I came up with as a makeshift solution.

Fixing the Double Cursor Bug when Zooming in OBS

To get around the cursor bug problem, we will setup a new OBS scene collection with two scenes. One scene will be setup to record the display with the mouse cursor, and the other without the mouse cursor. Using a shared keyboard shortcut and the transition feature of OBS, we will be able to automatically switch scenes when zoomed in or out so that only the enlarged render of the cursor will appear while magnified.

For this tutorial I am using OBS Studio 22.0.2 and ZoomIt v4.5, but you will find other magnification apps exhibit the same double cursor issue when used with OBS and should be able to easily adapt these instructions for those other utilities. These steps only need to be completed one time; you can then load the scene collection at any time to use these settings.

  1. Create a new scene collection by selecting Scene Collection → New from the top file menu. Give the collection a name, such as "Screencasting" and click OK.
  2. For clarify, let's rename the default scene to "Scene (With Cursor)" by right-clicking on it and selecting Rename.
  3. Add a second scene by clicking on the [+] button under the Scenes list and name it "Scene (Without Cursor") then click OK.
  4. Select the first scene again—Scene (With Cursor)—and then click the [+] button under the Sources list and select Display Capture.
    1. Note: Other source types will not allow you to capture the full screen as you see it. To capture magnification features of other utilities, you must use Display Capture.

    Give the selected Display Capture a more descriptive name, such as "Display Capture (With Cursor)" and then click OK.
    When the Properties window appears, make sure that "Capture Cursor" is checked and—if you have more than one connected display—that you have selected the correct display that you wish to capture, then click OK.
    Repeat steps 4-6 for the second scene—Scene (Without Cursor)—but name the source "Display Capture (Without Cursor)" and make sure that "Capture Cursor" is unchecked.
    Open up the magnifier tool to configure a toggle shortcut. In ZoomIt, click on the LiveZoom tab and then assign a unique keyboard shortcut such as CTRL+SHIFT+ALT+X.  Do NOT click OK yet as we don't want to enable the shortcut until after we also configure it in OBS.
    Click on "Settings" in OBS Studio, then click on Hotkeys and finally enter the same keyboard shortcut under Transition as you did in the zoom utility (e.g., CTRL+SHIFT+ALT+X). Then click OK.
    You can now click OK within ZoomIt as well to activate the utility, but don't press the shortcut just yet.
    Back inside of OBS Studio, click to select "Scene (Without Cursor)" from the Scenes list and then click on the Studio Mode button.
    With Studio Mode open, click to highlight "Scene (With Cursor)" and then click on the Transition button in the center of the screen. This will establish our transition process between the two scenes and ready it for use with our zoom utility and matching shortcut.

    1. Note: Make sure that "Swap Preview/Output Scenes After Transitioning" is activated in the Preferences button next to Transition, which it should be by default.

    Now you can start the recording, minimize OBS Studio and then toggle the magnification whenever needed using the keyboard shortcut. Only a single cursor will be recorded, as expected. The keyboard shortcut for Transition will not work if you currently have OBS Studio in focus, so either click onto a different app or minimize OBS before using the magnification shortcut.

    NOTE: After switching scenes or relaunching OBS, you may need to repeat steps 11-12 to prepare it for use again. You can also add audio input/output sources to both scenes for capturing audio.

    Although this is not the most desirable solution, it does solve the problem pending any official fix. Since OBS Studio is open-source, anyone could theoretically create a fork of the code to implement a workaround internally or perhaps a standalone plugin, time-permitting.