Add chat-archive description

Update repos and CV from prebuild
Revert Kölle to Koelle in meta/title/alt tags for SEO, keep Kölle in visible text
2026-09-17 17:00:25 +00:00 · 2026-09-17 16:45:17 +02:00 · 2026-09-17 16:21:56 +02:00 · 2026-09-14 12:15:26 +02:00 · 2026-09-13 23:44:49 +02:00 · 2026-09-13 23:33:43 +02:00
57 changed files with 631 additions and 135 deletions
@@ -161,6 +161,10 @@ CSS-Dateien werden als Passthrough kopiert (kein Hash im Dateinamen). Bei CSS-Ae

 Bei jeder CSS-Anpassung `?v=N` um 1 erhoehen, sonst cached der Browser die alte Datei.

+### skoelle GitHub-Repo im Auge behalten
+
+Bei Aenderungen an stefankoelle.de (Inhalte, Technologien, URLs) pruefen, ob die Datei `../skoelle/README.md` ebenfalls aktualisiert werden muss. Das README ist die Kurzform des Lebenslaufs und soll mit stefankoelle.de synchron bleiben.
+
 ## CI/CD

 ### IONOS SFTP (www.moonweb.org)
@@ -1,4 +1,21 @@
 [
+  {
+    "title": "Chat Archive",
+    "emoji": "💬",
+    "category": "code",
+    "subcategory": "Dev Tools",
+    "status": "active",
+    "stack": [
+      "Python",
+      "FastAPI",
+      "SQLAlchemy",
+      "Tauri",
+      "Rust"
+    ],
+    "repo": "chat-archive",
+    "repo_url": "https://github.com/skoelle/chat-archive",
+    "summary": "Import Instagram & Facebook (incl. E2EE) chat takeouts into a searchable MySQL database with a REST API for analysis"
+  },
  {
    "title": "PeopleCostCounter",
    "emoji": "💰",
@@ -14,6 +31,22 @@
    "repo_url": "https://github.com/skoelle/PeopleCostCounter",
    "summary": "A vanilla JS single-page tool that shows in real time how much a meeting is costing, based on team size and average salary, with English and German UIs."
  },
+  {
+    "title": "Smeagol WYSIWYG",
+    "emoji": "🧙",
+    "category": "code",
+    "subcategory": "Dev Tools",
+    "description": "Personal wiki with WYSIWYG editor for Markdown files",
+    "status": "active",
+    "stack": [
+      "Go",
+      "Milkdown",
+      "Markdown"
+    ],
+    "repo": "smeagol-wysiwyg",
+    "repo_url": "https://github.com/skoelle/smeagol-wysiwyg",
+    "summary": "A personal wiki with a real WYSIWYG editor. Single Go binary, Markdown files on disk, instant save, live reload, full-text search."
+  },
  {
    "title": "kctl-tui",
    "emoji": "🐳",
@@ -259,7 +292,7 @@
    ],
    "repo": "moonweb-site",
    "repo_url": "https://github.com/skoelle/moonweb-site",
-    "summary": "Monorepo for moonweb.org - my personal homelab hub. Six static sites (Eleventy) covering infrastructure, smart home, code, and retro hardware. Deployed to Cloudflare Pages or IONOS."
+    "summary": "Monorepo for moonweb.org - my personal homelab hub. Six static sites (Eleventy) covering infrastructure, smart home, code, and retro hardware. Deployed to IONOS."
  },
  {
    "title": "www.moonweb.org",
@@ -46,7 +46,9 @@ module.exports = function (eleventyConfig) {
  eleventyConfig.addPassthroughCopy("retro/atari-vga/*.jpg");
  eleventyConfig.addPassthroughCopy("retro/laser-mouse/*.jpg");
  eleventyConfig.addPassthroughCopy("retro/mega-st-high/*.jpg");
+  eleventyConfig.addPassthroughCopy("retro/dos-486-tower/*.jpg");
  eleventyConfig.addPassthroughCopy("retro/mistery-core/*.jpg");
+  eleventyConfig.addPassthroughCopy("retro/mini-arcade-handheld-roundup/*.jpg");

  // Standalone demo group archives (static HTML)
  eleventyConfig.addPassthroughCopy("phobia/**");
@@ -54,6 +56,7 @@ module.exports = function (eleventyConfig) {

  // Root-level shared assets
  eleventyConfig.addPassthroughCopy({ "shared/base.css": "shared-base.css" });
+  eleventyConfig.addPassthroughCopy({ "shared/fonts/lobster-latin.woff2": "fonts/lobster-latin.woff2" });
  eleventyConfig.addPassthroughCopy({ "shared/favicon/hub.svg": "favicon.svg" });
  eleventyConfig.addPassthroughCopy({ "hub/robots.txt": "robots.txt" });

@@ -1,9 +1,9 @@
 ---
-title: "Stefan Kölle, Homelab, Smart Home, Code & Retro Hardware | moonweb"
+title: "Stefan Koelle, Homelab, Smart Home, Code & Retro Hardware | moonweb"
 section: "hub"
 tags: "hub"
 permalink: /index.html
-description: "Stefan Kölle, Senior Software Developer & Architect in Munich. Homelab projects, smart home automation, open-source code, and retro hardware."
+description: "Stefan Koelle, Senior Software Developer & Architect in Munich. Homelab projects, smart home automation, open-source code, and retro hardware."
 layout: base.njk
 ogImage: "/stefan-koelle-foto.jpg"
 sections:
@@ -57,7 +57,7 @@ sections:
    <p>I'm a Senior Software Developer &amp; Architect based in Munich with 20+ years in the trenches, from Turbo Pascal on a real 486 back in the day to .NET, Kubernetes, and AI-driven development today. By day I build microservices and cloud architecture, by night I dive into smart home automation, restore retro computers, and automate things that don't necessarily need automating.</p>
    <p>Everything here runs on a homelab that has been evolving since the mid-90s, from multiple 486s and Pentiums back then to today's Proxmox cluster. Have a look around.</p>
  </div>
-  <img class="intro-photo" src="/stefan-koelle-foto.jpg" alt="Stefan Kölle" width="280" height="280">
+  <img class="intro-photo" src="/stefan-koelle-foto.jpg" alt="Stefan Koelle" width="280" height="280">
 </div>

 {% include "card-grid.njk" %}
@@ -5,7 +5,7 @@ tags: "infra"
 description: "Homelab infrastructure overview: Proxmox hosts, Synology NAS, Docker VMs and Setup-Guides."
 layout: base.njk
 sections:
-  - heading: "Plattform"
+  - heading: "Platform"
    cards:
      - title: "🖥️ Proxmox host (PVE)"
        summary: "Hosting environment for running production VMs and LXC containers for the homelab."
@@ -16,8 +16,8 @@ sections:
      - title: "🐳 Docker VMs (Debian)"
        summary: "Primary target for new Docker/Compose services, running the monitoring exporters."
        href: "/infra/docker/"
-      - title: "📦 LxC Container"
-        summary: "Pi-hole, Ubuntu-Worker and MariaDB running on slim LxC Containers."
+      - title: "📦 LXC Container"
+        summary: "Pi-hole, Ubuntu-Worker and MariaDB running on slim LXC Containers."
        href: "/infra/lxc/"
  - heading: "Strategies & Setup-Guides"
    cards:
@@ -7,22 +7,40 @@
 	<meta name="description" content="Explore the PHOBIA DemoGroup Archive, showcasing the 1994 PC intros, including the notable Phobia Welcome Intro. Relive the early days of PC intros with source code and more.">
 	<link rel="canonical" href="https://www.moonweb.org/phobia/" />
    <style>
-        body {
+		@font-face {
+			font-family: 'VT323';
+			font-style: normal;
+			font-weight: 400;
+			font-display: swap;
+			src: url('fonts/vt323-latin.woff2') format('woff2');
+		}
+		@font-face {
+			font-family: 'Press Start 2P';
+			font-style: normal;
+			font-weight: 400;
+			font-display: swap;
+			src: url('fonts/pressstart2p-latin.woff2') format('woff2');
+		}
+		body {
            background-color: #1a1a1a;
            margin: 0;
            color: #f0f0f0;
-            font-family: 'Arial', sans-serif;
+            font-family: 'VT323', monospace;
            line-height: 1.6;
+            font-size: 20px;
+            overflow-x: hidden;
+            text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;
        }
        .header {
            display: flex;
            align-items: center;
+            justify-content: center;
            background-color: #000071;
-			padding-top:5px;
-            padding-left: 20px;
+            padding: 10px 0;
        }
-        .header img {
-            margin-right: 20px;
+        .header img, .header canvas {
+            height: 120px;
+            margin-right: 0;
        }
        .header a {
            margin: 0 15px;
@@ -36,7 +54,9 @@
        .content {
            display: flex;
            flex-wrap: wrap;
-            padding: 40px;
+            padding: 20px 15px;
+            max-width: 1000px;
+            margin: 0 auto;
        }
        .program {
            display: flex;
@@ -52,15 +72,40 @@
            height: auto;
            border-radius: 10px;
        }
+        .video-thumb {
+            position: relative;
+            cursor: pointer;
+        }
+        .play-button {
+            position: absolute;
+            top: 50%;
+            left: 50%;
+            transform: translate(-50%, -50%);
+            width: 0;
+            height: 0;
+            border-left: 35px solid rgba(255,255,255,0.9);
+            border-top: 20px solid transparent;
+            border-bottom: 20px solid transparent;
+            filter: drop-shadow(0 0 6px rgba(0,0,0,0.6));
+            transition: opacity 0.2s;
+        }
+        .video-thumb:hover .play-button {
+            opacity: 0.7;
+        }
        .program-description {
            margin-top: 10px;
            font-size: 1.1em;
+            line-height: 1.4;
+        }
+        .program-description p {
+            margin: 0.3em 0;
        }
        .program-info {
            flex: 2 1 300px;
        }
        .program-info h2 {
-            font-size: 2em;
+            font-size: 1em;
+            margin-top: 0;
            margin-bottom: 10px;
        }
        .footer {
@@ -70,18 +115,23 @@
            background-color: #333;
            margin-top: 20px;
        }
-        @media (max-width: 768px) {
+        h1, h2 {
+            font-family: 'Press Start 2P', cursive;
+        }
+        @media (max-width: 600px) {
 			h1 {
 				font-size: 1.7em;
 			}
 			.program-info h2 {
-				font-size: 1.5em;
+				font-size: 1.2em;
 				margin-bottom: 10px;
 			}
-			.header img {
+			.header img, .header canvas {
 				width: 100%;
+				height: auto;
 			}
            .content {
+                padding: 15px 10px;
                flex-direction: column;
                align-items: left;
            }
@@ -96,9 +146,26 @@
            .program-info {
                text-align: left;
            }
+            .content table {
+                width: 100%;
+            }
+            .content table tr {
+                display: flex;
+                flex-direction: column;
+                margin-bottom: 0.8em;
+            }
+            .content table td {
+                padding-right: 0;
+            }
+            .content table td:first-child {
+                margin-bottom: 0.2em;
+            }
        }
-		th {
+		th, td {
 		  text-align:left;
+		  vertical-align: top;
+		  padding-right: 20px;
+		  overflow-wrap: break-word;
 		  }
 		a {
 			color:#00A6FF;
@@ -150,22 +217,26 @@
 <body>
    <div class="header">
        <a href="index.html">
-            <img src="phobialogo.png" alt="PHOBIA">
+            <canvas id="phobialogo" style="margin-right:20px;image-rendering:pixelated;"></canvas>
+            <img id="phobialogo-fallback" src="phobialogo.png" alt="PHOBIA" style="display:none;">
        </a>
    </div>
    <div class="content">
 	
 		<div class="welcome">
-		<h1>Welcome to the PHOBIA DemoGroup Archive</h1>
+		<h1>PHOBIA DemoGroup Archive</h1>

-		<p>This site showcases the releases from my DemoGroup, PHOBIA. Although PHOBIA existed only briefly on the PC in 1994, it made a notable impact with its focus on PC intros. The highlight of our work was the major release, the Phobia Welcome Intro.</p>
+		<p>This site showcases the releases from my DemoGroup, PHOBIA. Although PHOBIA existed only briefly in 1994, it made a notable impact with its focus on PC intros. The highlight of our work was the Phobia Welcome Intro.</p>
 		<p>Feel free to explore and enjoy the nostalgia of the early days of PC intros.</p>
-		<p>Best regards, Stefan Koelle</p>
+		<p style="margin-bottom: 1.5em;">Best regards, Stefan Koelle</p>
 		</div>
 		
        <div class="program">
            <div class="program-image">
-                <img src="welcomeintro.png" alt="Program 1 Image" onclick="openLightbox()">
+                <div class="video-thumb" onclick="openLightbox()">
+                    <img src="welcomeintro.png" alt="Program 1 Image">
+                    <div class="play-button"></div>
+                </div>
                <div class="program-description">
                    <p><b>Phobia Welcome Intro</b></p>
                    <p><a href="#" onclick="openLightbox()">YouTube Video of the Intro</a></p>
@@ -174,55 +245,51 @@
            </div>
            <div class="program-info">
                <h2>Phobia Welcome Intro</h2>
-                <p>The Phobia Welcome Intro was programmed in 1994 using Turbo Pascal, with inline assembler for the graphics routines. The idea for this intro was inspired by an Amiga demo, though the specific name of the demo has been forgotten. All graphics and programming were done by Stefan Koelle on a 486 DX2-66 DOS PC.</p>
-        <p>This intro utilized an early version of the X-LIB unit, specifically the TextGraf.pas, which was also developed by Stefan Koelle. The source code for the intro is available on GitHub. The primary technique used in this intro to create the illusion of movement was through color palette changes, rather than altering the pixels on the screen.</p>
-        <p>The music for the intro was borrowed from an old Amiga demo and played using a public Mod-Player. The font used in the intro was custom-created and compiled into the executable as an object, along with the music and graphics.</p>
+                <p>The Phobia Welcome Intro was programmed in 1994 using Turbo Pascal, with inline assembler for the graphics routines. This intro was inspired by an Amiga demo, though the specific name has been forgotten. All graphics and programming were done by Stefan Koelle on a 486 DX2-66 DOS PC.</p>
+        <p>This intro utilized an early version of the X-LIB unit, specifically the TextGraf.pas, which was also developed by Stefan Koelle. The source code for the intro is available on GitHub. The primary technique used to create the illusion of movement was color palette changes, rather than altering the pixels on the screen.</p>
+        <p>The music for the intro was borrowed from an old Amiga demo and played using a public Mod-Player. The font used in the intro was custom and compiled into the executable as an object, along with the music and graphics.</p>
        
-        <h2>Key Details:</h2>
+        <h2>Facts</h2>
        <table>
            <tr>
-                <th>Feature</th>
-                <th>Description</th>
-            </tr>
-            <tr>
-                <td>Programming Language</td>
+                <td><b>Language</b></td>
                <td>Turbo Pascal with inline assembler</td>
            </tr>
            <tr>
-                <td>Year</td>
+                <td><b>Year</b></td>
                <td>1994</td>
            </tr>
            <tr>
-                <td>Developer</td>
+                <td><b>Developer</b></td>
                <td>Stefan Koelle</td>
            </tr>
            <tr>
-                <td>Development Machine</td>
+                <td><b>Development Machine</b></td>
                <td>486 DX2-66 DOS PC</td>
            </tr>
            <tr>
-                <td>Graphics Technique</td>
+                <td><b>Graphics Technique</b></td>
                <td>Color palette changes</td>
            </tr>
            <tr>
-                <td>Music Source</td>
+                <td><b>Music Source</b></td>
                <td>Old Amiga demo</td>
            </tr>
            <tr>
-                <td>Music Player</td>
+                <td><b>Music Player</b></td>
                <td>Public Mod-Player</td>
            </tr>
            <tr>
-                <td>Custom Font</td>
+                <td><b>Custom Font</b></td>
                <td>Compiled into the executable as an object</td>
            </tr>
            <tr>
-                <td>Graphics Library</td>
+                <td><b>Graphics Library</b></td>
                <td>Early version of X-LIB unit (TextGraf.pas)</td>
            </tr>
            <tr>
-                <td>Source Code</td>
-                <td>Available on GitHub <a href="https://github.com/skoelle/dos-phobia-welcome-intro" target="_blank">https://github.com/skoelle/dos-phobia-welcome-intro</a></td>
+                <td><b>Source Code</b></td>
+                <td>Available on GitHub<br><a href="https://github.com/skoelle/dos-phobia-welcome-intro" target="_blank">https://github.com/skoelle/dos-phobia-welcome-intro</a></td>
            </tr>
        </table>
            </div>
@@ -255,6 +322,7 @@
            </div>
        </div>-->
    </div>
+    <canvas id="copperbars" style="position:fixed;top:0;left:0;width:100%;height:100%;z-index:-1;pointer-events:none;"></canvas>
    <div class="footer">
        PHOBIA website - initially created November 1999 - code from 1994 - Stefan Koelle<br>
        Part of <a href="/">moonweb.org</a> · <a href="/retro/">Retro Corner</a> · <a href="/impressum/">Legal Notice</a>
@@ -265,5 +333,115 @@
            <iframe id="video" src="" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
        </div>
    </div>
+    <script>
+        (function() {
+            var canvas = document.getElementById('phobialogo');
+            var fallback = document.getElementById('phobialogo-fallback');
+            var ctx = canvas.getContext('2d');
+            var img = new Image();
+            img.crossOrigin = 'anonymous';
+            img.onload = function() {
+                canvas.width = img.width;
+                canvas.height = img.height;
+                fallback.style.display = 'none';
+                canvas.style.display = 'inline';
+                var origData = null;
+                try {
+                    ctx.drawImage(img, 0, 0);
+                    origData = ctx.getImageData(0, 0, canvas.width, canvas.height);
+                } catch(e) {
+                    fallback.style.display = 'inline';
+                    canvas.style.display = 'none';
+                    return;
+                }
+                var pixels = origData.data;
+                var blueMap = {};
+                for (var i = 0; i < pixels.length; i += 4) {
+                    var r = pixels[i], g = pixels[i+1], b = pixels[i+2];
+                    if (b > 30 && b > r * 1.3 && b > g * 1.2) {
+                        var key = r + ',' + g + ',' + b;
+                        if (!blueMap[key]) blueMap[key] = { r: r, g: g, b: b, count: 0 };
+                        blueMap[key].count++;
+                    }
+                }
+                var palette = [];
+                for (var k in blueMap) {
+                    if (blueMap[k].count >= 500) palette.push(blueMap[k]);
+                }
+                palette.sort(function(a, b) {
+                    var la = a.r * 0.299 + a.g * 0.587 + a.b * 0.114;
+                    var lb = b.r * 0.299 + b.g * 0.587 + b.b * 0.114;
+                    return la - lb;
+                });
+                var origColors = palette.map(function(c) { return { r: c.r, g: c.g, b: c.b }; });
+                var rotColors = origColors.slice();
+                var offset = 0;
+                function draw() {
+                    var out = ctx.createImageData(canvas.width, canvas.height);
+                    out.data.set(pixels);
+                    var d = out.data;
+                    for (var i = 0; i < palette.length; i++) {
+                        rotColors[i] = origColors[(i + offset) % palette.length];
+                    }
+                    var lookup = {};
+                    for (var i = 0; i < palette.length; i++) {
+                        var oc = origColors[i];
+                        var rc = rotColors[i];
+                        lookup[oc.r + ',' + oc.g + ',' + oc.b] = rc;
+                    }
+                    for (var i = 0; i < d.length; i += 4) {
+                        var key = d[i] + ',' + d[i+1] + ',' + d[i+2];
+                        if (lookup[key]) {
+                            d[i]   = lookup[key].r;
+                            d[i+1] = lookup[key].g;
+                            d[i+2] = lookup[key].b;
+                        }
+                    }
+                    ctx.putImageData(out, 0, 0);
+                    offset = (offset + 1) % palette.length;
+                    setTimeout(function() { requestAnimationFrame(draw); }, 120);
+                }
+                draw();
+            };
+            img.onerror = function() {
+                fallback.style.display = 'inline';
+                canvas.style.display = 'none';
+            };
+            img.src = 'phobialogo.png';
+        })();
+    </script>
+    <script>
+        (function() {
+            var canvas = document.getElementById('copperbars');
+            var ctx = canvas.getContext('2d');
+            var w, h;
+            function resize() { w = canvas.width = window.innerWidth; h = canvas.height = window.innerHeight; }
+            resize();
+            window.addEventListener('resize', resize);
+            var bars = [
+                { baseY: 0.45, amplitude: 0.18, speed: 0.7, r: 255, g: 199, b: 0, barH: 50 },
+                { baseY: 0.55, amplitude: 0.15, speed: 1.1, r: 239, g: 0, b: 0, barH: 50 },
+                { baseY: 0.52, amplitude: 0.20, speed: 0.9, r: 4, g: 203, b: 0, barH: 50 },
+            ];
+            function draw(t) {
+                ctx.clearRect(0, 0, w, h);
+                for (var i = 0; i < bars.length; i++) {
+                    var bar = bars[i];
+                    var y = h * bar.baseY + Math.sin(t * 0.001 * bar.speed) * h * bar.amplitude;
+                    var halfH = bar.barH / 2;
+                    for (var row = -halfH; row <= halfH; row++) {
+                        var rel = row / halfH;
+                        var alpha = 1 - rel * rel;
+                        var py = Math.round(y + row);
+                        if (py < 0 || py >= h) continue;
+                        ctx.fillStyle = 'rgba(' + bar.r + ',' + bar.g + ',' + bar.b + ',' + alpha.toFixed(3) + ')';
+                        ctx.fillRect(0, py, w, 1);
+                    }
+                }
+                requestAnimationFrame(draw);
+            }
+            requestAnimationFrame(draw);
+        })();
+    </script>
 </body>
 </html>
@@ -25,10 +25,12 @@ parent: "/retro/"

 <h2>My Setup</h2>
 <p>I bought an ACSI2STM adapter, but it isn't in use anywhere yet, so it sits among my other uninstalled extensions. The <a href="/retro/ultrasatan/">UltraSatan</a> currently provides the ACSI hard-disk storage on the "Low" machine, so the ACSI2STM would be an alternative or a spare for another machine.</p>
+<p>I also collected all the parts to build a second unit from scratch, following the open-source <a href="https://github.com/retro16/acsi2stm/blob/stable/doc/hardware.md" target="_blank">hardware guide</a>, but never got around to soldering it together. If it eventually gets built, it could go into the <a href="/retro/mega-st-heirloom/">"Heirloom"</a> or the <a href="/retro/mega-st2/">Mega ST 2</a>.</p>

 <h2>Gallery</h2>
 <img src="acsi2stm.jpg" alt="The ACSI2STM adapter" width="640" height="640" loading="lazy">
 <p class="caption">The ACSI2STM adapter, not yet installed.</p>
+<p>The PPERA-HD-GAMES pack (1 GB iTOS version + 7 GB full pack, January 2026) was bought from Peter Putnik for 30 EUR.</p>

 <h2>Sources</h2>
 <ul>
@@ -23,6 +23,17 @@ parent: "/retro/"
 <li><strong>The spare <a href="/retro/mega-st2/">Mega ST 2</a></strong>, a reserve and test machine, kept in largely original condition, used to safely test upgrades before they go into the "real" machines.</li>
 </ul>

+<h2>Machine Inventory</h2>
+<p>All four machines were manufactured at Atari Taiwan Manufacturing Co. (indicated by the "A1" prefix in the serial numbers).</p>
+<table>
+<tr><th>Machine</th><th>Serial</th><th>Manufactured</th><th>Board</th></tr>
+<tr><td>Mega ST 2</td><td>A1 7B 4010182</td><td>11/1987</td><td>CA200019 / C100167-001 Rev.5.0</td></tr>
+<tr><td>Mega ST 4 "High"</td><td>A1 05 4009044</td><td>05/1990</td><td>—</td></tr>
+<tr><td>Mega ST 4 "Low"</td><td>A1 08 4011143</td><td>08/1990</td><td>—</td></tr>
+<tr><td>Mega ST 4 Heirloom</td><td>A1 08 4011015</td><td>08/1990</td><td>CA200019 / C100167-001 Rev.B</td></tr>
+<tr><td>Keyboard (Heirloom)</td><td>A1 07 4085985</td><td>07/1990</td><td>CA200043-004</td></tr>
+</table>
+
 <h2>Extensions Not Yet Installed</h2>
 <p>A few upgrades have been bought or built but aren't in a machine yet, either waiting to go in or kept as spares:</p>
 <ul>
@@ -35,4 +46,6 @@ parent: "/retro/"
 </ul>

 <p class="note">Fun fact: two of the "problem" machines turned out to have nothing wrong with the boards at all, a badly soldered CPU socket and a leftover blitter patch bridge were the actual culprits. Moral of the story: check your solder joints twice before blaming the silicon.</p>
+
+<p>For the full story of how it all started, see the <a href="/retro/computer-timeline/">computer timeline</a>.</p>
 </div>
@@ -21,6 +21,7 @@ parent: "/retro/"

 <h2>Dialing the DarkForce! BBS</h2>
 <p>To put it to the test, I dialed into <a href="https://www.telnetbbsguide.com/bbs/dark-force-bbs/" target="_blank">the DarkForce! BBS</a>, an Atari-centric system that has been running since the early 90s on a Mega ST4 with BBS Express! ST software. It's a fitting target for an Atari ST, since it's a fellow Atari machine at heart. With the terminal software on the Mega ST sending <code>ATDT</code> to the Wi-Fi modem, the connection to <code>darkforce-bbs.dyndns.org</code> over Telnet worked, and the ANSI login screen, message boards and file sections of a real BBS came up on the original hardware, no phone line involved.</p>
+<p>Another BBS I tested is the <a href="http://18.221.141.17" target="_blank">Ignition BBS</a>, also accessible via telnet.</p>

 <h2>Why do it</h2>
 <p>The obvious question is "why bother?", the Atari ST was never designed
@@ -33,12 +34,14 @@ culture on original hardware, over Wi-Fi instead of a phone line.</p>

 <h2>Also worth noting</h2>
 <p>Jungsi tested a <a href="https://www.jungsi.de/wimodem232-oled-retro/" target="_blank">WiModem232 OLED</a> on his Atari ST and wrote about it on his blog. He used a different modem hardware than I did, but the idea is the same. He used "Connect" as his terminal software on the ST, but I used a different terminal program that could render ANSI graphics in ST Medium resolution, though I'd have to look up which one it was exactly.</p>
+<p>For better ANSI rendering, <strong>AnsiTerm</strong> is reportedly a better choice than Connect95 for BBS terminal use on the Atari ST.</p>

 <h2>Sources</h2>
 <ul>
 <li><a href="https://github.com/dhansel/WifiModem" target="_blank">dhansel's WifiModem - GitHub</a></li>
 <li><a href="https://www.jungsi.de/wimodem232-oled-retro/" target="_blank">WiModem232 OLED - Jungsi's Corner</a></li>
 <li><a href="https://www.telnetbbsguide.com/" target="_blank">Telnet BBS Guide</a></li>
+<li><a href="http://www.sfhqbbs.org/ataribbslist.php" target="_blank">Atari BBS List - sfhqbbs.org</a></li>
 </ul>

 </div>
@@ -23,6 +23,15 @@ parent: "/retro/"
 <h2>A note on monitors</h2>
 <p>Passive RGB-to-VGA adapters output the Atari's native timings, so color modes (ST Low and ST Medium) need a monitor that can lock to a 15 kHz horizontal sync signal. See my <a href="/retro/atari-monitor-compatibility/">monitor compatibility</a> page for which modern panels actually work. Mono mode (ST High) works on any standard VGA display.</p>

+<h2>VGA switch setup</h2>
+<p>A 3-port VGA switch box routes the shared Dell monitor between the different machines:</p>
+<table>
+<tr><th>Port</th><th>VGA</th><th>USB</th></tr>
+<tr><td>1</td><td>Atari Mega 4 "High" (direct)</td><td>Raspberry Pi (not connected, otherwise no reboot)</td></tr>
+<tr><td>2</td><td>MiST</td><td>MiST</td></tr>
+<tr><td>3</td><td>MiSTer</td><td>MiSTer</td></tr>
+</table>
+
 <h2>Gallery</h2>
 <img src="stvga-low.jpg" alt="The MCSWITCH VGA adapter connected to the Atari" width="640" height="640" loading="lazy">
 <p class="caption">The MCSWITCH adapter on the Mega ST 4 "Low" machine.</p>
@@ -0,0 +1,43 @@
+---
+title: "My Computer Timeline: Atari ST, Amiga 500, DOS 486"
+section: "retro"
+tags: "retro"
+description: "The personal computing story behind the retro corner, from Atari ST and Amiga 500 to DOS 486 and beyond."
+layout: base.njk
+parent: "/retro/"
+---
+<h1>My Computer Timeline: Atari ST, Amiga 500, DOS 486</h1>
+<div class="detail-content">
+
+<p>Every retro computing setup has a story. Here's mine, from the first time I sat in front of a screen to the machines I use today.</p>
+
+<h2>1983-1987: First contact</h2>
+<p>When I started primary school in 1983, friends already had computers. One showed me everything a C64 could do, except the Lego game he kept promising to show me. That never happened, but I was hooked on computers anyway. Around the same time my father brought home an Epson HX-20, a tiny portable with a small screen and a built-in microcassette drive. That's where I wrote my very first BASIC programs.</p>
+
+<h2>1987-1990: The Atari ST era</h2>
+<p>In secondary school a friend named Matthias had an Atari, and a couple of classmates in the class also got Ataris over time. For Christmas 1989 I got my own 1040STFM. A year later, Christmas 1990, came the Mega ST 4 with a MegaFile hard disk, the beginning of a much deeper relationship with the platform. Early programming started with Omikron BASIC, then quickly moved to GFA BASIC, which became the main tool for writing software on the ST. Some of the things I built during that time are preserved here: <a href="https://28k8.moonweb.org/bbs/atari/tropic-dreams/" target="_blank">Tropic Dreams</a>.</p>
+
+<h2>1990-1992: The Amiga detour</h2>
+<p>More and more classmates had Amigas, and I wanted one too. The Amiga arrived around April 1991, and while the Atari ST remained the programming machine, the Amiga became the creative hub: <a href="https://28k8.moonweb.org/bbs/amiga/mods/" target="_blank">ProTracker</a> for music, Deluxe Paint for graphics. I also released a few things under the Esprit label: <a href="https://28k8.moonweb.org/bbs/amiga/esprit/" target="_blank">ESPRIT releases</a>.</p>
+
+<h2>1992-1994: The PC arrives</h2>
+<p>Christmas 1993 brought a Vobis Highscreen 486 DX2-66 in its distinctive Colani tower case. The PC opened the door to DOS games, and in 1994 the real creative phase began: <a href="https://28k8.moonweb.org/bbs/pc/dosmenu/" target="_blank">DOSMENU</a>, the <a href="https://28k8.moonweb.org/bbs/pc/skyline/" target="_blank">SkyLine</a> demo group, and the first modem connecting to the outside world.</p>
+
+<h2>1994-2000: The Fido era</h2>
+<p>A modem in spring 1994 led to the <a href="https://28k8.moonweb.org/bbs/fido/nodelist/" target="_blank">FidoNet</a> world, and by late 1995 I was running my own <a href="https://28k8.moonweb.org/" target="_blank">BBS node</a>. Through the mid-90s I collected old and new machines enthusiastically, building up a collection that lasted until 2005 when most of it was sold off. By 2000, the FidoNet hobby had quietly faded.</p>
+
+<h2>2000-2009: The Linux server years</h2>
+<p>After the FidoNet era wound down, the focus shifted to Linux. A home network grew in Augsburg with a Smoothwall firewall, a Red Hat server, a Postfix/Apache mail and web server, and a multimedia workstation, all connected over 10 Mbit thin-Ethernet and a demand-dial RAS connection. A FreeBSD server ran Apache, Sendmail and Perl scripts alongside a Windows NT 4.0 file server. Microsoft certifications in Windows NT 4.0 and IIS 4.0 followed in 2000, and the work at IXOS SOFTWARE AG as a Web Engineer rounded out the professional side. The retro hobby took a back seat during this period, but the collection of old machines was still growing quietly in the background until 2005. The <a href="/timecapsule/location/">location</a>, <a href="/timecapsule/network/">network</a> and <a href="/timecapsule/projects/">projects</a> pages of the timecapsule have the full story.</p>
+
+<h2>2009-2017: The Apple years</h2>
+<p>Everything got reduced down to what I actually used daily. The old collection was gone, and the stack became an iMac, an iPhone, and an iPad, with no PCs at home for the first time. A Windows notebook from work was the only non-Apple machine in the house. The retro hobby was completely dormant during this period, while on the iMac .NET Mono tools kept things running.</p>
+
+<h2>2017-2020: The rebuild begins</h2>
+<p>In 2017 a Chromebook from Google joined the setup for everyday tasks, and a Synology NAS arrived. MQTT and the first ESP32 LED matrix projects ran directly on the NAS, while Arduino and ESP32 development started as a parallel hobby. The retro hobby was still dormant, but the groundwork for the homelab and smart home was being laid.</p>
+
+<h2>2020: The retro revival</h2>
+<p>In 2020 the retro computing hobby came back in full force. The Mega ST 4 fleet was rebuilt, the MiSTer and MIST FPGA boards were added, and this site was born to document it all. The machines from the 90s were given new roles instead of gathering dust: a workstation, a demo machine, a reference piece, and a spare.</p>
+<p>At the same time the <a href="/infra/">homelab infrastructure</a> grew: Proxmox servers, a Synology NAS, network planning, and a growing <a href="/smarthome/">smart home</a> setup with Home Assistant, MQTT and various ESP projects.</p>
+
+<p class="note">The pattern seems to be: every 10-15 years I rediscover the machines I grew up with and find new ways to use them.</p>
+</div>
@@ -16,9 +16,19 @@ parent: "/retro/"

 <h2>The MiSTer recreation</h2>
 <p>The AO486 core on MiSTer FPGA handles the hardware convincingly. The real work was rebuilding the software environment from memory: the MS-DOS version, the memory managers (HIMEM.SYS, EMM386), the Sound Blaster drivers, and the AUTOEXEC.BAT and CONFIG.SYS tuning that made the original machine run smoothly.</p>
+<img src="mister.jpg" alt="MiSTer menu on NEC MultiSync" loading="lazy">
+<p class="caption">MiSTer menu on the NEC MultiSync LCD, the same monitor that drives the real retro hardware.</p>

 <h2>Context: DOSMENU</h2>
 <p>A key part of the preserved environment is <strong><a href="https://28k8.moonweb.org/bbs/pc/dosmenu/">DOSMENU</a></strong>, a boot configuration utility written in Turbo Pascal 6.0 in 1994, originally developed specifically for this Colani 486 machine. DOSMENU let you choose at boot time which AUTOEXEC.BAT and CONFIG.SYS commands to load, a critical feature in the DOS era, where memory management was manual and games often required different driver configurations. Features included saveable presets, a built-in MOD player, PCX picture display, and a DoubleSpace memory unloader. The original source: ~50k of Turbo Pascal, roughly 1900 lines plus some inline assembler.</p>
+<img src="mister_486_boot1_dosmenu.jpg" alt="DOSMENU Version 2.0 title screen" loading="lazy">
+<p class="caption">DOSMENU Version 2.0 title screen, the boot configuration utility.</p>
+<img src="mister_486_boot2_dosmenu.jpg" alt="DOSMENU configuration interface" loading="lazy">
+<p class="caption">The DOSMENU configuration interface showing system info, AUTOEXEC.BAT and CONFIG.SYS content, and saveable presets (F01-F10) for different boot configurations.</p>
+<img src="mister_486_boot3_dosmenu.jpg" alt="DOSMENU boot sequence" loading="lazy">
+<p class="caption">DOSMENU boot sequence showing the QEMM386 memory manager loading, registered to Stefan Koelle.</p>
+<img src="mister_486_boot4_dosmenu.jpg" alt="DOSMENU loading DOS Navigator" loading="lazy">
+<p class="caption">DOSMENU unregistered version with DOS Navigator 1.51 (by RIT Research Labs) loading at the C:\> prompt.</p>

 <h2>Why a rebuild from memory</h2>
 <p>The point isn't just to play DOS games, it's to recapture the computing experience from that era. The way DOS memory management worked, the way sound drivers had to be configured manually, the way batch files chained together to create a usable environment. This level of detail is lost when you just launch a DOS game from a modern frontend. The MiSTer setup recreates the whole boot process, from BIOS POST to the C:\> prompt, the way I remember it from the mid-90s.</p>
@@ -31,6 +41,12 @@ parent: "/retro/"
 <li><strong><a href="https://28k8.moonweb.org/bbs/pc/dosmenu/">DOSMENU</a></strong>, a custom boot configuration utility written specifically for this Colani 486 in 1994. Built in Turbo Pascal, it let you choose at boot time which AUTOEXEC.BAT and CONFIG.SYS commands to load, essential for managing DOS memory across different games and applications.</li>
 <li><strong>The quirks</strong>, the specific workarounds and tweaks that were needed to get everything running together, the kind of institutional knowledge that only exists on a well-used personal machine.</li>
 </ul>
+<img src="mister_486_prg1_shell.jpg" alt="X-OS file manager" loading="lazy">
+<p class="caption">X-OS (eXtended Operating System), my Norton Commander clone for DOS, browsing the SkyLINE source directory.</p>
+<img src="mister_486_prg2_diskinfo.jpg" alt="DiskInfo V1.0" loading="lazy">
+<p class="caption">DiskInfo V1.0, a freeware disk space visualizer I wrote in 1993 for SkyLINE.</p>
+<img src="mister_486_prg3_tetris.jpg" alt="Tetris Competition" loading="lazy">
+<p class="caption">Tetris Competition, a two-player Tetris game I wrote for SkyLINE.</p>

 <h2>AO486 vs real hardware</h2>
 <p>The MiSTer AO486 core handles the emulation convincingly. Timing accuracy is good enough for games that rely on cycle-sensitive behavior. Sound Blaster emulation covers the standard OPL3 FM synthesis and digital audio. The main trade-off is that some hardware-specific quirks, like the behavior of specific ISA bus peripherals, aren't perfectly replicated. But since this is a rebuild from memory rather than an exact copy anyway, that's more than good enough for a working DOS environment.</p>
@@ -17,17 +17,47 @@ parent: "/retro/"
 <h2>The Card and Driver</h2>
 <p>I can confirm that a card with the RAMDAC SC11487CN works with the Nova T8 and T6 drivers. And importantly, this particular card does not need -12V, which simplifies the wiring considerably. The STGA adapter comes with its own VDI (STGA_VDI.SYS, v1.3b), a control panel as a CPX module, and a ROM module that switches to the VGA automatically at boot.</p>

+<h2>Nova driver loading order</h2>
+<p>When using the ET4000 with Nova drivers, the loading order in the auto-start folder matters. The correct sequence is:</p>
+<ol>
+<li><code>Emulator.prg</code> (must be first)</li>
+<li><code>menu.prg</code> or <code>xmenu.prg</code></li>
+<li><code>sta_vdi.prg</code></li>
+</ol>
+
 <h2>What Made It Difficult</h2>
 <ul>
 <li><strong>Power supply overload</strong>, the stock Mega ST PSU simply wasn't designed to feed a MonSTerBoard, an ET4000, and a MegaBus adapter at the same time. The 5V and 12V rails ended up right at their instability limit.</li>
 <li><strong>The missing -12V</strong>, many ET4000 cards need -12V for their output drivers, usually tapped from the RS-232 port, adding yet another drain on an already stressed supply. The card I used avoids this.</li>
 <li><strong>Heat with nowhere to go</strong>, the card runs hot, and the Mega ST case has zero provision for active cooling.</li>
 <li><strong>Signal integrity issues</strong>, the ISA-to-MegaBus adapter introduces reflections at higher frequencies, and access to ET4000 RAM is roughly 65% slower than native ST RAM, with no hardware BitBLT to make up for it.</li>
+<li><strong>DVI incompatibility</strong>, the EIZO monitor has DVI-D (digital only), but all available DVI-to-VGA adapters only work with DVI-I (which includes analog lines). Since the EIZO lacks the analog pins, a DVI adapter cannot be used. The ET4000 has its own VGA output and connects directly to the monitor. The self-built <a href="/retro/atari-vga/">VGA adapter</a> on the Atari's native VGA output is only used as a fallback for diagnostics, when something goes wrong during boot before the ET4000 driver loads.</li>
 </ul>

 <h2>How It Got Working</h2>
 <p>Solving it came down to giving the supply the headroom it needed. With a properly beefed-up power supply to cover the 5V and 12V rails, plus a cooling solution for the card, the stability problems went away. The ET4000 now drives higher resolutions and more colors than the Shifter chip can natively produce, turning the "High" machine into a genuine workstation.</p>

+<h2>GemBench Results</h2>
+<p>How does the ET4000 actually perform on an 8 MHz 68000? GemBench 6.31 gives the answer. The reference system is an STE 68000 with stock Shifter, the "High" machine has the ET4000 running at 1024x768x256.</p>
+<img src="gembench.jpg" alt="GemBench 6.31 results on the ET4000" width="640" height="480" loading="lazy">
+<p class="caption">GemBench 6.31 running on the Mega ST 4 "High" with the ET4000.</p>
+<table>
+<tr><th>Test</th><th>Ratio</th><th>What it means</th></tr>
+<tr><td>VDI Text</td><td>269%</td><td>Nearly 3x faster, the ET4000 handles text rendering</td></tr>
+<tr><td>VDI Small Text</td><td>174%</td><td>Noticeably faster</td></tr>
+<tr><td>VDI Graphics</td><td>188%</td><td>Drawing and line work is quicker</td></tr>
+<tr><td>VDI Enquire</td><td>160%</td><td>Screen queries are faster</td></tr>
+<tr><td>VDI Text Effects</td><td>112%</td><td>Slightly faster</td></tr>
+<tr><td>GEM Dialog Box</td><td>97%</td><td>Barely affected</td></tr>
+<tr><td>Integer Division</td><td>99%</td><td>CPU-bound, unchanged</td></tr>
+<tr><td>RAM / ROM Access</td><td>99%</td><td>CPU-bound, unchanged</td></tr>
+<tr><td>Justified Text</td><td>63%</td><td>Slower, GEM still handles this via CPU</td></tr>
+<tr><td>GEM Window</td><td>69%</td><td>Slower, GEM window management adds overhead</td></tr>
+<tr><td>VDI Scroll</td><td>53%</td><td>Slower, scrolling is CPU-bound despite the card</td></tr>
+<tr><td>Blitting</td><td>32%</td><td>Much slower, no hardware BitBLT on the ET4000</td></tr>
+</table>
+<p>The overall average sits at 100%, which is misleading. The picture is split: anything the ET4000 can accelerate (text, graphics drawing) runs significantly faster, while GEM-level operations that still go through the CPU (window management, scrolling, blitting) are dragged down by the overhead of driving a higher resolution through the adapted ISA bus. Running at 1024x768 with 256 colors means roughly 3x the pixel count and roughly 25x the data volume compared to ST High (640x400 monochrome), since the ST's fixed 32 KB screen buffer holds far less data per frame than a 256-color 1024x768 framebuffer. The Nova driver without NVDI squeezes the maximum out of this particular card and driver combination. In day-to-day use, the VDI gains are what you see and feel: text is crisp, menus pop up quickly, and drawing applications are noticeably more responsive.</p>
+
 <h2>The Context</h2>
 <p>FPGA cores on MiSTer and MiST still only emulate the native ST Shifter, with no ET4000 emulation on the horizon given the FPGA resources it would require. So the real hardware approach remains the only way to get those higher resolutions, and now it works in the Mega ST 4 "High" machine with its dedicated <a href="/retro/atari-monitor-compatibility/">monitor</a>.</p>

@@ -98,8 +98,8 @@ sections:
      - title: "🛋️ Batocera in the Living Room"
        summary: "The couch-friendly, software-emulation counterpart to the FPGA rigs, covering everything from Atari ST to arcade."
        href: "/retro/batocera-living-room/"
-      - title: "🕹️ Mini Arcades & Handhelds"
-        summary: "A buyer's guide to compact retro gaming devices, and how to spot a bootleg clone before you buy one."
+      - title: "🕹️ Handheld Emulation Devices"
+        summary: "ODROID-GO, PocketGo and RG35XX, three handhelds for retro gaming on the move."
        href: "/retro/mini-arcade-handheld-roundup/"
  - heading: "DOS & PC"
    cards:
@@ -112,11 +112,20 @@ sections:
      - title: "🎵 TranceMission Archive"
        summary: "TranceMission demos and intros from 1992-1995, programmed in Turbo Pascal with assembler on DOS PCs."
        href: "/tcm/"
+      - title: "🕹️ SkyLINE Productions"
+        summary: "DOS games, demos and tools from the SkyLINE era, 1993-1995."
+        href: "https://28k8.moonweb.org/bbs/pc/skyline/"
  - heading: "Overview"
    cards:
      - title: "🏠 The Retro Corner Today"
        summary: "A room-by-room snapshot of every retro system currently active across the home."
        href: "/retro/retro-corner-snapshot/"
+      - title: "📅 Computer Timeline"
+        summary: "From Atari ST and Amiga 500 to DOS 486, the personal computing story behind the retro corner."
+        href: "/retro/computer-timeline/"
+      - title: "💾 28k8 BBS Archive"
+        summary: "tHE tEMPLE BBS Mailbox and 90s scene releases archive from the 28k8 era."
+        href: "https://28k8.moonweb.org"

 ---
 <h1>Retro Computing</h1>
@@ -19,6 +19,10 @@ parent: "/retro/"
 <li>Its own original Atari keyboard and mouse.</li>
 </ul>

+<h2>Details</h2>
+<p>Serial: A1 08 4011015 · Manufactured August 1990 · Board: CA200019 / C100167-001 Rev.B</p>
+<p>Original keyboard: A1 07 4085985 · Manufactured July 1990 · Board: CA200043-004, fully disassembled and cleaned on 6 March 2022.</p>
+
 <h2>Role in the Fleet</h2>
 <p>This machine serves as a nostalgia and comparison reference. When problems occur on one of the modified Megas, I can test against this unchanged original state to distinguish bus, flash, or configuration errors from genuine hardware faults. It can also be used as a test platform for uncritical experiments, but stays as close to original as possible for nostalgic reasons.</p>

@@ -11,16 +11,20 @@ parent: "/retro/"

 <p>Received for free in 2026, this Mega ST 4 was fully rebuilt and is today my primary workstation. It's the most capable machine in the fleet, running Geneva as a real multitasking environment.</p>

+<h2>Details</h2>
+<p>Serial: A1 05 4009044 · Manufactured May 1990</p>
+
 <h2>Work Performed</h2>
 <ul>
 <li><strong>Blitter patch</strong>, removed an existing patch and carefully bridged the severed trace with wire, verifying it with a continuity test. The installed blitter (marked S9012 / MM9092V, a National variant from week 12/1990) belongs to an unproblematic batch where the classic Mega ST blitter patch is generally no longer needed.</li>
 <li><strong>CPU socket</strong>, soldered in a 68000 socket and checked all connections to the board with a multimeter.</li>
 <li><strong>TOS</strong>, removed the onboard TOS from its sockets to avoid conflicts with the external flash TOS on the MonSTerBoard.</li>
 <li><strong>Power supply</strong>, replaced with a modern <a href="/retro/stpsu/">STPSU</a> for clean, stable power, which matters especially for the ET4000.</li>
+<li><strong>Floppy drive</strong>, the original drive was defective and got swapped with a working unit.</li>
 </ul>

 <h2>MonSTerBoard</h2>
-<p>The <a href="/retro/monsterboard/">MonSTerBoard</a> is plugged onto the 68000 socket, with jumpers set so TOS 2.06 is used from its flash. The TOS 2.06 is patched to skip the memory check, which noticeably speeds up the boot process. KAOS TOS is also installed on the flash, though currently I always run Geneva under TOS 2.06. No TOS switcher is wired up yet, so the machine is fixed to TOS 2.06 for now. The MonSTerBoard provides up to 8 MB of AltRAM (TT-compatible range, activated via <code>m_altram.prg</code>), an IDE interface for CF/IDE storage, and a flash ROM holding multiple TOS images. I boot from a 1 GB CompactFlash card over IDE, which is noticeably faster than an ACSI drive.</p>
+<p>The <a href="/retro/monsterboard/">MonSTerBoard</a> is plugged onto the 68000 socket, with jumpers set so TOS 2.06 is used from its flash. The TOS 2.06 is patched to skip the memory check, which noticeably speeds up the boot process. KAOS TOS is also installed on the flash, though currently I always run Geneva with <strong>NeoDesk 4.06</strong> under TOS 2.06. No TOS switcher is wired up yet, so the machine is fixed to TOS 2.06 for now. The MonSTerBoard provides up to 8 MB of AltRAM (TT-compatible range, activated via <code>m_altram.prg</code>), an IDE interface for CF/IDE storage, and a flash ROM holding multiple TOS images. I boot from a 1 GB CompactFlash card over IDE, which is noticeably faster than an ACSI drive.</p>

 <h2>Peripherals in Use</h2>
 <ul>
@@ -31,26 +35,26 @@ parent: "/retro/"
 </ul>

 <h2>Role</h2>
-<p>Workstation machine with multitasking (Geneva), AltRAM, IDE/CF boot, USB and network connectivity, and high-resolution display. My primary system for programming and productive work.</p>
+<p>Workstation machine with multitasking (<a href="https://www.atari-wiki.com/index.php/NeoDesk">NeoDesk</a> 4.06 under Geneva), AltRAM, IDE/CF boot, USB and network connectivity, and high-resolution display. My primary system for programming and productive work.</p>

 <h2>Gallery</h2>
 <img src="high-1.jpg" alt="The Mega ST 4 High machine" width="640" height="640" loading="lazy">
-<p class="caption">The Mega ST 4 "High" workstation.</p>
+<p class="caption">The NeoDesk desktop showing 4 MB ST RAM and 8 MB AltRAM from the MonSTerBoard.</p>
 <img src="high-2.jpg" alt="Mega ST 4 High internal view" width="640" height="640" loading="lazy">
-<p class="caption">Inside the "High" machine.</p>
+<p class="caption">The workstation running GEMBench, with the original Atari keyboard and mouse.</p>
 <img src="high-3.jpg" alt="Mega ST 4 High detail" width="640" height="853" loading="lazy">
-<p class="caption">A detail of the "High" setup.</p>
+<p class="caption">GEMBench 6.31 results comparing the ST reference to the High machine at 1024x768 with 256 colors.</p>
 <img src="high-4.jpg" alt="Mega ST 4 High expansion" width="640" height="480" loading="lazy">
-<p class="caption">Expansion boards in the "High" machine.</p>
+<p class="caption">The complete setup in daylight, showing the GEM desktop on the EIZO FlexScan L365.</p>
 <img src="high-5.jpg" alt="Mega ST 4 High close-up" width="640" height="640" loading="lazy">
-<p class="caption">Close-up of the "High" machine.</p>
+<p class="caption">Geneva multitasking: qed, Sound Player, World Clock, and Memory usage running side by side.</p>
 <img src="high-6.jpg" alt="Mega ST 4 High running" width="640" height="480" loading="lazy">
-<p class="caption">The "High" machine in operation.</p>
+<p class="caption">A side view of the setup, showing the Cherry PS/2 keyboard, Logitech mouse via the Eiffel adapter, and the floppy drive.</p>
 <img src="high-7.jpg" alt="Mega ST 4 High setup" width="640" height="480" loading="lazy">
-<p class="caption">The "High" workstation setup.</p>
+<p class="caption">Geneva running Vision 3.5a and qed in parallel, with green ambient light behind the EIZO.</p>
 <img src="high-8.jpg" alt="Mega ST 4 High board" width="640" height="640" loading="lazy">
-<p class="caption">Board detail of the "High" machine.</p>
+<p class="caption">The NeoDesk Applications menu with Geneva Manager, JAnE, and Vision 3.5a, alongside the system spec file.</p>
 <img src="high-9.jpg" alt="Mega ST 4 High final" width="640" height="480" loading="lazy">
-<p class="caption">The finished "High" machine.</p>
+<p class="caption">The full workstation at night, driven by the MonSTerBoard, ET4000, and TOS 2.06.</p>

 </div>
@@ -11,6 +11,9 @@ parent: "/retro/"

 <p>Bought via eBay as a bargain, this Mega ST 4 is today my LowRes demo and gaming machine. It's the most heavily expanded of the fleet, but tuned for fast disk-image swapping rather than productivity.</p>

+<h2>Details</h2>
+<p>Serial: A1 08 4011143 · Manufactured August 1990</p>
+
 <h2>History and Repair</h2>
 <p>I had originally cut out the TOS ROMs to experiment with external solutions, and afterwards it was unclear whether the board had been damaged in the process. Moving the <a href="/retro/storm-cloudy/">Cloudy/Storm ST combo</a> to this machine via the MegaBus connector brought it back to stable operation. The actual problem turned out to be a poorly and incompletely soldered CPU socket.</p>

@@ -23,7 +26,17 @@ parent: "/retro/"
 <li><strong>Peripherals</strong>, a <a href="/retro/sidecartridge/">SidecarTridge Multi-device</a> on the ROM port, a <a href="/retro/atari-networking-bbs/">Wi-Fi modem</a> for dialing into BBSs, an original Atari keyboard with a <a href="/retro/mouster/">mouSTer</a> and USB mouse, and an <a href="/retro/atari-vga/">MCSWITCH</a> adapter for VGA output.</li>
 </ul>

+<h2>Booting</h2>
+<p>Switching between High Res and Low Res is done at the VGA adapter, not in software. The iTOS 1.04 boot options select which drive to boot from:</p>
+<ul>
+<li><strong>High Res</strong>, switch to EmuTOS on the Cloudy, then set the VGA adapter to Mono. Let it boot through.</li>
+<li><strong>Low Res</strong>, switch to iTOS 1.04i on the Cloudy, then set the VGA adapter to Color. At the boot prompt:</li>
+<li><strong>1 + Space</strong>, boot from <code>C:\BT\1</code>, opens D: GAMES</li>
+<li><strong>2 + Space</strong>, boot from <code>C:\BT\2</code>, opens E: DEMOS</li>
+<li><strong>3 + Space</strong>, boot from <code>C:\BT\3</code>, opens F: Med-Res</li>
+</ul>
+
 <h2>Role</h2>
-<p>Focused on LowRes demos and games, with convenient image handling via the Gotek and SidecarTridge. No need for complex productivity software or precise keyboard layouts here. The entire SD card has been cloned to the <a href="/retro/mistery-core/">MiSTery Core on the MIST</a> as a backup and for easy data transfer between the real machine and the FPGA.</p>
+<p>Focused on LowRes demos and games, with convenient image handling via the Gotek and SidecarTridge. The desktop environment is an original <strong>NeoDesk 3.0</strong> installation from the 1990s, just as it was back then. No need for complex productivity software or precise keyboard layouts here. The entire SD card has been cloned to the <a href="/retro/mistery-core/">MiSTery Core on the MIST</a> as a backup and for easy data transfer between the real machine and the FPGA.</p>

 </div>
@@ -14,6 +14,9 @@ parent: "/retro/"
 <h2>Current State</h2>
 <p>It runs on original TOS with the internal RAM configuration, without the separate 4 MB expansion, which was removed for testing purposes and now sits set aside.</p>

+<h2>Details</h2>
+<p>Serial: A1 7B 4010182 · Manufactured November 1987 · Board: CA200019 / C100167-001 Rev.5.0</p>
+
 <h2>History</h2>
 <p>Everything in this machine was moved over to the <a href="/retro/mega-st-high/">Mega ST 4 "High"</a> that I was given, including its original power supply. It's not really a parts donor though, it's simply the spare machine now that the new Mega 4 carries the main setup. Back then it had an intermittent fault: after being on for a long time it would eventually show a white screen on boot. I first suspected the 4 MB expansion and removed it, but the fault persisted. Only after reverting it to the old TOS and a fully original state did it run stably again.</p>

@@ -1,23 +1,56 @@
 ---
-title: "Mini Arcades and Handhelds: Sorting the Real Deal from the Bootlegs"
+title: "Handheld Emulation Devices: ODROID-GO, PocketGo and RG35XX"
 section: "retro"
 tags: "retro"
-description: "A buyer's guide to compact retro gaming devices, and why the cheapest option is almost never the right one."
+description: "Three handheld emulation devices for retro gaming on the move, from an ESP32-based ODROID-GO to a pocketable PocketGo and a powerful RG35XX."
 layout: base.njk
 parent: "/retro/"
 ---
-<h1>Mini Arcades and Handhelds: Sorting the Real Deal from the Bootlegs</h1>
+<h1>Handheld Emulation Devices: ODROID-GO, PocketGo and RG35XX</h1>
 <div class="detail-content">

-<p>The market for tiny plug-and-play arcade cabinets is full of traps. Some devices ship with genuinely licensed classics; others are dressed-up bootleg NES clones with unfamiliar Chinese ROM hacks pretending to be arcade games.</p>
+<p>For retro gaming away from a screen, I use three handheld emulation devices. Each one covers a different sweet spot in the trade-off between size, power and convenience. The key difference is what systems each one can actually emulate well, and how much effort it takes to get there.</p>

-<h2>What to Watch For</h2>
-<ul>
-<li><strong>The bootleg trap</strong>, devices built around VT369-style chips (NES-compatible, not real arcade hardware) often bundle 200+ "games" that turn out to be unlicensed clones and homebrew hacks, cataloged in enthusiast bootleg-game wikis. No Pac-Man, no Donkey Kong, just look-alikes.</li>
-<li><strong>Genuinely licensed compact options</strong>, devices built around real Namco or SNK licenses deliver actual classics (Pac-Man, Galaga, Dig Dug, dozens of Neo Geo titles) with premium displays, at a similar price point to the bootleg boxes.</li>
-<li><strong>Expandable options</strong>, some cabinet-style devices accept extra MAME ROMs via SD card, letting you add real arcade classics after the fact, the one feature the bootleg boxes almost never offer without heavy soldering.</li>
-<li><strong>The maximalist route</strong>, a Raspberry Pi running RetroPie, or a MiSTer FPGA setup, both scale to tens of thousands of games or hardware-accurate arcade cores respectively, at the cost of more setup effort.</li>
-</ul>
+<h2>ODROID-GO</h2>
+<p>The ODROID-GO by Hardkernel is a DIY handheld built around an ESP32 microcontroller. It has a 2.4-inch 320x240 TFT display, a speaker, D-pad, face buttons, shoulder buttons, a Micro SD card slot, and a built-in rechargeable battery. It runs the stock firmware, which loads games from the SD card. The ESP32 is a dual-core chip running at 240 MHz with 4 MB of PSRAM, which is enough for 8-bit systems but starts to struggle with anything heavier.</p>
+<p><strong>What it plays well:</strong> NES, Game Boy, Game Boy Color, Sega Master System, Sega Game Gear.</p>
+<p><strong>What it does not play well:</strong> Anything beyond 8-bit is not on there, and would not run well anyway.</p>
+<p><strong>Game packs:</strong> Full game packs for all supported systems are on the SD card. No need to pick and choose.</p>
+<p><strong>Why use it:</strong> The killer feature is instant-on. The ESP32 boots in literally no time, you switch it on and the game is right there. A stopped game can be picked up again straight away. No other device in the collection comes close to this. It is the smallest and cheapest of the three, and for pure 8-bit gaming it is surprisingly capable. It is the grab-and-go option when you just want to play some NES or Game Boy games on the couch.</p>
+<img src="odroid-go.jpg" alt="ODROID-GO system selection screen" width="640" height="480" loading="lazy">
+<p class="caption">The ODROID-GO showing the Retro-Go system selection screen.</p>

-<p class="note">If a mini-arcade's game list reads like a string of titles you've genuinely never heard of, that's the tell. Real arcade classics have instantly recognisable names, bootlegs hide behind vague, generic-sounding ones.</p>
+<h2>PocketGo</h2>
+<p>The original PocketGo by BittBoy is a handheld in a Game-Boy-Advance-style landscape form factor with a 2.4-inch IPS display at 320x240. It runs on an Allwinner F1C100S chip at 533 to 798 MHz with 32 MB of RAM. The community CFW 1.3 firmware (Miyoo CFW) replaces the stock software with GMenu2X as the frontend, adds support for more emulators, a screen tearing fix, theme customisation and better overall performance. The stock firmware works but is rough around the edges, with an inconsistent button mapping across emulators and a less polished menu. It has D-pad, four face buttons, shoulder buttons, and runs off a 1000 mAh battery.</p>
+<p><strong>What it plays well:</strong> Game Boy, Game Boy Color, Game Boy Advance, NES, Sega Genesis, Sega Master System. The GBA emulation is the real draw here, something the ODROID-GO cannot do.</p>
+<p><strong>What it does not play well:</strong> SNES is playable but not perfect, with occasional slowdowns. PlayStation, CPS1/CPS2/CPS3, Jaguar, Sega CD and Sega 32X are not possible.</p>
+<p><strong>Game packs:</strong> Full game packs for all supported systems are on the SD card.</p>
+<p><strong>Why use it:</strong> It is still pocketable, the IPS screen looks great, and it fills the gap between the ODROID-GO and the RG35XX. If you want Game Boy Advance on the go without carrying something bigger, this is the one. The CFW 1.3 firmware makes a real difference over the stock software.</p>
+<img src="PocketGo1.jpg" alt="PocketGo boot screen" width="640" height="480" loading="lazy">
+<p class="caption">The PocketGo booting into Miyoo CFW 1.3.</p>
+<img src="PocketGo2.jpg" alt="PocketGo system selection" width="640" height="480" loading="lazy">
+<p class="caption">The system selection screen on the PocketGo.</p>
+
+<h2>RG35XX</h2>
+<p>The RG35XX by Anbernic is the serious handheld of the three. It has a 3.5-inch IPS display at 640x480, an Allwinner H313 quad-core ARM Cortex-A53 chip, and significantly more power than the other two. It runs GarlicOS, a custom firmware by Black Seraph built on RetroArch. GarlicOS replaces the stock firmware with a much cleaner interface, adds a sleep mode that lets you resume exactly where you left off, RTC support, overclocking options, and a wider range of configurable emulators. The stock firmware works but is bare-bones and lacks these quality-of-life features. The build quality is noticeably better than the other two devices, with a sturdier feel and a screen that is both larger and sharper.</p>
+<p><strong>What it plays well:</strong> Everything the ODROID-GO and PocketGo do, plus SNES running perfectly, PlayStation 1, CPS1/CPS2/CPS3 arcade, Jaguar, Sega CD, Sega 32X, and Neo Geo. It also supports HDMI output to a TV.</p>
+<p><strong>What it does not play well:</strong> Nintendo 64 and PSP are hit-or-miss. Dreamcast is mostly too much for it.</p>
+<p><strong>Game packs:</strong> Only the major platforms have game packs installed. The smaller systems are not pre-loaded.</p>
+<p><strong>Why use it:</strong> When you want the full experience, including PlayStation and arcade games, or when you want to hook the handheld up to a TV. It is the heaviest and least pocketable of the three, but it covers the widest range of systems.</p>
+<img src="RG35xx1.jpg" alt="RG35XX boot screen" width="640" height="480" loading="lazy">
+<p class="caption">The RG35XX boot screen.</p>
+<img src="RG35xx2.jpg" alt="RG35XX GarlicOS version" width="640" height="480" loading="lazy">
+<p class="caption">GarlicOS version 1.4.9 running on the RG35XX.</p>
+<img src="RG35xx3.jpg" alt="RG35XX system selection" width="640" height="480" loading="lazy">
+<p class="caption">The system selection screen on the RG35XX.</p>
+
+<h2>Which One for What</h2>
+<table>
+<tr><th>Device</th><th>Best for</th><th>Games loaded</th><th>Screen</th></tr>
+<tr><td>ODROID-GO</td><td>NES, Game Boy, instant-on 8-bit</td><td>All systems</td><td>2.4" TFT</td></tr>
+<tr><td>PocketGo</td><td>Game Boy Advance, 16-bit on the go</td><td>All systems</td><td>2.4" IPS</td></tr>
+<tr><td>RG35XX</td><td>PlayStation, arcade, everything at home</td><td>Major platforms only</td><td>3.5" IPS</td></tr>
+</table>
+
+<p class="note">The market for tiny retro gaming handhelds is full of traps. If a device's game list reads like a string of titles you have never heard of, that is the tell. Real arcade classics have instantly recognisable names, bootlegs hide behind vague, generic-sounding ones. All three devices above run proper emulation firmware with real ROMs, not bootleg NES clones dressed up as something else.</p>
 </div>
@@ -24,7 +24,13 @@ parent: "/retro/"
 <p class="caption">The MiSTery Core configuration selection screen, showing all five available setups.</p>

 <h3>1. iTOS 1.04 (same as the Low)</h3>
-<p>The same setup as on the <a href="/retro/mega-st-low/">Mega ST 4 "Low"</a>. With iTOS, pressing a number key and then space during boot selects the boot drive: 1 boots from D (GAMES), 2 from E (DEMOS), 3 from F (Medium Resolution). Exactly the way I have it on the real machine.</p>
+<p>The same setup as on the <a href="/retro/mega-st-low/">Mega ST 4 "Low"</a>. With iTOS, the boot options select which drive to boot from:</p>
+<ul>
+<li><strong>1 + Space</strong>, boot from <code>C:\BT\1</code>, opens D: GAMES</li>
+<li><strong>2 + Space</strong>, boot from <code>C:\BT\2</code>, opens E: DEMOS</li>
+<li><strong>3 + Space</strong>, boot from <code>C:\BT\3</code>, opens F: Med-Res</li>
+</ul>
+<p>Exactly the way I have it on the real machine.</p>

 <img src="itos1.jpg" alt="iTOS boot screen showing drive selection" width="640" height="640" loading="lazy">
 <p class="caption">The iTOS boot screen with the drive selection prompt.</p>
@@ -52,6 +52,14 @@ parent: "/retro/"
 <h2>My Setup</h2>
 <p>In my Mega ST 4 "High" machine the MonSTerBoard provides the 8 MB of TT-RAM that TOS 2.06 and Geneva use for real multitasking. For storage I use the dual IDE interface, booting the system directly from a CompactFlash card. I started with a 4 GB card, but that didn't work reliably, so I switched to a 1 GB card, which works fine. There's no ACSI hard drive connected in this machine; the IDE boot is noticeably faster than an ACSI drive would be. Combined with the <a href="/retro/et4000-experiment/">ET4000 graphics card</a> and its dedicated monitor, it's the most capable machine in the fleet.</p>

+<h2>Geneva and NeoDesk</h2>
+<p>Geneva and NeoDesk run together well on the MonSTerBoard, using the 8 MB of AltRAM. The two desktop modes can be switched without renaming any files:</p>
+<ul>
+<li><strong>Standard Desktop</strong>, the default TOS desktop.</li>
+<li><strong>Geneva</strong>, start <code>auto\geneva.prg</code> with "G" and <code>auto\neoload.prg</code> also with "G". Rename <code>newdesk.inf</code> to <code>newdesk.inX</code> (with an X instead of F).</li>
+</ul>
+<p>Geneva and NeoDesk can also be started directly from the desktop without renaming anything.</p>
+
 <h2>Gallery</h2>
 <img src="monster-ide.jpg" alt="MonSTerBoard IDE adapter with CompactFlash card" width="640" height="480" loading="lazy">
 <p class="caption">The MonSTerBoard IDE adapter with a CompactFlash card attached.</p>
@@ -21,6 +21,7 @@ parent: "/retro/"

 <h2>Real Internet with STinG</h2>
 <p>For networking I use the STinG TCP/IP stack together with the <code>enec.stx</code> (or <code>enec3.stx</code> for 68030) network card driver. Once configured, the Mega ST gets a real IP address on the network and can reach the internet, connecting the 1980s machine to modern services. The original NetUSBee was developed by Candle'O'Sin, and the current production runs are sold by Lotharek in a sturdy grey metal case that matches the Atari look.</p>
+<p>STinG MAC addresses on my machines: Mega ST 4 "High" <code>00:B7:F8:77:C6:B3</code>, MiST <code>A0:CE:C8:5D:9C:A2</code>.</p>

 <h2>Exchanging Data with Windows via USB</h2>
 <p>The USB port is particularly handy for data exchange. I use a FAT16-formatted USB stick, which the ST can read and write through the USB mass-storage driver. Because FAT16 is also readable on a modern Windows PC, I can transfer files between the Atari and a Windows machine just by moving the stick between them, no special cables or network tricks required.</p>
@@ -33,4 +34,15 @@ parent: "/retro/"
 <li><a href="https://www.jungsi.de/retro-atari-st-netusbee/" target="_blank">NetUSBee [Atari ST] - Jungsi's Corner (installation guide)</a></li>
 <li><a href="https://lotharek.pl/productdetail.php?id=46" target="_blank">Netusbee - Lotharek (order page, firmware and drivers)</a></li>
 </ul>
+
+<h2>WiFi SNTP Clock</h2>
+<p>A separate ESP module provides WiFi time synchronisation for the Atari ST. <a href="https://www.chzsoft.de/site/hardware/wifi-sntp-clock-for-the-atari-st-tt-falcon/" target="_blank">czietz's simple WiFi SNTP firmware</a> runs on the ESP and communicates with the Atari over a serial connection. Once connected, Connect95 can be used for serial communication, and WgetST can download files via HTTP, though it is limited to HTTP only.</p>
+
+<h2>Going online via proxy</h2>
+<p>With STinG configured and the network running, the next step is getting actual services accessible from the Atari. Two approaches work well:</p>
+<ul>
+<li><a href="https://github.com/atauenis/webone" target="_blank">WebOne</a>, a proxy server that translates HTTP requests so that a vintage browser like Cab can browse the web through it. Installation docs are on the <a href="https://github.com/atauenis/webone/wiki/Linux-installation" target="_blank">GitHub wiki</a>.</li>
+<li><a href="https://github.com/tenox7/wrp" target="_blank">Web Rendering Proxy (WRP)</a>, an alternative that renders pages server-side and serves them as images, useful when nothing else works with the old browser. Runs as a Docker container.</li>
+</ul>
+<p>Both run on a Linux machine on the same network, with the Atari pointing its browser proxy settings at that machine's IP. A Linux LXC container on the homelab can serve as a dedicated Atari internet proxy server for this purpose.</p>
 </div>
@@ -49,5 +49,5 @@ parent: "/retro/"
 <h2>How it all connects</h2>
 <p>All machines share the same network infrastructure, with FTP access to the NAS for file transfers. Disk images and software archives are stored centrally and served to individual machines as needed. The MiSTer and MiST both use SD cards for storage, while the original hardware uses CompactFlash adapters or SCSI-to-IDE bridges depending on the machine. The Raspberry Pi 400 accesses the same NFS shares as the other Pis in the flat.</p>

-<p class="note">The honest status update: several open items remain, documenting the exact handheld models, and the full-size <a href="/retro/the-a1200/">A1200</a> is on pre-order ahead of its 4 December 2026 launch. Retro computing, it turns out, is never really "done."</p>
+<p class="note">The <a href="/retro/the-a1200/">A1200</a> console is on pre-order ahead of its 4 December 2026 launch. Retro computing, it turns out, is never really "done."</p>
 </div>
@@ -39,6 +39,10 @@ parent: "/retro/"

 <h2>My Setup</h2>
 <p>The original Revision 0 SidecarTridge is in use on the Mega ST 4 "Low" machine. The new Revision 3 I've bought but not yet installed, so it's still sitting alongside the other uninstalled extensions until I decide where to use it.</p>
+<p>Future plan: fully wire the SidecarTridge and bring its buttons to the front of the case for easier access without having to reach into the cartridge slot area.</p>
+
+<h2>ROM and floppy emulation</h2>
+<p>ROM emulation works, but only partially with TOS 2.06 on the MonSTerBoard. Floppy emulation, on the other hand, works very well: floppy images can be created with HxC Floppy Emulator on Windows and transferred to the SidecarTridge, making it easy to move data between a modern PC and the Atari.</p>

 <h2>Sources</h2>
 <ul>
@@ -59,6 +59,7 @@ parent: "/retro/"
 <p>Geneva is a resource-friendly, self-contained multitasking environment for the Atari ST. It runs on top of normal TOS and replaces or extends GEM, letting several GEM programs and accessories run in parallel, even on older and weaker Atari models without a big performance hit. It needs little memory and stays very compatible with older software that was never written for multitasking, which is why I run it on the <a href="/retro/mega-st-high/">"High"</a> workstation.</p>
 <h3>MiNT</h3>
 <p>MiNT (originally "MiNT is Not TOS", later "MiNT is Now TOS") is a much more powerful, Unix-like replacement kernel. It swaps GEMDOS for a Unix-style memory and process management layer, and together with a graphical shell like XaAES or N.AES it enables true, modern multitasking, today usually known as FreeMiNT. The catch is that it often needs stronger hardware, ideally a processor with a memory-management unit (PMMU) such as the Motorola 68030 in the TT or Falcon, and tends to run slowly on a bare old ST. I haven't managed to get MiNT running reliably on any of my machines, which is exactly why the "High" machine uses Geneva instead.</p>
+<p>The iTOS 1.04i was bought from Peter Putnik for 20 EUR.</p>

 <h2>Sources</h2>
 <ul>
@@ -31,6 +31,8 @@ parent: "/retro/"

 <h2>My Setup</h2>
 <p>In my Mega ST 4 "Low" machine the UltraSatan Mini provides the hard-disk storage on an SD card, alongside the <a href="/retro/storm-cloudy/">Cloudy/Storm ST combo</a>, the <a href="/retro/gotek/">Gotek</a>, the <a href="/retro/sidecartridge/">SidecarTridge</a> and the <a href="/retro/atari-networking-bbs/">Wi-Fi modem</a>.</p>
+<p>The SD card is partitioned into 8 x 500 MB partitions, giving enough room for games, demos and tools without having to shuffle data around.</p>
+<p>The UltraSatan driver was bought from Peter Putnik for 15 EUR (I sent 20 EUR).</p>

 <h2>Sources</h2>
 <ul>
@@ -5,7 +5,7 @@
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>{{ title }}{% if 'moonweb' not in title and 'stefankoelle' not in title %} · moonweb.org{% endif %}</title>
  <meta name="description" content="{{ description }}">
-  <meta name="author" content="Stefan Kölle">
+  <meta name="author" content="Stefan Koelle">
  <meta name="theme-color" content="{% if section == 'hub' %}#3b6ea5{% elif section == 'infra' %}#99333A{% elif section == 'smarthome' %}#1f8a8a{% elif section == 'code' %}#3E5098{% elif section == 'retro' %}#8a6d3b{% else %}#3b6ea5{% endif %}">
  <link rel="canonical" href="{{ site.url }}{{ page.url }}">
  <meta property="og:title" content="{{ title }}{% if 'moonweb' not in title and 'stefankoelle' not in title %} · moonweb.org{% endif %}">
@@ -18,9 +18,6 @@
  <meta name="twitter:title" content="{{ title }}{% if 'moonweb' not in title and 'stefankoelle' not in title %} · moonweb.org{% endif %}">
  <meta name="twitter:description" content="{{ description }}">
  {% if ogImage %}<meta name="twitter:image" content="{{ site.url }}{{ ogImage }}">{% endif %}
-  <link rel="preconnect" href="https://fonts.googleapis.com">
-  <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
-  <link href="https://fonts.googleapis.com/css2?family=Lobster&display=swap" rel="stylesheet">
  <link rel="icon" href="{% if section and section != 'hub' %}/{{ section }}/favicon.svg{% else %}/favicon.svg{% endif %}">
  <link rel="stylesheet" href="/shared-base.css">
  <style>:root { --accent: {% if section == 'infra' %}#99333A{% elif section == 'smarthome' %}#1f8a8a{% elif section == 'code' %}#3E5098{% elif section == 'retro' %}#8a6d3b{% else %}#3b6ea5{% endif %}; }</style>
@@ -36,7 +33,7 @@
    {% else %}
    "name": "{{ title | safe }}{% if 'moonweb' not in title and 'stefankoelle' not in title %} · moonweb.org{% endif %}",
    "url": "{{ site.url }}",
-    "author": { "@type": "Person", "name": "Stefan Kölle" }
+    "author": { "@type": "Person", "name": "Stefan Koelle" }
    {% endif %}
  }
  </script>
@@ -45,7 +42,7 @@
  {
    "@context": "https://schema.org",
    "@type": "Person",
-    "name": "Stefan Kölle",
+    "name": "Stefan Koelle",
    "url": "https://www.moonweb.org",
    "image": "https://www.moonweb.org/stefan-koelle-foto.jpg",
    "jobTitle": "Senior Software Developer & Architect",
@@ -10,6 +10,14 @@

 * { box-sizing: border-box; }

+@font-face {
+  font-family: 'Lobster';
+  font-style: normal;
+  font-weight: 400;
+  font-display: swap;
+  src: url('fonts/lobster-latin.woff2') format('woff2');
+}
+
 body {
  margin: 0;
  font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;
@@ -14,9 +14,6 @@
  <meta name="twitter:title" content="{{ title }} · {{ siteTitle | default("moonweb.org") }}">
  <meta name="twitter:description" content="{{ description }}">
  <link rel="icon" href="/favicon.svg" type="image/svg+xml">
-  <link rel="preconnect" href="https://fonts.googleapis.com">
-  <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
-  <link href="https://fonts.googleapis.com/css2?family=Lobster&display=swap" rel="stylesheet">
  <link rel="stylesheet" href="/shared-base.css">
  <link rel="stylesheet" href="/theme.css">
 </head>
@@ -5,7 +5,7 @@
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <meta name="theme-color" content="#ffffff">
-  <title>{% if title %}{{ title }}{% else %}Stefan Kölle{% endif %}</title>
+  <title>{% if title %}{{ title }}{% else %}Stefan Koelle{% endif %}</title>
  <meta name="description" content="{{ description }}">
  <link rel="apple-touch-icon" sizes="57x57" href="/assets/apple-icon-57x57.png">
  <link rel="apple-touch-icon" sizes="60x60" href="/assets/apple-icon-60x60.png">
@@ -25,7 +25,7 @@
  <meta name="msapplication-TileColor" content="#ffffff">
  <meta name="msapplication-TileImage" href="/assets/ms-icon-144x144.png">
  <link rel="canonical" href="{{ site.url }}{{ page.url }}">
-  <meta name="author" content="Stefan Kölle">
+  <meta name="author" content="Stefan Koelle">
  <meta property="og:title" content="{{ title }}">
  <meta property="og:description" content="{{ description }}">
  <meta property="og:url" content="{{ site.url }}{{ page.url }}">
@@ -39,7 +39,7 @@
  {
    "@context": "https://schema.org",
    "@type": "Person",
-    "name": "Stefan Kölle",
+    "name": "Stefan Koelle",
    "url": "{{ site.url }}",
    "jobTitle": "Software Developer",
    "sameAs": [
@@ -84,7 +84,7 @@
      </div>

      <div id="head">
-        <div id="foto"><img src="/assets/stefan-koelle-foto.jpg" alt="Photo of Stefan Kölle" style="width: 100%;"></div>
+        <div id="foto"><img src="/assets/stefan-koelle-foto.jpg" alt="Photo of Stefan Koelle" style="width: 100%;"></div>
      </div>

      <div id="background-image"></div>
@@ -1,5 +1,5 @@
 {
- "name": "Stefan Kölle",
+ "name": "Stefan Koelle",
 "short_name": "SK",
 "icons": [
  {
@@ -3,7 +3,7 @@
 <head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
-  <title>CV - Stefan Kölle</title>
+  <title>CV - Stefan Koelle</title>
 </head>
 <body>
  <div id="container">
@@ -14,7 +14,7 @@
          Senior Software Developer & Software&nbsp;Architect
        </div>
        <div id="headline-photo">
-          <img src="../assets/stefan-koelle-foto.jpg" alt="Stefan Kölle">
+          <img src="../assets/stefan-koelle-foto.jpg" alt="Stefan Koelle">
        </div>
      </div>
      {% include "cv-content.njk" %}
@@ -7,6 +7,7 @@ module.exports = function (eleventyConfig) {
  eleventyConfig.addPassthroughCopy({ "stefankoelle/.htaccess": ".htaccess" });
  eleventyConfig.addPassthroughCopy({ "stefankoelle/pdf/cv.pdf": "pdf/cv.pdf" });
  eleventyConfig.addPassthroughCopy({ "shared/base.css": "shared-base.css" });
+  eleventyConfig.addPassthroughCopy({ "shared/fonts/lobster-latin.woff2": "fonts/lobster-latin.woff2" });
  eleventyConfig.addPassthroughCopy({ "shared/theme-hub.css": "theme.css" });
  eleventyConfig.addPassthroughCopy({ "shared/favicon/hub.svg": "favicon.svg" });

@@ -1,5 +1,5 @@
 ---
-title: "Stefan Kölle"
+title: "Stefan Koelle"
 description: "Experienced Senior Software Developer and Software Architect with over 20 years of experience. Specialized in .NET and Kubernetes, with hands-on experience in AI-assisted development using Claude Code."
 layout: stefankoelle.njk
 ---
@@ -8,7 +8,7 @@ description: "WiFi-controlled LED display solution with REST API, DHT22 sensor,
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="{{ description }}">
-  <meta name="author" content="Stefan Kölle">
+  <meta name="author" content="Stefan Koelle">
  <link rel="canonical" href="{{ site.url }}{{ page.url }}">
  <meta property="og:title" content="{{ title }}">
  <meta property="og:description" content="{{ description }}">
@@ -25,7 +25,7 @@ description: "WiFi-controlled LED display solution with REST API, DHT22 sensor,
    "@type": "Article",
    "headline": "{{ title }}",
    "description": "{{ description }}",
-    "author": { "@type": "Person", "name": "Stefan Kölle" },
+    "author": { "@type": "Person", "name": "Stefan Koelle" },
    "url": "{{ site.url }}{{ page.url }}"
  }
  </script>
@@ -7,6 +7,20 @@
 	<meta name="description" content="Explore three Pascal demo programs showcasing graphics, animation, and sound capabilities using Turbo Pascal and assembler. Learn about text and graphics animation, sound integration, and user interaction in Pascal programming.">
 	<link rel="canonical" href="https://www.moonweb.org/tcm/" />
    <style>
+		@font-face {
+			font-family: 'VT323';
+			font-style: normal;
+			font-weight: 400;
+			font-display: swap;
+			src: url('fonts/vt323-latin.woff2') format('woff2');
+		}
+		@font-face {
+			font-family: 'Press Start 2P';
+			font-style: normal;
+			font-weight: 400;
+			font-display: swap;
+			src: url('fonts/pressstart2p-latin.woff2') format('woff2');
+		}
        body {
            background-color: black;
            color: #FFF741;
@@ -14,10 +28,15 @@
            justify-content: center;
            align-items: center;
            flex-direction: column;
-            font-family: Arial, sans-serif;
+            font-family: 'VT323', monospace;
            margin: 0;
            padding: 0;
-            font-size: 18px; /* Schriftgröße des Textes */
+            font-size: 20px;
+            text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;
+        }
+        h1, h2 {
+            font-family: 'Press Start 2P', cursive;
+            font-size: 1em;
        }
        .container {
            text-align: center;
@@ -100,20 +119,27 @@
            text-decoration: none;
            cursor: pointer;
        }
-		table {
-			border:0px;
-			border-color:#000000;
-		}
-		th {
-			text-align:left;
-		}
-		td {
+		th, td {
 			text-align:left;
+			vertical-align: top;
+			padding-right: 20px;
+			overflow-wrap: break-word;
 		}
 		@media (max-width: 768px) {
 			#logo {
 				width:100%
 			}
+			table tr {
+				display: flex;
+				flex-direction: column;
+				margin-bottom: 0.8em;
+			}
+			table td {
+				padding-right: 0;
+			}
+			table td:first-child {
+				margin-bottom: 0.2em;
+			}
 		}
 		.footer {
 			font-size: 0.9em;
@@ -130,8 +156,9 @@
        <div class="logo">
            <img id="logo" src="logo.png" alt="TranceMission Logo">
        </div>
+        <h1>TranceMission Archive</h1>
        <div class="intro">
-			<p>TranceMission is a group known for creating demos and intros, primarily in the early 1990s. These demos often showcased advanced graphics, sound, and programming techniques using Turbo Pascal and assembler. The group was led by Stefan Koelle, who was responsible for coding, graphics, and music. TranceMission's work was characterized by creative animations, sound effects, and interactive elements, making them a notable name in the demo scene of that era. Their productions were designed to run on DOS-based PCs, often pushing the hardware capabilities of the time.</p>
+			<p>TranceMission is a group known for creating demos and intros, primarily in the early 1990s. These demos often showcased advanced graphics, sound, and programming techniques using Turbo Pascal and assembler. The group was led by Stefan Koelle, who was responsible for coding, graphics, and music. TranceMission's work was characterized by creative animations, sound effects, and interactive elements, making it a notable name in the demo scene of that era. Their productions were designed to run on DOS-based PCs, often pushing the hardware capabilities of the time.</p>
 			<p>Source code can be found on GitHub <a href="https://github.com/skoelle/dos-tcm-intros" target="_blank">https://github.com/skoelle/dos-tcm-intros</a>.</p>
        </div>
        <div class="program">
@@ -143,30 +170,26 @@
                    <img src="play.png" alt="YouTube Logo" class="youtube-logo">
                </a>
            </div>
-			<p>This Pascal program is a demo that displays animated stars and text on the screen, along with playing sound effects.</p>
+			<p>This Pascal program is a demo that displays animated stars and text on the screen and plays sound effects.</p>
 			<table>
 				<tr>
-					<th>Component</th>
-					<th>Description</th>
-				</tr>
-				<tr>
-					<td>Initialization</td>
+					<td><b>Initialization</b></td>
 					<td>Sets up graphics mode and clears the screen.</td>
 				</tr>
 				<tr>
-					<td>Text Display</td>
-					<td>Uses <code>writeline</code> procedure to display text.</td>
+					<td><b>Text Display</b></td>
+					<td>Uses the writeline procedure to display text.</td>
 				</tr>
 				<tr>
-					<td>Animation</td>
+					<td><b>Animation</b></td>
 					<td>Animates stars moving across the screen.</td>
 				</tr>
 				<tr>
-					<td>Sound</td>
+					<td><b>Sound</b></td>
 					<td>Plays sound if a SoundBlaster card is detected.</td>
 				</tr>
 				<tr>
-					<td>User Interaction</td>
+					<td><b>User Interaction</b></td>
 					<td>Waits for a key press to exit the demo.</td>
 				</tr>
 			</table>
@@ -184,28 +207,24 @@
 			 <p>This Pascal program is a demo that displays animated text and graphics with sound effects.</p>
 				<table>
 					<tr>
-						<th>Component</th>
-						<th>Description</th>
-					</tr>
-					<tr>
-						<td>Initialization</td>
+						<td><b>Initialization</b></td>
 						<td>Sets up graphics mode and clears the screen.</td>
 					</tr>
 					<tr>
-						<td>Text Display</td>
-						<td>Uses <code>writeline</code> and <code>writeline2</code> procedures to display text.</td>
+						<td><b>Text Display</b></td>
+						<td>Uses the writeline and writeline2 procedures to display text.</td>
 					</tr>
 					<tr>
-						<td>Animation</td>
+						<td><b>Animation</b></td>
 						<td>Animates text using a sine wave effect. Speed is controlled by 'S' and 'A' keys.</td>
 					</tr>
 					<tr>
-						<td>Sound</td>
+						<td><b>Sound</b></td>
 						<td>Plays sound if a SoundBlaster card is detected. Volume is controlled by '+' and '-' keys.</td>
 					</tr>
 					<tr>
-						<td>User Interaction</td>
-						<td>Responds to key presses and exits on ESC, Enter, or Space key.</td>
+						<td><b>User Interaction</b></td>
+						<td>Exits when ESC, Enter, or Space is pressed.</td>
 					</tr>
 				</table>
        </div>
@@ -221,31 +240,27 @@
                </a>
                
            </div>
-		<p>This Pascal program is a demo that displays a menu with animated text and graphics, along with playing sound effects.</p>
+		<p>This Pascal program is a demo that displays a menu with animated text and graphics and plays sound effects.</p>
 		 <table>
 				<tr>
-					<th>Component</th>
-					<th>Description</th>
-				</tr>
-				<tr>
-					<td>Initialization</td>
+					<td><b>Initialization</b></td>
 					<td>Sets up graphics mode and clears the screen.</td>
 				</tr>
 				<tr>
-					<td>Text Display</td>
-					<td>Uses <code>writeline</code> procedure to display text.</td>
+					<td><b>Text Display</b></td>
+					<td>Uses the writeline procedure to display text.</td>
 				</tr>
 				<tr>
-					<td>Animation</td>
+					<td><b>Animation</b></td>
 					<td>Animates a logo and text with a wobble effect.</td>
 				</tr>
 				<tr>
-					<td>Sound</td>
+					<td><b>Sound</b></td>
 					<td>Plays sound if a SoundBlaster card is detected.</td>
 				</tr>
 				<tr>
-					<td>User Interaction</td>
-					<td>Allows navigation through a menu using the keyboard and exits the demo on specific key presses.</td>
+					<td><b>User Interaction</b></td>
+					<td>Allows navigation through a menu using the keyboard and exits the demo on the exit menu point.</td>
 				</tr>
 			</table>
        </div>
@@ -262,6 +277,51 @@
        <iframe class="lightbox-content" id="lightbox-video" width="560" height="315" src="" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
    </div>

+    <canvas id="starfield" style="position:fixed;top:0;left:0;width:100%;height:100%;z-index:-1;pointer-events:none;"></canvas>
+    <script>
+        (function() {
+            const canvas = document.getElementById('starfield');
+            const ctx = canvas.getContext('2d');
+            let w, h, scrollY = 0;
+            function resize() { w = canvas.width = window.innerWidth; h = canvas.height = window.innerHeight; }
+            resize();
+            window.addEventListener('resize', resize);
+            window.addEventListener('scroll', function() { scrollY = window.scrollY; }, { passive: true });
+
+            const layers = [
+                { count: 80, speed: 0.3, sizeMin: 0.5, sizeMax: 1.2, alpha: 0.4 },
+                { count: 50, speed: 0.7, sizeMin: 1.0, sizeMax: 2.0, alpha: 0.6 },
+                { count: 25, speed: 1.5, sizeMin: 1.5, sizeMax: 3.0, alpha: 0.9 },
+            ];
+            const stars = [];
+            for (const layer of layers) {
+                for (let i = 0; i < layer.count; i++) {
+                    stars.push({
+                        x: Math.random() * w,
+                        y: Math.random() * h,
+                        speed: layer.speed + Math.random() * 0.3,
+                        size: layer.sizeMin + Math.random() * (layer.sizeMax - layer.sizeMin),
+                        alpha: layer.alpha * (0.7 + Math.random() * 0.3),
+                    });
+                }
+            }
+
+            function draw() {
+                ctx.clearRect(0, 0, w, h);
+                for (const s of stars) {
+                    s.x += s.speed;
+                    if (s.x > w + 5) { s.x = -5; s.y = Math.random() * h; }
+                    const y = ((s.y - scrollY * 0.02) % h + h) % h;
+                    ctx.beginPath();
+                    ctx.arc(s.x, y, s.size, 0, Math.PI * 2);
+                    ctx.fillStyle = 'rgba(255,255,255,' + s.alpha + ')';
+                    ctx.fill();
+                }
+                requestAnimationFrame(draw);
+            }
+            draw();
+        })();
+    </script>
    <script>
        function openLightbox(src) {
            document.getElementById('lightbox-img').src = src;
Author	SHA1	Message	Date
stefankoelle	b34262e11f	Add chat-archive description	2026-09-17 16:45:17 +02:00
stefankoelle	17c01086b7	Update repos and CV from prebuild	2026-09-17 16:21:56 +02:00
stefankoelle	5e870d1466	Revert Kölle to Koelle in meta/title/alt tags for SEO, keep Kölle in visible text	2026-09-14 12:15:26 +02:00
stefankoelle	8d00f6d1fc	Retro: Add 28k8 BBS Archive card to Overview section	2026-09-13 23:44:49 +02:00
stefankoelle	51f8e0264d	TCM: Fix menu intro text	2026-09-13 23:33:43 +02:00
stefankoelle	0fa880683a	TCM: Fix text formulations, grammar and consistency	2026-09-13 23:30:38 +02:00
stefankoelle	bda845dd8e	TCM: Enable starfield on mobile	2026-09-13 23:27:20 +02:00
stefankoelle	6f3d6a1661	TCM: Add VT323/Press Start 2P fonts, rebuild tables, remove code tags, fix h1 size	2026-09-13 23:23:23 +02:00
stefankoelle	5f4b008545	Self-host Lobster font, remove Google Fonts calls from shared and stefankoelle	2026-09-13 23:15:49 +02:00
stefankoelle	5c1c6ed697	Self-host VT323 and Press Start 2P fonts, remove Google Fonts calls	2026-09-13 23:05:08 +02:00
stefankoelle	96a8a15e2b	Add video play overlay, fix text formulations, improve readability	2026-09-13 23:00:24 +02:00
stefankoelle	05cafca9fc	Stack table vertically on mobile for better readability	2026-09-13 22:55:44 +02:00
stefankoelle	a71ca2f536	Add VT323/Press Start 2P fonts, enable animations on mobile, fix mobile layout	2026-09-13 22:52:59 +02:00
stefankoelle	acd50bfdd8	Add copper bars background, fix mobile logo display, layout improvements	2026-09-13 22:38:24 +02:00
stefankoelle	b0943dd878	Add palette rotation animation to PHOBIA logo, improve layout and responsive design	2026-09-13 22:27:59 +02:00
stefankoelle	b817c54332	Add parallax starfield background to TCM archive page	2026-09-13 21:55:42 +02:00
stefankoelle	7d57de34d0	Add h1 heading to TCM archive page	2026-09-13 21:50:33 +02:00
stefankoelle	f76521c02d	Fix mega-st-high gallery captions: original Atari keyboard in image 2, Cherry PS/2 + Logitech in image 6	2026-09-13 18:47:43 +02:00
stefankoelle	46b9c1b64d	Fix mega-st-high gallery captions to match actual image content, add skoelle sync note to AGENTS.md	2026-09-13 18:44:32 +02:00
stefankoelle	da87f09bbc	Improve ET4000 data volume explanation with 32 KB buffer context	2026-09-13 12:05:02 +02:00
stefankoelle	de32ab0ace	Fix pixel and data volume ratios: 3.1x and 25x	2026-09-13 12:03:01 +02:00
stefankoelle	9f5462f365	Fix ISA bus reference: adapted ISA bus	2026-09-13 12:02:18 +02:00
stefankoelle	6c58e13ab1	Add GemBench screenshot to ET4000 page above results table	2026-09-13 11:57:08 +02:00
stefankoelle	3bb90af124	Add pixel comparison and NVDI note to ET4000 GemBench section	2026-09-13 11:51:36 +02:00
stefankoelle	265dfa7541	Add GemBench 6.31 results to ET4000 page	2026-09-13 11:40:59 +02:00
stefankoelle	09d78a5f7c	Expand RG35XX systems, clarify PocketGo limitations	2026-09-13 00:17:04 +02:00
stefankoelle	2905625748	Remove SNES and GBA from ODROID-GO weak points	2026-09-13 00:10:11 +02:00
stefankoelle	f344c7e26e	Fix ODROID-GO: stock firmware, instant-on, remove unsupported systems	2026-09-13 00:09:16 +02:00
stefankoelle	4b06544128	Add handheld device images and passthrough copy	2026-09-13 00:07:39 +02:00
stefankoelle	267aaa7986	Expand Miyoo CFW details: GMenu2X, screen tearing, themes	2026-09-13 00:03:25 +02:00
stefankoelle	51a6a349aa	Add GarlicOS details to RG35XX, clarify Miyoo CFW on PocketGo	2026-09-13 00:01:44 +02:00
stefankoelle	2f0b31ba7d	Rename handheld card on retro overview page	2026-09-13 00:00:29 +02:00
stefankoelle	2e349c2023	Add ODROID-GO, PocketGo, RG35XX to handheld page, remove open-items note	2026-09-12 23:53:03 +02:00
stefankoelle	e4ceebf7d7	Add future plan: SidecarTridge buttons to front	2026-09-12 23:38:52 +02:00
stefankoelle	9aff826b34	Add floppy drive swap to High machine work performed	2026-09-12 23:38:32 +02:00
stefankoelle	a956086ee4	Add DIY ACSI2STM kit info to acsi2stm page	2026-09-12 23:36:38 +02:00
stefankoelle	9c71487ad4	Add UltraSatan partition layout: 8x 500 MB	2026-09-12 23:34:26 +02:00
stefankoelle	9880766dbf	Add NeoDesk 3.0 on Low, NeoDesk 4.06 on High	2026-09-12 23:33:34 +02:00
stefankoelle	bafaff68bb	Add SkyLINE Productions card to retro DOS & PC section	2026-09-12 22:10:14 +02:00
stefankoelle	747f90eea9	Split Apple years: 2009-2017 pure Apple, 2017-2020 rebuild begins	2026-09-12 22:07:22 +02:00
stefankoelle	78190c02c0	Clarify iMac (.NET Mono), Synology/MQTT/ESP32 separate	2026-09-12 22:06:27 +02:00
stefankoelle	2b1ceb8215	Add Arduino/ESP32/MQTT/Synology to Apple years section	2026-09-12 22:04:51 +02:00
stefankoelle	e23f5884c0	Add homelab and smart home to 2020 revival section	2026-09-12 22:03:40 +02:00
stefankoelle	8227847ad4	Fix timeline dates: Linux 2000-2009, Apple 2009-2020	2026-09-12 22:01:03 +02:00
stefankoelle	880c4f6f58	Update 2009-2019 section: Apple years with Chromebook	2026-09-12 21:59:20 +02:00
stefankoelle	bb9b9a92ad	Add 2000-2010 Linux server years to timeline with timecapsule links	2026-09-12 21:56:19 +02:00
stefankoelle	d577bcb74b	Add DOSMENU and SkyLine links to timeline PC section	2026-09-12 21:52:46 +02:00
stefankoelle	7b4c127b4d	ESPRIT all uppercase	2026-09-12 21:51:44 +02:00
stefankoelle	9381720df3	Rename 'Esprit disk magazine' to 'Esprit releases'	2026-09-12 21:50:17 +02:00
stefankoelle	c49380350f	Rename to 'My Computer Timeline', add Atari ST releases link	2026-09-12 21:47:41 +02:00
stefankoelle	5bd222ee45	Add Esprit and ProTracker links to timeline Amiga section	2026-09-12 21:46:45 +02:00
stefankoelle	2784a78308	Add BBS and FidoNet links to timeline	2026-09-12 21:44:48 +02:00
stefankoelle	0148581e25	Remove Esprit and BGC News from timeline	2026-09-12 21:43:43 +02:00
stefankoelle	e9267b10d6	Update timeline: HX-20, correct C64/Atari/Amiga stories	2026-09-12 21:42:29 +02:00
stefankoelle	9f5b5680bd	Update timeline title to Atari ST, Amiga 500, DOS 486	2026-09-12 21:37:33 +02:00
stefankoelle	331bcb6b1f	Fix timeline title: remove Dell, use Chromebook	2026-09-12 21:35:21 +02:00
stefankoelle	febf94a1b8	Add computer timeline page with link from fleet overview and retro index	2026-09-12 21:34:15 +02:00
stefankoelle	70da09cd85	Add Peter Putnik purchase prices to UltraSatan, TOS and ACSI2STM pages	2026-09-12 21:12:30 +02:00
stefankoelle	b8558f3c20	Fix ET4000 VGA connection description: direct, not via adapter	2026-09-12 21:06:52 +02:00
stefankoelle	72bcc20b0c	Add VGA switch setup and DVI incompatibility note	2026-09-12 21:04:26 +02:00
stefankoelle	f29d843b5f	Add BBS details (Ignition, AnsiTerm, Atari BBS list) and networking (MAC, WiFi SNTP, WebOne, WRP, LXC proxy)	2026-09-12 21:00:29 +02:00
stefankoelle	83dd09cc19	Update MiSTery Core iTOS boot options to match Low page format	2026-09-12 20:56:49 +02:00
stefankoelle	3c3c521fab	Add boot procedure and iTOS start options to Mega ST Low page	2026-09-12 20:52:09 +02:00
stefankoelle	7bec25d1e9	Add Nova driver order, SidecarTridge ROM/floppy notes, Geneva/NeoDesk switching to monsterboard	2026-09-12 20:49:34 +02:00
stefankoelle	d9ee54d1d0	Add machine inventory with serial numbers and manufacturing dates to Atari fleet	2026-09-12 20:42:21 +02:00
stefankoelle	a3fe5d8048	Add MiSTer 486 screenshots to dos-486-tower page	2026-09-12 20:14:43 +02:00
stefankoelle	f956c8ec32	Fix 'Plattform' -> 'Platform' and 'LxC' -> 'LXC' in infra index	2026-09-12 17:49:57 +02:00