HDTenEightyP/NetNews huggingface dataset:
From: robbie@winkle.bhpese.oz.au
Newsgroups: vmsnet.internals
Subject: RE: PATCH on ALPHA ?
Date: 7 Sep 92 14:39:15 +1000
Organization: BHP Information Technology, Newcastle

In article <1992Sep4.135207.15155@infocomm.com>, mark@infocomm.com writes:
> These are NOT arguments against the usefulness of PATCH.  I agree with Bruce
> and Hunter that it certainly has an important role as a tool.  I do see 
> that given the priorities of the Alpha VMS migration, PATCH was not a
> development tool and hence not on the critical path for deployment.

This was my point as well. I think that while there is a way around the
lack of a PATCH utility, there is an obvious argument for DEC to
concentrate on porting of other facilities that can't be done without.
This doesn't excuse them from porting it at all.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rob Spencer, BHP Information Technology           |   Sorry, but my .sig
Newcastle, Australia        Voice: +61 49 40 1673 |   is on .sig leave!
Bits: robbie@winkle.bhpese.oz.au                  |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Newsgroups: vmsnet.internals
Subject: RE: PATCH on ALPHA ?
From: mark@infocomm.com
Date: 4 Sep 92 13:52:07 PDT
Organization: INFO COMM - Computer Consulting, Redwood City, Ca

In article <9209021225.AA14429@sndsu1.sinet.slb.com>, brydon@dsny25.sinet.slb.com writes:
> You gotta be kidding!! All of the CSCPAT_nnnn kits (all of them!) are
> VMSINSTAL savesets that Patch an image.  Almost everything that is done in a
> VMS0nn, VMSMUPnnn and VMSUxnnn kit consists of patches.  If DEC is getting
> away from the use of the PATCH utility, then every single itty bitty VMS
> release and subrelease will become huge.  Can this be real?

Come on, this is really only a problem if you get your updates on TU58's!

Since normal distributions come on CDROM and/or TK50's this will not impact the
number of pieces of media.  Since the "speed" of a VMSINSTAL driven
installation is essentially limited by the NUMBER of "updates" or "files"
applied (unless special techniques are used) and NOT the size of these, then 
the time to install these is also not seriously affected.

Actually, I just did a survey of the 12 CSCPATs that I happen to have lying 
around in my DSN$COPY_DIRECTORY and these contained some 33 replacement images
and only 1 use of patch.

I don't have time to dig into the recent VMSUxnnn and VMSMUPnnn kits, but I
seem to recall that the recent ones (after VMS V5.0) were usually replacement
images rather than patching anyway.  In the old days when update media was
smaller there certainly were better reasons to keep the size of the update
down.

These are NOT arguments against the usefulness of PATCH.  I agree with Bruce
and Hunter that it certainly has an important role as a tool.  I do see 
that given the priorities of the Alpha VMS migration, PATCH was not a
development tool and hence not on the critical path for deployment.

--
Mark Pizzolato - INFO COMM Computer Consulting, Redwood City, Ca
PHONE:	(415)369-9366	UUCP:  decwrl!infopiz!mark or uunet!lupine!infopiz!mark
DOMAIN:	mark@infocomm.com
From: munroe@dmc.com (Dick Munroe)
Newsgroups: vmsnet.internals
Subject: Creating LT devices on the fly...
Date: 8 Sep 92 18:40:13 EDT
Organization: Doyle, Munroe Consultants, Inc., Hudson, MA

I'm curious.  How do you get LT devices created on the fly.  Examples would be
appreciated.

Thanks.
-- 
Dick Munroe				Internet: munroe@dmc.com
Doyle Munroe Consultants, Inc.		UUCP: ...uunet!thehulk!munroe
267 Cox St.				Office: (508) 568-1618
Hudson, Ma.				FAX: (508) 562-1133

GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection.
From: <jhawk@panix.com>
Newsgroups: vmsnet.internals
Subject: Problems with DISM32
Date: Sat, 12 Sep 92 11:02:46 EDT
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

Hello,

  I posted this to comp.os.vms, and no one suggested anything,
so I figured I'd try here:

  I just got a copy of DISM32, and I'm having some weird problems --
