Compare commits

...
18 Commits
Author SHA1 Message Date
stefankoelle 110173e357 Add moonweb.org and Smart Home links to LED matrix footer 2026-09-12 16:13:52 +02:00
stefankoelle 33793c9340 Fix double slashes in LED matrix URLs 2026-09-12 15:55:27 +02:00
stefankoelle 36e64f1899 Fix lang attribute, typos, and missing p-closing tags in phobia and tcm 2026-09-12 15:49:18 +02:00
stefankoelle b88e06a7f6 Add Legal Notice link to phobia and tcm footers 2026-09-12 15:39:15 +02:00
stefankoelle 90cdf6d0e4 Add footer with moonweb.org and Retro Corner links to phobia and tcm 2026-09-12 15:32:02 +02:00
stefankoelle 720e47e75e Fix CPU model in PHOBIA archive: DX50 -> DX2-66 2026-09-12 15:17:45 +02:00
stefankoelle 9988c5e47b Add PHOBIA and TranceMission archives as standalone sites with passthrough copy 2026-09-12 15:13:47 +02:00
stefankoelle dbb4d90306 Add deep links to MiSTery Core from MiST/MiSTer, Low, and retro snapshot 2026-09-12 13:38:27 +02:00
stefankoelle 0112b5a7b3 Fix timecapsule build output path: move assets out of src, fix passthrough and build script 2026-09-12 13:34:11 +02:00
stefankoelle 1e893e4d69 Add images to MiSTery Core page with passthrough copy 2026-09-12 13:17:33 +02:00
stefankoelle 14d210032d Add MiSTery Core on MIST page 2026-09-12 13:10:04 +02:00
stefankoelle fe315560d9 Add responsive image CSS, resize oversized images, fix aspect ratios, add lazy loading 2026-09-12 12:27:24 +02:00
stefankoelle 4c6c10b26e Fix terminal program note on Wi-Fi modem page 2026-09-12 12:15:20 +02:00
stefankoelle b072496639 Add Jungsi WiModem232 OLED mention and sources section to Wi-Fi modem page 2026-09-12 12:12:50 +02:00
stefankoelle 84c7c8a5a5 Move KAOS to High, add patched TOS 2.06 details, remove KAOS from Low 2026-09-12 12:11:36 +02:00
stefankoelle 67ae177de3 Restore Klyde link as only current order source for Eiffel 3 2026-09-12 12:10:04 +02:00
stefankoelle 76239f73fe Fix Eiffel source (Olivier Gossuin, not Klyde), add MCSWITCH price 2026-09-12 12:08:43 +02:00
stefankoelle fc133539d3 Swap bottom two Gotek gallery images, captions stay in place 2026-09-12 12:07:00 +02:00
117 changed files with 704 additions and 48 deletions
+5
View File
@@ -46,6 +46,11 @@ module.exports = function (eleventyConfig) {
eleventyConfig.addPassthroughCopy("retro/atari-vga/*.jpg"); eleventyConfig.addPassthroughCopy("retro/atari-vga/*.jpg");
eleventyConfig.addPassthroughCopy("retro/laser-mouse/*.jpg"); eleventyConfig.addPassthroughCopy("retro/laser-mouse/*.jpg");
eleventyConfig.addPassthroughCopy("retro/mega-st-high/*.jpg"); eleventyConfig.addPassthroughCopy("retro/mega-st-high/*.jpg");
eleventyConfig.addPassthroughCopy("retro/mistery-core/*.jpg");
// Standalone demo group archives (static HTML)
eleventyConfig.addPassthroughCopy("phobia/**");
eleventyConfig.addPassthroughCopy("tcm/**");
// Root-level shared assets // Root-level shared assets
eleventyConfig.addPassthroughCopy({ "shared/base.css": "shared-base.css" }); eleventyConfig.addPassthroughCopy({ "shared/base.css": "shared-base.css" });
+1 -1
View File
@@ -9,7 +9,7 @@
"dev:timecapsule": "cd timecapsule && npx @11ty/eleventy --serve --port=8087", "dev:timecapsule": "cd timecapsule && npx @11ty/eleventy --serve --port=8087",
"build": "npx @11ty/eleventy", "build": "npx @11ty/eleventy",
"build:stefankoelle": "mv .eleventyignore .eleventyignore.bak && npx @11ty/eleventy --config=stefankoelle/eleventy.config.js; mv .eleventyignore.bak .eleventyignore 2>/dev/null; true", "build:stefankoelle": "mv .eleventyignore .eleventyignore.bak && npx @11ty/eleventy --config=stefankoelle/eleventy.config.js; mv .eleventyignore.bak .eleventyignore 2>/dev/null; true",
"build:timecapsule": "cd timecapsule && npx @11ty/eleventy && mkdir -p ../dist/moonweb/timecapsule && cp -r _site/timecapsule/* ../dist/moonweb/timecapsule/", "build:timecapsule": "cd timecapsule && rm -r _site 2>/dev/null; npx @11ty/eleventy && rm -r ../dist/moonweb/timecapsule 2>/dev/null; mkdir -p ../dist/moonweb/timecapsule && cp -r _site/timecapsule/* ../dist/moonweb/timecapsule/",
"build:moonweb": "npm run build && npm run build:timecapsule", "build:moonweb": "npm run build && npm run build:timecapsule",
"pdf:cv": "bash stefankoelle/pdf/build-pdf.sh", "pdf:cv": "bash stefankoelle/pdf/build-pdf.sh",
"prebuild:cv": "bash prebuild.sh" "prebuild:cv": "bash prebuild.sh"
+269
View File
@@ -0,0 +1,269 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>PHOBIA DemoGroup Archive - Nostalgic PC Intros from 1994</title>
<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 {
background-color: #1a1a1a;
margin: 0;
color: #f0f0f0;
font-family: 'Arial', sans-serif;
line-height: 1.6;
}
.header {
display: flex;
align-items: center;
background-color: #000071;
padding-top:5px;
padding-left: 20px;
}
.header img {
margin-right: 20px;
}
.header a {
margin: 0 15px;
color: #518DAF;
text-decoration: none;
font-size: 1.2em;
}
.header a:hover {
color: #f0f0f0;
}
.content {
display: flex;
flex-wrap: wrap;
padding: 40px;
}
.program {
display: flex;
flex: 1 1 100%;
margin-bottom: 40px;
}
.program-image {
flex: 1 1 150px;
margin-right: 20px;
}
.program-image img {
width: 100%;
height: auto;
border-radius: 10px;
}
.program-description {
margin-top: 10px;
font-size: 1.1em;
}
.program-info {
flex: 2 1 300px;
}
.program-info h2 {
font-size: 2em;
margin-bottom: 10px;
}
.footer {
font-size: 0.9em;
text-align: center;
padding: 20px;
background-color: #333;
margin-top: 20px;
}
@media (max-width: 768px) {
h1 {
font-size: 1.7em;
}
.program-info h2 {
font-size: 1.5em;
margin-bottom: 10px;
}
.header img {
width: 100%;
}
.content {
flex-direction: column;
align-items: left;
}
.program {
flex-direction: column;
align-items: left;
}
.program-image {
margin-right: 0;
margin-bottom: 20px;
}
.program-info {
text-align: left;
}
}
th {
text-align:left;
}
a {
color:#00A6FF;
}
.lightbox {
display: none;
position: fixed;
top: 0;
left: 0;
width: 100%;
height: 100%;
background-color: rgba(0, 0, 0, 0.8);
justify-content: center;
align-items: center;
}
.lightbox-content {
position: relative;
width: 80%;
max-width: 800px;
}
.lightbox-content iframe {
width: 100%;
height: 450px;
}
.close {
position: absolute;
top: 10px;
right: 10px;
font-size: 30px;
color: #fff;
cursor: pointer;
}
</style>
<script>
function openLightbox() {
document.getElementById('lightbox').style.display = 'flex';
document.getElementById('video').src = 'https://www.youtube.com/embed/Cj3RgjVs5dk?autoplay=1';
}
function closeLightbox(event) {
if (event.target.id === 'lightbox' || event.target.className === 'close') {
document.getElementById('lightbox').style.display = 'none';
document.getElementById('video').src = '';
}
}
</script>
</head>
<body>
<div class="header">
<a href="index.html">
<img src="phobialogo.png" alt="PHOBIA">
</a>
</div>
<div class="content">
<div class="welcome">
<h1>Welcome to the 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>Feel free to explore and enjoy the nostalgia of the early days of PC intros.</p>
<p>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="program-description">
<p><b>Phobia Welcome Intro</b></p>
<p><a href="#" onclick="openLightbox()">YouTube Video of the Intro</a></p>
<p><a href="https://github.com/skoelle/dos-phobia-welcome-intro" target="_blank">GitHub Source Code</a></p>
</div>
</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>
<h2>Key Details:</h2>
<table>
<tr>
<th>Feature</th>
<th>Description</th>
</tr>
<tr>
<td>Programming Language</td>
<td>Turbo Pascal with inline assembler</td>
</tr>
<tr>
<td>Year</td>
<td>1994</td>
</tr>
<tr>
<td>Developer</td>
<td>Stefan Koelle</td>
</tr>
<tr>
<td>Development Machine</td>
<td>486 DX2-66 DOS PC</td>
</tr>
<tr>
<td>Graphics Technique</td>
<td>Color palette changes</td>
</tr>
<tr>
<td>Music Source</td>
<td>Old Amiga demo</td>
</tr>
<tr>
<td>Music Player</td>
<td>Public Mod-Player</td>
</tr>
<tr>
<td>Custom Font</td>
<td>Compiled into the executable as an object</td>
</tr>
<tr>
<td>Graphics Library</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>
</tr>
</table>
</div>
</div>
<!--
<div class="program">
<div class="program-image">
<img src="program2.jpg" alt="Program 2 Image">
<div class="program-description">
<p><b>Program 2</b></p>
<p>Kurze Beschreibung des zweiten Programms.</p>
</div>
</div>
<div class="program-info">
<h2>Program 2 Information</h2>
<p>Hier steht der Infotext zum zweiten Programm. Dieser Text enthält detaillierte Informationen über das Programm, seine Funktionen und andere relevante Details.</p>
</div>
</div>
<div class="program">
<div class="program-image">
<img src="program3.jpg" alt="Program 3 Image">
<div class="program-description">
<p><b>Program 3</b></p>
<p>Kurze Beschreibung des dritten Programms.</p>
</div>
</div>
<div class="program-info">
<h2>Program 3 Information</h2>
<p>Hier steht der Infotext zum dritten Programm. Dieser Text enthält detaillierte Informationen über das Programm, seine Funktionen und andere relevante Details.</p>
</div>
</div>-->
</div>
<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>
</div>
<div id="lightbox" class="lightbox" onclick="closeLightbox(event)">
<div class="lightbox-content">
<span class="close" onclick="closeLightbox()">&times;</span>
<iframe id="video" src="" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
</div>
</body>
</html>
BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB

BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.3 MiB

After

Width:  |  Height:  |  Size: 382 KiB

+1 -1
View File
@@ -27,7 +27,7 @@ parent: "/retro/"
<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 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>
<h2>Gallery</h2> <h2>Gallery</h2>
<img src="acsi2stm.jpg" alt="The ACSI2STM adapter" width="640" height="640"> <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 class="caption">The ACSI2STM adapter, not yet installed.</p>
<h2>Sources</h2> <h2>Sources</h2>
+11
View File
@@ -30,4 +30,15 @@ things it was never meant to do, and in experiencing the dial-up era's BBS
culture on original hardware, over Wi-Fi instead of a phone line.</p> culture on original hardware, over Wi-Fi instead of a phone line.</p>
<p class="note">If you're chasing BBS nostalgia on real hardware: budget far more patience for the networking layer than for the actual computer. The 1980s hardware is the easy part; convincing 2020s Wi-Fi and modern BBS ANSI dialects to cooperate is the real challenge.</p> <p class="note">If you're chasing BBS nostalgia on real hardware: budget far more patience for the networking layer than for the actual computer. The 1980s hardware is the easy part; convincing 2020s Wi-Fi and modern BBS ANSI dialects to cooperate is the real challenge.</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>
<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>
</ul>
</div> </div>
+2 -2
View File
@@ -12,7 +12,7 @@ parent: "/retro/"
<p>To get the Atari ST onto a modern monitor, I use RGB-to-VGA adapters. I have three of them: a passive MCSWITCH adapter on the "Low" machine, a self-built adapter on the "High" machine, and a newer active ST2VGA Enhanced that isn't in use yet.</p> <p>To get the Atari ST onto a modern monitor, I use RGB-to-VGA adapters. I have three of them: a passive MCSWITCH adapter on the "Low" machine, a self-built adapter on the "High" machine, and a newer active ST2VGA Enhanced that isn't in use yet.</p>
<h2>The MCSWITCH (Low machine)</h2> <h2>The MCSWITCH (Low machine)</h2>
<p>The <a href="/retro/atari-mega-st-fleet/">Mega ST 4 "Low"</a> uses an MCSWITCH adapter (ATARI Monochrome &amp; Color VGA Adapter) by Olivier Gossuin. It shows all three ST resolutions on a suitable VGA monitor, with a switch for mono and color. The version documented on <a href="http://www.albersdoerfer.de/erweiterungen/stvga.htm" target="_blank">albersdoerfer.de</a> also has an A/V connector and volume buttons, but mine is an older revision without the volume buttons and with a slightly different look. I can't find my exact version at Olivier's anymore, nor a newer one, so the adapter I have is a bit of a rare older revision.</p> <p>The <a href="/retro/atari-mega-st-fleet/">Mega ST 4 "Low"</a> uses an MCSWITCH adapter (ATARI Monochrome &amp; Color VGA Adapter) by Olivier Gossuin, bought directly from him in 2021 for 23 EUR. It shows all three ST resolutions on a suitable VGA monitor, with a switch for mono and color. The version documented on <a href="http://www.albersdoerfer.de/erweiterungen/stvga.htm" target="_blank">albersdoerfer.de</a> also has an A/V connector and volume buttons, but mine is an older revision without the volume buttons and with a slightly different look. I can't find my exact version at Olivier's anymore, nor a newer one, so the adapter I have is a bit of a rare older revision.</p>
<h2>The self-built adapter (High machine)</h2> <h2>The self-built adapter (High machine)</h2>
<p>The <a href="/retro/atari-mega-st-fleet/">Mega ST 4 "High"</a> uses a self-built adapter. I had to build my own because every off-the-shelf adapter blocks the VGA slot of the <a href="/retro/et4000-experiment/">ET4000</a> card, since both connectors sit at the same spot on the machine. My solution is a short cable leading to a small box, which carries the VGA connector and the mono/color switch, so the ET4000's own VGA output stays accessible. I followed the guide at <a href="https://pest.atari.org/www.logicsays.com/atari/mono/docs/atari_vga.htm" target="_blank">pest.atari.org</a> to build the RGB-to-VGA adapter itself.</p> <p>The <a href="/retro/atari-mega-st-fleet/">Mega ST 4 "High"</a> uses a self-built adapter. I had to build my own because every off-the-shelf adapter blocks the VGA slot of the <a href="/retro/et4000-experiment/">ET4000</a> card, since both connectors sit at the same spot on the machine. My solution is a short cable leading to a small box, which carries the VGA connector and the mono/color switch, so the ET4000's own VGA output stays accessible. I followed the guide at <a href="https://pest.atari.org/www.logicsays.com/atari/mono/docs/atari_vga.htm" target="_blank">pest.atari.org</a> to build the RGB-to-VGA adapter itself.</p>
@@ -24,7 +24,7 @@ parent: "/retro/"
<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> <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>Gallery</h2> <h2>Gallery</h2>
<img src="stvga-low.jpg" alt="The MCSWITCH VGA adapter connected to the Atari" width="640" height="640"> <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> <p class="caption">The MCSWITCH adapter on the Mega ST 4 "Low" machine.</p>
<h2>Sources</h2> <h2>Sources</h2>
Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.1 MiB

After

Width:  |  Height:  |  Size: 323 KiB

+2 -2
View File
@@ -22,7 +22,7 @@ parent: "/retro/"
</ul> </ul>
<h2>The version I use</h2> <h2>The version I use</h2>
<p>I use the <a href="https://klydes-korner.site/en/product/ps2-to-atari-eiffel-adapter-with-joysticks/" target="_blank">PS/2 Atari Eiffel adapter with joystick ports</a> from Klyde's Korner. This version connects to the keyboard port (RJ12) of an Atari Mega ST(E) or TT, and includes two joystick ports alongside the PS/2 keyboard and mouse. It's plug and play, comes pre-programmed with the latest firmware (v1.10.1Mq, which fixes a joystick firing problem), and needs no drivers. It connects via an RJ12 (6P6C) straight cable, and works with a native PS/2 keyboard and mouse or certain PS/2-compatible USB devices via a USB-to-PS/2 adapter.</p> <p>I have the <a href="https://www.eiffel-uno.com" target="_blank">Eiffel 3 for Mega ST, Mega STE and TT</a>, bought directly from Olivier Gossuin in 2021 for 18 EUR. As of 2026, the only place to still order one appears to be <a href="https://klydes-korner.site/en/product/ps2-to-atari-eiffel-adapter-with-joysticks/" target="_blank">Klyde's Korner</a>. This version connects to the keyboard port (RJ12) of an Atari Mega ST(E) or TT, and includes two joystick ports alongside the PS/2 keyboard and mouse. It's plug and play, comes pre-programmed with the latest firmware, and needs no drivers. It connects via an RJ12 (6P6C) straight cable, and works with a native PS/2 keyboard and mouse or certain PS/2-compatible USB devices via a USB-to-PS/2 adapter.</p>
<h2>Why use it</h2> <h2>Why use it</h2>
<p>Original Atari keyboards are getting rare and expensive. The Eiffel is a cheap, modern alternative that brings a standard PS/2 keyboard and mouse to the machine, along with the two joystick ports the original keyboard had. It also gives a much better typing feel: I use a Cherry PS/2 keyboard, which is far more pleasant to type on than the original, and a Logitech PS/2 mouse that tracks noticeably better than the original Atari STM1 mouse. It makes the workstation far more practical to use day to day. The older Eiffel versions were originally built and sold by Lyndon Amsdon, with the design documented on the <a href="https://hardware.atari.org/eiffel/index.htm" target="_blank">Atari Hardware Guide</a>, and the project history is covered in the <a href="https://wiki.newtosworld.de/index.php?title=Eiffel_Interface" target="_blank">Atari Wiki</a>.</p> <p>Original Atari keyboards are getting rare and expensive. The Eiffel is a cheap, modern alternative that brings a standard PS/2 keyboard and mouse to the machine, along with the two joystick ports the original keyboard had. It also gives a much better typing feel: I use a Cherry PS/2 keyboard, which is far more pleasant to type on than the original, and a Logitech PS/2 mouse that tracks noticeably better than the original Atari STM1 mouse. It makes the workstation far more practical to use day to day. The older Eiffel versions were originally built and sold by Lyndon Amsdon, with the design documented on the <a href="https://hardware.atari.org/eiffel/index.htm" target="_blank">Atari Hardware Guide</a>, and the project history is covered in the <a href="https://wiki.newtosworld.de/index.php?title=Eiffel_Interface" target="_blank">Atari Wiki</a>.</p>
@@ -31,7 +31,7 @@ parent: "/retro/"
<p>In my Mega ST 4 "High" machine the Eiffel connects the PS/2 keyboard and mouse, keeping the workstation fully usable alongside the <a href="/retro/monsterboard/">MonSTerBoard</a>, <a href="/retro/et4000-experiment/">ET4000</a> and <a href="/retro/netusb/">NetUSBee</a>. The original Atari keyboard is now used with the "Low" machine, which pairs it with a <a href="/retro/mouster/">mouSTer</a> and a USB mouse.</p> <p>In my Mega ST 4 "High" machine the Eiffel connects the PS/2 keyboard and mouse, keeping the workstation fully usable alongside the <a href="/retro/monsterboard/">MonSTerBoard</a>, <a href="/retro/et4000-experiment/">ET4000</a> and <a href="/retro/netusb/">NetUSBee</a>. The original Atari keyboard is now used with the "Low" machine, which pairs it with a <a href="/retro/mouster/">mouSTer</a> and a USB mouse.</p>
<h2>Gallery</h2> <h2>Gallery</h2>
<img src="eiffel-ps2.jpg" alt="The Eiffel PS/2 adapter without its case" width="480" height="640"> <img src="eiffel-ps2.jpg" alt="The Eiffel PS/2 adapter without its case" width="480" height="640" loading="lazy">
<p class="caption">The Eiffel PS/2 adapter, shown here without its case.</p> <p class="caption">The Eiffel PS/2 adapter, shown here without its case.</p>
<h2>Sources</h2> <h2>Sources</h2>
+5 -5
View File
@@ -32,19 +32,19 @@ parent: "/retro/"
<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> <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>
<h2>Gallery</h2> <h2>Gallery</h2>
<img src="et4000-1.jpg" alt="The ET4000 graphics card with STGA adapter" width="590" height="443"> <img src="et4000-1.jpg" alt="The ET4000 graphics card with STGA adapter" width="590" height="443" loading="lazy">
<p class="caption">The ET4000 graphics card ready for installation.</p> <p class="caption">The ET4000 graphics card ready for installation.</p>
<img src="et4000-2.jpg" alt="ET4000 card installed in the Mega ST" width="590" height="443"> <img src="et4000-2.jpg" alt="ET4000 card installed in the Mega ST" width="590" height="443" loading="lazy">
<p class="caption">The ET4000 installed in the Mega ST.</p> <p class="caption">The ET4000 installed in the Mega ST.</p>
<img src="et4000-3.jpg" alt="ET4000 card detail and wiring" width="590" height="443"> <img src="et4000-3.jpg" alt="ET4000 card detail and wiring" width="590" height="443" loading="lazy">
<p class="caption">Close-up of the card and its wiring.</p> <p class="caption">Close-up of the card and its wiring.</p>
<img src="et4000-4.jpg" alt="ET4000 running at higher resolution" width="590" height="443"> <img src="et4000-4.jpg" alt="ET4000 running at higher resolution" width="590" height="443" loading="lazy">
<p class="caption">The ET4000 driving a higher resolution desktop.</p> <p class="caption">The ET4000 driving a higher resolution desktop.</p>
<img src="et4000-5.jpg" alt="ET4000 final setup in the workstation" width="590" height="443"> <img src="et4000-5.jpg" alt="ET4000 final setup in the workstation" width="590" height="443" loading="lazy">
<p class="caption">The finished ET4000 setup in the workstation.</p> <p class="caption">The finished ET4000 setup in the workstation.</p>
<h2>Sources</h2> <h2>Sources</h2>
Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.5 MiB

After

Width:  |  Height:  |  Size: 350 KiB

+3 -3
View File
@@ -34,11 +34,11 @@ parent: "/retro/"
<p>For the internal mount I printed a <a href="https://www.thingiverse.com/thing:2664753" target="_blank">Gotek case from Thingiverse</a> that fits in the floppy bay. I used this to relocate the Storm/Cloudy TOS switcher: the 2-way switch is mounted in a slot at the front of the printed case, right where the floppy opening is. So the TOS switcher now sits at the front of the floppy bay, which meant no drilling into the case at all, and there was already space there for it.</p> <p>For the internal mount I printed a <a href="https://www.thingiverse.com/thing:2664753" target="_blank">Gotek case from Thingiverse</a> that fits in the floppy bay. I used this to relocate the Storm/Cloudy TOS switcher: the 2-way switch is mounted in a slot at the front of the printed case, right where the floppy opening is. So the TOS switcher now sits at the front of the floppy bay, which meant no drilling into the case at all, and there was already space there for it.</p>
<h2>Gallery</h2> <h2>Gallery</h2>
<img src="gotek-switch-2.jpg" alt="The relocated TOS switcher at the front of the Gotek case" width="640" height="640"> <img src="gotek-switch-2.jpg" alt="The relocated TOS switcher at the front of the Gotek case" width="640" height="640" loading="lazy">
<p class="caption">The relocated TOS switcher at the front of the printed Gotek case, a clear view of how it sits in the floppy bay.</p> <p class="caption">The relocated TOS switcher at the front of the printed Gotek case, a clear view of how it sits in the floppy bay.</p>
<img src="gotek-switch.jpg" alt="Gotek with the relocated TOS switcher in the printed case" width="640" height="480"> <img src="gotek-back.jpg" alt="Gotek floppy emulator rear view" width="640" height="480" loading="lazy">
<p class="caption">The Gotek in the 3D-printed case, with the relocated TOS switcher visible at the front.</p> <p class="caption">The Gotek in the 3D-printed case, with the relocated TOS switcher visible at the front.</p>
<img src="gotek-back.jpg" alt="Gotek floppy emulator rear view" width="640" height="480"> <img src="gotek-switch.jpg" alt="Gotek with the relocated TOS switcher in the printed case" width="640" height="480" loading="lazy">
<p class="caption">The Gotek rear view.</p> <p class="caption">The Gotek rear view.</p>
<h2>Sources</h2> <h2>Sources</h2>
+9
View File
@@ -73,6 +73,9 @@ sections:
- title: "🔌 Wi-Fi Modem & BBS" - title: "🔌 Wi-Fi Modem & BBS"
summary: "Dialing into telnet bulletin board systems from the Mega ST 4 'Low' using dhansel's WifiModem and terminal software." summary: "Dialing into telnet bulletin board systems from the Mega ST 4 'Low' using dhansel's WifiModem and terminal software."
href: "/retro/atari-networking-bbs/" href: "/retro/atari-networking-bbs/"
- title: "🧩 MiSTery Core on MIST"
summary: "Cloning the Low's SD card to the MIST FPGA for direct SD access, five configurations and a backup plan if the real Mega ST breaks."
href: "/retro/mistery-core/"
- heading: "Amiga Corner" - heading: "Amiga Corner"
cards: cards:
- title: "⚔️ Vampire, A600GS or MiSTer" - title: "⚔️ Vampire, A600GS or MiSTer"
@@ -103,6 +106,12 @@ sections:
- title: "💻 The 486 DX2-66" - title: "💻 The 486 DX2-66"
summary: "Rebuilding a DOS era from memory on MiSTer FPGA, recreating the environment the way it felt back then." summary: "Rebuilding a DOS era from memory on MiSTer FPGA, recreating the environment the way it felt back then."
href: "/retro/dos-486-tower/" href: "/retro/dos-486-tower/"
- title: "👾 PHOBIA DemoGroup Archive"
summary: "The PHOBIA DemoGroup Archive, showcasing 1994 PC intros including the Phobia Welcome Intro, written in Turbo Pascal."
href: "/phobia/"
- title: "🎵 TranceMission Archive"
summary: "TranceMission demos and intros from 1992-1995, programmed in Turbo Pascal with assembler on DOS PCs."
href: "/tcm/"
- heading: "Overview" - heading: "Overview"
cards: cards:
- title: "🏠 The Retro Corner Today" - title: "🏠 The Retro Corner Today"
+1 -1
View File
@@ -29,7 +29,7 @@ parent: "/retro/"
<p>The original STM-1 mouse is a classic, but the original sensors are getting tired after decades, and the feel isn't great compared to modern pointing devices. The laser board keeps the authentic Atari mouse shell while making it genuinely usable again, which is a nice middle ground between the original mouse and something like the <a href="/retro/mouster/">mouSTer</a> with a modern USB mouse.</p> <p>The original STM-1 mouse is a classic, but the original sensors are getting tired after decades, and the feel isn't great compared to modern pointing devices. The laser board keeps the authentic Atari mouse shell while making it genuinely usable again, which is a nice middle ground between the original mouse and something like the <a href="/retro/mouster/">mouSTer</a> with a modern USB mouse.</p>
<h2>Gallery</h2> <h2>Gallery</h2>
<img src="lasermouse.jpg" alt="The converted Atari STM-1 laser mouse" width="640" height="853"> <img src="lasermouse.jpg" alt="The converted Atari STM-1 laser mouse" width="640" height="853" loading="lazy">
<p class="caption">The original Atari STM-1 mouse converted to a laser sensor.</p> <p class="caption">The original Atari STM-1 mouse converted to a laser sensor.</p>
<h2>Sources</h2> <h2>Sources</h2>
Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.8 MiB

After

Width:  |  Height:  |  Size: 275 KiB

Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 3.9 MiB

After

Width:  |  Height:  |  Size: 869 KiB

Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.2 MiB

After

Width:  |  Height:  |  Size: 325 KiB

Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.4 MiB

After

Width:  |  Height:  |  Size: 481 KiB

Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.5 MiB

After

Width:  |  Height:  |  Size: 196 KiB

Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.7 MiB

After

Width:  |  Height:  |  Size: 621 KiB

Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.9 MiB

After

Width:  |  Height:  |  Size: 243 KiB

Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.9 MiB

After

Width:  |  Height:  |  Size: 220 KiB

Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.6 MiB

After

Width:  |  Height:  |  Size: 574 KiB

Executable → Regular
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.3 MiB

After

Width:  |  Height:  |  Size: 224 KiB

+11 -11
View File
@@ -2,7 +2,7 @@
title: "Mega ST 4 High: The Workstation" title: "Mega ST 4 High: The Workstation"
section: "retro" section: "retro"
tags: "retro" tags: "retro"
description: "The high-end Mega ST 4 workstation with MonSTerBoard, ET4000, NetUSBee, Eiffel interface and a modern STPSU, running Geneva." description: "The high-end Mega ST 4 workstation with MonSTerBoard, ET4000, NetUSBee, Eiffel interface, a modern STPSU and patched TOS 2.06, running Geneva."
layout: base.njk layout: base.njk
parent: "/retro/" parent: "/retro/"
--- ---
@@ -20,7 +20,7 @@ parent: "/retro/"
</ul> </ul>
<h2>MonSTerBoard</h2> <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. It 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 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> <h2>Peripherals in Use</h2>
<ul> <ul>
@@ -34,23 +34,23 @@ parent: "/retro/"
<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 (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> <h2>Gallery</h2>
<img src="high-1.jpg" alt="The Mega ST 4 High machine" width="640" height="640"> <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 Mega ST 4 "High" workstation.</p>
<img src="high-2.jpg" alt="Mega ST 4 High internal view" width="640" height="640"> <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">Inside the "High" machine.</p>
<img src="high-3.jpg" alt="Mega ST 4 High detail" width="640" height="640"> <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">A detail of the "High" setup.</p>
<img src="high-4.jpg" alt="Mega ST 4 High expansion" width="640" height="640"> <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">Expansion boards in the "High" machine.</p>
<img src="high-5.jpg" alt="Mega ST 4 High close-up" width="640" height="640"> <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">Close-up of the "High" machine.</p>
<img src="high-6.jpg" alt="Mega ST 4 High running" width="640" height="640"> <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">The "High" machine in operation.</p>
<img src="high-7.jpg" alt="Mega ST 4 High setup" width="640" height="640"> <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">The "High" workstation setup.</p>
<img src="high-8.jpg" alt="Mega ST 4 High board" width="640" height="640"> <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">Board detail of the "High" machine.</p>
<img src="high-9.jpg" alt="Mega ST 4 High final" width="640" height="640"> <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 finished "High" machine.</p>
</div> </div>
+2 -2
View File
@@ -17,13 +17,13 @@ parent: "/retro/"
<h2>Hardware Configuration</h2> <h2>Hardware Configuration</h2>
<ul> <ul>
<li><strong>CPU</strong>, 68000 with socket, plus the <a href="/retro/storm-cloudy/">Cloudy/Storm ST combo</a> via the MegaBus adapter.</li> <li><strong>CPU</strong>, 68000 with socket, plus the <a href="/retro/storm-cloudy/">Cloudy/Storm ST combo</a> via the MegaBus adapter.</li>
<li><strong>TOS/Flash</strong>, Cloudy as the TOS switcher/flash solution with EmuTOS and PP's improved iTOS 1.04, plus KAOS TOS installed as well (though rarely used).</li> <li><strong>TOS/Flash</strong>, Cloudy as the TOS switcher/flash solution with EmuTOS and PP's improved iTOS 1.04.</li>
<li><strong>RAM</strong>, 4 MB onboard ST-RAM plus 8 MB AltRAM via the Storm ST.</li> <li><strong>RAM</strong>, 4 MB onboard ST-RAM plus 8 MB AltRAM via the Storm ST.</li>
<li><strong>Mass storage</strong>, a <a href="/retro/gotek/">Gotek floppy emulator</a> in a 3D-printed case and an <a href="/retro/ultrasatan/">UltraSatan</a> ACSI-SD emulator.</li> <li><strong>Mass storage</strong>, a <a href="/retro/gotek/">Gotek floppy emulator</a> in a 3D-printed case and an <a href="/retro/ultrasatan/">UltraSatan</a> ACSI-SD emulator.</li>
<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> <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> </ul>
<h2>Role</h2> <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.</p> <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>
</div> </div>
+1 -1
View File
@@ -13,7 +13,7 @@ parent: "/retro/"
<h2>Division of Labour</h2> <h2>Division of Labour</h2>
<ul> <ul>
<li><strong>MiST for Atari ST</strong>, older and more limited in scope than MiSTer, but its ST/STE core is rock solid. It's the default choice for anything Atari, paired with a network-capable configuration for file transfers.</li> <li><strong>MiST for Atari ST</strong>, older and more limited in scope than MiSTer, but its ST/STE core is rock solid. It's the default choice for anything Atari, paired with a network-capable configuration for file transfers. I also run the <a href="/retro/mistery-core/">MiSTery Core</a> on it as a full backup for the <a href="/retro/mega-st-low/">Mega ST 4 "Low"</a>, with the entire SD card cloned from the UltraSatan.</li>
<li><strong>MiSTer for everything else</strong>, Amiga, DOS (via the AO486 core), and a huge library of other systems. Its Atari ST core, oddly, is the less reliable one of the two boards, reason enough to keep MiST around instead of retiring it.</li> <li><strong>MiSTer for everything else</strong>, Amiga, DOS (via the AO486 core), and a huge library of other systems. Its Atari ST core, oddly, is the less reliable one of the two boards, reason enough to keep MiST around instead of retiring it.</li>
<li><strong>Native resolution ceiling</strong>, both boards only emulate the original Shifter chip on Atari ST: Low-Res (320×200), Medium-Res (640×200), and High-Res (640×400 mono). No ET4000-style graphics card emulation is on the table; a Falcon030 core with higher native resolutions has been rumoured for years without shipping.</li> <li><strong>Native resolution ceiling</strong>, both boards only emulate the original Shifter chip on Atari ST: Low-Res (320×200), Medium-Res (640×200), and High-Res (640×400 mono). No ET4000-style graphics card emulation is on the table; a Falcon030 core with higher native resolutions has been rumoured for years without shipping.</li>
<li><strong>Known rough edges</strong>, accessory programs loading but not appearing on the desktop, and disabled XBOOT support, are still open items to chase down on the MiST side.</li> <li><strong>Known rough edges</strong>, accessory programs loading but not appearing on the desktop, and disabled XBOOT support, are still open items to chase down on the MiST side.</li>
+62
View File
@@ -0,0 +1,62 @@
---
title: "MiSTery Core on MIST: An FPGA Backup for the Mega ST 4"
section: "retro"
tags: "retro"
description: "Running the MiSTery Core on the MIST FPGA board as a preserve for the Mega ST 4 Low, with five configurations from original TOS to Viking graphics."
layout: base.njk
parent: "/retro/"
---
<h1>MiSTery Core on MIST: An FPGA Backup for the Mega ST 4</h1>
<div class="detail-content">
<p>After getting the <a href="/retro/mega-st-low/">Mega ST 4 "Low"</a> fully configured, I cloned its entire UltraSatan SD card for the <a href="/retro/mist-mister-fpga/">MIST</a> FPGA board. The MiSTery Core on the MIST can access SD cards directly, so every partition from the UltraSatan is available right away, no HDD images needed. I can pull the SD card out of the MIST, put it into my computer and copy data straight onto it, just like with the UltraSatan. That keeps the MIST and the "Low" in sync and makes backups and data transfers very easy.</p>
<h2>Why do it</h2>
<p>The main reason is preservation. If the real Mega ST 4 ever breaks down, the MiSTery Core on the MIST can take over. It's not a replacement for the real hardware, but it means a dead Mega 4 doesn't leave me without a working setup.</p>
<h2>The SD card workflow</h2>
<p>The MIST reads the same SD card layout as the UltraSatan. Since the MiSTery Core supports direct SD card access, all partitions are immediately available. There's no need to convert partitions into HDD images or mount them through an emulator menu. The card comes out of the MIST and goes straight into a PC card reader. That makes it trivially easy to move data between the MIST and the real machine, and to keep backups current.</p>
<h2>My configurations</h2>
<p>I've prepared five configurations, each for a different use case:</p>
<img src="mistery-configs.jpg" alt="The MiSTery Core configuration selection screen" width="640" height="640" loading="lazy">
<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>
<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>
<img src="itos2.jpg" alt="iTOS booting from the selected drive" width="640" height="640" loading="lazy">
<p class="caption">iTOS booting from the selected drive.</p>
<img src="itos3.jpg" alt="iTOS demo running after boot" width="640" height="640" loading="lazy">
<p class="caption">A demo running after boot on the iTOS configuration.</p>
<h3>2. 68020 14 MB with Viking Card</h3>
<p>This is the most interesting configuration. On the real Mega 4 "Low", high resolution is limited to 640x400, which always felt small to me, hence the <a href="/retro/et4000-experiment/">ET4000</a> experiments and eventually the <a href="/retro/mega-st-high/">Mega ST 4 "High"</a>. On the MiSTery Core, I can activate an FPGA recreation of the Viking graphics card. The original Viking had 1280x900, the FPGA version uses 1280x1024, which matches exactly the native resolution of my <a href="/retro/atari-monitor-compatibility/">NEC monitor</a>. Unlike the ET4000, which gives me 256 colours, the Viking is black and white only. But paired with Geneva and the faster 68020 processor, it's genuinely pleasant to work on. The core also emulates an EtherNEC and I have STinG configured for networking.</p>
<img src="viking1.jpg" alt="Viking configuration booting via EmuTOS" width="640" height="640" loading="lazy">
<p class="caption">The Viking configuration booting via EmuTOS.</p>
<img src="viking2.jpg" alt="Viking GEM desktop loading" width="640" height="640" loading="lazy">
<p class="caption">The Viking GEM desktop coming up.</p>
<img src="viking3.jpg" alt="Viking GEM desktop at full resolution" width="640" height="640" loading="lazy">
<p class="caption">The Viking GEM desktop at full 1280x1024 resolution.</p>
<img src="viking4.jpg" alt="Geneva desktop on the Viking card" width="640" height="640" loading="lazy">
<p class="caption">Geneva running on the Viking card.</p>
<img src="viking5.jpg" alt="Geneva desktop with windows open" width="640" height="640" loading="lazy">
<p class="caption">The Geneva desktop with windows open, the final result.</p>
<h3>3. 68000 8 MB</h3>
<p>A slightly improved version of my high resolution configuration without the Viking card. I use this one for testing only.</p>
<h3>4. ST TOS 1.04</h3>
<p>As close to the original ST as possible. For playing floppy games and demos in a native configuration.</p>
<h3>5. STE TOS 1.62</h3>
<p>Same idea, but for STE-specific content. Original floppy games and demos that need STE hardware.</p>
<h2>How it compares to the real Low</h2>
<p>The MiSTery Core is an accurate FPGA recreation, so it behaves very much like the real hardware. The biggest practical differences are the Viking card option, which the real Mega ST 4 doesn't have, and the fact that the MIST has no physical MegaBus or ACSI port. But for the core use cases, preserving the "Low" setup and running floppy content, it's a solid stand-in.</p>
</div>
Binary file not shown.

After

Width:  |  Height:  |  Size: 234 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 412 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 301 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 373 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 348 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 152 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1008 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 573 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 450 KiB

+3 -3
View File
@@ -53,11 +53,11 @@ parent: "/retro/"
<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> <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>Gallery</h2> <h2>Gallery</h2>
<img src="monster-ide.jpg" alt="MonSTerBoard IDE adapter with CompactFlash card" width="640" height="480"> <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> <p class="caption">The MonSTerBoard IDE adapter with a CompactFlash card attached.</p>
<img src="monster-1gb.jpg" alt="MonSTerBoard with the 1 GB CompactFlash card" width="640" height="480"> <img src="monster-1gb.jpg" alt="MonSTerBoard with the 1 GB CompactFlash card" width="640" height="640" loading="lazy">
<p class="caption">After the 4 GB card didn't work, I switched to a 1 GB CompactFlash card.</p> <p class="caption">After the 4 GB card didn't work, I switched to a 1 GB CompactFlash card.</p>
<img src="monster-pins.jpg" alt="MonSTerBoard pins and jumper block" width="640" height="480"> <img src="monster-pins.jpg" alt="MonSTerBoard pins and jumper block" width="640" height="480" loading="lazy">
<p class="caption">The MonSTerBoard pins and jumper block.</p> <p class="caption">The MonSTerBoard pins and jumper block.</p>
<h2>Sources</h2> <h2>Sources</h2>
BIN
View File
Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.4 MiB

After

Width:  |  Height:  |  Size: 467 KiB

+4 -4
View File
@@ -12,12 +12,12 @@ parent: "/retro/"
<p>What started with childhood memories of an Atari ST and an Amiga 500 turned into a full-blown home retro-computing corner after 2020. Here's a snapshot of the whole setup, which machines are actually set up and running right now, and which are boxed and ready to use on demand.</p> <p>What started with childhood memories of an Atari ST and an Amiga 500 turned into a full-blown home retro-computing corner after 2020. Here's a snapshot of the whole setup, which machines are actually set up and running right now, and which are boxed and ready to use on demand.</p>
<h2>The study</h2> <h2>The study</h2>
<p>The study holds the bulk of the serious gear. The <a href="/retro/mist-mister-fpga/">MiSTer FPGA</a> and the MiST FPGA are set up here, both connected to a <a href="https://www.nec-display.com/" target="_blank">NEC 1970NXp</a>. The <a href="/retro/atari-mega-st-fleet/">Mega ST 4 "Low"</a> machine is set up and running on a <a href="https://www.amazon.de/dp/B0957KH8X7/" target="_blank">Dell SE2722HX 27</a> that handles 15kHz, serving as the demo- and game-machine.</p> <p>The study holds the bulk of the serious gear. The <a href="/retro/mist-mister-fpga/">MiSTer FPGA</a> and the MiST FPGA are set up here, both connected to a <a href="https://www.nec-display.com/" target="_blank">NEC 1970NXp</a>. The MiST runs the <a href="/retro/mistery-core/">MiSTery Core</a> as a backup for the <a href="/retro/mega-st-low/">Mega ST 4 "Low"</a>, with the entire SD card cloned from the UltraSatan. The <a href="/retro/atari-mega-st-fleet/">Mega ST 4 "Low"</a> machine is set up and running on a <a href="https://www.amazon.de/dp/B0957KH8X7/" target="_blank">Dell SE2722HX 27</a> that handles 15kHz, serving as the demo- and game-machine.</p>
<p>The rest of the Atari hardware is stored here but not set up, mainly for lack of space:</p> <p>The rest of the Atari hardware is stored here but not set up, mainly for lack of space:</p>
<ul> <ul>
<li><strong>The Mega ST 4 "High"</strong>, the upgraded workstation, is boxed and can be set up on demand. It has its own EIZO FlexScan L365 15-inch monitor for the ET4000, and when I use it I set it up in the living room on the dining table. The L365 is a genuinely good 15-inch panel, with a sharp 1024×768 image and wide viewing angles that make it a great fit for high-resolution Atari desktop work, and it does the ET4000's output justice.</li> <li><strong><a href="/retro/mega-st-high/">The Mega ST 4 "High"</a></strong>, the upgraded workstation, is boxed and can be set up on demand. It has its own EIZO FlexScan L365 15-inch monitor for the ET4000, and when I use it I set it up in the living room on the dining table. The L365 is a genuinely good 15-inch panel, with a sharp 1024×768 image and wide viewing angles that make it a great fit for high-resolution Atari desktop work, and it does the ET4000's output justice.</li>
<li><strong>The heirloom Mega ST 4</strong>, kept factory-original, is not set up.</li> <li><strong><a href="/retro/mega-st-heirloom/">The heirloom Mega ST 4</a></strong>, kept factory-original, is not set up.</li>
<li><strong>The Mega ST 2</strong>, the spare and donor machine, is not set up.</li> <li><strong><a href="/retro/mega-st2/">The Mega ST 2</a></strong>, the spare and donor machine, is not set up.</li>
</ul> </ul>
<h2>Why the EIZO FlexScan L365 is a great fit</h2> <h2>Why the EIZO FlexScan L365 is a great fit</h2>
+4 -4
View File
@@ -21,16 +21,16 @@ parent: "/retro/"
<p>With the Storm ST and Cloudy ST combo in place, the machine boots into EmuTOS 1.0.1 with all 8 MB of Alt-RAM available, or switches over to PP's improved iTOS 1.04 for maximum software compatibility with games and demos from the era. iTOS 1.04 adds real FAT16 filesystem support, so it works much better with hard disks and mass storage, plus a few welcome extras on top of the classic TOS 1.04 behaviour. It's the best of both worlds: the modern conveniences of EmuTOS combined with the improved, authentic-feeling iTOS.</p> <p>With the Storm ST and Cloudy ST combo in place, the machine boots into EmuTOS 1.0.1 with all 8 MB of Alt-RAM available, or switches over to PP's improved iTOS 1.04 for maximum software compatibility with games and demos from the era. iTOS 1.04 adds real FAT16 filesystem support, so it works much better with hard disks and mass storage, plus a few welcome extras on top of the classic TOS 1.04 behaviour. It's the best of both worlds: the modern conveniences of EmuTOS combined with the improved, authentic-feeling iTOS.</p>
<h2>Gallery</h2> <h2>Gallery</h2>
<img src="storm-cloudy-1.jpg" alt="Storm ST and Cloudy ST installed in the Mega ST" width="590" height="443"> <img src="storm-cloudy-1.jpg" alt="Storm ST and Cloudy ST installed in the Mega ST" width="590" height="443" loading="lazy">
<p class="caption">The Storm ST and Cloudy ST combo installed in the Mega ST.</p> <p class="caption">The Storm ST and Cloudy ST combo installed in the Mega ST.</p>
<img src="storm-cloudy-2.jpg" alt="Storm ST and Cloudy ST board detail" width="590" height="443"> <img src="storm-cloudy-2.jpg" alt="Storm ST and Cloudy ST board detail" width="590" height="443" loading="lazy">
<p class="caption">Close-up of the Storm ST and Cloudy ST boards.</p> <p class="caption">Close-up of the Storm ST and Cloudy ST boards.</p>
<img src="storm-cloudy-3.jpg" alt="Storm ST and Cloudy ST with wiring" width="590" height="443"> <img src="storm-cloudy-3.jpg" alt="Storm ST and Cloudy ST with wiring" width="590" height="443" loading="lazy">
<p class="caption">The Storm ST and Cloudy ST with their wiring in place.</p> <p class="caption">The Storm ST and Cloudy ST with their wiring in place.</p>
<img src="storm-cloudy-4.jpg" alt="Storm ST and Cloudy ST final install" width="590" height="443"> <img src="storm-cloudy-4.jpg" alt="Storm ST and Cloudy ST final install" width="590" height="443" loading="lazy">
<p class="caption">The finished installation in the Mega ST.</p> <p class="caption">The finished installation in the Mega ST.</p>
<h2>Sources</h2> <h2>Sources</h2>
+2 -2
View File
@@ -31,9 +31,9 @@ parent: "/retro/"
<p>In the Mega ST 4 "High" machine the STPSU provides clean, stable power to the <a href="/retro/monsterboard/">MonSTerBoard</a>, IDE storage, the <a href="/retro/et4000-experiment/">ET4000</a> and the rest of the workstation, keeping everything running reliably.</p> <p>In the Mega ST 4 "High" machine the STPSU provides clean, stable power to the <a href="/retro/monsterboard/">MonSTerBoard</a>, IDE storage, the <a href="/retro/et4000-experiment/">ET4000</a> and the rest of the workstation, keeping everything running reliably.</p>
<h2>Gallery</h2> <h2>Gallery</h2>
<img src="stpsu-installed-1.jpg" alt="The STPSU installed in the Mega ST" width="480" height="640"> <img src="stpsu-installed-1.jpg" alt="The STPSU installed in the Mega ST" width="480" height="640" loading="lazy">
<p class="caption">The STPSU installed in my Mega ST 4 "High" machine.</p> <p class="caption">The STPSU installed in my Mega ST 4 "High" machine.</p>
<img src="stpsu-installed-2.jpg" alt="STPSU installation detail" width="640" height="480"> <img src="stpsu-installed-2.jpg" alt="STPSU installation detail" width="640" height="480" loading="lazy">
<p class="caption">A closer look at the installed STPSU.</p> <p class="caption">A closer look at the installed STPSU.</p>
<h2>Manual and documentation</h2> <h2>Manual and documentation</h2>
+1 -1
View File
@@ -51,7 +51,7 @@ parent: "/retro/"
<h2>KAOS TOS</h2> <h2>KAOS TOS</h2>
<p>KAOS TOS is a comprehensive software patch for the Atari ST's TOS, developed from 1990 to fix bugs and boost performance. It's not a standalone operating system but a patch for the original Atari TOS, mainly based on TOS 1.02 and TOS 1.04. The developers corrected over 80 known programming errors in the original system. KAOS 1.2 was published in the c't magazine, while the later KAOS 1.4.2 was sold commercially.</p> <p>KAOS TOS is a comprehensive software patch for the Atari ST's TOS, developed from 1990 to fix bugs and boost performance. It's not a standalone operating system but a patch for the original Atari TOS, mainly based on TOS 1.02 and TOS 1.04. The developers corrected over 80 known programming errors in the original system. KAOS 1.2 was published in the c't magazine, while the later KAOS 1.4.2 was sold commercially.</p>
<p>It ran noticeably faster, and although critics claimed this was only from disabling visual effects, re-enabling them disproved that. Since the Atari ST keeps its operating system in ROM, KAOS was often burned onto EPROM chips and physically installed in the machine. Most cleanly written applications ran without problems, with special helper patches for the few incompatible ones. Atari never officially licensed the project but tolerated it on the market. It was shaped by Andreas Kromke and Normen Kowalewski, among others, and became well known in the Atari community through coverage in the ST-Magazin.</p> <p>It ran noticeably faster, and although critics claimed this was only from disabling visual effects, re-enabling them disproved that. Since the Atari ST keeps its operating system in ROM, KAOS was often burned onto EPROM chips and physically installed in the machine. Most cleanly written applications ran without problems, with special helper patches for the few incompatible ones. Atari never officially licensed the project but tolerated it on the market. It was shaped by Andreas Kromke and Normen Kowalewski, among others, and became well known in the Atari community through coverage in the ST-Magazin.</p>
<p>KAOS TOS is also installed on my <a href="/retro/mega-st-low/">"Low"</a> machine, though I rarely use it. Theoretically it's there and available if needed.</p> <p>KAOS TOS is also installed on my <a href="/retro/mega-st-high/">"High"</a> machine, though I currently always run Geneva under TOS 2.06. No TOS switcher is wired up yet, so it's fixed to TOS 2.06 for now.</p>
<h2>Adding multitasking: Geneva and MiNT</h2> <h2>Adding multitasking: Geneva and MiNT</h2>
<p>Plain Atari TOS is a single-tasking system: only one main program runs at a time. Two well-known add-ons change that.</p> <p>Plain Atari TOS is a single-tasking system: only one main program runs at a time. Two well-known add-ons change that.</p>
+12
View File
@@ -185,6 +185,18 @@ main > h1 {
text-underline-offset: 2px; text-underline-offset: 2px;
} }
.detail-content a:hover { color: var(--text); } .detail-content a:hover { color: var(--text); }
.detail-content img {
display: block;
max-width: 100%;
height: auto;
margin: 1.5rem 0 0.5rem;
border-radius: 8px;
}
.detail-content .caption {
font-size: 0.85rem;
color: #666;
margin: 0 0 1.5rem;
}
.back-link { .back-link {
display: inline-block; display: inline-block;
+3 -3
View File
@@ -134,14 +134,14 @@ description: "WiFi-controlled LED display solution with REST API, DHT22 sensor,
<div class="feature-icon">📊</div> <div class="feature-icon">📊</div>
<div class="feature-text"> <div class="feature-text">
<h3>Sensor Readings</h3> <h3>Sensor Readings</h3>
<p>Live temperature and humidity from the on-board DHT22 sensor, stored in <a href="https://www.moonweb.org/smarthome//homematic-mqtt/">InfluxDB via MQTT</a></p> <p>Live temperature and humidity from the on-board DHT22 sensor, stored in <a href="https://www.moonweb.org/smarthome/homematic-mqtt/">InfluxDB via MQTT</a></p>
</div> </div>
</div> </div>
<div class="feature"> <div class="feature">
<div class="feature-icon">🔔</div> <div class="feature-icon">🔔</div>
<div class="feature-text"> <div class="feature-text">
<h3>Status Messages</h3> <h3>Status Messages</h3>
<p>Notifications like "washing machine done" triggered via <a href="https://www.moonweb.org/smarthome//tasmota-energy/">MQTT and Tasmota energy monitoring</a></p> <p>Notifications like "washing machine done" triggered via <a href="https://www.moonweb.org/smarthome/tasmota-energy/">MQTT and Tasmota energy monitoring</a></p>
</div> </div>
</div> </div>
<div class="feature"> <div class="feature">
@@ -575,7 +575,7 @@ ESP32 will be restarted (with display shutdown)</pre>
</div> </div>
<div class="footer-bottom"> <div class="footer-bottom">
<p>&copy; 2026 <a href="https://stefankoelle.de/">Stefan Kölle</a>. LED Matrix WebServer v1.08.</p> <p>&copy; 2026 <a href="https://stefankoelle.de/">Stefan Kölle</a>. LED Matrix WebServer v1.08.</p>
<p><a href="https://www.moonweb.org//impressum/">Legal Notice &amp; Privacy Policy</a></p> <p>Part of <a href="https://www.moonweb.org/">moonweb.org</a> · <a href="https://www.moonweb.org/smarthome/">More Smart Home Projects</a> · <a href="https://www.moonweb.org/impressum/">Legal Notice &amp; Privacy Policy</a></p>
</div> </div>
</footer> </footer>
BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 691 B

BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 681 B

BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 732 B

BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 711 B

Executable
+288
View File
@@ -0,0 +1,288 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>TranceMission Archive - Pascal PC Intros from 1992-1995 - Graphics, Animation, and Sound</title>
<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>
body {
background-color: black;
color: #FFF741;
display: flex;
justify-content: center;
align-items: center;
flex-direction: column;
font-family: Arial, sans-serif;
margin: 0;
padding: 0;
font-size: 18px; /* Schriftgröße des Textes */
}
.container {
text-align: center;
max-width: 1000px;
width: 100%;
padding: 20px;
}
.logo {
margin-bottom: 20px;
}
.intro {
margin-bottom: 40px;
}
.program {
margin-bottom: 40px;
}
.screenshots {
display: flex;
justify-content: center;
gap: 10px;
flex-wrap: wrap;
}
.screenshots a {
display: inline-block;
position: relative;
}
.screenshots img {
max-width: 300px;
height: auto;
}
.youtube-logo {
position: absolute;
top: 50%;
left: 50%;
transform: translate(-50%, -50%);
width: 50px;
height: 50px;
}
a {
color: #E76D00;
text-decoration: none;
font-weight: bold;
}
a:hover {
color: #CB4D00;
text-decoration: underline;
}
/* Lightbox CSS */
.lightbox {
display: none;
position: fixed;
z-index: 999;
padding-top: 60px;
left: 0;
top: 0;
width: 100%;
height: 100%;
overflow: auto;
background-color: rgba(0,0,0,0.9);
}
.lightbox-content {
margin: auto;
display: block;
width: 80%;
max-width: 700px;
height: 450px;
}
.lightbox-close {
position: absolute;
top: 15px;
right: 35px;
color: #f1f1f1;
font-size: 40px;
font-weight: bold;
transition: 0.3s;
}
.lightbox-close:hover,
.lightbox-close:focus {
color: #bbb;
text-decoration: none;
cursor: pointer;
}
table {
border:0px;
border-color:#000000;
}
th {
text-align:left;
}
td {
text-align:left;
}
@media (max-width: 768px) {
#logo {
width:100%
}
}
.footer {
font-size: 0.9em;
text-align: center;
padding: 20px;
background-color: #333;
color: #f0f0f0;
margin-top: 20px;
}
</style>
</head>
<body>
<div class="container">
<div class="logo">
<img id="logo" src="logo.png" alt="TranceMission Logo">
</div>
<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>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">
<img src="headline-star-intro.png" alt="Star Intro">
<div class="screenshots">
<a href="star-intro.png" onclick="openLightbox('star-intro.png'); return false;"><img src="star-intro.png" alt="Screenshot 1"></a>
<a href="https://www.youtube.com/embed/qdtqDdSPuG8?autoplay=1" onclick="openLightboxVideo(this.href); return false;">
<img src="https://img.youtube.com/vi/qdtqDdSPuG8/hqdefault.jpg" alt="Video Thumbnail">
<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>
<table>
<tr>
<th>Component</th>
<th>Description</th>
</tr>
<tr>
<td>Initialization</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>
</tr>
<tr>
<td>Animation</td>
<td>Animates stars moving across the screen.</td>
</tr>
<tr>
<td>Sound</td>
<td>Plays sound if a SoundBlaster card is detected.</td>
</tr>
<tr>
<td>User Interaction</td>
<td>Waits for a key press to exit the demo.</td>
</tr>
</table>
</div>
<div class="program">
<img src="headline-logo-intro.png" alt="Logo Intro">
<div class="screenshots">
<a href="logo-intro2.png" onclick="openLightbox('logo-intro2.png'); return false;"><img src="logo-intro2.png" alt="Screenshot 1"></a>
<a href="logo-intro.png" onclick="openLightbox('logo-intro.png'); return false;"><img src="logo-intro.png" alt="Screenshot 2"></a>
<a href="https://www.youtube.com/embed/i4UOuAOxkn4?autoplay=1" onclick="openLightboxVideo(this.href); return false;">
<img src="https://img.youtube.com/vi/i4UOuAOxkn4/hqdefault.jpg" alt="Video Thumbnail">
<img src="play.png" alt="YouTube Logo" class="youtube-logo">
</a>
</div>
<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>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>
</tr>
<tr>
<td>Animation</td>
<td>Animates text using a sine wave effect. Speed is controlled by 'S' and 'A' keys.</td>
</tr>
<tr>
<td>Sound</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>
</tr>
</table>
</div>
<div class="program">
<img src="headline-menu-intro.png" alt="Menu Intro">
<div class="screenshots">
<a href="menu-intro1.png" onclick="openLightbox('menu-intro1.png'); return false;"><img src="menu-intro1.png" alt="Screenshot 1"></a>
<!--<a href="menu-intro2.png" onclick="openLightbox('menu-intro2.png'); return false;"><img src="menu-intro2.png" alt="Screenshot 2"></a>-->
<a href="menu-intro3.png" onclick="openLightbox('menu-intro3.png'); return false;"><img src="menu-intro3.png" alt="Screenshot 3"></a>
<a href="https://www.youtube.com/embed/BvKIsfDLH48?autoplay=1" onclick="openLightboxVideo(this.href); return false;">
<img src="https://img.youtube.com/vi/BvKIsfDLH48/hqdefault.jpg" alt="Video Thumbnail">
<img src="play.png" alt="YouTube Logo" class="youtube-logo">
</a>
</div>
<p>This Pascal program is a demo that displays a menu with animated text and graphics, along with playing sound effects.</p>
<table>
<tr>
<th>Component</th>
<th>Description</th>
</tr>
<tr>
<td>Initialization</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>
</tr>
<tr>
<td>Animation</td>
<td>Animates a logo and text with a wobble effect.</td>
</tr>
<tr>
<td>Sound</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>
</tr>
</table>
</div>
<div class="footer">
Stefan Koelle 1992 - 1995<br>
Part of <a href="/">moonweb.org</a> · <a href="/retro/">Retro Corner</a> · <a href="/impressum/">Legal Notice</a>
</div>
</div>
<!-- Lightbox HTML -->
<div id="lightbox" class="lightbox" onclick="closeLightbox(event)">
<span class="lightbox-close" onclick="closeLightbox()">&times;</span>
<img class="lightbox-content" id="lightbox-img" src="">
<iframe class="lightbox-content" id="lightbox-video" width="560" height="315" src="" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
</div>
<script>
function openLightbox(src) {
document.getElementById('lightbox-img').src = src;
document.getElementById('lightbox-img').style.display = 'block';
document.getElementById('lightbox-video').style.display = 'none';
document.getElementById('lightbox').style.display = 'block';
}
function openLightboxVideo(src) {
document.getElementById('lightbox-video').src = src;
document.getElementById('lightbox-video').style.display = 'block';
document.getElementById('lightbox-img').style.display = 'none';
document.getElementById('lightbox').style.display = 'block';
}
function closeLightbox(event) {
if (event.target.id === 'lightbox' || event.target.className === 'lightbox-close') {
document.getElementById('lightbox').style.display = 'none';
document.getElementById('lightbox-video').src = '';
}
}
</script>
</body>
</html>
BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

Executable
BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Executable
BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 661 B

BIN
View File
Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Before

Width:  |  Height:  |  Size: 15 KiB

After

Width:  |  Height:  |  Size: 15 KiB

Before

Width:  |  Height:  |  Size: 13 KiB

After

Width:  |  Height:  |  Size: 13 KiB

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 11 KiB

Before

Width:  |  Height:  |  Size: 35 KiB

After

Width:  |  Height:  |  Size: 35 KiB

Before

Width:  |  Height:  |  Size: 4.3 KiB

After

Width:  |  Height:  |  Size: 4.3 KiB

Before

Width:  |  Height:  |  Size: 13 KiB

After

Width:  |  Height:  |  Size: 13 KiB

Before

Width:  |  Height:  |  Size: 7.4 KiB

After

Width:  |  Height:  |  Size: 7.4 KiB

Before

Width:  |  Height:  |  Size: 37 KiB

After

Width:  |  Height:  |  Size: 37 KiB

Before

Width:  |  Height:  |  Size: 10 KiB

After

Width:  |  Height:  |  Size: 10 KiB

Before

Width:  |  Height:  |  Size: 918 B

After

Width:  |  Height:  |  Size: 918 B

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 91 B

After

Width:  |  Height:  |  Size: 91 B

Before

Width:  |  Height:  |  Size: 7.3 KiB

After

Width:  |  Height:  |  Size: 7.3 KiB

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 11 KiB

Before

Width:  |  Height:  |  Size: 85 B

After

Width:  |  Height:  |  Size: 85 B

Before

Width:  |  Height:  |  Size: 818 B

After

Width:  |  Height:  |  Size: 818 B

Before

Width:  |  Height:  |  Size: 1.3 KiB

After

Width:  |  Height:  |  Size: 1.3 KiB

Before

Width:  |  Height:  |  Size: 1.5 KiB

After

Width:  |  Height:  |  Size: 1.5 KiB

Before

Width:  |  Height:  |  Size: 179 B

After

Width:  |  Height:  |  Size: 179 B

Before

Width:  |  Height:  |  Size: 141 B

After

Width:  |  Height:  |  Size: 141 B

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.2 KiB

After

Width:  |  Height:  |  Size: 1.2 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.2 KiB

After

Width:  |  Height:  |  Size: 1.2 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.2 KiB

After

Width:  |  Height:  |  Size: 1.2 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.2 KiB

After

Width:  |  Height:  |  Size: 1.2 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.2 KiB

After

Width:  |  Height:  |  Size: 1.2 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.1 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB

Before

Width:  |  Height:  |  Size: 1.2 KiB

After

Width:  |  Height:  |  Size: 1.2 KiB

Some files were not shown because too many files have changed in this diff Show More