[Info-vax] OpenVMS I64 V8.1 "Evaluation Release"?

[Doug Phillips]

On Mar 29, 8:19 pm, koeh... at eisner.nospam.encompasserve.org (Bob
Koehler) wrote:
> In article <jksliq$s8... at Iltempo.Update.UU.SE>, Johnny Billquist <b... at softjar.se> writes:
>
> > It wasn't an ECO (ECO = Engineering Correction Order). The VAX
> > architecture was expanded with a second mode for the PTE, which was
> > implemented on the NVAX CPU, which allowed for a 34 bit physical
> > address. The same architecture change also changed the layout of the
> > process memory space by removing the S1 memory space, and reducing the
> > size of S0, so you could get much closer to actually using 4 GB in a
> > single process (although you still couldn't get all the way, of course...)
>
>   A fellow from VMS Engineering (I don't rememeber the name, but I spoke to
>   him in person) called it an ECO against the VAX hardware architecture
>   specification.


ECO = Engineering _Change_ Order. ECOs can apply to documents,
software and/or hardware, and I've heard the term used in many other
industries.