HDTenEightyP/NetNews huggingface dataset:
From: nobody@PA.DEC.COM ("ftpmail service on inet-gw-2.pa.dec.com")
Newsgroups: comp.os.vms
Subject: results of ftpmail request 725708498.12240 [UUENCODE and UUDECODE to Info-VAX]
Date: 4 Jan 93 07:15:38 GMT
Reply-To: <nobody@inet-gw-2.pa.dec.com>
Distribution: world
Organization: The Internet

Orig message-id: <9212300153.AA08388@inet-gw-1.pa.dec.com>
Orig subject: UUENCODE and UUDECODE to Info-VAX
Orig from: "Jurassic Park Control Center" <FZC@CU.NIH.GOV>
Orig date: Tue, 29 Dec 1992 20:52:14 EST

--- connecting to wsmr-simtel20.army.mil...
Connecting to wsmr-simtel20.army.mil
220 WSMR-SIMTEL20.ARMY.MIL FTP Server Process 5Z(111)-7 at Mon 4-Jan-93 00:15-MST
--- logging in as user=anonymous password=ftpmail/FZC@CU.NIH.GOV...
---> USER anonymous
331 ANONYMOUS user ok, send real ident as password.
---> PASS <somestring>
230-Turn off this status message (not recommended) next time by using a hyphen
230-(-) as the first character of your password.
230-
230-WSMR-SIMTEL20.ARMY.MIL is owned and operated by the U.S. Army White Sands
230-Missile Range, New Mexico.  SIMTEL20 is usually always up, except for PM
230-on the first Wednesday of each month, 4pm and 8pm Mountain Time (GMT-7).
230-Send problem reports to ACTION@WSMR-SIMTEL20.ARMY.MIL.
230-
230-Only nine ANONYMOUS FTP logins are allowed during weekday prime time, 5am
230-to 3pm Mountain Time, but 27 all other times.  Try restricting your
230-connection attempts to those "other times" for best results.
230-
230-New ANONYMOUS users: please "get 00-readme.txt" and read it.
230-
230-SIMTEL20 files are also available by anonymous ftp from mirror sites
230-OAK.Oakland.Edu (141.210.10.117), wuarchive.wustl.edu (128.252.135.4),
230-ftp.uu.net (137.39.1.9), nic.funet.fi (128.214.6.100), src.doc.ic.ac.uk
230-(146.169.3.7), nic.switch.ch (130.59.1.40), archie.au (139.130.4.6), or
230-nctuccca.edu.tw (140.111.3.21).
230-
230- The system will go down 6-Jan-93 16:00:00 until 20:00:00
230 User ANONYMOUS logged in at Mon 4-Jan-93 00:15-MST, job 30. 
---> TYPE A
200 Type A ok.
--- getting file (pd1:<misc.vaxvms>uudecode.c as /tmp/ftpmail9738.file.0)...
---> PORT 16,1,0,23,8,149
200 Port 8.149 at host 16.1.0.23 accepted.
---> RETR pd1:<misc.vaxvms>uudecode.c
550 File not accessible. No such directory name
Failure on RETR command
!!! get failed
--- getting file (pd1:<misc.vaxvms>uuencode.c as /tmp/ftpmail9738.file.1)...
---> PORT 16,1,0,23,8,150
200 Port 8.150 at host 16.1.0.23 accepted.
---> RETR pd1:<misc.vaxvms>uuencode.c
550 File not accessible. No such directory name
Failure on RETR command
!!! get failed
--- getting file (pd1:<misc.vaxvms>uudecode.vms as /tmp/ftpmail9738.file.2)...
---> PORT 16,1,0,23,8,151
200 Port 8.151 at host 16.1.0.23 accepted.
---> RETR pd1:<misc.vaxvms>uudecode.vms
550 File not accessible. No such directory name
Failure on RETR command
!!! get failed
--- getting file (pd1:<misc.vaxvms>uudecode2.vms as /tmp/ftpmail9738.file.3)...
---> PORT 16,1,0,23,8,152
200 Port 8.152 at host 16.1.0.23 accepted.
---> RETR pd1:<misc.vaxvms>uudecode2.vms
550 File not accessible. No such directory name
Failure on RETR command
!!! get failed
---> (end of ftpmail session)
From: steve@dbaccess.com (Steve Suttles)
Newsgroups: comp.os.vms
Subject: Re: Using C to read Fortran Files
Date: 8 Jan 93 22:33:28 GMT
Organization: Cross Access Corp., Santa Clara, CA
X-Newsreader: Tin 1.1 PL4