It spits out a bunch of FORTRAN errors at me when I run it on DCL.EXE
(some other things, too); could these have to do with it needing to be
relinked? I'm running VMS 5.5.  Anyway, here's what it says:

--cut
%PHOTO-I-INIT, Recording initiated at  6-SEP-1992 20:10:09.68

%DISM32-I-NONSTDIMG, non-standard native mode image of type CLI
%DISM32-I-CREOPTFIL, image requires .OPT file; USR$SYSADMIN:[JHAWK.PROG.HACK]DCL
.OPT;2 created
%DISM32-I-SHRIMAGE, image is shareable (created with /SHAREABLE)
%FOR-E-OUTCONERR, output conversion error
  unit 2  file USR$SYSADMIN:[JHAWK.PROG.HACK]DCL.MAR;2
  user PC 0010D491
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           00184E22  00184E22
                                                           00184D1F  00184D1F
                                                           00180E94  00180E94
DISM32$MAIN     DISM32$MAIN                      1604      00001091  0010D491
--cut

And then it repeats the %FOR-E-OUTCONERR and the TRACEBACK 5 more times,
and then proceeds as normal.

Anyway, the reason I'm doing this (in case you missed my prev. post)
was I'm trying to figure out how to patch DCL to use a prompt longer
than 32 chars (which is probably a hopeless task). So, I looked at
Hunter's DCL recall patch. He mentions using DISM32 to disassemble
DCL.EXE. I've done this (assuming the above problem isn't affecting
this) and it fails to recognize the sy1bols in SYS$SYSTEM:DCLDEF.STB
(not surprisingly). In an effort to remedy this, I did a
LINK/NOEXEC/FULL/MAP SYS$SYSTEM:DCLDEF.STB and then converted the
symbols there to DISM32 .SYM format, and gave them a mask of FFFFFFFF,
and called the file DCL.SYM. I then ran DISM32 on DCL.EXE again, and
it still failed to use those symbols. Ideas?

--
John Hawkinson
jhawk@panix.com
Xref: sparky vmsnet.internals:1308 comp.os.vms:14956
From: domiller@ualr.edu
Newsgroups: vmsnet.internals,comp.os.vms
Subject: Help patching MAILSHR
Date: 12 Sep 92 20:52:12 GMT
Organization: University of Arkansas at Little Rock

Okay all you Macro/Patch hackers out there, here's a simple(?) one.

I have been trying to modify the mailshr patch posted Claude Barbe to verify
if a user exists in the local sysuaf, and transparently re-write the address
if not.  I can get the code to work fine in Macro using a call to sys$getuai,
but I can't figure out how to get it into a patch.  Apparently sys$getuai does
not translate to an address that can be used by patch (unlike sys$setprv or
sys$fao which are also used in the patch).

Okay, now the question.  How can I accomplish finding the validity of a user
in a manner that can be used in a patch to mailshr?

