1 INFO-VAX	Sun, 09 Apr 2000	Volume 2000 : Issue 199       Contents: Re: CC patches ?6 Re: DEC C++ V5.4-010 / Template Classes / Link problem Re: Freeware MIME 2 Re: Galaxy (or perhaps Wildfire) and shared memory2 Re: Galaxy (or perhaps Wildfire) and shared memory Re: Manuals for DEC 3000-400s  Re: Manuals for DEC 3000-400s " MicroVAX 3100-20 diagnostic LEDs ? Re: So who will buy VMS ?  Sun question for Andrew  VAXStation 3100 boot disks( Re: Warning: circuitsurgeon is a ripoff!( Re: Warning: circuitsurgeon is a ripoff!% Re: Wierd Elsa Gloria Synergy Problem   F ----------------------------------------------------------------------  # Date: Sun, 09 Apr 2000 13:29:41 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)  Subject: Re: CC patches ? 0 Message-ID: <009E858E.98838E97@SendSpamHere.ORG>  W In article <38efe62b$1@news.kapsch.co.at>, eplan@kapsch.net (Peter LANGSTOEGER) writes: V >In article <38B2EF32.5B1A21B9@mediaone.net>, Duane Smith <nhdas@mediaone.net> writes:J >>Perhaps the C++ project leader has more clout than the C project leader?; >>I will speak to the C project leader about this tomorrow.  > C >And now, a month later, my thanks to you and the C project leader.  > 6 >CCAE03062 is now downloadable (since a few days ago).  F Does this fix anything?  I've been fighting with CSC with 6.2 problems and getting nowhere.     --N VAXman- OpenVMS APE certification number: AAA-0001           VAXman@TMESIS.COM  O Compaq C V6.2 has bugs, bugs, bugs, bugs, bugs! No wait! They're ANSI features!    ------------------------------  % Date: Sun, 09 Apr 2000 13:51:32 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> ? Subject: Re: DEC C++ V5.4-010 / Template Classes / Link problem ) Message-ID: <38F06EC4.3B45C5BC@gtech.com>    Lee Gillie wrote: G > Comp.os.vms is an OS newsgroup, but I am desparate for DEC C++ input.   5 We are relative tolerant in this forum so no problem.   C > DEC C++ V5.4-010 is probably a bit dated.  I'm trying to port the B > Apache XERCES lib (XML) to VMS, and this source code seems to beD > a bit ahead of the standards for our installed version of DEC C++. > D > The problem involves template classes.  Building the Apache XERCESH > library into an OLB.  Then try to compile and link one of the samples. > Get a bunch of link warnings: - >     %LINK-W-NUDFSYMS, 30 undefined symbols:  >     %LINK-I-UDFSYM ...+ >     %LINK-W-USEUNDEF, undefined symbol...  > G > When demangled, each of the symbols is revealed to reference a member % > of specific template class, such as G > void RefVectorOf<TreeWalkerImpl >::addElement(TreeWalkerImpl *const ) K > void RefVectorOf<NodeIteratorImpl >::addElement(NodeIteratorImpl *const )  > E > I tried compiling all modules of XERCES with /TEMPLATE=COMPILE, but H > then I get duplicate symbol errors when inserting the objects into the > OLB.  D As you say DEC C++ 5.4 is pretty old. I not surprised that there are problems with templates.  ; If you have an old compiler then it is safest to stick with 0 cfront V2 compatible C++ or something like that.  C Sorry I can not come up with some good work-arounds, because then I  would H have to hav that compiler version and spend time working on the problem.  F Is it impossible to upgrade to V6.2/V6.3 (whatever is current today) ?   Arne   ------------------------------  % Date: Sun, 09 Apr 2000 13:53:35 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>  Subject: Re: Freeware MIME) Message-ID: <38F06F3F.7507E98C@gtech.com>    "Frits A.M. Storms" wrote:J > I am looking for a simple freeware tool to encode & decode MIME files on
 > OpenVMS.B > Could someone point me to the appropriate download site please ?  # There are a MIME tool with VMS 7.2.   < For older VMS versions people usually use MPACK or MMENCODE.  < Sorry I do not have an URL at hand, but try search for those	 packages.    Arne   ------------------------------  " Date: Sun, 9 Apr 2000 11:53:42 GMT2 From: kilgallen@eisner.decus.org (Larry Kilgallen); Subject: Re: Galaxy (or perhaps Wildfire) and shared memory & Message-ID: <2000Apr9.075342.1@eisner>  R In article <8cluid$or8$1@pyrite.mv.net>, "Bill Todd" <billtodd@foo.mv.com> writes: > ? > Larry Kilgallen <kilgallen@eisner.decus.org> wrote in message " > news:2000Apr7.184733.1@eisner...M >> In article <8cjdd4$18m$1@pyrite.mv.net>, "Bill Todd" <billtodd@foo.mv.com> 	 > writes:  >>L >> > Actually, my real worry was that the hardware interconnections required > toJ >> > join caches across partitions constituted a potential cross-partition > singleM >> > failure point in and of themselves (of a kind that your option '2' would  > not M >> > necessarily protect against, though hardware isolation on these paths in J >> > excess of that normally found on SMP systems could) - a failure point > which J >> > conventionally-separated cluster nodes do not have since they have no, >> > inter-node shared memory to begin with. >>A >> Well, of course, sharing a memory bus (or switch) introduces a B >> degree of commonality, and an arrangement with shared resourcesC >> is not so immune to propagation of failures as is an arrangement  >> with no shared resources. >>  >> I thought of that as obvious. > H > Of course it's obvious.  What was not obvious to me was that isolationE > mechanisms had been added over and beyond those present in a normal L > (unpartitionable) SMP that would allow the claim that a Wildfire or MarvelH > box offered fault isolation comparable to that of a cluster comprisingN > independent nodes to be true even when memory was shared between partitions.  @ Over a year ago I heard a talk by Clair Grant of VMS Development? that emphasized that Galaxy is not a "cluster in a box" in that ? it lacks the hardware separation features you get with separate < boxes.  Those of us who have ever seen a thermite grenade in@ action, (or even seen the Chemistry 101 demonstration) feel that: anything in the same box is not really isolated, even with separate power supplies.  6 Note that the current Galaxy offerings leave decisions: about galactic sections up to the customer.  I would think< that even with a "shared memory as a LAN" opportunity (which< may be there now for all I know), you still have the ability to use real wire and adapters.  ; So the very fact that DEQ leaves this as a decision for the ; customer indicates sharing is not the same as isolation.  I : do not understand where you saw any "claim that a Wildfire; or Marvel box offered fault isolation comparable to that of ; a cluster comprising independent nodes to be true even when & memory was shared between partitions."  = The available information from public displays would indicate ? that Wildfire for the time being has much less memory isolation 0 than Marvel because Wildfire actually exists :-)   ------------------------------  $ Date: Sun, 9 Apr 2000 10:26:35 -0400' From: "Bill Todd" <billtodd@foo.mv.com> ; Subject: Re: Galaxy (or perhaps Wildfire) and shared memory ( Message-ID: <8cq3rg$2ln$1@pyrite.mv.net>  = Larry Kilgallen <kilgallen@eisner.decus.org> wrote in message   news:2000Apr9.075342.1@eisner...   ...   B > Over a year ago I heard a talk by Clair Grant of VMS DevelopmentA > that emphasized that Galaxy is not a "cluster in a box" in that A > it lacks the hardware separation features you get with separate  > boxes.  L That level of hardware separation has been intimated to be present in futureD hardware (don't know whether Wildfire or Marvel) products in earlierJ discussions (I think here; could have been in comp.arch).  But the kind ofD insidious corruption after a fault I was worried about is a bit moreL troubling than the mere possibility that a fault will bring down the system.  6   Those of us who have ever seen a thermite grenade inB > action, (or even seen the Chemistry 101 demonstration) feel that< > anything in the same box is not really isolated, even with > separate power supplies.  I A thermite grenade qualifies as a site disaster, not fault isolation.  It L could as easily take out your RAID set if you're not using remote shadowing,A but that does not reflect upon RAID fault-isolation capabilities.    - bill   ------------------------------  " Date: Sun, 9 Apr 2000 12:08:59 GMT, From: kaplow_r@eisner.decus.org (Bob Kaplow)& Subject: Re: Manuals for DEC 3000-400s& Message-ID: <2000Apr9.080859.1@eisner>  ` In article <HYKF4.32753$dc2.320996@news0.telusplanet.net>, "Craig Wood" <cswood@agt.net> writes:J > Does anyone know where I can get on-line manuals, user guides, etc for a& > DEC 3000-400s (aka Sandpiper) Alpha? > B > There are on-line guides for the 3000-600, etc. but not the 400.  8 Where did you find these? I'm looking for a -300 myself.   	Bob Kaplow	  E SPAM:	spamrecycle@ChooseYourmail.com	uce@ftc.gov	postmaster@127.0.0.1    ------------------------------  # Date: Sun, 09 Apr 2000 13:48:50 GMT # From: "Craig Wood" <cswood@agt.net> & Subject: Re: Manuals for DEC 3000-400s: Message-ID: <6T%H4.38116$dc2.542005@news0.telusplanet.net>  ! The manual for the 3000-600 here:   : http://www.digital.com/alphaserver/archive/axp/dec3000.pdf      9 "Bob Kaplow" <kaplow_r@eisner.decus.org> wrote in message   news:2000Apr9.080859.1@eisner...I > In article <HYKF4.32753$dc2.320996@news0.telusplanet.net>, "Craig Wood"  <cswood@agt.net> writes:L > > Does anyone know where I can get on-line manuals, user guides, etc for a( > > DEC 3000-400s (aka Sandpiper) Alpha? > > D > > There are on-line guides for the 3000-600, etc. but not the 400. > : > Where did you find these? I'm looking for a -300 myself. >  > Bob Kaplow > G > SPAM: spamrecycle@ChooseYourmail.com uce@ftc.gov postmaster@127.0.0.1    ------------------------------  $ Date: Sun, 9 Apr 2000 09:39:38 -0400 From: "jam62" <jam62@psu.edu> + Subject: MicroVAX 3100-20 diagnostic LEDs ? 2 Message-ID: <004801bfa229$0e5c44b0$6a08978d@gonzo>  , This is a multi-part message in MIME format.  + ------=_NextPart_000_0045_01BFA207.86300CF0  Content-Type: text/plain;  	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   G Can someone tell me how to interpret the LEDs on the back panel of my =  MicroVAX 3100 Model 20?    Many thanks. GlinchJ -------------------------------------------------------------------------=J -------------------------------------------------------------------------= --- *                        James A. McGlinchey                       =20 C             -=3D< Sancho! My Armor! My Sword! My TECO Macros! >=3D-   H     145 Fawn Lane                      Asst. Prof. Information Science = and TechnologyD     Haverford PA 19041-1117            Pennsylvania State University=                                        Delaware County Campus <     (610) 527-8285  (home)             25 Yearsley Mill Road;     (610) 527-1999  (Home Office)      Media, PA 19063-5596 B     jim@glinchnet.com                  (610) 892-1263 (PSU Office)5     http://www.glinchnet.com/jim/      glinch@psu.edu                     =20                    =20  + ------=_NextPart_000_0045_01BFA207.86300CF0  Content-Type: text/html; 	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD>3 <META content=3D"text/html; charset=3Diso-8859-1" =  http-equiv=3DContent-Type>8 <META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR> <STYLE></STYLE>  </HEAD>  <BODY bgColor=3D#ffffff>J <DIV><FONT size=3D2>Can someone tell me how to interpret the LEDs on the = back=20 0 panel of my MicroVAX 3100 Model 20?</FONT></DIV> <DIV>&nbsp;</DIV> - <DIV><FONT size=3D2>Many thanks.</FONT></DIV> ' <DIV><FONT size=3D2>Glinch</FONT></DIV> 
 <DIV><FONT=20 J size=3D2>----------------------------------------------------------------=J -------------------------------------------------------------------------=J ------------<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=J sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs= p;=20  James A.=20 J McGlinchey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=J ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= =20 H <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = -=3D&lt;=20 A Sancho! My Armor! My Sword! My TECO Macros! &gt;=3D-</FONT></DIV>  <DIV>&nbsp;</DIV> 2 <DIV><FONT size=3D2>&nbsp;&nbsp;&nbsp; 145 Fawn=20J Lane&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=< sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20F Asst. Prof. Information Science and Technology<BR>&nbsp;&nbsp;&nbsp; = Haverford=20 PA =J 19041-1117&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;=20 Pennsylvania State=20 J University<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=J ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;&nbsp;&nbsp;&nbsp;=20D Delaware County Campus<BR>&nbsp;&nbsp;&nbsp; (610) 527-8285&nbsp;=20J (home)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20I 25 Yearsley Mill Road<BR>&nbsp;&nbsp;&nbsp; (610) 527-1999&nbsp; (Home=20 1 Office)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media, PA = # 19063-5596<BR>&nbsp;&nbsp;&nbsp;=20  <A=20 J href=3D"mailto:jim@glinchnet.com">jim@glinchnet.com</A>&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;&nbsp;=207 (610) 892-1263 (PSU Office)<BR>&nbsp;&nbsp;&nbsp; <A=20 J href=3D"http://www.glinchnet.com/jim/">http://www.glinchnet.com/jim/</A>&=  nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 <A=20 J href=3D"mailto:glinch@psu.edu">glinch@psu.edu</A><BR>&nbsp;&nbsp;&nbsp;&n=J bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;&nbsp;&nbsp;=20J <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=0 sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 </FONT></DIV></BODY></HTML>   - ------=_NextPart_000_0045_01BFA207.86300CF0--    ------------------------------  " Date: Sun, 9 Apr 2000 12:16:19 GMT, From: kaplow_r@eisner.decus.org (Bob Kaplow)" Subject: Re: So who will buy VMS ?& Message-ID: <2000Apr9.081619.1@eisner>  b In article <38E7D45F.F26463D7@vl.videotron.ca>, JF Mezei <jfmezei.spamnot@vl.videotron.ca> writes: > David Turner wrote: M >> All said and done - it certainly seems as though the Almighty Q is panning K >> for one it's fellow demi-gods and will undoubtedly dump it's last trusty  >> disciple, VMS >> Who's gonna buy it ?  > I > I would think it more likely for Compaq to spin off the VMS/True64 (and P > assiciated software products) into a company partly onwed by CMGI. It would beN > the logical thing to do. It would remain under the Compaq umbrella, ensuringK > that customers continue to buy support from Compaq, yet would give it the O > independance to market agressively etc. (As well as giving a less proprietary H > appearance since other makers of Alpha boxes could also sell VMS etc.)   CA :-(   	Bob Kaplow	  E SPAM:	spamrecycle@ChooseYourmail.com	uce@ftc.gov	postmaster@127.0.0.1    ------------------------------  % Date: Sun, 09 Apr 2000 09:33:37 -0500 / From: Scott Vieth <svieth@ameritech.net.nospam>   Subject: Sun question for Andrew4 Message-ID: <38F094C1.E7A54EAC@ameritech.net.nospam>   Andrew:   H Is there a newsgroup similar to comp.os.vms where folks discuss Solaris?  = I found only alt.solaris.x86 (not exactly what I'm after) and * comp.unix.solaris (which has no messages).   Thanks,   
 -Scott :^)   ------------------------------  # Date: Sun, 09 Apr 2000 13:48:50 GMT " From: stefan@softhome.net (Stefan)# Subject: VAXStation 3100 boot disks - Message-ID: <38f089d2.1813210@news.xs4all.nl>   = Are there any disks out there with which I can at least get a E VAXStation 3100 to do SOMETHING ?? Because I have about 4 of them and C I wanted to install NetBSD on them but I cant boot from disk (yet).   B So any software that you know of is welcome, even if its just some simple demo kinda thing.   yours,   Stefan.    ------------------------------  % Date: Sun, 09 Apr 2000 13:46:28 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> 1 Subject: Re: Warning: circuitsurgeon is a ripoff! ) Message-ID: <38F06D94.D87D1979@gtech.com>   
 Dan wrote: > Gil wrote:E > > The unit was working PERFECTLY when it left here on July 20 1999.lH > > DAN then screwed up the hard drive, which I replaced at no cost evenE > > though DAN did the damage. $35 to send hard drive FEDEX. This wasE > N > LIAR! I did NOT screw up the drive, and you know it. You sent me a defectiveG > one. You offered to replace it but ONLY if I paid shipping both ways!d  $ > > replace everything DAN dorks up. > + > You mean defective equipment you sold me.  > K > > Gil also has complaints on Ebay about these deals, so it's not just me.- > G > > seeing that he is posting LIES I retract this offer to him and will  > # > and seeing YOUR LIES posted here.r > I > > never deal with him again and advise all to be aware that if you dealS > >rI > > with him you may get a posting from him on the newsgroups like I did.r > $ > yeah unlike YOU who commits FRAUD! > H > > There are some people in this world that do NOT want to be helped or > > M > > fixed, these kind of people just want to spread misery amonst the rest of  > > the world.  I have >  > Yeah people you RIP OFF!  @ Lots of name-calling. And very little substance. None of you twoE can say with certainty that the drive was not send out OK but arrivedn1 non-OK due to something happend during transport.e  D I am not saying that was what happend. But I am saying that it could@ be possible (based on what I know). So I would recommend you two to stop the name-calling.o  E Regarding warranty and who pays for transport etc., then this kind of G stuff ussually exist in writing somewhere. And if you are not satisfiedrF with something, then contact a lawyer. This is a business transaction.C This news-group can not do anything about it. And neither can DECUSi for that matter.   Arne   ------------------------------  # Date: Sun, 09 Apr 2000 16:04:41 GMTl! From: Beyonder <beyonder@vrx.net>p1 Subject: Re: Warning: circuitsurgeon is a ripoff!t' Message-ID: <38F09C85.80825653@vrx.net>R  A >Lots of name-calling. And very little substance. None of you two F >can say with certainty that the drive was not send out OK but arrived2 >non-OK due to something happend during transport.  B Oh that's very easy to say actually. the drive came in the system,< but on powerup the drive was defective. DOA. that's what DOA means you know.d  R Given the drive was in the system, and the system was working (seemingly) there isP nothing that could have caused the amount of damage that was found to the drive.  E >I am not saying that was what happend. But I am saying that it coulddA >be possible (based on what I know). So I would recommend you twop >to stop the name-calling.  M nope. see above. and I'll stop when he admits the truth. or I'll stop when itI keeps I someone from being ripped off. or I'll stop when he refunds me. whatever.   F >Regarding warranty and who pays for transport etc., then this kind ofH >stuff ussually exist in writing somewhere. And if you are not satisfiedG >with something, then contact a lawyer. This is a business transaction. D >This news-group can not do anything about it. And neither can DECUS >for that matter.   = It was in email, not writing, so it doesn't account for much.s$ how about getting a defective cable?* how about getting a defective motherboard?  L Bottom line, he ripped me off, and I have emails from others saying the same thing.  M And you are wrong. The news-group CAN (and HAS) do something about it. It cangK inform other people in the world about the scum like circuitsurgeon. It hasoQ already done this, as I said, others have told me the same thing. And if it keepslR even ONE more person from getting ripped off, then it has done all it needs to do.  < As for DECUS, I have no idea. Again, serving only to inform.  P As for the legal remedy, I'm in Canada, he's in the US. two different countries,O it's very difficult, if not impossible. The legal entities in the other country:R are not usually interested unless it's something major. But you have just given me an idea.  R You just reminded me of something... mail fraud. Yep, I'm off to write an official% warning/complaint to the post office.i   Dan.   ------------------------------   Date: 9 Apr 2000 07:11:13 GMTr+ From: Tom Leitner <tom@radar.tu-graz.ac.at>1. Subject: Re: Wierd Elsa Gloria Synergy Problem1 Message-ID: <8cpaeh$mlh$1@fstgss02.tu-graz.ac.at>s  1 Zane H. Healy <healyzh@shell1.aracnet.com> wrote:dL >> If you can live with the beat frequency flicker at 60Hz, it "should" workK >> better... but this also tends to exacerbate any power supply glitches ase >> well.  M > Unfortunatly the results at 60Hz and 70Hz, while not as bad, were the same hK > as at say 75Hz.  At 1280x1024 24-bit I get 'wobbles' on the left side of dO > the screen.  I've tried this on both my DEC 17" and my VeiwSonic 21".  Hmmm,  ; > I take that back, I've not tried 60Hz on the ViewSonic.     I Same here. At 1280x1024, 24-bit with a VRC21-HA I get wobbles on the leftrE side of the screen when a text window is scolling or any other screentB activity occurs which causes many pixels to change simultaneously.I This seems to be independent of the monitor. I've tried different brands tI and all exhibit this behaviour. Also I see the problem on all three Elsa  E Gloria cards I have. But I still think that this is a problem of the nI graphics card. My interpretation is, that at 1280x1024 many pixel changesiG cause the card to temporarily draw a high current (DRAMS for video ram)l' which causes the voltage to drop a bit.b  L > On the DEC at 60Hz the wobble was *almost* gone.  In fact the only thing II > was able to do at 60Hz to bother it was to page through a web page withnM > Mozilla.  At higher frequencies I was able to effect it by paging through a 4 > directory listing with the DECwindows filemanager.  N > It's really wierd since at 1024x768 70Hz 8-bit or 24-bit it's rock solid on  > both monitors.  K I'm running mine at 1280x768, 75Hz and 16-bit (!!!) now which is sufficient I for all color intensive applications and where the wobble is almost gone.c! This is under Tru64 Unix, though.t  K > Actually I think the best solution for me is to leave it at 1024x768 70HzeL > 24-bit and simply start up another session at 1280x1024 24-bit on my Mac. N > That way I've got everything I want to run on the same desktop.  I don't seeJ > me needing to do anything with really heavy graphics on VMS, and the twoD > machines are on a 100Mbit switch, so it seems to work pretty good.  F I'd go for 16-bit depth. This reduces the wobble a lot and still gives) you lots of colors and a high resolution.t   Tom" -- hN Dr. Tom Leitner             Dept. of Communications, Graz Univ. of Technology,K tom@radar.tu-graz.ac.at     Inffeldgasse 12, A-8010 Graz / Austria / Europea: PGP public key @ http://wiis.tu-graz.ac.at/people/tom.html   ------------------------------   End of INFO-VAX 2000.199 ************************