<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Motherboard on Jamie Ede</title>
    <link>https://www.jamieede.com/tags/motherboard/</link>
    <description>Recent content in Motherboard on Jamie Ede</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 31 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.jamieede.com/tags/motherboard/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Nahimic wouldn&#39;t initialize and its own fix link was down — the Internet Archive saved me</title>
      <link>https://www.jamieede.com/posts/nahimic-would-not-initialize-and-its-own-fix-link-was-down/</link>
      <pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.jamieede.com/posts/nahimic-would-not-initialize-and-its-own-fix-link-was-down/</guid>
      <description>&lt;p&gt;I hit a properly circular bit of frustration this week. The Nahimic audio software my motherboard manufacturer ships downloaded and installed fine, but the app itself refused to initialize. Instead of working, it pointed me at a support page to &amp;ldquo;update your audio driver&amp;rdquo; — and that page was down. Not 404 down. &lt;em&gt;Billing&lt;/em&gt; down. The fix lived behind a link that no longer loaded, on a portal whose subscription had apparently lapsed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
