1 INFO-VAX	Fri, 07 Sep 2001	Volume 2001 : Issue 497       Contents:0 (resolved) Restoring from retired OpenVMS backup Re: a summing-up so far  Re: a summing-up so far  Big black helicopters  Re: Big black helicopters  Re: Big black helicopters . cancel <eF8yxxLd5jEC@eisner.encompasserve.org>! Re: Carly's email to Compaq staff 2 Re: Converting a stream_lf file to a variable file2 Re: Converting a stream_lf file to a variable file2 Re: Converting a stream_lf file to a variable file Re: cpio ported to OpenVMS?  Re: cpio ported to OpenVMS?  Re: cpio ported to OpenVMS?  Re: cpio ported to OpenVMS?  Re: cpio ported to OpenVMS?  Re: DCL doubts...  Re: DCL doubts... P Re: dir help ---%LIBRAR-F-OPENIN, error opening  SYS$COMMON:[SYSLIB]NCS$LIBRARY. DSN - dead or alive  Re: DSN - dead or alive  Re: DSN - dead or alive  Re: DSN - dead or alive  Re: DSN - dead or alive  Re: DSN - dead or alive  Re: ed/edt corrupting files  Re: ed/edt corrupting files  Re: ed/edt corrupting files  Re: eXcursion Question Re: eXcursion Question  Re: Feeling Better about Itanium  Re: Feeling Better about Itanium  Re: Feeling Better about Itanium	 filescopy  FW: Re: KZCCA-CB Problems  H-P "jumps the shark"  Re: H-P "jumps the shark" + Re: hobbyist license and cpu serial number.  HP-Compaq-Intel Trifecta.  Re: HP-Compaq-Intel Trifecta.  Re: Huh? Re: Huh? Re: I hate Compaq  Re: I hate Compaq  Re: I hate Compaq  Re: I hate Compaq < IDG reporter mentions positive comments made by HP PR person@ Re: IDG reporter mentions positive comments made by HP PR person@ Re: IDG reporter mentions positive comments made by HP PR person@ Re: IDG reporter mentions positive comments made by HP PR personJ Re: IDG reporter mentions some "interesting" comments made by HP PR person+ Re: INQUIRE/NODISPLAY or equivalent in DCL? + Re: INQUIRE/NODISPLAY or equivalent in DCL? C Looking ahead: What happens if the HP-Compaq merger falls through ? G Re: Looking ahead: What happens if the HP-Compaq merger falls through ? G Re: Looking ahead: What happens if the HP-Compaq merger falls through ? G Re: Looking ahead: What happens if the HP-Compaq merger falls through ? . MicroVAX II (KA630) - RXCS,RXDB,TXCS, and TXDB2 Re: MicroVAX II (KA630) - RXCS,RXDB,TXCS, and TXDB2 Re: MicroVAX II (KA630) - RXCS,RXDB,TXCS, and TXDB2 Re: MicroVAX II (KA630) - RXCS,RXDB,TXCS, and TXDB Re: My VMS Wish List (features) < RE: OT: Bush administration drops effort to break up Microso> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft> Re: OT: Bush administration drops effort to break up Microsoft Re: Pagefile questions Re: Pagefile questions Re: Pagefile questions Re: Pagefile questions< Re: Silly names (was: RE: HP to buy Compaq (Globe and Mail)) ss$_personadelpend What is it?" Re: ss$_personadelpend What is it? Re: Status of Alpha + Vax/Vms Systems Administrator in Albany, NY / Re: Vax/Vms Systems Administrator in Albany, NY " VMS 7.2 / CMU-IP6.6.5K FTP problem& Re: VMS 7.2 / CMU-IP6.6.5K FTP problem Re: VMS Cluster help.. Re: VMS Cluster help.." Re: VMS NFS and PC-NFS (Reflexion)5 Re: VMS To Be Squeezed Out Of HP's Strategic Vision ? 5 Re: VMS To Be Squeezed Out Of HP's Strategic Vision ? 5 Re: VMS To Be Squeezed Out Of HP's Strategic Vision ? 5 Re: VMS To Be Squeezed Out Of HP's Strategic Vision ? 5 Re: VMS To Be Squeezed Out Of HP's Strategic Vision ? 5 Re: VMS To Be Squeezed Out Of HP's Strategic Vision ? 5 Re: VMS To Be Squeezed Out Of HP's Strategic Vision ? 5 Re: VMS To Be Squeezed Out Of HP's Strategic Vision ? 5 Re: VMS To Be Squeezed Out Of HP's Strategic Vision ? 5 Re: VMS To Be Squeezed Out Of HP's Strategic Vision ? , Re: Why continue with VMS - new hope, indeed7 Re: Will Mozilla ever run without crashing DECW server? $ Re: WSJ reporting HP will buy Compaq  F ----------------------------------------------------------------------  % Date: Thu, 06 Sep 2001 23:39:00 -0400 - From: Kurt Krieger <kkrieger-xspam@erols.com> 9 Subject: (resolved) Restoring from retired OpenVMS backup ) Message-ID: <3B984153.783FC0B1@erols.com>    Hi, + Thanks to everyone who offered suggestions!   K I was able to obtain access to an OpenVMS Alpha server, and Duncan Brown of C Encompass provided tremendous help to me in networking my PC to the  Alpha - thanks Duncan!   So, case closed.   Kurt   Kurt Krieger wrote:    > Hi, R > I was the sysadmin for an OpenVMS 6.1 system that was retired in 1999. We made aR > full backup of all disks before "discarding" the server. My company now needs toP > resurrect some files from the backup tape, but, of course, we no longer own an > OpenVMS box. > M > I've searched Google and other sites for a company that can restore from an ? > OpenVMS backup tape (4mm, 1GB), but I haven't found anything.  > R > Can anyone provide advice on how I can restore these files? I need all the filesN > in a specific folder path (disk$user4:[eps]) copied to CD-ROM, or saved to aK > website, etc. Are there companies who can do this? Can I "rent" a running R > machine for an hour? Is the format of a standard backup tape compatible with any > other OS?  > 4 > (If replying directly, please remove the "-xspam") >  > Thanks a lot, Kurt   ------------------------------  % Date: Thu, 06 Sep 2001 15:19:37 -0700 < From: "Kenneth H. Fairfield" <Kenneth.H.Fairfield@intel.com>  Subject: Re: a summing-up so far) Message-ID: <3B97F679.CF63A813@intel.com>    Bill Todd wrote:  M > Ken Farmer invited me to write up a point-of-view article for tru64.org for K > those who don't follow the newsgroups.  I sent it to him last Sunday, and ' > you all know what happened on Monday.   = Bill, thanks for posting this letter.  Presented as you have, ? with a minimum of emotion and rhetoric, it carries a great deal  of weight, at least with me.  < Of particular importance, I agree fully that Compaq have not< even begun to address the question of "Why was Alpha killed"> (their assertions of performance or economic viability aside),9 let alone the question of "Why merge with HP".  While the 9 former _could_ easily be explained by the latter, but the ' latter makes no sense whatsoever, IMHO.   ; Sorry that I won't be at this year's CETS.  More sorry that > it may be the last DECUS/Encompass meeting of its kind...I had> planned to attend next year... :-(.  To all my DECUS/Encompass2 friends and acquaintances, if we don't meet again, "Live long and prosper!"       -Ken --6 I don't speak for Intel, Intel doesn't speak for me...   ------------------------------  % Date: Thu, 06 Sep 2001 20:54:00 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>   Subject: Re: a summing-up so far' Message-ID: <3B9828B8.AAA36571@fsi.net>    "Kenneth H. Fairfield" wrote:  >  > Bill Todd wrote: > O > > Ken Farmer invited me to write up a point-of-view article for tru64.org for M > > those who don't follow the newsgroups.  I sent it to him last Sunday, and ) > > you all know what happened on Monday.  > ? > Bill, thanks for posting this letter.  Presented as you have, A > with a minimum of emotion and rhetoric, it carries a great deal  > of weight, at least with me. > > > Of particular importance, I agree fully that Compaq have not> > even begun to address the question of "Why was Alpha killed"@ > (their assertions of performance or economic viability aside),; > let alone the question of "Why merge with HP".  While the ; > former _could_ easily be explained by the latter, but the ) > latter makes no sense whatsoever, IMHO.  > = > Sorry that I won't be at this year's CETS.  More sorry that @ > it may be the last DECUS/Encompass meeting of its kind...I had@ > planned to attend next year... :-(.  To all my DECUS/Encompass4 > friends and acquaintances, if we don't meet again, > "Live long and prosper!"  C I'm sure we'll be here to keep the newsgroup alive and support each & other both technically and personally.  + Raise your glass, VMS'ers - we're the best!    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  $ Date: Thu, 6 Sep 2001 18:28:44 -0500+ From: Phil Mendelsohn <mend0070@tc.umn.edu>  Subject: Big black helicoptersH Message-ID: <Pine.SOL.4.20.0109061819310.29908-100000@garnet.tc.umn.edu>  G Hrm, I knew there was scuttlebutt about DoJ dropping the monopoly suit, G but I only just received word it was the real deal.  So here's my black  helicopter theory:  F Microsoft has been nearing a buyout of the gov't (or bribing the rightE people), which resulted in the lawsuit being dropped.  HP and Compaq, C either tipped off or having their own sources decided to circle the H wagons.  While you're at it, link Microsoft to vote counting in Florida, and show premeditation.    --  + I liked HP, and at one time I liked Compaq, 7 but I liked DEC better than HP and Compaq put together.    ------------------------------  # Date: Fri, 07 Sep 2001 03:20:37 GMT 9 From: politics2000@hotmail.com (politics2000@hotmail.com) " Subject: Re: Big black helicopters: Message-ID: <3b9830fa.325950872@news.jamison1.pa.home.com>  A The only "black helicopter" theory that makes any sense regarding F Feds' suit against Microsoft (and this is a common political practice,D by the way) is that Gates was approached by both the RNC and the DNCE for campaign contributions, to which he politely replied "no thanks". F He was then informed, in well-chosen words, that his company would notD be a target of investigation or subjected to an IRS audit if he wereD to make hefty contributions (read "pay protection money").  When his= answer was still "no thanks" after that threat, Microsoft was B immediately demonized by the Feds (dutifully reported as such by aC lazy and/or biased press) and the DOJ, which is mostly "department" C with only trace elements of "justice", was given the green light to E send in the troops. This is evident by the fact that they based their F anti-trust argument on a very weak browser issue (which also means any4 IRS audit they may have considered was even weaker).  A By definition, a monopoly is when the public is not given another D choice.  Well, we do have other choices ... VMS, UNIX, Linux ... andA any Windows user can go to shareware.com and get Netscape or some E other browser for free.  The Feds know this, of course, and they knew > going into this suit that they'd probably lose.  However, theyA achieved their ultimate goal ... they demonstrated that no one is F going to be immune from their fund-raising shake-down tactics.  I hopeD Bill doesn't cave in and dole out contributions in the next electionE cycle.  DOJ investigations and IRS audits on successful companies who F don't contribute to either or both of these incredibly corrupt parties. has to stop, and now is as good a time as any.   ------------------------------  # Date: Fri, 07 Sep 2001 04:04:17 GMT ' From: ben_myers@charter.net (Ben Myers) " Subject: Re: Big black helicopters0 Message-ID: <3b98473f.59316093@news.charter.net>  D I wish that the computer choices available to the buying public wereC as simple as "VMS, UNIX, Linux".  Fact is Microsoft has most fo the B world by the short hairs because everyone wants to have COMPATIBLED SOFTWARE AND DATA EXCHANGE, and Microsoft Office controls 90% of the@ business software market with proprietary and ever-changing dataE formats to keep competitors from being able to cleanly process Office F data.  An all-Wintel network is much more readily interoperable than aD heterogenous one, taking into account all the various forms for data and file exchange.  C Facts are that the DOJ under the Clinton administration presented a A compelling case that Microsoft had committed abusive monopolistic A practices, Microsoft shot itself in the foot during hearings with 8 Gates' lame testimony and a blatantly fraudulent WindowsA demonstration, two federal judges and an appeals court issued the 2 findings that Microsoft is, in fact, a monopolist.  F Now we have the "W" administration letting Microsoft off the hook, notE even attempting to negotiate getting Microsoft to back off of some of E its practices?  And we will have dumped upon us on October 25 Windows E XP and Office XP, some of the most draconian software ever?  Ohmigod! A I forgot!  We're all software pirates, and poor poor Microsoft is F losing money.  And we're expected to trust Microsoft with Passport andA electronic payments?  This is, after all, the same Microsoft that C leaves virus holes in its software big enough to drive a tank thru.   C I could rail on and on, but it will do little good.  It's enough to D make me consider going back to the abacus and sliderule... Ben Myers  : On Fri, 07 Sep 2001 03:20:37 GMT, politics2000@hotmail.com! (politics2000@hotmail.com) wrote:   B >The only "black helicopter" theory that makes any sense regardingG >Feds' suit against Microsoft (and this is a common political practice, E >by the way) is that Gates was approached by both the RNC and the DNC F >for campaign contributions, to which he politely replied "no thanks".G >He was then informed, in well-chosen words, that his company would not E >be a target of investigation or subjected to an IRS audit if he were E >to make hefty contributions (read "pay protection money").  When his > >answer was still "no thanks" after that threat, Microsoft wasC >immediately demonized by the Feds (dutifully reported as such by a D >lazy and/or biased press) and the DOJ, which is mostly "department"D >with only trace elements of "justice", was given the green light toF >send in the troops. This is evident by the fact that they based theirG >anti-trust argument on a very weak browser issue (which also means any 5 >IRS audit they may have considered was even weaker).  > B >By definition, a monopoly is when the public is not given anotherE >choice.  Well, we do have other choices ... VMS, UNIX, Linux ... and B >any Windows user can go to shareware.com and get Netscape or someF >other browser for free.  The Feds know this, of course, and they knew? >going into this suit that they'd probably lose.  However, they B >achieved their ultimate goal ... they demonstrated that no one isG >going to be immune from their fund-raising shake-down tactics.  I hope E >Bill doesn't cave in and dole out contributions in the next election F >cycle.  DOJ investigations and IRS audits on successful companies whoG >don't contribute to either or both of these incredibly corrupt parties / >has to stop, and now is as good a time as any.   	 Ben Myers  Spirit of Performance, Inc.  73 Westcott Road Harvard, MA 01451  tel: 978-456-3889  eFax: 810-963-0412    PayPal, MC, VISA, AMEX accepted.   ------------------------------   Date: 6 Sep 2001 16:32:35 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen) 7 Subject: cancel <eF8yxxLd5jEC@eisner.encompasserve.org> 3 Message-ID: <We0JpR7ev$nl@eisner.encompasserve.org>   . cancel <eF8yxxLd5jEC@eisner.encompasserve.org>   ------------------------------  $ Date: Thu, 6 Sep 2001 13:10:28 -0500+ From: Phil Mendelsohn <mend0070@tc.umn.edu> * Subject: Re: Carly's email to Compaq staffH Message-ID: <Pine.SOL.4.20.0109061305450.23524-100000@garnet.tc.umn.edu>  ! On 6 Sep 2001, Tom Gardner wrote:   G >     	- Carly's memo, was long, contained words not in any dictionary, G >     	  made obscure references to "double downing" and "middle game". 7 >     	  It had the flavour of politician's propaganda.   ; And she ended the first paragraph with a grammatical error.m  B I don't like the comparisons of the DEC and HP culture.  Both wereH achieved in large part because Ken Olsen and Harlan Anderson, as well asH Monsieurs Hewlett and Packard, were engineers.  An engineer can engineerI business practices (instead of the pap coming out of MBA programs), but ayH business person can not use business practices to build a product.  None6 of that exists anywhere anymore, does it?  So it goes.   Phil Mendelsohn    -- e* I like HP, and at one time I liked Compaq,7 but I liked DEC better than HP and Compaq put together.r   ------------------------------  % Date: Thu, 06 Sep 2001 15:53:46 -0700w< From: "Kenneth H. Fairfield" <Kenneth.H.Fairfield@intel.com>; Subject: Re: Converting a stream_lf file to a variable file-) Message-ID: <3B97FE7A.63F9725B@intel.com>    David Spencer wrote:  @ > How about a timeout over the take-under of HP by Compaq for an > actual question :) >0I > I've got some files generated by a C program that are Stream_LF format. I > I'd like to write a BASIC program to read them. I've considered severalr1 > options but with little success in any of them.  >iC > Is there a CONVERT/FDL that works? Or perhaps someone has a nifty F > subroutine in C that I could call that would return the data line byA > line? (I'm not a C programmer.) Or another worthy suggestion on  > how I may solve my problem?l  A Given the other information provided in follow-ups, particularly, B the "161905 byte record too large for user's buffer" message, it'sB clear that the C program is NOT writing reasonable text _records_.A You might call it a "stream" file (no defined records), or even a0> "binary" file, even it the "binary" data consist only of ASCII characters.   @ In cases like this, I've found it useful to set the file to haveA the same characterists as a "binary" file, e.g., a VMS .EXE file,  so:a  E $ SET FILE/ATTR=(ORG:SEQ,LRL:512,MRS:512,RAT:NONE,RFM:FIX) <the_file>s  < This will allow you to read the program with essentially any? utility, but you will read the data in 512 byte chunks, whethereD or not that corresponds to any explicit or implied record structure.C If there are <LF> characters in the file, they will be read as <LF> 1 characters, not implicitly as record terminators.o  = One advantage that SET FILE/ATTR has over CONVERT is that the A contents of the file are left UNCHANGED, whereas CONVERT actuallye! modifies the content of the file.p      -Kenh --6 I don't speak for Intel, Intel doesn't speak for me...   ------------------------------  $ Date: Fri, 7 Sep 2001 00:47:04 +01001 From: "Chris Townley" <news@townleyc.demon.co.uk>t; Subject: Re: Converting a stream_lf file to a variable fileaA Message-ID: <999820406.15221.0.nnrp-14.d4e45fa5@news.demon.co.uk>n  @ "David Spencer" <spencer@spaamfree.recneps.com> wrote in message8 news:050920011539026758%spencer@spaamfree.recneps.com...I > In article <3B969D6A.708FFB4B@home.nl>, Dirk Munk <munk@home.nl> wrote:e >r > > David Spencer wrote: > >t > > > In article< <3b96213b$0$21924$6e365a64@newsreader02.highway.telekom.at>,7 > > > Ren Schelbaum <rene.schelbaum@datakom.at> wrote:o > > >dJ > > > > It should work with Basic, long as the records are not longer than 32k.   <skip>    > > $ run x > > > Record on file too bigI > > > On channel 1 for file STUFF:[SPENCER]TEST.TXT;3 at user PC 00000000u4 > > > 161905 byte record too large for user's buffer > >s@ > >   ^^^^^^ There is your problem, 32676 byte is the maximum !! >aE > Yep - looks more and more like I need a C subroutine to read this C4$ > generated file... Any volunteers?? >n  K No need for a C routine - been here, and done this in Basic to access fileswF from Unix - in fact had to work out to do it in a couple of hours fromK extreme pressure from the front line people. All because a former colleaguef? hadnt tested with any real sized files. Nothing unusual - then!O  K Simply open as STREAM format with a defined fixed length buffer. Now create G a function to extract the 'record' up to (and excluding) the LF, whilst J doing another GET from the file to re-fill the file buffer as is required.  B I have processed 1000+ block files in this manner with no problem.   --
 Chris Townleyc chris@townleyc.demon.co.uk townleyc@spicers.ltd.ukg   ------------------------------  % Date: Thu, 06 Sep 2001 20:11:09 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>e; Subject: Re: Converting a stream_lf file to a variable filed' Message-ID: <3B981EAD.1C9604A9@fsi.net>n   Tzachi Nissim wrote: > M > We've had to deal with the opposite problem - converting a variable file toiA > stream_lf. We just created an fdl file for a stream_lf and used 4 > convert/fdl=... - wouldn't that work here as well?  D Based on another post from him (101000+ bytes in a record), no - RMS2 only allows 32767. So, no - this would fail, also.   -- r David J. Dachterad dba DJE Systemso http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/M   ------------------------------  % Date: Thu, 06 Sep 2001 22:01:32 +0200s, From: Didier Morandi <Didier.Morandi@gmx.ch>$ Subject: Re: cpio ported to OpenVMS?& Message-ID: <3B97D61D.742469C5@gmx.ch>  ! jamese@beast.dtsw.army.mil wrote:l >  > Hello, > = > Does any one have any info about a port of cpio to OpenVMS?b  3 (Folks? Are you ready? Okay, let's go all together)   " W H A T   I S   CPIO ?????????????   D. l> ==============================================================> 4-sep-2001: one of the three happiest days of my whole life...   ------------------------------  $ Date: Thu, 6 Sep 2001 16:14:03 -0400  From: jamese@beast.dtsw.army.mil$ Subject: Re: cpio ported to OpenVMS?0 Message-ID: <01090616140360@beast.dtsw.army.mil>  M Didier Morandi <Didier.Morandi@gmx.ch> wrote in <3B97D61D.742469C5@gmx.ch> onb  Thu, 06 Sep 2001 22:01:32 +0200:  # > jamese@beast.dtsw.army.mil wrote:  > > 
 > > Hello, > > ? > > Does any one have any info about a port of cpio to OpenVMS?  > 5 > (Folks? Are you ready? Okay, let's go all together)n > $ > W H A T   I S   CPIO ?????????????   It's a unix archive program.  F We have one customer droping off compressed cpio files on our VMS box.H These have to be copied over to a Solaris box, uncompressed, un-cpio'ed,G and copied back to the VMS box. This is so another customer can pick upw@ the results from the VMS system. Just trying to save some steps.  : Ed James                           ed.james@telecomsys.com5 TeleCommunications Systems, Inc.   voice 410-295-1919l; 2024 West Street, Suite 300              800-810-0827 x1919y5 Annapolis, MD 21401-3556           fax   410-280-1094o   ------------------------------  % Date: Thu, 06 Sep 2001 22:35:18 +0200n< From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com>$ Subject: Re: cpio ported to OpenVMS?( Message-ID: <3B97DE06.926C1FCC@home.com>  + CPIO is included in the POSIX ad-on to VMS.o- Don't know if you have to run the whole POSIX . install, or if you just could extract the cpio- util from the kit and run it without the restc- of the POSIX stuff. Who is actualy using thise
 POSIX thing ?e  ! It's metioned in the VMS-FAQ on :t6 http://www.openvms.compaq.com/wizard/openvms_faq.html.   Jan-Erik Sderholm.,  ! jamese@beast.dtsw.army.mil wrote:  >5 > Hello, >4= > Does any one have any info about a port of cpio to OpenVMS?.   ------------------------------   Date: 6 Sep 2001 16:31:26 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen) $ Subject: Re: cpio ported to OpenVMS?3 Message-ID: <eF8yxxLd5jEC@eisner.encompasserve.org>r  U In article <3B97D61D.742469C5@gmx.ch>, Didier Morandi <Didier.Morandi@gmx.ch> writes:-# > jamese@beast.dtsw.army.mil wrote:0 >> 1	 >> Hello,  >>  > >> Does any one have any info about a port of cpio to OpenVMS? > 5 > (Folks? Are you ready? Okay, let's go all together)0 > $ > W H A T   I S   CPIO ?????????????  D See Sue Skonetski's list of DECUS sessions for next week in Anaheim," posted recently to this newsgroup.   ------------------------------  * Date: Thu, 6 Sep 2001 19:23:42 -0700 (PDT). From: Fabio Cardoso <fabiopenvms@yahoo.com.br>$ Subject: Re: cpio ported to OpenVMS?? Message-ID: <20010907022342.1322.qmail@web20203.mail.yahoo.com>   	 HP Peopler   What about  ....    
 $ BACKUP/CPIO    $ BACKUP/DDu   $ BACKUP/TAR   Regardsm   FC=20 2 --- Larry Kilgallen <Kilgallen@SpamCop.net> wrote:/ > In article <3B97D61D.742469C5@gmx.ch>, Didierd) > Morandi <Didier.Morandi@gmx.ch> writes: % > > jamese@beast.dtsw.army.mil wrote:a > >>=20f > >> Hello,r > >>=20e4 > >> Does any one have any info about a port of cpio
 > to OpenVMS?a > >=20- > > (Folks? Are you ready? Okay, let's go allO > together)  > >=20& > > W H A T   I S   CPIO ????????????? >=205 > See Sue Skonetski's list of DECUS sessions for nextV > week in Anaheim,$ > posted recently to this newsgroup.     =3D=3D=3D=3D=3D L =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3Dd F=E1bio dos Santos Cardoso OpenVMS System Manager Rio de Janeiro - Brazild fabiopenvms@yahoo.com.brL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3Dc  2 __________________________________________________ Do You Yahoo!?L Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger=   http://im.yahoo.come   ------------------------------  % Date: Thu, 06 Sep 2001 21:59:10 +0200t, From: Didier Morandi <Didier.Morandi@gmx.ch> Subject: Re: DCL doubts...& Message-ID: <3B97D58F.483DEF9C@gmx.ch>   Keith Cayemberg wrote: > O > Assuming one likes simplicity and has a decent VTxxx emulation, the followingoO > small improvements to Mr. Dachtera's and Mr Cayemberg's example might be niceo	 > to add.e   $ say = "write sys$output" $ esc[0,8] = 27iG $ say "Please enter your name: ____________________"	    !assuming it'si line 10e $ prompt= esc+"[10;25f"  $KOMON_BABY:6 $ read/end=NO_MORE/prompt="''prompt'" sys$command name- $ if f$len(name) .gt. 20 then goto KOMON_BABYL $ etc.  M I leave to you the pleasure to erase the previous input when it was too long.o     D.> ==============================================================> 4-sep-2001: one of the three happiest days in my whole life...   ------------------------------   Date: 7 Sep 2001 02:59:45 GMTa5 From: ccburgess@uqstu.jdstory.uq.edu.au (Ian Burgess)X Subject: Re: DCL doubts.... Message-ID: <9n9d71$m6r$1@bunyip.cc.uq.edu.au>  p In article <3a65a5c8.0109060151.4b378415@posting.google.com>, keith.cayemberg@conti.de (Keith Cayemberg) writes:9 >Assuming one has a decent VTxxx emulation, the followingr< >small improvements to Mr. Dachtera's example might be nice  >to add. >fM >$ ESC[0,8]==27                  !set terminal Escape code for VT100 commandsp? >$ CSI*VT :== "''ESC'["          !introduces a Control SequenceM< >$ UNDER*VT:== "''CSI'4m"        !sets underlined charactersI >$ NORM*VT:== "''CSI'0m"         !sets all character attributes to normal 2 >$ ONEUP*VT :==  "''CSI'1A"      !jump up one line >$!o" >$ UNDLN = "                     " >$ ULLEN = F$LENGTH( UNDLN ) >$ CTRLH[0,8]=8a( >$ BKSPC = F$FAO( "!''ULLEN'*''CTRLH'" )= >$ PRMPT = "Please enter your name: " + UNDER + UNDLN + BKSPCc+ >$ READ SYS$COMMAND UNAME/PROMPT="''PRMPT'"o >$!  >$ SAY ONEUP,NORM  >$ show symbol UNAME >$ exitp   A very elegant solution!   How about a very crude one?   < $ PRMPT = "Please enter your name: ________________________"; $ SET MESSAGE/NOFACILITY/NOSEVERITY/NOIDENTIFICATION/NOTEXTo1 $ READ SYS$COMMAND UNAME/PROMPT="''PRMPT'"/TIME=0a3 $ SET MESSAGE/FACILITY/SEVERITY/IDENTIFICATION/TEXT  $ CR[0,8] = 13) $ PRMPT = CR + "Please enter your name: "e* $ READ SYS$COMMAND UNAME/PROMPT="''PRMPT'"  E At least it has the virtue of working even if the emulation is crude!    Ian Burgess  University of Queensland I.Burgess[at]its.uq.edu.au www.its.uq.edu.aut   ------------------------------  $ Date: Thu, 6 Sep 2001 19:39:33 -0400; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>FY Subject: Re: dir help ---%LIBRAR-F-OPENIN, error opening  SYS$COMMON:[SYSLIB]NCS$LIBRARY.o$ Message-ID: <3b980989$1@news.si.com>  9 michaelandbarbarayoung@hotmail.com (Michael Young) wrote:t  E >Sure enough, show symbol showed that I'd used PURGE as the name of aeD >variable when I'd meant to use P1 in the 2.com another file I'd ran earlier.  L When you have stand-aloone command procedures and you want to make sure thatK there are no side effects from prior symbol definitions, be sure to includeq
 the comand  % $ set symbol/scope=(noglobal,nolocal)    at the top.  --A Brian Tillman                   Internet: tillman_brian at si.comVA Smiths Aerospace                          tillman at swdev.si.comz= 3290 Patterson Ave. SE, MS      Addresses modified to prevent < Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  % Date: Thu, 06 Sep 2001 15:04:59 -0400e) From: Andrew Robert <arobert@townisp.com>u Subject: DSN - dead or alive* Message-ID: <3B97C8DB.4070205@townisp.com>   Hi everyone,    G I am receiving DECevent messages indicating failures to connect to DSN.c  7 Anyone know if the Colorado service center DSN is down?e  0 Tried connecting to it manually but no susccess.   ------------------------------  # Date: Thu, 06 Sep 2001 19:32:22 GMTa& From: "john nixon" <jnixon@cfl.rr.com>  Subject: Re: DSN - dead or alive> Message-ID: <abQl7.54693$8c3.11296225@typhoon.tampabay.rr.com>  K My guess is that you are still using the recently retired DSN  version 1.2.o You must upgrade to DSN V3  6 "Andrew Robert" <arobert@townisp.com> wrote in message$ news:3B97C8DB.4070205@townisp.com... > Hi everyone, >  >)I > I am receiving DECevent messages indicating failures to connect to DSN.c >r9 > Anyone know if the Colorado service center DSN is down?o >r2 > Tried connecting to it manually but no susccess. >a >    ------------------------------  % Date: Thu, 06 Sep 2001 15:42:14 -0400 ) From: Andrew Robert <arobert@townisp.com>t  Subject: Re: DSN - dead or alive( Message-ID: <3B97D196.90701@townisp.com>   Nope.e    7 Using DSN v3 via direct internet connection to Colorado-   No modem involved-     john nixon wrote:0  M > My guess is that you are still using the recently retired DSN  version 1.2.  > You must upgrade to DSN V3 > 8 > "Andrew Robert" <arobert@townisp.com> wrote in message& > news:3B97C8DB.4070205@townisp.com... >  >>Hi everyone, >> >>I >>I am receiving DECevent messages indicating failures to connect to DSN.h >>9 >>Anyone know if the Colorado service center DSN is down?  >>2 >>Tried connecting to it manually but no susccess. >> >> >> >  >    ------------------------------  $ Date: Thu, 6 Sep 2001 16:42:14 -0400  From: norm.raphael@jamesbury.com  Subject: Re: DSN - dead or alive4 Message-ID: <C2256ABF.007176EC.00@jklh21.valmet.com>  7 Using DSN v3 via direct internet connection to Coloradoc   No modem involvede  
 Works for me.i        - arobert@townisp.com on 09/06/2001 03:42:14 PMe  % Please respond to arobert@townisp.com    To:   Info-VAX@mvb.saic.comv cc:M! Subject:  Re: DSN - dead or alivei         Nope.   7 Using DSN v3 via direct internet connection to Coloradog   No modem involved          john nixon wrote:.  M > My guess is that you are still using the recently retired DSN  version 1.2.g > You must upgrade to DSN V3 > 8 > "Andrew Robert" <arobert@townisp.com> wrote in message& > news:3B97C8DB.4070205@townisp.com... >- >>Hi everyone, >> >>I >>I am receiving DECevent messages indicating failures to connect to DSN.j >>9 >>Anyone know if the Colorado service center DSN is down?i >>2 >>Tried connecting to it manually but no susccess. >> >> >> >  >e   ------------------------------  % Date: Fri, 07 Sep 2001 00:20:27 +0100 1 From: Steve Reece <SYSTEM@ipl.demon.co.nospam.uk>i  Subject: Re: DSN - dead or alive6 Message-ID: <3B9812CB.1EBD37BE@ipl.demon.co.nospam.uk>  A DSN in the UK has virtually no content now.  The service is beingo7 retired in favour of a search-challenged web-interface.iH Look at www.compaq.co.uk/support and click on the "successor" (note: not3 replacement) which is found as the Ask Compaq link.n   Steve.   Andrew Robert wrote: >  > Hi everyone, > I > I am receiving DECevent messages indicating failures to connect to DSN.  > 9 > Anyone know if the Colorado service center DSN is down?e > 2 > Tried connecting to it manually but no susccess.   --  G "A shadow fell over her face; clear, as if the composure were rent likeaE a veil.  And her lips parted, but only with a short intake of breath.oA Then she said, 'Well, then you are right.  Indeed, we are even.'"u% 		Louis, "Interview with the Vampire"y   ------------------------------  # Date: Fri, 07 Sep 2001 01:28:12 GMTH- From: "Richard L. Dyson" <rickdyson@home.com>   Subject: Re: DSN - dead or alive' Message-ID: <3B98229F.A1A5242@home.com>-   Andrew Robert wrote: >  > Nope.  > 9 > Using DSN v3 via direct internet connection to Colorado. >  > No modem involvedt >  > john nixon wrote:  > O > > My guess is that you are still using the recently retired DSN  version 1.2.  > > You must upgrade to DSN V3 > >n: > > "Andrew Robert" <arobert@townisp.com> wrote in message( > > news:3B97C8DB.4070205@townisp.com... > >r > >>Hi everyone, > >> > >>K > >>I am receiving DECevent messages indicating failures to connect to DSN.  > >>; > >>Anyone know if the Colorado service center DSN is down?F > >>4 > >>Tried connecting to it manually but no susccess.  J 	I was in the middle of a DSN SRA when it quit on me too.  I was unable toJ augment.  I was able to submit a new SRA.  I was told that engineering had	 installedeL a new image on their CO server and it apparently did not work correctly. :)  TheyG reverted back to the previous version and I was able to get back again.i  L 	I also just got a patched share image file for DSN v3.0 that is supposed toB help with the DSN<->VMS Mail method problems some of use have been
 experiencing.   ! 	It is working well for me today.k   Rick   ------------------------------   Date: 6 Sep 2001 20:14:40 GMTs- From: forkosh@panix2.panix.com (John Forkosh)o$ Subject: Re: ed/edt corrupting files) Message-ID: <9n8lfg$s2v$1@news.panix.com>h  + Mike Rechtman (rechtman@tzora.co.il) wrote:n? : This strikes a familiar chord from back in the mists of time.s; : Try the edit/edt on a _real_ VT - just as a double-check.d; : I have a recollection of some emulators getting mixed up. 7 : Also "set term/inq" does not always do all it should.  : ~Miker  5 Bingo.  Couldn't get a real VT, but used KEA emulatorO3 running on a Win-NT box, and that worked perfectly.H8 Do you know any combination of settings for a Wyse (285)2 that works okay?  Thanks for clarifying situation, John (forkosh@panix.com)   : John Forkosh wrote:-7 : > Hoff Hoffman (hoffman@xdelta.zko.dec.nospam) wrote:m5 : > : forkosh@panix1.panix.com (John Forkosh) writes::H : > : :Just installed vms7.2 on a vs4000/60 and started using ed/edt.... : > :1E : > :   <discussion of apparent attribute incompatibility/corruption>m : > :cB : > I'm running vs with S3 up, and a Wyse-285 plugged in mmj port,= : > running as Device_Type: VT400_Series (I tried various andk? : > sundry combinations with same result), and set term/inquire E : > in login.com.  Also tried setting crfill and lffill with no luck.o : > Any suggestions?  Thanks,e : > John (forkosh@panix.com)   ------------------------------  % Date: Thu, 06 Sep 2001 20:13:05 -0500l1 From: "David J. Dachtera" <djesys.nospam@fsi.net>e$ Subject: Re: ed/edt corrupting files' Message-ID: <3B981F21.9086AACE@fsi.net>u   John Forkosh wrote:  > - > Mike Rechtman (rechtman@tzora.co.il) wrote:sA > : This strikes a familiar chord from back in the mists of time. = > : Try the edit/edt on a _real_ VT - just as a double-check.e= > : I have a recollection of some emulators getting mixed up. 9 > : Also "set term/inq" does not always do all it should.s	 > : ~Miker > 7 > Bingo.  Couldn't get a real VT, but used KEA emulatorr5 > running on a Win-NT box, and that worked perfectly.l: > Do you know any combination of settings for a Wyse (285) > that works okay?    D Make sure it's emulating at least a VT100 (VT102 if it has a printer. port). That still might not "fix" the problem.   -- ' David J. Dachteran dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/+   ------------------------------  $ Date: Thu, 6 Sep 2001 22:15:03 -0400  From: John Santos <JOHN@egh.com>$ Subject: Re: ed/edt corrupting files6 Message-ID: <1010906215754.64342B-100000@Ives.egh.com>  5 Could this be a console terminal driver problem?  SeeR below:  " On 6 Sep 2001, John Forkosh wrote:  - > Mike Rechtman (rechtman@tzora.co.il) wrote: A > : This strikes a familiar chord from back in the mists of time.b= > : Try the edit/edt on a _real_ VT - just as a double-check.t= > : I have a recollection of some emulators getting mixed up.o9 > : Also "set term/inq" does not always do all it should.m	 > : ~Mike0 > 7 > Bingo.  Couldn't get a real VT, but used KEA emulatorh5 > running on a Win-NT box, and that worked perfectly.J: > Do you know any combination of settings for a Wyse (285)4 > that works okay?  Thanks for clarifying situation, > John (forkosh@panix.com) >  > : John Forkosh wrote:19 > : > Hoff Hoffman (hoffman@xdelta.zko.dec.nospam) wrote:c7 > : > : forkosh@panix1.panix.com (John Forkosh) writes:9J > : > : :Just installed vms7.2 on a vs4000/60 and started using ed/edt.... > : > :sG > : > :   <discussion of apparent attribute incompatibility/corruption>o > : > :OD > : > I'm running vs with S3 up, and a Wyse-285 plugged in mmj port,? > : > running as Device_Type: VT400_Series (I tried various and=A > : > sundry combinations with same result), and set term/inquire G > : > in login.com.  Also tried setting crfill and lffill with no luck.  > : > Any suggestions?  Thanks,  > : > John (forkosh@panix.com)  D Over the last few versions (post v7.1 or .2? on both VAX and Alpha),D I've had random screen problems in TECO in screen mode (4,7:w mode).  @ I think Alpha V7.2 was the worst, and things have improved a lotC in v7.2-1 & V7.3.  Since TECO isn't supported, I haven't complained 	 about it.O  ; Anyway, the current problems seem to be worse on (and maybeh: exclusively on) the console port.  I wonder if the problem9 is really a flow-control problem in the OP driver?  (I'ver7 also seen problems using a DECterm, both locally (Alpha : console) and served by a DEC Unix workstation (V4.0d), but; these problems occur much less often.  Problems are usuallyw7 of the form of the cursor displaying one line down fromm: where it should be, scraps of old text left on the screen,9 and the scrolling regions getting messed up.  (4,7:w mode59 splits the screen into two scrolling regions, a large one2< at the top to display the text and a small one at the bottom9 for command input.  When the scrolling regions get messed08 up, the command window scrolls up into the text window.)  8 The problems when using DECTerm occur very rarely, maybe5 once every few weeks when using TECO constantly.  Then4 problems on a real VT420 on a VAX/Alpha console port4 (OPA0:) occur almost every time I try to use TECO in7 that environment.  TECO seems to work fine when used ono6 a VT420 connected via a LAT terminal server (DECserver2 200 & 700), and while telnet'ed or SET HOSTed from
 another node.w  4 I don't use EDT, but your problems sound similar and may have a common cause.   -- s John Santoso Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Thu, 06 Sep 2001 16:09:45 -0700e< From: "Kenneth H. Fairfield" <Kenneth.H.Fairfield@intel.com> Subject: Re: eXcursion Question ) Message-ID: <3B980239.5514F3D4@intel.com>E   Mark Berryman wrote:   > Hauser@Fauske.com wrote: > >CL > > A Fortran generated executable is launched from my "LOGIN.COM" file. TheN > > executable requests some information from the user at login time. While itM > > works fine from a VT type terminal and from local DECterms running on vaxeM > > and alpha workstations, it fails on PC's connected via eXcursion V3.0.571 I > > with the application being $create/terminal/detached. It seems that a.O > > connection is made, but the terminal window never appears on the PC screen. K > > If I remove the executable launch from my LOGIN.COM everything works aspN > > expected. Is there any way to make this work? VMS version is V7.2-1. Motif > > version is 1.2-5.. > B > Your login.com is executed twice when creating an X-window based
 > session.! > Recoding to use something like:t >r7 > $ IF F$MODE() .EQS. "INTERACTIVE" THEN RUN executable  >a) > will probably solve your problem. [...]a  E Good advise, but better is to check whether SYS$COMMAND is a terminalDC device before doing any kind of INQUIRE, particularly because there0F are circumstances (and starting a detached DECterm may be one of them,D I don't remember for sure) for which an INTERACTIVE process does NOT< have an attached terminal.  I recommend something like this:  &     $ If F$GetDvi("SYS$COMMAND","TRM")
     $ Then     $    RUN executableD     $    SET TERM ...D
     $    etc.=     $ Endif       -Ken  --6 I don't speak for Intel, Intel doesn't speak for me...   ------------------------------  $ Date: Thu, 6 Sep 2001 20:26:55 -0400; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>_ Subject: Re: eXcursion Question $ Message-ID: <3b9814a4$1@news.si.com>  I >A Fortran generated executable is launched from my "LOGIN.COM" file. TheeB >executable requests some information from the user at login time. ..snip..H >If I remove the executable launch from my LOGIN.COM everything works asK >expected. Is there any way to make this work? VMS version is V7.2-1. Motifi >version is 1.2-5.  	 Yes, put:   9 $ if f$mode() .eqs. "INTERACTIVE" then run yourexecutablet  H The DECterm controller is login mode OTHER and will fail in creating the DECterm window without this. --A Brian Tillman                   Internet: tillman_brian at si.com!A Smiths Aerospace                          tillman at swdev.si.com = 3290 Patterson Ave. SE, MS      Addresses modified to preventn< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  % Date: Thu, 06 Sep 2001 11:38:43 -0700=! From: Don Sykes <don@alphase.com>p) Subject: Re: Feeling Better about Itanium-+ Message-ID: <3B97C2B2.F1FC3C3F@alphase.com>9   Bill Todd wrote: > = > "Lyndon Bartels" <lbartels@pressenter.com> wrote in messaget* > news:3B9680EC.10CDD794@pressenter.com... >  > ...  > G > > Some of my thoughts are.... What does Intel have to loose by simply@J > > re-labeling current Alphas, or what would have been soon-to-be alphas. > M > Face.  Credibility with partners who have spent *years* preparing their owntK > products for the Itanium architecture (HP, for example, would likely be a1N > bit miffed, but so would a whole bunch of smaller fish who've been preparingN > compatible board components, etc.).  Monopoly power (no one else can legallyC > produce Itaniums or copies thereof, whereas Compaq owns the Alpha J > architecture, Samsung shares the right to develop it, and IBM is anotherL > production source:  likely good for customers, but likely not perceived asJ > good for Intel).  Time (you clearly haven't a clue what it takes to turnI > even a fully-completed design into shippable hardware if you think they K > could do so in a year - unless you're suggesting that they simply buy EV7eK > masks from Compaq and effectively become another EV7 production partner):"N > even *Compaq* doesn't think they can ship EV7 in a year, and they've alreadyG > got running silicon.  I'm sure there's a lot more, but why waste timeIJ > conjuring it up when the above is so much more than a sufficient answer? > J > > Like I said, their 64 bit processors aren't out there by the millions,K > > and all they'd have to do is say, "This next generation chip is TOTALLYdK > > different. You'll have to port you applications/Operating systems to it-L > > now, instead of moving to what we've been giving you." If they did that,5 > > I'd bet they'd have hardware out there next year.% > >RH > > Also, with the recent influx of Alpha engineers, you can bet in someL > > think tank at Intel they're weighing precisely that possibility. They're > > debating...n > K > Bullshit.  A few of the Alpha immigrants might be thinking such thoughts,dN > but the only thing Intel is concentrating on is how to make Itanium prevail.5 Really Bill, how do you know what Intel is thinking ?    > N > If, down the road, Power4 and Hammer whup their asses sufficiently, *and* ifN > the Alpha team has as much difficulty as seems likely getting Itanium workedM > around into something more competitive, *then* they might dust off EV8 as a 5 > last resort (but by then it'll likely be too late).t > " > I don't like Intel as a company,1 Could never have guessed that by your comments :)M  * > but nothing would please me more than toM > see them replace Itanium with Alpha and succeed wildly with it (and I think K > they could if they did).  But it just ain't gonna happen unless something I > forces it to happen, and as long as the pundits continue to assume that K > Itanium will inevitably prevail what possible reason would Intel have fornL > scrapping Itanium (hint:  certainly not *just* because it's a lousy idea)? >  > >cI > > 1. Take current Itanium, and get input from the alpha team to make ita > > better.e > N > That will definitely happen.  But the most optimistic estimate would be thatN > some of EV7's on-chip glue for memory and SMP would appear in 2005, and thenK > *maybe* some OOO SMT features in 2006 - and only if Power4 is enough of aoN > threat to make them hurry (otherwise, they'll just take their time and tweakK > it around the edges for as long as they can get away with doing so:  thati- > sucker will be *hard* to change radically).o >  > >D< > > 2. Start something totally new with our combined forces. > K > Not a chance:  their plate's more than full with Itanium plus keeping AMD-I > from kicking IA32 sand in their faces more than it already is (plus, ofrF > course, the considerable other development Intel engages in for bothJ > processor and non-processor chips).  If there's one thing Itanium shouldH > have taught Intel over the past 7 years, it's not to embark lightly on > 'something totally new'. >  > >iE > > 3. Trash Itanium and rebadge alpha, a proven, stable, mature CPU.  > N > Not a chance:  Intel's management is almost certainly incapable of believingM > that Itanium could fail in the market in the absence of compelling evidence I > to that effect (the exact opposite of Compaq's management, which provedCK > incapable of believing that Alpha could succeed in the market even in theu. > face of compelling evidence to that effect). >  > >-I > > I'm not the smartest man in the world, but it's clear to me which onesK > > would get onto the market and start producing profits first. Profits, I@- > > might add, that Intel would like to have.n > N > If you chose anything but (1), I'll agree whole-heartedly with your startingN > phrase 3 lines above.  Merced, uninspiring though it may be, is *already* onI > the market, and within a year McKinley will be as well.  They're hardlyvM > leadership products, but plenty adequate to generate profit - especially if I > the industry can continue to be horn-swoggled into believing that theiraN > ascendancy is inevitable, and so far Intel continues to succeed in doing so. >  > - bill   ------------------------------  % Date: Thu, 06 Sep 2001 20:01:21 -050001 From: "David J. Dachtera" <djesys.nospam@fsi.net>m) Subject: Re: Feeling Better about Itaniuml' Message-ID: <3B981C61.A4827A2F@fsi.net>o   Rob Young wrote: > ] > In article <3B96BF7A.218D81CA@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:  > > JF Mezei wrote:- > >> > >> "Main, Kerry" wrote:eP > >> > I suspect the recent Intel press releases will show that the Compaq AlphaP > >> > folks now working at Intel will have a fair amount of influence on future > >> > directions for IPF. > >>R > >> Be realistic. The digital engineers haven't had enough time to make an impactP > >> yet. However, remember that Intel probably had access (legit or not) to allP > >> the technologies, and now that they have the legal rights to them, they can$ > >> start to announce these things. > >c. > > To quote (more or less) from Tony Robbins: > >cC > > What people CAN do is virtually unlimited. What they WILL do iso > > frequently disappointing.  > >n > @ >         I can do ALL things through Christ who strengthens me. > " >                 Phillipians 4:13 > % >                                 Robh  D ...but the question remains, what *WILL* you do? How does the spirit	 move you?v   --   David J. Dachtera  dba DJE Systemsy http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/<   ------------------------------  % Date: Thu, 06 Sep 2001 20:58:47 -05009. From: Lyndon Bartels <lbartels@pressenter.com>) Subject: Re: Feeling Better about Itaniumn. Message-ID: <3B97E386.497D382C@pressenter.com>   Bill Todd wrote:  M > Face.  Credibility with partners who have spent *years* preparing their own K > products for the Itanium architecture (HP, for example, would likely be a N > bit miffed, but so would a whole bunch of smaller fish who've been preparing& > compatible board components, etc.).   H Face.... Credibility... Neither on means spit where profits are stake. I@ can image the "spin" Intel can put on it already. "Using all theF engineering experience from our combined sources, we've found many newH and exciting ways to extend the flexibility and performance of the alpha technology.e  > Considering that those Compaq engineers also know how to buildB compatible boards and components, that shouldn't be too much of an issue.  (  Monopoly power (no one else can legally& > produce Itaniums or copies thereof,   B I don't think "Monopoly" should be a big issue. Intel's capable of0 producing enough chips to control the market...     F What about the current EV6x processors? I'd be willing to bet that allE the schematics and specifications for every motherboard to support an4H EV6x processor is still in existence. I seriously doubt that information< has been deleted. And besides.... VMS backup actually works!   >  > N > If, down the road, Power4 and Hammer whup their asses sufficiently, *and* ifN > the Alpha team has as much difficulty as seems likely getting Itanium workedM > around into something more competitive, *then* they might dust off EV8 as a"5 > last resort (but by then it'll likely be too late).k  E Then why not pre-empt? Take the processor you have, that's already inaC production, that already has the infrastructure to support it. That F already has more performance. That's already paid for. And build that?C Like I said before. When profits and market share are concerned....f Pride don't mean spit.      I > > 1. Take current Itanium, and get input from the alpha team to make it  > > better.n > N > That will definitely happen.  But the most optimistic estimate would be thatN > some of EV7's on-chip glue for memory and SMP would appear in 2005, and thenK > *maybe* some OOO SMT features in 2006 - and only if Power4 is enough of aeN > threat to make them hurry (otherwise, they'll just take their time and tweakK > it around the edges for as long as they can get away with doing so:  thatl- > sucker will be *hard* to change radically).e >  > >n  @ This is possible, but I think Intel and the Itanium backers wantH performance *NOW*. HP among them. Intel has learned that it has a way to go.e  < > > 2. Start something totally new with our combined forces. > ; > Not a chance:  their plate's more than full with Itanium c >   ' I don't think this is an option either.f   > > E > > 3. Trash Itanium and rebadge alpha, a proven, stable, mature CPU._ > N > Not a chance:  Intel's management is almost certainly incapable of believingM > that Itanium could fail in the market in the absence of compelling evidencekI > to that effect (the exact opposite of Compaq's management, which proved K > incapable of believing that Alpha could succeed in the market even in thef. > face of compelling evidence to that effect).  H I don't think failing in the market is the issue, it's capturing as muchA market as you can, as fast as you can. And by having a product, atG deliverable product that eclipses the competition is a darn good way top do just that.     D Let's put it this way. You've built a Model T. And you're building a? Model A now. And you're working on designing the V8 and all theoH roadsters that that engine will go into, when somebody drives up drivingE a brand-new BMW Z3 and offers you the plans on how to make it.... Nowe what would you do?    E Better to make this change of direction now, then later. There aren't)? millions and millions of chips out there, hundreds of thousandssB applications. Things are just getting started. Better for everyoneD concerned to take a hit and experience a bit of pain now, then a lotH more later. By taking on the alpha technology now, with a small delay to redo some things.n  G Yes, there will be people upset, but with the promise of delivery *NOW*a should appease many.     -- kG My opinions are mine and mine alone. They seldom align with those of myn	 employer.i    H The only good thing about putting the cart before the horse is you don't have to look at the horse's butt.   ------------------------------  $ Date: Fri, 7 Sep 2001 13:11:29 +0900& From: "David Lee" <phongle@kornet.net> Subject: filescopy+ Message-ID: <9n9h7h$rot$1@news1.kornet.net>s  I Does anyone know how to copy files on VMS platform and then use it on the' Unix platform.  J Currently, there is no connection between the workstations running VMS andL Unix.  On one of my Alpha running OpenVMS 7.2, it has both Decnet and TCP/IPF install.  The other Alpha running Tru64 Unix.  I am wondering if thereK are ay utilities on VMS that allow you to backup files to 4mm data tape ands use it on a Unix wirkstation?e   Thank you in advance.. Davido   ------------------------------  $ Date: Thu, 6 Sep 2001 17:13:52 -0700* From: "Welsh, John" <John.Welsh@Avnet.com>" Subject: FW: Re: KZCCA-CB ProblemsG Message-ID: <FD833ACB0214D511B9B20004ACC5766B01112BA8@asia01.avnet.com>    > >>Barry Treahy wrote:u > K > >>The NIC is disabled per Compaq.  I have been poking around to see if it  > is possible to get it workinglJ > >>and one problem that I believe I have noticed is that there is not MAC" > for the NIC.  Perhaps the driver9 > >>could be loaded to use a hardcoded, arbitrary number?h > 
 > >>Regards, m > 
 > >>Barry  >  > D > >>Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO  > F > >>E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028  >  > Barry,A > 	The card I have has a MAC address on a label on the card so I i > 	presume this is correct.t > @ > 	The problem I have is that the EWDRIVER is not being loaded. B > 	The PKWDriver loads fine and I can see disks on a HSZ70 and run > 	UETP on these.t > G > 	If you use DUMP to look into config_pci.exe ( Block 35 ) you can see  > E > 	the sysgen command to load the ewdriver but it doesn't seem to be VG > 	executed, unlike the pkdriver command which occur just before in theo > file.  > 	( Block 33 )e > G > 	The critical piece of info I need to manually load the driver is then > vectorG > 	for the NIC device. The sysgen parameters in the file are symbols soo > # > 	they are not readily obtainable.s > E > 	I found that the vector for the pkw device is 504 which I obtainedr > fromG > 	ANA/SYSTEM and SHO DEV PKW.    I tried 500 then 510, but the system aE > 	hangs when trying to start up the network.  Obviously I just can'tn > guess the vector ! > 
 > Regards,
 > John Welsh.e >  > Sydney, Australia. > ============== > john.welsh@avnet.com >    ------------------------------  $ Date: Thu, 6 Sep 2001 14:29:14 -0400  From: norm.raphael@jamesbury.com Subject: H-P "jumps the shark"4 Message-ID: <C2256ABF.0065609E.00@jklh21.valmet.com>  A http://www.money.com/money/depts/techinvestor/archive/010905.htmln  P -------------------------------------------------------------------------------- September 5, 2001t H-P "jumps the shark"rC Why investors fled screaming from the specter of Hewlett-Compaq-ard  By David Futrelle   O TV mavens call it "jumping the shark." When producers of long-running shows runIL out of decent ideas to keep their story lines moving forward, they resort toM desperate gimmicks: They bring in a baby (as in Mad About You). They move thexO cast to a new city (Laverne & Shirley). In the case of Happy Days, on a trip tohK California, Fonzie -- on waterskis -- jumped over a shark, a crass grab for O ratings that, in the eyes of some fans, marked the beginning of the end for the N cult of the Fonz. (For more great TV blunders, check out jumpingtheshark.com.)  O Well, Hewlett-Packard and Compaq chose a much more conventional gimmick to perk M up their saggy ratings: They decided to get married (hey, look what it's doneN: for Friends), announcing late Monday the $25 billion deal.  O Announcing the move in a letter to Hewlett-Packard employees, CEO Carly FiorinaDJ warned that competitors would "use every chance they can to discredit" theM deal. Actually, competitors didn't need to say a thing -- this is a deal that- seemed to discredit itself.   L On Tuesday, Hewlett-Packard shares sank nearly 20 percent and Compaq fell 10M percent. On the message boards, critics greeted the merger news with derisionrK ("HOW DO U SPELL STUPID = CARLY FIORINA," wrote one non-fan). Analysts werelO more polite, but most were equally dismissive, doubting the ability of two suchtO massive firms to quickly and efficiently merge into one, especially given theirn track records.  L Compaq's acquisition of Digital Equipment Corporation in 1998 wasn't exactlyM considered a raging success. Meanwhile, Fiorina has had a tough time managingrN Hewlett alone, regularly coming in under quarterly estimates. It's hard to see; how managing a company twice H-P's size will be any easier.   H And even if these "integration issues" get worked out (and regulators inO Washington and Europe step aside to let the deal go through) the merged company K will still have to struggle to compete against an assortment of tech giantse from Dell to Sun to IBM.  O Sure, the combined company may be able to cut costs -- most notably through the M proposed layoff of 15,000 workers. And sure, the merger will create a massivegG tech monster, nearly the size of IBM in terms of total revenues, with a < commanding presence in PCs, servers, printing, and services.  I But in the tech world the biggest isn't always the best. While the mergedrM company would be the biggest PC seller in the world, being number one is cold L comfort if the business remains, as it has recently been for both companies,
 unprofitable.p  I In her letter, Fiorina urged H-P staffers to "stay focused" in the months,M ahead. With a messy merger looming, layoffs coming and the company's stock inmH the toilet, this may prove hard to do. We can only hope H-P and Compaq'sM proposed marriage doesn't end up on the Jump The Shark web site alongside theh? painfully tacky couplings of Lois and Clark and Mork and Mindy.r   ------------------------------  # Date: Thu, 06 Sep 2001 19:08:41 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) " Subject: Re: H-P "jumps the shark"0 Message-ID: <00A01A6E.47125386@SendSpamHere.ORG>   Latest headline news:   J Dr. Jack Kevorkian to become chief CEO of HP-Compaq merger corporation. ;)   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMa            vJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbes    ------------------------------  % Date: Thu, 06 Sep 2001 18:22:17 -0600 * From: yyyc186@illegaltospam.mindspring.com4 Subject: Re: hobbyist license and cpu serial number.; Message-ID: <3b98135e$1$lllp186$mr2ice@nntp.mindspring.com>   , In <frtl7.13$9l4.603@client>, on 09/05/2001 =    at 01:41 PM, "Robert Fraysse" <rfraysse@sctcorp.com> said:'  F I entered a serial number of "1" and it took it.  Then I went into theI console and set the serial number to "1" on my PC-164 and all works well.e   Roland  * >The SID is probably what you are after...   >$ SYSID = F$GETSYI("SID") >$ SHOW SYMBOL SYSID3 >   SYSID = 19923201  Hex = 01300101 Octal = 000401i  I >"Josef Kolbitsch" <skol@sbox.remove.for.spam.tugraz.at> wrote in messagen, >news:9n38js$1cj$1@fstgss02.tu-graz.ac.at... >>    hi there!  >>L >>    i wantd to get a hobbyist license at montagar.com, and i have to enterI >> the "CPU Serial Number" of my workstation. unfortunately it is a thirdu >partyH >> alpha-pc164 workstation, and there is no serial number on the machineH >> itself. how can i find out the serial number of my cpu? (do i have to >removeeM >> the fan, and the number is printed on the cpu itself? i did that once, andt >i7 >> know at least that there is no label on the cpu ...)e >> >>    thanks for your answers, >> >> >>    josef. >> >> --t< >> --------------------------------------------------------- >>  josef kolbitschs >>  > skol@sbox.tu-graz.ac.atp; >>  > http://www.sbox.tu-graz.ac.at/home/s/skol   -> NEW <-t< >> ---------------------------------------------------------     -- n; -----------------------------------------------------------' yyyc186@mindspring.com; -----------------------------------------------------------    ------------------------------  % Date: Thu, 06 Sep 2001 21:16:46 -0500 . From: Lyndon Bartels <lbartels@pressenter.com>" Subject: HP-Compaq-Intel Trifecta.- Message-ID: <3B97E7BE.F7682F5@pressenter.com>o  G I've been doing some thinking about the whole Intel-Compaq-HP trifecta.t    A For the sake of my opinions, I've made the following assumptions.   E 1. The alpha processor, from a strictly technical standpoint has morei> than a little potential left in it. Maybe several years worth.  D 1a. Only looking at the current 64-bit procesors available out thereB today, available today, and those to be available in the next 6-12= months, the alpha is technically the best there is. (strictly  technically speaking, again.)d  + 2. Compaq's PC area has been loosing money.o  E 3. Compaq's Enterprise area (VMS, Tru64, StorageWorks, NSK) have beenh
 making money.u  G 4. Intel's 64-bit processor, while working has a long way to go (like 3g7 or 4 years) before it can be called "enterprise ready."e    ? Now with those assumptions in mind. Let's look at each company.m   Intel:  H Intel has spent millions of dollars and many man-hours to get to ItaniumG where it is. They've made many promises, companies have counted on themcH to deliver on those promises. But they've learned that they're not goingH to. It'll take them years to get to where they thought they'd be by now.C They've learned, just like the alpha engineers did, that creating a > whole new 64-bit chip is a whole lot more involved than addingF to/augmenting current technology. (Digital with their chip, Intel withH the x86s.) They see AMD getting stronger and stronger, and the potentialG of loosing the opening surge into the 64-bit market space is becoming ae  greater and greater possibility.  F So they Pre-empt. They know the alpha's out there. They've had a tasteD of what it can do, why not acquire the alpha, and go from there? AllD they've have to do is tell their prospective customers that the nextE generation of 64-bit chip will have this "different" instruction set,r@ and since those people haven't gotten a lot of porting to 64-bitE completed yet, they're not loosing a whole lot of time/resources. And F besides, the new chip is "so much better, and so much faster, it'll be well worth it."   F Before getting any farther into to 64 bit realm, while losses would beG minimal, would be the time to make the change. Not 3 years from now. ItnC wouldn't go over very well if they were to make a mid-stream change H then. Right now, they've barely cast off, and are only a little way fromF shore. Changing to a new direction, one that already been traveled, is4 not as hard to do now as it could be in a few years.  G But what about one of their biggest backers? HP? They've spent time andmE resources with the McKinley and Itanium... What are they going to do?      HP.o  G HP's server technology is truly near the end of life. They've stretchedmE it as far as they can. And they've been betting the bank that Intel'soH new 64-bit processor is going to save the day. But it isn't ready... NowE they start scrambling... They look at Compaq... "Hmmm..." they think. F "That might work....what could we do...? We could port HP-UX to alpha.B No, that'd take too long. 'It'd take less time to port some of ourE applications over to alpha and Tru64.' somebody says. "But what abouteD our commitment to Intel and the IA64? How would that look if we justE abandoned them?" somebody else chimes in. "And besides, do we want totH actually *help* one of our competitors? We'd be giving them business andD money?" Yet another person says. "But what if we bought Compaq? ThenE we'd be able to do both." Then the first person comes back. "But what90 about Intel? Again, we have a commitment there."  G If Intel were to acquire the alpha, and call it an intel, then HP couldiH run HP-UX on the "new" "Intel" processor. And be good to go. But there'sB the porting issue. So HP needs to get an OS that will run on it... That's where Compaq comes in.t     Compaq.m  D They've been bleeding red ink from their PC business. Trying to stayF afloat until by siphoning off the money from the bigger boxes. But theE stock-holders are getting a bit restless, and they want profits. They > want profits now. Compaq wants to be a box builder. A "ServiceG Provider." They want to sell, and resell things other people make. ThisnF is what they think they're good at. They really didn't want that peskyE alpha processor when the bought Digital, they just wanted the servicelD organization and the support chain. So they dump the alpha to Intel.B Then they can phase out the OSes as well. Maybe sell them to CA orG somebody who wants them. They'll just bundle it all together and viola! G Instant profits, minimal expense. No R&D. Just a bit of advertising andr watch the money roll in.  H Add to that a bigger PC business... Hey no more PC market red-ink! Watch the money roll in now!  G I really think the the three players sat together, put all the cards onrF the table and took out what each one wanted the most. No matter who itH originally belonged to. Once that was accomplished, they figured out howH to arrive at that goal. First the Intel "licensing of alpha technology."E That made Intel happy. Then the merger. That positions HP to take thepF next step. And the next step, once the merger is actually approved andC completed? The "Roadmap." I wouldn't be surprised to see HP annoucerG using Tru64 (once it's ported to IA64 of course) as the basis for theirhH next generation of unix. Then they port over some of their software, andE their Unix world gets much bigger, better, happier. They'll phrase itaB something like "We'll take the best of both Operating systems, andE building upon the porting to IA64 that's already been done, move to amH new system that will fill the needs of all our customers." Intel waits aH while before announcing the next 64-bit processor, which could very wellG be a repackaged alpha. Intel's powers-that-be, if they ever get presseddF into speaking something near the truth can spin the tail of how "TheirG engineers, learning from the Itanium experience, found many new ways tohH expand the flexibility and power of what once was the alpha technology."C That saves their reputation. Compaq ceases to exist. And because itgA no-longer exists, any change of direction can't be traced back top: Capellas and Compaq because... "hey it was HP's decision."  < Was their a grand conspiracy.... Maybe.... More likely CarlyD orchestrated it all... She thought all this out and said to herself,G "what would be the best possible world according to me?" And arrived atu this scenario..r  G And also, if microsoft wants to have another hack and moving Windows NToF (Or whatever it's called this week) onto the "Intalpha" good for them,G and really good for HP. They've got all that old "NT" code, courtesy ofi Compaq, to help out.    F HP could be the big winner here... At the very least they could simplyF keep the obligations that Compaq agreed to. Snarf up storage works andA the PC area, and trash-can everything else. What would they care?t     -- sG My opinions are mine and mine alone. They seldom align with those of myu	 employer.o    H The only good thing about putting the cart before the horse is you don't have to look at the horse's butt.   ------------------------------  $ Date: Fri, 7 Sep 2001 00:10:33 -0400  From: John Santos <JOHN@egh.com>& Subject: Re: HP-Compaq-Intel Trifecta.6 Message-ID: <1010907000407.64342A-100000@Ives.egh.com>  ) On Thu, 6 Sep 2001, Lyndon Bartels wrote:u   [snip]  I > I've been doing some thinking about the whole Intel-Compaq-HP trifecta.oI > If Intel were to acquire the alpha, and call it an intel, then HP couldkJ > run HP-UX on the "new" "Intel" processor. And be good to go. But there'sD > the porting issue. So HP needs to get an OS that will run on it... > That's where Compaq comes in.-  B The unnamed HP PR person who was quoted in Ken Farmer's post (if IB have my attributes correct) did say they were going ahead with the> HP-UX port to *ALPHA*.  I just assumed he/she was misquoted or> fumble-tongued and meant the HP-UX port to IPF or possibly the% Tru64 and VMS ports to IPF...  but???k   [...]>   -- c John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  $ Date: Thu, 6 Sep 2001 19:35:58 -0400  From: John Santos <JOHN@egh.com> Subject: Re: Huh?w6 Message-ID: <1010906193221.18840A-100000@Ives.egh.com>  E Just got a correction.  It's actually in the local area (about a mile C from work at the Compaq office in Lexington) in October, so no timei' travel or long distances involved.  :-)s  ( On Wed, 5 Sep 2001, David Cressey wrote:   > Yeah, I just got it too. > N > August 16th, eh?  If I could travel in that direction I could make a KILLING > at the stock market!   -- . John Santoso Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Thu, 06 Sep 2001 23:23:12 -0400r' From: Jim Becker <jbecker@ui.urban.org>  Subject: Re: Huh? , Message-ID: <3B983DA0.86D4E84B@ui.urban.org>  ? Huh indeed! It looks like someone got careless with cutting andiC pasting from past announcements. Could someone forward me a copy of>. the faulty message (jbecker at ui.urban.org)?   2 I assume it was supposed to be an announcement of:- Boston Technology Day by Compaq and Encompassc Thursday, October 25th, 2001 a  D If so, the announcement presumably should have gone only to those in the Boston area.  6 See: http://www.encompassus.org/events/LPP/boston.html   --
 Jim Becker+ The Urban Institute (http://www.urban.org/)h' Encompass (http://www.encompassus.org/)P. ESILUG (http://encompasserve.org/lugs/esilug/)     John Santos wrote: > ) > Just received this about 2 minutes ago:f > & > Date: Wed, 5 Sep 2001 15:32:02 -0500% > From: Encompass <Encompass@SBA.COM>r% > To: "'john@egh.com'" <john@egh.com>e8 > Subject: Boston Technology Day by Compaq and Encompass >  > Dear John, > E > Mark your Calendars - Boston Technology Day by Compaq and Encompassh > * > Compaq Strategic Update on Alpha/Itanium/ > StorageWorks Current Offerings and Technologys" > SANs Technology & Customer Panel) > 512 Township Line Road, 3 Valley Squarer > Blue Bell, PAs > Thursday, August 16th, 2001  > 9:30 am - 4:00 pm  > G > Encompass, the evolution of the DECUS US Chapter, and Compaq ComputertM > Corporation cordially invite you to join us on Thursday, August 16th, for ad" > free all-day technical exchange. > E > * Rich Colarusso -- Compaq Strategic Directions (NDA form Required)-? > * Robb Macomber - StorageWorks Current Offerings & Technologyr# > * Brian Allison - SANs TechnologyuG > * SANs Customer Panel - 3 Encompass members discuss their experiencest? > * Compaq Demo center -- See the latest technologies in action  >  > [...]- >  > ------------------------ > ! > What's wrong with this picture?e > B > (P.S.  I checked the full headers... it was mailed today, hasn't2 > been sitting in some email limbo for 2-3 weeks.) >  > --
 > John Santosi > Evans Griffiths & Hart, Inc. > 781-861-0670 ext 539   ------------------------------   Date: 6 Sep 2001 17:37:50 -0700d4 From: gherbert@gw.retro.com (George William Herbert) Subject: Re: I hate Compaq' Message-ID: <9n94su$g3l$1@gw.retro.com>n  , Alexis Cousein  <al@brussels.sgi.com> wrote:H >(called HP, although I'm referring to it as Haitche-paq internally ;) )   Hewlett-Paqard.      -george william herberts gherbert@retro.com   ------------------------------  $ Date: Thu, 6 Sep 2001 19:26:01 -0700+ From: "Dennis O'Connor" <dmoc@primenet.com>- Subject: Re: I hate Compaq- Message-ID: <9n9b94$cis$1@nnrp3.phx.gblx.net>r  : "George William Herbert" <gherbert@gw.retro.com> wrote .... > Alexis Cousein  <al@brussels.sgi.com> wrote:J > >(called HP, although I'm referring to it as Haitche-paq internally ;) ) >o > Hewlett-Paqard.r  ! Jean-Luc's long lost brother. :-)u" (That should inspire a parody ...) --3 Dennis O'Connor                   dmoc@primenet.comt. Vanity Web Page http://www.primenet.com/~dmoc/   ------------------------------   Date: 6 Sep 2001 19:51:52 -0700n4 From: gherbert@gw.retro.com (George William Herbert) Subject: Re: I hate Compaq' Message-ID: <9n9co8$h1g$1@gw.retro.com>I  * Dennis O'Connor <dmoc@primenet.com> wrote:; >"George William Herbert" <gherbert@gw.retro.com> wrote ...t/ >> Alexis Cousein  <al@brussels.sgi.com> wrote:iK >> >(called HP, although I'm referring to it as Haitche-paq internally ;) )  >> >> Hewlett-Paqard. >i" >Jean-Luc's long lost brother. :-)# >(That should inspire a parody ...)u   Sales..... the final frontier.8 These are the voyages of the sales force "Merger-sized". It's five quarter mission: To seek out new market share,a
 New segments,H* And to boldly innovate in every direction.     -george william herbertg gherbert@retro.com   ------------------------------  % Date: Thu, 06 Sep 2001 22:41:11 -0600t* From: yyyc186@illegaltospam.mindspring.com Subject: Re: I hate Compaq; Message-ID: <3b985055$1$lllp186$mr2ice@nntp.mindspring.com>h  . In <3B96BEFB.B27682D6@fsi.net>, on 09/05/2001 A    at 07:10 PM, "David J. Dachtera" <djesys.nospam@fsi.net> said:,  , >yyyc186@illegaltospam.mindspring.com wrote: >> rF >> In <y4k7zkd75k.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>, on
 >> 08/31/2001v" >>    at 09:23 AM, Jan Vorbrueggen: >> <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> said: >> rI >> Just remember....IBM delivered the 1.4Gig Copper Stamped Alpha 2 years ! >> ago...it is just shipping now.e >> ,M >> And despite all of that they went with Intel...a company that is dead lastF/ >> in the world of chip fabrication technology.e  < >Where would you say they stand in terms of chip fabrication >infrastructure?  J They don't have any infrastructure with respect to the new technologies inG place at either IBM or AMD.  What they have is a large capacity to turns out very dated chips.k   -- i; ------------------------------------------------------------ yyyc186@mindspring.com; -----------------------------------------------------------    ------------------------------  # Date: Thu, 06 Sep 2001 23:43:38 GMTs& From: "Ken Farmer" <kfarmer@tru64.org>E Subject: IDG reporter mentions positive comments made by HP PR personO> Message-ID: <KSTl7.68013$xj.13498606@typhoon.southeast.rr.com>  F In the HP-Compaq forum on Tru64.org a reporter which wrote a report in6 InfoWorld, (Future uncertain for HP-Compaq customers",F http://www.infoworld.com/articles/hn/xml/01/09/05/010905hnhpusers.xml) mentions  L Q. How will the new HP work through having five different platforms and five different Oses?    A.A  Both companies are moving more aggressively to IA-64 and IA-32.pJ  Through the convergence of the best of both HP-UX and Tru64 UNIX we will/ deliver the industry's leading enterprise UNIX. 3  HP-UX would be extended to support Alpha systems.cK  We are committed to the plan laid out for Alpha when Compaq announced itsnE agreement with Intel to standardize its 64-bit servers on the Itaniumo processor family.d5  MPE will continue to be managed as it is currently.SK  Compaq has made a long-term commitment to its important OpenVMS customers16 and will continue to deliver on its committed roadmap.  ! Here is her comment in the forum:g5 (http://www2.tru64.org/phorum/read.php?f=8&i=47&t=32)      Ken      -- Ken Farmer, kfarmer@tru64.orgi Tru64.org, http://www.tru64.org  Tru64.org Newsletter:e< http://www2.tru64.org/pages.php?page=Newsletter-Registration   ------------------------------  % Date: Thu, 06 Sep 2001 21:46:38 -0400c- From: JF Mezei <jfmezei.spamnot@videotron.ca>nI Subject: Re: IDG reporter mentions positive comments made by HP PR personn, Message-ID: <3B9826FB.22D6C493@videotron.ca>   Ken Farmer wrote:tM >  Compaq has made a long-term commitment to its important OpenVMS customers 8 > and will continue to deliver on its committed roadmap.  J Makes me wonder if those few important customers worthy of getting a visitH from Compaq on the day Alpha died were told that Compaq would donate its% assets to HP and then cease to exist.-   ------------------------------  $ Date: Thu, 6 Sep 2001 23:13:01 -0400' From: "Bill Todd" <billtodd@foo.mv.com> I Subject: Re: IDG reporter mentions positive comments made by HP PR person-( Message-ID: <9n9du9$35f$1@pyrite.mv.net>  L Well, the 'positiveness' of some of the below is at least subject to debate.  1 "Ken Farmer" <kfarmer@tru64.org> wrote in message@8 news:KSTl7.68013$xj.13498606@typhoon.southeast.rr.com...H > In the HP-Compaq forum on Tru64.org a reporter which wrote a report in8 > InfoWorld, (Future uncertain for HP-Compaq customers",H > http://www.infoworld.com/articles/hn/xml/01/09/05/010905hnhpusers.xml)
 > mentions >bI > Q. How will the new HP work through having five different platforms anda five > different Oses?, >a > A.C >  Both companies are moving more aggressively to IA-64 and IA-32.   I Sorry:  performance regression (at least in the case of the Alpha to IA64 I move, and for that matter in the case of the PA-RISC to IA64 move) is note	 positive.6  L >  Through the convergence of the best of both HP-UX and Tru64 UNIX we will1 > deliver the industry's leading enterprise UNIX.y  J CEO/marketing drivel for saying that one Unix will be the result, and thatI at best one of the two sets of customers will not be perturbed (the otherlD *will* be perturbed, by the change in 'endianness' if nothing else).  5 >  HP-UX would be extended to support Alpha systems.   H Right.  Now, does anyone really think that Hpaq is going to aggressivelyK support HP-UX, *and* Linux, *and* Tru64 on both hardware platforms?  Didn'tv	 think so.j  I >  We are committed to the plan laid out for Alpha when Compaq announceda itseG > agreement with Intel to standardize its 64-bit servers on the Itaniuml > processor family.e  F Let's hope HP treats 'commitments' a little more seriously than Compaq does...f  C >  Compaq has made a long-term commitment to its important OpenVMS 	 customers 8 > and will continue to deliver on its committed roadmap.  . ... and makes its new acquisition do the same.  7 >  MPE will continue to be managed as it is currently.h  H That's positive for existing HP customers, but kind of uninteresting for this audience.   - bill   ------------------------------  $ Date: Fri, 7 Sep 2001 00:32:19 -0400  From: John Santos <JOHN@egh.com>I Subject: Re: IDG reporter mentions positive comments made by HP PR person,6 Message-ID: <1010907002441.64342B-100000@Ives.egh.com>  4 Here's the quote I was refering to in my other post:  % On Thu, 6 Sep 2001, Ken Farmer wrote:e  H > In the HP-Compaq forum on Tru64.org a reporter which wrote a report in8 > InfoWorld, (Future uncertain for HP-Compaq customers",H > http://www.infoworld.com/articles/hn/xml/01/09/05/010905hnhpusers.xml)
 > mentions >=20L > Q. How will the new HP work through having five different platforms and f= ive  > different Oses?i >=20 > A.E > =A7 Both companies are moving more aggressively to IA-64 and IA-32.mL > =A7 Through the convergence of the best of both HP-UX and Tru64 UNIX we w= ill 1 > deliver the industry's leading enterprise UNIX.d7 > =A7 HP-UX would be extended to support Alpha systems.t,     ^^^^^                              ^^^^^  , I just assumed it was a typo or misquote ;-)  L > =A7 We are committed to the plan laid out for Alpha when Compaq announced=  itsG > agreement with Intel to standardize its 64-bit servers on the Itanium  > processor family.k9 > =A7 MPE will continue to be managed as it is currently.cL > =A7 Compaq has made a long-term commitment to its important OpenVMS custo= mers8 > and will continue to deliver on its committed roadmap. >=20& > Here is her comment in the forum:=20? >(http://www2.tru64.org/phorum/read.php?f=3D8&i=3D47&t=3D32)=20b   --=20t John Santosa Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  # Date: Fri, 07 Sep 2001 03:20:54 GMTe& From: "Ken Farmer" <kfarmer@tru64.org>S Subject: Re: IDG reporter mentions some "interesting" comments made by HP PR persont> Message-ID: <q2Xl7.68031$xj.13590188@typhoon.southeast.rr.com>  = Maybe I should have said "interesting" instead of "positive."e   Ken    -- Ken Farmer, kfarmer@tru64.orgC Tru64.org, http://www.tru64.org  Tru64.org Newsletter:e< http://www2.tru64.org/pages.php?page=Newsletter-Registration      2 "Bill Todd" <billtodd@foo.mv.com> wrote in message" news:9n9du9$35f$1@pyrite.mv.net...F > Well, the 'positiveness' of some of the below is at least subject to debate.d > 3 > "Ken Farmer" <kfarmer@tru64.org> wrote in messaget: > news:KSTl7.68013$xj.13498606@typhoon.southeast.rr.com...J > > In the HP-Compaq forum on Tru64.org a reporter which wrote a report in: > > InfoWorld, (Future uncertain for HP-Compaq customers",J > > http://www.infoworld.com/articles/hn/xml/01/09/05/010905hnhpusers.xml) > > mentions > >bK > > Q. How will the new HP work through having five different platforms ande > five > > different Oses?f > >m > > A.E > >  Both companies are moving more aggressively to IA-64 and IA-32.. > K > Sorry:  performance regression (at least in the case of the Alpha to IA64 K > move, and for that matter in the case of the PA-RISC to IA64 move) is nota > positive.o > I > >  Through the convergence of the best of both HP-UX and Tru64 UNIX weg will3 > > deliver the industry's leading enterprise UNIX.d >tL > CEO/marketing drivel for saying that one Unix will be the result, and thatK > at best one of the two sets of customers will not be perturbed (the othertF > *will* be perturbed, by the change in 'endianness' if nothing else). >e7 > >  HP-UX would be extended to support Alpha systems.c > J > Right.  Now, does anyone really think that Hpaq is going to aggressivelyE > support HP-UX, *and* Linux, *and* Tru64 on both hardware platforms?  Didn't > think so.  >hK > >  We are committed to the plan laid out for Alpha when Compaq announcedb > itsbI > > agreement with Intel to standardize its 64-bit servers on the Itaniumy > > processor family.  > H > Let's hope HP treats 'commitments' a little more seriously than Compaq	 > does...n >cE > >  Compaq has made a long-term commitment to its important OpenVMSl > customersp: > > and will continue to deliver on its committed roadmap. >n0 > ... and makes its new acquisition do the same. >i9 > >  MPE will continue to be managed as it is currently.  >sJ > That's positive for existing HP customers, but kind of uninteresting for > this audience. >r > - bill >m >  >s   ------------------------------  % Date: Thu, 06 Sep 2001 12:13:53 -0700'! From: Don Sykes <don@alphase.com>C4 Subject: Re: INQUIRE/NODISPLAY or equivalent in DCL?+ Message-ID: <3B97CAF1.711D0DDB@alphase.com>e   Hoff Hoffman wrote:i > Q > In article <3B96539B.99C77F5C@alphase.com>, Don Sykes <don@alphase.com> writes:e5 > :This is what I use as a way to capture a password:. > :  > .. > :$ set term/noecho+ > :$ inquiry       query   "Enter password"  > :$ set term/echo > .. > B >   INQUIRE is a deeply powerful and often mysterious command, andE >   particularly a command that should only be used by those that are 7 >   well-versed in the magicks of the command language.e > J >   Use of INQUIRE is explicitly prohibited in captive command procedures. > L >   Put another way, the approach that is suggested above is quite insecure. > E >   I would strongly encourage the use of the existing OpenVMS accessuI >   control and authentication mechanisms, as various direct and indirectsE >   attacks can and are regularly found against tools that prompt for-  >   passwords.  (eg: See above.) >   G Everything isn't always so crucial. I only use this method to capture atG password when someone is watching over my sholder, so instead of using,n e.g.:   7 	copy Node1"myname MyActualPassword"::dev:[dir]file  []o  
 I can use  	capture via inquire procedure2 	copy Node1"myname ''password'"::dev:[dir]file  [] 	del/sym passwordt  D It may not be completely safe, but its better than just typing it in clear text.t   Dons   ------------------------------  $ Date: Thu, 6 Sep 2001 20:23:26 -0400; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>o4 Subject: Re: INQUIRE/NODISPLAY or equivalent in DCL?$ Message-ID: <3b9813d3$1@news.si.com>  H >Everything isn't always so crucial. I only use this method to capture aH >password when someone is watching over my sholder, so instead of using, >e.g.: >t7 >copy Node1"myname MyActualPassword"::dev:[dir]file  []n   I use:   @dir:netlogname-   Logical name: other- Node name: vaxa- Username: tillmanh	 Password:0   $ copy other::dev:[dir]file []   where NETLOGNAME.COM contains:   $       write sys$output ""19 $       read/prompt="Logical name: " sys$command log_namea7 $       read/prompt="Node name: " sys$command node_namee5 $       read/prompt="Username: " sys$command usernamer $       set term/noechov5 $       read/prompt="Password: " sys$command password: $       set term/echoi+ $       loc = 'f$locate ( "::", node_name )a% $       len = 'f$length ( node_name )LJ $       if loc .ne. len then node_name := 'f$extract ( 0, loc, node_name )D $       define 'log_name "''node_name'""''username' ''password'""::" $       write sys$output ""0   -- m  A Brian Tillman                   Internet: tillman_brian at si.com A Smiths Aerospace                          tillman at swdev.si.comn= 3290 Patterson Ave. SE, MS      Addresses modified to preventt< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  # Date: Thu, 06 Sep 2001 18:11:05 GMTrB From: Simon Clubley <simon_clubley@remove_me.excite.com-Earth.UFP>L Subject: Looking ahead: What happens if the HP-Compaq merger falls through ?4 Message-ID: <Z_Ol7.6823$4z.28697@www.newsranger.com>  H [I am a technical person and not a business person, so I am not familiar% with the history of merger failures.]l  L Given the negative reaction to the merger, and the falling share price, I amH wondering what is likely to happen to Compaq and VMS if the merger falls	 through ?M  I Is Compaq likely to survive, but in another form, or is it likely to comeb, completely apart and be sold off in pieces ?  = In the history of merger failures what has tended to happen ?p  H Also, does history have anything to say about how likely it is that this$ merger is actually going to happen ?   Simon.   -- r; Simon Clubley, simon_clubley@remove_me.excite.com-Earth.UFPlK In the task of removing Microsoft from the marketplace, I have discovered a,E truly remarkable plan, but this signature is too small to contain it.t   ------------------------------  * Date: Thu, 6 Sep 2001 12:00:53 -0700 (PDT). From: Fabio Cardoso <fabiopenvms@yahoo.com.br>P Subject: Re: Looking ahead: What happens if the HP-Compaq merger falls through ?@ Message-ID: <20010906190053.15465.qmail@web20202.mail.yahoo.com>   Well  4 Compaq and HP will stay as concurrent companies I=205 believe., but..... I think they will become much morea3 closer to each other. making agreements, etc ...=20-  4 I am not a business person too ! I have decency !=20   REgards    FC=20c   --- Simon Clubleyr5 <simon_clubley@remove_me.excite.com-Earth.UFP> wrote:e5 > [I am a technical person and not a business person,  > so I am not familiar' > with the history of merger failures.]- >=204 > Given the negative reaction to the merger, and the > falling share price, I amG6 > wondering what is likely to happen to Compaq and VMS > if the merger fallsw > through ?  >=206 > Is Compaq likely to survive, but in another form, or > is it likely to come. > completely apart and be sold off in pieces ? >=206 > In the history of merger failures what has tended to
 > happen ? >=203 > Also, does history have anything to say about howr > likely it is that this& > merger is actually going to happen ? >=20 > Simon. >=20 > --=20@ > Simon Clubley,. > simon_clubley@remove_me.excite.com-Earth.UFP, > In the task of removing Microsoft from the" > marketplace, I have discovered a2 > truly remarkable plan, but this signature is too > small to contain it.     =3D=3D=3D=3D=3DlL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D  F=E1bio dos Santos Cardoso OpenVMS System Manager Rio de Janeiro - Brazilo fabiopenvms@yahoo.com.brL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D   2 __________________________________________________ Do You Yahoo!?L Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger=   http://im.yahoo.comw   ------------------------------  % Date: Thu, 06 Sep 2001 16:31:43 -0400>- From: JF Mezei <jfmezei.spamnot@videotron.ca>aP Subject: Re: Looking ahead: What happens if the HP-Compaq merger falls through ?, Message-ID: <3B97DD26.329E4B0C@videotron.ca>   Simon Clubley wrote:N > Given the negative reaction to the merger, and the falling share price, I amJ > wondering what is likely to happen to Compaq and VMS if the merger falls > through ?i  N 1- Can the merger actually fall thourgh ? From my understanding, it is a stockK swap deal where Compaq shareholders will be given X number of HP shares for@N each Compaq share they have. So it would seem that shareholders would not haveM the choice of not selling the shares as would be the case in a real takeover./  ! Is this a correct understanding ?a  M 2-Now, if shareholders do revolt and the Boards decide to kill the deal, thenrK a possibility would be for a 3rd party to make an offer for Compaq's shares>L which would be tandamount of a fire sale. They'd buy what is left of Compaq.6 Some large Japanese outfit would be a logical company.   ------------------------------  % Date: Thu, 06 Sep 2001 22:34:18 +0100i+ From: "antonio.carlini" <arcarlini@iee.org>eP Subject: Re: Looking ahead: What happens if the HP-Compaq merger falls through ?' Message-ID: <3B97EBDA.61FD3398@iee.org>e   JF Mezei wrote: P > 1- Can the merger actually fall thourgh ? From my understanding, it is a stock    Surely the US or Euro monopolies" people could put the kibosh on it?  ' There must be lots of other things thato# could either kill it or make one ori  other of the boards want to pull out (HP's current stock plummetc leaps to mind ...)   Antonio-   -- -   ----------------- Antonio Carlini             arcarlini@iee.org-   ------------------------------  % Date: Thu, 06 Sep 2001 18:53:49 -0000@ From: sword7@speakeasy.org7 Subject: MicroVAX II (KA630) - RXCS,RXDB,TXCS, and TXDBe/ Message-ID: <tpfhhtkf0cvl35@corp.supernews.com>a   Hello folks (or Jeff):  D Good news! I implemented some and fixed some bugs.  I encountered a E few big problems during test #4, etc.  In test #4, I learned and had t> implemented the prefetch instruction buffer.  It will not work@ without the prefetch instruction buffer.  When it turned memory B management on, next instruction crashed.  When it was done, a pageD is not affected until any branch instruction that cause the prefetchK instruction flush.  Also it resulted much faster!  On 450 Mhz Pentium III, N it is estimated VUP 1.3.  H Test was counted down to 3.  During test #7, I got welcome messsage and I starting 7 to count down on my screen.  During test #3,  it crashed.   I  E looked into my debug log file and found out that some "undocumented"  K information in console terminal registers.  It is waiting for RXCS<11> bit tG forever.  That is not docemented in my VAX reference handbook, etc.  I oJ believe that it is one of KA630's implementations.  Primary boot (console D program) almost was finished before OpenVMS boot started (secondary C boot ater >>> prompt).  When test #3 is passed, >>> prompt will be r7 printed.  Test #2 to #0 are secondary boot for OpenVMS.t  H Does anyone have complete console terminal registers for KA630 processor (MicroVAX II)?  
 Thank you!   -- Tim Stark   -- n, Timothy Stark	<><	Inet: sword7@speakeasy.orgJ --------------------------------------------------------------------------F "For God so loved the world, that he gave his only begotten Son, that H whosoever believeth in him should not perish, but have everlasting life.. Amen." -- John 3:16 (King James Version Bible)   ------------------------------  # Date: Thu, 06 Sep 2001 23:25:17 GMTa+ From: Jeff Campbell <jcampbell@ins-msi.com> ; Subject: Re: MicroVAX II (KA630) - RXCS,RXDB,TXCS, and TXDB-+ Message-ID: <3B97FE5F.FCEAF332@ins-msi.com>-   sword7@speakeasy.org wrote:d >  > Hello folks (or Jeff): > E > Good news! I implemented some and fixed some bugs.  I encountered a9F > few big problems during test #4, etc.  In test #4, I learned and had@ > implemented the prefetch instruction buffer.  It will not workA > without the prefetch instruction buffer.  When it turned memoryaD > management on, next instruction crashed.  When it was done, a pageF > is not affected until any branch instruction that cause the prefetchL > instruction flush.  Also it resulted much faster!  On 450 Mhz Pentium III, > it is estimated VUP 1.3. > I > Test was counted down to 3.  During test #7, I got welcome messsage andnJ > starting 7 to count down on my screen.  During test #3,  it crashed.   IF > looked into my debug log file and found out that some "undocumented"L > information in console terminal registers.  It is waiting for RXCS<11> bitH > forever.  That is not docemented in my VAX reference handbook, etc.  IK > believe that it is one of KA630's implementations.  Primary boot (consolesE > program) almost was finished before OpenVMS boot started (secondaryeD > boot ater >>> prompt).  When test #3 is passed, >>> prompt will be9 > printed.  Test #2 to #0 are secondary boot for OpenVMS.  > J > Does anyone have complete console terminal registers for KA630 processor > (MicroVAX II)?  B Here's the layout for the Console Receive Control Status Register:  ,    <31:12>             unused, read as zeros  C    <11:11>  RCV ACT  - Receive Active. This read-only bit is set atlF                        the center of the start bit of the serial inputB                        data, and is cleared at the expected centerG                        (per DLART timing) of the stop bit at the end of C                        the serial data. RX DONE is set one bit time ,                        after RCV ACT clears.  ,    <10:08>             unused, read as zeros  D    <07:07>  RX  DONE - Receiver Done. This read-only bit is set whenC                        an entire character has been received and isuD                        ready to be read from the RBUF register. This@                        bit is automatically cleared when RBUF isC                        read. It is also cleared by power-up, by theoC                        negation of DC OK, and by writes to the BIR.1  A    <06:06>  RX  IE   - Receiver Interrupt Enable. This R/W bit is A                        cleared by power-up, by the negation of DCeC                        OK, and by writes to the BIR. If RX DONE andnA                        RX IE are both set, a program interrupt isi!                        requested.0  ,    <05:00>             unused, read as zeros  B Given the description of RCV ACT, I am surprised that the firmwareF would be looking for it, since it will go away as soon as the stop bitC for the current character is half received. Since RX DONE will then " set one bit time later why bother?  8 Here's the Console Receiver Data Buffer Register layout:  +    <31:16>            unused, read as zeroso  E    <15:15>  ERR     - Error. This read-only bit is set if RBUF bit 14tD                       or 13 is set. ERR is clear if these 2 bits are?                       clear. This bit cannot generate a programn
 interrupt.  C    <14:14>  OVR ERR - Overrun Error. This read-only bit is set if ak@                       previously received character was not readH                       before being overwritten by the present character.  E    <13:13>  FRM ERR - Framing Error. This read-only bit is set if thee>                       present character has no valid stop bit.  *    <12:12>            unused, read as zero  E    <11:11>  RCV BRK - Receive Break. This read-only bit is set at the-F                       end of a received character for which the serialH                       data input remained in the SPACE condition for allE                       eleven bit times. RCV BRK the remains set until1?                       the serial data input returns to the MARKdD                       condition. RCV BRK is also cleared by power-up3                       and by the negation of DC OK.6  *    <10:08>            unused, read as zero  >    <07:00>            Received Data Bits. These read-only bits:                       contain the last received character.   >  > Thank you! >  > -- Tim Stark >  > --4 > Timothy Stark   <><     Inet: sword7@speakeasy.orgL > --------------------------------------------------------------------------G > "For God so loved the world, that he gave his only begotten Son, thatwJ > whosoever believeth in him should not perish, but have everlasting life.0 > Amen." -- John 3:16 (King James Version Bible)   HTH,  
 Jeff Campbellr n8wxs@arrl.net   ------------------------------  # Date: Thu, 06 Sep 2001 23:47:38 GMT + From: Jeff Campbell <jcampbell@ins-msi.com> ; Subject: Re: MicroVAX II (KA630) - RXCS,RXDB,TXCS, and TXDBl+ Message-ID: <3B98039C.71D47735@ins-msi.com>a  @ Sorry to follow-up on my own answer but I forgot some stuff. 8-)   Jeff Campbell wrote: >  > sword7@speakeasy.org wrote:) > >o > > Hello folks (or Jeff): > >gG > > Good news! I implemented some and fixed some bugs.  I encountered a H > > few big problems during test #4, etc.  In test #4, I learned and hadB > > implemented the prefetch instruction buffer.  It will not workC > > without the prefetch instruction buffer.  When it turned memory F > > management on, next instruction crashed.  When it was done, a pageH > > is not affected until any branch instruction that cause the prefetchN > > instruction flush.  Also it resulted much faster!  On 450 Mhz Pentium III, > > it is estimated VUP 1.3. > > K > > Test was counted down to 3.  During test #7, I got welcome messsage and L > > starting 7 to count down on my screen.  During test #3,  it crashed.   IH > > looked into my debug log file and found out that some "undocumented"N > > information in console terminal registers.  It is waiting for RXCS<11> bitJ > > forever.  That is not docemented in my VAX reference handbook, etc.  IM > > believe that it is one of KA630's implementations.  Primary boot (consoleoG > > program) almost was finished before OpenVMS boot started (secondaryPF > > boot ater >>> prompt).  When test #3 is passed, >>> prompt will be; > > printed.  Test #2 to #0 are secondary boot for OpenVMS.  > >aL > > Does anyone have complete console terminal registers for KA630 processor > > (MicroVAX II)? > D > Here's the layout for the Console Receive Control Status Register: > . >    <31:12>             unused, read as zeros > E >    <11:11>  RCV ACT  - Receive Active. This read-only bit is set at9H >                        the center of the start bit of the serial inputD >                        data, and is cleared at the expected centerI >                        (per DLART timing) of the stop bit at the end of.E >                        the serial data. RX DONE is set one bit timed. >                        after RCV ACT clears. > . >    <10:08>             unused, read as zeros > F >    <07:07>  RX  DONE - Receiver Done. This read-only bit is set whenE >                        an entire character has been received and iscF >                        ready to be read from the RBUF register. ThisB >                        bit is automatically cleared when RBUF isE >                        read. It is also cleared by power-up, by theaE >                        negation of DC OK, and by writes to the BIR.. > C >    <06:06>  RX  IE   - Receiver Interrupt Enable. This R/W bit istC >                        cleared by power-up, by the negation of DChE >                        OK, and by writes to the BIR. If RX DONE andwC >                        RX IE are both set, a program interrupt ise# >                        requested.v > . >    <05:00>             unused, read as zeros > D > Given the description of RCV ACT, I am surprised that the firmwareH > would be looking for it, since it will go away as soon as the stop bitE > for the current character is half received. Since RX DONE will thenc$ > set one bit time later why bother? > : > Here's the Console Receiver Data Buffer Register layout: > - >    <31:16>            unused, read as zerosp > G >    <15:15>  ERR     - Error. This read-only bit is set if RBUF bit 14nF >                       or 13 is set. ERR is clear if these 2 bits areA >                       clear. This bit cannot generate a programv > interrupt. > E >    <14:14>  OVR ERR - Overrun Error. This read-only bit is set if aEB >                       previously received character was not readJ >                       before being overwritten by the present character. > G >    <13:13>  FRM ERR - Framing Error. This read-only bit is set if the @ >                       present character has no valid stop bit. > , >    <12:12>            unused, read as zero > G >    <11:11>  RCV BRK - Receive Break. This read-only bit is set at the H >                       end of a received character for which the serialJ >                       data input remained in the SPACE condition for allG >                       eleven bit times. RCV BRK the remains set untiltA >                       the serial data input returns to the MARK F >                       condition. RCV BRK is also cleared by power-up5 >                       and by the negation of DC OK.M > , >    <10:08>            unused, read as zero > @ >    <07:00>            Received Data Bits. These read-only bits< >                       contain the last received character. >  > >y > > Thank you! > >- > > -- Tim Stark > >o > > --6 > > Timothy Stark   <><     Inet: sword7@speakeasy.orgN > > --------------------------------------------------------------------------I > > "For God so loved the world, that he gave his only begotten Son, thatgL > > whosoever believeth in him should not perish, but have everlasting life.2 > > Amen." -- John 3:16 (King James Version Bible) >  > HTH, >  > Jeff Campbellf > n8wxs@arrl.net  < The Console Transmitter Control Status Register is laid out:  -    <31:08>              unused, read as zeros   F    <07:07>   TX  RDY  - Transmitter Ready. This read-only bit is clearA                         when the XBUF is loaded and sets when thetC                         XBUF can send another character. XMT RDY isoB                         set by power-up, negation of DC OK, and by*                         writes to the BIR.  E    <06:06>   TX  IE   - Transmitter Interrupt Enable. This R/W bit issF                         cleared by power-up, negation of DC OK, and byG                         writes to the BIR. If both TX RDY and TX IE areb>                         set, a program interrupt is requested.  -    <05:03>              unused, read as zeros.  G    <02:02>   MAINT    - Maintenance. This R/W bit is used to facilitatecG                         a maintenance self-test. When MAINT is set, thehE                         external serial input is disconnected and thetB                         serial output is used as the serial input.D                         This bit is cleared by power-up, negation of8                         DC OK, and by writes to the BIR.  ,    <01:01>              unused, read as zero  E    <00:00>   XMIT BRK - Transmit Break. When this R/W bit is set, the,G                         serial output is forced to the SPACE condition.pD                         XMIT BRK is cleared by power-up, negation of8                         DC OK, and by writes to the BIR.    < The Console Transmitter Data Buffer Register is laid out as:      <31:08>              unused  0    <07:00>              transmit character bits.  " The TXDB is a write-only register.   Jeff   ------------------------------  $ Date: Thu, 6 Sep 2001 23:23:56 -0400  From: John Santos <JOHN@egh.com>; Subject: Re: MicroVAX II (KA630) - RXCS,RXDB,TXCS, and TXDBn6 Message-ID: <1010906232206.64342D-100000@Ives.egh.com>  ( On Thu, 6 Sep 2001, Jeff Campbell wrote:  B > Sorry to follow-up on my own answer but I forgot some stuff. 8-) >  > Jeff Campbell wrote: > >  > > sword7@speakeasy.org wrote:3 > > >=  I >    <02:02>   MAINT    - Maintenance. This R/W bit is used to facilitateiI >                         a maintenance self-test. When MAINT is set, theDG >                         external serial input is disconnected and the_D >                         serial output is used as the serial input.F >                         This bit is cleared by power-up, negation of: >                         DC OK, and by writes to the BIR.   Tim -4  ? Could it be that the test sent a character in MAINT mode and isR0 waiting for it to appear in the receiver buffer?  
 Good luck!   --   John Santos3 Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  $ Date: Thu, 6 Sep 2001 21:44:08 -0400  From: John Santos <JOHN@egh.com>( Subject: Re: My VMS Wish List (features)6 Message-ID: <1010906212841.64342A-100000@Ives.egh.com>  , On Wed, 5 Sep 2001, David J. Dachtera wrote:   > Tim Llewellyn wrote: > > * > > "Brian Schenkenberger, VAXman-" wrote: > > H > > > I don't think that the underlying mechanism need be a mailbox (MB)G > > > or a pipe (MP) device.  I think that what would appease those re-aI > > > questing this would be some *supported* mechanism for DCL interpro-  > > > cess communication.e > > >l > > % > > I thought that was called DECNet.a > 7 > ...and if you don't have DECnet installed, then what?    Install it?  ;-)  > Seriously, ISTR that you don't need a license to use DECnet to< connect to node 0 (i.e. yourself).  Until approx. V6.2-V7.0,= DECnet was *always* installed.  (The license just enabled it,o> i.e. it was a SIP like clustering.)  Since then, it has become1 optional since you have a choice of Ph 4 or Ph 5.e  : DECnet licenses are now included in practically everything: (NAS, EIP (or whatever the replacement for NAS is called),9 CSA, hobbyist LP set...), so lack of a license would onlyp< apply to a very old, non-hobbyist system that has never been& DECneted, and so never had a license.)  6 (I couldn't find anything about this in the FAQ, but I9 think the standard method for obtaining a session log has-7 always been "set host/log 0", which was claimed to workn even without a DECnet license.)-   -- - John Santosh Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  $ Date: Thu, 6 Sep 2001 16:39:01 -0500* From: WILLIAM WEBB <WWEBB1@email.usps.gov>E Subject: RE: OT: Bush administration drops effort to break up Microsob- Message-ID: <0033000034416318000002L082*@MHS>   ! =0AHow quickly Winsock is forgot.a   WWWebb   > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNETh, > Sent: Thursday, September 06, 2001 3:54 PMD > To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNETH > Subject: RE: OT: Bush administration drops effort to break up Microso=   >  >s- > In article <9n8ind$4j3$1@bob.news.rcn.net>,e3 >     "John Saunders" <jws@ma.ultranet.com> writes:u >d6 > > "Alan Greig" <a.greig@virgin.net> wrote in message( > > news:3B97C8A9.71A79CF1@virgin.net... > >> > >> > >> John Saunders wrote:k > >>9 > >> > "It seems to me that the existence of a very large  > number of personal4 > >> > computers with modems, TCP/IP and PPP, made a > substantial difference.o > >> > > >>7 > >> That was due to the US government allowing privatee > connections to the> > >> Internet somewhere around 1990 or so.  Nothing to do with > Microsoft. > >a= > > If Microsoft hadn't shipped a with Windows a TCP/IP stackd > with PPP and a> > > dialer, which devices would have connected hosts privately > connecting to them
 > > Internet?e >nH >    Presumably those same devices, using a TCP/IP stack from one of th= ekH > several vendors who sold them for Windows before Microsoft decided to=   > bundle it in with Win95. >-? >    Granted having the stack built in at no ( ie hidden ) cost 
 > sped up theeH > adoption, but I think if MS hadn't done this you would have seen ISPs=  D > delivering startup kits with someone elses IP stack bundled in andC > simple set-up procedures (in fact some did this back when Win 3.x  > was still widely in use).m >c: >    Your comment is much like saying "if Microsoft hadn't > shipped a browser38 > with Windows what would people use to surf the net". I > believe that at one ; > time Netscape thought they had the answer to that one :-)e >=   ------------------------------   Date: 6 Sep 2001 18:57:32 GMTe1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)hG Subject: Re: OT: Bush administration drops effort to break up Microsoftn, Message-ID: <9n8gus$1gpl$1@info.cs.uofs.edu>  J In article <Pine.LNX.4.33.0109061235001.11090-100000@malacandra.localnet>,3  "P. Thompson" <thompson-nospam@new.rr.com> writes:  |> |> o: |> BITNET died out before M$ had any internet to speak of.  B BITNET died!!  No wonder the lights on the modem stopped blinking.   bill   -- IJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   X   ------------------------------  % Date: Thu, 06 Sep 2001 20:04:09 +0100,% From: Alan Greig <a.greig@virgin.net>AG Subject: Re: OT: Bush administration drops effort to break up Microsofti* Message-ID: <3B97C8A9.71A79CF1@virgin.net>   John Saunders wrote:  G > "It seems to me that the existence of a very large number of personalrG > computers with modems, TCP/IP and PPP, made a substantial difference.e >n  E That was due to the US government allowing private connections to theoD Internet somewhere around 1990 or so.  Nothing to do with Microsoft.       > -- > John Saunders  > jws@ma.ultranet.comc   --
 Alan Greig   ------------------------------  $ Date: Thu, 6 Sep 2001 15:27:31 -0400+ From: "John Saunders" <jws@ma.ultranet.com> G Subject: Re: OT: Bush administration drops effort to break up Microsoft + Message-ID: <9n8ind$4j3$1@bob.news.rcn.net>   2 "Alan Greig" <a.greig@virgin.net> wrote in message$ news:3B97C8A9.71A79CF1@virgin.net... >t >R > John Saunders wrote: >>I > > "It seems to me that the existence of a very large number of personal I > > computers with modems, TCP/IP and PPP, made a substantial difference.h > >e >eG > That was due to the US government allowing private connections to theiF > Internet somewhere around 1990 or so.  Nothing to do with Microsoft.  H If Microsoft hadn't shipped a with Windows a TCP/IP stack with PPP and aL dialer, which devices would have connected hosts privately connecting to the	 Internet?E --
 John Saundersr jws@ma.ultranet.comb   ------------------------------   Date: 6 Sep 2001 12:40:38 -0700f1 From: nothome@spammers.are.scum (Malcolm Dunnett)hG Subject: Re: OT: Bush administration drops effort to break up Microsoftr, Message-ID: <k5BqKwGEQhp3@malvm5.mala.bc.ca>  , In article <9n8ind$4j3$1@bob.news.rcn.net>, 1     "John Saunders" <jws@ma.ultranet.com> writes:r  4 > "Alan Greig" <a.greig@virgin.net> wrote in message& > news:3B97C8A9.71A79CF1@virgin.net... >> >> >> John Saunders wrote:l >>J >> > "It seems to me that the existence of a very large number of personalJ >> > computers with modems, TCP/IP and PPP, made a substantial difference. >> > >>H >> That was due to the US government allowing private connections to theG >> Internet somewhere around 1990 or so.  Nothing to do with Microsoft.  > J > If Microsoft hadn't shipped a with Windows a TCP/IP stack with PPP and aN > dialer, which devices would have connected hosts privately connecting to the > Internet?   F    Presumably those same devices, using a TCP/IP stack from one of theE several vendors who sold them for Windows before Microsoft decided to  bundle it in with Win95.  I    Granted having the stack built in at no ( ie hidden ) cost sped up thevE adoption, but I think if MS hadn't done this you would have seen ISPs1B delivering startup kits with someone elses IP stack bundled in andA simple set-up procedures (in fact some did this back when Win 3.x  was still widely in use).i  J    Your comment is much like saying "if Microsoft hadn't shipped a browserJ with Windows what would people use to surf the net". I believe that at one9 time Netscape thought they had the answer to that one :-)o   ------------------------------  % Date: Thu, 06 Sep 2001 20:56:41 +0100g% From: Alan Greig <a.greig@virgin.net> G Subject: Re: OT: Bush administration drops effort to break up Microsoft * Message-ID: <3B97D4F8.BCC4DE3F@virgin.net>   John Saunders wrote:  J > If Microsoft hadn't shipped a with Windows a TCP/IP stack with PPP and aN > dialer, which devices would have connected hosts privately connecting to the > Internet?-  L There were PC IP stacks supporting dialup SLIP and PPP available long beforeM Microsoft shipped one. Have you heard of Winsock for instance? It was Winsockg< that most commonly connected earlier Windows PCs to the net.  M In the UK when one of the world's first commercial public access dial-up ISPshP (demon) went online users of Macs, Ataris and various other home systems all had3 suitable software to connect as well as Wintel PCs.l  N Dial-up slip access from home computers was common in universities long before% deregulation allowed the current use.f   >b > -- > John Saunders7 > jws@ma.ultranet.com    --
 Alan Greig   ------------------------------  % Date: Thu, 06 Sep 2001 21:02:11 +0100.% From: Alan Greig <a.greig@virgin.net>sG Subject: Re: OT: Bush administration drops effort to break up Microsoft * Message-ID: <3B97D643.275DC8C6@virgin.net>   Alan Greig wrote:r   > John Saunders wrote: >hL > > If Microsoft hadn't shipped a with Windows a TCP/IP stack with PPP and aP > > dialer, which devices would have connected hosts privately connecting to the
 > > Internet?t >tN > There were PC IP stacks supporting dialup SLIP and PPP available long beforeO > Microsoft shipped one. Have you heard of Winsock for instance? It was Winsockl> > that most commonly connected earlier Windows PCs to the net. >i  3 Trumpet Winsock, I should have said, to be accuratel   >lO > In the UK when one of the world's first commercial public access dial-up ISPsiR > (demon) went online users of Macs, Ataris and various other home systems all had5 > suitable software to connect as well as Wintel PCs.o >oP > Dial-up slip access from home computers was common in universities long before' > deregulation allowed the current use.P >  > >t > > -- > > John Saunderss > > jws@ma.ultranet.comt >l > -- > Alan Greig   --
 Alan Greig   ------------------------------   Date: 6 Sep 2001 15:26:28 -0500s- From: Kilgallen@SpamCop.net (Larry Kilgallen) G Subject: Re: OT: Bush administration drops effort to break up Microsoftt3 Message-ID: <CiUDvwzrID$$@eisner.encompasserve.org>r  Y In article <9n8ind$4j3$1@bob.news.rcn.net>, "John Saunders" <jws@ma.ultranet.com> writes: 4 > "Alan Greig" <a.greig@virgin.net> wrote in message& > news:3B97C8A9.71A79CF1@virgin.net... >> >> >> John Saunders wrote:c >>J >> > "It seems to me that the existence of a very large number of personalJ >> > computers with modems, TCP/IP and PPP, made a substantial difference. >> > >>H >> That was due to the US government allowing private connections to theG >> Internet somewhere around 1990 or so.  Nothing to do with Microsoft.- > J > If Microsoft hadn't shipped a with Windows a TCP/IP stack with PPP and aN > dialer, which devices would have connected hosts privately connecting to the > Internet?   9 The TCP/IP stacks that third party vendors had on Windows " before Microsoft got around to it.   ------------------------------  # Date: Thu, 06 Sep 2001 22:02:09 GMT " From: Art Rice <arice@myhouse.org>G Subject: Re: OT: Bush administration drops effort to break up Microsoft 9 Message-ID: <BnSl7.734$7G6.462726@paloalto-snr1.gtei.net>f   John Saunders wrote:  4 > "Alan Greig" <a.greig@virgin.net> wrote in message& > news:3B97C8A9.71A79CF1@virgin.net... >> >> >> John Saunders wrote:  >>J >> > "It seems to me that the existence of a very large number of personalJ >> > computers with modems, TCP/IP and PPP, made a substantial difference. >> > >>H >> That was due to the US government allowing private connections to theG >> Internet somewhere around 1990 or so.  Nothing to do with Microsoft.  > J > If Microsoft hadn't shipped a with Windows a TCP/IP stack with PPP and aJ > dialer, which devices would have connected hosts privately connecting to > the Internet?r > -- > John Saunders  > jws@ma.ultranet.com  >  >  >  > J Never seemed to have a problem with Win 3.1, Netscape, and a package from 9 FTP Software that the ISP shipped me in the early 90's....   --   Art Rice Tandem Admin Special Data Processing Corp ----------------------------* All opinions are my own and do not reflect* the views of the above mentioned employer.   ------------------------------  # Date: Fri, 07 Sep 2001 00:03:20 GMTmL From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr")G Subject: Re: OT: Bush administration drops effort to break up Microsoftd8 Message-ID: <00A01A7E.4B085357@SSRL04.SLAC.STANFORD.EDU>  Y In article <9n8ind$4j3$1@bob.news.rcn.net>, "John Saunders" <jws@ma.ultranet.com> writes:h3 >"Alan Greig" <a.greig@virgin.net> wrote in message % >news:3B97C8A9.71A79CF1@virgin.net...  >> >> >> John Saunders wrote:  >>J >> > "It seems to me that the existence of a very large number of personalJ >> > computers with modems, TCP/IP and PPP, made a substantial difference. >> > >>H >> That was due to the US government allowing private connections to theG >> Internet somewhere around 1990 or so.  Nothing to do with Microsoft.d >tI >If Microsoft hadn't shipped a with Windows a TCP/IP stack with PPP and aiM >dialer, which devices would have connected hosts privately connecting to the 
 >Internet?  K Macintoshes?  The third-party IP stacks that were written for Windows 3.1, -H which certainly didn't shop with an IP stack?  AOL software for Windows?7 PPP support shipped by third-party modem manufacturers?e   -- Alan   O =============================================================================== 0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056iM  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349, STANFORD, CA  94309-0210YO ===============================================================================t   ------------------------------   Date: 7 Sep 2001 02:38:06 GMTc) From: leslie@clio.rice.edu (Jerry Leslie) G Subject: Re: OT: Bush administration drops effort to break up Microsoft ' Message-ID: <9n9bue$gse$1@joe.rice.edu>6  K Alan Winston - SSRL Admin Cmptg Mgr (winston@SSRL.SLAC.STANFORD.EDU) wrote:  : M : Macintoshes?  The third-party IP stacks that were written for Windows 3.1, r1 : which certainly didn't shop with an IP stack?    : L But Microsoft did offer an IP stack for Windows 3.1, code name "Wolverine", ) to create Windows for Workgroups in 1994.M  L There was a bug in the final version of Wolverine that made it incompatible H with VMS, either UCX or TGV Multinet. The bug was not in the final beta.  G I posted the bug to the comp.protocols.tcp-ip.ibmpc news group, and was H surprised when the Microsoft programmer responsible for Wolverine's FTP L code, Keith Moore, emailed asking whether our VMS systems could be accessed 0 from the internet, so he could test his bug fix.  D Since we weren't comfortable with opening up our VAXes and ALPHAs to0 the 'net, he emailed his code to us for testing.   --Jerry Leslie   ------------------------------  $ Date: Thu, 6 Sep 2001 22:50:42 -0400  From: John Santos <JOHN@egh.com>G Subject: Re: OT: Bush administration drops effort to break up Microsoft / Message-ID: <1010906224554.64342C@Ives.egh.com>>  ( On Thu, 6 Sep 2001, John Saunders wrote:  4 > "Alan Greig" <a.greig@virgin.net> wrote in message& > news:3B97C8A9.71A79CF1@virgin.net... > >- > >- > > John Saunders wrote: > >:K > > > "It seems to me that the existence of a very large number of personal-K > > > computers with modems, TCP/IP and PPP, made a substantial difference.. > > >  > >uI > > That was due to the US government allowing private connections to the H > > Internet somewhere around 1990 or so.  Nothing to do with Microsoft. > J > If Microsoft hadn't shipped a with Windows a TCP/IP stack with PPP and aN > dialer, which devices would have connected hosts privately connecting to the > Internet?s > -- > John Saunders  > jws@ma.ultranet.coms  E When I signed up with Ultranet in the fall of 1994, Windows did *not*tB contain any of this stuff.  Ultranet sent me a floppy with TrumpetA Winsock, Eudora Light, Netscape browser, news client, FTP client,O telnet, ping, etc. ...  > M$ might have ultimately made it easier to connect to the net,A but they were late to the game and they resisted for a long time.    -- l John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  $ Date: Thu, 6 Sep 2001 23:48:40 -0400+ From: "John Saunders" <jws@ma.ultranet.com>>G Subject: Re: OT: Bush administration drops effort to break up Microsoft3+ Message-ID: <9n9g31$i0i$1@bob.news.rcn.net>1  2 "Alan Greig" <a.greig@virgin.net> wrote in message$ news:3B97D4F8.BCC4DE3F@virgin.net... >  >t > John Saunders wrote: >nL > > If Microsoft hadn't shipped a with Windows a TCP/IP stack with PPP and aL > > dialer, which devices would have connected hosts privately connecting to them
 > > Internet?e >nG > There were PC IP stacks supporting dialup SLIP and PPP available longh beforeG > Microsoft shipped one. Have you heard of Winsock for instance? It wast Winsock > > that most commonly connected earlier Windows PCs to the net.    I am very familiar with Winsock.  H It's not a matter of the existence of PPP, the issue is that Microsoft'sJ stack was available as soon as you bought your machine. You didn't have to8 go out and  buy a third-party stack and then install it. --
 John Saunders  jws@ma.ultranet.com    ------------------------------  $ Date: Thu, 6 Sep 2001 23:47:09 -0400+ From: "John Saunders" <jws@ma.ultranet.com>tG Subject: Re: OT: Bush administration drops effort to break up Microsoft + Message-ID: <9n9g07$hgo$1@bob.news.rcn.net>n  > "Malcolm Dunnett" <nothome@spammers.are.scum> wrote in message& news:k5BqKwGEQhp3@malvm5.mala.bc.ca...- > In article <9n8ind$4j3$1@bob.news.rcn.net>,s3 >     "John Saunders" <jws@ma.ultranet.com> writes:o >a6 > > "Alan Greig" <a.greig@virgin.net> wrote in message( > > news:3B97C8A9.71A79CF1@virgin.net... > >> > >> > >> John Saunders wrote:h > >>L > >> > "It seems to me that the existence of a very large number of personalL > >> > computers with modems, TCP/IP and PPP, made a substantial difference. > >> > > >>J > >> That was due to the US government allowing private connections to theI > >> Internet somewhere around 1990 or so.  Nothing to do with Microsoft.  > > L > > If Microsoft hadn't shipped a with Windows a TCP/IP stack with PPP and aL > > dialer, which devices would have connected hosts privately connecting to theo
 > > Internet?s > H >    Presumably those same devices, using a TCP/IP stack from one of theG > several vendors who sold them for Windows before Microsoft decided ton > bundle it in with Win95.  L I don't think this would have had the same effect as software which was partI of the system. There was no need for a separate installation, and all the I user had to enter to get onto the Internet was phone number, username andaI password. This is very different from installing Netmanage Chameleon, forn* instance, even if the ISP gives it to you.  D I also note that OEMs were not shipping machines with TCP/IP alreadyI installed. Before it shipped as part of Windows, anyone who wanted to useP TCP/IP had to install it.e  L >    Your comment is much like saying "if Microsoft hadn't shipped a browserL > with Windows what would people use to surf the net". I believe that at one; > time Netscape thought they had the answer to that one :-)o  K No, my comment is that _someone_ needed to ship a browser with Windows PCs,cL same way _someone_ had to provide TCP/IP and PPP. If OEMs had been includingL a TCP/IP stack with their products, then it wouldn't have been necessary for Microsoft to do so.  --
 John Saundersd jws@ma.ultranet.comc   ------------------------------  $ Date: Thu, 6 Sep 2001 23:51:01 -0400+ From: "John Saunders" <jws@ma.ultranet.com>nG Subject: Re: OT: Bush administration drops effort to break up Microsofte+ Message-ID: <9n9g7f$ip0$1@bob.news.rcn.net>a  6 "Jerry Leslie" <leslie@clio.rice.edu> wrote in message! news:9n9bue$gse$1@joe.rice.edu...-F > Alan Winston - SSRL Admin Cmptg Mgr (winston@SSRL.SLAC.STANFORD.EDU) wrote: > : I > : Macintoshes?  The third-party IP stacks that were written for Windows  3.1,1 > : which certainly didn't shop with an IP stack?  > :a@ > But Microsoft did offer an IP stack for Windows 3.1, code name "Wolverine",+ > to create Windows for Workgroups in 1994.   < I don't believe that the WfW IP stack supported PPP, did it? --
 John Saunders! jws@ma.ultranet.comt   ------------------------------  # Date: Fri, 07 Sep 2001 04:57:36 GMT 4 From: LESLIE@209-16-45-102.insync.net (Jerry Leslie)G Subject: Re: OT: Bush administration drops effort to break up Microsoftr' Message-ID: <4tYl7.753$Oh1.8105@insync>n  * John Saunders (jws@ma.ultranet.com) wrote:8 : "Jerry Leslie" <leslie@clio.rice.edu> wrote in message# : news:9n9bue$gse$1@joe.rice.edu...<H : > Alan Winston - SSRL Admin Cmptg Mgr (winston@SSRL.SLAC.STANFORD.EDU) : wrote: : > :fK : > : Macintoshes?  The third-party IP stacks that were written for WindowsI : 3.1,3 : > : which certainly didn't shop with an IP stack?r : > : B : > But Microsoft did offer an IP stack for Windows 3.1, code name : "Wolverine",- : > to create Windows for Workgroups in 1994.c : > : I don't believe that the WfW IP stack supported PPP, did it? :o% Yes, here's a trouble-shooting guide:u  @   http://support.microsoft.com/support/kb/articles/Q115/5/93.asp>   Troubleshooting Remote Access in Windows for Workgroups 3.11  0 but it only supported the NetBeui protocol, per:  0   http://pla-netx.com/linebackn/guis/win311.html   Windows for Workgroups 3.11$  % --Jerry Leslie   leslie@clio.rice.edur/                  leslie@209-16-45-97.insync.net1;                  leslie@209-16-45-102.insync.net is invalid    ------------------------------  # Date: Thu, 06 Sep 2001 17:49:56 GMT 1 From: "Mark D. Jilson" <jilly@clarityconnect.com>s Subject: Re: Pagefile questions 2 Message-ID: <3B97B7B1.FC089077@clarityconnect.com>  F Given the peak space usage and the file sizes I'd drop to 2 files.  IfG the peak usage did not cover a peak working period for this system thentH you will either want to wait for a peak usage period and revisit this or' not drop as many files or not drop any.o   Rob Young wrote: > s > In article <20010906141142.18877.qmail@web20201.mail.yahoo.com>, Fabio Cardoso <fabiopenvms@yahoo.com.br> writes:l > K >         One major gotcha... a process can at most use 4 pagefiles (unlessrD >         this has changed, sorry no reference handy).  I got bit byH >         a site that thought.. "hey , let's make a bunch of them", theyO >         had 10.  Came a time a large process ran up maxed out the 4 pagefiles.J >         that were mapped (they were unequal sizes and unfortunately this* >         process didn't map a large one). > C >         Those pagefiles (from max used) probably aren't that hot.t > F >         I'd consolodate to 4 across 2 RAID1 volumes.  Your pagefilesF >         are on RAID?  Preferrably write-back cache enabled RAIDsets.< >         If not, you have 7 single points of failure below. > K >         (I am assuming that you can verify I/O of pagefiles over a periodeN >         of days, this may not be easy to isolate without a performance tool.H >         If they are on their own volume you can probably run MONI DISKG >         and summarize.  If not, you may not be able to zero in unless9K >         I am overlooking or forgetting a technique.  Point is.. you don'thJ >         want to saturate your pagefiles with I/O if you can avoid it and >         it appears you can). > - >                                         Robr > 
 > > HP Peopleo > >d > > 0 > > I created a report by AUTOGEN and I have the5 > > information below regarding to the PAGEFILES use.t3 > > I would like to reduce  the number of PAGEFILEse9 > > spreaded in my disks. May I just create two PAGEFILEsu8 > > in two different disks adding the usage sizes of all7 > > in a new files ? I think the number of PAGEFILES isg: > > excessive - it was a VAX/VMS heritage. Nowadays I have > >d' > > Alphaservers 4100 with 4 GB of RAM.r > >  > >s$ > > Page and Swap file calculations:$ > > -------------------------------- > >h# > > PAGEFILE1_SIZE information (for * > > DISCO01:[SYS0.SYSEXE]PAGEFILE1.SYS;1):! > >         Feedback information.e9 > >            Old value was 860000, New value is 1199500k6 > >            Maximum observed usage (blocks): 2673606 > >            PAGEFILE1_SIZE will be modified to hold > > 1199500 blocks > >h# > > PAGEFILE2_SIZE information (forn* > > DISCO02:[SYS0.SYSEXE]PAGEFILE2.SYS;1):! > >         Feedback information.i9 > >            Old value was 860000, New value is 1199500A6 > >            Maximum observed usage (blocks): 1278086 > >            PAGEFILE2_SIZE will be modified to hold > > 1199500 blocks > >t# > > PAGEFILE3_SIZE information (fore* > > DISCO03:[SYS0.SYSEXE]PAGEFILE3.SYS;1):! > >         Feedback information.w9 > >            Old value was 860000, New value is 1199500-6 > >            Maximum observed usage (blocks): 1188006 > >            PAGEFILE3_SIZE will be modified to hold > > 1199500 blocks > >e > >  > >e# > > PAGEFILE4_SIZE information (for4* > > DISCO04:[SYS0.SYSEXE]PAGEFILE4.SYS;1):! > >         Feedback information. 9 > >            Old value was 860000, New value is 1199500i6 > >            Maximum observed usage (blocks): 1344646 > >            PAGEFILE4_SIZE will be modified to hold > > 1199500 blocks > >a# > > PAGEFILE5_SIZE information (fora* > > DISCO05:[SYS0.SYSEXE]PAGEFILE5.SYS;1):! > >         Feedback information.a9 > >            Old value was 860000, New value is 1199500r6 > >            Maximum observed usage (blocks): 1523046 > >            PAGEFILE5_SIZE will be modified to hold > > 1199500 blocks > >m# > > PAGEFILE6_SIZE information (for * > > DISCO06:[SYS0.SYSEXE]PAGEFILE6.SYS;1):! > >         Feedback information.d9 > >            Old value was 859900, New value is 1199500o6 > >            Maximum observed usage (blocks): 1240166 > >            PAGEFILE6_SIZE will be modified to hold > > 1199500 blocks > > # > > PAGEFILE7_SIZE information (foru* > > DISCO07:[SYS0.SYSEXE]PAGEFILE7.SYS;1):! > >         Feedback information.-9 > >            Old value was 859900, New value is 1199500e6 > >            Maximum observed usage (blocks): 122464P > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=P > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
 > > =3D=3D=3Dr > >c > >r > >  > > =3D=3D=3D=3D=3DrP > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > > =3Da > > F=E1bio dos Santos Cardoso > > OpenVMS System Manager > > Rio de Janeiro - Brazils > > fabiopenvms@yahoo.com.brP > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > > =3De > >t6 > > __________________________________________________ > > Do You Yahoo!?P > > Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger= > >T > > http://im.yahoo.coma   -- lD Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY0 	- jilly@clarityconnect.com			- Brett Bodine fan. 	- Mark.Jilson@Compaq.com			- since 1975 or so, 	- http://www.jilly.baka.com               -   ------------------------------  $ Date: Thu, 6 Sep 2001 19:38:52 +02008 From: "Martin Hoogenboom \(XS4All\)" <martinh@xs4all.nl> Subject: Re: Pagefile questionsD3 Message-ID: <006601c136fa$d38e0b30$8149130a@WWS006>o   Fabio,  J I would descrease the number of page-files down to one or two, possibly on  separate (pagefile only?) disks.L As you can see in the usage numbers you actually don't need to increase the=  L pagefile size (provided your system load is not changed dramatically) since=  @ the maximum use of the pagefiles is less then 1/4 of their size.  ; Consider disabling pagefile modifications in modparams.dat.    Regards, Martin Hoogenboomd     ----- Original Message -----0 From: "Fabio Cardoso" <fabiopenvms@yahoo.com.br> To: <Info-VAX@Mvb.Saic.Com>c* Sent: Thursday, September 06, 2001 4:11 PM Subject: Pagefile questionsn     > HP Peoplen >u >r. > I created a report by AUTOGEN and I have the3 > information below regarding to the PAGEFILES use.d1 > I would like to reduce  the number of PAGEFILEs 7 > spreaded in my disks. May I just create two PAGEFILEs 6 > in two different disks adding the usage sizes of all5 > in a new files ? I think the number of PAGEFILES isw8 > excessive - it was a VAX/VMS heritage. Nowadays I have >-% > Alphaservers 4100 with 4 GB of RAM.2 >M > " > Page and Swap file calculations:" > -------------------------------- >)! > PAGEFILE1_SIZE information (fori( > DISCO01:[SYS0.SYSEXE]PAGEFILE1.SYS;1): >         Feedback information.07 >            Old value was 860000, New value is 1199500.4 >            Maximum observed usage (blocks): 2673604 >            PAGEFILE1_SIZE will be modified to hold > 1199500 blocks >A! > PAGEFILE2_SIZE information (forh( > DISCO02:[SYS0.SYSEXE]PAGEFILE2.SYS;1): >         Feedback information.a7 >            Old value was 860000, New value is 1199500P4 >            Maximum observed usage (blocks): 1278084 >            PAGEFILE2_SIZE will be modified to hold > 1199500 blocks >I! > PAGEFILE3_SIZE information (for.( > DISCO03:[SYS0.SYSEXE]PAGEFILE3.SYS;1): >         Feedback information.i7 >            Old value was 860000, New value is 1199500c4 >            Maximum observed usage (blocks): 1188004 >            PAGEFILE3_SIZE will be modified to hold > 1199500 blocks >e >o >i! > PAGEFILE4_SIZE information (fort( > DISCO04:[SYS0.SYSEXE]PAGEFILE4.SYS;1): >         Feedback information.t7 >            Old value was 860000, New value is 1199500=4 >            Maximum observed usage (blocks): 1344644 >            PAGEFILE4_SIZE will be modified to hold > 1199500 blocks >i! > PAGEFILE5_SIZE information (forL( > DISCO05:[SYS0.SYSEXE]PAGEFILE5.SYS;1): >         Feedback information. 7 >            Old value was 860000, New value is 1199500=4 >            Maximum observed usage (blocks): 1523044 >            PAGEFILE5_SIZE will be modified to hold > 1199500 blocks >c! > PAGEFILE6_SIZE information (for ( > DISCO06:[SYS0.SYSEXE]PAGEFILE6.SYS;1): >         Feedback information.r7 >            Old value was 859900, New value is 1199500W4 >            Maximum observed usage (blocks): 1240164 >            PAGEFILE6_SIZE will be modified to hold > 1199500 blocks >r! > PAGEFILE7_SIZE information (fore( > DISCO07:[SYS0.SYSEXE]PAGEFILE7.SYS;1): >         Feedback information. 7 >            Old value was 859900, New value is 1199500 4 >            Maximum observed usage (blocks): 122464N > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=L =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=	 =3D=3D=3Do >s >p >. > =3D=3D=3D=3D=3DnN > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3De > F=E1bio dos Santos Cardoso > OpenVMS System Manager > Rio de Janeiro - Brazili > fabiopenvms@yahoo.com.brN > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3Dh >n4 > __________________________________________________ > Do You Yahoo!?C > Get email alerts & NEW webcam video instant messaging with Yahoo! 	 Messenger  > http://im.yahoo.com: >:   ------------------------------  $ Date: Thu, 6 Sep 2001 13:41:35 -0400  From: jamese@beast.dtsw.army.mil Subject: Re: Pagefile questionsu0 Message-ID: <01090613413544@beast.dtsw.army.mil>  M Kilgallen@SpamCop.net (Larry Kilgallen) wrote on 6 Sep 2001 11:47:12 -0500 inS( <qv7gcAUiBp7U@eisner.encompasserve.org>:  P > In article <4J90RQoqHk43@eisner.encompasserve.org>, young_r@encompasserve.org  > (Rob Young) writes:  > > S > > In article <20010906141142.18877.qmail@web20201.mail.yahoo.com>, Fabio Cardoso i$ > <fabiopenvms@yahoo.com.br> writes: > > F > > 	One major gotcha... a process can at most use 4 pagefiles (unless1 > > 	this has changed, sorry no reference handy).h > " > On Alpha it has gone away.  See: > : > file:///VMSDOC073/v73/6620/6620pro_004.html#large_pf_sec   Or:   M http://www.openvms.compaq.com:8000/73final/6620/6620pro_004.html#large_pf_sec   - Wow! Up to 254 page/swap files of 128GB each!t  : Ed James                           ed.james@telecomsys.com5 TeleCommunications Systems, Inc.   voice 410-295-1919O; 2024 West Street, Suite 300              800-810-0827 x1919e5 Annapolis, MD 21401-3556           fax   410-280-1094    ------------------------------  * Date: Thu, 6 Sep 2001 11:53:28 -0700 (PDT). From: Fabio Cardoso <fabiopenvms@yahoo.com.br> Subject: Re: Pagefile questions,@ Message-ID: <20010906185328.25968.qmail@web20207.mail.yahoo.com>   Martin  6 Like everybody shared their experiences  I will reduce  4 the number of PAGEFILES. I will instal one BA-200 in2 my Alpha 4100 with 2 RAIDs (8 GB) each to do that.   Thnks a lotD Fabio4      4 --- "Martin Hoogenboom (XS4All)" <martinh@xs4all.nl> wrote: > Fabio, >=204 > I would descrease the number of page-files down to > one or two, possibly on " > separate (pagefile only?) disks.2 > As you can see in the usage numbers you actually > don't need to increase the1 > pagefile size (provided your system load is notp > changed dramatically) sinceo6 > the maximum use of the pagefiles is less then 1/4 of
 > their size.i >=20. > Consider disabling pagefile modifications in > modparams.dat. >=20
 > Regards, > Martin Hoogenboome >=20 >=20 > ----- Original Message -----2 > From: "Fabio Cardoso" <fabiopenvms@yahoo.com.br> > To: <Info-VAX@Mvb.Saic.Com>-, > Sent: Thursday, September 06, 2001 4:11 PM > Subject: Pagefile questions  >=20 >=20
 > > HP People- > >  > > 0 > > I created a report by AUTOGEN and I have the5 > > information below regarding to the PAGEFILES use.i3 > > I would like to reduce  the number of PAGEFILEs-/ > > spreaded in my disks. May I just create twoD > PAGEFILEso4 > > in two different disks adding the usage sizes of > allv4 > > in a new files ? I think the number of PAGEFILES > is5 > > excessive - it was a VAX/VMS heritage. Nowadays Is > have > >A' > > Alphaservers 4100 with 4 GB of RAM.m > >e > > $ > > Page and Swap file calculations:$ > > -------------------------------- > >># > > PAGEFILE1_SIZE information (fors* > > DISCO01:[SYS0.SYSEXE]PAGEFILE1.SYS;1):! > >         Feedback information.a1 > >            Old value was 860000, New value is>	 > 1199500 6 > >            Maximum observed usage (blocks): 2673606 > >            PAGEFILE1_SIZE will be modified to hold > > 1199500 blocks > >t# > > PAGEFILE2_SIZE information (forp* > > DISCO02:[SYS0.SYSEXE]PAGEFILE2.SYS;1):! > >         Feedback information.l1 > >            Old value was 860000, New value iso	 > 1199500n6 > >            Maximum observed usage (blocks): 1278086 > >            PAGEFILE2_SIZE will be modified to hold > > 1199500 blocks > >c# > > PAGEFILE3_SIZE information (fort* > > DISCO03:[SYS0.SYSEXE]PAGEFILE3.SYS;1):! > >         Feedback information. 1 > >            Old value was 860000, New value isp	 > 1199500l6 > >            Maximum observed usage (blocks): 1188006 > >            PAGEFILE3_SIZE will be modified to hold > > 1199500 blocks > >n > >i > >t# > > PAGEFILE4_SIZE information (forn* > > DISCO04:[SYS0.SYSEXE]PAGEFILE4.SYS;1):! > >         Feedback information.s1 > >            Old value was 860000, New value isa	 > 1199500i6 > >            Maximum observed usage (blocks): 1344646 > >            PAGEFILE4_SIZE will be modified to hold > > 1199500 blocks > >s# > > PAGEFILE5_SIZE information (foru* > > DISCO05:[SYS0.SYSEXE]PAGEFILE5.SYS;1):! > >         Feedback information.e1 > >            Old value was 860000, New value is_	 > 1199500e6 > >            Maximum observed usage (blocks): 1523046 > >            PAGEFILE5_SIZE will be modified to hold > > 1199500 blocks > >t# > > PAGEFILE6_SIZE information (forv* > > DISCO06:[SYS0.SYSEXE]PAGEFILE6.SYS;1):! > >         Feedback information..1 > >            Old value was 859900, New value is,	 > 1199500 6 > >            Maximum observed usage (blocks): 1240166 > >            PAGEFILE6_SIZE will be modified to hold > > 1199500 blocks > >e# > > PAGEFILE7_SIZE information (forn* > > DISCO07:[SYS0.SYSEXE]PAGEFILE7.SYS;1):! > >         Feedback information.$1 > >            Old value was 859900, New value ist	 > 1199500t6 > >            Maximum observed usage (blocks): 122464 > >h >hL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=L =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=	 =3D=3D=3D. > >d > >e > >l > > =3D=3D=3D=3D=3D M > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=r =3D=3D > > F=E1bio dos Santos Cardoso > > OpenVMS System Manager > > Rio de Janeiro - Brazila > > fabiopenvms@yahoo.com.brM > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=s =3D=3D > >i6 > > __________________________________________________ > > Do You Yahoo!?/ > > Get email alerts & NEW webcam video instant: > messaging with Yahoo!e > Messengeru > > http://im.yahoo.coms > >u >=20     =3D=3D=3D=3D=3D L =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D  F=E1bio dos Santos Cardoso OpenVMS System Manager Rio de Janeiro - Brazild fabiopenvms@yahoo.com.brL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D   2 __________________________________________________ Do You Yahoo!?L Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger=   http://im.yahoo.come   ------------------------------   Date: 06 Sep 2001 22:56:16 GMT$ From: jobseekerr@aol.comNoSpam (Dan)E Subject: Re: Silly names (was: RE: HP to buy Compaq (Globe and Mail))t9 Message-ID: <20010906185616.08149.00000403@mb-mq.aol.com>n  E All good names, but I thought up one today that I think you'll like. e  L I intentionally did an extremely amateurish job on this... so nobody sue me. ;-)   . http://members.aol.com/jobseekerr/hpcompaq.bmp    8 HP and Compaq together make one huge whale of a company.   Dan1   With apologies to all. DanJ   ------------------------------  $ Date: Thu, 6 Sep 2001 19:56:55 +0100, From: "Richard Maher" <maher_rj@hotmail.c*m>' Subject: ss$_personadelpend What is it?l3 Message-ID: <9n8gv1$h3c$1@neptunium.btinternet.com>n   Hi,r  6 Does anyone have any documentation on the status value7 ss$_personadelpend as returned from sys$persona_delete.    Help/message doesn't help.  9 I know it's a success status but why am I getting it in a6: single-threaded program and only after (in this particular1 case) I've called Rdb7.0.6 SQL> Set Session Auth?n2 Who is referencing it? I've done a $persona_assume with iss$c_id_natural.  5 Thankfully $persona_find seems to know it's no longery9 there (can anyone confirm this?) but why can't the delete 2 complete immediately? What is it waiting for? When7 does it complete and why don't we have both synchronoush- and asynchronous versions of $persona_delete?o  	 VMS 7.2-1s   Regards Richard Maher.   ------------------------------  % Date: Thu, 06 Sep 2001 16:59:55 -0500aC From: "Craig A. Berry" <craig.berry@nospam.SignalTreeSolutions.com>o+ Subject: Re: ss$_personadelpend What is it??I Message-ID: <craig.berry-DC1730.16595506092001@newsrump.sjc.telocity.net>e  3 In article <9n8gv1$h3c$1@neptunium.btinternet.com>, .  "Richard Maher" <maher_rj@hotmail.c*m> wrote:  8 > Does anyone have any documentation on the status value9 > ss$_personadelpend as returned from sys$persona_delete.t   <snip>  4 > Who is referencing it? I've done a $persona_assume > with iss$c_id_natural.  F Are you doing that before or after the delete?  I think if you do the @ delete first, and then drop the persona you've just deleted (by B reassuming your natural one) the persona you've deleted will then H actually be gone.  My memory may not be right, though, and you may also * have other things referencing the persona.    D I would recommend the system services reference manual over on-line  help:   = <http://www.openvms.compaq.com/doc/73final/4527/4527PRO.HTML>i   ------------------------------  % Date: Thu, 06 Sep 2001 20:13:57 -0500d1 From: "David J. Dachtera" <djesys.nospam@fsi.net>t Subject: Re: Status of Alpha' Message-ID: <3B981F55.98A410DE@fsi.net>t   "www.islandco.com" wrote:  > = > "Burnie M" <burniem.NOSPAM@ozemail.com.au> wrote in messagea4 > news:7kjdptso4b45br291cmqgk4q9mcrl7l0pm@4ax.com...D > > Yes, but don't worry about it. You missed something much bigger. > >P > >LD > > On 5 Sep 2001 09:15:57 -0700, net2res@aol.com (Bob Sikes) wrote: > >s > > >Hello All,e > > >98 > > >I noticed while flipping thru the postings, someone: > > >mentioned the end of Alphas?    I have been knee deep; > > >in code for the past two years...did I miss something?n > > >IC > > >Sorry, I'm still getting over KO leaving...Best To All!!   Bobn > B > Yeah.. John Lennon was shot and they brought back Rockford Files  2 THEY DID??!!! SHOOT! I don't get *THAT* channel...   --   David J. Dachteral dba DJE Systemso http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/3   ------------------------------   Date: 6 Sep 2001 18:20:30 GMTl2 From: ken.s.robinson@exxonmobil.com (Ken Robinson)4 Subject: Vax/Vms Systems Administrator in Albany, NY8 Message-ID: <Xns911491E3E373Dksrobinerenjcom@159.70.1.1>  I     I recieved the following from a recruiter who called me. He indicatedSH     that the job is located in Albany, NY.  If you contact the recruiterB     concerning this job, please let him know that you saw it here.          Ken Robinson          Ad follows:      L One of the nation's leading financial services companies is searching for a E strong-minded, hard-working, leader. This individual must be able to  E organize and motivate a project team to analyze and enhance existing ND technology, operations, processes, and systems, and to capitalize onF production and value. To meet this challenge, you will lead efforts toD perform analysis, system enhancements, and system development tasks,K and will act as an internal consultant to provide direction on a variety of G operational, procedural, and systems interface issues. You will exhibitsB solid analytical expertise, business judgement, and communicationsJ skills to review risks and alternatives, and to introduce recommendations D to management. Specifically the lead analyst will be responsible forC administration, monitoring, and maintenance of VMS/VAX systems in a9" large production based environment      Skills and Qualifications=     7     2+ years administering Unix-based computer systems.3%     Basic TCP/IP networking concepts.3F     Knowledge of OpenVMS installation, configuration, and maintenance.H     Experience compiling and installing C/C++ as well as vendor-supplied+     "shrink-wrapped" programs and packages. H     Knowledge of installation software, systems monitoring software, and     system backup software.aG     Experience/Knowledge of trouble-shooting computer hardware/software=7     problems and replacing/upgrading computer hardware._K     Willingness to carry a pager, partake in night/weekend on-call schedulei+     and work outside of "normal" 9-5 hours. 1     Shell Scripting (Perl, Bourne, SH, KSH, CSH).oD     COMPANY PAID RELOCATION TO ALBANY NY GOOD BENEFITS AND CHANCE TO     ADVANCE.      Barry Bliss, CPC Executive Search Consultantr Ethan Allen Personnel Group  845-471-9700 x 348   ------------------------------   Date: 6 Sep 2001 14:44:05 -0500-- From: Kilgallen@SpamCop.net (Larry Kilgallen) 8 Subject: Re: Vax/Vms Systems Administrator in Albany, NY3 Message-ID: <iK$gDimHWGXX@eisner.encompasserve.org>$  m In article <Xns911491E3E373Dksrobinerenjcom@159.70.1.1>, ken.s.robinson@exxonmobil.com (Ken Robinson) writes:n > K >     I recieved the following from a recruiter who called me. He indicatedlJ >     that the job is located in Albany, NY.  If you contact the recruiterD >     concerning this job, please let him know that you saw it here.  5 Even if we saw it first on your DECUServe post ?  :-)g   ------------------------------  $ Date: Thu, 6 Sep 2001 19:20:28 -0400! From: "me" <wicklinedd@erols.com>m+ Subject: VMS 7.2 / CMU-IP6.6.5K FTP problem + Message-ID: <9n8ugh$7cn$1@bob.news.rcn.net>   E I have a vaxstation 4000/90 with vms7.2 and DECW and CMU TCP/IP 6.6.5nI loaded.  When I ftp in it downlaods files from the VAX fast, (10BaseT huboL with one BNC and many) twisted pair ports.  However anything I upload to theJ Vax is SLOW.  Iam not an expert and on the LINUX box with hash on it seemsK to burst out the first 10k but the rest is on the order 1k/min.  Any ideas?e   Dave   ------------------------------  # Date: Fri, 07 Sep 2001 01:18:51 GMTe- From: goathunter@goatley.com (Hunter Goatley)M/ Subject: Re: VMS 7.2 / CMU-IP6.6.5K FTP problem-0 Message-ID: <3b982015.43235819@news.process.com>  E On Thu, 6 Sep 2001 19:20:28 -0400, "me" <wicklinedd@erols.com> wrote:d  F >I have a vaxstation 4000/90 with vms7.2 and DECW and CMU TCP/IP 6.6.5J >loaded.  When I ftp in it downlaods files from the VAX fast, (10BaseT hubM >with one BNC and many) twisted pair ports.  However anything I upload to therK >Vax is SLOW.  Iam not an expert and on the LINUX box with hash on it seemsfL >to burst out the first 10k but the rest is on the order 1k/min.  Any ideas? > J Replace the CMU FTP with MGFTP.  I don't remember exactly what the problemL was, but you should find that MGFTP greatly outperforms the CMU FTP, as wellJ as offering a lot more features.  (But since MGFTP was originally based onN the CMU FTP code, you'll find that it's virtually identical in how it's used.)  5 ftp://ftp.process.com/vms-freeware/fileserv/mgftp.zipZ   Hunter ------9 Hunter Goatley, Process Software, http://www.process.com/f9 goathunter@goatley.com     http://www.goatley.com/hunter/    ------------------------------  # Date: Thu, 06 Sep 2001 21:17:50 GMTl2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: VMS Cluster help..G- Message-ID: <2KRl7.3$YP.122@news.cpqcorp.net>   W In article <3b96e606_2@corp.newsgroups.com>, jkclausen@yahoo.com (John Clausen) writes: 8 :Hello, could someone point me in the correct direction?O :I am looking for a howto on VMS clustering or some good information on how to 3 :do it.   J   Please start by skimming the cluster documentation in the OpenVMS manualL   set, and the VOTES and EXPECTED_VOTES stuff in the OpenVMS FAQ.  (The FAQ 6   has pointers to the OpenVMS documentation set, too.)  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Fri, 07 Sep 2001 00:32:58 GMT=) From: rob.buxton@wcc.govt.nz (Rob Buxton)D Subject: Re: VMS Cluster help..=0 Message-ID: <3b98153e.16678121@news.wcc.govt.nz>   To add what's already here.sD The sysgen parameters TMSCP_SERVE_ALL and TMSCP_LOAD will need to be6 set on the MicroVAX  in order to Serve the TK50 Drive.  @ On 5 Sep 2001 21:57:10 -0500, jkclausen@yahoo.com (John Clausen) wrote:  8 >Hello, could someone point me in the correct direction?O >I am looking for a howto on VMS clustering or some good information on how to _ >do it._ >_P >I have a MicroVAX II I would like to boot over the network from my VAX Station 	 >4000/60.Y >oJ >I would also like to have access to the TK50 in the MicroVAX II from the  >4000/60 >,  >Thanks in advance for the help, >e >Johnt >s >r >m? >-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----@B >http://www.newsfeeds.com - The #1 Newsgroup Service in the World!? >-----==  Over 80,000 Newsgroups - 16 Different Servers! =-----s   ------------------------------   Date: 6 Sep 2001 22:36:57 GMT / From: Hans.Bachner@altavista.net (Hans Bachner) + Subject: Re: VMS NFS and PC-NFS (Reflexion)q( Message-ID: <9n94r2.9l.1@hans.myfqdn.de>  # Jakob Erber (erberj@post.ch) wrote:e   <snip>8 >... but Reflexion always comes back saying: Cannot readH >targets file system (or similar). We are using HPs (:-)) TCPIP Services& >for VMS. Ping works fine from the PC.  0 Anything interesting in the NFS server log file?  L Turn on the SECURITY privilege, enable OPCOM replies, and see what messages 9 you get when you try to access the files from reflection.h   Hope this helps, Hans.    ------------------------------  % Date: Thu, 06 Sep 2001 16:09:55 -0400i- From: JF Mezei <jfmezei.spamnot@videotron.ca> > Subject: Re: VMS To Be Squeezed Out Of HP's Strategic Vision ?, Message-ID: <3B97D80C.1C5D9E7D@videotron.ca>   Jerry Leslie wrote:,6 >    http://news.cnet.com/news/0-1003-200-7071077.htmlI >    Eventually, HP will converge toward Linux, NT and Unix, according to0K >    McDonnell. The challenge will lie in coming up with a product road mapsD >    that will push customers toward a more streamlined OS portfolio  >    without alienating them..."  M Easier said than done. If they do not quickly correct their public statement,rJ they risk restarting the quick migration FROM vms and especially TRu64 and( that cause a lot of blood to flow at HP.  N For all its faults, I am confident that Compaq knew that it couldn't just killM VMS and that it needed to slowly manage its disapearance over long time as toe not lose the customers.   H It is interesting that the text you quoted did not include Compaq's trueJ enterprise OS: Tandem's NSK. I used "true" because it seems to be the onlyL non-MS OS that Compaq was proud of (since it is good to be bragging that you/ run x% of the world's stock exchanges etc etc).r  N I am not surprised this is happening. I think that the 25 billion goes towards eliminating a competitor.6  L As Carly said : "Who are you going to call ?" (refering to Ghostbusters). HPM will be the only "serious"  NT outfit left, so Microsoft, Oracle , SAP et all : will have to deal with HP as a channel for their products.  N Next, I think that Price WaterHouse or some other big outfit will be purchasedM by Mickey Dell and Dell will then become a serious enterprise candatidate andaN its much better health will make Microsoft focus its efforst to help Dell push the MS bloatware to enterprise.e  " That will leave IBM, SUN and DELL.  J IBM will selll Cadillacs and Rolls Royces. SUN will sell Midrange cars andK DELL will sell the small low price no-frills cars in the enterprise market.:   ------------------------------  $ Date: Thu, 6 Sep 2001 16:43:58 -0400' From: "Bill Todd" <billtodd@foo.mv.com>i> Subject: Re: VMS To Be Squeezed Out Of HP's Strategic Vision ?( Message-ID: <9n8n4q$d1j$1@pyrite.mv.net>  : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message& news:3B97D80C.1C5D9E7D@videotron.ca...   ...E  D > Easier said than done. If they do not quickly correct their public
 statement,L > they risk restarting the quick migration FROM vms and especially TRu64 and* > that cause a lot of blood to flow at HP. >lK > For all its faults, I am confident that Compaq knew that it couldn't justn killL > VMS and that it needed to slowly manage its disapearance over long time as to > not lose the customers.s  J That certainly seemed to be the case up until Monday's announcement.  Now,J however, it seems possible that the porting and other 'commitments' to theH Alpha OSs may simply have been what was necessary to keep Compaq lookingJ like a somewhat going concern during the period between the Intel deal and! completion of the merger details.,  L Who knows?  And quite possibly who cares?  It looks like it's time for AlphaK users to either find a different vendor or slam Capellas up against a bricksG wall so hard that his teeth rattle and his underwear needs changing andG straighten him out.    - bill   ------------------------------  % Date: Thu, 06 Sep 2001 17:20:27 -04001- From: JF Mezei <jfmezei.spamnot@videotron.ca>b> Subject: Re: VMS To Be Squeezed Out Of HP's Strategic Vision ?, Message-ID: <3B97E88E.C7E75E04@videotron.ca>   Bill Todd wrote:N > Who knows?  And quite possibly who cares?  It looks like it's time for AlphaM > users to either find a different vendor or slam Capellas up against a brick I > wall so hard that his teeth rattle and his underwear needs changing and  > straighten him out.d  D Capellas has been made irrelevant. Pointless to throw bricks at him.  M Consider also that, in hindsight,  it was Carly that killed Alpha and allowed = Compaq to announce porting efforts for Tru64 and VMS and NSK.   J The interesting aspect is the keeping of EV7 folks for a while. As someoneM else mentioned, what about the possibility that VMS and Tru64 wouldn't really=L be ported to IA64 and that they will instead find it cheaper to extend EV7'sN life to allow for a proper downsizing of VMS while retaining the VMS customers on a different platform ?r  J At the time the deal with Intel was negotiated and announced, they alreadyH knew that Compaq would cease to exist and HP would inherit the stuff. IfL Capellas had tried to kill VMS but was convinced that it would have resultedN in instant loss of significant revenus and more importantly, permanent loss ofN a large percentage of customers, then Capellas would have communicated that toN Carly when Carly mentioned she would kill those rogue operating systems living in Compaq's basement.3  M So, at this point in time, at best, I think that HP will allow VMS to survivemM as long as it stays hidden in the basement. It is a given that it won't be onD HP's list of core products.   K I think that outright killing of VMS would not be the worse case. The worse_M case would be continued uncertainty about its future, especially if you don't N even know if it will be ported to IA64 or continue on Alpha until they run out of Alpha chips.2  M The message seems to become clearer and clearer that VMS is not for new "long(J term" customers and that HP will just be a good corporate citizen and help existing large customers.n   ------------------------------  $ Date: Thu, 6 Sep 2001 17:21:14 -0400' From: "Bill Todd" <billtodd@foo.mv.com>e> Subject: Re: VMS To Be Squeezed Out Of HP's Strategic Vision ?( Message-ID: <9n8pak$evj$1@pyrite.mv.net>  : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message& news:3B97E88E.C7E75E04@videotron.ca... > Bill Todd wrote:J > > Who knows?  And quite possibly who cares?  It looks like it's time for Alpha.I > > users to either find a different vendor or slam Capellas up against ae brick.K > > wall so hard that his teeth rattle and his underwear needs changing andv > > straighten him out.a >e$ > Capellas has been made irrelevant.  6 Not if the merger fails, as seems increasingly likely.   - bill   ------------------------------   Date: 6 Sep 2001 22:34:09 GMT / From: Hans.Bachner@altavista.net (Hans Bachner)e> Subject: Re: VMS To Be Squeezed Out Of HP's Strategic Vision ?( Message-ID: <9n94ln.9l.1@hans.myfqdn.de>  . JF Mezei (jfmezei.spamnot@videotron.ca) wrote:   <snip>I >It is interesting that the text you quoted did not include Compaq's truewF >enterprise OS: Tandem's NSK. I used "true" because it seems to be theI >only non-MS OS that Compaq was proud of (since it is good to be bragging 9 >that you run x% of the world's stock exchanges etc etc).h <snip>  J Running x% of the world's stock exchanges is also true for OpenVMS, along C with (very) significant presense in lottery business, mobile phone -4 accounting, healthcare, chip manufacturing etc. etc.  E After several years of declining revenue, OpenVMS has been a growing iK business since last year, with healthy profit margins btw. I don't see any aG business reason to kill it in the foreseeable future (which admittedly n@ isn't too long in this business), let aside DII COE commitments.   Strictly my personal opinion,a Hans.r   ------------------------------  % Date: Thu, 06 Sep 2001 20:25:48 -0500e1 From: "David J. Dachtera" <djesys.nospam@fsi.net>e> Subject: Re: VMS To Be Squeezed Out Of HP's Strategic Vision ?' Message-ID: <3B98221C.684E6E4D@fsi.net>m   Nic Clews wrote: >  > Jerry Leslie wrote:e > >r( > >    HP to have merger map in 100 days > >    By Michael Kanellos" > >    Staff Writer, CNET News.com& > >    September 5, 2001, 5:15 p.m. PT	 > >>    .nK > >    HP's transition plan will have to tackle a number of issues. Because I > >    of the merger, HP finds itself responsible for supporting multipleuI > >    server operating systems, for example: Linux, Windows NT, OpenVMS,w< > >    HP-UX and Compaq's own version of Unix, among others. > >mK > >    Eventually, HP will converge toward Linux, NT and Unix, according to M > >    McDonnell. The challenge will lie in coming up with a product road mapLF > >    that will push customers toward a more streamlined OS portfolio" > >    without alienating them..." > E > The writer is wrong, and you're reading the wrong things into this.d  D The writer is paraphrasing his source. Not as accurate as a quote, IG grant you, ... I wrote to the columnist and his response indicated that F Mr. McDonnell has been made aware of the potentially dire consequences* of what was attributed as his having said.   D > I cannot and will not discuss my sources, but yet again c.o.v. are > panicking over nothing.e  G Hardly. As it stands, the article is tanatmount to a proclamation of he/8 death of OpenVMS - and at a fairly high, official level.  D However, if you are unable to quote your sources, than simply making2 such a statement may border on a breach of an NDA.   E > You'll have to accept my word, but if it's not good enough for you,v  	 It isn't.i  J > don't spend time arguing with me, retrain yourself, if you think that isI > your personal future. If you want to flame someone, flame the writer ofsJ > the article, and get him to prove what he/his source claims with respect. > to VMS. His email is on the page referenced.  G Already did. In his reply, he said without saying it that Mr. McDonnelllE has had to back-pedal seriously from what was implied in the article.c  eD > Personally I'll be wheeled out the door from 'a VMS site' into theE > crematorium, I'll have a little plate that says "Nic P Clews, Fatals& > bugcheck dd-mm-yyyy". I work on VMS,  H You would do the world a greater favor by teaching others how to achieveE the job security that you enjoy than by asking us to simply trust youpH with no evidence. The act of teaching alone would provide more creedence# than all the trust you can beg for.d  # > I'm not employed to fix marketinge	 > issues.a  D I sure hope someone is - AND SOON! This is beyond a circus - this is more like kindergarten!w   ( > You're entitled to your point of view.   ...as are you.   -- V David J. Dachtera9 dba DJE Systemsn http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/p   ------------------------------  # Date: Fri, 07 Sep 2001 01:23:45 GMTOL From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr")> Subject: Re: VMS To Be Squeezed Out Of HP's Strategic Vision ?8 Message-ID: <00A01A89.8748ED67@SSRL04.SLAC.STANFORD.EDU>  [ In article <3B98221C.684E6E4D@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:o >Nic Clews wrote:h >> g >> Jerry Leslie wrote: >> >) >> >    HP to have merger map in 100 dayse >> >    By Michael Kanellos # >> >    Staff Writer, CNET News.come' >> >    September 5, 2001, 5:15 p.m. PTi
 >> >>    .L >> >    HP's transition plan will have to tackle a number of issues. BecauseJ >> >    of the merger, HP finds itself responsible for supporting multipleJ >> >    server operating systems, for example: Linux, Windows NT, OpenVMS,= >> >    HP-UX and Compaq's own version of Unix, among others.a >> >L >> >    Eventually, HP will converge toward Linux, NT and Unix, according toN >> >    McDonnell. The challenge will lie in coming up with a product road mapG >> >    that will push customers toward a more streamlined OS portfolio@# >> >    without alienating them..."l >> (F >> The writer is wrong, and you're reading the wrong things into this. > E >The writer is paraphrasing his source. Not as accurate as a quote, INH >grant you, ... I wrote to the columnist and his response indicated thatG >Mr. McDonnell has been made aware of the potentially dire consequences + >of what was attributed as his having said.-  L That was smarter than what I tried.  I tried writing to Jim.McDonnell@hp.com6 and to James.McDonnell@hp.com, both of which bounced.    -- Alan$  O ===============================================================================P0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056.M  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349, STANFORD, CA  94309-0210LO ===============================================================================    ------------------------------  % Date: Thu, 06 Sep 2001 20:47:24 -0500e1 From: "David J. Dachtera" <djesys.nospam@fsi.net>g> Subject: Re: VMS To Be Squeezed Out Of HP's Strategic Vision ?& Message-ID: <3B98272C.9F195BD@fsi.net>   Bill Todd wrote: > 7 > "Nic Clews" <sendspamhere@127.0.0.1> wrote in messager% > news:3B975552.2E1B2DE2@127.0.0.1...n > > Jerry Leslie wrote:D > > > * > > >    HP to have merger map in 100 days > > >    By Michael Kanellos$ > > >    Staff Writer, CNET News.com( > > >    September 5, 2001, 5:15 p.m. PT > > >>    . M > > >    HP's transition plan will have to tackle a number of issues. BecausemK > > >    of the merger, HP finds itself responsible for supporting multipleaK > > >    server operating systems, for example: Linux, Windows NT, OpenVMS,o> > > >    HP-UX and Compaq's own version of Unix, among others. > > >TM > > >    Eventually, HP will converge toward Linux, NT and Unix, according toaK > > >    McDonnell. The challenge will lie in coming up with a product road' > map)H > > >    that will push customers toward a more streamlined OS portfolio$ > > >    without alienating them..." > >/G > > The writer is wrong, and you're reading the wrong things into this.t > > F > > I cannot and will not discuss my sources, but yet again c.o.v. are > > panicking over nothing.c > I > Maybe, maybe not.  For example, a post on the merger forum at tru64.orgY	 > states:c > " > Author: itsover (---.compaq.com) > Date:   09-06-01 03:46 > N > As heared internally from one of the great players, tru64 will be stopped asM > soon as possible and the service support organisation behind compaq will bei, > cutted down to 1/2 or 1/3 of the manpower.E > all central organisations will be set free (marketing, sales etc.).e > J > openvms will be dead also. an outsourcing contract is not in discussion.E > instead a fee to the government will be paid to get rid of this os.   G Y'know, in retrospect, Compaq management destroying its own credibilitya now actually makes sense.w  	 Consider:p  F At HPETS (CETS?), the "HP/Compaq Listens" (yeah, right - and Micro$oftG works!) panel will be asked for assurances of the future of OpenVMS andaG a host of other items. Having blown their credibility to hell, they caneG now issue any old bold-faced lie they want with near-total impunity. No:C one trusts them any farther than one can throw a GS160, so they cant@ pretty much say whatever they want and no one will believe them.  F What's worse is that at this point, no one on either side really cares anymore, or very few of 'em do.p  4 ...which was probably what the "Q" wanted all along.  G So, you see Nic, your technical credibility is probably above reproach.   G However, with regard to the future of OpenVMS, whatever sources you are E unable to cite or quote have no credibility themselves. So, any info.rC they may feed you will be considered horse crap, at best, and utterc fantasy at the very least.  H The only future for OpenVMS that makes *ANY* sense at all at this point,D is for it to become, perhaps, OpenVMS, Inc. - a reincarnation of theF former Digital. Maybe they could even be granted control of the formerB Digital names and marks, unite with DNPG and do business under theH |d|i|g|i|t|a|l| moniker, but such practice would be ill-advised at best,) given history - past, recent and current.r   -- j David J. Dachterad dba DJE Systemsn http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/b   ------------------------------  % Date: Thu, 06 Sep 2001 21:35:25 -0400r- From: JF Mezei <jfmezei.spamnot@videotron.ca>s> Subject: Re: VMS To Be Squeezed Out Of HP's Strategic Vision ?, Message-ID: <3B98245B.A05D2539@videotron.ca>   Bill Todd wrote:& > > Capellas has been made irrelevant. > 8 > Not if the merger fails, as seems increasingly likely.  N If the merger fails, I suspect (and would hope) that Ben Rosen would work hardM to find a replacement for Capellas. It didn't take much for the folks to kick:H Pfeiffer out. Of course, now that they know that nobody is interested in6 taking the job, they hesitate in kicking Capellas out.  M But I would hope that they have been working behind the scenes to try to finde a suitable CEO for Compaq.  I Actually, I just had a wonderful idea. Apple should buy Compaq. Now, thatpI would make Billy Gates worry a little. With Apple-VMS and Apple-Tru74 andSJ Apple-NSK Apple will have true presence in the enterprise space. Apple hasL vision and energy and they also have independance from Microsoft. And with aM presence in the enterprise space, the Macintosh might get much greater marketf share for desktops.    ------------------------------  % Date: Thu, 06 Sep 2001 21:10:19 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>e> Subject: Re: VMS To Be Squeezed Out Of HP's Strategic Vision ?' Message-ID: <3B982C8B.24C73EDC@fsi.net>c   JF Mezei wrote:  >  > Bill Todd wrote:( > > > Capellas has been made irrelevant. > >n: > > Not if the merger fails, as seems increasingly likely. > P > If the merger fails, I suspect (and would hope) that Ben Rosen would work hardO > to find a replacement for Capellas. It didn't take much for the folks to kick J > Pfeiffer out. Of course, now that they know that nobody is interested in8 > taking the job, they hesitate in kicking Capellas out. > O > But I would hope that they have been working behind the scenes to try to finde > a suitable CEO for Compaq.   I'll take the job.  G ...and then everyone grit your teeth and hang on, 'cuz we'll take AlphaeF *AND* VMS to places that no one has yet even dreamed of! Look out WallH Street - d'ya ever see a company's stock triple (upward!) in a matter of seconds?   --   David J. Dachtera, dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/l   ------------------------------  $ Date: Thu, 6 Sep 2001 19:45:46 -0400; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>l5 Subject: Re: Why continue with VMS - new hope, indeedS$ Message-ID: <3b980aff$1@news.si.com>  < >Btw, Gartner predicts that the merger will most likely failD >(probability 0.6) and that even if it gets past the regulators only% >Compaq/HPs competitors will benefit.n  L No, the top execs of Compaq will also benefit, because they'll get big bucks for sinking their ship.n --A Brian Tillman                   Internet: tillman_brian at si.com A Smiths Aerospace                          tillman at swdev.si.comh= 3290 Patterson Ave. SE, MS      Addresses modified to preventm< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  $ Date: Thu, 6 Sep 2001 15:03:27 -04005 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>h@ Subject: Re: Will Mozilla ever run without crashing DECW server?0 Message-ID: <HMPl7.45$wn4.1621@news.cpqcorp.net>  < Can you do a anal/image on the decw$server_ddx_gy.exe image?  J A copy plane was done, which dispatched to the CFB DDX, which *looks* likeG it did a punt on it... but it makes no sense offhand, since *something*a! looks like it called FatalError()d   Is Open3D installed?   _Fredg  . Brian Schenkenberger, VAXman- wrote in message' <00A01A1F.5D3A9E1B@SendSpamHere.ORG>...2F >In article <9n6vkd$k27@gap.cco.caltech.edu>, vance@alumni.caltech.edu (Vance R. Haemmerle) writes:2 >>In article <00A019AC.56F7772D@SendSpamHere.ORG>,@ >>Brian Schenkenberger, VAXman- <system@SendSpamHere.ORG> wrote: >>>c> >>>As for the SYS$MANAGER:DECW$SERVER_0_ERROR.LOG, here it is: >>>f5 >>> 4-SEP-2001 23:19:20.1 Hello, this is the X serveraH >>>This is the DECwindows X11 display server for OpenVMS AXP V7.1-990529' >>> compiled on May 29 1999 at 12:43:24  >>>Main address = 00028770 >> >>[...]s >>- >>>Activating extension image DECW$SVEXT_glx,a. >>>extension name: glx, entry address 006301801 >>>Activating extension image DECW$SVEXT_X3D_PEX,K2 >>>extension name: X3D-PEX, entry address 007242D83 >>>Activating extension image DECW$SVEXT_decstereo,o4 >>>extension name: decstereo, entry address 007E6058 >> >>[...]o >>4 >>>DECWINDOWS DigitalEquipmentCorp. AXP, Release 7.18 >>>Shareable Image DDX GY, InitOutput loaded at 00A030B0 >> >>[...]e >>B >>>Screen 0: depth 24, vclass PseudoColor not allowed, using 8-bit PseudoColoroH >>>Screen 0  sfb+/TGA  revision # 4   32 bits/pixel  16719296 bytes VRAM' >>>Compiled on May 29 1999, at 12:49:39l7 >>>ffbvmsScreenInit: Call the Default Colormap Creationh0 >>>ffbvmsScreenInit: Exit from init with success$ >>>glScreenInit: Drawlib not loaded.' >>>GLExtensionInit: glScreenInit failede& >>>tm_device_init: Drawlib not loaded.* >>>PexExtensionInit: DD_DEVICE_INIT failed >> >>[...]  >>3 >>> 4-SEP-2001 23:19:32.3 Calling the dispatcher...tJ >>> 5-SEP-2001 10:17:39.6 Connection d1c8830 is closed by Txport (status = 20e4)s >>> 5-SEP-2001 15:38:00.6e >>>Fatal server error: >>> 5-SEP-2001 15:38:00.7 0 >>> 5-SEP-2001 15:38:00.8 %SYSTEM-F-ABORT, abort >>>VK >>>Unrecoverable server internal error (error code = 44) found, terminatingt all connections. >>A >>>Again, OpenVMS V7.2-1, TCP/IP V5.0A, ZXLp-E3, 384MB of memory.o >>L >>  I see you have Open3D installed (from the extensions).  What version areH >>you running?  It looks like OpenGL and PEX have problems initializing. >>E >>  The version which last "supports" the ZXLp-E3 is 4.4, but that isoH >>only supported on OpenVMS V7.1 et. al.  Of course, I'm not sure if theK >>hardware support for the ZLXp-Ex is latent in the 4.9x versions so it maye" >>have no bearing on your crashes. >sH >Hmm.  I'll wait to hear from Fred or Hoff on this but you may be right. >.I >I'm getting tired of this non-supported graphics game in VMS.  I've beenrI >on a search for a year for a "supported" adapter for a 1200 and now it'seJ >looking like one that *was* supported (shipped with the unit in fact) may >no longer supported.  >aI >DEC -> CPQ -> HP... Alpha euthanasia... questionable graphics support... J >You've really got to love VMS to stick with it in light of all this crap! >--e3 >VAXman- OpenVMS APE certification number: AAA-0001- VAXman(at)TMESIS(dot)COM > J >  "And of course, I'm a genius, so people are naturally drawn to my fieryJ >  intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbes >-   ------------------------------  $ Date: Thu, 6 Sep 2001 03:17:29 -0400+ From: "Roy Nicholas" <roy.nicholas@rcn.com>h- Subject: Re: WSJ reporting HP will buy Compaqw+ Message-ID: <9n9696$n6v$1@bob.news.rcn.net>   ? "Terry C. Shannon" <terryshannon@mediaone.net> wrote in messagef7 news:HAql7.19496$zj5.4848264@typhoon.ne.mediaone.net...h >oF > Yep, three years is about right. Re,mber the Sculptor Project Enrico killed/n > 1 No, I don't remember anything about that project.f   ------------------------------   End of INFO-VAX 2001.497 ************************