Ok.  Everybody's seen the code, everybody's identified the root cause.
The solution should be, open the file in binary mode.
 (the second argument to fopen should be "rb").

According to the rules, the program is currently doing what it should.

sas
-- 
Steve Suttles                Internet:  steve@dbaccess.com      Dr. DCL is IN!
CROSS ACCESS Corporation     UUCP: {uunet,sgiblab}!troi!steve  Yo speako TECO!
2900 Gordon Ave, Suite 100   fax: (408) 735-0328              Talk data to me!
Santa Clara, CA 95051-0718   vox: (408) 735-7545   HA! It's under 4 lines NOW!
Newsgroups: comp.os.vms
From: kupfer@htlulx.htl-bw.ch (Kupferschmid Christian)
Subject: Timed for VAX-VMS??
Keywords: timedeamon
Organization: HTL Brugg-Windisch, Switzerland
Date: Thu, 7 Jan 1993 12:30:48 GMT


Hi everybody

Can everone tell me wether there is an time deamon for VAX-VMS V5.5 that corresponds to the ULTRIX timed.
I'm interrested to synchronize my VAXes to the network time.

If it exists where can i get it?

Thanks for any info.

Chris

-- 
School of Engineering, Switzerland
Information Center

HTL Brugg-Windisch               |RFC-822:        kupfer@htl-bw.ch
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Question about RMS and MSCP-pair
Date: 9 Jan 1993 11:59:58 GMT
Organization: HST Wide Field/Planetary Camera
Distribution: world
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <61050104@acf3.NYU.EDU>, tihor@acf3.NYU.EDU (Stephen Tihor) writes:
>(a) that is not my impression but perhaps I misunderstood Ken bates
>when we were talking about it.  (b) So, there is in fact no tool
>available to proerply (and in a recomendable or at least guarenteed
>safe manner) stress test a disk.

Sure, there's a guaranteed safe way to do it:
	1)  Take an image backup of the disk;
	2)  Use the FINDBAD program I just posted to exercise the disk;
	3)  If FINDBAD reports errors, restore the disk from the BACKUP
	    saveset;  if FINDBAD reports no errors, the disk can simply be
	    remounted, as FINDBAD leaves it in its original state in that case.

>I proposed one that would.  If BAD
>worked on DSA disks or if ANAL had a /REWRITE check mode that rewrote
>every file on disk those might be sufficient.

FINDBAD does both.  Well, it doesn't rewrite files;  instead, it rewrites
blocks with the original information.  I've never been able to figure out why
BAD doesn't do this, nor why there's no qualifier for ANAL/MEDIA to tell it
to simply deal with the logical disk, thus circumventing the problems with DSA
devices (Digital, are you listening?).
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
From: moeller@gwdgv1.dnet.gwdg.de ("GWDGV1::MOELLER")
Newsgroups: comp.os.vms
Subject: RE: 'ASSUME' macro in VAXC?
Date: 11 Jan 93 17:41:59 GMT
Distribution: world
Organization: The Internet

Kenn Humborg <elehumborg@orbsen.ucg.ie> asks:
> Does anybody know any way of implementing compile-time checking in VAXC
> similar to the ASSUME macro defined in LIB.MLB (or is it STARLET?)?
>
> What I want to check for specifically is that the size of a certain struct
> is equal to 512 bytes and if not, print a warning message.
>
> Say:
> check sizeof(struct foo) "Error: foo is the wrong size"
>
> I don't really mind how kludgy the solution would have to be, as long as
> it works.

No way to have the compiler issue (only) an error message of your choice,
but how about this:

| #define assume(condition) { int assumption_failed[(condition) ? 1 : 0]; }
|
| /* example */
| main()
| {
|	struct x { int a; } xx;
|
|	assume(sizeof(xx) == 512)
| }

| $ cc <...>
| 		assume(sizeof(xx) == 512)
| %CC-E-INVARRAYBOUND, The declaration of "assumption_failed" specifies
|		a missing or invalid array bound.
|		At line number 8 in <...>
|...
| %CC-I-NOBJECT, No object file produced.
|...

NB. For the macro to operate correctly when the condition is satisfied,
it must be invoked *within* a function.

Wolfgang J. Moeller, GWDG, D-3400 Goettingen, F.R.Germany | Disclaimer ...
PSI%(0262)45050352008::MOELLER      Phone: +49 551 201516 | No claim intended!
Internet: moeller@gwdgv1.dnet.gwdg.de   | This space intentionally left blank.

Newsgroups: comp.os.vms
From: bob@harrier.demon.co.uk (Bob day)
Subject: Re: Does anybody know about Excelan interfaces? 
Distribution: world
Organization: Harrier Softnet Ltd
Reply-To: bob@harrier.demon.co.uk
X-Mailer: Simple NEWS 1.90 (ka9q DIS 1.19)
Date: Thu, 7 Jan 1993 15:53:32 +0000

>Hello,
>recently, I acquired a used VAXstation II/GPX. This machine contained an
>interface EXCELAN EXOS 203. I could not find any information about this
>type of board. It is posslibly an ethernet controller, but the chips on
>the card are not specific to determine the function.
>

Ding give that man a prize. It is indeed an ethernet interface. But it is
an intelligent card. Excelan's tcpip kernel runs on the card, not in the VAX.
I beleive Microdyne in the US now have the rights to it

cheers

bob
-- 

Harrier Softnet Ltd    tel +44-734-731181              I'd rather be playing
Ivanhoe Rd             fax +44-734-734546              with my chopper
Finchampstead          email bob@harrier.demon.co.uk     O  / __________
Berkshire                                               -|-<>     /\======O
RG11 4QQ                                               _/ \_    __\/__
From: t_wade@vms.eurokom.ie
Newsgroups: comp.os.vms
Subject: Re: The VAX Vacuum
Date: 5 Jan 93 20:36:37 GMT
Organization: EuroKom Conferencing Service

In article <9301040153.AA20250@ucbvax.Berkeley.EDU>, FZC@CU.NIH.GOV ("Paul Robinson, Contractor") writes:
> The issue of the VAX vacuum vs. VAX computers and the
> trademark isn't significant except to the extent Digital
> might have wanted to sell their computer in the same
> countries as that other company had been selling vacuums.
> 
> Until last year, in the U.S. a trademark/servicemark is owned
> ONLY by the first party to USE it in a particular country.  This
> meant that legally, if DEC had used VAX in the U.S. before that
> other company used the term for its vacuum cleaners in the U.S.,
> it could prevent that company from selling vacuums under that
> name in the U.S.

Can't the same name be used for totally different things ?  For example,
if you brought out a new computer and called it a MAC, you would probably
have Apple after you.  If, however, your new product was a hamburger, you
might get a call from McDonalds.

