1 INFO-VAX	Sun, 29 Oct 2006	Volume 2006 : Issue 594       Contents:! Re: Another Vax/Alpha/VMS triumph ! Re: Another Vax/Alpha/VMS triumph ! Re: Another Vax/Alpha/VMS triumph ! Re: Another Vax/Alpha/VMS triumph ( Re: execlet layout (segments) on Itanium# Re: HP eyes top VMS people for cuts * Re: Java Applet pulled from VMS Web Server* Re: Java Applet pulled from VMS Web Server* Re: Java Applet pulled from VMS Web Server* Re: Java Applet pulled from VMS Web Server Re: Mylex controller update  Re: Mylex controller update  Re: Mylex controller update  Re: Mylex controller update  Re: Novice's questions Re: Novice's questions Re: Novice's questions Re: Novice's questions Re: Novice's questionsG Re: OT: Babylon-5 (was Heads up: La Fiorina's book coming out nextweek) " Re: OT: R/C Plane with Video Servo Scary Movie 5: The Vaxorcist !1 Re: simple improvements to disk write performance 1 Re: simple improvements to disk write performance  Re: Spit Brook location  Re: Spit Brook location  Re: Spit Brook location  Re: Spit Brook location  Re: VMS installation crash Re: VMS installation crash Re: VMS installation crash VMS Mozilla (CSWB) support ?  F ----------------------------------------------------------------------    Date: 28 Oct 2006 15:43:12 -0500% From: frey@encompasserve.org (Sharon) * Subject: Re: Another Vax/Alpha/VMS triumph3 Message-ID: <6hTVbtfqdfw3@eisner.encompasserve.org>   h In article <dc565$4542a167$cef8887a$22779@TEKSAVVY.COM>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > Sharon wrote: M >> Cobol/VMS product in favor of the Windoze version, so even though this is  L >> really a great thing, they might frown on me publicising it.  Politics... > G > Well Sharon, you shouldn't be bragging about this... you did mention  B > your systems were down for a whopping 4 minutes after all... :-) > F > I take it that this was a staggered downtime where only part of the J > folks were offline for 4 minutes at any point in time followed by other + > staff being down for 4 minutes later on ?   E 	Um, nope, actually it was TOTAL downtime to the entire group of 911  K dispatchers.  The dispatching system is what ties all the other components  O together; phones, radios, etc. like a hub.  Although it takes advantage of VMS  N clustering to provide quick failover, there's no way to do a phased switchout  of the hardware. 	Ain't it great?  :-)   	  - Sharon " "Gravity...  is a harsh mistress!"   ------------------------------    Date: 28 Oct 2006 15:52:36 -0500% From: frey@encompasserve.org (Sharon) * Subject: Re: Another Vax/Alpha/VMS triumph3 Message-ID: <386yK7+gJlOS@eisner.encompasserve.org>   g In article <ehv0mo$m8t$1@news-02.connect.com.au>, "Richard Maher" <maher_rj@hotspamnotmail.com> writes: K > Don't worry! They've been trying for over 10 years and have still failed. L > Your site appears to have a lot more stringent restrictions than most, butN > I've worked at several where the original VMS/COBOL-busting new systems haveM > themselves already been replaced. And the VMS/COBOL/MACRO systems just keep J > rockin' on! They have also cut the staff and support costs back on theseJ > systems to such a level that it will never again make financial sense to > remove them.  H 	Yep, actually we're in development (and first customer rollout) of our N second "generation" of Windows dispatching product.  I have to admit that I'm L as much of a snob for my product as they are against my product.  It's VERY P impolitic to point out that it's taken 15 years and two product lines for their M products to achieve the functionality and reliability of our Cobol/Macro/VMS   product.  M > No, what was really sad was being sneered at by Digital/Compaq/HP employees E > in our own house! When they disappeared all the Macro examples from I > Alpha/VMS and spat on us when we weren't using C. All because they were N > ashamed of where they'd come from, and manifested that shame in a hatred andG > loathing of all others who had stuck to their values. Sleep peacfully   . 	Oh, you do have me there.  That REALLY hurts!  L > What you need to do is front-end the reliability, security and performanceM > VMS COBOL with the "user interface de jour". Don't be as bitter and twisted M > as most of the people here! Pluralism is good! We need to co-exits, survive D > and thrive in heterogeneous environments. .NET or Java web browserM > interfaces? No problem! Two-Phase Commit with your SQL Server databases? No 
 > Problem!  F 	Ha!  Actually we have!  We have one amazing Windows programmer who's L been tasked with designing and implementing a client for us.  His first few L generations of product weren't great, but now...  now...  it's as slick and L sexy as the full-blown windows product line.  But better because it has the O reliability of the VMS backend.  And he had the foresight to implement it as a  M scripting language so that anyone can write their own client, moving buttons  @ around, making drop-down menus, implementing drag-and-drop, etc.G 	We do owe it to him because this client has extended the "shelf life"  J of our product.  (After all, it's the mucky-mucks who make the purchasing . decisions, and they LOVE the pointy-clickies.)  	  - Sharon " "Gravity...  is a harsh mistress!"   ------------------------------  % Date: Sat, 28 Oct 2006 20:00:05 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> * Subject: Re: Another Vax/Alpha/VMS triumph8 Message-ID: <86bb4$4543ef28$cef8887a$27557@TEKSAVVY.COM>  
 Sharon wrote:   G > 	Um, nope, actually it was TOTAL downtime to the entire group of 911  M > dispatchers.  The dispatching system is what ties all the other components  Q > together; phones, radios, etc. like a hub.  Although it takes advantage of VMS  P > clustering to provide quick failover, there's no way to do a phased switchout  > of the hardware.  I What sort of hardware made it impossible for you to just failover from a   VAX to an Alpha ?   I Not meant as a criticism, just trying to understand various scenarios of  H hardware/telecom/OS gear around a computer that allow or disallow rapid 	 failover.   I There is a lot more to fault tolerance than just the OS and applications  G unless your application does no IO with the outside world. I think you  A could/should make a fascinating presentation at DECUS user group  F meetings. And if that system (and you!) become famous because it is a D showcase for reliability and smart management/planning, your bosses 8 might not be so interested in replacing it with Windows.   ------------------------------  % Date: Sat, 28 Oct 2006 20:03:25 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> * Subject: Re: Another Vax/Alpha/VMS triumph8 Message-ID: <53ec8$4543eff0$cef8887a$27735@TEKSAVVY.COM>  
 Sharon wrote: H > 	Ha!  Actually we have!  We have one amazing Windows programmer who's ? > been tasked with designing and implementing a client for us.    F Was there ever a consideration for developing an X-windows front end ?   ------------------------------  # Date: Sat, 28 Oct 2006 18:11:40 GMT " From:   VAXman-  @SendSpamHere.ORG1 Subject: Re: execlet layout (segments) on Itanium 0 Message-ID: <00A5DE23.740980A6@SendSpamHere.ORG>  S In article <00A5DD97.1F8B9BFB@SendSpamHere.ORG>, VAXman-  @SendSpamHere.ORG writes:  >  > 0 >I wrote and loaded a simple execlet on Itanium. > I >It has a EXEC$NONPAGED_DATA section with some "markers" in it and in its J >EXEC$NONPAGED_CODE section there is a single routine which simply returns	 >success.  > H >The LDRIMG block no longer maintains pointers to these sections.  It isG >now in a vector pointed to by LDRIMG$L_SEGCOUNT and LDRIMG$L_SEGMENTS.  > H >This particular image has 7 segments.  I'm trying to decode these but I >am lost in the $ELFDEF. > ! >Here are some of these segments:  > ' >FFFFFFFF.86D28130    60000001.00000002 ' >FFFFFFFF.86D28138    00400005.00000048 2 >FFFFFFFF.86D28140    FFFFFFFF.8007FF00  LEI+100006 >FFFFFFFF.86D28148    00000000.00000040 <-- lenght of H >FFFFFFFF.86D28150    00000000.00010000 EXEC$NONPAGED_CODE relative base( >FFFFFFFF.86D28158    00000000.00010040 ' >FFFFFFFF.86D28160    00000000.00000000 ' >FFFFFFFF.86D28168    00000000.00000000 ' >FFFFFFFF.86D28170    00000000.00000000  >  > ' >FFFFFFFF.86D28178    00000001.00000003 ' >FFFFFFFF.86D28180    00400004.00000048 2 >FFFFFFFF.86D28188    FFFFFFFF.8663E600  LEI+120006 >FFFFFFFF.86D28190    00000000.00000030 <-- Length of J >FFFFFFFF.86D28198    00000000.00012000 $LINKER UNWIND$/UNWINFO$ rel. base' >FFFFFFFF.86D281A0    00000000.00012030 ' >FFFFFFFF.86D281A8    00000000.00000000 ' >FFFFFFFF.86D281B0    00000000.00000000 ' >FFFFFFFF.86D281B8    00000000.00000000  > ' >FFFFFFFF.86D281C0    00000001.00000004 ' >FFFFFFFF.86D281C8    00400006.00000048 2 >FFFFFFFF.86D281D0    FFFFFFFF.8663E800  LEI+140006 >FFFFFFFF.86D281D8    00000000.00000010 <-- Length of H >FFFFFFFF.86D281E0    00000000.00014000 EXEC$NONPAGED_DATA relative base' >FFFFFFFF.86D281E8    00000000.00014010 ' >FFFFFFFF.86D281F0    00000000.00000000 ' >FFFFFFFF.86D281F8    00000000.00000000 ' >FFFFFFFF.86D28200    00000000.00000000  > K >I've been able to id these as noted.  I'd like to be able to parse through H >these programatically but I'm not sure about all of the fields in theseG >segment headers/descriptors and their appropriate designation from the  >$ELFDEF file. > K >I think that the value in the first longword is an identifier.  The second L >a flag field?  The third longword is always 00000048 -- some section ident-H >ifier perhaps?  The fourth longword??? more flags???  No idea about theJ >last 3 quadwords.... perhaps just filler based on the type of header that
 >this may be.  > K >Any help/ideas appreciated.  Source listings would be so handy but I can't + >see laying out $3K every release of VMS.     = Nevermind.  I figured it out!  :)  ...and I'm not telling! :P      --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  % Date: Sun, 29 Oct 2006 01:40:14 +0800  From: prep@prep.synonet.com , Subject: Re: HP eyes top VMS people for cuts0 Message-ID: <87slh8gwzl.fsf@k9.prep.synonet.com>   healyzh@aracnet.com writes:   A > This question will seem strange, but does anyone know of a good 9 > equivalent to the versioning filesystem in VMS on Unix?   - There arn't any. Best is Unisucks or AS400...   ? For a very bitter value of `best'. AS400 has the advantage that > there are people all over who know it, and if YOU know it, you will always be in work.    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Sat, 28 Oct 2006 16:51:58 -0400 6 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>3 Subject: Re: Java Applet pulled from VMS Web Server 7 Message-ID: <4543c2ec$0$49203$14726298@news.sunsite.dk>    Richard Maher wrote:? >> The applet can only connect to the server it is loaded from.  > M > Either way I'm happy, as what I wanted to (be able to) achieve was have the K > applet coming from a diffent server than the one hosting the original web < > page. I think we're all agreed that that can still happen?  1 Yes. Java does not care about all the HTML stuff.    Arne  F PS: Have you investigated Java Web Start as an alternative to applet ?   ------------------------------  % Date: Sat, 28 Oct 2006 16:55:47 -0400 6 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>3 Subject: Re: Java Applet pulled from VMS Web Server 7 Message-ID: <4543c3d2$0$49197$14726298@news.sunsite.dk>    Richard Maher wrote:? >> Different servers is a problem. Default applet security will  >> not allow that. > E > I believe this is not true. If the codebase parameter points to the : > different server then it's ok. See ITRC thread for more.  ? Codebase is where the applet is fetched from, so codebase is by   definition not diffreent server.  > >> You need to stuff your class files into a jar file and sign >> it. > E > I do not believe that you need to sign the .JAR file. Are you sure?   5 If you need to go beyond default applet security like 1 make a socket connection to a different server or 6 accessing local files on the client PC's, then you do.  @ >> Then we the user opens the applet, the JVM within the browser= >> will ask if the user wants to give the applet extra privs.  > C > Why does the applet need extra privs? We're still in the sandbox.   2 It is only needed if you need to do something that the sandbox does not allow.   + BTW, sandbox is really a Java 1.0/1.1 term.    Arne   ------------------------------  % Date: Sat, 28 Oct 2006 17:28:54 -0400 ) From: "Neil Rieck" <n.rieck@sympatico.ca> 3 Subject: Re: Java Applet pulled from VMS Web Server ; Message-ID: <4543cb2f$0$7476$9a6e19ea@news.newshosting.com>   ? "Richard Maher" <maher_rj@hotspamnotmail.com> wrote in message  + news:ehopna$g4d$1@news-02.connect.com.au...  > Hi,  > G > Does anyone have an example of the commands involved in creating and  	 > storing & > a small Java Applet on a VMS system? > K > I want to be able to activate the Applet from a page in a Web Broswer and B > link back to the same (or other) VMS server via a TCP/IP socket. > E > Pointers to the "specific" documentation will also be very welcome.  > , > I have this much to go on at the moment: - > " > http://java.sun.com/sfaq/#socket > I > This from some Java Socket discussion page on what the Applet(s) should  > contain: - >  > Creating a client  > = > To talk to a server, open a socket to the machine and port:  > ; > Socket s = new Socket("mastercard.com", 303); // port 303  > 6 > When this returns, you can get input/output streams: > ) > OutputStream out = s.getOutputStream(); * > PrintStream pout = new PrintStream(out);& > pout.println("hi from java client"); > pout.close();  > s.close(); > J > The client's input stream is pulling from the server's output stream and
 > vice versa.  >  > Regards Richard Maher  > H Here is an example of a Java applet (my first) as referenced from a web  page. 8 http://www3.sympatico.ca/n.rieck/docs/RieckCalendar.html9 Do a "View Source" then note the <applet> </applet> tags.   J If you like, I can send you the source code. Just in case no one else has J mentioned it yet, a JAVA applet runs in your browser so you almost always E will compile your JAVA source code (YADA.JAVA) into a file name like  < YADA.CLASS which is then store somewhere on your web server.  L A JAVA servlet can sometimes do more technical things and is usually run by J the web server via some application container like TOMCAT, WEBSPHERE, etc.  ? p.s. Maybe I should just post a link to the applet source code.   
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.! http://www3.sympatico.ca/n.rieck/    ------------------------------  # Date: Sat, 28 Oct 2006 22:05:03 GMT + From: =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= 3 Subject: Re: Java Applet pulled from VMS Web Server 2 Message-ID: <juQ0h.21102$E02.8593@newsb.telia.net>   Neil Rieck wrote :  J > Here is an example of a Java applet (my first) as referenced from a web  > page. : > http://www3.sympatico.ca/n.rieck/docs/RieckCalendar.html; > Do a "View Source" then note the <applet> </applet> tags.   : But this applet does nothing with regard to VMS, does it ?9 I thought the point was to make an applet that "talks" to 9 an VMS box, not to load and run the applet as such, which  seems to be common knowledge.   ' But I might be missing something... :-)   A > p.s. Maybe I should just post a link to the applet source code.    Why not ?  :-)  
 Best Regards, 	 Jan-Erik.      >  > Neil Rieck > Kitchener/Waterloo/Cambridge,  > Ontario, Canada.# > http://www3.sympatico.ca/n.rieck/  >  >    ------------------------------    Date: 28 Oct 2006 11:19:32 -07001 From: nothome@spammers.are.scum (Malcolm Dunnett) $ Subject: Re: Mylex controller update, Message-ID: <xJDxTrRonEFQ@malvm3.mala.bc.ca>  4 In article <ehvql3$l6p$1@registered.motzarella.org>,,        "H Vlems" <hvlems@freenet.de> writes:  K > Whar is dispappointing is that 3 members, 9 GB each give me only 35545088 L > blocks of storage, a little under 18 GB so I one drive! I did not select aM > hot spare drive so either RAID5 is inefficient or I'm still doing something  > wrong here...   J    No, that sounds right. RAID5 requires 1 disk for parity information, soQ three 9gb disks would give you 18gb of user data and 9gb of parity. RAID5 becomes : more space efficient as you add more disks to the raidset.   ------------------------------  % Date: Sat, 28 Oct 2006 14:44:13 -0400 / From: "William Webb" <william.w.webb@gmail.com> $ Subject: Re: Mylex controller updateI Message-ID: <8660a3a10610281144u29fefac3u69c295031ecda87d@mail.gmail.com>   / On 10/28/06, H Vlems <hvlems@freenet.de> wrote:  > 8 > "WWWebb" <William.W.Webb@gmail.com> schreef in bericht? > news:1162045469.973840.164300@k70g2000cwa.googlegroups.com...  > >  > > H Vlems wrote:J > > > Last week I reported problems with Mylex controllers (KZPSC), I have > two, aM > > > single channel (KZPSC-AA) and a three channel (KZPSC-CB). Neither would  > workL > > > in an Alpha Server 1200. As it happens, both controllers had different7 > > > problems but to the Alpha they all appeared dead.  > > > J > > > The -AA has Mylex V3.52 firmware and two firmware chips. I tried the	 > RA200FL K > > > and the DAC960FL utilities to downgrade to DEC firmware version 2.70. G > > > The RA200FL program wouldn't run: program too large for available 	 > memory. H > > > The host PC is a Compaq EP model with 512 MB and I hit F5 when DOS	 > booted. D > > > However DAC960FL did run, but refused to downgrade from V3.52. > > > J > > > The -CB had a jumper block missing and was not recognized by neither > Alpha L > > > nor PC. Since the -AA wasn't going to work anyway, I pulled its jumper > block N > > > and the -CB was suddenly recognized by the Alpha. It ran V2.50 and I wasM > > > able to upgrade the firmware to V2.70. The three RZ1DF drives were seen  > byM > > > the controller and right now it's building a RAID5 set from these three  > 9 GB
 > > > drives. * > > > That is expected to take 90 minutes. > > # > > Congratulations, and good luck.  > > 8 > > It may take considerably longer, from my experience. > > 
 > > WWWebb > >  > N > The first 5% took a little under 5 minutes, extrapolating from that I got 90& > minutes. Eventually it took 1hr55...F > Right now I'm booting VMS 8.2 for the first time since the Mylex wasG > installed and SRM at least detects dra0 as a three member RAID 5 set. K > Whar is dispappointing is that 3 members, 9 GB each give me only 35545088 L > blocks of storage, a little under 18 GB so I one drive! I did not select aM > hot spare drive so either RAID5 is inefficient or I'm still doing something  > wrong here...  >  >  >   9 You're not doing anything wrong and your math is correct.   ? When you do RAID5, defined as distributed data with distributed F parity, the amount of space on the RAIDset is equal to the total spaceE on the volumes less the space of one volume.  You can lose one volume E and replace it with no problems; lose two and you'll have to pull out  the tape backups.   D I've not done it with volumes of dissimilar size so I can't tell youC how it picks which one to not count in the total space; it probably E depends on how the firmware in the particular controller that's doing  the RAIDing was written.  C Here's a site with a pretty good explanation of all levels of RAID, : including those which are not spoken of in polite society: http://www.raid-arrays.net/   = See http://www.raid-arrays.net/raid5 for RAID5 in particular.    HTH, WWWebb   --   Ajilon Consulting  Site resident at Quest Diagnostics = first.x.last@f$edit(contents of previous line,"COMPRESS").com    ------------------------------  % Date: Sat, 28 Oct 2006 17:35:29 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> $ Subject: Re: Mylex controller update: Message-ID: <xsGdnYspd9W-UN7YnZ2dnUVZ_oKdnZ2d@comcast.com>   H Vlems wrote:  8 > "WWWebb" <William.W.Webb@gmail.com> schreef in bericht? > news:1162045469.973840.164300@k70g2000cwa.googlegroups.com...  >  >>H Vlems wrote: >>G >>>Last week I reported problems with Mylex controllers (KZPSC), I have  >  > two, a > J >>>single channel (KZPSC-AA) and a three channel (KZPSC-CB). Neither would >  > work > I >>>in an Alpha Server 1200. As it happens, both controllers had different 4 >>>problems but to the Alpha they all appeared dead. >>> G >>>The -AA has Mylex V3.52 firmware and two firmware chips. I tried the  > 	 > RA200FL  > H >>>and the DAC960FL utilities to downgrade to DEC firmware version 2.70.D >>>The RA200FL program wouldn't run: program too large for available > 	 > memory.  > E >>>The host PC is a Compaq EP model with 512 MB and I hit F5 when DOS  > 	 > booted.  > A >>>However DAC960FL did run, but refused to downgrade from V3.52.  >>> G >>>The -CB had a jumper block missing and was not recognized by neither  >  > Alpha  > I >>>nor PC. Since the -AA wasn't going to work anyway, I pulled its jumper  >  > block  > K >>>and the -CB was suddenly recognized by the Alpha. It ran V2.50 and I was J >>>able to upgrade the firmware to V2.70. The three RZ1DF drives were seen >  > by > J >>>the controller and right now it's building a RAID5 set from these three >  > 9 GB > 
 >>>drives.' >>>That is expected to take 90 minutes.  >>! >>Congratulations, and good luck.  >>6 >>It may take considerably longer, from my experience. >> >>WWWebb >> >  > N > The first 5% took a little under 5 minutes, extrapolating from that I got 90& > minutes. Eventually it took 1hr55...F > Right now I'm booting VMS 8.2 for the first time since the Mylex wasG > installed and SRM at least detects dra0 as a three member RAID 5 set. K > Whar is dispappointing is that 3 members, 9 GB each give me only 35545088 L > blocks of storage, a little under 18 GB so I one drive! I did not select aM > hot spare drive so either RAID5 is inefficient or I'm still doing something  > wrong here...  >  >   I How many blocks were you expecting?  With a three member RAID 5 set, one  C third of the space is devoted to parity!!  So ~18GB is about right!    ------------------------------    Date: 28 Oct 2006 20:14:25 -0700& From: "Jeff Campbell" <n8wxs@arrl.net>$ Subject: Re: Mylex controller updateA Message-ID: <1162091665.820698.78580@e3g2000cwe.googlegroups.com>    H Vlems wrote:> > "William Webb" <william.w.webb@gmail.com> schreef in berichtE > news:8660a3a10610281144u29fefac3u69c295031ecda87d@mail.gmail.com... 3 > > On 10/28/06, H Vlems <hvlems@freenet.de> wrote:  > > > < > > > "WWWebb" <William.W.Webb@gmail.com> schreef in berichtC > > > news:1162045469.973840.164300@k70g2000cwa.googlegroups.com...  > > > >  > > > > H Vlems wrote: > [snip] > > > byK > > > > > the controller and right now it's building a RAID5 set from these  > three 
 > > > 9 GB > > > > > drives. . > > > > > That is expected to take 90 minutes. > > > > ' > > > > Congratulations, and good luck.  > > > > < > > > > It may take considerably longer, from my experience. > > > >  > > > > WWWebb > > > >  > > > K > > > The first 5% took a little under 5 minutes, extrapolating from that I  > got 90* > > > minutes. Eventually it took 1hr55...J > > > Right now I'm booting VMS 8.2 for the first time since the Mylex wasK > > > installed and SRM at least detects dra0 as a three member RAID 5 set. F > > > Whar is dispappointing is that 3 members, 9 GB each give me only
 > 35545088N > > > blocks of storage, a little under 18 GB so I one drive! I did not select > a G > > > hot spare drive so either RAID5 is inefficient or I'm still doing  > something  > > > wrong here...  > > >  > > >  > > >  > > = > > You're not doing anything wrong and your math is correct.  > > C > > When you do RAID5, defined as distributed data with distributed J > > parity, the amount of space on the RAIDset is equal to the total spaceI > > on the volumes less the space of one volume.  You can lose one volume I > > and replace it with no problems; lose two and you'll have to pull out  > > the tape backups.  > > H > > I've not done it with volumes of dissimilar size so I can't tell youG > > how it picks which one to not count in the total space; it probably I > > depends on how the firmware in the particular controller that's doing  > > the RAIDing was written. > > G > > Here's a site with a pretty good explanation of all levels of RAID, > > > including those which are not spoken of in polite society: > > http://www.raid-arrays.net/  > > A > > See http://www.raid-arrays.net/raid5 for RAID5 in particular.  > >  > > HTH,
 > > WWWebb > > M > Read the page on RAID 5 and yes, I should have remembered what I learned at ' > those DECUS seminars 20 years ago :-( N > Anyway, if I want to optimize storage I'd better break up the RAID5 set into( > a JBOD (Just a Bunch Of Disks), right?  G Another choice would be a stripe set. The 3 drives would appear as a 27  GB (approx.)F logical drive, which I think is what you were expecting with the RAID5 array. Be aware D that the stripe set will be fatally damaged if one of the configured drives fails. Backup is  your friend.  8-)   
 Jeff Campbell  n8wxs@arrl.net   ------------------------------  % Date: Sat, 28 Oct 2006 13:16:13 -0700 4 From: Alan Frisbie <Usenet02_REMOVE@Flying-Disk.com> Subject: Re: Novice's questions % Message-ID: <1162066410.505362@smirk>    Dan Foster wrote: ] > In article <1162056520.429351@smirk>, Alan Frisbie <Usenet02_REMOVE@Flying-Disk.com> wrote:  > ; >>These will show you the Palcode version (1.88-27) but not : >>the Firmware (SRM Console) version (V5.9-1), at least on >>my VMS v8.3 XP1000.   C > Ugh, indeed... I goofed since I had been thinking of a recent and + > separate discussion when I wrote that. :)   ; I know how that goes.   In another thread, I gave the wrong 9 ASCII character for a hex value.   Red face and all that.    Alan   ------------------------------  % Date: Sat, 28 Oct 2006 17:30:03 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net>  Subject: Re: Novice's questions : Message-ID: <L4idnaFN7tJGVt7YnZ2dnUVZ_tydnZ2d@comcast.com>  
 MZN wrote:   > Thanks to all of you!  >  > 1. Questtion resolved. >  > 2. Resolved. I have last.  > E > 3. Speaking more precisely, if I input command (like sh dev) in SRM H > or/and in OVMS, and its output is more then one full screen, how I canH > read all that output?  What means 'serial console'? In hardware sense.   show dev | more    ------------------------------  # Date: Sat, 28 Oct 2006 22:09:52 GMT + From: =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?=  Subject: Re: Novice's questions 2 Message-ID: <QyQ0h.21103$E02.8640@newsb.telia.net>   Richard B. Gilbert skrev:  > MZN wrote: >  >> Thanks to all of you! >> >> 1. Questtion resolved.  >> >> 2. Resolved. I have last. >>F >> 3. Speaking more precisely, if I input command (like sh dev) in SRMI >> or/and in OVMS, and its output is more then one full screen, how I can I >> read all that output?  What means 'serial console'? In hardware sense.  >  > show dev | more   < Nice, I didn't know that "| more" worked from the console...  	 Jan-Erik.    ------------------------------  % Date: Sat, 28 Oct 2006 22:07:40 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net>  Subject: Re: Novice's questions : Message-ID: <O8udnYBjEtRxkdnYnZ2dnUVZ_tOdnZ2d@comcast.com>   Jan-Erik Sderholm wrote:    > Richard B. Gilbert skrev:  > 
 >> MZN wrote:  >> >>> Thanks to all of you!  >>>  >>> 1. Questtion resolved. >>>  >>> 2. Resolved. I have last.  >>> G >>> 3. Speaking more precisely, if I input command (like sh dev) in SRM J >>> or/and in OVMS, and its output is more then one full screen, how I canJ >>> read all that output?  What means 'serial console'? In hardware sense. >> >> >> show dev | more >  > > > Nice, I didn't know that "| more" worked from the console... >  > Jan-Erik.   @ I didn't know either until I peeked over my CE's shoulder. . . .   ------------------------------  % Date: Sat, 28 Oct 2006 23:08:50 -0400 / From: "William Webb" <william.w.webb@gmail.com>  Subject: Re: Novice's questions G Message-ID: <8660a3a10610282008l76168fn55effa8acbf1cf03@mail.gmail.com>   ? On 10/28/06, Richard B. Gilbert <rgilbert88@comcast.net> wrote:  > Jan-Erik S=F6derholm wrote:  >  > > Richard B. Gilbert skrev:  > >  > >> MZN wrote:  > >> > >>> Thanks to all of you!  > >>>  > >>> 1. Questtion resolved. > >>>  > >>> 2. Resolved. I have last.  > >>> I > >>> 3. Speaking more precisely, if I input command (like sh dev) in SRM L > >>> or/and in OVMS, and its output is more then one full screen, how I ca= n L > >>> read all that output?  What means 'serial console'? In hardware sense= .  > >> > >> > >> show dev | more > >  > > @ > > Nice, I didn't know that "| more" worked from the console... > > 
 > > Jan-Erik.  > B > I didn't know either until I peeked over my CE's shoulder. . . . >    Dare I say it?  F The use of the "pipe more" command that way is a UNIXism, and, believe& it or not, it works under MS-DOS, too.  I And technically there shouldn't be a space between the pipe and the more-   
 it's |more   WWWebb --=20  Ajilon Consulting  Site resident at Quest Diagnostics = first.x.last@f$edit(contents of previous line,"COMPRESS").com    ------------------------------  % Date: Sun, 29 Oct 2006 11:16:13 +1100 ( From: Phaeton <phaeton@internode.on.net>P Subject: Re: OT: Babylon-5 (was Heads up: La Fiorina's book coming out nextweek)0 Message-ID: <12k7sm0e82p924e@corp.supernews.com>   Neil Rieck wrote: 6 > "Neil Rieck" <n.rieck@sympatico.ca> wrote in message7 > news:45279b7c$0$5934$9a6e19ea@news.newshosting.com...  >  > [...snip...] > K > I just purchased a 5 year DVD kit of Babylon 5 (the complete seasons) for  > US$99 from this link:  > www.savingcity.net/specials   > 	Has anyone seen the B5 offshoot, "Crusade" ( 13 parts ) ? Any; 	opinions ?  ( Also, what is the consensus about the "LEXX" : 	sci-fi series ? It is a Canadian-German made, comedy... )  9 	And watch out for the coming ( funny ) UK sci-fi parody, 4 	"Starhyke" :-)  With Claudia Christian ( B5 fame. )  C                                                     Cheers,   Csaba   E --------------------------------------------------------------------- D    CSABA I. HARANGOZO    |d|i|g|i|t|a|l|    phaeton@internode.on.netE --------------------------------------------------------------------- <     EARTH::AUSTRALIA:[SYDNEY]HARANGOZO.CSABA;1, delete? [N]:     Robert E. Lee's Truce : I    Judgement comes from experience; experience comes from poor judgement.    ------------------------------  % Date: Sat, 28 Oct 2006 14:04:35 -0500 . From: Alphaman <alphaman-nix-spam@alphant.com>+ Subject: Re: OT: R/C Plane with Video Servo 7 Message-ID: <6404b$4543a9c0$186088ed$10968@KNOLOGY.NET>    Neil Rieck wrote:  > Golf club Royal Bromont O > A Canadian RC airplane enthusiast combined a model airplane, virtual reality  M > goggles and a wireless camera. It works like this: A fairly standard model  D > airplane is controlled normally with a wireless remote control. A K > pan-and-tilt camera is mounted at the airplane's center of gravity, also  K > controlled wirelessly. Video from the camera is viewable through virtual  L > reality goggles, which have a gyroscope attached to sense the movement of L > the goggles and control the camera accordingly. When the wearer moves his H > head, the camera also moves. This is a breathtaking, goggle-eye video. > C > http://video.google.fr/videoplay?docid=-2237947353453839215&hl=fr   
 Very cool!  G Have you seen the DraganFlyer?  (No typo, that's an A in there.)  RC 4  I bladed helicopter with gyro stabilization built in. No tail rotor, but a   built-in wifi camera!   3 http://www.rctoys.com/Merchant2/videos/DF-VTI_9.mov   3 http://www.rctoys.com/Merchant2/videos/DF-VTI_1.mov    And more videos and info here:  R http://www.rctoys.com/rc-toys-and-parts/DF-VTI/RC-HELICOPTERS-DRAGANFLYER-VTI.html   Aaron  --I "Believe nothing, no matter where you read it, or who said it, no matter  F if I have said it, unless it agrees with your own reason and your own   common sense." (Buddha, ~500BCE)   ------------------------------  % Date: Sun, 29 Oct 2006 01:36:08 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> ' Subject: Scary Movie 5: The Vaxorcist ! 8 Message-ID: <72a18$45443dec$cef8887a$13923@TEKSAVVY.COM>  @ It's halloween, time for scary movies, ghosts,  gobblins etc....     			THE VAXORCIST 			-------------  3               A rough draft of a video presentation ,                       by Christopher Russell:         Operations Manager, Dept of Mechanical Engineering,                       University of Maryland  I -------------------------------------------------------------------------   E (SCENE: Inside of a VAX computer room.  CREDITS ROLL as the SYSMGR is H sitting in front of the console terminal, typing.  He pauses, picks up aJ small magnetic tape, walks over to a tape drive, mounts it, and returns to' the console where he continues typing.)   F (There is a knock at the door.  SYSMGR walks to the door and opens it, revealing USER.)  + USER:  Any idea when the system will be up?   G SYSMGR:  Well, I just installed version 5.0 of VMS, so I'm going to run I some diagnostics on it overnight to make sure it works alright.  Assuming E everything goes alright, the system should be up first thing tomorrow  morning.   USER:  Great.  Thanks.  (Exits)   4 (SYSMGR closes the door and returns to the console.)  J ROD SERLING-LIKE VOICE:  This is John Smith, University of Maryland SystemI Manager.  In an effort to make his system the best it can be, he has just I installed VMS Version 5.0 onto his VAX.  But little does he know that the I Version 5 documentation kit from Digital includes a one-way ticket to ...  the VMS TWILIGHT ZONE!   (ominous music - fade out)  J (Fade in.  The SYSMGR scans the console for a moment, then turns, picks upK his coat and walks to the door.  He stops at the door for a moment, looking D back at the big machine.  Finally, he turns out the light and exits, closing the door behind him.)   H (Cut to the Console Terminal.  We read the following as it is printed on the console terminal:)   VMS V5.0 DIAGNOSTICS --   ! DIAGNOSTICS - PHASE 1 STARTING...   , DIAGNOSTICS - PHASE 1 FINISHED SUCCESSFULLY.  ! DIAGNOSTICS - PHASE 2 STARTING...     TESTING MICROCODE ... SUCCESSFUL   TESTING DECNET ...  SUCCESSFUL  1 TESTING LICENSE MANAGEMENT UTILITY ... SUCCESSFUL   & TESTING SYSTEM SERVICES ... SUCCESSFUL  F TESTING HIGHLY EXPERIMENTAL AND COMPLETELY UNDOCUMENTED AI ROUTINE ...  I (Cut to view of the Tape in the Tape drive.  The tape spins for a moment,  and suddenly stops.)  F (Cut to view of the Machine Room.  A fog has begun drifting across theG floor, and the hardware is slowly being backlit by a pulsing red light. H A peal of weird laughter cuts through the silence.  A variety of bizarreD things occur:  A VT100 monitor sitting on a table slowly rotates 360F degrees; the tape drive opens and tape begins spewing out of it; slimeH begins pouring out of a disk drive; the line printer begins form-feedingG like mad.  These continue for several minutes, or for as long as we can  keep them up.  FADE OUT)  J (SCENE: Hallway outside of the computer room.  SYSMGR walks up to the door and is met by USER.)  " USER:  System going to be up soon?  G SYSMGR:  (as he speaks, he tries to open the Machine room door, but the G door is apparently stuck.) The diagnostics should be done by now, so we I should be up in about 15 minutes... (he succeeds in opening the door, but F is confronted by floor to ceiling magnetic tape.  Tangled at about eyeJ level is an empty tape reel. SYSMGR takes the reel and looks at it.  CLOSEB UP of the reel so we can read the label, which reads: VAX/VMS V5.09 DIAGNOSTIC KIT.) (to USER) ...give or take a few days....   J (SCENE:  View of TSR (Telephone Support Rep) from behind as she is sittingF in a cubicle, a terminal in front of her.  Beside her on the wall is aH poster which reads "Digital Has It Now - But You Can't Have It".  We canJ see the terminal, but we should not be able to read what is on it.  She is wearing a headset.)   E TSR:  Colorado Customer Support.  What is your access number, please?    SYSMGR VOICE: 31576    TSR:  And your name?   SYSMGR VOICE:  John Smith.  J (Cut to SYSMGR standing beside his console.  He his holding a phone to hisH head with his right hand, and holding a printout in his left which he is& perusing while he talks on the phone.)  4 TSR VOICE:  And what operating system are you using?   SYSMGR:  VMS version 5.   H TSR VOICE:  And is this a problem with the operating system or a layered product?  F (As the SYSMGR looks up from the printout, his eyes suddenly widen andF he drops the printout and ducks.  At that second, a disk platter fliesF through the air where his head just was.  Slowly, SYSMGR stands up andI looks to where the disk went.  PAN BACK to reveal a stack of boxes with a - disk embedded in one of them at neck height.)   M SYSMGR:  (into the phone) Operating System.  Definitely the Operating System.   & (Cut back to TSR sitting at her desk.)  + TSR:  Can you describe the problem, please?   0 (SYSMGR voice can now only be heard as mumbling)  J TSR:  Yes... Tape drive spewing tape into the air... yes...  Line printersF printing backwards... yes... miscellaneous hardware flying through theK air... uh huh...  disk drives melting... yeah... strange voices coming from K the CPU board... I see... yes.  Is that all?  (pause as she finishes typing H at the terminal)  Well, I'm afraid that that team is busy at the moment,  can I have them get back to you?  E (CUT TO SCENE: MANAGER sitting behind a large desk in a plush office. < DEVELOPER is pacing in front of him, hands behind his back.)  # (SUBTITLE: Meanwhile at Maynard...)   / MANAGER:  So tell me!  What the hell happened?!   J DEVELOPER:  (turning to face MANAGER)  It's a glitch, a fluke.  A one in a? billion chance.  And it's not Development's fault.  Not really.   ! MANAGER:  Then who's fault is it?   F DEVELOPER:  We traced it back to the Software Distribution Center.  ItI seems that there was a mixup and some of the code for the experimental AI J routine was copied onto the distribution from the wrong optical disk.  (He7 removes a CD from his jacket)  This one, to be precise.    MANAGER:  And what's that?  A DEVELOPER:  (reading the label)  "Ozzy Osbourne's Greatest Hits". G Normally, it wouldn't have made any difference, as the AI routine isn't J used yet.  But when they began running diagnostics, it hit the routine and3 the computer just sort of became a thing possessed.   < MANAGER:  Wonderful.  Were any other distributions affected?  2 DEVELOPER:  No, just the University of Maryland's.  E MANAGER:  Well, that's a relief.  We've got to get them taken care of F before anyone finds out.  Can you imagine what Digital Review would do if they heard about this?   A DEVELOPER:  We could always blame it on the Chaos Computer Group.   J MANAGER:  No, we've already used that one.  This calls for drastic action.D (MANAGER picks up the phone and begins flipping through the rolodex)  & DEVELOPER:  Who are you going to send?  I (CUT to the Rolodex so that we can read the cards.  The first card reads:   & 	SYSTEM PROBLEMS - Ron Jankowski, x474   he flips to the next card:  ) 	BAD SYSTEM PROBLEMS - Bob Candless, x937    he flips to the next card:  3 	REALLY BAD SYSTEM PROBLEMS - Michelle French, x365    he flips to the next card   3 	OUTRAGEOUSLY BAD SYSTEM PROBLEMS - Mike West, x887   < he flips to the next card and taps the card with forefinger:  > 	SYSTEM %%%%ED UP BEYOND ALL RECOGNITION - The VAXorcist, x666    @ (CUT to Machine Room.  SYSMGR is standing by the console holdingJ an RA60 disk cover and using it as a shield to defend himself from variousE pieces of hardware which are flying at him from off-camera.  There is H a knock at the door.  Slowly, SYSMGR makes his way to the door and opensD it.  Standing there, backlit amidst outrageous amounts of fog is theG VAXORCIST, wearing a trench coat and fedora, and carrying a briefcase.)   H VAXORCIST:  (in a hushed voice)  DEC sent me.  I hear you're having some	 problems.   F (CUT to SYSMGR OFFICE, a small but pleasant office with posters on theG walls and clutter on the desk.  As the VAXORCIST enters, he removes his J coat and hat, revealing a very techie outfit beneath.  He is wearing a DEC badge.)   I SYSMGR:  (Frantic)  Problems?  Problems?!?  You could say I'm having some J problems.  4.6 was fine.  4.7 was fine.  I install 5.0 and all Hell breaks< loose.  The damn thing ate two of my operators this morning!  C VAXORCIST:  Calm down, everything will be alright.  I've dealt with  situations like this before.   SYSMGR:  You have?  E VAXORCIST:  Four years ago at an installation in Oregon, a programmer F renamed his Star Trek program to VMB.EXE and copied it into the systemE directory.  When the system was rebooted the next day it phasored the J entire accounting department claiming that they were Klingon spies.  ThereJ was a similar problem in Texas three years ago, and then, of course, thereJ was the IRS fiasco that we're not allowed to talk about.  But don't worry.H These things can be fixed.  Before I can help you, though, I have to askE you a few questions. (The VAXorcist opens his briefcase and removes a K clipboard) Now, according to the report, the strange occurences began after - you installed VMS Version 5, is that correct?    SYSMGR:  Yes, that's correct.   F VAXORCIST:  Now, did you carefully read the Installation Guide for VMS
 Version 5?  ' SYSMGR:  (confused) Installation Guide?   < VAXORCIST:  Yes, it should have come with the Release Notes.  H SYSMGR:  (still confused) Release Notes? (SYSMGR begins rooting about onE his disk, shifting papers around as if he might find them underneath)   J VAXORCIST:  (annoyed) Yes, Release Notes.  They should have come with your documentation upgrade.  E SYSMGR:  (completely confused - looks up from his rooting through the * papers on his desk) Documentation upgrade?  @ VAXORCIST:  (angry) YES!  The Documentation upgrade for your VMS Documentation Set!  J SYSMGR:  Documentation S...?  Oh, you mean the grey binders?  They're overH there. (he points to the wall behind the VAXORCIST.  The VAXORCIST turnsK and we see a closed glass-front bookcase packed with grey binders.  A small I red sign on the front of the bookcase reads: "IN CASE OF EMERGENCY, BREAK  GLASS").  I VAXORCIST:  Right.  This is going to be tougher than I thought.  Let's go > take a look at your system and see just how bad everything is.  I (CUT to the Machine Room.  The room is neat and tidy and there is no sign F that anything is wrong.  The VAXORCIST enters the room with the SYSMGR behind him.)  ( VAXORCIST:  Everything looks okay to me.    SYSMGR:  Maybe it's hibernating.  I VAXORCIST:  Unlikely.  It's probably trying to lure us into a false sense  of security.  E SYSMGR:  Sounds like VMS alright.  (VAXORCIST gives him a dirty look)   K VAXORCIST:  I'm going to have to test it's power.  This could get ugly, you I may want to leave.  (The SYSMGR shakes his head no.  The VAXORCIST brings G hiself up to full height in front of the VAX and points a finger at it) E By the power of DEC, I expel thee from this system! (Clap of thunder)   H (CUT to door to the machine room.  The SYSMGR is pulling a cart on which= sits the VAXORCIST wrapped from head to toe in magnetic tape)     SYSMGR:  Any other bright ideas?  ; VAXORCIST:  Just shut up and get this damn stuff off of me.    (CUT to SYSMGRs office)   H VAXORCIST:  (Writing on the clipboard)  Things look pretty bad.  I think0 we're going to need a full-scale VAXorcism here.  , SYSMGR:  Is there anything I can do to help?  I VAXORCIST:  As a matter of fact, there is.  We've got to incapacitate the H VAX to keep it from causing any more damage until I'm ready to deal withK it.  Now, I've got some software here that will do that, but it's got to be G installed.  (VAXORCIST hands SYSMGR a tape)  With that running, the CPU > will be so bogged down, the VAX won't be able to harm anybody.  K SYSMGR:  (Examining the tape) What is it?  A program to calculate pi to the  last digit?   I VAXORCIST:  Better than that.  It starts up All-in-1 with a 10 user load.   J (CUT to Hall outside of Computer Room.  The VAXORCIST approaches the door.@ As the SYSMGR approaches the door, the VAXORCIST holds him back.  J VAXORCIST:  I appreciate your help, but it won't be safe for you in there.  G SYSMGR:  What?  You're going in there to face that thing alone?  You're  nuts!   < VAXORCIST:  Hey, it's my job.  (VAXORCIST turns to the door)  G SYSMGR:  Wait a minute.  (VAXORCIST stops and turns around)  You better H take this with you.  (SYSMGR removes a very large and very nasty looking" gun from the inside of his jacket)  F VAXORCIST:  (Smiling)  No, I won't need that.  I've got something moreK powerful.  (VAXORCIST holds up a small guide-sized orange binder, opens it, K and shows it to SYSMGR.  CUT to closeup of the book which reads:  "GUIDE TO  VAX/VMS SYSTEM EXORCISM")   K (CUT to view of Machine room door as seen by the VAX.  The VAXORCIST enters I the room and stands in front of the VAX.  CUT to view of the Machine Room ' showing the SYSMGR confronting the VAX)   E VAXORCIST:  By the power of DEC, I command thee, Evil Spirit, to show  thyself.   VAX:  Bugger off.    VAXORCIST:  (Shaken)  What?   I VAX:  I said Bugger off!  Now get out of here before I core-dump all over  you!  H VAXORCIST:  (Recovered)  Threaten me not, oh Evil one!  For I speak with5 the power of DEC, and I command thee to show thyself!   H (A rumble is heard and again the VAX becomes backlit by red lights and aH fog begins to roll across the floor.  The VAX cabinet doors slowly creakJ open to reveal two small red lights in the dark cabinet which appear to be the creature's eyes)  G VAX:  There.  Happy?  Now get out of here before I drop a tape drive on  your private parts.   J VAXORCIST:  (Opening the orange binder, he begins intoning SHUTDOWN.COM in# gregorian chant.  The VAX screams.)   J VAX:  Stop that!  Stop that!  You, you DOS LOVER!  Your mother manages RSX systems in Hell!  4 (The VAXORCIST continues and the VAX screams again.)  I VAX:  Stop it!  (a large wad of computer tape is thrown at the VAXORCIST, 8 apparently from the VAX).  Eat oxide, bit-bucket breath!  8 (The VAXORCIST continues and the VAX screams once more.)   VAX:  Mount me!  Mount me!  F VAXORCIST:  (finishing the intonation) And now, by the power of DEC, II banish thee back to the null-space from which you came!  (The VAX screams ! and the scream fades to silence.)   D (CUT to the doorway of the Machine room, which now stands open.  The< VAXORCIST is once again wearing his trench coat and fedora.)   SYSMGR:  So it's over?  / VAXORCIST: (Putting his hat on) Yes, it's over.   K SYSMGR:  (Shaking the VAXORCISTs hand) Thank God.  Listen, thanks a lot.  I / don't know what we would have done without you.   G VAXORCIST:  Hey, it's the least we could do.  The Software Distribution G Center should be sending you a patch tape in a week or two to patch out G that AI routine and prevent this from happening again.  Sign here.  (he I hands SYSMGR the clipboard, SYSMGR signs at the bottom and hands it back) % Have a good one.  (VAXORCIST leaves).   9 (SYSMGR enters the machine room.  Camera follows him in.)   C SYSMGR:  (Calling to someone off-camera)  Okay, you guys, let's get F rolling.  Get those backup tapes out.  We've got a clean system again!J (cheers are heard from off-camera.  The SYSMGR leaves the picture, leavingJ only the VAX with it's cabinet doors still open in the picture.  Slow zoomF in to the LSI unit.  Slowly, the LSI unit begins to emit a pulsing red glow)    (Fade to black.  CREDITS ROLL)K --------------------------------------------------------------------------- I Copyright (C) 1991 by Christopher Russell (crussell@eng.umd.edu).  Please F feel free to copy this and pass it around if it amuses you, as long as this notice is left intact.   K Any similarity between characters appearing in this script and any persons, I creatures, or entities living, dead, or otherwise is purely coincidental.   D I am no longer an employee of the University of Maryland, so I'm notG particularly bothered if you think that they are responsible for any of ) this.  Unless it's funny, then it's mine.   E Thanks to my friends and colleagues at the University of Maryland and E elsewhere for their help and encouragement in the developement of the  script and the video.    ------------------------------  % Date: Sat, 28 Oct 2006 14:11:12 -0500 % From: Dan Foster <usenet@evilphb.org> : Subject: Re: simple improvements to disk write performance5 Message-ID: <slrnek7aqg.5bi.usenet@zappy.catbert.org>    In article <rdeininger-2810060837520001@dialup-4.233.173.215.dial1.manchester1.level3.net>, Robert Deininger <rdeininger@mindspringdot.com> wrote: >>H >>Well, actually, it does make certain features mandatory which provides< >>some performance boost such as Next Command Queuing (NCQ). > 5 > Unfortunately, even required features are optional.   H Heh, nice. Unfortunate they don't use IETF standards documents where theG distinction between SHOULD and MUST is clear. ;) But, ah, well, such is A reality for the drive manufacturers in that part of the industry.   D And, yes, quite familiar with the idea that actual implementation ofF standards can veer sometimes quite dramatically from how it should be.  J >>My impression of the NCQ implementation is that it is a weaker cousin ofI >>SCSI's Tagged Command Queuing (TCQ), but certainly better than nothing.  >>C >>I can only speculate this was an intentional move in order to not ; >>undercut the more expensive SCSI drive sales for servers.  > L > I doubt it.  Features that are hard to implement correctly will get shoved0 > aside if it saves a few weeks on the schedule.  E I don't have any actual inside knowledge, so any comments I make here   are pure speculation, obviously.  E With that said, it seems strange to imagine they would spend the time H and effort to develop and implement NCQ to shave off time-to-market whenE they already had well understood and supported protocols such as TCQ.   K > The financial models for these products usually assume that any sales you K > miss at the beginning of the product's lifetime will NEVER be recovered.    5 Yeah, but there's also the support cost to factor in.   E Make one that results in a lot of eventual expensive returns prior to B end of the warranty period as well as a damaging hit to brand nameG reputation and future sales; then one has just killed a lot of benefits / of bringing out the product in the first place.   G > SCSI disks are fading away in any case.  There's not much more in the H > pipeline.  FibreChannel and SAS disks will replace SCSI in the market.  D For the unaware following this, SAS is fundamentally serial-attachedG SCSI versus traditional parallel-attached SCSI, with a number of modern 
 enhancements.   H I've certainly seen SAS start to appear in some of our newest purchases.  F A nice selling point for SAS and SATA is that they are interchangeableF as a form of investment protection if a system has a well designed SAS
 backplane.  F We didn't get it for THAT particular reason, but it was interesting toE see how they designed the connector types for both with this in mind.   G I'm personally used to serial-attached disk storage, as I've used IBM's H own proprietary serial attached disks for about 10 years now, so nothingF particularly new to me. Obviously, also have familiarity with FC disksC given their role in the enterprise. Both are nice stuff in general.    -Dan   ------------------------------  % Date: Sun, 29 Oct 2006 01:26:12 +0800  From: prep@prep.synonet.com : Subject: Re: simple improvements to disk write performance0 Message-ID: <87wt6kgxmz.fsf@k9.prep.synonet.com>  ' Dan Foster <usenet@evilphb.org> writes:   ? > Well, actually, it does make certain features mandatory which E > provides some performance boost such as Next Command Queuing (NCQ).   @ > My impression of the NCQ implementation is that it is a weakerE > cousin of SCSI's Tagged Command Queuing (TCQ), but certainly better  > than nothing.   G Yes, but SATA *can't* have commands queued from multiple hosts, yet, so   it does not need to track that.    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Sat, 28 Oct 2006 13:25:57 -0500 . From: Alphaman <alphaman-nix-spam@alphant.com>  Subject: Re: Spit Brook location6 Message-ID: <1da52$4543a0b2$186088ed$7098@KNOLOGY.NET>   Alan Frisbie wrote: > > In particular, on the bottom row, the first character shouldB > be an upper case "W" (hex 57).   Instead, it is hex 17 (Escape).< > Likewise, the seventh character is supposed to be an upper3 > case "D" (hex 44).   Instead, it is hex 46 ("F").   F Errr, Uhm, 0x17 is a 23 (decimal), which is NOT the escape character.  Escape is 27 decimal, or 0x1B.  B Does anyone have a photo of the wall they'd care to share with us * geographically challenged trivia lovers???  I Okay, all this talk about the barcode wall and ZK3 has gotten me feeling  C nostalgic.  Anyone got a copy of ZK???  Oops, just found it on the   hobbyist site...  - http://www.openvmshobbyist.com/downloads.html   C Cool!  Something to do this afternoon while my son plays the PS2...    Aaron  --E "The deepest sin against the human mind is to believe things without  I evidence. Science is simply common sense at its best -- that is, rigidly  F accurate in observation, and merciless to fallacy in logic."  (Thomas 
 Henry Huxley)    ------------------------------  % Date: Sat, 28 Oct 2006 13:12:37 -0700 4 From: Alan Frisbie <Usenet02_REMOVE@Flying-Disk.com>  Subject: Re: Spit Brook location% Message-ID: <1162066194.655334@smirk>    Alphaman wrote:  > Alan Frisbie wrote:  > ? >> In particular, on the bottom row, the first character should C >> be an upper case "W" (hex 57).   Instead, it is hex 17 (Escape). = >> Likewise, the seventh character is supposed to be an upper 4 >> case "D" (hex 44).   Instead, it is hex 46 ("F").  H > Errr, Uhm, 0x17 is a 23 (decimal), which is NOT the escape character.   > Escape is 27 decimal, or 0x1B.  = You are, of course, right.   I don't know what I was thinking = when I wrote that.   I'll blame it on a brain fart.   The hex  values are correct, though.   ; I mentioned the errors to several VMS developers when I was < there in 2005, and one of them gave me the e-mail address of9 the facilities manager.   I sent him a description of the ! problem, but never got an answer.   9 Would anyone care to place a bet on whether or not it has  been fixed yet?   = Would anyone care to place bets on whether or not it is fixed ! before my next trip there in May?   < If it is "fixed", would anyone care to bet on whether or not= they do it correctly?   :-)   All they have to do is swap the  two incorrect bars.    Alan   ------------------------------  % Date: Sun, 29 Oct 2006 01:13:16 +0800  From: prep@prep.synonet.com   Subject: Re: Spit Brook location0 Message-ID: <871wosicsz.fsf@k9.prep.synonet.com>  / "Steve Lionel" <steve.lionel@intel.com> writes:    > prep@prep.synonet.com wrote:  I >> Thanks Steve. The Sheraton is the building with the 7-ish shape to the H >> east? And VMS is in the building with the 2 AC units on the roof, the> >> middle one having 6, and the eastern one 4 in an odd setup? > D > I'm not sure which "7-ish" building you refer to.  The Sheraton isC > the light-roofed building in the lower right of the Google image, C > right next to the highway.  Directly south (towards the bottom of E > the image) of ZK3 is a slim, curved, 7-ish shaped structure that is C > the parking garage for Oracle, whose building can be seen next to E > it.  You have the various Spit Brook buildings identified correctly F > - the eastern one, ZK2, is the one I am in (no HP people are left in > ZK2.)   C Got it now. Part of the problem is over 20 years since I was there, F plus my direction sence was WAY screwed up by first time in the North.F Must be end of winter, no colours, and the trees look pretty sparce asC well. I walked from the sheraton up the slope to ZK, and discovered E that 6-8" of leafe litter is not fun to walk through. Out here, 2" is  about the limit it gets to.    >> The Helipad still there?   3 > Yes, though there is no longer regular use of it.   G Ah, found it now. I thought it was to the west of the building, outside  the end of old RSX offices.   > > I was sent a different aerial view URL which is even better,T > http://local.live.com/default.aspx?v=2&cp=r3k2tq91br5p&style=o&lvl=1&scene=1706810G > In this one, ZK3, with VMS, is at the top, and you can see the "great G > barcode wall" at the ZK1 entrance in the middle.  (It's a popular VMS H > trivia question to ask what this wall reads now, and what it read when > first erected.)   D > The Google photo must have been taken on a weekend, as the parking > lots are TOO empty.   J Say that again, though there are quite a few in the Sheraton's, so weekendG it is. Still seems a lot emptier than it used to be on weekends though.    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Sun, 29 Oct 2006 01:16:48 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>   Subject: Re: Spit Brook location, Message-ID: <4544392E.491405BA@teksavvy.com>  F > > The Google photo must have been taken on a weekend, as the parking > > lots are TOO empty.   E Or it was taken recently, now that the VMS engineering group has been  severely downsized ......    ------------------------------  % Date: Sat, 28 Oct 2006 16:25:47 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> # Subject: Re: VMS installation crash 8 Message-ID: <e3c53$4543bcaf$cef8887a$19571@TEKSAVVY.COM>  D If your NVRAM script contains a "LOOP", it is possible to fix this. G (This, according to the DS10 console management manual, so not sure if  % it applies to your specific machine):   I Pressthe HALT button while the system is powering up. You should then be  G taken to the >>> when you can use EDIT to remove the offending command.   E Note: automatic booting is achioeved though an environment variables:    auto_action  bootdef_dev  boot_osflags  # For instance, in your NVRAM script:    set auto_action restart  set bootdef_dev dqa0 set boot_osflags 0,0  E Then, the SRM will execute your NVRAM scriipt and automatically boot   afterwards.    ------------------------------    Date: 28 Oct 2006 22:58:44 +02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)# Subject: Re: VMS installation crash , Message-ID: <4543e0a4$1@news.langstoeger.at>  e In article <1162054569.999336.184860@m7g2000cwm.googlegroups.com>, "Mike" <mlpoole@gmail.com> writes: H >I got 7-3_2 up and running beautifully and was ready to move it to it'sH >new home on my desk plugged into my router so I could access it through >telnet/Reflection.  > H >I had forgotten that I didn't put a boot command in the NVRAM and I hadH >to make the world's longest serial cable to plug in to tell it to boot. > H >I tried creating an NVRAM script with boot dqa0 -flags 0,0  and now the0 >thing just initializes over and over in a loop.  : See >>> SET BOOTDEFDEV and >>> SET BOOTFLAGS in SRM's help  G >I understand I can use the halt button to break the loop and erase the , >NVRAM script but I am just not having luck.  G >Forgive my PC-entric question, but is there a jumper/battery/switch on ( >the motherboard that would clear NVRAM?  G There is a battery on the MoBo, so although I don't know how NV the RAM F is, I bet it will loose its content if you unplug the battery (if thisI works at all, IIRC the battery could be in a soldered-in DIP chip or so).    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Sat, 28 Oct 2006 17:09:29 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> # Subject: Re: VMS installation crash : Message-ID: <JeudnbpGeeqXWt7YnZ2dnUVZ_rCdnZ2d@comcast.com>   JF Mezei wrote:   G > For what it is worth, my DS10L from the wonderful people at IslandCo  J > came with SRM version 7.2-1 dated June 9 2006 if I remember well. And I D > have not have a problem with crashing VMS during install or while $ > running with both 8.2 and now 8.3. > G > But I did not install VMS from CD, I installed it via an MSCP served   > disk on another node.  > K > I'd have to crash the node again to get the PAL code version though, and  ; > in doing so would lose this message before it is sent :-(    JF,   . $ WRITE SYS$OUTPUT F$GETSYI("CONSOLE_VERSION"). $ WRITE SYS$OUTPUT F$GETSYI("PALCODE_VERSION")   It's all in knowing how. . . .   ------------------------------  % Date: Sat, 28 Oct 2006 20:45:41 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> % Subject: VMS Mozilla (CSWB) support ? 6 Message-ID: <7f32$4543f998$cef8887a$2117@TEKSAVVY.COM>  I What is the status of Mozilla on VMS ? Since it is a proprietary version  G of the open source Mozilla, is VMS engineering responsible for any/all   bugs/suggestions ?  G Is there a clearly defined deliniation of responsabilities between the  G VMS engineers and the Mozilla folks with regards to who is responsible   for what in Mozilla ?    ------------------------------   End of INFO-VAX 2006.594 ************************                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        