<?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: New V7.3-2 driver patch kit. in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886504#M66844</link>
    <description>Thanks to all; I just tried HTTP downloading and then applied the &lt;BR /&gt;&lt;BR /&gt;SET FILE/ATTR=(RFM:FIX,MRS:512,LRL:512)&lt;BR /&gt;&lt;BR /&gt;fix it all appears good.  I'll close the thread.</description>
    <pubDate>Thu, 17 Feb 2005 22:30:25 GMT</pubDate>
    <dc:creator>Malcolm Wade</dc:creator>
    <dc:date>2005-02-17T22:30:25Z</dc:date>
    <item>
      <title>New V7.3-2 driver patch kit.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886498#M66838</link>
      <description>What's the go?  It downloads from the hp resource centre as a pcsi$compressed kit which PRODUCT INSTALL fails to read with a RMS-W-RTB error.  What's wrong with using a DCX EXE like all the others?&lt;BR /&gt;&lt;BR /&gt;Malcolm</description>
      <pubDate>Thu, 17 Feb 2005 17:16:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886498#M66838</guid>
      <dc:creator>Malcolm Wade</dc:creator>
      <dc:date>2005-02-17T17:16:11Z</dc:date>
    </item>
    <item>
      <title>Re: New V7.3-2 driver patch kit.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886499#M66839</link>
      <description>Hi Malcolm,&lt;BR /&gt;&lt;BR /&gt;  It's not supposed to do that! Please log a case with the support centre so we can look into it. Maybe the file has been microsofted on it's way to your OpenVMS system?&lt;BR /&gt;&lt;BR /&gt;  The PCSI$COMPRESSED kits are supposed to bypass the additonal step of unpacking the DCX compressed images. The plan is to phase out self expanding compressed images in favour of the "native" compressed image.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Feb 2005 21:07:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886499#M66839</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2005-02-17T21:07:37Z</dc:date>
    </item>
    <item>
      <title>Re: New V7.3-2 driver patch kit.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886500#M66840</link>
      <description>Malcolm,&lt;BR /&gt;&lt;BR /&gt;Did you download it directly to a VMS system&lt;BR /&gt;or go via some other box?&lt;BR /&gt;I downloaded direct to VMS and the kit is fine.&lt;BR /&gt;&lt;BR /&gt;Dave&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Feb 2005 21:36:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886500#M66840</guid>
      <dc:creator>David B Sneddon</dc:creator>
      <dc:date>2005-02-17T21:36:57Z</dc:date>
    </item>
    <item>
      <title>Re: New V7.3-2 driver patch kit.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886501#M66841</link>
      <description>Direct to my Windoze box which has always worked fine for the DCX EXE.  I then drag and drop the file to my VMS server via attached pathworks drives.&lt;BR /&gt;&lt;BR /&gt;From there I used to run the .EXE; now I just try PRODUCT INSTALL * and it fails.&lt;BR /&gt;&lt;BR /&gt;That all said; I have fixed my problem by using a interactive FTP session to get the file.  Using 'IE' and the web site stuff it all up.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Did you download it directly to a VMS&lt;BR /&gt;&amp;gt;system&lt;BR /&gt;&amp;gt;or go via some other box?&lt;BR /&gt;&amp;gt;I downloaded direct to VMS and the kit is&lt;BR /&gt;&amp;gt;fine.&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Feb 2005 22:05:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886501#M66841</guid>
      <dc:creator>Malcolm Wade</dc:creator>
      <dc:date>2005-02-17T22:05:49Z</dc:date>
    </item>
    <item>
      <title>Re: New V7.3-2 driver patch kit.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886502#M66842</link>
      <description>This is a bug in ITRC. The format of the files is changed from FIXED 512 to stream by the FTP transfer.&lt;BR /&gt;&lt;BR /&gt;The same happens for the compressed images, but the image activator doesn't care about the record format so RUN works.&lt;BR /&gt;&lt;BR /&gt;PCSI is more fussy, so it requires the expected file type.&lt;BR /&gt;&lt;BR /&gt;Try:&lt;BR /&gt; &lt;BR /&gt;$ SET FILE/ATTR=(RFM:FIX,MRS:512,LRL:512)&lt;BR /&gt;&lt;BR /&gt;This should "repair" the file. We'll need to find a way to convince ITRC &amp;amp; FTP to preserve the record attributes.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Feb 2005 22:11:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886502#M66842</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2005-02-17T22:11:25Z</dc:date>
    </item>
    <item>
      <title>Re: New V7.3-2 driver patch kit.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886503#M66843</link>
      <description>John, It may be difficult to "convince ITRC &amp;amp; FTP to preserve the record attributes."  Its likely easier to convince PRODUCT INSTALL to ignore them.</description>
      <pubDate>Thu, 17 Feb 2005 22:24:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886503#M66843</guid>
      <dc:creator>Garry Fruth</dc:creator>
      <dc:date>2005-02-17T22:24:52Z</dc:date>
    </item>
    <item>
      <title>Re: New V7.3-2 driver patch kit.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886504#M66844</link>
      <description>Thanks to all; I just tried HTTP downloading and then applied the &lt;BR /&gt;&lt;BR /&gt;SET FILE/ATTR=(RFM:FIX,MRS:512,LRL:512)&lt;BR /&gt;&lt;BR /&gt;fix it all appears good.  I'll close the thread.</description>
      <pubDate>Thu, 17 Feb 2005 22:30:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886504#M66844</guid>
      <dc:creator>Malcolm Wade</dc:creator>
      <dc:date>2005-02-17T22:30:25Z</dc:date>
    </item>
    <item>
      <title>Re: New V7.3-2 driver patch kit.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886505#M66845</link>
      <description>As above indicate; it's a 'feature' of the files being in PCSI* format and the method of dowloading.  Fixable in the interm via a SET FILE command.</description>
      <pubDate>Thu, 17 Feb 2005 22:32:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/new-v7-3-2-driver-patch-kit/m-p/4886505#M66845</guid>
      <dc:creator>Malcolm Wade</dc:creator>
      <dc:date>2005-02-17T22:32:10Z</dc:date>
    </item>
  </channel>
</rss>