True story:  The makers of the VAX vacuum cleaner brought out a new smaller
model a couple of years ago.  They decided to call it ......
the MiniVAX  (a major marketing opportunity lost there :-( )
------------------------------------------------------------------------------
Tom Wade        | Internet: T.Wade@vms.eurokom.ie  (all domain mailers).
Network Manager | DEC Enet: DECWRL::"t.wade@vms.eurokom.ie"  (VMS Mail)
EuroKom         | PSI-Mail: PSI%272431001992::_T_WADE
UCD Belfield    | JANET:    t.wade%ie.eurokom.vms@UK.AC.EARN-RELAY
Dublin 4        | X400:     g=tom;s=wade;o=eurokom;p=eurokom;a=eirmail400;c=ie
Ireland         | Telex:       (0500) 91178 UCD EI  ("TO: WADE" at start)
-------------------+----------------------------------------------------------
Tel: +353-1-2830555|  Official Disclaimer:  "This is not a disclaimer"
Fax: +353-1-2838605|          Unix  ....  Just say No !
From: guy@wmsg02.wm.estec.esa.nl (Guy Brooker)
Subject: RMS RAB & FAB for VAXC file
Organization: ESA/Estec/WMS, Noordwijk, The Netherlands
Date: Mon, 4 Jan 1993 12:18:04 GMT

Coming back from my Christmas I have read a long discussion about VAX C
buffer flushing. Many people say that it is easy to get the RAB/FABs from
a VAX C FILE *

OK so how do you do it ???

(Call me 'butthead' if you like)

Guy
-- 

-------------------------------------        	Guy Brooker
Internet: guy@wm.estec.esa.nl        		European Space Research and
	  guy@wmsg02.dnet.estec.esa.nl		Technology Centre (ESTEC)
	  gbrooker@estec.esa.nl
Bitnet  : gbrooker@estec.bitnet		SPAN    : ESTERS::GUY
Phone	: +31-1719-83611		Fax	: +31-1719-85617
Mail	: ESTEC JW/WMS, Keplerlaan 1, 2200AG NOORDWIJK, The Netherlands
From: vader@diku.dk (Christoph Walter Ressel Larsen)
Newsgroups: comp.os.vms
Subject: RMU/BACKUP (tape mounting).
Summary: Why must one confirm RMU tape mounts ?
Keywords: RMU, RMU/BACKUP
Date: 5 Jan 93 19:45:48 GMT
Organization: Department of Computer Science, U of Copenhagen

I have an annoying problem. We are running VMS5.2 and RDB 3.1B.
When making backup of an RDB database directly to tape you have to verify
the mount of every tape, i find that annoying and was wondering if there was
a way to get around the problem smoothly. VMS BACKUP mounts it's tapes by it-
self and why shouldnt RMU/BACKUP not be able to that too.

Reg. Chris.
-- 
      Chris W. R. Larsen       |             We learn from history that 
      vader@freja.diku.dk      |             we do not learn from history.
   University of Copenhagen    |
Department of computer science |
From: DWING@UH01.Colorado.EDU (Dan Wing)
Newsgroups: comp.os.vms
Subject: Re: Starting remote process over Decnet?
Date: 6 Jan 93 00:23:38 GMT
Distribution: world
Organization: The Internet

Bruce Rosen, brosen@bbn.com, writes:

>Is there some system service that supports starting a process on a different,
>but DECnet connected, VMS machine?  It would be something like a LIB$SPAWN,
>but would take hostname, userid, and password, as necessary arguments.
>
>What I'm looking for is a DECnet equivalent of the TCP/IP "rexec" system call.

The TASK object can do this for you; however, many system managers disable
the TASK object.  You could also setup DECnet objects between the nodes which
would give you the desired effect (see HELP SET OBJECT in NCP).

-Dan Wing, dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet (DGW11)
 Systems Administrator, University Hospital, Denver
From: ecf_stbo@jhuvms.hcf.jhu.edu (UNIX of course, now what was the question?)
Newsgroups: comp.os.vms
Subject: Re: SYSDUMP.DMP File Question...
Date: 8 Jan 1993 09:14 EST
Organization: The Johns Hopkins University - HCF
Distribution: world
NNTP-Posting-Host: jhuvms.hcf.jhu.edu
News-Software: VAX/VMS VNEWS 1.41    

In article <9301080512.AA12581@uu3.psi.com>, leichter@lrw.com (Jerry Leichter) writes...
>Note, BTW, that because the dump is ALWAYS taken, and it is the value of
>SAVEDUMP defined at the NEXT boot that matters, you can run with SAVEDUMP=0,

Just to be complete, a dump is not taken if DUMPBUG is not set, or in later
versions of VMS, if it was an operator requested shutdown.


Tom O'Toole - ecf_stbo@jhuvms.hcf.jhu.edu - JHUVMS system programmer 
Homewood Computing Facilities, Johns Hopkins University, Balto. Md. 21218 
>Here comes a jet ski.
>weuh weeuhh weeuhh weeuhh WEEUHH WEEUHH WEEUHH WEEUHH weeuhh weeuhh weeuhh weuh
From: mr2461@shamu.ca.boeing.com
Newsgroups: comp.os.vms
Subject: How to get accurate memory error count
Date: 5 Jan 93 15:27:50 -0800
Organization: Central Storage Facility




    I'm developing a suite of routines to monitor various VAXes, and notify
    appropriate people when an "important event" has occurred. One of the
    categories of events that I'm watching for is hardware errors. I use the
    $GETDVI system service to retrieve the number of errors most devices
    have accumulated, and (ugh!) parse the output of the $SHOW ERROR command
    to see if there are any memory or CPU errors. Recently, on a 7610 we
    just installed, we noticed that we were generating massive numbers of
    memory errors that were not showing up via the $SHOW ERROR command, but
    were being logged in the error log. I know that VAXsim+ can report errors
    of this type (although we have been told by DEC not to run that product
    on a 7610), so I assume this information is detectable from software.
    Unfortunately, I don't have source for VAXsim+ available to look up
    its methods.

    Three questions:

    1. Why do some errors get logged to the error log, but not increment
       the count in the $SHOW ERROR command?

    2. Does this behavior apply to devices other than memory, and thus
       render my calls to $GETDVI for the ERRCNT inaccurate?

    3. How (without parsing the error log file!) can I get the true
       number of errors for a device, particularly memory and CPU
       boards?

    Thanks, in advance, for any help you can provide. If there is
    enough interest, I'll post a summary.


    						- Matt Robertson
    						mr2461@shamu.ca.boeing.com
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Courtesy and Civility
Date: 4 Jan 1993 08:18:00 GMT
Organization: HST Wide Field/Planetary Camera
Distribution: world
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <1993Jan1.114605.303@rlgsc.com>, gezelter@rlgsc.com writes:
>In both cases, the "flames" have involved a variety of rude, and,
>in some cases, obscene, electronic speech.
> 
>In dealing with either group of participants, there is no need or
>justification for the use of insults and obscenities by any 
>respondent, whether this is their first "response" to a query, or 
>the 100th response on this particular day.

May I ask a question, please?  When a novice or a non-English speaker proves
himself incapable or unwilling to listen to (or to understand) polite
responses, WHAT THE FUCK DO YOU EXPECT US TO DO?  Yes, we *COULD* try to
protect his oversensitive ego by giving the same polite responses again and
again, but WHY DO YOU THINK THAT WOULD DO ANY FUCKING GOOD?

Please note that the language used in this post was very carefully chosen.

>In any event, international forums require sensitivity to other 
>peoples' languages and cultures. For example, in the US, many people, 
>particularly those in the computing field, are accustomed to informality, 
>particularly the use of first names. In other countries and cultures, 
>such unsolicited informality is considered to be in extremely poor taste.

I see.  This group is no longer to give a goddamn about technical matters, but
it's to be a strictly politically correct forum.  BULLSHIT!

[The rest of what appears to be a sociologists view of the newsgroup deleted]
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
From: longo@sfpp.com (Bob Longo)
Newsgroups: comp.os.vms
Subject: Re: PASSWORDS & SCHEMES
Date: 9 Jan 93 22:27:44 PST
Distribution: world
Organization: Santa Fe Pacific Pipelines

In article <01GT8W0T1GO2006MJF@VAXF.COLORADO.EDU>, DWING@UH01.Colorado.EDU (Dan Wing) writes:
> 
> The V5.4 password checking algorithm does not allow your username to be
> your password, or your username + username:
> 
>   $ SET PASS
>   Old password:
>   New password: DWINGDWING
>   %SYSTEM-F-PWDWEAK, password is too easy to guess; please choose another 
>   string
> 
> Mayhaps someone with source listings could detail all the various permutations 
> that are (currently) dis-allowed.
> 

I looked at the sources and found the following checks in SETPWD (the SET
PASSWORD module):

	o  Length
	o  Syntax
	o  If not a generate password, and user is not DISPWDDIC, and not
	    setting the system password (SET PASSWORD/SYSTEM), then
		1) Make sure that the chosen password is not in the system
		   dictionary.
		2) Disallow any password that contains the username or node
		   name.
		3) Check plaintext password against site-specific policy.
	o  User is asked to enter password again and 2nd is checked to make
	   sure it matches the first.
	o  Password is then hashed and checked against the history file (if
	   appropriate).

