1 INFO-VAX	Sun, 16 Jun 2002	Volume 2002 : Issue 331       Contents:< Re: "We stay with VMS because we have forgotten that we have@ Re: "We stay with VMS because we have forgotten that we have it"@ Re: "We stay with VMS because we have forgotten that we have it"@ Re: "We stay with VMS because we have forgotten that we have it" %DRA,RWMBX TIMEOUT Re: 8400 (MS7CC-FU) problems?  A Clarification re: VACS# Re: A [departure from] VMS Disaster  Re: Affinity and Itanic 3 Re: Another analyst says VMS port won't be finished 3 Re: Another analyst says VMS port won't be finished # Re: Carly was here in ZKO yesterday  Re: COE, ODS-5 and Spiralog. Re: COE, ODS-5 and Spiralog. Re: COE, ODS-5 and Spiralog. DUMPING !: AS1000a@ Re: Fastest CD-R or CD-RW capabilities for burning under OpenVMS Re: Linus' comments about VMS  Re: Linus' comments about VMS D Major kernel bug found in Linux!  VMS kernel remains bulletproof ...H Re: Major kernel bug found in Linux!  VMS kernel remains bulletproof ..., Re: My conversation with Linus about VMS ..., Re: My conversation with Linus about VMS ..., Re: My conversation with Linus about VMS ... Re: Open Letter to HP  Re: Open Letter to HP  Re: Open Letter to HP  Re: Open Letter to HP ; Re: Secure HTTP client app buildable under OpenVMS/OpenSSL? 2 Re: SSH v2 (was Re: OpenVMS, Volume Desktop OS...) Re: unix history Re: unix historyH Re: unix history (was: RE: OpenVMS, Volume Desktop OS (Re: Mark Gorham's Re: VMS advertising suggestion Re: VMS advertising suggestion Re: VMS advertising suggestion Re: volume not software enabled ' Re: Why is Compaq memory so expensive ?  Windoze woes 13 Windoze woes 2 ... XP blue screen of you know what! 2 Windoze woes 3 - Micro$oft sends nimda to S. Korea Re: __asm__ in DEC CXX Re: __asm__ in DEC CXX Re: __asm__ in DEC CXX Re: __asm__ in DEC CXX  F ----------------------------------------------------------------------  # Date: Sat, 15 Jun 2002 18:24:49 GMT # From: "John Smith" <a@nonymous.com> E Subject: Re: "We stay with VMS because we have forgotten that we have G Message-ID: <RDLO8.27868$831.3282@news01.bloor.is.net.cable.rogers.com>   F "Phillip Helbig" <HELBPHI@sysdev.deutsche-boerse.com> wrote in message5 news:01KIXMIT925S96WTPR@sysdev.deutsche-boerse.com... K >> More seriously, a commercial in which a customer says "we haven't bought G > anything from the vendor in 10 years" and the vendor says "that's the I > kind of customers we like" would cast an interesting light on those who J > sell quality products and those who sell just to make money.  Fade to anJ > accountant who then announces that VMS is the most profitable product in > the vendor's portfolio.     E "More like fade to the customer's accountant who then says, "We audit J hundreds of small/medium/large businesses annually, and of those, the onesD that run Alpha/VMS have the lowest cost of total cost of ownership."  D Then voiceover to, "Alpha & OpenVMS. It's like money in the bank for/ businesses of all sizes. Only from the New HP"" ) (c) 2002, John Smith. All rights reserved    ------------------------------  % Date: Sat, 15 Jun 2002 22:34:24 +0200 " From: "Hans Vlems" <hvlems@iae.nl>I Subject: Re: "We stay with VMS because we have forgotten that we have it" 5 Message-ID: <aeg7to$5u9it$1@ID-143435.news.dfncis.de>   J At least you're on Alpha's. I run VAX Stations, a 2000, two 3100's and two 4000's. G The youngest is probably twice the age of your hardware, so why are you  complaining <g> K OTOH these systems are mine and there's no way I could afford a maintenance 	 contract. ; Thank you DEC for designing and building reliable hardware.   1 Jay E. Morris <jem@epsilon3.com> wrote in message % news:3D0B7758.7040704@epsilon3.com...  > Hans Vlems wrote:  > > Sue, > > H > > most if not all VMS customers will react like that, especially those that > > run VAX/VMS.G > > The confidence and trust in the engineering quality of software and  hardware > > is difficult9 > > to match. I doubt that IBM customers even come close. J > > It is astounding that these attributes have not been commercially used to > > advantage. > >  > > Hans VlemsK > > (now only running VMS at home, so I'm technically no longer a customer)  > H > Well, actually I hate it.  Damn hardware, software.  I hate it becauseJ > it runs so well.  Been trying to convince them for 4 years to upgrade myJ > 2100/1000.  But no, damn stuff never breaks, never crashes so they don't! > see any reason to upgrade. Bah!  > I > (But the databases have gotten so large that I convinced them we needed G > SDLT to cut down our backup time, and of course we just HAD to have a G > better server for the tape library, and we just ....  Stuff should be  > here in a couple weeks!) >  > -- > Jay E. Morris  > System Software Specialist > Brooks AFB, TXE > ANYA: I found one of those 24-hour places for coffee. Remember that G > bookstore? Well they became one of those books-and-coffee places, and @ > now they're just coffee. It's like evolution, only without the > getting-better part.
 > -----------  >    ------------------------------  # Date: Sat, 15 Jun 2002 21:44:04 GMT ( From: "Jay E. Morris" <jem@epsilon3.com>I Subject: Re: "We stay with VMS because we have forgotten that we have it" + Message-ID: <3D0BB40F.4000509@epsilon3.com>    Hans Vlems wrote: L > At least you're on Alpha's. I run VAX Stations, a 2000, two 3100's and two	 > 4000's. I > The youngest is probably twice the age of your hardware, so why are you  > complaining <g> M > OTOH these systems are mine and there's no way I could afford a maintenance  > contract. = > Thank you DEC for designing and building reliable hardware.  > 3 > Jay E. Morris <jem@epsilon3.com> wrote in message ' > news:3D0B7758.7040704@epsilon3.com...  >  >>Hans Vlems wrote:  >> >>>Sue,  >>> G >>>most if not all VMS customers will react like that, especially those  >> > that >  >>>run VAX/VMS. F >>>The confidence and trust in the engineering quality of software and >>
 > hardware >  >>>is difficult 8 >>>to match. I doubt that IBM customers even come close.I >>>It is astounding that these attributes have not been commercially used  >> > to > 
 >>>advantage.  >>> 
 >>>Hans Vlems J >>>(now only running VMS at home, so I'm technically no longer a customer) >>H >>Well, actually I hate it.  Damn hardware, software.  I hate it becauseJ >>it runs so well.  Been trying to convince them for 4 years to upgrade myJ >>2100/1000.  But no, damn stuff never breaks, never crashes so they don't! >>see any reason to upgrade. Bah!  >>I >>(But the databases have gotten so large that I convinced them we needed G >>SDLT to cut down our backup time, and of course we just HAD to have a G >>better server for the tape library, and we just ....  Stuff should be  >>here in a couple weeks!) >>  G Well, yes, but that is at work.  In the garage I have the 2000 and the  A 3100.  Oh, and the odd 5000.  I do have a line on a AS800 though.    --  
 Jay E. Morris  Epsilon 3 Productions  jem@epsilon3.comD ANYA: I found one of those 24-hour places for coffee. Remember that F bookstore? Well they became one of those books-and-coffee places, and ? now they're just coffee. It's like evolution, only without the   getting-better part. -----------    ------------------------------  % Date: Sun, 16 Jun 2002 00:41:43 +0200 - From: Didier Morandi <Didier.Morandi@Free.fr> I Subject: Re: "We stay with VMS because we have forgotten that we have it" ' Message-ID: <3D0BC2A6.5C1FFF72@Free.fr>    ha ha ha :-)    D.   Hans Vlems wrote:  > 
 > Phillip, > K > a rational answer like that is beyond Didier, or any other real frenchman  > :-)    ------------------------------  # Date: Sun, 16 Jun 2002 05:04:02 GMT ) From: Carl Bennett <vze35kfz@verizon.net>  Subject: %DRA,RWMBX TIMEOUT * Message-ID: <3D0C1D00.1080404@verizon.net>  & --------------0400070606050907050307009 Content-Type: text/plain; charset=us-ascii; format=flowed  Content-Transfer-Encoding: 7bit   I     I do phone in tech support for a VAR and was working with someone on  I an alphaserver 1200 running OVMS 7.1, 768 Mb Ram, 6 * 4.3 Gb Scsi drives  ) on a KZPAC-CA 3 Channel raid controller.. E     In November, the system locked up with a %DRA error that we were  F never able to track down.. except that it did it again last week, and H whenever this happens, the only thing she can do to get into the system I is a hard reboot, as everything locks up,, makes troubleshooting it over  E the phone almost impossible... the only other record that we have of  E this kind of error popping up was from about five years ago, and was  H fixed by bumping up defmbxmsgquo to about 10,000.. this system has that 3 set at 64,000 (max) so it's not really an option... C     didn't know if anyone else had ever seen this kind of an error  I before... I will prob bring Compaq in on it direct next week, but I know  H that they will balk at the old firmware.. v5.1-3 and will probably want 3 that upgraded before getting too deeply involved... B     anyway, would appreciate any insight that anyone might have...     Carl Bennett carltbennett@yahoo.com      ) FAA$ write sys$output f$getsyi("HW_Name")  AlphaServer 1200 5/533 4MB1 FAA$ write sys$output f$getsyi("Console_version")  V5.1-31 FAA$ write sys$output f$getsyi("palcode_version")  1.19-14  FAA$ mc sysman io show bus   / %SYSMAN-I-OUTPUT, command execution on node FAA    : _Bus__________Node_TR#__Name____________Base CSR__________;     PCI           8    3    PCI/SCSI       FFFFFFFF81FE2000 ;     PCI           16   3    PCI/SCSI       FFFFFFFF81FE4000 ;     PCI           24   3    PCI/SCSI       FFFFFFFF81FE6000 ?         XBUS          0    6    System Board   FFFFFFFF81FF4000 ?         XBUS          1    6    Floppy         FFFFFFFF81FF4000 ?         XBUS          2    6    Parallel Port  FFFFFFFF81FF4000 ?         XBUS          3    6    Serial Port    FFFFFFFF81FF4000 ;     PCI           24   4    PCI/NI         FFFFFFFF8221C000 ;     PCI           32   4    PCI/RAID       FFFFFFFF8221E000 9   MC_BUS        1    2    Unknown device 0000000000000000  FAA$ sh cpu /full    ! FAA, a AlphaServer 1200 5/533 4MB H Multiprocessing is DISABLED. Uniprocessing synchronization image loaded.0 Minimum multiprocessing revision levels: CPU = 1    System Page Size = 8192  System Revision Code =! System Serial Number = BT00000000  Default CPU Capabilities: "         System:         QUORUM RUN Default Process Capabilities: "         System:         QUORUM RUN    PRIMARY CPU = 00    CPU 00 is in RUN state/ Current Process: _RTA1:          PID = 000004B4  Serial Number:	 Revision: ( VAX floating point operations supported.8 IEEE floating point operations and data types supported. Processor is Primary Eligible.  PALCODE: Revision Code = 1.19-01#          PALcode Compatibility = 14 &          Maximum Shared Processors = 4<          Memory Space:  Physical address = 00000000 00000000"                         Length = 0<          Scratch Space: Physical address = 00000000 00000000"                         Length = 0 Capabilities of this CPU: *         System:         PRIMARY QUORUM RUN- Processes which can only execute on this CPU: C         NETACP           PID = 0000008E  Reason: PRIMARY Capability 
 FAA$ sh dev d    G Device                  Device           Error    Volume         Free   	 Trans Mnt G  Name                   Status           Count     Label        Blocks  	 Count Cnt I DSA0:                   Mounted              0  OVMS71         3797970     403   1 ? DSA1:                   Mounted              0  FAALIV           1972305    40   1 . $1$DKA500:       (FAA)  Online wrtlck        0A $1$DRA0:         (FAA)  ShadowSetMember      0  (member of DSA0:) A $1$DRA1:         (FAA)  ShadowSetMember      0  (member of DSA1:) ? $1$DRA2:         (FAA)  Mounted              0  FAAALT           2227860     2   1 A $1$DRA3:         (FAA)  ShadowSetMember      0  (member of DSA0:) A $1$DRA4:         (FAA)  ShadowSetMember      0  (member of DSA1:) ? $1$DRA5:         (FAA)  Mounted              0  FAAALT2          1956627     1   1 . $1$DRMA0:        (FAA)  Online               0. $1$DVA0:         (FAA)  Online               0  & --------------040007060605090705030700) Content-Type: text/html; charset=us-ascii  Content-Transfer-Encoding: 7bit    <html> <head> </head>  <body>W &nbsp;&nbsp; &nbsp;I do phone in tech support for a VAR and was working with someone on H an alphaserver 1200 running OVMS 7.1, 768 Mb Ram, 6 * 4.3 Gb Scsi drives. on a KZPAC-CA 3 Channel raid controller.. <br>Y &nbsp;&nbsp;&nbsp; In November, the system locked up with a %DRA error that we were never H able to track down.. except that it did it again last week, and wheneverH this happens, the only thing she can do to get into the system is a hardH reboot, as everything locks up,, makes troubleshooting it over the phoneM almost impossible... the only other record that we have of this kind of error R popping up was from about five years ago, and was fixed by bumping up defmbxmsgquoM to about 10,000.. this system has that set at 64,000 (max) so it's not really  an option... <br> [ &nbsp;&nbsp;&nbsp; didn't know if anyone else had ever seen this kind of an error before... H I will prob bring Compaq in on it direct next week, but I know that theyK will balk at the old firmware.. v5.1-3 and will probably want that upgraded * before getting too deeply involved... <br>V &nbsp;&nbsp;&nbsp; anyway, would appreciate any insight that anyone might have... <br> <br> <br> Carl Bennett<br>h <a class="moz-txt-link-abbreviated" href="mailto:carltbennett@yahoo.com">carltbennett@yahoo.com</a> <br> <br> <br> <br>P <font size="2" face="Arial">FAA$ write sys$output f$getsyi("HW_Name")</font><br>A <font size="2" face="Arial">AlphaServer 1200 5/533 4MB</font><br> X <font size="2" face="Arial">FAA$ write sys$output f$getsyi("Console_version")</font><br>- <font size="2" face="Arial">V5.1-3</font><br> X <font size="2" face="Arial">FAA$ write sys$output f$getsyi("palcode_version")</font><br>. <font size="2" face="Arial">1.19-14</font><br>A <font size="2" face="Arial">FAA$ mc sysman io show bus</font><br> - <font size="2" face="Arial">&nbsp;</font><br> V <font size="2" face="Arial">%SYSMAN-I-OUTPUT, command execution on node FAA</font><br>- <font size="2" face="Arial">&nbsp;</font><br> H <font size="2" face="Arial">_Bus__________Node_TR#__Name____________Base CSR__________</font><br> <font size="2" face="Arial">&nbsp;&nbsp;&nbsp; PCI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8&nbsp;&nbsp;&nbsp; 3&nbsp;&nbsp;&nbsp; PCI/SCSI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FFFFFFFF81FE2000</font><br>  <font size="2" face="Arial">&nbsp;&nbsp;&nbsp; PCI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 16&nbsp;&nbsp; 3&nbsp;&nbsp;&nbsp; PCI/SCSI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FFFFFFFF81FE4000</font><br> <font size="2" face="Arial">&nbsp;&nbsp;&nbsp; PCI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24&nbsp;&nbsp; 3&nbsp;&nbsp;&nbsp; PCI/SCSI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FFFFFFFF81FE6000</font><br> <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; XBUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; 6&nbsp;&nbsp;&nbsp; System Board&nbsp;&nbsp; FFFFFFFF81FF4000</font><br>  <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; XBUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; 6&nbsp;&nbsp;&nbsp; Floppy&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FFFFFFFF81FF4000</font><br>  <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; XBUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp; 6&nbsp;&nbsp;&nbsp; Parallel Port&nbsp;  FFFFFFFF81FF4000</font><br>  <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; XBUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3&nbsp;&nbsp;&nbsp; 6&nbsp;&nbsp;&nbsp; Serial Port&nbsp;&nbsp;&nbsp;  FFFFFFFF81FF4000</font><br>  <font size="2" face="Arial">&nbsp;&nbsp;&nbsp; PCI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24&nbsp;&nbsp; 4&nbsp;&nbsp;&nbsp; PCI/NI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FFFFFFFF8221C000</font><br> <font size="2" face="Arial">&nbsp;&nbsp;&nbsp; PCI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 32&nbsp;&nbsp; 4&nbsp;&nbsp;&nbsp; PCI/RAID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FFFFFFFF8221E000</font><br> <font size="2" face="Arial">&nbsp; MC_BUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp; Unknown device 0000000000000000</font><br>8 <font size="2" face="Arial">FAA$ sh cpu /full</font><br>- <font size="2" face="Arial">&nbsp;</font><br>IH <font size="2" face="Arial">FAA, a AlphaServer 1200 5/533 4MB</font><br>V <font size="2" face="Arial">Multiprocessing is DISABLED. Uniprocessing synchronization image loaded.</font><br>H <font size="2" face="Arial">Minimum multiprocessing revision levels: CPU = 1</font><br>- <font size="2" face="Arial">&nbsp;</font><br>V> <font size="2" face="Arial">System Page Size = 8192</font><br>= <font size="2" face="Arial">System Revision Code =</font><br>pH <font size="2" face="Arial">System Serial Number = BT00000000</font><br>@ <font size="2" face="Arial">Default CPU Capabilities:</font><br> <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; System:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; QUORUM RUN</font><br>D <font size="2" face="Arial">Default Process Capabilities:</font><br> <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; System:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; QUORUM RUN</font><br>- <font size="2" face="Arial">&nbsp;</font><br>s7 <font size="2" face="Arial">PRIMARY CPU = 00</font><br>d- <font size="2" face="Arial">&nbsp;</font><br>n= <font size="2" face="Arial">CPU 00 is in RUN state</font><br>1 <font size="2" face="Arial">Current Process: _RTA1:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PID = 000004B4</font><br>e5 <font size="2" face="Arial">Serial Number:</font><br>_0 <font size="2" face="Arial">Revision:</font><br>O <font size="2" face="Arial">VAX floating point operations supported.</font><br>mI <font size="2" face="Arial">IEEE floating point operations and data types  supported.</font><br>hE <font size="2" face="Arial">Processor is Primary Eligible.</font><br>sG <font size="2" face="Arial">PALCODE: Revision Code = 1.19-01</font><br>mr <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PALcode Compatibility = 14</font><br>u <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Maximum Shared Processors = 4</font><br> | <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Memory Space:&nbsp; Physical address = 00000000 00000000</font><br>o <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length = 0</font><br>w <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Scratch Space: Physical address = 00000000  00000000</font><br>l <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length = 0</font><br>@ <font size="2" face="Arial">Capabilities of this CPU:</font><br> <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; System:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PRIMARY QUORUM RUN</font><br>T <font size="2" face="Arial">Processes which can only execute on this CPU:</font><br> <font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NETACP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PID = 0000008E&nbsp; Reason: PRIMARY Capability</font><br>l4 <font size="2" face="Arial">FAA$ sh dev d</font><br>- <font size="2" face="Arial">&nbsp;</font><br>3 <font size="2" face="Arial">Device&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Device&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Error&nbsp;&nbsp;&nbsp; V Volume&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Free&nbsp; Trans Mnt</font><br> <font size="2" face="Arial">&nbsp;Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Count&nbsp;&nbsp;&nbsp;&nbsp;IK Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Blocks Count Cnt</font><br>s <font size="2" face="Arial">DSA0:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mounted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ro 0&nbsp; OVMS71&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3797970&nbsp;&nbsp; 403&nbsp;&nbsp; 1</font><br>  <font size="2" face="Arial">DSA1:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mounted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;et 0&nbsp; FAALIV&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1972305&nbsp;&nbsp;&nbsp; 40&nbsp;&nbsp; 1</font><br> <font size="2" face="Arial">$1$DKA500:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (FAA)&nbsp; Online wrtlck&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</font><br> <font size="2" face="Arial">$1$DRA0:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (FAA)&nbsp; ShadowSetMember&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;$ 0&nbsp; (member of DSA0:)</font><br> <font size="2" face="Arial">$1$DRA1:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (FAA)&nbsp; ShadowSetMember&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;$ 0&nbsp; (member of DSA1:)</font><br> <font size="2" face="Arial">$1$DRA2:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (FAA)&nbsp; Mounted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;y 0&nbsp; FAAALT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2227860&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp; 1</font><br>e <font size="2" face="Arial">$1$DRA3:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (FAA)&nbsp; ShadowSetMember&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;$ 0&nbsp; (member of DSA0:)</font><br> <font size="2" face="Arial">$1$DRA4:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (FAA)&nbsp; ShadowSetMember&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;$ 0&nbsp; (member of DSA1:)</font><br> <font size="2" face="Arial">$1$DRA5:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (FAA)&nbsp; Mounted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t 0&nbsp; FAAALT2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1956627&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp; 1</font><br> <font size="2" face="Arial">$1$DRMA0:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (FAA)&nbsp; Online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</font><br> <font size="2" face="Arial">$1$DVA0:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (FAA)&nbsp; Online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;. 0</font><br> </body>  </html>u  ( --------------040007060605090705030700--   ------------------------------    Date: 15 Jun 2002 22:28:31 -06009 From: kaplow_r@eisner.encompasserve.org.mars (Bob Kaplow) & Subject: Re: 8400 (MS7CC-FU) problems?3 Message-ID: <DvZVswDQX+Hv@eisner.encompasserve.org>t  i In article <55f85d77.0206140526.4e38612e@posting.google.com>, P.Young@unsw.EDU.AU (Patrick Young) writes::5 > Looking at my 8400 in detail I am starting to think.< > it is the best design of a computer system I've ever seen,= > including many of the Alphas, VAXen and PDPs I've had (that $ > would be going back 21 years now).  E I'd have to agree. The VAX 6000 was nice. The VAX 7000 / AXP 7000 was L better. The 8200/8400/GS60/GS140 even better. And the Wildfire better again.I I've always been impressed with DEC engineering. Just not their marketing D and management. Especially when viewed from the inside for 12 years.    @         You [should] not examine legislation in the light of theD         benefits it will convey if properly administered, but in theF         light of the wrongs it would do and the harm it would cause ifF         improperly administered -- Lyndon Johnson, former President of         the U.S.  1 	26-October, 2001: A day that will live in infamy,4 	Support Freedom: http://www.indefenseoffreedom.org/   ------------------------------  # Date: Sun, 16 Jun 2002 00:31:37 GMT 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> ! Subject: A Clarification re: VACSo' Message-ID: <3D0BE01C.40D318F2@fsi.net>e  F Apparently, a lurker/poster on this group misread a post of mine, so I need to clarify:  F An employee of VACS (http://www.vacs-inc.com/) has been auctioning offF some surplus DEC items on eBay. This should *NOT* be construed as VACS$ getting out of the OpenVMS business.  E Per Dick Reichmann, VACS is still in the OpenVMS business (one of the 2 few in metro Chicago with the tenacity to remain).   -- e David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/l   ------------------------------  % Date: Sat, 15 Jun 2002 19:59:32 -0400h1 From: Michael Austin <maustin@firstdbasource.com> , Subject: Re: A [departure from] VMS Disaster2 Message-ID: <3D0BD4E4.D0C2056E@firstdbasource.com>   Atlant Schmidt wrote:" >   > system@SendSpamHere.ORG wrote: > g > > In article <3D09F659.8A954A5E@mindspring.com>, Atlant Schmidt <atlantnospam@mindspring.com> writes:d
 > > >John: > > >_1 > > >Could you please wrap your text to something 3 > > >like 79 columns? Your messages are essentiallyF2 > > >unreadable on my newsreader as they run about# > > >five or six screenwidths wide.4 > > >  > > >Atlant  > > >F > > >0 > > M > > But you have that great unix multi-line editor you've been boasting about ! > > to remedy that situation.  ;)F > 7 > And if I were reading them with tcsh, that'd be true.F3 > But I'm reading them with Netscape, and it hasn'ti > yet bought this clue. :-)  >  > Atlant  B in netscape edit-> preferences-> messages-> wrap at 72 characters.   how hard is that? :) -- 8 Regards,  7 Michael Austin            Registered Linux User #261163 7 First DBA Source, Inc.    http://www.firstdbasource.com  Sr. Consultant 704-947-1089 (Office)s 704-236-4377 (Mobile)a   ------------------------------  % Date: Sat, 15 Jun 2002 20:34:19 -0400g- From: JF Mezei <jfmezei.spamnot@videotron.ca>S  Subject: Re: Affinity and Itanic, Message-ID: <3D0BDD03.522A5B3A@videotron.ca>   Bob Ceculski wrote:cD > no, because Intel was smart in getting the Alpha team and EV8-9 soD > they have something to fall back on just in case ... if the Itanic@ > Epic boat anchor hits an iceberg, then they can just use EV8-9F > technology, hpux can have an emulator written, and hp can just tweak    L No. If IA64 doesn't perform, HP will simply have to build machines with moreN CPUs in them and sell them with less profit. IA64 is here to stay, at least asH HP's proprietary chip. Sun was highly succesfull with a chip that wasn'tM bleeding edge. HP would do the same with the IA64 dog it it is able to market # and price its systems appropriatly.i  M Consider the VAX at the end of the 1980s. Had Digital priced and marketed theaM "slower" VAXes very competitively against the new RISC kids on the block,  itP8 would have been able to do to Sun what Sun did to Alpha.  N When HP realises it is stuck with a slow dog chip, it will be most interestingK to see its reaction. Will it be able to become lean and mean and compensate L for its inadequacies with flashy marketing and low prices, or will it fail ?    L Intel will not revive Alpha. Worse case scenario, HP decides to keep the EV7I team and tells them to continue to develop Alpha. But that would mean yet). another eposide of who will port what to what.   ------------------------------  # Date: Sat, 15 Jun 2002 19:11:05 GMT:# From: "John Smith" <a@nonymous.com>0< Subject: Re: Another analyst says VMS port won't be finishedI Message-ID: <djMO8.351771$t8_.34482@news01.bloor.is.net.cable.rogers.com>w  < "Terry C. Shannon" <terryshannon@attbi.com> wrote in message' news:eOJO8.41659$nZ3.10326@rwcrnsc53...9 >2 > J > Wish I could figure out an equally profitable scam, but then there's the5 > little matter of ethics and integrity to deal with.6 >9  L Let's you and I go to HP with a real business proposal - expenses only, withL a contingency fee when we succeed, based on agreed upon metrics of success aL priori. No need to worry about ethics and integrity - it's already built-in.  H But HP **has** to agree to some stringent terms & conditions of positiveJ participation too, else there's a hefty penalty clause that they will have
 to pay to us.e  3 Then, and only then, will we see if HP is for real.h   ------------------------------  % Date: Sat, 15 Jun 2002 20:40:31 -0400e- From: JF Mezei <jfmezei.spamnot@videotron.ca>t< Subject: Re: Another analyst says VMS port won't be finished, Message-ID: <3D0BDE77.BD38CDB1@videotron.ca>   "Terry C. Shannon" wrote:oK > Yes, in my humble opinion HPQ will lose a lot of business thanks to theiru( > nonresponse to the Gartner codswallop.  N As long as the losses are within the range that HP expected, then HP will be a happy puppy.   ------------------------------   Date: 16 Jun 2002 05:22:49 GMT- From: djweath@attglobal.net (Dave Weatherall)x, Subject: Re: Carly was here in ZKO yesterday5 Message-ID: <DTiotGxQ0bj6-pn2-DL0mq969juZW@localhost>a  D On Fri, 14 Jun 2002 10:20:59 UTC, Brass Christof <welcome@spam.not>  wrote:   > Dave Weatherall wrote: > > G > > On Wed, 12 Jun 2002 13:33:32 UTC, "Main, Kerry" <Kerry.Main@hp.com>i
 > > wrote: > >  > > > Dave,r > > >tN > > > >>> If Rational were to port their development suite maybe we could stay > > > on VMS.<<w > > >sN > > > Note - My albeit limited understanding is that Rational's major focus isI > > > now J2EE and java based products. We just did a major RFP (big UNIXuJ > > > shop) here in Canada and the Customer stated they wanted Rational as > > > their development suite. > > >l( > > > However, they also clearly stated:C > > > - J2EE/Java was their future architecture (more future vendor $ > > > independence was reason given)L > > > - all J2EE/Java application development would be done on cheap Windows  > > > based PC's using Rational.@ > > > - all production deployment would be on UNIX based serversF > > > - they had typical dev, test, qa, pre-prod and prod environments > > > defined. > > >_J > > > In other words, in the J2EE/Java world, the development platform canE > > > very easily be different than what is rolled out in production.s > > G > > I take your point Kerry but I don't expect to see Java VM's runningpE > > aircraft any time soon :-) Would be interesting though. Maybe the;, > > Pentagon already has a project  running. > > H > > OTOH if Rational's ADA-95 IDE suite (i.e. Apex) were written in JavaH > > then we could possibly have deployed it on VMS instead of Solaris. I% > > suspect it's mostly C/C++ though.s > D > Why do you think so? There is a long term analysis available from C > Rational that comes to the conclusion that Ada is *at least* two FD > times as productive than C. The author says that C++ might change G > the picture in the future. This is true but in a different direction pB > than the author thought, C++ es even worse. Why should a decent " > company switch from Ada to C++??   Hi Christoff@                      well I might be wrong but I had gained the F impression that they were more geared to C/C++ than anything else. It F might be nothing simpler than the fact that the most of APEX seems to E revolve around the GUI (the only thing that tells you you're on Unix nE is the filename window, with all those "/"s). The member of my group bF who knows Ada quite well tells me that his previous group's experienceF of doing X/Motif in Ada was not striaghtforward. The bindings were notB easy to use. This is not surprising when X seems to be a C thing.   A Maybe I'll ask the Rational man the next time he's in the office.i   -- & Cheers - Dave.   ------------------------------  % Date: Sat, 15 Jun 2002 14:37:24 -0400n From: Everhart <ge@gce.com>s% Subject: Re: COE, ODS-5 and Spiralog.2& Message-ID: <3D0B8964.3040308@gce.com>   David J. Dachtera wrote: > "C.W.Holeman II" wrote:F > 8 >>http://www.openvms.compaq.com/tud/unixportability.htm: >>) >>* V7.3-1 Contents - File System (cont.)n% >>New Filesystem Features: ODS-5 only& >>ODS-5 system disk/ >>Hard links >>Create as usual;! >>$ SET FILE foo. /ENTER=foo.link  >>View link count with >>$ DIRECTORY /LINKCOUNT >>= >>lists COE as having in ODS-5. I thought ODS-5 was Spiralog.& >  > I > "They" never could work the bugs out of Spiralog. ODS-5 is ODS-2.2 withsG > extensions to support UN*X-friendly (Windows "long") filespec.'s, andf > other stuff. >   J Spiralog was not far as I recall notoriously buggy. What was wrong with itF was lack of major performance win over ODS2 and some issues with largeG cluster scalability. That you could not completely fill a logstructurediE filesystem was known from the first. The thing might have been usefultK for environments where almost all activity was write activity (the arm-wave H being that you use enough cache memory and reads never hit the disk) andH DID have the notion that small scratch files might be created, used, andL destroyed without ever hitting disk oxide. That is harder to do with a cacheO system and something like ODS2 in the back, and is a useful trick. There remainnO however numerous other filesystem examples one could adopt. That they generallysF lack file attributes is not an issue. At XQP level, ODS2 knows nothingA basically (aside from being able to store) about file attributes.s   ------------------------------  # Date: Sun, 16 Jun 2002 00:09:53 GMT/1 From: "David J. Dachtera" <djesys.nospam@fsi.net> % Subject: Re: COE, ODS-5 and Spiralog.A' Message-ID: <3D0BDB07.7C9D7098@fsi.net>f   Everhart wrote:i >  > David J. Dachtera wrote: > > "C.W.Holeman II" wrote:n > >c: > >>http://www.openvms.compaq.com/tud/unixportability.htm: > >>+ > >>* V7.3-1 Contents - File System (cont.)c' > >>New Filesystem Features: ODS-5 onlyn > >>ODS-5 system disk> > >>Hard links > >>Create as usualf# > >>$ SET FILE foo. /ENTER=foo.linki > >>View link count with > >>$ DIRECTORY /LINKCOUNT > >>? > >>lists COE as having in ODS-5. I thought ODS-5 was Spiralog.h > >n > >eK > > "They" never could work the bugs out of Spiralog. ODS-5 is ODS-2.2 withfI > > extensions to support UN*X-friendly (Windows "long") filespec.'s, andc > > other stuff. > >n > L > Spiralog was not far as I recall notoriously buggy. What was wrong with itH > was lack of major performance win over ODS2 and some issues with largeI > cluster scalability. That you could not completely fill a logstructureds' > filesystem was known from the first. m   Glen (and Bill),  @ I thought those *WERE* the "bugs" "they" couldn't work out ... ?   -- > David J. Dachteran dba DJE Systemsn http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/L   ------------------------------  # Date: Sun, 16 Jun 2002 04:22:32 GMT;* From: "Bill Todd" <billtodd@metrocast.net>% Subject: Re: COE, ODS-5 and Spiralog.tB Message-ID: <coUO8.241666$%y.21535220@bin4.nnrp.aus1.giganews.com>  < "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message! news:3D0BDB07.7C9D7098@fsi.net...;   ...L  B > I thought those *WERE* the "bugs" "they" couldn't work out ... ?  J The problem is your use of the word "couldn't" rather than "didn't".  It'sF quite a bit like the 'failure' of VMS and Alpha:  it's not that Compaq' *couldn't* make them more successful...f   - bill   ------------------------------  % Date: Sat, 15 Jun 2002 21:50:08 -0400f1 From: "Island (hpaq.net)" <dbturner@islandco.com>s Subject: DUMPING !: AS1000ab/ Message-ID: <ugnrq7qtjdmv68@news.supernews.com>0  " We are dumping these for $400 each   10 left in stock   In pretty good condition   No memory or Diskf   Includes CD ROM CPU (266Mhz)   These use Parity SIMMS (72 pin)A     Buy em whilst they're 'ot !s   Davidn       -- Island Computers US Corp.s 2700 Gregory Streetn Savannah GA 31404b Toll Free: 1-877 636 4332& International: 001 912 447 6622o  Facsimile:      001 912 201 0096 dbturner@hpaq.netn www.hpaq.net   ------------------------------    Date: 15 Jun 2002 16:04:30 -0700& From: jordan@ccs4vms.com (Rich Jordan)I Subject: Re: Fastest CD-R or CD-RW capabilities for burning under OpenVMSs= Message-ID: <cc5619f2.0206151504.5b1ea119@posting.google.com>&  k jordan@ccs4vms.com (Rich Jordan) wrote in message news:<cc5619f2.0206142025.5b37c62d@posting.google.com>...r' > And do you think its possible to makepG > effective use of a really fast (like the 40X burner from Compaq) on a&D > PWD 60au Enhanced like mine, either SCSI or IDE as needed?  Thanks > very much for the info.& >   3 Which should have read PWS 600au Enhanced, sorry...n   ------------------------------  % Date: Sat, 15 Jun 2002 22:36:42 +0200f" From: "Hans Vlems" <hvlems@iae.nl>& Subject: Re: Linus' comments about VMS5 Message-ID: <aeg829$6mg04$1@ID-143435.news.dfncis.de>p  @ Why care what a guy said who made a copy of a someone elses o/s?E Just the fact that he got it going on an i386 hardly makes him as o/s;	 designer.;  2 Brass Christof <welcome@spam.not> wrote in message" news:3D0B34A6.855A8EC7@spam.not... > G Everhart wrote:; > >;< > > I have to wonder if Linus last saw VMS at, say, V2 or V3B > > back when max filename size was 9.3 characters, all uppercase?   [snip]  E > A smart person analyses the concepts and makes a difference betweenrF > what's actual there and what will probably there in the near future.F > He should taken into account that VMS is 10 years younger than UNIX.F > When I started with VMS in 1987 it was like being hit by a lightningG > flash: the first system of real power that has been designed like then > Mac. >n > --@ > According to the Quality Assurance Institute C/C++/ObjC, PERL,A > UNIX (incl. Linux) and Windows/XY are regarded as harmful. Javap2 > is slow and the class library is badly designed.9 > moc dot slupofni at ssarb - please reverse the sequence<   ------------------------------  % Date: Sun, 16 Jun 2002 00:00:03 +0200s' From: Brass Christof <welcome@spam.not>r& Subject: Re: Linus' comments about VMS( Message-ID: <3D0BB8E3.8450CF1D@spam.not>   Hans Vlems wrote:A > B > Why care what a guy said who made a copy of a someone elses o/s?G > Just the fact that he got it going on an i386 hardly makes him as o/s> > designer."  E Good point. The problem is that the original topic of the thread was (F whether Linux could be VMS or vice versa (or was it whether VMS could H have the same development support by open source programmers as Linux?).  A Anyway Linux is there and will stay probably for a certain time.  B I don't see the end of Linux. We have to live with this guy named 	 Torvalds.    -- b? According to the Quality Assurance Institute C/C++/ObjC, PERL, n@ UNIX (incl. Linux) and Windows/XY are regarded as harmful. Java 0 is slow and the class library is badly designed.7 moc dot slupofni at ssarb - please reverse the sequenceb   ------------------------------    Date: 15 Jun 2002 11:57:33 -0700( From: bob@instantwhip.com (Bob Ceculski)M Subject: Major kernel bug found in Linux!  VMS kernel remains bulletproof ... = Message-ID: <d7791aa1.0206151057.230dc7aa@posting.google.com>o  1 AMD says Linux kernel bug affects latest Athlons e   But fixes already available ( By the INQUIRER, 11/06/2002 19:27:29 BST  ? AMD SAID THERE IS A LINUX KERNEL BUG related to cache attributeiB conflicts in newer versions of the Athlon XP and Athlon MP and has= appealed to the Linux Community to help it solve the problem.sC A posting reveals that the problem is related to the use of the AGP A Aperture with Athlon processors but there appear to be short term6# fixes and long term fixes en route.   E A note from Richard Brunner at AMD outlines the problems which happene# mostly when an AGP card is present.w  A But Brunner says that there's a simple short term solution to thei@ problems without major fixes needing implementation in the Linux kernel.t  D There's already a kernel patch available although Brunner points out4 there's still a hole left using this short term fix.  C As far as the long term solution is concerned, AMD also provides anp& experimental patch to fix the problem.  & You can find the posting at this page.  D AMD says in the note that it is "sort of new" to the Linux CommunityA but is giving a lot of detail about the problem so that it can bea fixed quickly.   ------------------------------  % Date: Sat, 15 Jun 2002 22:17:09 +0200j" From: "Hans Vlems" <hvlems@iae.nl>Q Subject: Re: Major kernel bug found in Linux!  VMS kernel remains bulletproof ...i5 Message-ID: <aeg6th$6goio$1@ID-143435.news.dfncis.de>o  @ The bug is hardly new, it's been in there since RH 7.2 came out.  3 Bob Ceculski <bob@instantwhip.com> wrote in messageu7 news:d7791aa1.0206151057.230dc7aa@posting.google.com...i2 > AMD says Linux kernel bug affects latest Athlons >e > But fixes already availablew* > By the INQUIRER, 11/06/2002 19:27:29 BST >DA > AMD SAID THERE IS A LINUX KERNEL BUG related to cache attributefD > conflicts in newer versions of the Athlon XP and Athlon MP and has? > appealed to the Linux Community to help it solve the problem.hE > A posting reveals that the problem is related to the use of the AGPeC > Aperture with Athlon processors but there appear to be short termu% > fixes and long term fixes en route.  >yG > A note from Richard Brunner at AMD outlines the problems which happenp% > mostly when an AGP card is present.@ >dC > But Brunner says that there's a simple short term solution to theyB > problems without major fixes needing implementation in the Linux	 > kernel.  >uF > There's already a kernel patch available although Brunner points out6 > there's still a hole left using this short term fix. > E > As far as the long term solution is concerned, AMD also provides anu( > experimental patch to fix the problem. > ( > You can find the posting at this page. >bF > AMD says in the note that it is "sort of new" to the Linux CommunityC > but is giving a lot of detail about the problem so that it can be> > fixed quickly.   ------------------------------  # Date: Sat, 15 Jun 2002 18:53:10 GMTn# From: "John Smith" <a@nonymous.com>15 Subject: Re: My conversation with Linus about VMS ...cJ Message-ID: <q2MO8.351644$t8_.249693@news01.bloor.is.net.cable.rogers.com>  L And along the lines of  BIFF we get YACC. What was wrong with the 1st or 2ndD compiler compiler that we needed yet another compiler compiler?  :-)        4 "Carl Perkins" <carl@gerg.tamu.edu> wrote in message' news:15JUN200202081498@gerg.tamu.edu... 8 > Atlant Schmidt <atlantnospam@mindspring.com> writes...+ > }"DIRECTORY /NOHEADER /NOTRAILER" takes at7 > }wee bit longer. (Yes, I *KNOW* you can abbreviate itu
 > }somewhat.)  > }o	 > }Atlantc >h5 > "DIRECTORY /NOHEADER /NOTRAILER" -> "DIR/NOHE/NOTR"  >I5 > So a reduction of 56 and 2/3 percent is "somewhat"?n >w> > By the way, how exactly is anyone supposed to determine that; > when they want to see if something is in a file what theyl? > really want to do is "get a regular expression and print" it,t& > which is then abbreviated to "grep"? >mB > How is someone supposed to know what the programmer's dog's name; > was, as that is the origin of the command "biff"? And whys< > wasn't that abbreviated to "bf" to make it match (most of)< > the rest of the single word commands which are abbreviated  > to their first two consonants? >s
 > --- Carl   ------------------------------  # Date: Sat, 15 Jun 2002 18:58:59 GMTb# From: "John Smith" <a@nonymous.com>m5 Subject: Re: My conversation with Linus about VMS ...dH Message-ID: <T7MO8.27941$831.26458@news01.bloor.is.net.cable.rogers.com>  2 "Main, Kerry" <Kerry.Main@hp.com> wrote in messageL news:BE56C50EA024184DAF48F0B9A47F5CF40266078B@kaoexc01.americas.cpqcorp.net. .. Andrew,o  E >>> It isn't the fastest except in Bobs fevered imagination and thats0H the Tru64 JVM, Compaq have never run SPECjbb on OpenVMS which is a major release behind Tru64.<<<  @ OpenVMS JVM performance is now approx +/- 5% of Tru64. Also, TheH production version of Java available today is the same version as Tru64.D OpenVMS JVM is V1.3.1-3 with V1.4 cooking (most developers today are* still on some flavour of V1.3). Reference:. http://www.compaq.com/java/download/index.html  ? Is it the fastest JVM on the market? Don't know. Perhaps not...w  H However, as Sun has shown with Solaris - you certainly do not need to be* the fastest on the block to win Customers.   ------------------  I I don't mind a minor speed penalty given the relative low cost of harwarehJ these days and more importantly, having a robust operating system. Give meL reliability any day - that way I can spend my time more profitably on moving/ my business forward rather than fighting fires.   K In commercial applications, the cost of downtime is far more expensive than0D extracting the last drop of performance. That may not necessarily be= perceived to be the case in academia or in HPTC environments.7   ------------------------------    Date: 15 Jun 2002 16:25:43 -0700( From: bob@instantwhip.com (Bob Ceculski)5 Subject: Re: My conversation with Linus about VMS ...w< Message-ID: <d7791aa1.0206151525.87d090e@posting.google.com>  s "John Smith" <a@nonymous.com> wrote in message news:<T7MO8.27941$831.26458@news01.bloor.is.net.cable.rogers.com>...e4 > "Main, Kerry" <Kerry.Main@hp.com> wrote in messageN > news:BE56C50EA024184DAF48F0B9A47F5CF40266078B@kaoexc01.americas.cpqcorp.net. > ..	 > Andrew,4 > G > >>> It isn't the fastest except in Bobs fevered imagination and thatsWJ > the Tru64 JVM, Compaq have never run SPECjbb on OpenVMS which is a major > release behind Tru64.<<< > B > OpenVMS JVM performance is now approx +/- 5% of Tru64. Also, TheJ > production version of Java available today is the same version as Tru64.F > OpenVMS JVM is V1.3.1-3 with V1.4 cooking (most developers today are, > still on some flavour of V1.3). Reference:0 > http://www.compaq.com/java/download/index.html > A > Is it the fastest JVM on the market? Don't know. Perhaps not...e > J > However, as Sun has shown with Solaris - you certainly do not need to be, > the fastest on the block to win Customers. >  > ------------------ > K > I don't mind a minor speed penalty given the relative low cost of harware L > these days and more importantly, having a robust operating system. Give meN > reliability any day - that way I can spend my time more profitably on moving1 > my business forward rather than fighting fires.  > M > In commercial applications, the cost of downtime is far more expensive than F > extracting the last drop of performance. That may not necessarily be? > perceived to be the case in academia or in HPTC environments.   ; Would you please repeat that, esp. to Andrew and the othersh8 on this board that didn't quite catch on to that yet ...   ------------------------------  # Date: Sat, 15 Jun 2002 19:06:26 GMTt# From: "John Smith" <a@nonymous.com>y Subject: Re: Open Letter to HPJ Message-ID: <SeMO8.351746$t8_.295721@news01.bloor.is.net.cable.rogers.com>  9 "Paul Repacholi" <prep@prep.synonet.com> wrote in messagen' news:87ofec3ilc.fsf@prep.synonet.com...i >aA > So when they say "But that is dead now isn't it?" your reply isCE > "Didn't you watch the F1 GP last night? There where 3 ads on then."f >eH So maybe the logo on the side of the Williams BMW should be changed from 'Compaq' to 'OpenVMS'.  G For the (incremental cost) of a few cans of paint, HP can get the wholewJ world talking about OpenVMS. Everybody already knows the word 'Compaq' andI that they are dead. Why not use the valuable 'mobile billboard' space fort something that makes money?r   ------------------------------  # Date: Sat, 15 Jun 2002 19:50:17 GMTn. From: peter@langstoeger.at (Peter LANGSTOEGER) Subject: Re: Open Letter to HP5 Message-ID: <ZTMO8.253106$305.3550811@news.chello.at>d  p In article <SeMO8.351746$t8_.295721@news01.bloor.is.net.cable.rogers.com>, "John Smith" <a@nonymous.com> writes:I >So maybe the logo on the side of the Williams BMW should be changed from  >'Compaq' to 'OpenVMS'.e  G No. OpenVMS has unfortunately nothing in common with Q's F1 activities.7  L And only the word "OpenVMS" is not enough as an ad. You also need to let theP crowd know that: OpenVMS is an operating system, is from HPQ (previously COMPAQ,L previously DEC) and is much better for enterprise computing (and all others,H too) than all the toys from the competition. Then and only then a simple- reminder "OpenVMS" on the F1 cars can help...s   -- a Peter "EPLAN" LANGSTOEGERf% Network and OpenVMS system specialist  E-mail  peter@langstoeger.atP A-1030 VIENNA  AUSTRIA              I'm looking for (a) Network _and_ VMS Job(s)   ------------------------------  # Date: Sat, 15 Jun 2002 21:25:41 GMT 1 From: "Terry C. Shannon" <terryshannon@attbi.com>) Subject: Re: Open Letter to HP= Message-ID: <phOO8.55832$6m5.43268@rwcrnsc51.ops.asp.att.net>h  ; "Peter LANGSTOEGER" <peter@langstoeger.at> wrote in messageS/ news:ZTMO8.253106$305.3550811@news.chello.at....L > In article <SeMO8.351746$t8_.295721@news01.bloor.is.net.cable.rogers.com>,% "John Smith" <a@nonymous.com> writes:uK > >So maybe the logo on the side of the Williams BMW should be changed fromm > >'Compaq' to 'OpenVMS'.e >gI > No. OpenVMS has unfortunately nothing in common with Q's F1 activities.s >lJ > And only the word "OpenVMS" is not enough as an ad. You also need to let thexJ > crowd know that: OpenVMS is an operating system, is from HPQ (previously COMPAQ,nF > previously DEC) and is much better for enterprise computing (and all others,eJ > too) than all the toys from the competition. Then and only then a simple/ > reminder "OpenVMS" on the F1 cars can help...f  J Before wasting money on television ads, HPQ should demonstrate that it hasK the intestinal fortitude to call clueless and lying analysts just what theyy" are, Armani suits notwithstanding.  & Alas, such fortitude is sadly lacking.   ------------------------------  % Date: Sat, 15 Jun 2002 20:47:08 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>w Subject: Re: Open Letter to HP, Message-ID: <3D0BE003.5068DEAD@videotron.ca>   "Terry C. Shannon" wrote: L > Before wasting money on television ads, HPQ should demonstrate that it hasM > the intestinal fortitude to call clueless and lying analysts just what theyh$ > are, Armani suits notwithstanding.  N No. By doing the public ad on TV, it will kill the fore that the Gartner folksJ have been feeding all these years. They were able to keep the fire burningJ because Compaq and HP refused to publicly acknowledge VMS so they doom and0 gloom predictions for VMS were quite believable.   ------------------------------  % Date: Sat, 15 Jun 2002 21:31:05 -0500f* From: Rich Jordan <rjordan@mindspring.com>D Subject: Re: Secure HTTP client app buildable under OpenVMS/OpenSSL?- Message-ID: <3D0BF869.6090007@mindspring.com>s  E Thanks for the input, all of you.  I'm taking a look at cURL and the dE OpenSSL package to see if we can do a quick and dirty viability test./   Rich   ------------------------------    Date: 15 Jun 2002 16:19:13 -0700( From: bob@instantwhip.com (Bob Ceculski); Subject: Re: SSH v2 (was Re: OpenVMS, Volume Desktop OS...) = Message-ID: <d7791aa1.0206151519.6d72e56a@posting.google.com>r  Q david20@alpha2.mdx.ac.uk wrote in message news:<aefnki$977$1@aquila.mdx.ac.uk>...J > In article <craig.berry-D5C343.14462614062002@news.directvinternet.com>, "Craig A. Berry" <craig.berry@nospam.SignalTreeSolutions.com> writes: > >In article @ > ><craig.berry-DE7718.13465107062002@news.directvinternet.com>,H > > "Craig A. Berry" <craig.berry@nospam.SignalTreeSolutions.com> wrote: > >aJ > >> In article <adqst1$am3$1@aquila.mdx.ac.uk>, david20@alpha2.mdx.ac.uk  > >> wrote:- > >>  Q > >> > I believe Multinet and TCPWARE will shortly (if they do not already) have o) > >> > version 2 SSH clients and servers.g > >> uL > >> v2 is shipping in Multinet.  It looks like it should be in TCPWare any 
 > >> day now.  > >> eS > >> > Dec TCPIP services though, despite frequent requests, seems not to have any  . > >> > firm plans for providing SSH version 2. > >> sI > >> A year ago they had no plans.  Now they have plans, but perhaps not a > >> much more than that yet.  > >4K > >I just noticed on the Process Software site today that they now have an u7 > >SSH product for TCP/IP Services 4.2 and later.  See -J > ><http://www.process.com/tcpip/ssh.html>.  So that's good news, but the H > >cost of an add-on will probably be a real difficulty for some of the C > >places, like universities, that are most eager to implement SSH & > >everywhere. > O > Yes cost maybe an issue. On the otherhand HPQ's DEC TCPIP Services version oflM > SSH v2 when it eventually appears is very unlikely to be backported to worklK > with UCX V4.2 or VMS 6.2. Certainly we have a number of systems which for,+ > various reasons are stuck at that level. yQ > I'll probably be contacting our local distributor Essential Computing in the UK Q > to inquire about the product and whether there are any educational discounts onn	 > Monday.v >  > David Webb > VMS and Unix team leader > CCSS > Middlesex University  D I think Process software gives hobbyist and educational licenses for@ TCPware ... check it out ... it runs crisper than the others ...   ------------------------------  # Date: Sat, 15 Jun 2002 19:30:26 GMTp& From: Bob Willard <BobwBSGS@attbi.com> Subject: Re: unix historyv) Message-ID: <3D0B95E2.B94E7FAC@attbi.com>i   Atlant Schmidt wrote:s >  > Nic Clews wrote: > @ > > ... and we'll get to see how many C applications (on *MANY*,/ > > > *MANY* operating systems *INCLUDING* VMS)a4 > > > mistakenly treated time_t as a signed integer. > >rJ > > Umph..VMS? I think I can quote from the article without being done for > > copyright... > >U@ > > ...With this fix, DEC C RTL time functions will handle times- > >  successfully until 07-Feb-2106 06:28:15.o > >h, > > So please exclude VMS from your list ;-) > 6 > I will freely stipulate to you that the DEC-supplied, > components don't suffer from this problem. > 3 > But please note that I said "C applications", noti3 > C Operating System services or C Run-Time Library 1 > functions. There's plenty more C-code out there-6 > that wasn't written by DEC (etc.); I'll bet at least3 > a few lines of it runs on VMS *AND* treats time_t:4 > as a signed integer. And will probably still do so > on January 19th, 2038. > . > We could always bet a beer on it, payable on > January 20th 2038. :-) >  > Atlant  ? Sorry, Atlant, but they don't allow beer in most nursing homes.  -- n Cheers, Bobp   ------------------------------  % Date: Sat, 15 Jun 2002 22:13:16 +0000i2 From: John Eisenschmidt <jweisen@eisenschmidt.org> Subject: Re: unix historye4 Message-ID: <20020615221316.A31653@eisenschmidt.org>  J Unless the Voices are Mistaken, Paul Sture (p_sture@elias.decus.ch) Wrote:b > In article <aecv8f$304c$1@info.cs.uofs.edu>, bill@triangle.cs.uofs.edu (Bill Gunshannon) writes:2 > > In article <3D09ECEA.898151E7@mindspring.com>,9 > >  Atlant Schmidt <atlantnospam@mindspring.com> writes:  > > |> Nic Clews wrote:i > > |> b) > > |> > UNIX has only 67 years to go :-)  > > |> >' > > |> > VMS has another 290 CENTURIES.- > > |> -9 > > |> Actually, much of the excrement's going to hit the.C > > |> ventilator on Tuesday, January 19, 2038 at GMT 03:14:07 UTC.r@ > > |> The next second, the clock spills over into bit <31>, and; > > |> we'll get to see how many C applications (on *MANY*,t0 > > |> *MANY* operating systems *INCLUDING* VMS)5 > > |> mistakenly treated time_t as a signed integer.T > > I > > Yes, it will.  A quick scan of Linux and FreeBSD shows it to be alongnF > > on both of them.  Because of commonality of much of the codebase IF > > would bet that OpenBSD and NetBSD are the same.  Hmmmm.  What does > > MSDN say??  :-)  > 4 > So which of the BSDs would you recommend, and why?  =Depends on what you're using it for. FreeBSD is generally optimized for x86 and Alpha hardware. NetBSD's goal is to port it to every possible operating platform. OpenBSD's goal is to develop the most secure Unix-like OS that they possibly can. You can get more information at daemon news or at each project's website.r   > __ > Paul Sture
 > Switzerlanda   --  / John W. Eisenschmidt <jweisen@eisenschmidt.org>n6  Homepage URL    | http://www.eisenschmidt.org/jweisenM  PGP Public Key  | http://www.eisenschmidt.org/jweisen/misc/jeisenschmidt.asc D  PGP Fingerprint | 5F9B F916 5AD1 3295 CF99 BC1E 1F97 E6A3 37E3 BEF2  O FOO MANE PADME HUM: "Our first obligation is to keep the FOO counters turning."    ------------------------------  # Date: Sat, 15 Jun 2002 20:59:21 GMT-+ From: Jeff Campbell <jcampbell@ins-msi.com> Q Subject: Re: unix history (was: RE: OpenVMS, Volume Desktop OS (Re: Mark Gorham'sV+ Message-ID: <3D0BA032.750D826D@ins-msi.com>D   Paul Sture wrote:1 > b > In article <aeak8g$1r3b$2@info.cs.uofs.edu>, bill@triangle.cs.uofs.edu (Bill Gunshannon) writes:2 > > In article <3D089C8E.B02155A6@mindspring.com>,9 > >  Atlant Schmidt <atlantnospam@mindspring.com> writes:s > > |>2 > > |> I suspect RT-11 has run out of few as well. > > |> > >lE > > I'm not exactly sure as I have never done anythign with RT11 that E > > really cared wether you set the date and time at all, but I thinkrG > > this is wrong. I think because of how the date was stored it basiclmD > > started with 0 being the year 1900.  Of course, it only held two3 > > digits and thus had a serious Y2K problem.  :-)tD > > I also believe the common way to fix it was to use extra bits toE > > add another digit. But the official way may have been to move thei > > starting date forward. > > M > I seem to remember reading an article in the 1970s about how DEC fudged thepN > date format on RT-11 to cope with it "running out". Never noticed a thing at > the time.L  F There were 2 unused bits in the word format that RT-11 uses to store a date. H These bits are now defined as encoding an epoch. The first epoch started inH 1972, RT-11's date base year. The second epoch will begin in 2004. RT-11 dates are good through 2099.   > C > > As I have said, I have never used a Y2Ked version of RT11 but IeC > > do remember there being a discussion about it on the pdp11 newso > > groups for a while.b > >o >  > __ > Paul Sture
 > Switzerland-  
 Jeff Campbell- n8wxs@arrl.net   ------------------------------  # Date: Sun, 16 Jun 2002 00:06:54 GMT 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>.' Subject: Re: VMS advertising suggestionn' Message-ID: <3D0BDA53.DC361CB6@fsi.net>n   Kenneth Farmer wrote:F > > > "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message# > news:3D0AA057.3D5DC150@fsi.net...o > > Bill Todd wrote: > > >e> > > > "Rob Young" <young_r@encompasserve.org> wrote in message3 > > > news:AOrY43M5jVs6@eisner.encompasserve.org...m > > > >nN > > > >         There is a full page ad in the back of yesterday's Wall Street
 > > > JournalWJ > > > >         Marketplace section page B12.  It features a success story > usingR? > > > >         IBM's iSeries server (OS/400) and Omaha Steaks.2 > > > >tL > > > >         This is the type of ad that would work very well for VMS.  A > big " > > > >         VMS success story. > > >aH > > > And once VMS is running on Itanic, you could show it *cooking* the	 > steaks.  > > J > > ...and by the time that happens (VMS on a viable, ready-for-prime-timeJ > > Itanic), a good number more of us will be asking about that steak, "Do > > you want fries with that?" > 1 > Don't you mean "ready-for-prime-rib" Itanic. :)o  C Well, yeah, I suppose; but does Steak and Shake even do ribeye? ;-)c   -- t David J. Dachtera  dba DJE Systems- http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/:   ------------------------------  % Date: Sat, 15 Jun 2002 22:11:39 -04001- From: JF Mezei <jfmezei.spamnot@videotron.ca> ' Subject: Re: VMS advertising suggestionn, Message-ID: <3D0BF3CC.29727A17@videotron.ca>  	 Scenario:e  K Carly rummaging through an old abandonned attic. Finds a glowing box hiddenBC under a hay stack. Uncovers it to find "VMS". Followed by "oh wow".r   Followed by a catch phrase:a7 "HP understands treasures were not meant to be hidden".c    The new HP, expect more to come.   ------------------------------  # Date: Sun, 16 Jun 2002 03:25:55 GMT 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>m' Subject: Re: VMS advertising suggestionl' Message-ID: <3D0C08F9.9C5D5444@fsi.net>m   JF Mezei wrote:a >  > Scenario:s > M > Carly rummaging through an old abandonned attic. Finds a glowing box hiddenaE > under a hay stack. Uncovers it to find "VMS". Followed by "oh wow".t >  > Followed by a catch phrase:-9 > "HP understands treasures were not meant to be hidden".e > " > The new HP, expect more to come.  
 Truly, a gem!t   -- h David J. Dachteraa dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Sat, 15 Jun 2002 15:52:35 -0700n' From: JMK <jeffrey.m.klopotic@lmco.com>i( Subject: Re: volume not software enabled( Message-ID: <3D0BC533.CE0BB2CF@lmco.com>  @ It could also be something as simple as needing to take the tapeH *completely* out of the tape drive and reinserting it.  If you are usingH the older tape systems, you may need to push the button in after puttingE the tape in the drive, pushing down on the tongue and waiting for the<E tape to mount itself.  (This is for the older TK series tape drives).o  G DEC tape drives are a science unto themselves.  One can make some leveln0 V errors if not proficient in their operation.    
 Jeff Klopotica   ------------------------------  # Date: Sat, 15 Jun 2002 23:53:02 GMTc( From: "C.W.Holeman II" <cwhii5@ACM5.org>0 Subject: Re: Why is Compaq memory so expensive ?? Message-ID: <yrQO8.292$6a.137@newsread1.prod.itd.earthlink.net>n   system@SendSpamHere.ORG wrote:  E > In article <ugmf9ibhrguaa9@news.supernews.com>, "Island (hpaq.net)"i! > <dbturner@islandco.com> writes:n
 >>Even better. >>H >>Most Compaq memory IS Infineon memory with the compaq hologram sticker
 >>added to it: >>6 >>That is the big difference - a 19,200 Euro sticker ! >  > 0 > Wow!  Holograms are that expensive to produce?  . No, just to sell, all that marketing and such.   -- c C.W.Holeman II cwhii5@ACM5.org  remove the fives http://also.as/cwhii   ------------------------------    Date: 15 Jun 2002 11:36:05 -0700( From: bob@instantwhip.com (Bob Ceculski) Subject: Windoze woes 1n= Message-ID: <d7791aa1.0206151036.71ecbf42@posting.google.com>n  - Bundles of holes found in Microsoft software b   Voleware becomes Holeware & By Paul Hales, 13/06/2002 09:28:04 BST    E MICROSOFT MANAGED TO FIND a bunch of holes in its software yesterday,a7 posting warnings of the vulnerabilities on its website.oA One "critical" flaw could allow anyone into an NT, Win 2000 or XP $ system to run any code they fancied.  @ The Vole itself called the problem with its Remote Access Server< 'critical' and posted a patch, which you can find from here.  C Further, Microsoft posted warnings of a couple of problems in SQL'soD handling of XML here. Says the Vole: "Under a daunting scenario, theF vulnerability could provide an attacker with an avenue by which to run! script on another user's system."n  F The company also revealed that servers running its older HTR scripting; were also vulnerable to attack. Here's the gen on that one.   D That brings the total number of dangerous holes discovered this year3 to around 40, we believe. And there's more to come.r  E The question remaining is: is the discovery of these holes proof that E Microsoft is working hard to fix security problems with its software?rC Or was the software shite in the first place, and brought to market 2 too early due to commercial pressures? You decide.   ------------------------------    Date: 15 Jun 2002 11:37:26 -0700( From: bob@instantwhip.com (Bob Ceculski)< Subject: Windoze woes 2 ... XP blue screen of you know what!= Message-ID: <d7791aa1.0206151037.5e1b3cbf@posting.google.com>c  , XP registry bug causes blue screen of death    Maybe no fix for it yet, sorry n( By the INQUIRER, 15/06/2002 10:27:21 BST    F MICROSOFT HAS QUIETLY issued a notice about problems with the registryE that can cause users of XP, both Home and Professional edition to seei. the dreaded blue screen of death on their PCs.C The company says that when "registry hives" get damaged, people may B see the message "Unexpected Shutdown" or the far more friendly andA informative message "Stop: 0cx0000135", resulting in PCs possibly) being a little hard to boot.  A The explanation, says MS, is that programs which use the registrycE don't "cleanly" remove temporary items stored in the registry but theM? problem also can happen if a program is "terminated" (ended) or 2 "experiences a user-mode fault", whatever that is.  B Microsoft has a hotfix that repairs the registry but it is obviousF that it's not a complete fix. The firm recommends that people wait forA the next service pack containing the fix if they're not "severelyr
 affected".  F So the fix may not be a fix, and Microsoft is even prepared to suspendF charging you for a support call if it's convinced it's not your fault.  F And when's the service pack out? Well, you'd better ask Microsoft that question...c   ------------------------------    Date: 15 Jun 2002 11:38:40 -0700( From: bob@instantwhip.com (Bob Ceculski); Subject: Windoze woes 3 - Micro$oft sends nimda to S. Korea = Message-ID: <d7791aa1.0206151038.63fa1ed9@posting.google.com>n  * Microsoft sends Nimda worm to South Korea    It's an own goal O( By the INQUIRER, 14/06/2002 19:32:14 BST    E THAT CONCENTRATED EFFORT to focus on security has obviously paid off. C News.com reports today that Microsoft has accidentally sent out thet@ Nimda worm to South Korean developers with the latest version of Visual Studio .NET.   C Microsoft moved its spin doctor mechanisms into high gear today andh6 claimed that no-one had executed Mr Nimda by accident.  @ Plus the thing wouldn't start being a wormy Nimda because Visual- Studio .NET needs version 6.0 of its browser.-  9 The nematode won't work with that version, says the wire.   E Nevertheless, it is something of a humiliation for the firm, which isrA having the same kind of annus horribilis that Intel had two yearsh back.w   ------------------------------  % Date: Sat, 15 Jun 2002 15:44:19 -0700a' From: JMK <jeffrey.m.klopotic@lmco.com>a Subject: Re: __asm__ in DEC CXXs& Message-ID: <3D0BC343.A70A72@lmco.com>   Larry, Thanks for the response.  D What you point out is valid -- where did the code come from and whatE system am I going to try and run it on.  The choices are tremendous. o@ But, if I want to do assembly on any available platforms, I have resources for that.   F However, I can't find any info on how to invoke assembly on HPQ CXX.    ! Did they yank the capability out?i   TIA,  
 Jeff Klopoticr   ------------------------------    Date: 15 Jun 2002 18:45:30 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)i Subject: Re: __asm__ in DEC CXX 3 Message-ID: <WsfdLZ5O3K2i@eisner.encompasserve.org>n  P In article <3D0BC343.A70A72@lmco.com>, JMK <jeffrey.m.klopotic@lmco.com> writes: > Larry, > Thanks for the response. > F > What you point out is valid -- where did the code come from and whatG > system am I going to try and run it on.  The choices are tremendous. .B > But, if I want to do assembly on any available platforms, I have > resources for that.< > H > However, I can't find any info on how to invoke assembly on HPQ CXX.    G Typically you would call out to a module written in the other language,lG just as if you wanted to do Fortran, Ada, Pascal, PL/I, Basic or Cobol.0  I That way you can have a common C++ module that is portable and individualSJ assembly language programs for the two (going on three) VMS architectures.  C I have one assembly language module in my code, used to make up forlG a deficiency in an Alpha compiler.  But in general when you are running D on VMS, the need to do assembly language should be minimal.  You are8 typically, for instance, unlikely to do better on speed.   ------------------------------  % Date: Sat, 15 Jun 2002 17:58:52 -0700r' From: JMK <jeffrey.m.klopotic@lmco.com>f Subject: Re: __asm__ in DEC CXXo( Message-ID: <3D0BE2CC.581555D7@lmco.com>   Larry, Thanks again for the response.  G I was hoping to find that HPQ's CXX compatibility with other sources ofsG CXX code would work, i.e., early C++, MS, Linux, etc.  By and large, ite= does work except for occaisional glitches like this one here.s  G However, I just did find it in Stroustrup's Special Edition.  I'll haveyD to give it a try.  It seems like it should work.  It wouldn't be theE first time I've discovered an incompatibility.  This could be anotherm one!   Let's see how it works.P   Thanks,I   Jeff   ------------------------------  % Date: Sat, 15 Jun 2002 23:32:30 -0500bC From: "Craig A. Berry" <craig.berry@nospam.SignalTreeSolutions.com>u Subject: Re: __asm__ in DEC CXXiH Message-ID: <craig.berry-DC796E.23323015062002@news.directvinternet.com>  ( In article <3D0A659B.F6DF2485@lmco.com>,)  JMK <jeffrey.m.klopotic@lmco.com> wrote:e  G > I have some C++ code that has some assembler in it, and it appears by E > the conspicuous lack of any reference to assembler in my DEC/Compaqr+ > manuals that ... oh, well, I'd just vent.  > I > How does one invoke what would be an otherwise straightforward assembly  > routine in DEC/Compaq/HP CXX?   G 30 seconds with the docs reveals that there is a mechanism for in-line oH assembly available via "#pragma intrinsic (asm)" though as someone else H pointed out, assembly language is by definition implementation-defined, H so whatever assembly language you've got is unlikely to be VAX or Alpha  assembly language.     You might start with d   $ help cxx language builtin   E and scroll down to the section entitled "Intrinsic functions".  Also eC see Appendix C, "Built-in Functions" in the document "Using Compaq n C++".w   ------------------------------   End of INFO-VAX 2002.331 ************************