1 INFO-VAX	Mon, 07 May 2001	Volume 2001 : Issue 255       Contents:, Re: 1GHz Alpha EV68CB Microprocessor Exposed. Re: ABS - backup service from NT to VMS device ALPHAbook1, Tadpole, VMS Re: ALPHAbook1, Tadpole, VMS4 bug or feature: Elapsed CPU :17-NOV-1858 00:00:00.00H Re: Bypassing LOGOUT.COM (was: Re: TCP/IP 5.1 Allow Host Table To Wiped)H Re: Bypassing LOGOUT.COM (was: Re: TCP/IP 5.1 Allow Host Table To Wiped)D Re: Bypassing LOGOUT.COM (was: TCP/IP 5.1 Allow Host Table To Wiped)! Cleaning up the License database. A Re: Conference: CETS-2001 - Content Advisory Teams Phase I report ' FREE:  MicroVAX II shell (BA23 cabinet)  Re: Global delete in UAF?  Re: Global delete in UAF?  Re: Glue for a BA356-KC  Re: GNU C++ Compiler  HTF 4000/XXX Internal SCSI Cable Re: LAT v Telnet Performance' Motif/X Training: June 18-22 Boston, MA  Re: mozilla .81  Re: mozilla .81 - MV2000/VS2000 4MB boards going to a good home  Re: OT: Pioneer 10 lives! = Re: Reply before or after? (was: seeing escapes is believing)  Re: SCSSYSTEMID / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants / Re: The Internet, Tru64 and other unix variants  Re: VAX vs AXP executable  Re: VAX vs AXP executable  VxWorks ) What is the best way to erase SCSI disks? - Re: What is the best way to erase SCSI disks? ) What is the best way to erase SCSI disks? - Re: What is the best way to erase SCSI disks? - Re: What is the best way to erase SCSI disks?  Re: Xserver NodeName- Re: [DCPS] Duplex Problem with HP Laserjet 5M   F ----------------------------------------------------------------------    Date: 07 May 2001 12:28:07 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> 5 Subject: Re: 1GHz Alpha EV68CB Microprocessor Exposed H Message-ID: <y4d79llah4.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  . Paul Repacholi <prep@prep.synonet.com> writes:  M > Palimino is out now in mobile form. The 1.7 is reported/rumoured to be RSN.   J I have the distinct impression that availability of AMD processors is moreK driven by positioning with respect to Intel processors than to what the fab N can deliver, i.e., always have a few aces up your sleeve in case Intel managesL to deliver something new (not necessarily better, depending on your measure) than play them now.    	Jan   ------------------------------  $ Date: Mon, 7 May 2001 11:12:19 -0400- From: "Peter Weaver" <peter.weaver@stelco.ca> 7 Subject: Re: ABS - backup service from NT to VMS device 4 Message-ID: <5YyJ6.235271$Z2.2516384@nnrp1.uunet.ca>  F "Curtis Rempel" <vmsguy.no.spam.here.please@home.com> wrote in message2 news:etKI6.164$Hk4.13289@news1.rdc1.ab.home.com... >...; > We have since killed ABS since Digital and now Compaq has  consistentlyF > demonstrated that they cannot get their act together.  We have moved forward C > with Veritas NetBackup running on a Tru64 AlphaServer.  We tested  the VMS F > client support extremely rigorously and found no major deficiencies.  E How do you handle your system drives? Aliases and Contiguous files on  non-system drives?  D > Veritas support for the VMS client is out of the UK (Chertsey) and Alan FayD > is 110% top notch (thanks for all your extremely helpful and quick	 responses 	 > Alan!).   C Seconded, he is very quick to fix problems. I did get a bit nervous E when I recieved a new image at 9:40 and noticed that the link time on A it was 9:30 (after converting for time zones) - but the new image  fixed the problem.     >...E > the software and ask for your money back - ALL of it.  Having grown  up with B > Digital and become accustomed to the stellar engineering efforts made by F > various product groups, it was an absolute nightmare to believe thatD > something like ABS was actually released in public as a product by Digital.= > I would have been personally embarrassed myself to have let  something like > ABS see the light of day.   D Compaq Analyze, DSN 2.2, DSN 3.0, ABS... How is this garbage gettingD through the door at Compaq? How do we get Compaq's attention so theyB know that we expect all the products on our VMS systems to work as well as the base OS itself?    ------------------------------  % Date: Mon, 07 May 2001 11:07:37 +0200 $ From: Michael Unger <unger@decus.de>! Subject: ALPHAbook1, Tadpole, VMS * Message-ID: <009FBA6E.63B558CA.5@decus.de>  ; > From: Phillip Helbig <HELBPHI@SYSDEV.DEUTSCHE-BOERSE.COM> ' > Subject: Re: ALPHAbook1, Tadpole, VMS  >   H > > I see that the ALPHAbook1 is listed as supported in the VMS 7.2 SPD. > > L > > I haven't been able to find much information on this product, neither at" > > www.tadpole.com nor elsewhere. >   I > I have since found out that, although it is no longer made, it is still I > supported by Tadpole, and they sell refurbished ones (for a fraction of  > the original cost).  >   , > It WOULD make a nice gift for myself!  :-)  ( I guess you are not the only one ... ;-)  I > As I mentioned, it appears that current Compaq software is supported on H > it.  Any guess how long this will continue to be the case?  Should newI > software run on it for approximately the length of time as new software 2 > is supported on hardware made by Digital/Compaq?  A I have no definite answer to this question, but: as far as I know F hardware modules on Alpha systems are removed earlier from the list ofD supported options than on VAX systems. If I remember correctly thereA are a few "non-standard" modules in this notebook. As always, new F OpenVMS versions are tested on current hardware and limited testing is done on (rather) old hardware.  D I got a datasheet of this ALPHAbook years ago. I will have to search for a while ... :-)    Michael    ------------------------------   Date: 7 May 2001 11:57:27 GMT 3 From: gartmann@immunbio.mpg.de (Christoph Gartmann) % Subject: Re: ALPHAbook1, Tadpole, VMS 0 Message-ID: <9d62j7$bla$1@n.ruf.uni-freiburg.de>  Q In article <009FBA6E.63B558CA.5@decus.de>, Michael Unger <unger@decus.de> writes: < >> From: Phillip Helbig <HELBPHI@SYSDEV.DEUTSCHE-BOERSE.COM>( >> Subject: Re: ALPHAbook1, Tadpole, VMS >>    I >> > I see that the ALPHAbook1 is listed as supported in the VMS 7.2 SPD.  >> >  M >> > I haven't been able to find much information on this product, neither at # >> > www.tadpole.com nor elsewhere.  >>    J >> I have since found out that, although it is no longer made, it is stillJ >> supported by Tadpole, and they sell refurbished ones (for a fraction of >> the original cost). >>    - >> It WOULD make a nice gift for myself!  :-)  > ) >I guess you are not the only one ... ;-)  > J >> As I mentioned, it appears that current Compaq software is supported onI >> it.  Any guess how long this will continue to be the case?  Should new J >> software run on it for approximately the length of time as new software3 >> is supported on hardware made by Digital/Compaq?  > B >I have no definite answer to this question, but: as far as I knowG >hardware modules on Alpha systems are removed earlier from the list of E >supported options than on VAX systems. If I remember correctly there B >are a few "non-standard" modules in this notebook. As always, newG >OpenVMS versions are tested on current hardware and limited testing is  >done on (rather) old hardware.  > E >I got a datasheet of this ALPHAbook years ago. I will have to search  >for a while ... :-)  O As to my knowledge the VMS gurus at Compaq have one as well. And I would expect < that they will support it as long as it is running there ;-)   Regards,    Christoph Gartmann   H -- --------------------------------------------------------------------+H | Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -452 |H | Immunbiologie                                                        |H | Postfach 1169                 Internet: gartmann@immunbio.mpg.de     |H | D-79011  Freiburg, FRG                                               |H +--------- http://www.immunbio.mpg.de/home/english/menue.html ---------+   ------------------------------  % Date: Mon, 07 May 2001 16:20:39 +0200 $ From: Michael Unger <unger@decus.de>= Subject: bug or feature: Elapsed CPU :17-NOV-1858 00:00:00.00 * Message-ID: <009FBA9A.1E874A84.7@decus.de>  & > Date: Mon, 7 May 2001 15:08:22 +0200; > From: Phillip Helbig <HELBPHI@SYSDEV.DEUTSCHE-BOERSE.COM> ? > Subject: bug or feature: Elapsed CPU :17-NOV-1858 00:00:00.00  >   J > If, within the precision, the elapsed CPU is 0 in the output of the show' > status command, instead of outputting  >   " >    Elapsed CPU :   0 00:00:00.01 >    > the output is  >   ) >    Elapsed CPU :17-NOV-1858 00:00:00.00  >    > Bug or feature?  >   H > Of course, this date is the start-date of VMS, so it is not completely: > surprising that this appears, but it looks inconsistent.  M If I don't mix up something "absolute time" is a _positive_ number and "delta O time" is a _negative_ number in the internal representation. So a delta time of E zero had to be a _negative_ zero value which simply doesn't exist :-)   
 Michael Unger    ------------------------------    Date: 07 May 2001 12:19:32 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> Q Subject: Re: Bypassing LOGOUT.COM (was: Re: TCP/IP 5.1 Allow Host Table To Wiped) H Message-ID: <y4g0ehlavf.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  ; Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes:   E > > Still, I've always kinda wondered why there is no SYS$SYLOGOUT or K > > equiv., y'know? ...or an LGOCMD field in the UAF? ...some other hook in  > > the process run-down code?  J That is available, but only in an inner mode (at least exec), not as a DCL command procedure.  D > It is hard to depend on the process context, so this capability isI > provided in the most robust fashion possible -- the process termination 
 > mailbox.  J Well, that informs you of the subject process's recently-occured death; itK doesn't allow you to execute code in its context just before it dies, which 5 I understood the intent of the original poster to be.    	Jan   ------------------------------   Date: 7 May 2001 12:59:52 GMT & From: dsf@frontiernet.net (Dan Foster)Q Subject: Re: Bypassing LOGOUT.COM (was: Re: TCP/IP 5.1 Allow Host Table To Wiped) 4 Message-ID: <9d6688$q94$1@node17.cwnet.roc.gblx.net>  0 In article <9blH6.369$5I.7462@news.cpqcorp.net>,3 Hoff Hoffman <hoffman@xdelta.zko.dec.nospam> wrote: O >In article <VA.00000378.24e8d2bd@sture.ch>, Paul Sture <paul@sture.ch> writes:  > I >  There are a number of ways to log off without triggering a LOGOUT.COM  H >  established via the LOGOUT symbol.  The seldom-used EOJ command, via   . True story from my college days (a while ago):  L I discovered this neat command called 'EOJ' (End Of Job, IIRC). At the time,L there was a running joke with friends on how many different forms of logging them out that I could discover.   I For this one, I told a friend named Joe about the EOJ command, and warned  him not to do it.   C He ran it anyway, and was quite astonished to find out what it did.   I When asked about why he ran it anyway, his response? "EOJ? I thought that - was just you spelling my name backwards." :-)   K Alas, I wasn't the one who found the most interesting way of logging people H out of a system: a well-crafted plan.txt file with certain "interesting"I characters, when read on a VT220 terminal, would result in the user being L effectively logged out or disconnected (don't recall; it's been a while). SoM friends who FINGER'd the friend (who found this) was quite surprised :-) This / "feature" didn't stay up for very long, though.   M I always wondered how EOJ differed from LOGOUT in terms of execution, if any.    -Dan   ------------------------------  % Date: Mon, 07 May 2001 17:56:48 +0100   From: Paul Sture <paul@sture.ch>M Subject: Re: Bypassing LOGOUT.COM (was: TCP/IP 5.1 Allow Host Table To Wiped) + Message-ID: <VA.00000383.20d9d8ee@sture.ch>   F In article <9d6688$q94$1@node17.cwnet.roc.gblx.net>, Dan Foster wrote:( > From: dsf@frontiernet.net (Dan Foster) > Newsgroups: comp.os.vms S > Subject: Re: Bypassing LOGOUT.COM (was: Re: TCP/IP 5.1 Allow Host Table To Wiped)  > Date: 7 May 2001 12:59:52 GMT  > 2 > In article <9blH6.369$5I.7462@news.cpqcorp.net>,5 > Hoff Hoffman <hoffman@xdelta.zko.dec.nospam> wrote: Q > >In article <VA.00000378.24e8d2bd@sture.ch>, Paul Sture <paul@sture.ch> writes:  > > K > >  There are a number of ways to log off without triggering a LOGOUT.COM  J > >  established via the LOGOUT symbol.  The seldom-used EOJ command, via  > 0 > True story from my college days (a while ago): > N > I discovered this neat command called 'EOJ' (End Of Job, IIRC). At the time,N > there was a running joke with friends on how many different forms of logging! > them out that I could discover.  > K > For this one, I told a friend named Joe about the EOJ command, and warned  > him not to do it.  > E > He ran it anyway, and was quite astonished to find out what it did.  > K > When asked about why he ran it anyway, his response? "EOJ? I thought that / > was just you spelling my name backwards." :-)  >    :-)   M > Alas, I wasn't the one who found the most interesting way of logging people J > out of a system: a well-crafted plan.txt file with certain "interesting"K > characters, when read on a VT220 terminal, would result in the user being N > effectively logged out or disconnected (don't recall; it's been a while). SoO > friends who FINGER'd the friend (who found this) was quite surprised :-) This 1 > "feature" didn't stay up for very long, though.  > O > I always wondered how EOJ differed from LOGOUT in terms of execution, if any.  >   : EOJ prints the same message as LOGOUT/BRIEF (the default).$ LOGOUT provides a /HANGUP qualifier.$ STOP/ID=0 doesn't print any message.  R IIRC LOGOUT will fail if someone has installed a new version of DCLTABLES.EXE but P not re-INSTALLed it (but it's a loong time ago - it might be mistaken about the O image name there). STOP/ID=0 can be used to terminate the process in this case.  ___ 
 Paul Sture Switzerland    ------------------------------   Date: 7 May 01 08:25:22 EDT ! From: smithp01@mcrc16.med.nyu.edu * Subject: Cleaning up the License database.- Message-ID: <alXyXs3l5s$+@mcrc16.med.nyu.edu>   L I have ~80-odd expired licenses in the license d/b that I'd like to get rid  of: disable would be fine.  M I can do it by hand, but a script wouold be better.  Is there an easy way to  J get rid of them?  It really slows down a reboot while the machine reports  each stupid expired license.   Thanks!    L +------------ 8F EF 51 4E 4F 23 22 AF  6A 41 D6 C0 AE 31 B1 82 ------------+L |Ross Smith, Academic Computing (RCR), NYU-SoM, 550 First Ave, NY, NY 10016|L |E-Mail:  SMITHP01@MED.NYU.EDU   Phone:  (212)263-5356:  FAX: (212)263-8139|L +-------------- <http://www.med.nyu.edu/people/P.Smith.html> --------------+   ------------------------------  % Date: Mon, 07 May 2001 10:30:32 -0700 0 From: Mark Berryman <Mark.Berryman@Mvb.Saic.Com>J Subject: Re: Conference: CETS-2001 - Content Advisory Teams Phase I report, Message-ID: <3AF67948.254CA350@Mvb.Saic.Com>   Paul Repacholi wrote:  > 4 > Mark Berryman <Mark.Berryman@Mvb.Saic.Com> writes: > H > > I see a PDF file there.  What is VMS-incompatible about PDF?  I haveE > > at least 4 different programs on my VMS system that can read PDF.  > H > I 'only' have 2, GS and XPDF. I do have a big pile of Decpaq PDF files > that are unreadable...  F There is also the commercial version from Applied Synergy and the JavaF version from Adobe (you have run the Java version using the FAST VM toE get acceptable performance, if you use the Fast VM the performance of G the Java version is roughly equivalent to ghostscript although it still + takes longer than ghostscript to start up).   = XV will also display PDF files but, since it actually invokes 7 ghostscript to convert the file first I don't count it.   
 Mark Berryman    ------------------------------  # Date: Mon, 07 May 2001 15:31:25 GMT , From: "Frank Sapienza" <sapienza@noesys.com>0 Subject: FREE:  MicroVAX II shell (BA23 cabinet): Message-ID: <hdzJ6.41532$4X4.6454233@news02.optonline.net>  H Well, I think it's a BA23.  It's the narrow tower -- it's either BA23 or BA123.  G Whatever.  When I last cannabilized this system everything worked fine.bL What remains is the tower with Q-bus backplane and power supply, an internalI TK50 drive, an RD54-compatible drive, and a bunch of screws and knobs.  IoJ also have the hardware maintainance books.  And there's a CPU board with aD bad console port (output, no input).  The CPU actually booted last I	 remember.T  L Unit is located in East Northport, Long Island, New York.  You want it, come and get it.a  J Of course, since there wasn't any interest in the VR299, maybe this'll get trashed as well.     Frank Sapienza sapienza@noesys.com6   ------------------------------  $ Date: Fri, 4 May 2001 22:37:39 -0400* From: "Andy Stoffel" <acs@fcgnetworks.net>" Subject: Re: Global delete in UAF?5 Message-ID: <PkvJ6.4462$oa2.97624@news6.giganews.com>d  / "Russ Leathe" <russ@goron.edu> wrote in messagee  news:cWEI6.19$tJ4.1133@client...I > I recently took over a VAX 4000 with about 500 user accounts.  Over theaH > years different priv were assigned including sysprv to the majority ofI > users.  I can only assume that the person who created the accounts useda > "copy" from a priv account.n   > My question is...   L > can I globally modify all these accounts and remove all priv except netmbx
 > and tmpmbx?   B Yes. Of course, you might want to check first to see WHY different; accounts were given what privs so that when you change themt7 you can provide other access methods to whatever systemC; resources those accounts were given privs to access if theyi% still need to. (If that makes sense).-  9 Taking a system with a "questionable" or "loose" security < history and cleaning it up can be time consuming and complex> and not something you can fix in an hour or two... been there,) done that, still have nightmares.... %-).     (And when the folks? needing the security "cleanup" think you can fix it at the tail.? end of other things but expect it to be done for free... argh!)    -Andy- --' VMS - When access to your data matters.i   ------------------------------  % Date: Mon, 07 May 2001 17:56:49 +0100i  From: Paul Sture <paul@sture.ch>" Subject: Re: Global delete in UAF?+ Message-ID: <VA.00000384.20d9db15@sture.ch>e  I In article <PkvJ6.4462$oa2.97624@news6.giganews.com>, Andy Stoffel wrote:e, > From: "Andy Stoffel" <acs@fcgnetworks.net> > Newsgroups: comp.os.vms-$ > Subject: Re: Global delete in UAF?& > Date: Fri, 4 May 2001 22:37:39 -0400 >  > 1 > "Russ Leathe" <russ@goron.edu> wrote in message " > news:cWEI6.19$tJ4.1133@client...K > > I recently took over a VAX 4000 with about 500 user accounts.  Over theeJ > > years different priv were assigned including sysprv to the majority ofK > > users.  I can only assume that the person who created the accounts useda > > "copy" from a priv account.t >  > > My question is...c > N > > can I globally modify all these accounts and remove all priv except netmbx > > and tmpmbx?s > D > Yes. Of course, you might want to check first to see WHY different= > accounts were given what privs so that when you change themn9 > you can provide other access methods to whatever systemp= > resources those accounts were given privs to access if theyy' > still need to. (If that makes sense).r >tN I can think of at least one scenario where SYSPRV may have been granted to getO around file protection problems. Users from different groups sharing a scratch  / directory for sort and spool files for example.r  N IIRC, somewhere around the V6.0 - V6.1 timezone, security was tightened up so L that a user couldn't create a higher version of a given file if they didn't N have write or delete access to the existing file. The real life example I saw L used a temporary workaround of setting the default protection to WO:WRED in E SYLOGIN.COM until they figured how to do it via ACLs on the relevant . directories.  N Russ, rather than removing SYSPRV globally, I'd recommend investigating which O users from different groups share scratch or other directories. And start with t7 a couple of users first to see if that breaks anything.a  ; > Taking a system with a "questionable" or "loose" securityM> > history and cleaning it up can be time consuming and complex@ > and not something you can fix in an hour or two... been there,+ > done that, still have nightmares.... %-).A >A$ Agreed. It can be a real rat's nest.   >  (And when the folksA > needing the security "cleanup" think you can fix it at the tail A > end of other things but expect it to be done for free... argh!)P >  Argh indeed! ___p
 Paul Sture Switzerland.   ------------------------------  % Date: Mon, 07 May 2001 10:32:16 -0700e! From: Shane.F.Smith@Healthnet.coml  Subject: Re: Glue for a BA356-KCD Message-ID: <OFC0F528E7.F7E1EFAD-ON88256A45.00601B68@foundation.com>  K For larger holes, where there's some plastic missing, I've had some successcJ with epoxy putty. Put a little too much on, and sand down the visible sideG when it's completely cured. It's not as tough as the 24-hour epoxy glueoJ though. If you need structural strength epoxy a metal or plastic backplate0 on, and fill in the surface hole with the putty.   Shaneo          F rdeininger@mindspring.com (Robert Deininger) on 05/05/2001 08:05:55 AM  > Please respond to rdeininger@mindspring.com (Robert Deininger)   To:   Info-VAX@Mvb.Saic.Comd cc:o  ! Subject:  Re: Glue for a BA356-KCr    < In article <3AF31BB9.3FE9E0B@pressenter.com>, Lyndon Bartels  <lbartels@pressenter.com> wrote:  H > I have aquired a couple BA356-KC (pedestal) and while the shelf is notC > damaged, the "cap" and "door" have some breaks and/or cracks. AnydE > recommendations on a glue that I can rely on to fix said cracks 'n'e > such?hF > I tried superglue, and it held for a while... but not when put under > some stress.  H Try some epoxy from the hardware store.  Not the 5-minute stuff, but theE kind that cures in 12-24 hours.  That will hold on almost any sort ofr plastic.   -- Robert Deininger rdeininger@mindspring.coma   ------------------------------  % Date: Mon, 07 May 2001 08:46:51 +0200.= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>  Subject: Re: GNU C++ CompilerH) Message-ID: <3AF644DB.AD4DC92B@gtech.com>2   "A. Irmak" wrote:IH > can anybody tell me where I can obtain a VMS distribution of GNU C++ ?   There are some links at:+   http://www.levitte.org/~ava/vms_gnu.htmlxh   Arne   ------------------------------  % Date: Mon, 07 May 2001 10:32:35 -0700e+ From: "Barry Treahy, Jr." <treahy@mmaz.com>e) Subject: HTF 4000/XXX Internal SCSI Cablea( Message-ID: <3AF6DC33.1C5C34A2@mmaz.com>  H Can anyone make a recommendation on a good web site that illustrates theH SCSI cable and not just a model number and description?  I know what I'mF looking for, but I do not know if a DEC/Compaq model number exists for6 it nor do I know if an after market of it might exist.  F For those familiar with the DSSI expansion board that rides on the CPUF board of the VAX 4000/xxx systems, there is an internal cable set thatD runs from the expansion board to an external interface (in this caseH DSSI) with the bulkhead strip.  I'm looking for that same type of cable,8 interface, bulkhead but for a 68-pin HD SCSI connection.   Regards,   Barry    --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIOI  A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028    ------------------------------  % Date: Mon, 07 May 2001 08:30:42 -0700 + From: "Barry Treahy, Jr." <treahy@mmaz.com>s% Subject: Re: LAT v Telnet Performancee( Message-ID: <3AF6BFA2.463A855F@mmaz.com>   Paul Repacholi wrote:-  ) > "John Vottero" <John@mvpsi.com> writes:- > H > > If someone is saying that you have to stop using LAT so that you canB > > stop bridging across the slow links between the LANs, they are > > probably correct.  > G > The problem is the 'slow' not the bridging. Put a router with lots ofF> > buffering in, go all IP and watch it all collapse in a heap.  H I ran remote LAT from Boston to Albuquerque, Albuquerque to Phoenix, andE Phoenix to Hartford over a 56k frame relay circuits using compressionhJ bridges for over three years, flawlessly.  Even with heavy IP traffic fromL ftp or http, the LAT sessions never timed out.  Perhaps I was lucky, or justJ may be, these bridges we're real good.  All I know is that we did not have" all of the rumored LAT problems...   Regards,   Barry1 --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO0  A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028    ------------------------------   Date: 07 May 2001 14:11:22 GMT! From: Mark Hatch <mhatch@ics.com>00 Subject: Motif/X Training: June 18-22 Boston, MA' Message-ID: <3AF6AD08.8BF3FBB1@ics.com>,   Hi,i  G We're holding another round of public X/Motif training on June 18-22 in.' Burlington, Mass (just outside Boston).   @ This challenging 5-day lab course provides all the essentials ofC programming the X Window System and the Motif widget set, includinge
 Motif 2.1.  > The course outline can be found at:  http://www.ics.com/xmotif  A  To register, or for more information (including pricing), email:r! info@ics.com or call 800.704.6825e   Mark   ------------------------------  # Date: Mon, 07 May 2001 12:18:06 GMTC' From: Colin Blake <colin@theblakes.com>s Subject: Re: mozilla .81- Message-ID: <3AF69279.F937D6D1@theblakes.com>i  j I thought they'd fixed these "write to the install tree" problems. I guess not. Bug 42184 is one such bug.  T For now, you need to have write access to all the RDF files in the chrome directory.   Colin.   Everett Chong wrote:  J > I encountered essentially the same problem.  After some experimentation,+ > I discovered that the file protections ondD > SYS$COMMON:[MOZILLA.CHROME]USER*.RDF need to be WORLD:RWED!!  It's > definitely a bug in my book! >-	 > Everetts >e& > system@niuhep.physics.niu.edu wrote: > >y[ > > In article <3AEE8720.E8C2639B@theblakes.com>, Colin Blake <colin@theblakes.com> writes:iy > > >Double check the file/directory protections. I've seen cases before where lack of access to one of the MozIlla files-G > > >causes this sort of a problem (though to be honest, not recently).  > > >su > > >The other thing to check is quotas. Look for differences between the privileged and non-privileged accounts. Seee` > > >http://www.openvms.compaq.com/openvms/products/ips/mozilla_relnotes.html#param for details. > >a/ > > Thanks I'll have another look to make sure.8 > >d
 > > Robert   ------------------------------  # Date: Mon, 07 May 2001 14:31:36 GMT ' From: Colin Blake <colin@theblakes.com>M Subject: Re: mozilla .81- Message-ID: <3AF6B1BE.6BF93CAA@theblakes.com>i  t I've been doing some more testing and now believe that as long as all the RDF files are present and W:R then that is{ enough. I think the problem was caused by the kit not containing all the RDF files, and when Mozilla is run without all the Q RDF files it will auto-create them, and this is where the write access is needed.o  e The M0.9 kit should contain all the required RDF files and hopefully then the following will be true:w   - SYSTEM installs Mozillao!   - no files are left world writet#   - non-priv'd user can run Mozilla   p If anyone has any problems in this area with M0.9 (or later) please enter details into Bugzilla bug number 791474 (http://bugzilla.mozilla.org/show_bug.cgi?id=79147).   ------------------------------  $ Date: Mon, 7 May 2001 10:36:17 +01006 From: "Adrian Lumsden" <A.Lumsden@spam.trap.xdt.co.uk>6 Subject: MV2000/VS2000 4MB boards going to a good home% Message-ID: <e8uJ6.38$IQ2.6073@wards>u  @ I am in the process of sorting out a big list of stuff that I amA disposing of before we leave the UK to go to live in New Zealand.   C For the moment though I have two 4MB memory expansion modules for a B MicroVAX or VAX Station 2000. One of them has even got the plastic mounting posts with it!H  : Going free to anyone who will collect or pay for shipping.    
 best regards,<   Adrian Lumsden   Tel: +44 (1455) 828896   ------------------------------    Date: 07 May 2001 12:59:43 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>A" Subject: Re: OT: Pioneer 10 lives!H Message-ID: <y4ae4pl90g.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  L They also mentioned (can't remember where I read it) that last summer, theirK last PDP (no number) broke that was used for command generation. They first H had to port the code to a PC (can't have been easy...) before they could generate new commands.   	Jan   ------------------------------  $ Date: Mon, 7 May 2001 16:30:19 +0200: From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl>F Subject: Re: Reply before or after? (was: seeing escapes is believing)I Message-ID: <Pine.LNX.4.21.0105071619160.8966-100000@irys.stanpol.com.pl>o  * On Mon, 30 Apr 2001, Christof Brass wrote:  $ >+"Gotfryd Smolik, VMS lists" wrote: >+ >+[SNIP] >+: >+> +If there is a better reason or an habit or any other  >+> +etiquette-based reason to; >+> +post replies *after* the original text, I will change.O >+> ( >+> AFAIR that was a standard in past :) >+= >+Is there anything wrong with intermixing request and reply?u    *NO* ! ;  My post was for format "full answer & next full original".-1  "Intermixing" IMHO is the "best readable" way :)    [...]s= >+I suggest to use ">" as an indicator where the lines of the A >+request are. This is the normal "request indication" character.   8  I know. Althought that was not a standard in past, some; "intelligent programs" has function for automatic selectionp1 of answers; I don't know how reliably that works.o  9 >+AFAIK there is only one person from several NGs I visit   1  At least some time ago here was more than one ;)d  A >+regularly who uses a different character. It would be easier ton3 >+read the posts if only the ">" character is used.s  -  If that makes any differrence I will change.o7  The reason: if you see answer for answer for answer :)e b.ex.:  Person 1 posts: > Preson 2 posts:/ > > Person 3 posts:e > > > Person 4 posts:t > > > > Person 5 posts:u  1 (you *can* see something like on info-vax !) here 0 may be problem to count the original position :)3  But if anyone has trouble with his mailer programmb4 (for the "non >" reason) then nothing hard (for me)  changing to b.ex. ">+".l.  If that makes differrence - please inform me.4  Och, no: will change immediately, if *that* may be  a problem - inform me :)    Regards - Gotfryd -- aE =====================================================================nF $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - 		THEN EXCUSE/OBJECT=ME6. $!                        GS@stanpol.zabrze.plE =====================================================================M   ------------------------------  # Date: Mon, 07 May 2001 07:24:06 GMT  From:  <remy@younes.nom.fr>e Subject: Re: SCSSYSTEMID$ Message-ID: <1103_989220040@seattle>   When you take the DecNet address of your computer, SCSSYSTEMID has to be just 1024 * Area_number + node_number. (DECNET IV, don't remember 1Y how to find it with ISO). If you don't care about decnet address, 1025 will be just fine.a  > On Mon, 07 May 2001 05:50:21 GMT, adroso@home.com (ADR) wrote:B > I'm installing V7.2 onto a VS 4000 VLC and I've never done a VMSG > install before (sorry, I'm a newbie).  Anyway, I'm being prompted formG > SCSSYSTEMID.  This isn't part of a cluster or anything, just a system - > I'm using at home.  Can I just put in 1025?. > .    ------------------------------  # Date: Mon, 07 May 2001 09:01:36 GMTe1 From: CSABA  HARANGOZO   <csabah@zipworld.com.au>n8 Subject: Re: The Internet, Tru64 and other unix variants9 Message-ID: <QvtJ6.1712$CN.321365@nostril.pacific.net.au>   * Christof Brass <brass@infopuls.com> wrote: > Dirk Munk wrote:   > [SNIP]   > Brillant. @ > And not to mix UNIX features into VMS because this would offerA > the pure VMS apps to step by step be re-written to be more UNIXy8 > like and to end up on UNIX finally. Moreover will this> > UNIXication of VMS introduce subtle and heavy problems which  > will raise the platform costs.7 > Branding is the art to remain sufficiently different.n > Nobody needs another UNIX.  E 	Unfortunately, the "bastardisation" of VMS continues unabated... :-(.? 	See:   http://www.openvms.compaq.com/solutions/government/coe/r  > 	Here you can read ( among others ) the DII COE Faq, and weep.C 	If the stupid DoD wants Unix, there is Tru64, no need to ruin VMS.uD 	But of course, one can not expect common sense from these places...   						Csaba			  I    ----------------------------------------------------------------------eE    * Csaba I. Harangozo     |    'To err is human', said the hedgehog E    * csabah@zipworld.com.au |           as he dismounted a wirebrush.sI    ----------------------------------------------------------------------n;    EARTH::AUSTRALIA:[SYDNEY]HARANGOZO.CSABA;1, delete? [N]:-   ------------------------------  * Date: Mon, 7 May 2001 10:49:27 +0000 (UTC)' From: david20@alpha1.mdx.ac.uk (D.Webb)A8 Subject: Re: The Internet, Tru64 and other unix variants+ Message-ID: <9d5ujn$fv0$1@aquila.mdx.ac.uk>e  m In article <QvtJ6.1712$CN.321365@nostril.pacific.net.au>, CSABA  HARANGOZO   <csabah@zipworld.com.au> writes:h+ >Christof Brass <brass@infopuls.com> wrote:u >> Dirk Munk wrote:j >t	 >> [SNIP]r >  >> Brillant.A >> And not to mix UNIX features into VMS because this would offer B >> the pure VMS apps to step by step be re-written to be more UNIX9 >> like and to end up on UNIX finally. Moreover will thism? >> UNIXication of VMS introduce subtle and heavy problems whichY! >> will raise the platform costs.t8 >> Branding is the art to remain sufficiently different. >> Nobody needs another UNIX.s >CF >	Unfortunately, the "bastardisation" of VMS continues unabated... :-(@ >	See:   http://www.openvms.compaq.com/solutions/government/coe/ >e? >	Here you can read ( among others ) the DII COE Faq, and weep.nD >	If the stupid DoD wants Unix, there is Tru64, no need to ruin VMS.E >	But of course, one can not expect common sense from these places...t >f >						Csaba			  >u   Sorry have to disagree. K So long as it doesn't interfere with VMS's strengths ie Security, Stability.G and clustering then anything which increases the number of applications-L (either by easing the porting efforts of Volunteers or persuading commercialB companies that a VMS port is not too difficult) is to be welcomed.  L All operating systems pinch from each other. VMS has pinched from Unix, UnixN has pinched from VMS. (Hell the Core of NT was allegedly pinched almost whole 
 from VMS).L This is normal. It's happened ever since VMS was concieved (and before since5 VMS was designed based on earlier operating systems).dC I want a growing evolving VMS not a dead preserved museum specimen.t  
 David Webb VMS and Unix team leader CCSS Middlesex University     PS.i  O If Tru64 really were in trouble then far from being a reason to celebrate it isnO bad news for VMS. Tru64 sells Alpha chips. Those using Tru64 would be forced toaN move to other vendor's Unix systems (Since their applications won't run on VMSN !!). Sun would probably be the big winner. Linux would take some (and a few of4 them - probably a very few would be Linux on Alpha).K The death of Tru64 would almost certainly mean that Compaq would reconsidervI whether it should continue to invest in developing new versions of Alpha.r   ------------------------------    Date: 07 May 2001 19:31:10 +0800, From: Paul Repacholi <prep@prep.synonet.com>8 Subject: Re: The Internet, Tru64 and other unix variants- Message-ID: <87pudlz98h.fsf@prep.synonet.com>s    Dirk Munk <munk@home.nl> writes:  7 > I found this quote on http://www.netcraft.com/survey/t   ...   C > Since there is no free variant of VMS, this part of the market iseD > quite save as long as Compaq can convince existing customers no toA > change to Unix/Linux, and get new customers of course. The onlyd= > thing they have to for this is to make VMS so good, rich in:; > features, scalable and cheap in running costs that a wells> > calculating customer will opt for VMS instead of Unix/Linux.  F If I had to run a unix system, DU/T64 would be the first pick. But theD cost difference to Linux is real hard to swallow, and harder for theE PHB who has not a clue about the value of errorloging, design, etc...h  E The people who DO care about costs like VMS; the idiots who can't seebE past day 0 don't. The sad flip side, is that there are a large numberr- who have a hard upper limit on day 0 price...    -- r< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.k@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov r   ------------------------------   Date: 7 May 2001 12:08:47 -0500e9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)o8 Subject: Re: The Internet, Tru64 and other unix variants3 Message-ID: <8H+XlOaT$8Hb@eisner.encompasserve.org>   m In article <QvtJ6.1712$CN.321365@nostril.pacific.net.au>, CSABA  HARANGOZO   <csabah@zipworld.com.au> writes:e, > Christof Brass <brass@infopuls.com> wrote: >> Dirk Munk wrote:r > 	 >> [SNIP]a >  >> Brillant.A >> And not to mix UNIX features into VMS because this would offermB >> the pure VMS apps to step by step be re-written to be more UNIX9 >> like and to end up on UNIX finally. Moreover will this ? >> UNIXication of VMS introduce subtle and heavy problems which3! >> will raise the platform costs.E8 >> Branding is the art to remain sufficiently different. >> Nobody needs another UNIX.d > G > 	Unfortunately, the "bastardisation" of VMS continues unabated... :-("A > 	See:   http://www.openvms.compaq.com/solutions/government/coe/  > @ > 	Here you can read ( among others ) the DII COE Faq, and weep.E > 	If the stupid DoD wants Unix, there is Tru64, no need to ruin VMS.e  F There is also Solaris, which the DII COE favors.  But Tru64 _has_ beenK certified as compliant with (a prior version of) DII COE.  My understandingtL is that the folks who are governed by the DII COE rules were not interested.K They want VMS, but they are under orders to use DII-COE-compliant operating= systems.  E Thus Compaq (DEC?) tried all they could do with Tru64, but it did not  meet the need (to run VMS).B   ------------------------------  % Date: Mon, 07 May 2001 12:20:36 -0400n- From: JF Mezei <jfmezei.spamnot@videotron.ca>o8 Subject: Re: The Internet, Tru64 and other unix variants, Message-ID: <3AF6CB4A.3BC5B0F9@videotron.ca>   "D.Webb" wrote:0M > The death of Tru64 would almost certainly mean that Compaq would reconsider4K > whether it should continue to invest in developing new versions of Alpha.   H Don't forget the efforts to port Tandem's NSK/Gardian to Alpha. And as I$ recall, Linuc runs on alpha as well.  M What I find interesting is the timing aspect of this versus the fact that thelM most recent game of musical chairs at Compaq has Marcello heading both True64o and VMS.   ------------------------------  % Date: Mon, 07 May 2001 12:21:31 -0400X9 From: Matthew Doremus <Matthew.Doremus@Compaq.Com.NoSpam>s" Subject: Re: VAX vs AXP executable1 Message-ID: <3AF6CB8B.4DBAA522@Compaq.Com.NoSpam>a  J If you are running OpenVMS V7.1 or greater, the simplest and most accurateN method would be to use "Analyze/Image/Select=Architecture *.exe".  The /SelectM qualifier is documented in OpenVMS V7.3, but has latent support back to V7.1.n   Ed Wilts wrote:A  M > I'm about to retire the last of my Vaxes (he says with fond memories).   Is0M > there a relatively fast and easy way for me to identify a VAX executable aslM > opposed to an AXP exe?  I'm looking to write a script that will archive allo > the old VAX exes.r ><	 > Thanks,c >         .../Ed > --  > Ed Wilts, Mounds View, MN, USA > mailto:ewilts@mediaone.net   ------------------------------  % Date: Mon, 07 May 2001 13:23:47 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>l" Subject: Re: VAX vs AXP executable, Message-ID: <3AF6DA15.2709B602@videotron.ca>   Matthew Doremus wrote: > L > If you are running OpenVMS V7.1 or greater, the simplest and most accurateP > method would be to use "Analyze/Image/Select=Architecture *.exe".  The /SelectO > qualifier is documented in OpenVMS V7.3, but has latent support back to V7.1.e   WOW ! Neat trick !!!!    ------------------------------  % Date: Mon, 07 May 2001 14:29:09 +0200 2 From: "Dr. Otto Titze" <titze@ikp.tu-darmstadt.de> Subject: VxWorks3 Message-ID: <3AF69515.8C360A40@ikp.tu-darmstadt.de>d   Hi,c  : this is probably somewhat off topic but the people on this list know so much...  = Is someone out there who still uses VxWorks on AXPvme alphas?M   Regards1 Otto   ,  -------------------------------------------, | Dr. Otto Titze, Kernphysik TUD           |, | Schlossgartenstr. 9, D-64289 Darmstadt   |, | titze@ikp.tu-darmstadt.de                |, | Tel: +49(6151)16-2916,FAX:16-4321        |,  -------------------------------------------   ------------------------------  # Date: Mon, 07 May 2001 13:25:46 GMTs$ From: Scott Vieth <svieth@wi.rr.com>2 Subject: What is the best way to erase SCSI disks?) Message-ID: <3AF6A2CF.53723772@wi.rr.com>r   Hi:r  E We've got an AlphaServer 4100 running OpenVMS 7.2-1 that is connected7E to two SW800s full of HSJ50s which host two, four, and nine GB disks.   H Our migration from CI to fibre channel will soon be complete.  I want to
 thoroughlyF erase the disks in the SW800s before I send them to the used equipment market.r  C What is the most effective way to erase every single block on thoseu drives?   G Could I use DILX and let it run for a very long time?  Would that covert ever sector?  F What about creating a file that has an allocation as big as the number of free blocks) on the drive and then using DELETE/ERASE?p  = Is there a utility somewhere that was designed for this task?   H I don't need super-duper-NSA-level erase.  Just one pass over every byte to make sure4 that there isn't any data that's easily recoverable.   Thanks much,  
 -Scott :^)   ------------------------------  % Date: Mon, 07 May 2001 09:57:55 -0400p# From: Jim Agnew <Agnew@hsc.vcu.edu>e6 Subject: Re: What is the best way to erase SCSI disks?+ Message-ID: <3AF6A9E3.FD5544EC@hsc.vcu.edu>s  P What I'd do is to set the volume erase on delete, and turn highwater marking on.  [ then, fill it up with trash files, and then delete 'em...  takes a while, but works for me.c  @ alternatively, stick it into a pc, and format it and so forth...  & the first option can be automated...     j.   Scott Vieth wrote: >  > Hi:- > G > We've got an AlphaServer 4100 running OpenVMS 7.2-1 that is connectedlG > to two SW800s full of HSJ50s which host two, four, and nine GB disks.B > J > Our migration from CI to fibre channel will soon be complete.  I want to > thoroughlyH > erase the disks in the SW800s before I send them to the used equipment	 > market.  > E > What is the most effective way to erase every single block on those 	 > drives?  > I > Could I use DILX and let it run for a very long time?  Would that cover  > ever sector? > H > What about creating a file that has an allocation as big as the number > of free blocks+ > on the drive and then using DELETE/ERASE?s > ? > Is there a utility somewhere that was designed for this task?y > J > I don't need super-duper-NSA-level erase.  Just one pass over every byte > to make sure6 > that there isn't any data that's easily recoverable. >  > Thanks much, >  > -Scott :^)   ------------------------------  % Date: Mon, 07 May 2001 16:24:36 +0200s$ From: Michael Unger <unger@decus.de>2 Subject: What is the best way to erase SCSI disks?+ Message-ID: <009FBA9A.ABBD5597.13@decus.de>   $ > Date: Mon, 7 May 2001 13:25:46 GMT& > From: Scott Vieth <svieth@WI.RR.COM>4 > Subject: What is the best way to erase SCSI disks? >      [...]a  E > What is the most effective way to erase every single block on those 	 > drives?  >   I > Could I use DILX and let it run for a very long time?  Would that coverl > ever sector? >   H > What about creating a file that has an allocation as big as the number > of free blocks+ > on the drive and then using DELETE/ERASE?+ >   ? > Is there a utility somewhere that was designed for this task?u   What about INIT /ERASE ?   Michaele   ------------------------------   Date: 7 May 2001 14:50:59 GMTo2 From: mathog@seqaxp.bio.caltech.edu (David Mathog)6 Subject: Re: What is the best way to erase SCSI disks?, Message-ID: <9d6coj$7es@gap.cco.caltech.edu>  R In article <009FBA9A.ABBD5597.13@decus.de>, Michael Unger <unger@decus.de> writes: >>   aI >> What about creating a file that has an allocation as big as the numberM >> of free blocks2, >> on the drive and then using DELETE/ERASE?  L Try the program after my signature.  It works on a variety of OS's.  But be K sure you have no diskquota or it will only zero up that limit.  It removes oK the file it writes when it's done, so that you should end up with an empty S. disk, other than whatever indices the OS uses.   David Mathog mathog@caltech.edu? Manager, sequence analysis facility, biology division, Caltech rJ ************************************************************************** /*
    zerofill.ct6    19-AUG-1999, David Mathog, Biology Division Caltech  C    This program fills all available space in a disk unit (partition"C    or disk, depending on the OS) with a single file full of zeroes. @    The purpose of this is to clean the disk of any residual dataB    remaining when files have been deleted but not erased. The mainA    reason I run this is to allow disk copying programs that don'tpF    understand the native file format to do a better job of compressing?    the disk image.  (Examples: Ghost, ImageCast, DiskCopy.)  DooF    not rely on this program for security purposes - sophisticated diskF    recovery techniques might still be able to recover data from a disk$    entirely zeroed by this program.   =    This program is freeware.  No guarantees, warranties, etc.e    Use it at your own risk.n   */   #include <stdlib.h>e #include <stdio.h>   void main(void){
 FILE * fd; char block[512]; int i;
 size_t wrote;   &   /* make a block of 512 zero bytes */     for(i=0;i<512;i++){a     block[i]='\0';   }m  C   /* open a binary file named ZERO.DAT to fill with these blocks */   :   (void) printf("Zerofill: creating the file ZERO.DAT\n");   fd = fopen("ZERO.DAT","wb");  <   if(fd != NULL){   /* open was successful, fill the file */S     (void) printf("Zerofill: filling the file ZERO.DAT (this may take a while)\n");r     wrote=1;      for(i=0; wrote == 1; i++  ){1        wrote = fwrite(&block[0],512,1,fd);       G     }EF     (void) printf("Zerofill: wrote %d 512 byte blocks into file\n",i);     (void) fclose(fd);      if(0 != remove("ZERO.DAT")){T       (void) printf("Zerofill: error while removing ZERO.DAT, delete it by hand\n");	     }     
     else {4       (void) printf("Zerofill: ZERO.DAT deleted\n");	     }    R   }S   else {Q     (void) printf("Zerofill: fatal error, could not create the file ZERO.DAT\n");m   },1   (void) printf("Zerofill: program completed\n");d }u   ------------------------------  % Date: Mon, 07 May 2001 17:56:49 +0100c  From: Paul Sture <paul@sture.ch>6 Subject: Re: What is the best way to erase SCSI disks?+ Message-ID: <VA.00000385.20d9dda0@sture.ch>V  < In article <3AF6A2CF.53723772@wi.rr.com>, Scott Vieth wrote:& > From: Scott Vieth <svieth@wi.rr.com> > Newsgroups: comp.os.vmsS4 > Subject: What is the best way to erase SCSI disks?% > Date: Mon, 07 May 2001 13:25:46 GMT  >  > Hi:  > G > We've got an AlphaServer 4100 running OpenVMS 7.2-1 that is connected1G > to two SW800s full of HSJ50s which host two, four, and nine GB disks.: > J > Our migration from CI to fibre channel will soon be complete.  I want to > thoroughlyH > erase the disks in the SW800s before I send them to the used equipment	 > market.I > E > What is the most effective way to erase every single block on thoseu	 > drives?  > I > Could I use DILX and let it run for a very long time?  Would that cover  > ever sector? > H > What about creating a file that has an allocation as big as the number > of free blocks+ > on the drive and then using DELETE/ERASE?h > ? > Is there a utility somewhere that was designed for this task?. > J > I don't need super-duper-NSA-level erase.  Just one pass over every byte > to make sure6 > that there isn't any data that's easily recoverable. > K Since they are on HSJ50s, consider erasing the meta data too. I don't have U; the HSJ manuals to hand, but the HSZs support INIT DESTROY.n   ___o
 Paul Sture Switzerlandm   ------------------------------  $ Date: Mon, 7 May 2001 12:39:25 -0400; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>z Subject: Re: Xserver NodeNamea$ Message-ID: <3af6cfc1$1@news.si.com>  = >How can I determine the nodename of the Xserver during login-E >Running VMS 6.2 on VAX 7000.  Xclients include VAXstation 4000, unix: >machines, and NT computers.  I Since the servers themselves know their own IP address, why not have them0K send it as a parameter to a command procedure on the client system?  That's:B what we do.  The procedure then uses SET DISPLAY/CREATE/NODE='ip',- where "ip" is the IP address the server sent.2 --A Brian Tillman                   Internet: tillman_brian at si.com.A Smiths Aerospace                          tillman at swdev.si.comD= 3290 Patterson Ave. SE, MS      Addresses modified to preventt< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  % Date: Mon, 07 May 2001 10:45:43 -0400i0 From: paul.r.anderson@compaq.com (Paul Anderson)6 Subject: Re: [DCPS] Duplex Problem with HP Laserjet 5MP Message-ID: <paul.r.anderson-0705011045430001@dhcp-16-21-34-107.eng.lkg.dec.com>  @ In article <3af56ea3@news.kapsch.co.at>, eplan@kapsch.net wrote:  = > I'll try to test this with another LJ 5M (if I find one)...    Yes, please do.r  H > It currently looks like DCPS forces single side printing in all cases.  I I assume there are no errors displayed anywhere when your DCPS duplex jobcF comes out simplex and that the job prints properly other than it's not duplex.i  D Especially if you can't find another 5M printer, it might be wise toJ collect a DCPS diag file to see what's being sent to the printer.  (DEFINE9 /SYSTEM /EXEC DCPS$TEST TRUE, restart the queue and PRINTnI /PARAM=(DIAG=FILE=BOTH,SIDES=2).  You'll get a "TO" and a "FROM" log fileu( which you can look at and/or send to me.   Paul   -- m
 Paul AndersonS  OpenVMS Engineering  Compaq Computer Corporation   ------------------------------   End of INFO-VAX 2001.255 ************************