<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by nosamu on Medium]]></title>
        <description><![CDATA[Stories by nosamu on Medium]]></description>
        <link>https://medium.com/@nosamu?source=rss-f078c4ba17b8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9rsvD0re2zZMxsnq9-fT6g.png</url>
            <title>Stories by nosamu on Medium</title>
            <link>https://medium.com/@nosamu?source=rss-f078c4ba17b8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:34:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nosamu/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Get Internet Explorer Back on Windows 10 and 11 In 2023]]></title>
            <link>https://nosamu.medium.com/how-to-get-internet-explorer-back-on-windows-10-and-11-in-2023-bdb632299822?source=rss-f078c4ba17b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdb632299822</guid>
            <category><![CDATA[internet-explorer]]></category>
            <category><![CDATA[windows-10]]></category>
            <category><![CDATA[windows-11]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[nosamu]]></dc:creator>
            <pubDate>Wed, 15 Feb 2023 14:05:26 GMT</pubDate>
            <atom:updated>2023-03-23T20:06:27.783Z</atom:updated>
            <content:encoded><![CDATA[<p>On February 14, 2023, <a href="https://techcommunity.microsoft.com/t5/windows-it-pro-blog/internet-explorer-11-desktop-app-retirement-faq/ba-p/2366549">a Microsoft update</a> disabled Internet Explorer on Windows 10 PCs everywhere. At the time of writing, the Internet Explorer application still opens on Windows 10, but attempting to navigate to any website will open it in Microsoft Edge instead. Microsoft claims that “users will not be able to reverse this change.” But with a few simple steps, it is actually possible to get Internet Explorer fully working again. The method works even on Windows 11 — read on for details!</p><p>Before I explain the steps to get Internet Explorer working again on Windows 10 or 11, I would like to make it clear that Microsoft Edge’s Internet Explorer mode is sufficient for most users. With IE Mode, you can access legacy sites and applications from a convenient button on Edge’s toolbar, while using a modern browsing engine for all other sites. To learn more about Internet Explorer mode, I recommend <a href="https://helpdeskgeek.com/how-to/how-to-enable-internet-explorer-mode-in-edge-on-windows-10-11/">this excellent Help Desk Geek article</a>.</p><p>Despite all that, some legacy applications and workflows absolutely do require the Internet Explorer application. If you find yourself needing to use Internet Explorer, you don’t need to go rummaging for an old PC. To re-activate Internet Explorer on Windows 10 or 11, all you need to do is create a special shortcut on your desktop. Follow the steps below!</p><ol><li>Right-click on an empty spot on your desktop, then click New =&gt; Shortcut.</li></ol><figure><img alt="The Windows right-click menu, with New Shortcut highlighted." src="https://cdn-images-1.medium.com/max/490/1*Wbrwymfib1udGbzSmZX_KQ.png" /></figure><p>2. Paste the following text into the Location box: <br>mshta.exe javascript:open();close()</p><figure><img alt="The Windows shortcut dialog, with the provided code written in the Location box." src="https://cdn-images-1.medium.com/max/614/1*--_3T1SXrvr954-OxTOgzw.png" /></figure><p>3. Click the Next button, then type “Internet Explorer” for the name of the shortcut. Click the Finish button to save the shortcut.</p><p>And that’s all there is to it! You can open Internet Explorer at any time by double-clicking the new shortcut on your desktop.</p><figure><img alt="The Internet Explorer shortcut." src="https://cdn-images-1.medium.com/max/131/1*BAKOtZtJf0fcHeaBvfphuw.png" /></figure><h4>Bonus Tip: How to change the shortcut icon</h4><p>If you find the default shortcut icon a bit ugly and want that nice IE logo back, simply follow the steps below!</p><ol><li>Right-click the shortcut, then click Properties.</li></ol><figure><img alt="The right-click menu on the Internet Explorer shortcut." src="https://cdn-images-1.medium.com/max/366/1*YsKDabCVT2J6Kiza-K6bDg.png" /></figure><p>2. In the Properties dialog, click the Change Icon button.</p><figure><img alt="The Properties dialog for the Internet Explorer shortcut." src="https://cdn-images-1.medium.com/max/363/1*n2gu6i4IGF1IYpsyLwHY3w.png" /></figure><p>3. Paste the following path into the box under “Look for icons in this file”, then click the OK button:<br>%ProgramFiles%\Internet Explorer\iexplore.exe</p><figure><img alt="The Change Icon dialog after pasting in the Internet Explorer path and clicking OK." src="https://cdn-images-1.medium.com/max/292/1*SrUFp_KOloC1SEkRZ7QvFg.png" /></figure><p>4. Select the IE icon and click the OK button. Then click OK in the Properties dialog to save the change!</p><figure><img alt="The final Internet Explorer shortcut with the IE icon set." src="https://cdn-images-1.medium.com/max/113/1*JYnxDzKs4FLoeM85K0bLjg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdb632299822" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Reactivate  Flash-based Games and Screensavers on Windows 10 or 8.1]]></title>
            <link>https://nosamu.medium.com/how-to-reactivate-flash-based-games-and-screensavers-on-windows-10-or-8-1-f9b0218a332c?source=rss-f078c4ba17b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9b0218a332c</guid>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[flash]]></category>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[adobe-flash]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[nosamu]]></dc:creator>
            <pubDate>Sun, 28 Mar 2021 12:33:56 GMT</pubDate>
            <atom:updated>2021-12-20T23:02:30.565Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Reactivate Flash-based Games and Screensavers on Windows 10 or 8.1</h3><p>If you have an old Flash-based screensaver or game on your Windows PC, it probably stopped working in January of 2021. This is because Flash-based Windows applications usually rely on the Flash ActiveX control, which is also used by Internet Explorer. That means Flash’s removal from browsers like Internet Explorer also affected your screensavers and games. But never fear; with a few simple steps, you can get Flash Player up and running again!</p><p>(Note: This article has been updated on June 20, 2021. I now recommend using the <a href="https://gitlab.com/cleanflash/installer/-/releases">Clean Flash installer</a> because Adobe has disabled the archived official installers. I have updated the article to reflect this.)</p><h4>Check your Flash plugin</h4><p>First, open up the Start menu and search for <em>Internet Explorer</em>. Yes, it still exists on Windows 10!</p><p>Now copy and paste the following URL into Internet Explorer’s address bar: <a href="https://n0samu.github.io/flash-player-check.html">https://n0samu.github.io/flash-player-check.html</a></p><p>This will open my Flash Player test page. If you see a blank red box, go to <strong>Solution 1</strong> and install Flash Player. If you see a Flash Player information icon like the image below, go to <strong>Solution 2</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*srEel8tnmxteTP8m6fuHPA.png" /><figcaption>The Flash Player information icon (time bomb screen)</figcaption></figure><h4>Solution 1: Install Flash Player</h4><p>First, <a href="https://gitlab.com/cleanflash/installer/-/releases">download the Clean Flash Player installer</a>. This tool allows easy installation of the latest version of Flash Player, with the time bomb and other annoyances patched out.</p><p>Double-click the Flash installer to run it. Allow it to run as an Administrator if prompted, and close any web browser windows that you have open. After it finishes, open Internet Explorer and go back to <a href="https://n0samu.github.io/flash-player-check.html">my Flash Player test page</a>. You should see your Flash Player version in the red box, and your Flash-based programs should work again!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*QBki73iKu6TwUmW84_wWuA.png" /><figcaption>What you’ll see if Flash Player installed successfully. (Your version may be different, though.)</figcaption></figure><h4>Solution 2: Patch your Flash Player</h4><p>If you see the information icon on the <a href="https://n0samu.github.io/flash-player-check.html">Flash Player test page</a>, you’ll need to activate Flash Player by patching out its time bomb. Adobe added a time bomb to Flash Player in order to prevent it from being used after January 12, 2021. Luckily, patching out the time bomb is easy!</p><p>First, <a href="https://github.com/darktohka/FlashPatch/releases/latest">download the FlashPatch tool</a>. Be sure to download the <strong>FlashPatch.zip</strong> file. Next, right-click the downloaded file and click “Extract All.”</p><p>After it’s done extracting, double-click the FlashPatch program (FlashPatch.exe) and allow it to run. Click the “Patch” button, then close all of your browser windows (including Internet Explorer) when told to do so.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/395/1*VHxvR1xLi_6aCIwwUsdRbw.png" /><figcaption>The FlashPatch program window</figcaption></figure><p>Finally, open Internet Explorer and go back to <a href="https://n0samu.github.io/flash-player-check.html">my Flash Player test page</a>. You should see your Flash Player version in the red box, and your Flash-based programs should work again!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*QBki73iKu6TwUmW84_wWuA.png" /><figcaption>What you’ll see if Flash Player was successfully patched. (Your version may be different, though.)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9b0218a332c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flash Player Emulators: How to Play SWFs in 2021 and Beyond]]></title>
            <link>https://nosamu.medium.com/flash-player-emulators-how-to-play-swfs-in-2021-and-beyond-d56c3899b7e6?source=rss-f078c4ba17b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d56c3899b7e6</guid>
            <category><![CDATA[emulation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[emulator]]></category>
            <category><![CDATA[adobe-flash]]></category>
            <category><![CDATA[flash]]></category>
            <dc:creator><![CDATA[nosamu]]></dc:creator>
            <pubDate>Sat, 09 Jan 2021 20:46:25 GMT</pubDate>
            <atom:updated>2021-11-28T09:47:09.653Z</atom:updated>
            <content:encoded><![CDATA[<h3>Flash Player Emulators: How to Play SWF Files in 2021 and Beyond</h3><p>Adobe <a href="https://blog.adobe.com/en/publish/2017/07/25/adobe-flash-update.html">ended support for Flash Player</a> on December 31, 2020, and <a href="https://datahorde.org/?p=1916">Flash Player will completely stop working on January 12</a>. If you’re reading this, you probably have some Flash content that you want to keep running after January 12. That’s where Flash emulators come in; you can use them to play SWF files without installing the Flash Player. Unfortunately, no Flash emulator is perfect — each one has unique strengths and weaknesses. This article will introduce you to all of the major Flash emulators, what they are most useful for, and how to use them to play your favorite Flash content. Let’s get started!</p><h3>Downloading SWF Files</h3><p>Before you can use a Flash emulator, you will need to download an SWF that you wish to play. <a href="https://www.wikihow.com/Download-SWF-Files">This guide</a> goes over some simple approaches, and <a href="https://bluemaxima.org/flashpoint/datahub/Curation_Tutorial#Finding_the_Source_of_a_Flash_Game">this tutorial</a> from the <a href="https://bluemaxima.org/flashpoint/">Flashpoint web game preservation project</a> has some additional tips. After you’ve downloaded some SWF files, you’ll be ready to try out the emulators!</p><h3>Ruffle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6TIFNZJVc5NnJ6oCJ6Jyg.png" /><figcaption><a href="https://en.wikipedia.org/wiki/Alien_Hominid">Alien Hominid</a> running in the <a href="https://ruffle.rs/demo/">Ruffle Web Demo</a></figcaption></figure><p><a href="https://ruffle.rs/">Ruffle</a> is a new, promising Flash emulator with a very active team of developers. It is built using Rust, a modern and high-performance programming language that supports Windows, Mac, Linux and the web. Best of all, Ruffle is fully open source! However, Ruffle is still in the early stages of development, so ActionScript 3 (the most recent version of Flash’s programming language) is not supported yet. ActionScript 3 was introduced in 2006; nearly all SWFs from before then will work in Ruffle, but many SWFs from later years will not function at all.</p><p>To try out Ruffle, go to the <a href="https://ruffle.rs/demo/">Ruffle Web Demo</a> and click “Browse…” to load an SWF from your computer. If everything goes well, the SWF will play just like it did in the Flash Player. If you like what you see, you can <a href="https://github.com/ruffle-rs/ruffle/wiki/Using-Ruffle#desktop">install the desktop app</a> to use Ruffle offline or <a href="https://github.com/ruffle-rs/ruffle/wiki/Using-Ruffle#browser-extension">install the browser extension</a> to use Ruffle on all the Flash websites you visit. Webmasters can even <a href="https://github.com/ruffle-rs/ruffle/wiki/Using-Ruffle#web">add Ruffle to their own websites</a> with just one line of HTML code. How cool is that?</p><h3>Lightspark</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/1*13CjPCZUNmKJdElSp75ORw.png" /></figure><p><a href="http://lightspark.github.io/">Lightspark</a> is another free, open source, and actively developed Flash emulator. Its code is written in C++, an older programming language. For this reason, there is no web demo or browser extension; you’ll have to <a href="https://github.com/lightspark/lightspark/releases">download the desktop app</a>.</p><p>Lightspark excels where Ruffle falls short: it supports some of the more recent Flash files that use ActionScript 3. However, ActionScript 3 is a lot more complicated than previous versions of the language, so don’t expect every SWF to work. Nevertheless, if you have an SWF that doesn’t work in Ruffle, Lightspark is definitely worth a try!</p><h3>WAFlash</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*qWNsAaYZ1sHL6fPOrO9X4g.png" /></figure><p><a href="https://vidkidz.github.io/">WAFlash</a> is a Flash emulator that has excellent compatibility with all three ActionScript versions, a very impressive feat. It is written in C++ by Korean developer Jinsoo Park, and it is compiled for the web using Emscripten. That means you can try it out in your browser right now; just head over to the demo page and select an SWF file from your computer to play! Unfortunately, the official demo page no longer works, but you can use <a href="https://clubpenguinadvanced.github.io/waflash-demo/">this unofficial demo page</a> instead.</p><p>WAFlash might be the most widely compatible Flash emulator, but this good news comes with a catch. There is no offline download available and no browser extension. Worse still, the project is not open source, and the developer says he may take the emulator commercial in the future. The future of WAFlash is uncertain, and the developer has stated that webmasters are not currently allowed to use it on their own websites, either.</p><h3>AwayFL</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*f7tstoKX1I2HVkTDQ0fsgw.png" /></figure><p><a href="https://github.com/awayfl">AwayFL</a> is an open source Flash emulator created by the non-profit <a href="http://www.theawayfoundation.org/">Away Foundation</a>. They have notably worked with <a href="https://poki.com/">Poki</a> to create official emulated versions of <a href="https://www.nitrome.com/html5-games/">Nitrome’s classic Flash games</a>. You can learn more about the partnership from <a href="https://www.pocketgamer.biz/interview/73491/interview-poki-preserving-flash-games-nitrome/">this Pocket Gamer interview</a>. Although these conversions are excellent, there is very little official documentation of AwayFL. The emulator is said to work very well for a narrow segment of early ActionScript 3 games, but in my tests, it proved underwhelming for general usage. Your mileage may vary; you can try out the emulator on this <a href="https://exponenta.games/games/AFL/">unofficial demo page</a>. If you have questions about the emulator, you can contact the Away Foundation or join their semi-official <a href="https://discord.gg/8PGDZh8VZj">Discord server</a>. And if you’re a webmaster, you can integrate AwayFL with your website by following <a href="https://github.com/eXponenta/away-player-embed">these instructions</a>.</p><h3>swf2js</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*nd4ds2-1mCoeMJaAWRitGA.png" /></figure><p><a href="https://swf2js.com/en/">swf2js</a> is a pure JavaScript Flash emulator developed by a Japanese team led by <a href="https://github.com/ienaga">Toshiyuki Ienaga</a>. The emulator has a free edition and a paid edition, but you can try out both editions for free in the “<a href="https://swf2js.com/en/#services">live preview</a>” area of the site. You will only need to pay a fee if you want to use the production version of swf2js on your own website.</p><p>If you have an older SWF you want to play, head to the <a href="https://swf2js.com/free/index.html">free version demo</a> and click “Browse” at the top of the page to load the SWF. Next, click “Upload” and wait some time for the SWF to load. If you have a newer SWF that uses ActionScript 3, try the <a href="https://swf2js.com/prod/index.html">production version demo</a> instead.</p><p>swf2js has been in continuous development since 2013, and it shows. Because it uses plain JavaScript instead of newer, faster technologies such as WebAssembly, it struggles mightily with more intensive SWFs. However, swf2js is very accurate; in my tests, it often seemed to have fewer visual glitches than other emulators.</p><h3>Conclusion</h3><p>There is clearly no “silver bullet” emulator that can play all SWFs. In its twenty-five-year history, Flash gained a plethora of features, many of which are a monumental challenge to emulate within the restricted sandbox of the modern web. Earlier, simpler Flash content is likely to work well enough with free emulators, but the outlook seems grim for newer, more advanced Flash content. Even paid options for emulating ActionScript 3 are severely lacking. Until Flash emulation matures, your best bet is probably to run the official Flash Player in a closed environment. I will explain your options for doing so in a future post — stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d56c3899b7e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Mount BIN/CUE Images in SheepShaver or Basilisk II]]></title>
            <link>https://nosamu.medium.com/how-to-mount-bin-cue-images-in-sheepshaver-or-basilisk-ii-6f1a3d21fa42?source=rss-f078c4ba17b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f1a3d21fa42</guid>
            <category><![CDATA[file-format]]></category>
            <category><![CDATA[mac-emulation]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[emulation]]></category>
            <dc:creator><![CDATA[nosamu]]></dc:creator>
            <pubDate>Wed, 02 Sep 2020 13:31:19 GMT</pubDate>
            <atom:updated>2020-09-02T13:31:19.866Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="SheepShaver running on Windows 10" src="https://cdn-images-1.medium.com/max/802/1*bWg4txbbHfCAqed4YndSsQ.png" /></figure><p>Mounting ISO images in Mac emulators like SheepShaver and Basilisk II is easy. But what if the CD-ROM image you downloaded came as a BIN/CUE, not an ISO? Before you can use a BIN/CUE image with your Mac emulator, you will need to convert it to an ISO image.</p><p>Most tools for converting BIN/CUE images will produce an ISO that is unreadable to your Mac emulator. Fortunately, I tried all the tools so you don’t have to! I found that the right tool for the job is <a href="https://github.com/extramaster/bchunk/"><strong>bchunk</strong></a>. If you’re on MacOS, you can follow <a href="https://osxdaily.com/2018/08/05/how-convert-bin-cue-to-iso-mac/">this handy guide</a> to use the tool. If you’re on Windows, I’ll explain the steps below!</p><p>First, download <em>bchunk.v1.2.1_repub.1.exe</em> from <a href="https://github.com/extramaster/bchunk/releases/tag/v1.2.1_repub.1">this page</a>. Move it to the same folder as the BIN/CUE image that you want to convert. While you’re in this folder, click the location bar and press Ctrl-C to copy the folder path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*W357m0nUuz4LYKlAmLQYTw.png" /><figcaption>A folder containing bchunk.exe and a BIN/CUE image, ready for conversion.</figcaption></figure><p>Now open the Start Menu and search for <em>Command Prompt</em><strong><em>. </em></strong>Once you’ve opened it, type cd /d , then press Ctrl-V to paste the path you copied earlier. Now press Enter. Your screen should look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*U82aiHELMNbhORt-2XOlRQ.png" /><figcaption>Changing directory in the Command Prompt</figcaption></figure><p>Now we’re going to run the command to convert your disc image. Type bchunk , then the name of the BIN file, then the name of the CUE file, and finally the name you want to give your ISO. Be sure to add a space between each name! Your screen should look something like this now:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*Ldzi3r0GGCdJzncBCkayrw.png" /><figcaption>An example bchunk command.</figcaption></figure><p>Press Enter and wait for the program to finish running. When it’s done, you should see an ISO file appear in the folder!</p><p>To load your new ISO into SheepShaver or Basilisk II, first open its preferences file (BasiliskII_prefs or SheepShaver_prefs) with Notepad. Then add a line like this to the beginning of the file: cdrom ALIUS01.iso. Finally, move the ISO file into the same folder as the emulator. The next time you open your emulator, you should see the disc appear on your Mac desktop!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f1a3d21fa42" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ShiVa3D Web Games: What They Are, and How We Saved Them]]></title>
            <link>https://medium.com/bluemaximas-flashpoint/shiva3d-web-games-what-they-are-and-how-we-saved-them-20c2a2f486ec?source=rss-f078c4ba17b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/20c2a2f486ec</guid>
            <dc:creator><![CDATA[nosamu]]></dc:creator>
            <pubDate>Thu, 27 Aug 2020 23:19:42 GMT</pubDate>
            <atom:updated>2024-12-10T08:06:17.681Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OFEkjdqkHt77Z_JVOCuBvg.png" /><figcaption>Some of the ShiVa games you can play right now in Flashpoint.</figcaption></figure><p>If you dig deep enough into a web game site, you never know what you might find. And on March 31, 2019, Flashpoint volunteer eientei95 decided to try his luck on <a href="https://www.agame.com/">Agame.com</a>.</p><p>Now, if you’ve played a Flash game in the past few years, you’ve probably seen the Agame.com logo, if not visited the site. What you might not know is that they are owned by a Dutch company called <a href="https://en.wikipedia.org/wiki/Spil_Games">Spil Games</a>, which owns over <a href="https://spilgames.com/games/">thirty other web game portals</a>, as well as a number of popular mobile games. Needless to say, eientei had a lot of ground to cover!</p><p>Luckily, eientei wasn’t on his own. <a href="https://web.archive.org/">Archive.org’s Wayback Machine</a>, through its free <a href="https://github.com/internetarchive/wayback/tree/master/wayback-cdx-server">CDX API</a>, provides an unmatched capability to find hidden gems on nearly any website. With a quick URL query, eientei had a list of every URL on the Agame.com <a href="https://en.wikipedia.org/wiki/Content_delivery_network">CDN</a> that the Wayback Machine had ever captured.</p><p>The www8.agame.com/mirror/ directory contains an organized folder of games. It includes subfolders for advergames, Flash games, Shockwave games, and more. But as eientei looked through the folder, he noticed a small, mysterious directory called “shiva.”</p><pre><a href="http://www8.agame.com/mirror/shiva/t/the-hunt/TheHunt-startup.stk">http://www8.agame.com/mirror/shiva/t/the-hunt/TheHunt-startup.stk</a><br><a href="http://www8.agame.com/mirror/shiva/t/the-hunt/TheHunt.html">http://www8.agame.com/mirror/shiva/t/the-hunt/TheHunt.html</a></pre><p>These were the only files indexed by Wayback Machine in that directory. The HTML link contained only a bit of JavaScript code and this text: “Application created with ShiVa.” What was ShiVa, and what was it doing on the Agame.com CDN?</p><p><a href="https://archive.is/20190502064938/https://en.wikipedia.org/wiki/ShiVa">ShiVa</a>, we found, is a 3D game engine similar to Unity. And just like Unity, ShiVa once had its own browser plugin, called ShiVa Web Player. The game we had found, called The Hunt, was a technical demo produced by ShiVa Technologies (then called StoneTrip) to show what the engine is capable of. I found a <a href="https://www.youtube.com/watch?v=UCgMCupq_x0">gameplay video</a> and was immediately impressed — That level of graphical quality was unheard of in web games of the time! I knew I had to get ShiVa games working in Flashpoint somehow.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FUCgMCupq_x0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DUCgMCupq_x0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FUCgMCupq_x0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/642cdc1a0906609638bf806c482423b2/href">https://medium.com/media/642cdc1a0906609638bf806c482423b2/href</a></iframe><p>First, I attempted to install the plugin in my browser and try out the game. Although I found an installer for ShiVa Web Player fairly quickly, I discovered that the game was embedded using a script called stkobject1.8.js. This script was supposed to load from ShiVa’s servers, but ShiVa had moved to a new domain, and the script was inaccessible. Luckily, the script was still available from Wayback Machine. But how could I get the script to load from there?</p><p>To test whether the game would work with the script from Wayback Machine, I decided to add the game to Flashpoint. This let me use Flashpoint’s “fake internet,” which allows files to load as if from their original websites. I downloaded the script from Wayback Machine and added it to a location in Flashpoint matching its original URL on the internet. Next, I did the same for the game files and the original HTML file. Finally, I used Flashpoint’s browser to load the HTML file. I had all the game files, and I had the plugin installed, so the game should work, right?</p><p>Well, it didn’t. You see, just like Unity Web Player and some other plugins, the ShiVa3D Web Player installer is really just a stub. That means that when the user first loads a ShiVa3D web game, the plugin attempts to download the playback components necessary to play the game. Unfortunately, these components were also requested from the ShiVa3D server, which was no longer online. And Wayback Machine had not saved these files. I had the game files, and I had the plugin, but I still couldn’t play the game!</p><p>At this point I was stumped, so I searched the internet to see if anyone else had reported the same problem. Sure enough, I found <a href="https://web.archive.org/web/20190331194444/http://shiva-engine.com/forum/viewtopic.php?f=20&amp;t=30304">this thread</a> on the ShiVa forums describing the same issue. I learned from the thread that the beta version of the player should be unaffected by the problem, so I looked for a game that used the beta version. Soon I found one on GameJolt called <a href="https://gamejolt.com/games/kumoon/42309">Kumoon</a>.</p><figure><img alt="Kumoon playing in Flashpoint using the standalone ShiVa player" src="https://cdn-images-1.medium.com/max/1024/1*AT4fcVTev6UpqkVH9CO6Xg.png" /><figcaption>Kumoon playing in Flashpoint. Read on to learn how we did it!</figcaption></figure><p>When I tried to load this game, I discovered a whole new problem: the servers for the <em>beta version </em>of ShiVa Web Player had an expired SSL certificate. This meant that I could only connect to the site over HTTP, although the game attempted to load a script from it over HTTPS. So once again, I added the game files, HTML, and script to Flashpoint in order to work around the problem with the original website. But did the plugin work this time?</p><p>…No, Kumoon did not work either. Somehow, although the beta server was still online, the URL for the required components did not exist. I gave up in frustration.</p><p>Fast-forward nearly seven months, to October 28. That evening, I had a sudden epiphany. A while ago, I remembered, LeoV from the Flashpoint <a href="https://discord.gg/qhvAkhWXU5">Discord group</a> had found a standalone Unity Web Player installer inside the installer for the Unity development environment. I had been searching for an installer for that specific Unity version everywhere, but unable to find one. <em>What if I could apply this idea to ShiVa Web Player, too?</em></p><p>To test my idea, I visited the <a href="https://web.archive.org/web/20200809042911/https://shiva-engine.com/">ShiVa3D website</a> and downloaded the free ShiVa 1.9.2 Web Edition. Since I wasn’t planning on creating my own ShiVa3D content, I simply opened the installer in <a href="https://www.7-zip.org/">7-Zip</a> and examined its files. At first I was disappointed: the ShiVa3D Web Player installer was the same as the one I already had. But I soon found something more interesting.</p><figure><img alt="The ShiVa Web Edition installer open in 7-Zip" src="https://cdn-images-1.medium.com/max/1024/1*9sxM4v9w5zpSA08Ugxyu9A.png" /><figcaption>“S3DPlayer-1.9.2.0.exe”, it turns out, is the standalone desktop player!</figcaption></figure><p>Jackpot! After I installed the program, I could play any ShiVa3D STK file, including ones that were originally embedded on webpages. I discovered that for better or worse, ShiVa Web Player files are identical to their desktop counterparts, and are only lacking the executable and components necessary to play them, since this role is fulfilled by the plugin. This means that ShiVa Web Player games can reach ludicrous file sizes. In 2013, who in their right mind was going to sit through a hundred megabyte download just to play a web game? It’s no wonder this plugin never caught on.</p><p>Anyway, since ShiVa Web Player content wasn’t really “optimized for web”, this meant that the desktop player was capable of playing plugin content just fine. This is a very different situation from Unity Web Player; better optimization means that Unity Web Player files can only be played with the browser plugin. Gamers in 2013 hadn’t suffered in vain!</p><figure><img alt="The opening cutscene of The Hunt, playing in the ShiVa desktop player" src="https://cdn-images-1.medium.com/max/1024/1*RZe4GI-mtGX0jzA_Rkcp0Q.png" /><figcaption>The opening cutscene of The Hunt, playing in the ShiVa desktop player</figcaption></figure><p>All I had to do now was get this new program working in Flashpoint. And at first, everything seemed so flawless! It was too good to be true. The ShiVa3D Player was portable, so I could just copy it from its Program Files location directly into Flashpoint. The program could load any ShiVa3D game filename or URL. It even had a command-line parameter to determine whether it started in fullscreen. I just needed to figure out how to get the player to use Flashpoint’s proxy.</p><p>The first thing I tried was to use the Flashpoint Redirector. (The Redirector has since been replaced by <a href="https://github.com/FlashpointProject/FlashpointProxy">Flashpoint Proxy</a>, but back then, it was the best we had.) The Redirector sets the system proxy, so if ShiVa3D Player obeys the system proxy (as most programs do), then it should work fine in Flashpoint. Unfortunately, it does not obey the system proxy. Next, I tried setting the HTTP_PROXY environment variable using a batch file. This did not work either.</p><p>I was stumped once again, so I searched the internet. Unfortunately, a lot had changed in seven months. The entire ShiVa3D forums were replaced with a page stating “This site is currently down for maintenance — please come back soon.” Incidentally, I discovered that the server for the beta version of the ShiVa3D Web Player was completely gone as well. In fact, if I did not have the foresight to save the forum threads mentioned in this article to Wayback Machine, they would be gone too.</p><p>With everything that could have possibly helped me wiped from the internet, I decided to try my luck with the documentation included with the development environment. I scoured the help PDF, but I found absolutely nothing about proxy settings! As far as I could tell, ShiVa had no way to use anything but a direct internet connection.</p><p>So what could I do with a direct internet connection? I couldn’t use Flashpoint’s fancy “fake internet”, but I <em>could </em>use Flashpoint’s server the old-fashioned way, using <a href="https://en.wikipedia.org/wiki/Localhost"><em>localhost</em></a>. Luckily for us, nearly all ShiVa Web Player games are self-contained, and do not require internet access or to be located on a particular website. I created a simple batch file that could convert a game’s original URL to a localhost URL and launch it:</p><pre>SET URL=%*<br>SET URL=http://localhost:22500%URL:~6%<br>START /B ShiVa3D\S3DEngine.exe --fullscreen=0 %URL%</pre><p>It was a bit of a hack, but it worked! And just like that, we had a new technology supported in Flashpoint. I made a <a href="https://bluemaxima.org/flashpoint/datahub/ShiVa3D_Curation">curation tutorial</a>, and we’re discovering more games, animations, and other oddities all the time. As of Flashpoint 8.2, our contributors have saved <strong>87 </strong>ShiVa3D web games and <strong>53</strong> animations — I didn’t think so many existed on the internet! We’ve also improved our implementation, replacing my original batch file with a fancy <a href="https://github.com/FlashpointProject/FlashpointSecureTools/tree/master/FlashpointSecurePlayer">Flashpoint Secure Player</a> configuration.</p><p>As this story demonstrates, it’s not always programming skill that moves the Flashpoint project forward (though tons of coding goes into developing Flashpoint Launcher and Secure Player; shoutout to our amazing developers!). Often, breakthroughs are a matter of collaboration, dedication, and a bit of creative thinking. Volunteering for Flashpoint is rewarding because there are so many ways to make a difference, regardless of your skill level. If this sounds interesting, be sure to check out our <a href="https://bluemaxima.org/flashpoint/">website</a> and join our <a href="https://discord.gg/qhvAkhWXU5">Discord</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20c2a2f486ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bluemaximas-flashpoint/shiva3d-web-games-what-they-are-and-how-we-saved-them-20c2a2f486ec">ShiVa3D Web Games: What They Are, and How We Saved Them</a> was originally published in <a href="https://medium.com/bluemaximas-flashpoint">BlueMaxima’s Flashpoint</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Tour of the Adobe Director File Format]]></title>
            <link>https://nosamu.medium.com/a-tour-of-the-adobe-director-file-format-e375d1e063c0?source=rss-f078c4ba17b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e375d1e063c0</guid>
            <category><![CDATA[reverse-engineering]]></category>
            <category><![CDATA[macromedia-director]]></category>
            <category><![CDATA[adobe-director]]></category>
            <category><![CDATA[file-format]]></category>
            <dc:creator><![CDATA[nosamu]]></dc:creator>
            <pubDate>Fri, 25 Oct 2019 10:57:10 GMT</pubDate>
            <atom:updated>2023-08-11T23:45:19.589Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A Macromedia Director 5 Movie, displayed in a hex editor." src="https://cdn-images-1.medium.com/max/1024/1*i4BG84SaKSfyFEF67tU1Wg.png" /><figcaption>A Macromedia Director 5 Movie, displayed in a hex editor. You’ll learn all about the chunks visible here!</figcaption></figure><p>Anthony Kleine, known online as Tomysshadow, has amassed expert-level knowledge of the Adobe/Macromedia Director Movie file format. In our recent text conversation, he gave me a great rundown of this knowledge. Because the details were so fascinating to me, I decided to condense and edit his messages into a set of “lecture notes.” And if you’d like to delve into more of the details, I’ve provided helpful links at the end of the article. The Director file format can feel dizzying in complexity, but this article is the best place to begin. So let’s get started!</p><h4>Introduction</h4><p>The first thing is to just ignore Shockwave Movies (.DCR files) for the time being and focus on Director Movies (.DIR) since you need to understand Director Movies before you can understand the Shockwave Movie format.<br>Director Movie Files use a RIFX container. This format has a long history, beginning as the default multimedia format of Windows 3.1. If you’ve looked at a lot of archive formats before this is likely par for the course for you. The file consists of Chunks, each beginning with a ChunkID (taking the form of a FourCC.) It’s similar to a RIFF container, like what WAV uses, except that RIFX containers can either be little or big endian. If the file is big-endian, it will begin with the ID RIFX. If it’s little-endian, it will begin with the ID XFIR. Whether the file is little or big endian depends on the processor of the computer that saved the file, but Director is always capable of opening files of either endianness. All Director versions before 11 were not designed for Intel Macs and that’s why they save big-endian files.</p><p>For the purposes of learning the format, it can be easier to inspect big-endian files since that way, not everything will be backwards and you can acquaint yourself with the format better. However, since Windows uses an Intel processor it will save little-endian files, so you may want to search around for a game made on the Mac for some files that will be easier on the eyes. Note that saving one of these files on Windows with a tool like dirOpener or Movie Restorer will swap the file’s endianness.</p><h4>The Structure</h4><p>Alright, so let’s actually talk about the format structure.<br>The first thing in the file is its ID (RIFX or XFIR) followed by the length of the container as an INT32. Then we have the codec (in the case of most Director movies, this is MV93, which is short for Movie 1993, the year of the specification.)</p><p>Director Movie Files can have a variety of Chunks, but the first one is always the Initial Map, with a ChunkID of imap. (note: Initial Map is just a guessed name, since we don’t know for sure.) The Initial Map has the absolute address of the Memory Map in the file. I’ll explain why the Initial Map needs to exist in a bit.</p><p>The most important value (for our purposes) in the Initial Map is the second INT32, which is the Memory Map’s Position. The Memory Map is a Chunk with a ChunkID of mmap. It is an array which lists all of the resources in the Movie in order. Its job is what it sounds like — if you’re familiar with the PE format, think of this kind of like the sections of an EXE. The purpose of the Memory Map is to say where resources are in the file and their size, so that they can be loaded into memory.</p><p>You might be wondering why the Memory Map needs to exist, when it’s easy to just loop over the sections yourself by using the RIFX format. Well, it’s actually to serve as a performance optimization. You see, when you delete a resource in Director, it does not actually get removed in the Director Movie File — because if it did, everything after that resource in the file would need to be moved to earlier in the file, which would make saving take longer. To get around this, when you delete a resource in Director, it does not get deleted from the Movie File — instead, the pointer to that resource is made null in the Memory Map. This is akin to “deleting” a chapter of a book by not mentioning it in the Table of Contents. It’s much faster to erase one line in the Table of Contents than it is to remove all of the actual pages.</p><p>This does pose a problem however. If you add a lot of resources, the Memory Map gets long enough that nothing can be fit onto the end without moving every other resource later in the file. So, this is the purpose of the Initial Map. If the Memory Map gets too long, a brand new, longer one is created at a different location, and the Initial Map now points to the new one. This effectively makes it so every time you delete something in Director, the only thing that actually has to be changed is the pointer to it, rather than deleting the actual resource itself. The upper limit on how big an mmap chunk can be is the maximum size of an INT32, which is pretty big.</p><p>Before we go any further, we need to talk about ResourceIDs. A ResourceID is the index of a resource in the Memory Map. (Remember that The Memory Map is an array.) So for example, the first resource in the Memory Map is the RIFX Container, so it has a ResourceID of 0. The second is the Initial Map so it has a ResourceID of 1. This goes up to the last element of the Memory Map, whose index will never be greater than the maximum INT32. This upper limit allows Director to store ResourceIDs as INT32s.</p><p>But remember, INT32s are signed! So what does Director do with all those negative numbers? They don’t go unused — Director uses negative ResourceIDs to refer to resources that it has built in. For example, let’s say you have a palette resource. If the ResourceID is 57, 103, 472, or any other positive number, that refers to a resource in the Memory Map, since it’s an array indexed from 0 upwards. Meanwhile, a ResourceID of -100 might refer to the Windows system palette, -101 the Mac palette, and so on. Director can use those numbers because they aren’t positive, and they can’t possibly be in the Memory Map, because that array starts at 0 and goes up.</p><p>Another thing I should mention briefly before we continue is that Director never truly “reads” Chunks. The Chunks are actually just dumps of the state of Director’s memory in various places at the time of saving. When opening the file, the Chunk’s data is simply copied back into memory without being read/parsed.</p><p>So to be clear, all chunks are actually memory dumps. Which is why finding out how they are read is so difficult. It’s not like they are all read in nicely with something like readInt32 for example. Instead, it’s more like they are a bunch of C++ structs and Director simply creates one of these structs and points it to the Chunk. That makes it so only when the properties are actually used can you find out what they do.</p><p>So if chunks are just loaded directly into memory, you might think you could you use a tool to watch how Director’s memory changes. But surprise! Director uses a custom heap manager (specifically, SmartHeap). Windbg is totally useless! You’re better off opening a file, changing something, then saving the file and seeing what changed in a particular Chunk, which you can of course do anyway. The problem being, a bunch of other irrelevant values will also change because that is the nature of just dumping sections of memory.</p><h4>Key Mapping Pointers</h4><p>Anyway, so far, here is what the format looks like:<br>RIFX Container -&gt; Initial Map -&gt; Memory Map<br>It’s also worth noting that the resources in the Memory Map are not necessarily in order by address. In fact, most of them are not in any particular order at all. However, the first four resources of the Memory Map must always be the same. The first, second and third are the aforementioned RIFX Container, Initial Map and Memory Map (yes, the Memory Map does reference itself.) The fourth is the Key Mapping Pointers (an inferred name), which has a ChunkID of KEY*.</p><p>Okay, so we have the RIFX Container, which has the Initial Map, which we can use to find the Memory Map. The next thing we need to do is find the Key Mapping Pointers with a ChunkID of KEY*. This is always the fourth resource in the Memory Map, which is how we find it. The Key Mapping Pointers Chunk is probably the most difficult Chunk for beginners to understand. It allows an “owned by” relationship to exist between resources. For example, Sound Headers and Sound Samples can be “owned by” a Cast Member. The Key Mapping Pointers chunk has an array, each element of which consists of two ResourceIDs and one ChunkID. A ResourceID is the index of the resource in the Memory Map. (Remember that The Memory Map is an array.) So for example, the first resource in the Memory Map is the RIFX Container, so it has a ResourceID of 0. The second is the Initial Map so it has a ResourceID of 1, and so on. The first INT32 is the ResourceID of the owned Resource. The second INT32 is the ResourceID of the owner Resource. And then there is the ChunkID of the owned Resource.</p><p>Now, here’s how this actually works. Let’s say that Director encounters a Cast Member, and it is a sound. So Director knows that this Cast Member owns Sound Headers and Sound Samples. So it will search every Key Mapping Pointer, until it finds one with both the ChunkID it is looking for, and the ResourceID of the owner Chunk (since it already has the owner chunk, and is looking for the owned one.) Sound Headers have a ChunkID of sndH, so it’ll stop when it finds one that has a ChunkID of sndH and is owned by the Cast Member it knows is a sound. From there, it will get the ResourceID of the Sound Headers, which it can then use to find those Sound Headers by using the Memory Map.</p><p>This sounds really complicated, but it’s simple in reality. It’s just a table where you plug in two things you do know (the owner, and what you’re looking for) in order to find one thing you don’t know (the owned chunk). This is important to understand, because after you’ve found the Initial Map, and then the Memory Map, the Key Mapping Pointers is what we will use to find everything from here on out. This is because there are some chunks which are owned by the Movie itself, which always has a ResourceID of 1024.<br>I don’t know why they chose 1024. I just know that looking at Director in IDA, it is a constant and that constant is 1024.</p><p>Now, there is one other very important aspect of ResourceIDs, which is that they are not exclusive! You see, the Movie always has a ResourceID of 1024 — but there can be more than 1024 Resources in the Memory Map. So what happens if you have 1024 Resources in the Memory Map? Does the 1024th one become blank, as to not be confused with the Movie? Well, no — if you have 1024 sound Cast Members, for example, in the Memory Map, the 1024th one will in fact be a sound Cast Member. But, here’s the thing — when it looks in the Key Mapping Pointers for a resource that is owned by another one, it is looking for a particular resource. For example, with sound Cast Members, Director will only look for Sound Headers and Sound Samples. So it’ll only consider the resource owned by the other one if it both has the ResourceID of the owned chunk AND also the ChunkID of what it is looking for (sndH or sndS). Both the Movie and the sound Cast Member can have the same ResourceID, because when Director looks for resources owned by the sound Cast Member, it’ll only look for sound-related stuff, and ignore the movie-related stuff. As a result, certain Resources can only own certain other types of Resources, otherwise there would be a conflict. This is because a ResourceID is not like a primary key — it’s not exclusive to one resource alone.</p><h4>What Belongs to the Movie?</h4><p>So, let’s talk again about opening our movie. The first thing we do is open the RIFX Container, the Initial Map leads us to the Memory Map, which leads us to the Key Mapping Pointers. Now, Director is going to find a few things that the Movie owns, and it can do this because the Movie always has a ResourceID of 1024.</p><p>The first thing it needs to find is the Config. Depending on the Director version, the Config will either have a ChunkID of VWCF or DRCF (which is short for VideoWorks Config and Director Config respectively.) Director Configs are exactly the same as VideoWorks Configs though, only the ChunkID is changed and Director will always search for either. They didn’t change it from VWCF to DRCF until around Director 6, though even Director 12 checks for both of them. If a Movie has more than one Config it causes undefined behaviour. (This was actually a CVE at one point because having more than one Config could cause heap corruption.)</p><p>The Config, as you might imagine, has some basic properties about the movie itself. This includes the version number, stage size, background colour and etc. In older Director versions where only one Cast was allowed, Cast Properties were also stored here, but now they are stored somewhere else. Also, it’s worth mentioning that Config is not actually a guessed name, as it is one of the clipboard types registered by Director, so we know this is its official name.</p><p>The next thing that is owned by the Movie itself is the Cast Properties, which has a ChunkID of MCsL (which is short for Movie Cast Libraries.) This Chunk was introduced in Director 5 to allow Movies to have multiple Casts. The Cast Properties, which used to be a part of the Config, were moved here. This is a list which has the names, filenames (if external), minimum and maximum member number (will touch again on this in a moment), number of members, and most importantly, ResourceIDs of the Casts. That’s right — Casts have ResourceIDs too! And again — they’re not exclusive, so it can be the same ResourceID as anything else.</p><p>Another resource owned by the Movie is the Sort Order chunk. This is an array of INT32s, each of which form the number property of a Cast Member. Each INT32 is really made up of two INT16s: the two most significant bytes of each INT32 represent the Cast’s index, and the two least significant represent the Cast Member’s index. The number property allows Director to match Cast Members to slots in the Cast window, regardless of where the Cast Member resources actually are in memory.</p><p>This is where the minimum and maximum member number come in! Remember how the Cast’s index is represented by an INT16? This explains why the maximum number of Cast Members per Cast is 32000 — I’m certain it’s just 32768 rounded down. The minimum member number (minMember property) also shows something interesting about Director. For example, if the first ten members of a Cast are blank, Director can avoid having 10 null slots in the Cast Mapping Pointers where the empty Cast Members would be. Instead, Director actually treats the 11th member as the first one internally, and adds the minMember to it to pose the illusion to the author that it is the 11th.</p><p>Another thing that belongs to the Movie is the Score. The Score has a ChunkID of VWSC (which stands for VideoWorks Score). Note that this Chunk abbreviation was never changed from VW to DR (in fact, Config is the only chunk that did change in this way).</p><p>The format of the Score is probably the most varied thing between Director versions. Unlike the Cast, which consists of many different Chunks, the Score is entirely one chunk. It is also easily the most ridiculously complex, so much so that I’m not going to explain it in too much detail. One thing to note however is that the first five channels are always dedicated to timing, transitions, sound 1 &amp; 2, and scripts.</p><p>The thing is, what you see in a Director Movie File is actually lightly compressed (at least in Director 8.5 which is the primary version I inspected). The Score actually pads all the channels to a certain length in memory, but if they were saved in the file that way it’d be mostly blank, so it is actually modified to have a pretty stupid RLE implementation before saving.<br>It’s sort of like MIDI — it says which sprites are on which frame. Having more channels requires more memory, because like I said, in memory they have a fixed width. This means that the majority of the memory describing the Score is likely to be blank, but it comes with the performance optimization of always being able to know exactly where a particular sprite is in memory. This can be quite inefficient for movies that skip a lot of channels. If Director didn’t implement RLE compression, Director Movie Files would probably be much larger because of the Score alone. Or at least, it does use more memory. But for the CPU, of course, it will very much improve performance.</p><p>Note that what I am saying here does not apply to all Director versions. Like I said, it changed a lot, especially from Director 4–7. What I am explaining mostly applies to Director 8.5 and onwards, and I haven’t really looked into Director 7 and below. ScummVM does support some of those versions if you want a reference.</p><p>Anyway those are the main things the Movie owns. It does also own some other uneventful Resources. For example, your Favorite Colors (FCOL), FileInfo (VWFI), Guides and Grid (GRID), some of which are only accessed during authoring. For example, Favorite Colors allow you to choose some colours that will always appear in a colour picker.</p><h4>Where are the Cast Members?</h4><p>Alright, back to the Cast. Here is an updated summary of the file structure so far:<br>RIFX Container -&gt; Initial Map -&gt; Memory Map -&gt; Key Mapping Pointers -&gt; Cast Properties</p><p>Now, the ResourceID of the Cast is important. This is going to allow us to find Resources owned by the Cast.<br>And those Resources are the Cast Mapping Pointers, Lingo Context, CastInfo, and Score References.</p><p>One of the craziest things is when you have a Director movie as a cast member. I’ll have to talk about that, but not yet.<br> <br>The Cast Mapping Pointers chunk has — guess what — more ResourceIDs! These are actually the ResourceIDs of the Cast Members in order, with any blank spaces being null. Finally!</p><p>So we open the RIFX Container, use the Initial Map to find the Memory Map, which we use to find the Key Mapping Pointers, which we can use the ResourceIDs from in conjunction with the Memory Map to find the Cast Properties, which gives us the ResourceID of the Cast, which we then use with the Memory Map again to find the Cast Mapping Pointers, which gives us the ResourceIDs of the Cast Members, which we use with the Memory Map to find the Cast Member’s chunks. You got all that?</p><p>This is years. This is years of research here. I don’t expect anyone to understand it in a day, to be honest.</p><p>But anyway, that’s how you get at the Cast Members. What about Lingo?</p><h4>Getting the Lingo</h4><p>The Cast also owns the Lingo Context, which has a ChunkID of Lctx. Each Cast has its own Lingo Context. The Lingo Context has the ResourceID of the Lingo Names, and the ResourceIDs of the Lingo Scripts. Those have the ChunkIDs of Lnam and Lscr, respectively. The Lingo Names have strings which can be turned into symbols, such as “go” or “alert”. These strings are used across the multiple Lingo Scripts owned by the Lingo Context. The format of the Lingo Names is simply a bunch of C Strings back to back.</p><p>Now, this is why you can’t have a Lingo decompiler without being able to read the rest of the format. You can’t even get here without finding the Casts, which you can’t get to without finding the Key Mapping Pointers and everything else before it. You also can’t use the ResourceIDs in the Lingo Context to find the other Lingo-related Chunks without having the Key Mapping Pointers and Memory Map at the ready.</p><p>So the chunks are dependent on one another. Without the Lingo Context, what you effectively have is the scripts without symbols, but the symbols are very important to the decompilation! You can’t properly read the Lscr chunks without knowing which Lingo Names belong to which Scripts.</p><p>Now, remember how I said that these chunks are all just dumps of Director’s memory? If you look at a Lingo Script chunk, it might seem a bit perplexing, because there seems to be quite a few values that are repeated or unused<br>This is because the Lingo Script chunk has a buffer that is normally empty, but this buffer is used as the stack during playback. Once loaded into memory, the Lingo Script chunk is used to track the state of all aspects of the Lingo Script. If you’re thinking of it like a struct — you could have a Lingo Script, with a &lt;std::vector&gt; stack, as an example.</p><p>The Lingo Script chunk has quite a few numbers in it. Importantly, the Lingo Script has the ResourceID of the Cast Member it’s for. The Lingo Scripts are not actually owned by their Cast Members — they don’t appear in the Key Mapping Pointers. Instead, the Lingo Context belongs to the Cast, and the Lingo Scripts state which Cast Member they are for. This means that you cannot find out which Lingo Script “belongs” to a Cast Member. You can only do the reverse — find out what Cast Member a Lingo Script is for.</p><p>Also, the scriptText is NOT stored in the Lingo Script chunk. Everything in the Lingo Context and below is bytecode related. The scriptText is a property of the Cast Member. That said — I’m not sure how something like Parent Scripts work. That is still an unknown to me.</p><p>Anyway, so that’s where you find Lingo — it belongs to the Cast, for which the ResourceID is found in the Cast Properties, which belongs to the Movie.</p><h4>Cast Member Types</h4><p>But! I still haven’t talked about all the Cast Member types! There are a ton of them, but Director supports 15 major ones.</p><p>They are:<br> 1. Bitmaps<br> 2. Film Loops<br> 3. Text<br> 4. Palettes<br> 5. Pictures<br> 6. Sounds<br> 7. Buttons<br> 8. Shapes<br> 9. Movies<br>10. Digital Videos<br>11. Scripts<br>12. Rich Text<br>13. OLE<br>14. Transitions<br>15. Xtras<br> <br>Let’s explain them all one by one. The important thing to understand is that Cast Members can own media as separate resources. The Cast Member itself is, again, like a struct — it has a bunch of properties describing what the Cast Member is. But the media is a different Resource — which is found by plugging in the ResourceID of the Cast Member into the Key Mapping Pointers.<br>Cast Members have a ChunkID of CASt.</p><p>The <strong>Bitmap</strong> is the first type of Cast Member on the menu. They can own Bitmap Data (BITD,) Editable Media (ediM,) and an Alpha Channel (ALFA) in the event the bitmap is compressed as JPEG in a Shockwave Movie. (This will only actually appear in a Director Movie File when using dirOpener on a Shockwave Movie since it’s not compressed to JPEG until after exporting.)<br>The Bitmap Data (BITD) is what Director treats like a BMP file. It is losslessly RLE compressed, which Director refers to as Standard compression. They can have a variety of bit depths, and may or may not rely on a palette. Bitmap Data is just the raw colour data. All of the other properties like width, height, bit depth and palette to use are part of the Cast Member which owns the media. This is another case where one Resource depends on another. You cannot render Bitmap Data without having the Cast Member that owns it first. This is because the width and height of the Cast Member doubles as the width and height to use when reading the Bitmap Data.</p><p>The Editable Media (ediM) Chunk is created if you choose from the Media dropdown to keep an editable version of the file on import. This just copies the contents of the original imported file literally. This means that when you choose to export the bitmap into an external editor, if you choose this option it will actually export the original file. Director will also reflect this in the external editor window, which will say JPG or PNG etc. in place of BMP, which is the Bitmap Data’s equivalent. When publishing as a Shockwave Movie, if you choose to compress to JPEG, the Bitmap Data is replaced by an Editable Media chunk with a JPEG image, and an Alpha Channel chunk (ALFA) to preserve alpha transparency despite being in JPEG, which is simply a map of the alpha channel.</p><p><strong>Film Loop</strong>s are the next type of Cast Members. They can own Film Loops, which have a ChunkID of VWCS. You will notice that this is just the ChunkID for the Score with the S and C flipped. Film Loops use the same format as the Score, and are actually just a Score which is owned by a Cast Member. That’s why during Director authoring, you can paste a film loop into the score as its original score data.</p><p>However, If they are the same format as the Score — why is the ChunkID different? Well, remember, ResourceIDs aren’t exclusive! If the ChunkID for a Film Loop was the same as the Score, then if a Cast Member were the 1024th Resource, there would be a conflict because that ResourceID would have two Scores associated with it! So they are the exact same, but they have a different ChunkID to avoid conflicting with the Movie Resource.</p><p>Next we have <strong>Text</strong> members. These are the basic Fields/Styled Text introduced in older Director versions. There are a variety of differences between this type and Rich Text. Rich Text is more similar to, well, RTF. This is a simple text member that isn’t as customizable. The main big difference between Text and Rich Text is that Text is rendered on the fly, while Rich Text is rendered to a bitmap. This means that Text can be edited during playback, but if the user doesn’t have the correct font installed it’ll fall back on something like Arial. Rich Text is rendered to a bitmap during authoring so it’ll display correctly no matter what, but can’t ever be changed during playback. The difference between Text and Rich Text during authoring is a lot like the difference between TXT and RTF. Text Cast Members own Styled Text media (STXT).</p><p>Next we have <strong>Palette</strong> Cast Members. These are fairly self explanatory. They can own Photoshop CLUT media (CLUT). These are Color Lookup Tables for a palette. If a Bitmap Cast Member depends on a custom palette, it will have the ResourceID of one of these Palette Cast Members. Otherwise, the Bitmap will use a negative number to refer to one of Director’s built-in palettes. Remember that this is possible because a ResourceID is an INT32, and a positive value refers to a resource defined in the movie, while a negative value refers to a built-in resource.</p><p>Then there are <strong>Picture</strong> Cast Members. This is a Macintosh PICT copied into the Movie file, just look up Macintosh PICT.</p><p>Then there’s <strong>Sound</strong> Cast Members. They can own Sound Headers (sndH) and Sound Samples (sndS.) They are exactly what they… sound like. Lossless, uncompressed PCM samples. They can also own Macintosh Sound Resources (snd) if importing a Macintosh Sound file. Sound Headers and Sound Samples (sndH/sndS) are Director’s WAV equivalent.</p><p>Note that in early Director versions, AIFF was the only cross platform external sound file format. External sound files were generally used when internal sound cast members would take up too much memory. As such, authors would often opt to play an AIFF file. External WAV files could only be played on Windows and external Macintosh Sound files could only be played on Mac.</p><p>What we have next are <strong>Button</strong> Cast Members. These actually also own Styled Text (STXT) media. The only difference between these and Text cast members is that they have a button look. In fact in the Director API both Text and Buttons use the exact same rendering subroutine.</p><p>Next there are <strong>Shape</strong> Cast Members which, in older versions of Director, owned Vector Shapes. In newer Director versions the rendering of these is just relegated to the Flash Xtra. As such, they own Xtra Media (XMED)</p><p>Then we have <strong>Movie</strong> Cast Members. A movie Cast Member is a Cast Member which can own… well… anything a Director Movie can own. When importing a Director Movie as a Cast Member, everything that Movie owned now belongs to the movie Cast Member. The Score of said Movie is changed to a Film Loop, again to avoid conflicts with the actual Movie. Everything the Movie owned is then added to the current Movie’s Memory Map and Key Mapping Pointers appropriately.</p><p><strong>Digital Video</strong> Cast Members can only link to external video files, so they can’t own any media within the Movie. There are lots of digital video types, which all use different Xtras. Despite being considered a “native” type, even QuickTime cast members use an Xtra. In fact, there are quite a few “native” types that actually use an Xtra. Even bitmaps rely on JPEG Agent when publishing to a Shockwave Movie, for example, and sounds rely on Shockwave Audio in the same situation. And text relies on the TextXtra. But around Director 4–5 that was much less the case. Director 4 didn’t even have Xtras yet, only XObjects. I think that if they designed Director today they just would’ve used Xtras for everything from the ground up.</p><p><strong>Lingo Script</strong> Cast Members, as discussed earlier, don’t own any resources either. This is because Lingo Scripts are not media. They belong to the Lingo Context, which belongs to the Cast, not individual Cast Members. Lingo Script Cast Members don’t have anything distinct about them aside from that you can select what types of scripts they are.</p><p>The scriptText is a little bit different. This is the code typed in the Script window, not the compiled bytecode. When a movie is protected, all of the scriptText is completely removed, and this is why we use decompilers! Anyway, the scriptText is a property of the Script Cast Member. Like other Cast Member properties, it is ingrained into the Cast Member itself. It is not a separate resource owned by the Cast Member.<br> <br><strong>Rich Text</strong> Cast Members are basically Cast Members which can have many more text styles, and notably are rendered as bitmaps during authoring. They own three Resources, with ChunkIDs of RTE0, RTE1 and RTE2 respectively. These represent the same thing but in different forms (which is really true of all Cast Member media — same thing in different formats applicable to different situations). The first is the actual style runs, the second is a plaintext version to be used by thumbnails and scripts, and the third is a bitmap render. I’ve talked about this before so I’m not going to reiterate in too much detail.</p><p>Next we have <strong>OLE</strong> Cast Members. I’m going to admit I don’t know what these can all own. I think they can own Bitmap Data as a render of themselves, but honestly I’m not sure. They can however own OLE Data (OLED). OLE cast members are often used to display documents such as excel spreadsheets. OLE is actually a Windows thing — it’s commonly used in other applications like MS Word. It is built on top of COM and allows importing a variety of objects that support it. Both Rich Text and OLE were introduced in Director 5.</p><p>The final type is <strong>Xtra</strong>. Which can be, well, anything! The Xtra itself defines what the Cast Member type is called in this case. Any other type Director supports is going to be via an Xtra.</p><p>Phew… and there you have it! I probably didn’t even cover half the chunks to be honest, it’s a tonne. Like, I didn’t mention Score References, which are owned by Casts. They ensure that an error occurs if External Casts are modified from what the movie expects. There’s a lot of unremarkable or only barely important chunks that are easy to forget exist, but this is the basic format rundown.</p><p>I didn’t even cover Shockwave Movies. We’d be here for another four hours probably.</p><p>I hope you found this information as interesting and valuable as I did! If you’d like to learn even more, here are a number of additional resources:</p><ol><li>Kleine, Anthony. <em>More Director Movie File Unofficial Documentation</em>. <br><a href="https://docs.google.com/document/d/1jDBXE4Wv1AEga-o1Wi8xtlNZY4K2fHxW2Xs8RgARrqk/edit">https://docs.google.com/document/d/1jDBXE4Wv1AEga-o1Wi8xtlNZY4K2fHxW2Xs8RgARrqk/edit</a></li><li><em>Team Earthquake Guide: Shockwave Unofficial Documentation and XDK Director Properties. <br></em><a href="https://docs.google.com/document/d/18FMRZ0EvR2uF9rKTtvt-TXyIMFIBVg13bUhmV3_iHD0/edit">https://docs.google.com/document/d/18FMRZ0EvR2uF9rKTtvt-TXyIMFIBVg13bUhmV3_iHD0/edit</a></li><li>Archive Team contributors. <em>Lingo bytecode</em>. <br><a href="http://fileformats.archiveteam.org/wiki/Lingo_bytecode">http://fileformats.archiveteam.org/wiki/Lingo_bytecode</a></li><li><em>ProjectorRays Shockwave Decompiler</em>. <br><a href="https://github.com/ProjectorRays/ProjectorRays">https://github.com/ProjectorRays/ProjectorRays</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e375d1e063c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Difference Between Flash and Shockwave]]></title>
            <link>https://nosamu.medium.com/the-difference-between-flash-and-shockwave-b27609808a02?source=rss-f078c4ba17b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b27609808a02</guid>
            <category><![CDATA[adobe]]></category>
            <category><![CDATA[shock-wave]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[flash]]></category>
            <dc:creator><![CDATA[nosamu]]></dc:creator>
            <pubDate>Mon, 15 Oct 2018 01:10:58 GMT</pubDate>
            <atom:updated>2021-07-15T22:40:18.182Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*4l-70lqaxs9lV8K7Tza5Bw.jpeg" /></figure><p>Over the past few months, I’ve been working with the folks over at <a href="https://blog.usejournal.com/adobe-flashs-gaming-legacy-thousands-upon-thousands-of-titles-and-my-efforts-to-save-it-58c14811558a">Flashpoint</a> to preserve web games. One of the questions I hear most often is: What is the difference between a Flash game and a Shockwave game? I’ve adapted the following article from a series of chat messages written by Anthony Kleine, known online as Tomysshadow. Thanks to him for providing this great explanation!</p><p>When asking the difference between Shockwave and Flash, you’ll often get the answer that they’re two products that have nothing to do with each other<br>That is almost true, but not entirely true.</p><p>Macromedia Director was originally designed to make software development easy, and it found its first home on the CD-ROM. However, in the 1990s, it began finding a new home on the web. “Shockwave” was Macromedia’s term which meant “compressed for the web.”</p><p>The first entry in the Shockwave line of products was Shockwave Director Player — so called because it could play Director Movies which had been compressed for the web. Because it was, at the time, the first and only product in the Shockwave line of products, Shockwave Director Player was often shortened to just “Shockwave.”</p><p>Enter Flash. Again, Macromedia wanted Flash Movies to be able to be compressed so they could be downloaded quickly over the web — so they made the Shockwave Flash Player plugin, so called because it could play Flash Movies which had been compressed for the web.</p><p>So there was Shockwave Director Player, to play compressed Director Movies, and Shockwave Flash Player, to play compressed Flash Movies. The problem is, by this point, everyone already knew Shockwave Director Player as just “Shockwave.” To those uninformed, it seemed that there was now both a Shockwave AND a Shockwave Flash. Shockwave Flash Player was more often referred to as just Flash, to avoid confusion with what was already being referred to as Shockwave.</p><p>So when we say Shockwave, we’re referring to the first word in Shockwave Director Player, but when we say Flash, we’re referring to the second word in Shockwave Flash Player.</p><p>This was the case until Adobe acquired these names from Macromedia, at which point they just decided to rename the plugins to what they were being popularly referred to as. Now what was Shockwave Director Player is just called Shockwave, and what was Shockwave Flash Player is just called Flash. In order to further undo the confusion, SWF was changed to stand for Small Web Format instead of ShockWave Flash.</p><p>There was actually a third Shockwave plugin — the little used Shockwave Authorware Player. As far as I’m aware it was mostly used in schools for educational software and never really found its way into gaming or the web at all. There was a web plugin for it as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b27609808a02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analyzing Eastern Mind: What’s the Deal with the Furoshiki?]]></title>
            <link>https://nosamu.medium.com/analyzing-eastern-mind-whats-the-deal-with-the-furoshiki-b89c3ba613a9?source=rss-f078c4ba17b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b89c3ba613a9</guid>
            <category><![CDATA[macromedia-director]]></category>
            <category><![CDATA[osamu-sato]]></category>
            <dc:creator><![CDATA[nosamu]]></dc:creator>
            <pubDate>Thu, 16 Aug 2018 04:11:51 GMT</pubDate>
            <atom:updated>2018-08-16T04:11:51.595Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Analyzing Eastern Mind: What’s the Deal with the Furoshiki?</strong></p><p>Some Eastern Mind players have noticed that the game’s Furoshiki displays weird and seemingly inconsistent behavior when clicked. Watch the clip below to see what I mean:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fclips.twitch.tv%2Fembed%3Fclip%3DRoundHilariousClamStrawBeary%26autoplay%3Dfalse&amp;url=https%3A%2F%2Fclips.twitch.tv%2FRoundHilariousClamStrawBeary&amp;image=https%3A%2F%2Fclips-media-assets2.twitch.tv%2FAT-cm%257C291398246-preview.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=twitch" width="620" height="351" frameborder="0" scrolling="no"><a href="https://medium.com/media/d4abb0b683fd20b2482bb79fecbce495/href">https://medium.com/media/d4abb0b683fd20b2482bb79fecbce495/href</a></iframe><p>Luckily, the Mac version of Eastern Mind was distributed with editable Macromedia Director files, meaning I could take a peek at how the code works. First, I found the “hitbox” of the Furoshiki sprite:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*j9wlN5fwOjT-fNp6BGj0AA.png" /><figcaption>A rectangle represents the Furoshiki’s “hitbox”</figcaption></figure><p>Next, I found the associated scripts. This script is attached to the Furoshiki sprite:</p><pre>on mouseUp<br>    if doubleClick() then<br>        ClickBag<br>    end if<br>end mouseUp</pre><p>And this is the clickBag handler called by that code (<em>handler </em>is Director’s name for a function)</p><pre>on clickBag<br>  if gFlag &lt;&gt; 1  then<br>    --    when Bag is close<br>    OpenBag<br>  else<br>    --    when Bag is Open<br>    closeBag<br>  end if<br>end clickBag</pre><p>As we can see, the clickBag handler simply toggles whether the bag is open or closed. But when exactly is the clickBag handler called? Looking at the first script, on mouseUp means that something happens whenever the bag’s sprite is clicked. But what happens? The condition doubleClick is checked, and if it’s true then the clickBag handler runs.</p><p>That brings us to the heart of the matter: what exactly satisfies the doubleClick condition? This is not up to the game; it’s decided by Director Player. And Director Player defines a double-click as 2 clicks on the same sprite within a very short period of time. This has weird implications: a triple-click counts as 2 double-clicks, a quadruple-click counts as 3 double-clicks, etc. Strangely enough, one triple-click will actually open the bag <em>and</em> close it again. That’s because both the 2nd and the 3rd click occur soon after another click on the same sprite, thus satisfying the definition of a double-click.</p><p>So there you have it, a very minor quirk of Eastern Mind explained in great detail. Kudos to you if you actually read the whole thing :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b89c3ba613a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>