<?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: TOUR 2.0 availability in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tour-2-0-availability/m-p/4982907#M420217</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;HP pulls obsolete version of software from their website when the new version is posted.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=TOUR" target="_blank"&gt;http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=TOUR&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;To get archive versions, you need to open a software call to gain access to an ftp server that has the old versions.&lt;BR /&gt;&lt;BR /&gt;Its really incumbant on the local administrator to keep copies of software that he or she finds critical and not rely on HP to maintain archives. I imagine the cost of keeping every old version of every piece of software would be significant, even for a big company like HP,&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Mon, 05 Jun 2006 05:32:23 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2006-06-05T05:32:23Z</dc:date>
    <item>
      <title>TOUR 2.0 availability</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tour-2-0-availability/m-p/4982906#M420216</link>
      <description>Couple of years back I downloaded TOUR 2.0 from one of the HP website. Recently my server crashed and i did the reinstallation of OS. I need to install TOUR 2.0 but I didn't find the same in any of the HP website. Is there any way to get the same version back?.&lt;BR /&gt;Note: Currently 3.1 version of TOUR is available.</description>
      <pubDate>Mon, 05 Jun 2006 04:26:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tour-2-0-availability/m-p/4982906#M420216</guid>
      <dc:creator>Prabu_3</dc:creator>
      <dc:date>2006-06-05T04:26:48Z</dc:date>
    </item>
    <item>
      <title>Re: TOUR 2.0 availability</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tour-2-0-availability/m-p/4982907#M420217</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;HP pulls obsolete version of software from their website when the new version is posted.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=TOUR" target="_blank"&gt;http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=TOUR&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;To get archive versions, you need to open a software call to gain access to an ftp server that has the old versions.&lt;BR /&gt;&lt;BR /&gt;Its really incumbant on the local administrator to keep copies of software that he or she finds critical and not rely on HP to maintain archives. I imagine the cost of keeping every old version of every piece of software would be significant, even for a big company like HP,&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 05 Jun 2006 05:32:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tour-2-0-availability/m-p/4982907#M420217</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-06-05T05:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: TOUR 2.0 availability</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tour-2-0-availability/m-p/4982908#M420218</link>
      <description>comments was useful. I will follow up with HP support.</description>
      <pubDate>Mon, 05 Jun 2006 10:28:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tour-2-0-availability/m-p/4982908#M420218</guid>
      <dc:creator>Prabu_3</dc:creator>
      <dc:date>2006-06-05T10:28:04Z</dc:date>
    </item>
  </channel>
</rss>

