[Info-vax] Intel proposal to simplify x86-64

Pizza RAC pizzaracorders at gmail.com
Thu Jun 8 17:31:25 EDT 2023


On Monday, June 5, 2023 at 9:39:47 AM UTC-4, John H Reinhardt wrote:
> On 6/5/2023 7:21 AM, Simon Clubley wrote: 
> > On 2023-06-05, Chris Townley <ne... at cct-net.co.uk> wrote: 
> >> On 05/06/2023 13:11, Simon Clubley wrote: 
> >>> On 2023-06-05, terry-... at glaver.org <terry-... at glaver.org> wrote: 
> >>>> 
> >>>> Does anyone with a VSI x86 kit have TECO? 
> >>> 
> >>> I wouldn't mind an answer to that question either. :-) 
> >>> 
> >>> (Not because I use it these days, but simply because VSI said they were 
> >>> going to offer TECO in some form on x86-64 and I wonder if they followed 
> >>> through with that.) 
> >>> 
> >>> Simon. 
> >>> 
> >>> PS: I've been offered x86-64 access but am _way_ too busy with other 
> >>> things at the moment, so will not be setting it up any time in the near 
> >>> future. (Just mentioning this before someone makes the suggestion. :-)) 
> >>> 
> >> 
> >> The V9.2-1 release notes stated it does not include TECO 
> >> 
> > 
> > Thanks. 
> > 
> > Simon. 
> >
> Neither does the E9.2-1 
> 
> $ show system/noproc 
> OpenVMS E9.2-1 on node SCALZI 5-JUN-2023 08:21:00.83 Uptime 21 08:35:01 
> $ teco 
> %DCL-W-IVVERB, unrecognized command verb - check validity and spelling 
> \TECO\ 
> $ dir sys$system:*TECO* 
> %DIRECT-W-NOFILES, no files found 
> 
> 
> I'm thinking TECO is probably a low priority item. If Compaq/HP had to VEST and TIE/VEST it then the source must be way out of date and not an easy upgrade. 
> 
> John H. Reinhardt

you may have to vest DIBOL if it is not ported to x86 by synergy company



More information about the Info-vax mailing list