Alternatively, is there a user with source listings on CD who would be willing
to let me peruse the MAILSHR sources (if that's legal)?
	Thanks,
	Dale

----------------------------------------------------------------------------
| Dale O. Miller                          | #   #  ###  #     ####         |
| University of Arkansas at Little Rock   | #   # #   # #     #   #        |
| 2801 S. University                      | #   # ##### #     ####         |
| Little Rock, AR  72204-1099  USA        | #   # #   # #     #  #         |
| (501)569-8714                           |  ###  #   # ##### #   #        |
| DOMILLER@UALR.EDU, DOMILLER@UALR.BITNET | Disclaimer: This does not      |
| 92-20-28 W,34-43-30 N.ICBMNET           | say what I say it doesn't say. |
----------------------------------------------------------------------------
From: gjc@mitech.com (George J. Carrette)
Newsgroups: vmsnet.internals
Subject: CRASHME on ALPHA
Date: 8 Sep 92 10:56:27 GMT
Organization: Mitech Corporation, Concord MA

Reports of the behavior of CRASHME on ALPHA have just started to trickle in.
Field test agreements would proclude detailed discussion in this forum. 

So this is just a reminder that CRASHME version 1.8 was posted to
VMSNET.SOURCES and also COMP.SOURCES.UNIX, and is generally available.
(I'll mail it to anybody who can't otherwise get a copy).

-gjc
Newsgroups: vmsnet.internals
From: mats@efd.lth.se (Mats Akerberg)
Subject: Fortran....
Organization: EFD, Lund Inst. of Technology, Lund, Sweden
Distribution: vmsnet
Date: 14 Sep 92 16:43:54 GMT


I just tried compile DISM32 again (Last time I did it was 1991).
No I have VMS 5.5-1 and FORTRAN V5.8-155

And the compilation bombs at the following rows in 
DISMEXTEND.FOR


01249        +          CRFCTLTBL.CRF$B_KEYTYPE .NE. 1).OR.
01250        +         CRFCTLTBL.CRF$W_ERRSTS .NE. 0 .OR.
01251        +         CRFCTLTBL.CRF$L_ENTRIES .NE. 0 .OR.
01252        +         CRFCTLTBL.CRF$L_DYNMEM(1) .NE. 0 .OR.
01253        +         CRFCTLTBL.CRF$L_DYNMEM(2) .NE. 0 .OR.
01254        +         CRFCTLTBL.CRF$L_MAXBLK .NE.
01255        +                          512*CRFCTLTBL.CRF$L_MEMEXP .OR.
01256        +         CRFCTLTBL.CRFDEF$$_FILL_10(1) .NE. 0 .OR.
01257        +         CRFCTLTBL.CRFDEF$$_FILL_10(2) .NE. 0 .OR.
01258        +         CRFCTLTBL.CRFDEF$$_FILL_10(3) .NE. 0 .OR.
01259        +         CRFCTLTBL.CRFDEF$$_FILL_10(4) .NE. 0 .OR.
01260        +         CRFCTLTBL.CRFDEF$$_FILL_10(5) .NE. 0 .OR.
01261        +         CRFCTLTBL.CRFDEF$$_FILL_10(6) .NE. 0 .OR.
01262        +         CRFCTLTBL.CRFDEF$$_FILL_10(7) .NE. 0 .OR.
01263        +         CRFCTLTBL.CRFDEF$$_FILL_10(8) .NE. 0)THEN
%F, Field name not defined for this structure
        [FDEF$$_FILL_10] in module EXTENDED_DATA_SYMTBL at line 1246


Any fortran guru out there.....
Something must be missing in my sys$library:FORSYSDEF.TLB

                  /Mats
 
--
  Mats Akerberg, System Manager (mats@efd.lth.se),(MATS@SELDC52) on Earn/Bitnet
  Lund Institute of Technology ,School of Electrical Engineering and  
  Computer Sciences. Snail: Box 118  S-221 00 Lund Sweden
  Phone: + 46 46-109847 FAX: + 46 46-129948 
Newsgroups: vmsnet.internals
From: boardman@cancer.unm.edu (Bob Boardman)
Subject: Re: DR bad, VAX PRO good
Date: Fri, 04 Sep 92 22:41:07 GMT
Organization: UNM Cancer Center
Distribution: world,local
Reply-To: boardman@cancer.unm.edu

In article <1992Sep4.135230.2305@cpu.com>,
           gwlester@cpu.com (Gerald W. Lester) writes:
>In article <3SEP199210004588@mrsvax.mis.arizona.edu>,
     jms@mrsvax.mis.arizona.edu (Entia non blah de blah) writes:
>>In article <1992Sep1.221944.12789@cpu.com>, gwlester@cpu.com writes...
>>> 
>>>P.S. - I have a Matco mug for pointing out to DR that VMS does *NOT* run on 
>>>       any of the PDP-11 series.
>>
>>It depends on whether you consider a VAX-11/780 a PDP-11.  If you define a
>>PDP-11 as a system which runs PDP-11 code "native" (i.e., without software
>>emulators, as in the newer VAX systems), the VAX-11/780 is a fine PDP-11
>>which happens to run VMS.  Also, since you can microcode it yourself, it
>>can run WPS-8 as well (and does).
>
>	The PDP-11 I'm refering to was the PDP-11/84.  Yets try not to make
>asses of ourself, *Digital* defines the PDP-11 series, not us.  I guess under
>your definition (and with some interesting microcode) I could change a
>VAX-11/780 into a PDP-10!  Of course with how you just defined a processor
>series, many of the new VAX models are not a VAX since they use software
>emulation to handle some of the instructions.  
>
	While VMS probably has not run on a PDP-11, I have a PDP-11 which
  could be made to run something like VMS - it's an old 11/60, which with
  the WCS/UCS option (writable control store/user control store), allowed
  one to actually program one's own microcode.  I imagine that given enough
  time, one could have it running VMS after a fashion.
	I don't have the time, though!  ;-}

  -Bob

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|      Bob Boardman, University of New Mexico, Albuquerque, New Mexico        |
|         internet:boardman@cancer.unm.edu    bitnet:BOARDMAN@UNMB            |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Newsgroups: vmsnet.internals
From: bandy@netnews.jhuapl.edu (Bandy Michael C. PDP x3351 )
Subject: Re: Fortran....
Organization: JHU/Applied Physics Laboratory
Distribution: vmsnet
Date: Tue, 15 Sep 1992 20:31:38 GMT

mats@efd.lth.se (Mats Akerberg) writes:


>I just tried compile DISM32 again (Last time I did it was 1991).
>No I have VMS 5.5-1 and FORTRAN V5.8-155

>And the compilation bombs at the following rows in 
>DISMEXTEND.FOR


>01249        +          CRFCTLTBL.CRF$B_KEYTYPE .NE. 1).OR.
    [ lots more of the same deleted ... ]
>01262        +         CRFCTLTBL.CRFDEF$$_FILL_10(7) .NE. 0 .OR.
>01263        +         CRFCTLTBL.CRFDEF$$_FILL_10(8) .NE. 0)THEN
>%F, Field name not defined for this structure
>        [FDEF$$_FILL_10] in module EXTENDED_DATA_SYMTBL at line 1246

Have you tried "FORTRAN /EXTEND_SOURCE"?  I think they changed the defaults
somewhere along the version chain.

		Mike Bandy
		Johns Hopkins University / Applied Physics Lab
		bandy@aplcomm.apljhu.edu
From: gwlester@cpu.com (Gerald W. Lester)
Newsgroups: vmsnet.internals
Subject: Re: DR bad, VAX PRO good
Date: 4 Sep 92 13:52:30 GMT
Reply-To: gwlester@cpu.com
Distribution: world,local
Organization: Computerized Processes Unlimited, Metairie, LA, (504)-889-2784

In article <3SEP199210004588@mrsvax.mis.arizona.edu>, jms@mrsvax.mis.arizona.edu (Entia non sunt multiplicanda praeter necessitatem) writes:
>In article <1992Sep1.221944.12789@cpu.com>, gwlester@cpu.com writes...
>> 
>>	The problem that at least some of us have is that we don't have time to
>>read all of sources of information.  I have eliminate DR from my list due to
>>the amount of material that I had to read to get new and useful information.
>> 
>
>Well, it's a tradeoff, isn't it?  You can read nothing that ever comes to
>you, and spend all your time running around re-inventing the wheel.  Or,
>you can do nothing but read all day long, have all of the answers, and no
>time to do your job.  I still claim that you can't be an effective and
>useful system manager without reading DR.  If all you do is kernel mode
>programming, that's one thing.  But who has a job description that narrow
>these days?

	Joel, I think we must agree to disagree, since in my opion DR is a
waste of trees and if it were sent via the inter net a waste of bandwidth.

>
>>P.S. - I have a Matco mug for pointing out to DR that VMS does *NOT* run on 
>>       any of the PDP-11 series.
>
>It depends on whether you consider a VAX-11/780 a PDP-11.  If you define a
>PDP-11 as a system which runs PDP-11 code "native" (i.e., without software
>emulators, as in the newer VAX systems), the VAX-11/780 is a fine PDP-11
>which happens to run VMS.  Also, since you can microcode it yourself, it
>can run WPS-8 as well (and does).

	The PDP-11 I'm refering to was the PDP-11/84.  Yets try not to make
asses of ourself, *Digital* defines the PDP-11 series, not us.  I guess under
your definition (and with some interesting microcode) I could change a
VAX-11/780 into a PDP-10!  Of course with how you just defined a processor
series, many of the new VAX models are not a VAX since they use software
emulation to handle some of the instructions.  