> 
> Using the site-specific policy, you can require that special characters such 
> as @, #, $, %, &, etc., be present in the password string.  It also captures
> the plaintext password -- I hope it goes without saying, but DON'T STORE 
> THIS ANYWHERE!

I don't think so.  The code first verifies password syntax and only allows
characters are "A-Z", "0-9", "$" and "_".  This check is done before the
plaintext password policy check is invoked.

-Bob Longo
-- 
==============================================================================
Bob Longo (longo@sfpp.com)
Santa Fe Pacific Pipelines
Los Angeles, CA
From: DAHMS@ifk20.mach.uni-karlsruhe.de (Heribert Dahms)
Newsgroups: comp.os.vms
Subject: Re: TN3270 emulation on a VAX
Date: 12 Jan 1993 12:45:44 GMT
Organization: University of Karlsruhe, FRG (Dept. of Mechanical Engineering)
Distribution: world
NNTP-Posting-Host: ifk28.mach.uni-karlsruhe.de
X-News-Reader: VMS NEWS 1.20

In <1993Jan12.080701.13011@aragorn.unibe.ch> system@ubevx1.unibe.ch writes:

: In article <01GTE8HKP66A004FG7@VAXF.COLORADO.EDU>, DWING@UH01.Colorado.EDU (Dan Wing) writes:
: >Posted for a friend of mine ...
: >
: >A site needs TN3270 emulation to access an IBM system through dumb VTxxx 
[...]
: >Anyone know of such a beast (DEC's SNA-3270 requires too much hardware)?
: Process TCPware and Multinet offer a TN3270 emulation.

Yes, we have UCX and want DEC to have TN3270 built right into it.
We can access our campus IBM3090 via TCP/IP but not DECnet (LAT, CTERM...).
So there's no need for a hardware solution, only TELNET's 3270 software
emulation is missing.

Hey DEC, what's your opinion?


Bye, Heribert (dahms@ifk20.mach.uni-karlsruhe.de)
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: SHOW/UNIBUS (was: What is XPDRIVER for?
Date: 4 Jan 1993 08:02:56 GMT
Organization: HST Wide Field/Planetary Camera
Distribution: world
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <1993Jan4.023201.6158@pony.Ingres.COM>, mikes@Ingres.COM (Mike Schilling) writes:
>From article <1i6e3uINNrct@gap.caltech.edu>, by carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick):
>> In article <1992Dec30.100239.1043@cmkrnl.com>, jeh@cmkrnl.com writes:
>>>> Using this command can crash your system.  
>>>
>>>Calling all readers:  Has ANYONE out there ever seen this actually happen?  
>>>If so, what devices were on the bus?
>> 
>> I've had it happen ONCE.  On a VAXstation-II, running VWS.  Of course, even
>> looking at that system cross-eyed seemed likely to crash it.
>> --------------------------------------------------------------------------------
>Yeah, I could crash a system like that reliably (so to speak) with the BACKUP
>command, if the target was MUA0: (a TK50).  I have seen serial interfaces
>lose characters from SHOW/UNIBUS, but never a crash (hmm, 
>SHOW/UNIBUS/OUTPUT=MUA0 might do it :-) )

Well, wait a minute.  With that first generation of uVAX-IIs, using the TK50
was just *ASKING* for trouble.

By the way, on the system I was describing, doing a SHOW/UNIBUS resulted in the
screen being divided about halfway down, and the bottom was a mirror image of
the top.

On this particular system, the windowing hardware did its own memory
management, and expected VMS to leave the memory it was using alone;  It did
this, of course, via the PHYSICALPAGES SYSGEN parameter.  Installing any of
about 3 other layered products managed to foul up MODPARAMS.DAT so that AUTOGEN
set PHYSICALPAGES wrong.  Truly a dark day for VMS.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.