1 INFO-VAX	Tue, 22 Nov 2005	Volume 2005 : Issue 651       Contents: $GETDVI suggestions requested " ??==MacOSX burned VMS CD <CR><LF>." ??==MacOSX burned VMS CD <CR><LF>.& Re: ??==MacOSX burned VMS CD <CR><LF>.& Re: ??==MacOSX burned VMS CD <CR><LF>.& Re: ??==MacOSX burned VMS CD <CR><LF>.& Re: ??==MacOSX burned VMS CD <CR><LF>." Alpha uArchitecture in the news...
 Re: Boot disk 
 Re: Boot disk ! Re: Debugger and FORTRAN INCLUDES  Re: Need help with C program Re: Need help with C program Re: Need help with C program Re: Need help with C program Re: Need help with C program+ Re: OT: Sun's Andy Bechtolsheim  on Itanium * Re: OT: Sun's Andy Bechtolsheim on ItaniumM Re: Weird screen color ... greenish screens likely card-video incompatibility   F ----------------------------------------------------------------------    Date: 21 Nov 2005 18:30:10 -0600. From: brooks@cuebid.zko.hp.nospam (Rob Brooks)& Subject: $GETDVI suggestions requested, Message-ID: <vrmGpQuutT6J@cuebid.zko.hp.com>  N Note: This is a long message; anyone who quotes it fully (or substantially so)5 in suggesting an new item code will be ignored by me.  -----------------   K Once again, I am soliciting suggestions for new $GETDVI item codes.  These  H new item codes (as all others) will also be available via LIB$GETDVI and/ F$GETDVI.  They will be for Alpha and I64 only.   J At the end of this message is a list of all item codes that were added forN V8.2, and the ones that have already been added for V8.3, although there is noM guarantee that they will be there in the final, shipping release (I can think N of no particular reason why one might disappear, but as field test sites know,N "stuff" that is in field test is not necessarily always in the final product.)   N Note that any suggested new item code WILL NOT BE IN THE V8.3 FIELD TEST.  TheM deadline for changes for the field test release is fast approaching, and I've - got some other more important work for that.    K For those that have not upgraded to V8.2, or have not read the new features O and/or release notes manuals, a big change to $GETDVI for V8.2 was the addition M of an optional path specification parameter.  For use with multipath devices, L this allows one to get path-specific information.  For example, the existingO item codes dvi$_errcnt and dvi$_opcnt return the aggregated error count for all M paths.  By specifying a particular path, one can get the values for that path N only.  In the System Services Reference Manual, an item code that can make useB of the path specification will have this text in its description:   < 	This item code is usually used with the PATHNAME parameter.< 	If the PATHNAME parameter is omitted, information about the2 	current path of the multipath device is returned.  H To find out what paths exists for a device, use the SYS$DEVICE_PATH_SCANJ system service.  From DCL, use the F$MULTIPATH lexical function, which wasB added for V8.2; F$MULTIPATH is essentially a "wrapper" around the ! $DEVICE_PATH_SCAN system service.      ! Added for V8.2 MPDEV_AUTO_PATH_SW_CNT MPDEV_MAN_PATH_SW_CNT  WRITETHRU_CACHE_ENABLED  NOCACHE_ON_VOLUME  MOUNTVER_ELIGIBLE  ERASE_ON_DELETE  NOHIGHWATER  NOSHARE_MOUNTED  CLUSLOCK ODS2_SUBSET0 PROT_SUBSYSTEM_ENABLED ODS5 ACCESSTIMES_RECORDED HARDLINKS_SUPPORTED  SCSI_DEVICE_FIRMWARE_REV TOTAL_PATH_COUNT AVAILABLE_PATH_COUNT VOLUME_EXTEND_QUANTITY
 MOUNT_TIME VOLUME_MOUNT_SYS VOLUME_MOUNT_GROUP VOLUME_MOUNT_GROUP PATH_AVAILABLE PATH_USER_DISABLED PATH_NOT_RESPONDING  PATH_POLL_ENABLED  MVSUPMSG PATH_SWITCH_TO_TIME  PATH_SWITCH_FROM_TIME  ERROR_RESET_TIME  @ All of the above item codes have been unofficially backported toM V7.3-2, although there is no support for their use on V7.3-2.  Also note that K since we do not distribute updated STARLET libraries as part of patch kits, I the relevant DVI$_ constants for the item codes do not exist for V7.3-2,  O although one can grab them from any V8.2 distribution, add them to the relevant M V7.3-2 language-specific STARLET library, and things should work correctly.   M The backported version of these item codes exists in UPDATE V0400 and beyond, C and the latest DCL patch kit (for use with F$GETDVI).  Note that no H STARLET library trickery is needed to use these item codes on V7.3-2 for5 F$GETDVI; only the above-noted patch kits are needed.   F No backporting work was done to make these codes work with LIB$GETDVI  for V7.3-2.   M Also, of the new-for-V8.3 item codes, DEVICE_MAX_IO_SIZE, VOLUME_RETAIN_MAX,  N and VOLUME_RETAIN_MIN have been backported to V7.3-2.  One would need the most recent SYS kit for those.    ! Added for V8.3 DEVICE_MAX_IO_SIZE VOLUME_RETAIN_MAX  VOLUME_RETAIN_MIN  PREFERRED_CPU_BITMAP MAILBOX_INITIAL_QUOTA  MAILBOX_BUFFER_QUOTA   --    M Rob Brooks    VMS Engineering -- I/O Exec Group     brooks!cuebid.zko.dec.com    ------------------------------  % Date: Mon, 21 Nov 2005 21:28:32 +0100 . From: "Hans M. Aus" <aus@vim.uni-wuerzburg.de>+ Subject: ??==MacOSX burned VMS CD <CR><LF>. 7 Message-ID: <aus-1476F1.21283121112005@news.cis.dfn.de>   I How do I burn a VMS CD with text files so that the CR and LF are handled  
 correctly?  G I have tried to burn CDs with Disk Utility and Toast but the CR and LF  I are subsequently not handled correctly in the VMS Editor. The text lines  H contain <CR><LF> and the line runs off the screen. The remainder of the  text seems to be fine.  B How to I make an exact copy of the CD with OSX including the file  attributes?    ------------------------------  + Date: Mon, 21 Nov 2005 14:34:05 -0600 (CST) * From: sms@antinode.org (Steven M. Schweda)+ Subject: ??==MacOSX burned VMS CD <CR><LF>. 2 Message-ID: <05112114340591_2038971B@antinode.org>  . From: "Hans M. Aus" <aus@vim.uni-wuerzburg.de>  K > How do I burn a VMS CD with text files so that the CR and LF are handled   > correctly?  @    What is a "VMS CD"?  A CD which will be read on a VMS system?  I > I have tried to burn CDs with Disk Utility and Toast but the CR and LF  K > are subsequently not handled correctly in the VMS Editor. The text lines  J > contain <CR><LF> and the line runs off the screen. The remainder of the  > text seems to be fine.  6    So, CR and LF characters, but no record boundaries?  D > How to I make an exact copy of the CD with OSX including the file 
 > attributes?   H    Are you making "an exact copy of" an existing CD, or are you making a CD from a set of files?   F    There are no file attributes on the Mac OS X, so it's hard for them to be included.   >    What are the file attributes you get now on the VMS system?  =    You might look into MOUNT /UNDEFINED_FAT.  It sounds as if 4 "/UNDEFINED_FAT = record-format: STREAM" might help.  H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-org     Saint Paul  MN  55105-2547    ------------------------------  # Date: Mon, 21 Nov 2005 22:17:44 GMT  From: "Jim" <j.n@nospam.com>/ Subject: Re: ??==MacOSX burned VMS CD <CR><LF>. = Message-ID: <cIrgf.32740$6e1.9217@newssvr14.news.prodigy.com>   : "Hans M. Aus" <aus@vim.uni-wuerzburg.de> wrote in message 1 news:aus-1476F1.21283121112005@news.cis.dfn.de... J > How do I burn a VMS CD with text files so that the CR and LF are handled > correctly? > H > I have tried to burn CDs with Disk Utility and Toast but the CR and LFJ > are subsequently not handled correctly in the VMS Editor. The text linesI > contain <CR><LF> and the line runs off the screen. The remainder of the  > text seems to be fine. > C > How to I make an exact copy of the CD with OSX including the file 
 > attributes? I Don't Unix systems assume that all text files are delimited by CR and LF? J Anyway, the normal file on VMS is VFC.  The editor may have a way to read  files with CR-LF attributes.G You probably should use the Convert utility to change the files to VFC.  Jim    ------------------------------  % Date: Mon, 21 Nov 2005 19:11:21 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>/ Subject: Re: ??==MacOSX burned VMS CD <CR><LF>. + Message-ID: <43827039.C482D1AF@comcast.net>    "Hans M. Aus" wrote: > J > How do I burn a VMS CD with text files so that the CR and LF are handled > correctly? > H > I have tried to burn CDs with Disk Utility and Toast but the CR and LFJ > are subsequently not handled correctly in the VMS Editor. The text linesI > contain <CR><LF> and the line runs off the screen. The remainder of the  > text seems to be fine. > C > How to I make an exact copy of the CD with OSX including the file 
 > attributes?   A O.k. I detect two distinct questions here: Mac files burned to CD 9 (ISO-9660?), and copying a CD using something like Toast.   F Mac files burned to CD, if the filesystem on that CD is ISO-9660, willF still just be "bit-stream" files, since Mac OS.'s have no knowledge of or facilities for RMS.  F On the other hand, to COPY a CD, rip the track using a program or "dd"H from he raw CD device, then feed the output to something that can burn a( disc image to a CD (can Toast do that?).   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Mon, 21 Nov 2005 19:08:26 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>/ Subject: Re: ??==MacOSX burned VMS CD <CR><LF>. + Message-ID: <43826F8A.5EDB79B2@comcast.net>   
 Jim wrote: > ; > "Hans M. Aus" <aus@vim.uni-wuerzburg.de> wrote in message 3 > news:aus-1476F1.21283121112005@news.cis.dfn.de... L > > How do I burn a VMS CD with text files so that the CR and LF are handled > > correctly? > > J > > I have tried to burn CDs with Disk Utility and Toast but the CR and LFL > > are subsequently not handled correctly in the VMS Editor. The text linesK > > contain <CR><LF> and the line runs off the screen. The remainder of the  > > text seems to be fine. > > E > > How to I make an exact copy of the CD with OSX including the file  > > attributes? K > Don't Unix systems assume that all text files are delimited by CR and LF?   G UN*X expects <LF> only. <CR><LF> is what DOS/Windows typically expects.   ( > Anyway, the normal file on VMS is VFC.  D Mmmm... Yes and no. VFC is common, but I'd hesitate to say that it'sH "normal" on VMS. I'd say sequential variable is as "normal" as VMS gets.  $ >  The editor may have a way to read > files with CR-LF attributes.   Yes: it's called "RMS".   I > You probably should use the Convert utility to change the files to VFC.    Might do more harm than good.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Tue, 22 Nov 2005 02:13:00 +0000 & From: Elliott Roper <nospam@yrl.co.uk>/ Subject: Re: ??==MacOSX burned VMS CD <CR><LF>. 1 Message-ID: <221120050213002095%nospam@yrl.co.uk>   / [[ This message was both posted and mailed: see ;    the "To," "Cc," and "Newsgroups" headers for details. ]]   C In article <aus-1476F1.21283121112005@news.cis.dfn.de>, Hans M. Aus ! <aus@vim.uni-wuerzburg.de> wrote:   K > How do I burn a VMS CD with text files so that the CR and LF are handled   > correctly? > I > I have tried to burn CDs with Disk Utility and Toast but the CR and LF  K > are subsequently not handled correctly in the VMS Editor. The text lines  J > contain <CR><LF> and the line runs off the screen. The remainder of the  > text seems to be fine. > D > How to I make an exact copy of the CD with OSX including the file 
 > attributes?   G If your question is really "how do I copy a CD made for and with VMS on  Mac OS X?", then....  F On Mac, run Disk utility. Insert CD. Choose new image from.. (the cd).C when it finishes creating the .dmg file, spit the disk, choose burn @ with the .dmg selected, insert a blank cd and ok all the obvious/ palaver that the pointy-clicky foists upon you.   E If you have text files on a Mac CD in Mac format, then there at least  three techniques....  * ftp from Mac to VMS with type set to text. or@ read the CD files in VMS then (a) set file /attr= stream crlf orD whatever. (sorry, all my vms boxes are switched off so I can't check exactly)& or (b) Use a proper editor, like teco.D If you simply push the files through teco, it will fix 'em up so you! can use another editor afterward.  edit /teco file.txt  ex<esc/<esc> ..is all you need to do.  G If you have lots of files like that and set file does not work for you, 4 then ask again, and I'll write a teco macro for you.D If they are all in one directory, it will be something verbose like:F en*.*$<en$;ebg*$;ec$>ex$$ but I'm not sure the termination handling is< the right way round, and the error handling is non-existent.   --  1 To de-mung my e-mail address:- fsnospam$elliott$$ C PGP Fingerprint: 1A96 3CF7 637F 896B C810  E199 7E5C A9E4 8E59 E248    ------------------------------  % Date: Mon, 21 Nov 2005 16:58:08 -0500 ) From: "Neil Rieck" <n.rieck@sympatico.ca> + Subject: Alpha uArchitecture in the news... 8 Message-ID: <Nprgf.978$e43.129242@news20.bellglobal.com>  F For anyone who is interested, the Nov-2005 issue of COMPUTER (an IEEE I publication) contains an article comparing some characteristics of Alpha  K EV3, EV4, EV5, EV6, and EV8. (I'm not sure why this last entry isn't EV7).  + It is co-written by an author from HP LABS.   
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.8 http://www3.sympatico.ca/n.rieck/links/cool_openvms.html   ------------------------------    Date: 21 Nov 2005 10:43:24 -0800( From: "Rich Jordan" <jordan@ccs4vms.com> Subject: Re: Boot diskC Message-ID: <1132598604.206067.326260@g43g2000cwa.googlegroups.com>   F Some MicroVAX 3100s had a test function (TEST 75 or 76) that would runF the low level formatter.  I don't have any info on which models, or ifE the -95 is so endowed.  We last used a 3100-10e to low level format a C number of old disks that were scheduled for the trash heap; it took ; quite a while but we had time (an RZ56 took several hours).    ------------------------------  % Date: Mon, 21 Nov 2005 22:55:36 +0100 & From: "H Vlems" <nospam@what.ever.com> Subject: Re: Boot disk< Message-ID: <4d3f$43824272$513b9a2c$26758@news.versatel.net>  1 "Oblix" <oba_baby@hotmail.com> schreef in bericht = news:1132521098.276654.269570@f14g2000cwb.googlegroups.com... E > My knowledge with OpenVMS is not that good so bare with me please..  > E > I now managed to make format and restore on a Conner 2.4GB new hard & > disk on my MicroVAX 3100/95 station.. > The hard disk takes DKA0 on the workstation.- > How can I change it to be DKA300 or DKA200? 9 > Is there a way to remove the bad blocks on a hard disk? C > I have alot of parity errors on the original hard disk. how can I  > remove them?F > I don't think formatting will help. Is there anything that I can do? > G > Another thing, I tried to make a backup copy of another HD. It take a " > long time and it never finishes.H > I am afraid that if i do Analyze disk it will damage some files that I3 > don't have a backup copy of. Can you help please?  >  > Thank  >   H You've already managed to open up the system and remove the disk. Have aI close look at the disk and look for three pairs of jumper pins located at F the sides or bottom of the drive. The pattern is usually one of these:  % . . .     or    . . . . . . .   . . . % . . .     or    . . . . . . . . . . . ! 421                           421   I Putting a jumper on one of the (vertical) pairs generates a binary 1. Put F one in the right or left pair, power up the system, and if you hit theJ correct pins you either have dka100 or dka400. Usually the drive reads the= address only at power up, make sure you don't cycle power too 4 fast or the power supply may die during the process.   Hans  3 BTW there are Connor manuals to be found on the web    ------------------------------    Date: 21 Nov 2005 17:27:04 -0800" From: chris_doran@postmaster.co.uk* Subject: Re: Debugger and FORTRAN INCLUDESC Message-ID: <1132622824.056953.144980@g47g2000cwa.googlegroups.com>    Steve Kulpa wrote:; > I know this is a little off topic, but here it is anyway.  > I > I started a new job w/ a huge legacy system that I have to maintain and G > update from time to time.  the FORTRAN was originally written (NOT by H > me) as one HUGE source file containing besides the main program, maybeI > 70 subroutines.  I come from a background where each module was in it's H > own source file so this really bugged me but I was told not to mess w/F > that yet.  When allowed to, I broke out a few of the bigger routinesI > and put INCLUDE filename.for/LIST where they used to be (I had to do it I > this way instead of using libraries due to the development distribution F > system they use - don' t ask!).  Well all works fine but I can't seeH > the source lines in the debugger for any of the modules I included outH > of the huge file.   I had hoped that adding the /LIST qualifier to the+ > include statement would help but no luck.  >  > any ideas? > ' > thanks, now off to the FORTRAN group! 6 > Steve "Happy to be a FORTRAN programmer again" Kulpa  B Normal practice if you don't use libraries is to compile each fileB separately rather than INCLUDE them, then LINK them together, e.g.   $ FORTRAN/DEBUG MAIN $ FORTRAN/DEBUG SUB1 $ FORTRAN/DEBUG SUB1 ...  $ LINK/DEBUG MAIN,SUB1,SUB2,...   F Also, look up the use of commas and/or plus signs on the FORTRAN line,@ but it's usually easier to just recompile the files you changed.   Chris    ------------------------------  % Date: Mon, 21 Nov 2005 16:42:17 -0500 * From: "Stanley F. Quayle" <stan@stanq.com>% Subject: Re: Need help with C program . Message-ID: <4381F8E9.22386.A025384@localhost>  ' On 21 Nov 2005 at 8:30, RJDurkee wrote: E > While I hate to appear ungrateful, so far I have seen nothing to be H > grateful for. - several undocumented programs that don't compile. As aF > programmer I would not post code that did not work, especially for a( > novice in a given language, such as C.  ? We were trying to help you, not do your work for you.  I could  : "document" my opinion of your attitude, but that would be * inappropriate in a forum such as this one.  B You get what you pay for.  Send one of us a check for $5,000, and # we'll be glad to do all the work...   
 --Stan Quayle  Quayle Consulting Inc.  
 ----------- Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363 3 8572 North Spring Ct., Pickerington, OH  43147  USA 0 stan-at-stanq-dot-com       http://www.stanq.com) "OpenVMS, when downtime is not an option"    ------------------------------   Date: 21 Nov 2005 22:13:43 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)% Subject: Re: Need help with C program , Message-ID: <3uev4nF11400hU1@individual.net>  . In article <4381F8E9.22386.A025384@localhost>,- 	"Stanley F. Quayle" <stan@stanq.com> writes: ) > On 21 Nov 2005 at 8:30, RJDurkee wrote: F >> While I hate to appear ungrateful, so far I have seen nothing to beI >> grateful for. - several undocumented programs that don't compile. As a G >> programmer I would not post code that did not work, especially for a ) >> novice in a given language, such as C.  > A > We were trying to help you, not do your work for you.  I could  < > "document" my opinion of your attitude, but that would be , > inappropriate in a forum such as this one. > D > You get what you pay for.  Send one of us a check for $5,000, and % > we'll be glad to do all the work...   A I was just going to let it go, but this is the kind of thing that A really gets me.  People bitch about all the bad C code out there. ? Well, there's your reason.  Code written by someone who doesn't B know the language and has no intention to learn anything about it.C And then when some program crashes and destroys all their important A data or some hacker gets in using a buffer overflow or some other 0 well now exploit, C gets the blame!!  Go figure.   bill   --  J 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>       ------------------------------  + Date: Mon, 21 Nov 2005 23:29:42 +0000 (UTC) ? From: Graham Burley <burley.not-this@encompasserve-or-this.org> % Subject: Re: Need help with C program 9 Message-ID: <43825898.20E659AA@encompasserve-or-this.org>    RJDurkee wrote:  > > > I get the following error when I compile the above program - >  >         sys$exit(s); >      ....................^4 > %CC-E-BADSTMT, Invalid statement.at line number 37  H Looks suspiciously like something got lost when you copied it. If you'reG using Google then use show options + show original and copy from there.      >         $DESCRIPTOR(d, b); >  ........^F > %CC-W-ADDRCONSTEXT, In the initializer for d.dsc$a_pointer, "b" doesG > not have a constant address, but occurs in a context that requires an H > address constant.  This is an extension of the language.at line number > 17  E I have to CC/WARNING=ENABLE=ALL or CC/STANDARD=PORTABLE to raise that C warning, and even then it's an informational. It would help to know B what compiler version you're using and what command/qualifiers you/ tried (and if you have a symbol set-up for CC).     G > I told you I didn't know anything about C - not even enough to figure E > out how to correct these simple errors. I did, however, change this  > line:  >  > long long q; >  > to > 	 > long q;  > 1 > As I was getting an error on the original code.   E It would help to know what error. I'd guess it was %CC-W-TYPECONFLICT  and that you're using a VAX ?    ------------------------------  % Date: Mon, 21 Nov 2005 18:24:25 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> % Subject: Re: Need help with C program + Message-ID: <43825728.D262B37@teksavvy.com>    RJDurkee wrote: G > When I posted the original email, I stated that I not know C and I do  > not plan on learning.    Then hire someone who does.   B You said you needed a way to display a vms date in nanoseconds. WeC provided rough examples on how to do that and how to use VMS system G services and which services were needed.  We have no idea of what other F tasks your program needs to do, how it reads it data and how it writesF the output. So you cannot expect us to write all of your code for you.  G And when you first posted your question, it wasn't obvious that you had G no C experience and were unwilling to learn. My impression was that you G were new to VMS and didn't quite know how to get the VMS specific bits.    ------------------------------  % Date: Mon, 21 Nov 2005 16:30:55 -0800 # From: "Tom Linden" <tom@kednos.com> % Subject: Re: Need help with C program ( Message-ID: <ops0l81tgczgicya@hyrrokkin>  C On 21 Nov 2005 08:30:40 -0800, RJDurkee <RJDurkee@yahoo.com> wrote:   G > When I posted the original email, I stated that I not know C and I do G > not plan on learning. The project is a final project to pull data off I > the OpenVMS system prior to sunsetting. I have a process working but it I > would be simpler if I had a small C program that would convert the date  > as I mentioned earlier on.E > While I hate to appear ungrateful, so far I have seen nothing to be H > grateful for. - several undocumented programs that don't compile. As aF > programmer I would not post code that did not work, especially for a( > novice in a given language, such as C.2 > Doing so would be a waste of my time and theirs. > Rich > I Since your task is to clean-up so you can get rid of VMS, I can't see why I anyone in this group would have an incentive to help you, aside from your H petulant manner.  As others have said buy a consultant or a compiler forE a language your are confortable with.  I would be happy to sell you a  PL/I compiler:-)   ------------------------------   Date: 15 Nov 2005 17:25:21 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)4 Subject: Re: OT: Sun's Andy Bechtolsheim  on Itanium+ Message-ID: <3tuk01Fud7f2U1@individual.net>   0 In article <7aadnePy1aLdhefeRVn-vg@bresnan.com>,% 	GreyCloud <mist@cumulus.com> writes:  > Alan Greig wrote:  >>   >>   >> GreyCloud wrote:  >>   >>>  >>> - >>> http://www.sgi.com/industries/government/  >>   >>  < >> I do wonder how this will go down with government buyers: >>  S >> http://www.sgi.com/company_info/newsroom/press_releases/2005/november/nyse.html   >>   >> ===' >> SGI Securities to Cease NYSE Trading  >>  I >> MOUNTAIN VIEW, Calif., (November 1, 2005)SGI announced today that it  J >> has been advised by the New York Stock Exchange (NYSE) that its common G >> stock - ticker symbol SGI - and its 6.5% Senior Secured Convertible  L >> Notes due June 1, 2009 - ticker symbol SGI 09 - will no longer be traded J >> on the NYSE beginning with the opening of business on Monday, November K >> 7, 2005. The Company expects its common stock will be quoted on the OTC   >> Bulletin Board. >>  L >> As previously reported, SGI received notice from the NYSE on May 9, 2005 K >> that SGI's common stock had fallen below the NYSE's minimum share price  G >> standard for continued listing. The NYSE's standard requires that a  L >> company's common stock trade at a minimum average closing share price of L >> $1.00 during a consecutive 30-day trading period. SGI's common stock has 1 >> not returned to compliance with this standard.  >>  I >> On November 1, 2005, the NYSE notified SGI of its decision to suspend  I >> trading and stated that an application to the Securities and Exchange  F >> Commission to delist these securities from the NYSE is pending the ' >> completion of applicable procedures.  >> ===0 >> And some analysis on the new Itanium monsters >>  : >> http://www.theregister.co.uk/2005/11/15/sgi_altix_4000/ >>  F >> Without question, SGI's focus on bringing Linux to the highest-end J >> systems has been appreciated by the industry. Its reliance on Itanium, & >> however, has proved less rewarding. >>  I >> Back when SGI pitched Irix on MIPS, it was burned just by the idea of  I >> Itanic. Customers questioned how SGI could compete against this super  L >> chip from Intel and HP and stalled their purchases of SGI gear. That was  >> the first burn. >>  I >> Then SGI actually moved to Itanic and saw the chip struggle to gain a  J >> foothold in the server market. Intel still has not shipped a dual-core J >> Itanium, while competitors busy away on their second, third and fourth K >> generation dual-core parts. In addition, HP stands as the clear Itanium  E >> server leader, making SGI look like an also ran tied to a rival's  + >> architecture. Industry standard? Hardly.  >>  L >> The slow sales of Itanium-based gear have left SGI in financial turmoil. G >> It now trades on the pink sheets and has a market cap far less than  & >> relative newcomer Rackable Systems. >>  J >> Customers aren't likely to flock to the Altix 4000 until the dual-core J >> Montecito ships arrived in the middle of next year. That's a long time $ >> to wait for a troubled concern.  > G > You'd be surprised at what the government would buy.  These concerns  E > don't bother them for some reason.  I've seen worse decisions made. E > If the specifications document for what they want, and some really  K > klutzy system fits it precisely, then that is what they buy.  Been there  D > and done that.  I had to be really careful with the specs and the K > wording to get a VAX with VMS back in the 80s, and the process goes thru  K > a few depts. and it always takes at least a year to three years before a  K > contract is awarded.  By the time I received the 785, the machine was at   > end of life.  H That's why contracting rules were changed to make it easier to buy COTS.E Computer lifetimes are much to short for doing contracting the way it F used to be done when I was playing that game.  And, yes, I have had toI do some real creative RFP writting to get a system we wanted at one time. H By the time my RFP was ready to hit the streets the system we wanted wasH on the GSA Schedule.  Over 6 months of work down the toilet.  Good thingI I was only a SSG then, it only cost the Army about $5000 for my time. :-)    bill   --  J 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>       ------------------------------  % Date: Mon, 21 Nov 2005 15:48:15 -0500 - From: William Webb <william.w.webb@gmail.com> 3 Subject: Re: OT: Sun's Andy Bechtolsheim on Itanium G Message-ID: <8660a3a10511211248o84a1343w8d5fc292b6c9007@mail.gmail.com>   0 On 11/15/05, GreyCloud <mist@cumulus.com> wrote:    [snip]    > F > You'd be surprised at what the government would buy.  These concernsE > don't bother them for some reason.  I've seen worse decisions made. D > If the specifications document for what they want, and some reallyJ > klutzy system fits it precisely, then that is what they buy.  Been thereC > and done that.  I had to be really careful with the specs and the J > wording to get a VAX with VMS back in the 80s, and the process goes thruJ > a few depts. and it always takes at least a year to three years before aJ > contract is awarded.  By the time I received the 785, the machine was at > end of life. >   A I may [or may not] have seen computer hardware go out-of-warranty > while sitting unopened in the warehouse where it was received.   WWWebb   --C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------    Date: 21 Nov 2005 10:39:04 -0800( From: "Rich Jordan" <jordan@ccs4vms.com>V Subject: Re: Weird screen color ... greenish screens likely card-video incompatibilityC Message-ID: <1132598344.711685.155780@g14g2000cwa.googlegroups.com>   E The ZLXp-E series cards had an issue where teh ground for the 'green' F signal was floating on the card; DEC monitor cables of the appropriateB type grounded the green signal.  When using the card with a peeceeC monitor and cable, you'd get fringing and ringing and other display E artifacts.  I don't know if the -L series had the same feature, and I E don't recall anyone getting just dark green; that makes it sound like 6 one or more of the color feeds is not getting through.  F In the -E cards' case the solution was to tie the green ground line onD the card to one or both of the other color signal grounds.  Again, IG have no idea if the -L cards have the problem or would benefit from the  'fix'.  E Is the monitor using BNC connectors or HD15 (at the monitor end)?  If A BNC, then you need to make sure you have enabled SYNC ON GREEN at C console level on the Alpha (no references handy for the environment ? variable, sorry).  You could also try swapping the red and blue F connections to see if you get a color shift, but not the green (you'll lose sync).   C If the monitor is HD15 then it should get the separate sync signals  from the cable.   D No other ideas, sorry.  my -L1 card worked very well with a standard+ Philips SVGA monitor, and with a DEC VRC21.    ------------------------------   End of INFO-VAX 2005.651 ************************                                                                                                                      hpwasd.obj
 --------                   -------
   486129                   12 files
                                                                                                                                                                                                                                                                                                                                                                                                                                            