1 INFO-VAX	Sat, 25 Nov 2000	Volume 2000 : Issue 658       Contents:7 Re: almost identical system disks in different clusters 7 Re: almost identical system disks in different clusters  RE: Connecting a CD-writer.. Re: Connecting a CD-writer.. Re: Connecting a CD-writer.. Re: DHCP Client for Multinet Re: EBay vs. QXL Re: EBay vs. QXL Re: EBay vs. QXL Re: EBay vs. QXL Re: EBay vs. QXL8 HSJ40 dual-redundant controller rolling firmware upgrade< Re: HSJ40 dual-redundant controller rolling firmware upgrade Re: openvsm and vga cards  Re: openvsm and vga cards  Re: remote DECWindows , Starting a DECWINDOWS app from a Microvax II Re: [Q]"vi" section for TPU   F ----------------------------------------------------------------------   Date: 24 Nov 2000 16:07:17 PSTT From: Fairfield@SLAC.Stanford.EDU (Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515)@ Subject: Re: almost identical system disks in different clusters3 Message-ID: <9UycFNMfMuAA@mccdev.slac.stanford.edu>   - In article <8vj79h$sj$1@info.service.rug.nl>, 4         helbig@astro.rug.nl (Phillip Helbig) writes: [...] C > I'm sure this must be a really common problem and find it hard to J > believe that people actually apply patches, compiler updates etc to two,% > or even more, system disks by hand.  [...]   H         Personally, I would  think  it  _far_  faster  to  install a fewH     patches  than  to  do a full system disk image  restore!   (I  guessH     cluster uptime isn't an issue  for  you  either,  eh?)  You're  onlyH     talking  about two system disks, one for each cluster, and a handfulH     of patches and  layered  product  installations.   I mean, we're notH     talking about replicating a new manufacturing system across 20 sites#     world wide or something, right?   H         Someone else mentioned using essentially the same system disk inH     different clusters, but using one set of system roots in one clusterH     and another set in the other.   That  would  work for you, but thereF     are a LOT of things I'd think you'd want to be VERY careful about:  D      1) Make  sure  to  move  all  the  various  SYSUAF, RIGHTSLIST,D         MAILUAF,   QMAN$MASTER.DAT,  queue  manager  journal   file,D         operator log files, audit  files,  error  log  files,  etc.,D         etc.,  _off_  the  system  disk.   If you can't do that, allD         sorts of history, etc., will be  lost when you overwrite theD         second  system  disk (more precisely, will contain only  the&         history of the first cluster).  D      2) Make sure you have somewhere to copy the current contents ofD         SYS$SPECIFIC:[SYSEXE] and restore them after the system diskD         overwrite.  If you're upgrading,  then  be  sure to copy theD         current  contents  from the second cluster's system disk  ofD         its  nodes'  SYS$SPECIFIC:[SYSEXE]  to   the   correspondingD         location  on  the system disk that will be upgraded _before_D         doing the upgrade.   Get  fresh  copies  of AUTOGEN feedback         data before doing so.   H     I'm sure there are other gotchas  to  watch out for.  These are justH     the ones that immediately come to mind.  Personally, I wouldn't findH     the  risk of screwing things up royally worth any time savings  that/     may, or more likely, may not be realized...            -Ken --M  Kenneth H. Fairfield            |  Internet: Fairfield@SLC.Slac.Stanford.Edu :  SLAC, 2575 Sand Hill Rd, MS 46  |  Voice:    650-926-2924:  Menlo Park, CA  94025           |  FAX:      650-926-3515N  -----------------------------------------------------------------------------B  These opinions are mine, not SLAC's, Stanford's, nor the DOE's...   ------------------------------  % Date: Fri, 24 Nov 2000 19:21:10 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> @ Subject: Re: almost identical system disks in different clusters, Message-ID: <3A1F05E9.A7ECAF88@videotron.ca>  E > > I'm sure this must be a really common problem and find it hard to L > > believe that people actually apply patches, compiler updates etc to two,' > > or even more, system disks by hand.   M One advantage of applying patches individually is that it then becomes easier M to roll-back should the patch prove to be problematic since you probably have C the old intact file in a system where the patch wasn't applied yet.    ------------------------------  % Date: Fri, 24 Nov 2000 14:50:46 -0600 * From: WILLIAM WEBB <WWEBB1@email.usps.gov>% Subject: RE: Connecting a CD-writer.. - Message-ID: <0033000009647387000002L072*@MHS>   3 =0AY'all need to remember that in the acronym SCSI, % *neither* S was short for "standard".    WWWEbb -----Original Message-----/ From: Info-VAX-Request@Mvb.Saic.Com at INTERNET ' Sent: Friday, November 24, 2000 1:50 PM 6 To: Webb, William W; Info-VAX@Mvb.Saic.Com at INTERNET% Subject: RE: Connecting a CD-writer..      > -----Original Message-----> > From: David J. Dachtera [mailto:djesys.nospam@earthlink.net]+ > Sent: Thursday, November 23, 2000 9:59 PM  >  > Chuck McCrobie wrote:  > > > > > What are the shortfalls of the "generic SCSI" in DKDRIVER? > C > See the Deja archive of the myriad posts in this newsgroup and/or F > comp.sys.dec on this topic, and/or review the info. at the following > URL: > 7 > http://www.djesys.com/vms/hobbyist/support.html#cworb  > H > Note: The removeable aspect is immaterial and can(should) be ignored.=   >   H Why are you blaming your problems with the Orb drive on VMS?  Compaq ca= n't H be expected to test VMS with every SCSI device made but, it is reasonab= le to H expect Castlewood to test the Orb with more than just Wintel and Mac.  = I'llH bet the problems are either Castlewood's fault or mushy areas of the SC= SI spec.=   ------------------------------  % Date: Fri, 24 Nov 2000 14:31:18 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> % Subject: Re: Connecting a CD-writer.. - Message-ID: <3A1ED016.77ADBEAD@earthlink.net>    John Vottero wrote:  >  > > -----Original Message-----@ > > From: David J. Dachtera [mailto:djesys.nospam@earthlink.net]- > > Sent: Thursday, November 23, 2000 9:59 PM  > >  > > Chuck McCrobie wrote:  > > > @ > > > What are the shortfalls of the "generic SCSI" in DKDRIVER? > > E > > See the Deja archive of the myriad posts in this newsgroup and/or H > > comp.sys.dec on this topic, and/or review the info. at the following > > URL: > > 9 > > http://www.djesys.com/vms/hobbyist/support.html#cworb  > > I > > Note: The removeable aspect is immaterial and can(should) be ignored.  > >  > @ > Why are you blaming your problems with the Orb drive on VMS?    D The point is that over the course of the last year or so I've hookedG this up to Tekram, SCSI, NEC and Qlogic SCSI cards with everything from F OpenVMS (V6.2-1H3 thru V7.2 Alpha, V6.2 thru V7.2 VAX), Linux, FreeBSDG (V2.5), Mandrake Linux V7.0-2, W/95, MS-DOS V6.2, ... Orb (indeed, most G any 3rd party SCSI device) works with every o.s. that supports the SCSI " card in question *EXCEPT* OpenVMS.  G JF's reason for wanting to abandon OVMS is (IMHO) somewhat less weighty  by comparison.  : If Compaq was smart, they'd be working with Castlewood to:  " o up the capacity of Orb to > 10GB< o come up with an HSx compatible SW SBB with Orb as the core@ o provide OpenVMS, Tru64 and Linux-Alpha support for Orb and Orb derivatives F o market Orb and Orb derivatives as "near-zero" backup window productsA (split HSx mirror-sets, swap Orb cart.'s, kick-off mirror-copies)    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Fri, 24 Nov 2000 22:26:57 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> % Subject: Re: Connecting a CD-writer.. - Message-ID: <3A1F3F91.60F27BB8@earthlink.net>    John Vottero wrote:  >  > > -----Original Message-----@ > > From: David J. Dachtera [mailto:djesys.nospam@earthlink.net]- > > Sent: Thursday, November 23, 2000 9:59 PM  > >  > > Chuck McCrobie wrote:  > > > @ > > > What are the shortfalls of the "generic SCSI" in DKDRIVER? > > E > > See the Deja archive of the myriad posts in this newsgroup and/or H > > comp.sys.dec on this topic, and/or review the info. at the following > > URL: > > 9 > > http://www.djesys.com/vms/hobbyist/support.html#cworb  > > I > > Note: The removeable aspect is immaterial and can(should) be ignored.  > >  > > > Why are you blaming your problems with the Orb drive on VMS?  $ Because DKDRIVER is so damned picky!  E Seriously, I went ahead and put in the current firmware update on the G Orb drive. (Had to reconfigure W/95 (boot to DOS) to do it - WhineBloze D is now hosed, as you might expect; will take a couple days to get itG back together.) The manual eject button on the front of the drive still G doesn't work. Still gotta use the "paper clip" eject button. Otherwise, % it seems to have survived the update.   E The AlphaStation 200 4/233 is currently booted from a V6.2-1H3 CD and A can MOUNT, ANALYZE/DISK, COPY to/from, etc. the Orb drive. I also F checked with V7.1-2. V6.2-1H3 is much less stable with it than V7.1-2.E Gotta get the MicroVAX 3100 going again and try it with that critter.   B The drive *MUST* be spinning and ready when VMS tries to MOUNT it.E MOUNT/NOUNLOAD is recommended. I just waited the usual timeout period H for it to spindown to see what happens when it gets accessed (spins back) up and goes through the MntVerify cycle).   D So, some of the issues have been resolved. Still a ways to go yet...   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------   Date: 24 Nov 2000 18:12:58 GMT( From: brian-DOT-mcneil@easynet.be (BMcN)% Subject: Re: DHCP Client for Multinet + Message-ID: <8FF6C1223BMcN@212.100.160.123>   2 Hey! echong@my-deja.com you went and wrote messageD <8vljlu$rgi$1@nnrp1.deja.com> and forced me to type some nonsense in response...   H >Currently, AFAIK, the only DHCP client for VMS/Multinet --- indeed, theH >only DHCP client for VMS period --- is my port of the Linux DHCP client& >to VMS/Multinet.  It can be found at: > / >http://home.hawaii.rr.com/echong/vms/dhcp.html  > H >You'll need a C compiler (the one on the hobbyist CD (DEC C V6.0) worksF >fine) and the UNZIP tool (ftp://ftp.wku.edu/vms/fileserv/).  The DHCPF >client is known to work on VMS 7.2 and Multinet 4.2A in a Road Runner >cable modem environment.  > E >Note that this DHCP client is NOT supported by Process Software.  In G >fact, it is is not supported by anyone.  I wouldn't recommend it for a E >critical environment, but it should be good enough for hobbyist use. E >I've been using it for more than a year on my computer at home, from $ >which I am sending this message :-) > 	 >-Everett  >  <snip>   Thanks for that!  H However, a couple of days after posting that the local teleco decided to change connect protocols.   C Now I've ordered myself a router - A Nexland ISB2Lan which includes F firewall etc. A little on the expensive side compared with some of theG competition, but shouldn't end up redundant if the connection protocols $ for my ADSL link get changed again.   H Once everything is up and running I should be able to serve up a websiteH straight from my AlphaServer with a little help from the DDNS service at cjb.net :).      --  + Reply to brian<dot>mcneil<at>easynet<dot>be   - The crux of the biscuit is the Apostrophe (')  - F.Z.   ------------------------------  % Date: Fri, 24 Nov 2000 19:54:30 +0100   From: Paul Sture <paul@sture.ch> Subject: Re: EBay vs. QXL + Message-ID: <VA.0000019b.20772d5e@sture.ch>   B In article <8vm25k$35b$1@lisa.gemair.com>, Jordan Henderson wrote:1 > From: jordan@lisa.gemair.com (Jordan Henderson)  > Newsgroups: comp.os.vms  > Subject: Re: EBay vs. QXL " > Date: 24 Nov 2000 10:40:36 -0500 > 2 > In article <dEvT5.157$__5.3272@news.get2net.dk>,& > Philip J. Lewis <phl@bwsc.dk> wrote:O > >QXL seems to be even worse than Ebay on the reliability stakes.  Anyone know  > >what they use ??  > >  > >  >  > Their job postings at: > 6 >   http://www.qxl.com/isroot/html/EN/static/100.shtml > O > Seem to indicate a mix of Solaris, Linux and NT, with Oracle, Sybase and SQL   > Server for databases.  > O > Netcraft shows that they are running "Netscape-Enterprise/3.6 SP2 on unknown" M > to serve up www.qxl.com, but interestingly, the history feature on netcraft J > shows that they were running "Netscape-Enterprise/3.6 SP2 on Solaris" onG > the 20th of November.  I'd guess it's solaris and some http proxy or  L > somesuch is reporting "unknown", or they're hiding this detail on purpose. > L Interestingly I see that Netcraft have added and "uptime" facility to their N site reports. It says there's not enough history for qxl yet - come back in a 	 few days.   O Delving further into their info on this subject VMS is not on the list of OS's  J which report uptime info in response to Netcraft queries. By that I would L assume they mean that the web server software on VMS doesn't report this. I 4 wonder if the VMS port of Apache _does_ supply this?   ___ 
 Paul Sture Switzerland    ------------------------------   Date: 24 Nov 2000 20:04:05 GMT# From: rifepe@langran.iem.csic.espam  Subject: Re: EBay vs. QXL ' Message-ID: <8vmhjl$1mm$1@tejo.csic.es>   g In article <3A1E91FB.38D5A0E7@earthlink.net>, "David J. Dachtera" <djesys.nospam@earthlink.net> writes:  >Jordan Henderson wrote: >>  3 >> In article <dEvT5.157$__5.3272@news.get2net.dk>, ' >> Philip J. Lewis <phl@bwsc.dk> wrote: P >> >QXL seems to be even worse than Ebay on the reliability stakes.  Anyone know >> >what they use ?? >> > >> > >>   >> Their job postings at:  >>  7 >>   http://www.qxl.com/isroot/html/EN/static/100.shtml  >>  O >> Seem to indicate a mix of Solaris, Linux and NT, with Oracle, Sybase and SQL  >> Server for databases. >>  P >> Netcraft shows that they are running "Netscape-Enterprise/3.6 SP2 on unknown"N >> to serve up www.qxl.com, but interestingly, the history feature on netcraftK >> shows that they were running "Netscape-Enterprise/3.6 SP2 on Solaris" on G >> the 20th of November.  I'd guess it's solaris and some http proxy or M >> somesuch is reporting "unknown", or they're hiding this detail on purpose.   G I have Check netscraft for www.openvms.compaq.com and eisner.decus.org. < And both appeard as unknown and like unanvle to read uptime.1 Anyone know what need to be did so they reconice.  Ricardo    > B >Knowing what we know, would ANYone openly admit to running Sun orI >Solaris? Speaking only for myself, I'D think twice about broadcasting it  >world-wide! >  >--  >David J. Dachtera >dba DJE Systems >http://www.djesys.com/  > ; >Unofficial Affordable OpenVMS Home Page and Message Board:   >http://www.djesys.com/vms/soho/ > G >This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings  >is to be expected.  > A >Feel free to exercise your rights of free speech and expression.  > G >However, attacks against individual posters, or groups of posters, are  >strongly discouraged.   ------------------------------  % Date: Fri, 24 Nov 2000 21:08:57 +0100 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>  Subject: Re: EBay vs. QXL ) Message-ID: <3A1ECAD9.A9E8C9F6@gtech.com>    Jordan Henderson wrote: K > Some security minded sites like to hide information so as to reduce their O > exposure to exploits that become known to black hats before they become known  > to themselves.  < That is of very limited value, when running a well-known OS.  = If OS is not supplied, then hackers will try the most obviousN ones first: NT, Solaris, etc..   Arne   ------------------------------  % Date: Fri, 24 Nov 2000 21:06:24 +0100u= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>  Subject: Re: EBay vs. QXLr) Message-ID: <3A1ECA40.F0EE5923@gtech.com>c   Jordan Henderson wrote:P2 > In article <dEvT5.157$__5.3272@news.get2net.dk>,& > Philip J. Lewis <phl@bwsc.dk> wrote:O > >QXL seems to be even worse than Ebay on the reliability stakes.  Anyone know  > >what they use ??c >  > Their job postings at: > 6 >   http://www.qxl.com/isroot/html/EN/static/100.shtml > N > Seem to indicate a mix of Solaris, Linux and NT, with Oracle, Sybase and SQL > Server for databases.- > O > Netcraft shows that they are running "Netscape-Enterprise/3.6 SP2 on unknown" M > to serve up www.qxl.com, but interestingly, the history feature on netcraft9J > shows that they were running "Netscape-Enterprise/3.6 SP2 on Solaris" onF > the 20th of November.  I'd guess it's solaris and some http proxy orL > somesuch is reporting "unknown", or they're hiding this detail on purpose.  A Strange how Solaris and internet sites with a bad uptime seems tob turn up together so often !e   :-)h   Arne   ------------------------------    Date: 24 Nov 2000 15:48:43 -0500/ From: jordan@lisa.gemair.com (Jordan Henderson)n Subject: Re: EBay vs. QXLf* Message-ID: <8vmk7b$io6$1@lisa.gemair.com>  ) In article <3A1ECAD9.A9E8C9F6@gtech.com>,r? Arne =?iso-8859-1?Q?Vajh=F8j?=  <arne.vajhoej@gtech.com> wrote:e >Jordan Henderson wrote:L >> Some security minded sites like to hide information so as to reduce theirP >> exposure to exploits that become known to black hats before they become known >> to themselves.e >a= >That is of very limited value, when running a well-known OS., >g> >If OS is not supplied, then hackers will try the most obvious >ones first: NT, Solaris, etc..l >e  F I agree that this is an example of security through obscurity, which I don't advocate.h  G However, it can be some added protection in that many of the black hats G aren't looking to attack a specific site, but rather it's the case that E they have in their hands a hot new exploit that works against a givene@ configuration and they then go looking for a site to knock over.  C Also, some firewalls will watch protocol level traffic for HTTP and.D start keeping track if suspicious requests are coming from a certainC address.  Suspicious being defined as poorly defined (too much dataiI in an attempt to hit a buffer overflow exploit) or known exploits against J a range of configurations.  Enough of these suspicious requests will causeH the firewall to shutdown any access from that address.  This policy willJ frustrate the black hat who is trying a range of exploits to find one that works in a given configuration.s   > Arne >f   -Jordan Henderson  jordan@greenapple.com    ------------------------------  % Date: Fri, 24 Nov 2000 16:14:58 -0700e$ From: Lee Y T Mah <lytmah@cha.ab.ca>A Subject: HSJ40 dual-redundant controller rolling firmware upgradef) Message-ID: <3A1EF672.22A77F4C@cha.ab.ca>h  * 1. Does version HSJ40 firmware V3.3 exist?> 2. If it does, can a rolling upgrade be done from V3.2 to V3.40     without dropping dual-pathed shadow members?   Background information:sH         An FDDI cluster comprised of 4 AlphaServer's across two computer rooms.E         Two Alpha's in each computer room.  All Alpha's at VMS 7.1-2.dD         The StorageWorks disk farm has Compaq 4.3 and 9.1 GB drives.F         All Alpha's participate in host-based volume shadowing using a pair>                 of HSJ40'S at V3.2 in each room.  For example, HSJ11/HSJ12iC                 in computer room 1, HSJ21/HSJ22 in computer room 2.-:         The shadow set DSA11 is comprised of shadow memberF                 DUA11 in computer room 1 and DUA21 in computer room 2.G                 DUA11 and DUA21 are dual-pathed to their respective HSJn8                 controllers HSJ11/HSJ12 and HSJ21/HSJ22.H                 Compaq says the rolling upgrade procedure is recommended onlyE                 when upgrading to an adjacent version.  That is, froma V3.3 toaG                 V3.4.  However, that would be true only if V3.3 exists.kF                 Has anyone gone directly from V3.2 to V3.4 without anyF                 problems, such as dropping shadow members (serious) or@                 shadow sets going into the merge or copy states? TIA.     -- LeeE  C Lee Y T Mah                                Capital Health Authoritys? Email: lytmah@cha.ab.ca            Information Systems, RAH CSCm   ------------------------------  % Date: Fri, 24 Nov 2000 22:37:10 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>tE Subject: Re: HSJ40 dual-redundant controller rolling firmware upgradeo- Message-ID: <3A1F41F6.D47DC553@earthlink.net>E   Lee Y T Mah wrote: > , > 1. Does version HSJ40 firmware V3.3 exist?   Don't know.   @ > 2. If it does, can a rolling upgrade be done from V3.2 to V3.42 >     without dropping dual-pathed shadow members?  H In this scenario, you will *ALWAYS* end up causing all units to be takenD over by the "surviving" member of the dual-redundant set when one ofD them is being upgraded. When both units in a dual-redundant pair areC upgraded and back on-line, PREFERRED_HOST settings will again be inhH effect. If you have not set preferred hosts, you may need to restore theB normal hosting preferences using PREFER (SYS$EXAMPLES:PREFER.MAR).  D This should have no appreciable impact on shadow-set conditions, but1 check just to be sure when you're done upgrading.t  C Ideally, if you have enough equipment available, shadow-set membersl2 should be hosted by separate dual-redundant pairs.   My $0.02 worth...=   -- p David J. Dachtera- dba DJE Systems- http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/e  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  # Date: Fri, 24 Nov 2000 18:24:15 GMTC8 From: "Volckaerts, Tommy" <Tommy.Volckaerts@Advalvas.be>" Subject: Re: openvsm and vga cards4 Message-ID: <jnyT5.48$Ty.2898@nreader1.kpnqwest.net>  H Tnx for the replies, I can get my hands on both of those cards as I have very good sources at Compaq.    3 "Rudolf Wingert" <win@fom.fgan.de> wrote in messaged0 news:200011230745.IAA26343@sinet1.fom.fgan.de... > Hello, >iF > the S3 Trio64V+ with 2mb should work under OpenVMS. We did have fourE > of this  (but three only with oneMB), working under OpenVMS. But itIB > is a low end 2D graohic adpater with eight bit deepth. So we didC > change to the PowerStorm4D20. This one you can't get anymore. Now,E > you have to buy the ELSA Gloria Synergy. This card should work alsow= > in a PC with LINUX and WINxx. I do not know the other OSes.T >p > Regards Rudolf Wingert >t >    ------------------------------  % Date: Fri, 24 Nov 2000 13:18:37 -0500a- From: "Island Computers" <sales@islandco.com>t" Subject: Re: openvsm and vga cards/ Message-ID: <t1tbqb8nhqtub6@corp.supernews.com>h   Sorry,   chhhhhhhhppputtttt !M      H As to the B2 variants of the ELSA Synergy (b2-PBXGK-BB) - COmpaq may say- that they're available - but try ordering oner   We have them in stock-     David Tb2 <paddy.o'brien@zzz.tg.nsw.gov.au> wrote in message/ news:01JWXIRM4UF60004DL@tgmail.tg.nsw.gov.au...o | David, |i? | >Elsa Gloria Synergy works great with all of these plus Tru64e | >o | >$250 each |h |*2 | Wrong newsgroup.  Rudolf mainly asked about VMS. | ! | Isn't Tru64 a "spit word" here.l |e |o   ------------------------------   Date: 23 Nov 2000 23:00:03 GMT& From: Cthulhu <cthulhu@kadath.deep.it> Subject: Re: remote DECWindows( Message-ID: <8vk7hj$vh$1@kadath.deep.it>  " azog <azog@nospam.azog.org> wrote:  L > There was a recent thread where someone couldn't get DECWindows to displayK > to his remote X server. He posted the problem was solved, but didn't postoK > the solution, so I'm wondering what my problem is, trying to run remote Xc > apps.i  
 It was me!C My problem was a misconfigured linux router that was doing half-way  NAT, nothing to do with VMS.  ? I can see you have found the answer. I did the same mistake. :)D  
 	tailoringly,  	   Cthulhua   -- o  G        Ph'nglui mglw'nafh Cthulhu http://www.rlyeh.it wgah'nagl fhtgan!c# 		        <cthulhu at rlyeh dot it>o   ------------------------------  % Date: Fri, 24 Nov 2000 19:18:56 -0500w- From: JF Mezei <jfmezei.spamnot@videotron.ca>i5 Subject: Starting a DECWINDOWS app from a Microvax II , Message-ID: <3A1F0563.58EFF76C@videotron.ca>  7 I have my all mighty teenage Microvax II (node: VELO). uC I have a younger Vaxstation 3100 with Decwindows Motif (node: BIKE)   J Both are in a heteregonous cluster, each with access to the other's disks. Decnet installed.e  K I beleive I installed VELO with the base Decwindows. (How can I make sure ?oF CREATE/TERMINAL fails since the file isn't found). However, I have theK IGNORE_DECWINDOWS logical set, and of course, VELO has the SYSGEN paremeter  for windowing system set to 0. u   Here is the question:2  N What are the different ways for a process on VELO to start a windowing program	 in BIKE ?h  K For instance, I'd like a process running on VELO to cause a TIFF file to beV& displayed with the CDA viewer on BIKE.  8 What exactly does the DECWINDOWS base services provide ?   ------------------------------  % Date: Fri, 24 Nov 2000 19:54:30 +0100l  From: Paul Sture <paul@sture.ch>$ Subject: Re: [Q]"vi" section for TPU+ Message-ID: <VA.0000019a.20772ba5@sture.ch>n  B In article <8vj4rc$r6g$1@lisa.gemair.com>, Jordan Henderson wrote:1 > From: jordan@lisa.gemair.com (Jordan Henderson)  > Newsgroups: comp.os.vmse& > Subject: Re: [Q]"vi" section for TPU" > Date: 23 Nov 2000 08:07:56 -0500 > P > In article <VA.00000198.1868f5a7@sture.ch>, Paul Sture  <paul@sture.ch> wrote:E > >In article <8vgtfk$olu$1@lisa.gemair.com>, Jordan Henderson wrote:t > >> eK > >> Hey, I really have nothing against TPU, well not much (lack of UNDO isrI > >> annoying - I think I'm going to regret saying that...), but I don't -I > >> have it on every system that I need to use.  When I do use TPU, I'm cF > >> too used to the 'ol EDT keyboard, which is more than a little bit' > >> difficult to emulate on my laptop.o > >> e$ > >[snip] to avoid an editor war :-) > >eQ > >In TPU/EVE, issue DO followed by SET KEPYPAD EDT (can be abbreviated to S K E t	 > >IIRC).P > >n8 > >Alternatively slot the following into your login.com: > >e > >$ define eve$keypad edt > G > Yes, I know about edt keypad mode in TPU, what I don't know is how tow6 > use the application keypad effectively on my laptop. > & Duh! I didn't read your post properly.   ___r
 Paul Sture Switzerlandt   ------------------------------   End of INFO-VAX 2000.658 ************************