<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: STABACKIT won't boot if disk is ODS5 structured in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563793#M68954</link>
    <description>By the way this system is running OpenVMS 7.3-2 with all recent patches on it. The SYSBOOT.EXE is on the disk but I found a small difference: It is located in[SYSE.syscommon.SYSEXE]! And there is the problem because after I renamed the "syscommon.dir" to "SYSCOMMON.DIR" everythings worked well! Only this directory was created in small characters, the others having capital letters!</description>
    <pubDate>Wed, 15 Jun 2005 03:34:50 GMT</pubDate>
    <dc:creator>Andreas Kaempfe</dc:creator>
    <dc:date>2005-06-15T03:34:50Z</dc:date>
    <item>
      <title>STABACKIT won't boot if disk is ODS5 structured</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563790#M68951</link>
      <description>Problem found: If you prepare an additional ODS5 disk with @SYS$UPDATE:STABACKIT (@SYS$SYSTEM:AXPVMS$PCSI_INSTALL_MIN.COM), after the boot command "&amp;gt;&amp;gt;&amp;gt; boot -fl e,0 dka100" it stops with "%APB-I-FILENOTLOC, Unable to locate SYSBOOT.EXE", "%APB-I-LOADFAIL, Failed to load secondary bootstrap, status = 00000910".&lt;BR /&gt;Same procedure with an ODS2 disk runs without a problem! Until this problem is fixed use ODS2!</description>
      <pubDate>Tue, 14 Jun 2005 08:45:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563790#M68951</guid>
      <dc:creator>Andreas Kaempfe</dc:creator>
      <dc:date>2005-06-14T08:45:41Z</dc:date>
    </item>
    <item>
      <title>Re: STABACKIT won't boot if disk is ODS5 structured</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563791#M68952</link>
      <description>Andreas,&lt;BR /&gt;&lt;BR /&gt;which version of OpenVMS ?&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Tue, 14 Jun 2005 09:29:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563791#M68952</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-06-14T09:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: STABACKIT won't boot if disk is ODS5 structured</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563792#M68953</link>
      <description>hex 910 = %SYSTEM-W-NOSUCHFILE, no such file&lt;BR /&gt;&lt;BR /&gt;is it there?</description>
      <pubDate>Tue, 14 Jun 2005 09:48:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563792#M68953</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-06-14T09:48:11Z</dc:date>
    </item>
    <item>
      <title>Re: STABACKIT won't boot if disk is ODS5 structured</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563793#M68954</link>
      <description>By the way this system is running OpenVMS 7.3-2 with all recent patches on it. The SYSBOOT.EXE is on the disk but I found a small difference: It is located in[SYSE.syscommon.SYSEXE]! And there is the problem because after I renamed the "syscommon.dir" to "SYSCOMMON.DIR" everythings worked well! Only this directory was created in small characters, the others having capital letters!</description>
      <pubDate>Wed, 15 Jun 2005 03:34:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563793#M68954</guid>
      <dc:creator>Andreas Kaempfe</dc:creator>
      <dc:date>2005-06-15T03:34:50Z</dc:date>
    </item>
    <item>
      <title>Re: STABACKIT won't boot if disk is ODS5 structured</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563794#M68955</link>
      <description>Andreas,&lt;BR /&gt;&lt;BR /&gt;this seems to be effected by the Parse Style settings of your current process when creating the disk with STABACKIT.COM&lt;BR /&gt;&lt;BR /&gt;$ SET PROC/PARSE=TRADITIONAL should prevent this problem from happening, SET PROC/PARSE=EXTENDED will create lowercase directory names.&lt;BR /&gt;&lt;BR /&gt;APB does not seem to be able to correctly handle lowercase directory names.&lt;BR /&gt;&lt;BR /&gt;If you care about this problem, consider to write 2 internal PTRs:&lt;BR /&gt;&lt;BR /&gt;- make sure AXPVMS$PCSI_INSTALL_MIN.COM sets parse style = traditional when creating a new SYSCOMMON directory tree on the target disk.&lt;BR /&gt;&lt;BR /&gt;- enhance APB to handle lowercase directory names on ODS-5 disks.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Wed, 15 Jun 2005 05:46:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/stabackit-won-t-boot-if-disk-is-ods5-structured/m-p/3563794#M68955</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-06-15T05:46:12Z</dc:date>
    </item>
  </channel>
</rss>