==========================================================================
* Gerald W. Lester                        !   Voice:  (504)-889-2784     *
* Computerized Processes Unlimited        !   FAX:    (504)-889-2799     *
* 4200 S. I-10 Service Road, Suite #205   !   E-Mail: gwl@cpu.com        *
* Metairie, LA  70001                     !                              *
==========================================================================
From: Hunter Goatley <goathunter@WKUVX1.BITNET>
Newsgroups: vmsnet.internals
Subject: RE: Moving DDTs etc.
Date: Thu, 10 Sep 1992 08:42:08 EDT
Organization: Macro32<==>Vmsnet.Internals Gateway
X-Gateway-Source-Info: Mailing List

raxco!galaxy.dnet!gleeve@uunet.UU.NET writes:
>
>I'm inclined to agree with Jon Pinkley's extensions to my suggestions
>about moving DDTs into intercept UCBs. (And yes, I meant DDTs, not
>DDBs...too many of these darn three letter acronyms occasionally
>fry my brain when posting...)
>   While such suggestions cannot be enforced, having a number of folks
>publically promise to follow them (and I will in some code I'm developing
>for starters) will help to create support for the standard. In the

[...]

For what it's worth, when I started at Clyde Digital back in '87, we
spent some time trying to convince DEC to go along with something very
similar to what you're talking about.  We could never get any support
from DEC, even when we pointed out that they have layered products
that can crash the system when used together in the right (wrong)
combination.  Those products include SSU, DEC Test Manager, Terminal
Fallback, and ACMS.

Good luck this time around....

Hunter
------
Hunter Goatley, VMS Systems Programmer, Western Kentucky University
goathunter@WKUVX1.BITNET, 502-745-5251
Newsgroups: vmsnet.internals
Subject: Why we need PATCH
From: leonard@telcom.arizona.edu (Aaron Leonard)
Date: 10 Sep 92 09:25:23 MST
Reply-To: Leonard@Arizona.EDU
Distribution: world,local
Organization: University of Arizona Telecommunications

Listen up vendors (especially you, DEC):

We users need PATCH because vendors don't give us sources to everything.
So PATCHing (or otherwise poking) .EXEs is the only way we can fix or
improve your code.

End of debate.

