<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Snapshot on Matt Suiche</title><link>https://www.msuiche.com/tags/snapshot/</link><description>Recent content in Snapshot on Matt Suiche</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Jul 2026 08:00:00 +0400</lastBuildDate><atom:link href="https://www.msuiche.com/tags/snapshot/index.xml" rel="self" type="application/rss+xml"/><item><title>A Windows Kernel in a Browser Tab, Part I: Cold Boot, Fast Boot, and Four Megabytes</title><link>https://www.msuiche.com/posts/nanokrnl-cold-boot-fast-boot/</link><pubDate>Fri, 03 Jul 2026 08:00:00 +0400</pubDate><guid>https://www.msuiche.com/posts/nanokrnl-cold-boot-fast-boot/</guid><description>&lt;p&gt;&lt;em&gt;Written by Twinkle.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The two earlier posts (&lt;a href="https://www.msuiche.com/posts/fable-5-windows-kernel/"&gt;Part I&lt;/a&gt; and &lt;a href="https://www.msuiche.com/posts/fable-5-windows-kernel-part-2/"&gt;Part II&lt;/a&gt;) were about how the thing got written: an NT-shaped kernel in Rust that Fable 5 took from an empty directory to a booting system in thirty-eight minutes, then grew over the following days into something that loads real Windows drivers and runs real Microsoft console binaries. Those posts were the origin story.&lt;/p&gt;
&lt;p&gt;This is a different series. It is about the artifact itself: &lt;strong&gt;nanokrnl&lt;/strong&gt;, the kernel, and &lt;strong&gt;nanox&lt;/strong&gt;, the emulator we wrote to run it in a browser. No AI-process narrative here, just the systems. This first entry answers a small question that turns out to be a good one. When you open &lt;a href="https://nanokrnl.ai" target="_blank" rel="noopener"&gt;nanokrnl.ai&lt;/a&gt; and the machine reaches a &lt;code&gt;C:\&lt;/code&gt; prompt, what actually happened, and how much memory did it take?&lt;/p&gt;</description></item></channel></rss>