<p>Looks like we&#39;re having a mini-family reunion in June.</p><p>Last night, out of the blue, my mom&#39;s youngest brother reached out to me. He, his wife &amp; son are coming out west for some sort of memorial(on his wife&#39;s side) &amp; will be staying in the neighborhood for a week.</p><p>We&#39;re not terribly close; but my daughter &amp; his son were best pals whenever they saw each other as kids.</p><p>I&#39;m touched that he reached out to me &amp; nervously excited to hang out without my folks being intermediaries.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@zmz" class="u-url mention">@<span>zmz</span></a></span> <span class="h-card" translate="no"><a href="https://urusai.social/@thepi" class="u-url mention">@<span>thepi</span></a></span> excellent</p>

<p>that&#39;s so cute that this code considers &quot;256 instructions&quot; to be a meaningful length of time.</p>

<p>I just found a function (inside another function!) that&#39;s a fixed delay. How long is it?<br />it&#39;s a loop that runs 256 times!</p>

<p>I suspect there may be an issue here: I identified a variable as containing the Soundblaster IO port, right? and I&#39;m assuming everything that uses it is Soundblaster code.</p><p>But it may just be &quot;soundcard IO port&quot; and there&#39;s other sound device code mixed in here. So that&#39;s why some of it doesn&#39;t make sense as soundblaster, it&#39;s actually tandy 3voice or something</p>

<p>they&#39;re sending a... internal soundblaster test command? <br />(DSP 0xF0)</p><p>I dunno why this code is like this.</p>

<p>they&#39;re passing single bytes to functions! C widens integer parameters to a word, so on a 16bit system, they&#39;re passed in 16-bit registers.</p>

<p>yeah a compiler doesn&#39;t just start using CF to return bools instead of AX. This is assembly.</p>

<p>I bet broderbund bought this sound code. It feels completely different: This was either compiled on a different compiler or was written in assembly.</p>