<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ghosting on Dev's Log</title><link>https://piot5.github.io/devs_log/tags/ghosting/</link><description>Recent content in Ghosting on Dev's Log</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 13 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://piot5.github.io/devs_log/tags/ghosting/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter Three: Ghost Monitors &amp; The EDID Void</title><link>https://piot5.github.io/devs_log/posts/chapter-three-ghost-monitors/</link><pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate><guid>https://piot5.github.io/devs_log/posts/chapter-three-ghost-monitors/</guid><description>REGISTRY LAYER (Persistent) SYSTEM\...\DISPLAY ↳ EDID (Cached Serial) ↳ InstanceID (GSM5B09...) Result: Identity Found GDI LAYER (Hardware) EnumDisplayMonitors() ❌ Detached: No HMONITOR ❌ DDC/CI: Fail (No Pulse) DISPLAYFLOW BRIDGE 1. scan.rs → Fetch Serial from Registry 2. synth.rs → Map InstanceID to Profile 3. Wake Up → ChangeDisplaySettingsExW Action: Create Live Handle After Wake: DDC/CI commands enabled THE EDID VOID: Identity vs. Accessibility In a perfect world, every monitor would always be reachable.</description></item></channel></rss>