<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 2016-Apr-16 12:48 , Programmingkid
      wrote:<br>
    </div>
    <blockquote
      cite="mid:62F2349C-F8BB-419D-B07D-B36D90577BE8@gmail.com"
      type="cite">
      <pre wrap="">I wanted to share what I found out. If I remove the '\r' to '\n' patch that allows Mac OS 9 to boot, the boot script will stop executing at a r> word. This is the position:

<BOOT-SCRIPT>
here &gt;r
dev /
cr ." Checkpoint 1" cr " model" active-package get-package-property abort" can't find MODEL"</pre>
    </blockquote>
    <blockquote
      cite="mid:62F2349C-F8BB-419D-B07D-B36D90577BE8@gmail.com"
      type="cite">
      <pre wrap="">[...]


r&gt;               <---------------  This is where execution stops


[...]
This boot script was taken from the Mac OS 9 file "Mac OS ROM". 

Does anyone have any idea why removing '\r' characters from the script makes it work? 
</pre>
    </blockquote>
    <br>
    I'm baffled. There are two other lines above which are end-of-line
    sensitive, using the "dev" word:<br>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <div class="page" title="Page 133">
      <div class="layoutArea">
        <div class="column">
          <blockquote>
            <p><span style="font-size: 10.000000pt; font-family:
                'Courier'; font-weight: 700">dev </span><span
                style="font-size: 10.000000pt; font-family: 'Times'">(
                "device-specifier<eol>" -- )
              </span><span style="font-size: 9.000000pt; font-family:
                'Times'">Make the specified device node the </span><span
                style="font-size: 9.000000pt; font-family: 'Times';
                font-style: italic">active package</span><span
                style="font-size: 9.000000pt; font-family: 'Times'">.
              </span></p>
            <p><span style="font-size: 9.000000pt; font-family: 'Times'">Parse
              </span><span style="font-size: 9.000000pt; font-family:
                'Times'; font-style: italic">device-specifier </span><span
                style="font-size: 9.000000pt; font-family: 'Times'">delimited
                by end of line. Perform the equivalent of </span><span
                style="font-size: 9.000000pt; font-family: 'Courier';
                font-weight: 700">find-device </span><span
                style="font-size: 9.000000pt; font-family: 'Times'">with
              </span><span style="font-size: 9.000000pt; font-family:
                'Times'; font-style: italic">device-specifier </span><span
                style="font-size: 9.000000pt; font-family: 'Times'">as
                its
                argument.
              </span></p>
            <p><span style="font-size: 9.000000pt; font-family: 'Times';
                font-weight: 700">Used as: </span><span
                style="font-size: 9.000000pt; font-family: 'Courier'">ok
                dev device-specifier <eol><br>
              </span></p>
          </blockquote>
          You could try replacing the two lines with the equivalent
          find-device operations:<br>
          <blockquote>" /" find-device<br>
            " /openprom" find-device<br>
          </blockquote>
          which aren't end-of-line sensitive, but if that were the
          problem, we wouldn't be seeing the checkpoint 1 message.<br>
          <br>
          Usually when something blows up on a r>, that means the
          return stack has been clobbered - and I don't see anything
          there that looks like it would clobber it based on an eol. </div>
      </div>
    </div>
    <title>Microsoft Word - 1275.DOC</title>
  </body>
</html>