<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span style="font-family: monospace; white-space: pre-wrap;" class="">> </span><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">Would you mind providing a disk image usable with oberon-risc-emu?</span></font><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">A disk image that works with the Oberon emulator has been uploaded to:</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">  <a href="https://github.com/andreaspirklbauer/Oberon-experimental/tree/master/Documentation/S3RISCinstall.tar.gz" class="">https://github.com/andreaspirklbauer/Oberon-experimental/tree/master/Documentation/S3RISCinstall.tar.gz</a></span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">To use it, download this file to your emulator directory and run:</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">  tar xvf </span></font><span style="font-family: monospace; white-space: pre-wrap;" class="">S3RISCinstall.tar.gz</span></div><div class=""><span style="font-family: monospace; white-space: pre-wrap;" class=""><br class=""></span></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">Then just start the Oberon emulator. EO should come up in a blitz.</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">——————————</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">PS: </span></font><span style="font-family: monospace; white-space: pre-wrap;" class="">I have not yet uploaded an Oberon disk image where the *entire*</span></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">Oberon system (i.e. module System and all its imports) is contained</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">as a *single* boot file in the *boot area* of the local disk (area</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">starting at block #2 on disk) - mainly because one would first need</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">to increase the size of the boot area itself to make room for the</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">enlarged boot file. It’s not difficult, just a little tricky. </span></font><span style="font-family: monospace; white-space: pre-wrap;" class="">If</span></div><div class=""><span style="font-family: monospace; white-space: pre-wrap;" class="">you want an image for THAT, it can be </span><span style="font-family: monospace; white-space: pre-wrap;" class="">provided in the </span><span style="font-family: monospace; white-space: pre-wrap;" class="">repository.</span></div><div class=""><span style="font-family: monospace; white-space: pre-wrap;" class="">Alternatively, you can just </span><span style="font-family: monospace; white-space: pre-wrap;" class="">follow the instructions provided at</span></div><div class=""><span style="font-family: monospace; white-space: pre-wrap;" class=""><a href="https://github.com/andreaspirklbauer/Oberon-building-tools" class="">https://github.com/andreaspirklbauer/Oberon-building-tools</a>. Takes</span></div><div class=""><span style="font-family: monospace; white-space: pre-wrap;" class="">only a few seconds, but requires a few additional source files.</span></div><div class=""><span style="font-family: monospace; white-space: pre-wrap;" class=""><br class=""></span></div><div class=""><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">It’s fun little exercise of what one can already do with the (still)</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">rather rudimentary Oberon system building tools. This must be the</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">absolutely fastest possible way to boot the Oberon system if it is</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">stored as a single binary file on disk - it really is absolutely</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">instantaneous (it better be, as the *entire* OS is transferred</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">"en bloc" from disk directly to main memory, without even invoking</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">the module loader; in fact, it doesn’t even require a working file</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">system; not even the directory root block (block #1 on disk) must</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">be initialized - nothing; just a single boot file, that’s it).</span></font></div></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">PS2: The next version of the building tools will include the</span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class="">ability </span></font><span style="white-space: pre-wrap; font-family: monospace;" class="">to create “partitions”. Surprisingly the whole thing can</span></div><div class=""><span style="white-space: pre-wrap; font-family: monospace;" class="">be </span><span style="white-space: pre-wrap; font-family: monospace;" class="">implemented with only a few lines of code - far cry from</span></div><div class=""><span style="white-space: pre-wrap; font-family: monospace;" class="">other </span><span style="white-space: pre-wrap; font-family: monospace;" class="">implementations that offer partition management.</span></div><div class=""><span style="font-family: monospace; white-space: pre-wrap;" class=""><br class=""></span></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></font></div><div class=""><font face="monospace" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></font></div></body></html>