Aaron
From: murphy@npri6.npri.com (David P. Murphy)
Newsgroups: vmsnet.internals
Subject: Re: PATCH on ALPHA ?
Date: 7 Sep 92 18:53:38 GMT
Distribution: world
Organization: NPRI, Alexandria VA


 >Secondly, compare the experience of the average VMS patcher with that
 >of your average ALPHA patcher. I hope this doesn't offend anyones
 >pride too much, but I wouldn't really put a lot of trust in a patch on a
 >fairly new machine (You can't even buy them yet!) compared to a newly
 >compiled program. How many ALPHA gurus can there be in the industry by now?
 >And so what proportion of developers will be able to successfully make use
 >of PATCH?
 >
 >robbie@winkle.bhpese.oz.au

i agree (obviously) with your claim that there can't be too many
experienced ALPHA patchers.  however, i must point out that your
conclusion is overly optimistic:  since there will be a demand
for ALPHA patches, all the more reason to start _now_!

"*how* many registers?  hey, what happened to my arglist??"
-- me

ok
dpm
-- 
murphy@npri6.npri.com 602 Cameron St. Alexandria, VA 22314 (703) 683-9090

              When every one is dead the Great Game is finished.  Not before.
                              --- Hurree Babu, "Kim"
From: murphy@npri6.npri.com (David P. Murphy)
Newsgroups: vmsnet.internals
Subject: Re: DR bad, VAX PRO good
Date: 3 Sep 92 13:34:08 GMT
Distribution: world,local
Organization: NPRI, Alexandria VA


 >Suggesting that one should refuse to read anything in the same format as
 >the National Enquirer betrays an astonishing parochialism.  Eliminating
 >fee-free publications from your reading list will cause you to be
 >ignorant of the nature of the industry you work in, probably more so than
 >if you believed every word that Bill Hancock wrote.  You should be able to
 >distinguish between fact and fantasy, between press release and media hype,
 >and between correct and incorrect technical information. 
 > [stuff deleted]
 >If you make no attempt to discriminate
 >in what you read, but simply latch onto the most reliable source to the
 >exclusion of all others, your knowledge will be woefully inadequate and
 >incomplete.

oh, very well.  i refuse to read DR because it is not worth my time,
not because i think it is wildly inaccurate.  i rarely see an article
which is useful to me as a systems programmer, so i don't bother reading it.
i'm probably missing something good every once in a while, but i'll survive.

>/* Now for the flame part. */
>I found it particularly amusing that those who would claim that my own work
>is fact-free, useless, and not worth reading, are themselves incapable of
>preparing good postings.  Certainly my trust in the abilities of writers
>who refuse to capitalize the word "I," cannot spell the word "faineant," do
>not know the title of the "National Enquirer," do not have good
>adjective/noun number agreement (e.g., "a few reservation about"), fail to 
>capitalize proper nouns, misuse commas and conjunctions (e.g., "Albeit, a 
>good series") and question marks, and pepper their prose with redundancies
>(e.g., "biased or prejudiced toward") to evaluate the merit---technical or
>otherwise---of a publication is severely shaken.  
>
>jms@mrsvax.mis.arizona.edu (Joel M Snyder)

"those who can't, teach"

as far as i can tell, i'm guilty of only one of these infractions:
i'm too lazy to hold down the SHIFT key when typing 'i'.  :-)
i prefer to think of this habit as a bit of humility on my part;
why should i capitalize 'i' if i don't capitalize 'you' or 'we' or 'them'?

anyway, it's just a post on the net, not an article being submitted for
publication in a national magazine, so it's not worth the effort of
extensive proofreading (although some people, apparently, never proofread
due to time or software or personal habits).

hey, and, no hard feelings, joel.

ok
dpm
-- 
murphy@npri6.npri.com 602 Cameron St. Alexandria, VA 22314 (703) 683-9090

              When every one is dead the Great Game is finished.  Not before.
                              --- Hurree Babu, "Kim"
From: richard@npri6.npri.com (Richard Head)
Newsgroups: vmsnet.internals
Subject: Re: Digital Corporate Security - on my tail
Date: 5 Sep 92 00:09:04 GMT
Distribution: world
Organization: NPRI, Alexandria VA

Cool!
-- 
richard@npri6.npri.com  <Richard Head>
I've fallen and I can't reach my beer!
Newsgroups: vmsnet.internals
From: zrepachol@cc.curtin.edu.au (Paul Repacholi)
Subject: Re: DR bad, VAX PRO good
Organization: Curtin University of Technology
Distribution: world,local
Date: Sat, 5 Sep 1992 05:04:22 GMT

In article <n5mn#n=@lynx.unm.edu>, boardman@cancer.unm.edu (Bob Boardman) writes:
> In article <1992Sep4.135230.2305@cpu.com>,
>            gwlester@cpu.com (Gerald W. Lester) writes:
>>In article <3SEP199210004588@mrsvax.mis.arizona.edu>,
>      jms@mrsvax.mis.arizona.edu (Entia non blah de blah) writes:
>>>In article <1992Sep1.221944.12789@cpu.com>, gwlester@cpu.com writes...
>>>> 
>>>>P.S. - I have a Matco mug for pointing out to DR that VMS does *NOT* run on 
>>>>       any of the PDP-11 series.
>>>
...

I guess it's now time to drag out the old chestnut again...
What is the FULL name of the 780?

>>your definition (and with some interesting microcode) I could change a
>>VAX-11/780 into a PDP-10!  Of course with how you just defined a processor
No, you could not get at enough of the MMU/pager. Was 4 bits too stupid
as well...

>>series, many of the new VAX models are not a VAX since they use software
>>emulation to handle some of the instructions.  

And prior to that, some Vaxen did not conform to the Vax ARM.

> 	While VMS probably has not run on a PDP-11, I have a PDP-11 which
>   could be made to run something like VMS - it's an old 11/60, which with
>   the WCS/UCS option (writable control store/user control store), allowed
>   one to actually program one's own microcode.  I imagine that given enough
>   time, one could have it running VMS after a fashion.

Ah, any old timers remember obscure references to "the emulator"?

~Paul