1 INFO-VAX	Sun, 11 Dec 2005	Volume 2005 : Issue 688       Contents: Re: CMUIP Patches . Re: Help with Storageworks Drive/BA364 problem/ Re: HP : Massive strike and protest march today  Re: MEMORY RULES FOR ES40-2   Re: Running Image From Procedure  F ----------------------------------------------------------------------  % Date: Sat, 10 Dec 2005 17:45:05 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: CMUIP Patches+ Message-ID: <439B6880.C56129FC@comcast.net>    Dave wrote:  > D > Does anyone know where I can dowload the patches for CMUIP v6.6-5? > H > I specifically need the FTP patches for the password fix as I recently) > upgrade and old VAX of mine to VMS v7.3  > ( > Is anyone out there still using CMUIP?  ' There isn't much traffic on this group.   1 I've cross-posted to comp.sys.dec and comp.os.vms   2 Maybe someone in those groups will have an idea...   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------    Date: 10 Dec 2005 12:51:29 -0800 From: mcbill20@yahoo.com7 Subject: Re: Help with Storageworks Drive/BA364 problem A Message-ID: <1134247889.232094.4900@g14g2000cwa.googlegroups.com>    William Webb wrote: N > On 9 Dec 2005 16:16:58 -0800, mcbill20@yahoo.com <mcbill20@yahoo.com> wrote: > >  > > William Webb wrote: R > > > On 9 Dec 2005 12:13:18 -0800, mcbill20@yahoo.com <mcbill20@yahoo.com> wrote:O > > > > Thanks. I'll see if the machine has enough slots to get a second KZPBA. K > > > > Right now I have that, plus the slower NCR one for my CDROM and DLT  > > > > drive. > > > 
 > > > OMG! > > > A > > > You're running a DLT off of an NCR53C810 or whatever it is?  > > > Narrow SCSI? > > >  > > > What KIND of DLT?  > > ' > > It's a TZ87. I also have a DLT4000.  > >  > R > Yeah, but it's kind of like running around with your gear shift stuck in second.K > These drives would be much, much happier with something wider and faster.  > I > In fact, I'm surprised you haven't had problems with loss of streaming.   G Well, if I get the second SCSI card, and can find a really short cable, 2 I guess I could put it on the end after the BA364.   >  > > >  > > > WWWebb > > > F > > > In the mean time I may take the Alpha apart, take one of the newH > > > > drives out of it's box, put it inside in order to install an OS. > % > Think carefully before you do this.  > L > You'll get an unpleasant surprise if you open up an UltraWide brick, which > the 36GB disk probably is. > L > Instead of the 68-pin VHDC connector like the one you'd find in an RZ28-VWO >  or RZ29-VW,  the disk drive will have an Ultra connector (power and SCSI bus E > all rolled into one) and in order to use it, you'll have to find an  > Ultra to 68 pin Q > converter which will run you about $20 for each Ultra drive you wish to unbox..  >  > How do I know this?  > L > I have two of them inside my PW433au (which has more drives mounted insideG > of it than either God or d|i|g|i|t|a|l intended--  requiring tweaking 
 > of not only L > mounting rails but also the number of SCSI connectors on the ribbon cable. >  > WWW (more below) >  > ThenO > > > > I'll try putting it back in the Storageworks box and see if the machine 4 > > > > boots without any internal drives connected. > > > I > > > It's the fact that you have the internal ribbon CABLE on it [making 6 > > > your bus too long].  Not what's connected to it. > > >  > > > If that works I'll grab ! > > > > another card from Island.  > > > + > > > Island's a good place to do business.  > > G > > I wholeheartedly agree. I've had nothing but excellent service with H > > everything I've gotten from Island. Unfortunately, the environment IJ > > work in has very little VMS now so the only orders I place with Island> > > are occasional small items for my machines in my basement. > > K > > BTW, someone had asked in an earlier post about what the console showed I > > for these drives. Last night I took down the machine and tested that.  > > H > > For those unfamiliar with BA364's, they have four Storageworks slotsG > > and each slot has it's SCSI address assigned by a group of four dip I > > switches. The last working configuration I had was an RZ29 in the top J > > slot and a TZ87 below it. Unfortunately, the TZ87 takes up three slots* > > so I had to pull drives when using it. > > I > > When I had the RZ29 in the top slot (SCSI ID 6), it shoed up fine and G > > also worked with VMS. When I added one of the new drives to a lower K > > slot (SCSI ID 2 or 4), it did not even show up when I typed SHOW DEV at J > > the console prompt. However, when I put the new drive in the top slot,I > > it did show up. However, when I booted VMS and attempted to mount the K > > drive, the lights would flas a couple of times and then I would get the  > > "media is offline" error.  > > G > I was thinking that chain position might matter considering the speed M > difference between drives, but we weren't that far along in the discussion.  > F > > When I tried putting both new drives in the top slots, neither one# > > showed up at the console level.  > >  > > Regards, > > Bill > >  > >  >  > One last thing:  > - > Check the SCSI address setting on your HBA.  >  > From Console:  show pk*  > ! > should give you something like:  >  > pka0_disconnect  1 > pka0_fast        1 > pka0_host_id     6 > @ > If you type set pka0_host_id 7, followed by an init, it should- > reset the host id for that controller to 7.   $ Here is the output from the console:   pka0_host_id      7  pka0_mode      ultra pka0_soft_term    off    Thanks.  Bill   ------------------------------  % Date: Sat, 10 Dec 2005 14:10:16 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>8 Subject: Re: HP : Massive strike and protest march today+ Message-ID: <439B3628.36213F03@comcast.net>   
 AEF wrote: >  > David J Dachtera wrote: 
 > > [snip]. > > Never said that, either. Check the record. > ' > David, look. You are not being clear.    I am being abundantly clear.  # > I make points and you respond and > > I make reasonable inferences as to what those responses mean  H That's where you're going wrong. Instead of reading what is written, you "make ... inferences".  	 > and you C > then say you never said that. Well, what the hell are you saying?   B Exactly what I said, Go back, read it again, and again, and again, and... until you get it.   > Please do try to be clear.   Always do exactly that.   - > I made the point that the NYC transit union F > is being unreasonable in its demands. That is my point. And you keepF > saying things in favor of said union. What should I infer from that?   That we disagree.   D > That you think the union is only being fair, but you claim the 33% > raise is not fair   9 Never said that. (...and never said the reverse, either!)   4 >, but that the union is being fair in demading said( > raise? You are contradicting yourself.  & Nope - *YOU* are contradicting myself.  E > DO NOT TELL ME TO REREAD WHAT YOU WROTE. I AM NOT GOING TO DO THAT.   > Then, I cannot help you if you are unwilling to help yourself.   > [snip]E > Please provide some real, non-cryptic, non-dodging answers to these  > questions or I'm outta here!  C All of my "real, non-cryptic, non-dodging answers" are here in this  thread.    Clearly:+ - you are unable to follow the conversation G - you are unwilling to do your own research to help yourself follow the  conversation    So, I guess you're outta here...   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Sat, 10 Dec 2005 14:14:33 -0500 , From: Carl Friedberg <frida.fried@gmail.com>$ Subject: Re: MEMORY RULES FOR ES40-2I Message-ID: <890539d90512101114m6ad72192j97a45a561e0a126f@mail.gmail.com>   8 On 12/5/05, BRANDON, JOHN M <brandon@dalsemi.com> wrote:L > In an ES40 model 2 there are specific rules regarding the installation of=  the= > memory modules.  I have included those rules for reference:  > L > * You can install up to 16 DIMMs or up to 32 DIMMs, depending on the syst= em >   model you purchased.  L Almost all ES40's have 32 DIMM slots. There are 4 MBB's in the machine, som= e J ES40's (I've got one) have MBB"s with only 4 of the 8 MBB's populated with
 DIMM sockets.    > L > * A n options consists of a set of 4 DIMMs.  You must install all 4 DIMMs= .  > L > * Fill sets in numerical order. Populate all 4 slots in Set 0, and then p= opulate  >   Set 1, and so on.  > L > * An "array" is one set for systems that support 16 DIMMs and two sets fo= r " >   systems that support 32 DIMMs. > L > * DIMMs in an array must be the same size and type.  For example, suppose=  youL >   populated Sets 0, 1, 2, and 3.  When you populated Set 4, the DIMMs mus= t beL >   the same size and type as those installed in Set 0.  DIMMs must be the = sameL >   size and type as those installed Set 0.  Similarity Set 5 must be popul= atedL >   with the same size and type of DIMMs as are in Set 1, and son on, as in= dicated 0 >   in the following table. (table not included) >  > L > In our ES40 we seem to have violated the "Fill sets in numerical order.".=   We; > filled numerical sets 0, 1, 2, 4, and 5 - skipping set 3.  > K > Has anyone did the same and what was the outcome?  The system seems to be 5 > running fine and all the installed memory is there.  >   J The ES40 memory configuration is challenging. I have had some installationL issues, but field service has always been able to get things working; and o= nce L working, they continued to work. I've had to remove and reinsert DIMMs up t= o = 10 times before they were recognized during power on testing.   L If you don't populate the way it says on the inside of the cover, you may h= ave L a working configuration, but if you want 4-way interleaving (the fastest me= moryJ access paths) then you must follow the order given. I would say you shouldL do that anyway. On the other hand, with 5 sets of those DIMMs, I don't thin= k L you will be able to get 4-way interleaving, as all the sets have to be the = same, ! I think (not sure on that point).   
 Good luck,   Carl Friedberg >  >  > John "REBOOT" Brandon  > VMS Systems Administrator , > firstname.lastname.spam.me.not@dalsemi.com >    ------------------------------  # Date: Sat, 10 Dec 2005 21:29:23 GMT L From: winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing)) Subject: Re: Running Image From Procedure 6 Message-ID: <00A4E116.32DDD41F@SSRL.SLAC.STANFORD.EDU>  w In article <dnei61$idc$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: 7 >In article <00A4DFDB.975980E3@SSRL.SLAC.STANFORD.EDU>, G >winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing) 	 >writes:   > O >> You want to make SYS$INPUT point to the terminal explicitly.  TT: is handily J >> supplied as by the system to be the name of the terminal in the current >> session.  >>   >> $ ! THIS IS MENU.COM  >> $ DEFINE SYS$INPUT TT: % >> $ RUN OPT:[PROG.PASCAL.DIV]ALC.EXE  > 6 >I usually use DEFINE/USER_MODE SYS$INPUT SYS$COMMAND. > J >The /USER_MODE means that it is automatically deassigned after the image F >is run.  (An, of course, it is in USER mode and not SUPERVISOR mode.)  O And indeed, that's better for not having unwanted knock-on effects.  (I drafted J the post with "/USER" and an explanation, and then realized I was about toL do a disquisition on logical names, so I thought I'd just give him somethingD that worked and let him ask the next question when he can absorb it.  C >What are the thoughts here?  Is SYS$COMMAND to be preferred to TT?  > J >With some Fortran programs, I once found that I had to define SYS$OUTPUT E >to SYS$COMMAND as well in order to get them to work the same from a   >procedure as interactively.   Never ran into that one.   -- Alan    ------------------------------   End of INFO-VAX 2005.688 ************************                                                                                                                                                                                        ">	  <tr>	    <td><pre class="dcl">$ PRODUCT INSTALL freetype&nbsp;&nbsp;<em>(default)</em>&nbsp;&nbsp;or ...$ PRODUCT INSTALL freetype /DESTINATION=<var>dev:[dir]</var></pre>	    </td>	  </tr>	</table></li>      <li>Finally, run the DCL procedure <code>STARTUP.COM</code> to define the necessary logicals.	<table summary="" class="dcl">	  <tr>	    <td><pre class="dcl">(You might want to add the relevant line to your <code>SYSTARTUP_VMS.COM</code> file.)<br>$ @SYS$COMMON:[FREETYPE]STARTUP&nbsp;&nbsp;<em>(default)</em>or ...$ @<var>dev:[dir</var>.FREETYPE]STARTUP</pre>	    </td>	  </tr>	</table></li>    </ol>    <p><a href="#pgTop">Back to Top</a></p>                       <hr><h3 id="libimaging">LibImaging V1.1.4</h3>    <p>LibImaging is a image processing library which supports many file formats, and provides powerful image processing and graphics capabilities and used by several software packages, including Python.</p>    <p>By default, the installation procedure installs this        library package in the <code>SYS$COMMON:[LIBIMAGING]</code> directory.      To install it in another directory, <var>dev:[dir]</var>, use the <code>/DESTINATION</code>      parameter of the <code>PRODUCT</code> command.      In this case, the library package will be installed in the       <code><var>dev:[dir</var>.LIBIMAGING]</code> directory.</p>     <h4>Installation</h4>    <ol class="dotnum">      <li>Make the directory which holds the ZIP file your default directory</li>      <li>Extract the PCSI kit from the ZIP archive.	<table summary="" class="dcl">	  <tr>	    <td><pre class="dcl">$ UNZIP "-V" LIBIMAGING-V0101-4-1.ZIP</pre>	    </td>	  </tr>	</table></li>      <li>Install the library package to your chosen destination.	<table summary="" class="dcl">	  <tr>	    <td><pre class="dcl">$ PRODUCT INSTALL libimaging&nbsp;&nbsp;<em>(default)</em>&nbsp;&nbsp;or ...$ PRODUCT INSTALL libimaging /DESTINATION=<var>dev:[dir]</var></pre>	    </td>	  </tr>	</table></li>      <li>Finally, run the DCL procedure <code>STARTUP.COM</code> to define the necessary logicals.	<table summary="" class="dcl">	  <tr>	    <td><pre class="dcl">(You might want to add the relevant line to your <code>SYSTARTUP_VMS.COM</code> file.)<br>$ @SYS$COMMON:[LIBIMAGING]STARTUP&nbsp;&nbsp;<em>(default)</em>or ...$ @<var>dev:[dir</var>.LIBIMAGING]STARTUP</pre>	    </td>	  </tr>	</table></li>    </ol>    <p><a href="#pgTop">Back to Top</a></p>                       <hr><h3 id="libgd">LibGD V2.0.33</h3>    <p>LibGD is an ANSI C library for the dynamic creation of images. GD creates PNG, JPEG and GIF images, among other formats.It is used by several software packages, including Python.</p>    <p>By default, the installation procedure installs this        library package in the <code>SYS$COMMON:[LIBGD]</code> directory.      To install it in another directory, <var>dev:[dir]</var>, use the <code>/DESTINATION</code>      parameter of the <code>PRODUCT</code> command.      In this case, the library package will be installed in the       <code><var>dev:[dir</var>.LIBGD]</code> directory.</p>     <h4>Installation</h4>    <ol class="dotnum">      <li>Make the directory which holds the ZIP file your default directory</li>      <li>Extract the PCSI kit from the ZIP archive.	<table summary="" class="dcl">	  <tr>	    <td><pre class="dcl">$ UNZIP "-V" LIBGD-V0200-33-1.ZIP</pre>	    </td>	  </tr>	</table></li>      <li>Install the library package to your chosen destination.	<table summary="" class="dcl">	  <tr>	    <td><pre class="dcl">$ PRODUCT INSTALL libgd&nbsp;&nbsp;<em>(default)</em>&nb