<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SD Cards on Nalar</title>
    <link>https://nalar.dev/tags/sd-cards/</link>
    <description>Recent content in SD Cards on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/sd-cards/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why an SD Card Can Become Read-Only</title>
      <link>https://nalar.dev/tech/why-an-sd-card-can-become-read-only/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/tech/why-an-sd-card-can-become-read-only/</guid>
      <description>&lt;p&gt;An SD card can behave normally when you open photos or copy files from it, yet refuse to save new files, delete old ones, or format the card. A camera may call the card &amp;ldquo;locked&amp;rdquo; or &amp;ldquo;write-protected,&amp;rdquo; while a computer may describe it as read-only.&lt;/p&gt;&#xA;&lt;p&gt;These messages all point to the same practical distinction: &lt;strong&gt;reading data and changing data are separate operations&lt;/strong&gt;. A device may still be able to retrieve existing information even when writes are being blocked.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
