<?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: Pathworks Remote Boot problem... in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/pathworks-remote-boot-problem/m-p/3960049#M54098</link>
    <description>Wow, that's going back to WFWG &amp;amp; PW for DOS days! The EWRK3.DOS image (DEC EtherWORKS 3 driver) is trying to load (TSR) and doesn't find the right configuration. There are files on the PC and also on the server (the network key disk) that hold config data, so you need to go through the PC's PW setup again; NETSETUP at least. Then, your old software and new NIC may or may not get along. The old stuff was pretty picky about the NIC. AFA any tricks to try, that was too long ago for me to remember.&lt;BR /&gt;</description>
    <pubDate>Tue, 13 Mar 2007 14:07:08 GMT</pubDate>
    <dc:creator>Doug Phillips</dc:creator>
    <dc:date>2007-03-13T14:07:08Z</dc:date>
    <item>
      <title>Pathworks Remote Boot problem...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pathworks-remote-boot-problem/m-p/3960048#M54097</link>
      <description>I have a PC that remote boots using a DE203 NIC to a Pathworks 4 server.  The NIC went faulty and was replaced.  I have used ezworks.exe to tell the card that remote boot is enabled.  On the Pathworks 4 server I have in NCP set and def the node char to have the replacement NIC hardware address.  A repl/enable sees the pc being loaded, but on the PC the following message appears.&lt;BR /&gt;&lt;BR /&gt;EWRK3 Remote Boot TSK Image Version V2.00.000&lt;BR /&gt;Copyright © 1993 by Digital Equipment Corporation&lt;BR /&gt;&lt;BR /&gt;Fatal Error: TSR failed, can not continue ….&lt;BR /&gt;&lt;BR /&gt;Anyone with any ideas what could be wrong?&lt;BR /&gt;&lt;BR /&gt;Thanks Nigel.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 12 Mar 2007 10:55:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pathworks-remote-boot-problem/m-p/3960048#M54097</guid>
      <dc:creator>Nigel Wright_1</dc:creator>
      <dc:date>2007-03-12T10:55:02Z</dc:date>
    </item>
    <item>
      <title>Re: Pathworks Remote Boot problem...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/pathworks-remote-boot-problem/m-p/3960049#M54098</link>
      <description>Wow, that's going back to WFWG &amp;amp; PW for DOS days! The EWRK3.DOS image (DEC EtherWORKS 3 driver) is trying to load (TSR) and doesn't find the right configuration. There are files on the PC and also on the server (the network key disk) that hold config data, so you need to go through the PC's PW setup again; NETSETUP at least. Then, your old software and new NIC may or may not get along. The old stuff was pretty picky about the NIC. AFA any tricks to try, that was too long ago for me to remember.&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Mar 2007 14:07:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/pathworks-remote-boot-problem/m-p/3960049#M54098</guid>
      <dc:creator>Doug Phillips</dc:creator>
      <dc:date>2007-03-13T14:07:08Z</dc:date>
    </item>
  </channel>
</rss>

