Andy "Museumpiece" Goldstein retirement

[V***@SendSpamHere.ORG]

Wow. What a morning eye-opener and before I even had a chance to
take my first sip of coffee too...

In my email that arrived during the sleep phase was an email from
Andy Goldstein announcing his retirement. Effective June 5 and co-
inciding with Sue's departure. :(

Good luck in your retirement Andy. Thanks for your years of work
on the best operating system in the known universe.

Will the last person out of VMS Engineering please turn off the
lights?

[Tom Dahl]

You may be seeing a lot more such letters today and tomorrow; Friday
is the last day all of us being let go have access to HP resources
(such as our computers and email addresses).

Back on topic: I very much enjoyed working with Andy, and wish him
well in retirement. (As for me, I'm sadly a bit too young to retire;
my 27 years with the company didn't get me close enough to the golden
years!)

[JF Mezei]

Post by Tom Dahl
You may be seeing a lot more such letters today and tomorrow; Friday
is the last day all of us being let go have access to HP resources
(such as our computers and email addresses).

Is June 5th the one final "layoff day" for new england staff, or are
there other similar days for more groups to be let go ?

I originally had been told it would be spread until Oct 31 (end of
fiscal year). Or are they now finishing the job this week ?

Or put differently, if, on June 6th, we see someone posting from an HP
account, can we assume he is there to stay beyond Oct 31, or would he be
slated for another round between now and Oct 31 ?

[Tom Dahl]

Post by JF Mezei
Is June 5th the one final "layoff day" for new england staff, or are
there other similar days for more groups to be let go ?

June 5th is when those of us in the big VMS layoff lose all access to
HP -- turn in HP badges, no more access to HP facilities, HP email
addresses, etc.

Post by JF Mezei
I originally had been told it would be spread until Oct 31 (end of
fiscal year).

That had been the plan (note past-tense).

Post by JF Mezei
Or put differently, if, on June 6th, we see someone posting from an HP
account, can we assume he is there to stay beyond Oct 31, or would he be
slated for another round between now and Oct 31 ?

I wouldn't make very many assumptions.

[Tom Dahl]

...for new england staff....

I forgot to comment on this earlier. There are VMS folks outside of
New England, who are also affected. Tip your hat to them too!

[JF Mezei]

Post by Tom Dahl
I forgot to comment on this earlier. There are VMS folks outside of
New England, who are also affected. Tip your hat to them too!

Is Mr TCPIP Surfer Boy in the gold coast in Australia going on the dole
? I feel less sorry for him because he lives near the pacific ocean with
great beaches and good weather :-) :-) :-) :-) :-)

[Richard B. Gilbert]

Post by Tom Dahl
You may be seeing a lot more such letters today and tomorrow; Friday
is the last day all of us being let go have access to HP resources
(such as our computers and email addresses).
Back on topic: I very much enjoyed working with Andy, and wish him
well in retirement. (As for me, I'm sadly a bit too young to retire;
my 27 years with the company didn't get me close enough to the golden
years!)

Face it! Your "golden years" were thirty or so years ago when you
couldn't afford them!

[JF Mezei]

Post by V***@SendSpamHere.ORG
In my email that arrived during the sleep phase was an email from
Andy Goldstein announcing his retirement. Effective June 5 and co-
inciding with Sue's departure. :(

I wonder how many people are leaving June 5th, and how many will remain
who will leave later. I suspect that John Reagan will stay. I guess
we'll have to wait until Oct 31 to see if he still posts from an hp.com
account :-)

I also heard that some dude who is very good with X and graphic drivers
might be retained by HP in north america.

I also heard that the IO group would stay because they also handle other
OSs. Nothing confirmed.

I wonder if Mr Paul Printer Anderson is staying. Since he supports HP's
core business, perhaps they would retain him ?

Sue's mini "bootcamp" last week was probably quite the farewell for many
people who had worked together for a very long time. I can understand
they wanted to stay in the family, but it would have been really nice
for us to be able to say a proper farewell and thank you for all the
work they did.

And it says a lot that it was Sue who organised that "farewell bootcamp"
in her own time, it wasn't an HP party.

[Tom Dahl]

Post by JF Mezei
I also heard that the IO group would stay because they also handle other
OSs. Nothing confirmed.

Many of the VMS I/O engineers were moved into a shared-OS group last
year. I don't think they are directly affected by the 2009 activity.

I don't feel comfortable discussing the fate of other individuals;
they can share their stories if and as they see fit.

Post by JF Mezei
And it says a lot that it was Sue who organised that "farewell bootcamp"
in her own time, it wasn't an HP party.

I agree that it says a lot that us employees had to organize (and pay
for) our own farewell get-togethers.

[Paul Anderson]

Post by JF Mezei
I wonder if Mr Paul Printer Anderson is staying. Since he supports
HP's core business, perhaps they would retain him ?

No such luck. As of close of business June 5, I am no longer an HP
employee.

However, I have retained my knowledge of software development and
printers and all the other skills that allowed me to provide twelve
years of most excellent DCPS releases, so I'd be glad to talk to anyone
that might have a job opening.

Paul

[V***@SendSpamHere.ORG]

Post by Paul Anderson

Post by JF Mezei
I wonder if Mr Paul Printer Anderson is staying. Since he supports
HP's core business, perhaps they would retain him ?

No such luck. As of close of business June 5, I am no longer an HP
employee.
However, I have retained my knowledge of software development and
printers and all the other skills that allowed me to provide twelve
years of most excellent DCPS releases, so I'd be glad to talk to anyone
that might have a job opening.

Wow! Too bad Paul... From d|i|g|i|t|a|l to Genicom and back. I'd
have bet they would have kept you. I don't have any job opening to
offer you but if you make one of the treks down to Lavalette you've
mentioned to me in the past, let me know so we can get together and
tip back a beer or three.

Thanks for all the DCPS help in the past and the help with my LNCO2
which I wish I could get consumables for... such a nice printer and
now just a space consumer.

[Paul Anderson]

I don't have any job opening to offer you but if you make one of the
treks down to Lavalette you've mentioned to me in the past, let me
know so we can get together and tip back a beer or three.

I made it down to Lavallette last summer for the first time in many
years, but I doubt I'll be down this year. Might make it down to
Roselle Park for some White Castles though.

Thanks for all the DCPS help in the past and the help with my LNCO2
which I wish I could get consumables for... such a nice printer and
now just a space consumer.

I know we've talked about what consumables you need, and their
unavailability. What is it you need? Would supplies for the QMS
Magicolor 2 printer work in the LNC02? (Yes, I know QMS was absorbed
into Minolta and now isn't even mentioned since the company is now
Konica Minolta.)

Maybe it's time to retire the LNC02. New color laser printers are
pretty cheap these days. I even think HP makes some. ;-)

Paul

[V***@SendSpamHere.ORG]

Post by Paul Anderson

I don't have any job opening to offer you but if you make one of the
treks down to Lavalette you've mentioned to me in the past, let me
know so we can get together and tip back a beer or three.

I made it down to Lavallette last summer for the first time in many
years, but I doubt I'll be down this year. Might make it down to
Roselle Park for some White Castles though.

You don't like yourself very much, do you? :)

Post by Paul Anderson
Maybe it's time to retire the LNC02. New color laser printers are
pretty cheap these days. I even think HP makes some. ;-)

...but I won't buy anything HP.

I'll just have to get by on the Epson and Canon ink-jets. What I
really want is the PostScript. I now sent PS to a linux queue and
it converts it to PDF and forwards to a printer.

[JF Mezei]

Post by Paul Anderson
However, I have retained my knowledge of software development and
printers and all the other skills that allowed me to provide twelve
years of most excellent DCPS releases, so I'd be glad to talk to anyone
that might have a job opening.

Sorry to see you leave VMS. You were a faithful contributor to c.o.v and
your answers were always very good and helpful.

How did you manage to escape HP's brain wipe ? Were you wearing dark
glasses to avoid their flashing device from erasing your memory of VMS ?

:-) :-) :-) :-)

[Paul Anderson]

Post by JF Mezei
Sorry to see you leave VMS. You were a faithful contributor to c.o.v
and your answers were always very good and helpful.

I won't stop lurking or contributing here. I just can't answer as an
HP employee and will have no knowledge of future plans or the changes
the new engineers are making.

Post by JF Mezei
How did you manage to escape HP's brain wipe ? Were you wearing dark
glasses to avoid their flashing device from erasing your memory of VMS ?

Reynolds Wrap.

Paul

[Richard B. Gilbert]

Post by Paul Anderson

Post by JF Mezei
I wonder if Mr Paul Printer Anderson is staying. Since he supports
HP's core business, perhaps they would retain him ?

No such luck. As of close of business June 5, I am no longer an HP
employee.
However, I have retained my knowledge of software development and
printers and all the other skills that allowed me to provide twelve
years of most excellent DCPS releases, so I'd be glad to talk to anyone
that might have a job opening.
Paul

If you need recommendations, don't hesitate to ask. I think a lot of
people here know you.

I recall talking with you on the phone about ten years ago about
printers that could print bar codes.

[Paul Anderson]

Post by Richard B. Gilbert
If you need recommendations, don't hesitate to ask. I think a lot of
people here know you.

I've received many kind words from people I've worked with over the
years. If anyone is comfortable giving me a recommendation on my
Linkedin page, that would be wonderful!

<http://www.linkedin.com/in/paulranderson>

Post by Richard B. Gilbert
I recall talking with you on the phone about ten years ago about
printers that could print bar codes.

I will certainly miss all the people who have presented me with
printing challenges over the years. Hopefully there will be even more
challenges wherever I wind up next.

Paul

[Richard B. Gilbert]

Post by Paul Anderson

Post by Richard B. Gilbert
If you need recommendations, don't hesitate to ask. I think a lot of
people here know you.

I've received many kind words from people I've worked with over the
years. If anyone is comfortable giving me a recommendation on my
Linkedin page, that would be wonderful!
<http://www.linkedin.com/in/paulranderson>

Post by Richard B. Gilbert
I recall talking with you on the phone about ten years ago about
printers that could print bar codes.

I will certainly miss all the people who have presented me with
printing challenges over the years. Hopefully there will be even more
challenges wherever I wind up next.

That's what makes it fun!

[DaveG]

Wow.  What a morning eye-opener and before I even had a chance to
take my first sip of coffee too...
In my email that arrived during the sleep phase was an email from
Andy Goldstein announcing his retirement.  Effective June 5 and co-
inciding with Sue's departure.  :(
Good luck in your retirement Andy.  Thanks for your years of work
on the best operating system in the known universe.
Will the last person out of VMS Engineering please turn off the
lights?
--
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG
 http://www.quirkfactory.com/popart/asskey/eqn2.png
  "Well my son, life is like a beanstalk, isn't it?"

I recall an Andy story at a long ago DECUS symposia. Something about
a junior engineer making a mistake fixing something in backup (I
think). Andy's first course of action: "I find a heavy blunt
instrument". That brought a roar from the audience.

Thanks Andy.

[Phillip Helbig---remove CLOTHES to reply]

Post by V***@SendSpamHere.ORG
Good luck in your retirement Andy. Thanks for your years of work
on the best operating system in the known universe.
Will the last person out of VMS Engineering please turn off the
lights?

Back in 1999 I made a pilgrimage up to Nashua. Steve Lionel showed me
around and I got to meet Hoff, Andy etc. It seems that an era is coming
to an end.

[Jerry]

Wow.  What a morning eye-opener and before I even had a chance to
take my first sip of coffee too...
In my email that arrived during the sleep phase was an email from
Andy Goldstein announcing his retirement.  Effective June 5 and co-
inciding with Sue's departure.  :(
Good luck in your retirement Andy.  Thanks for your years of work
on the best operating system in the known universe.
Will the last person out of VMS Engineering please turn off the
lights?
--
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG
 http://www.quirkfactory.com/popart/asskey/eqn2.png
  "Well my son, life is like a beanstalk, isn't it?"

Any word on who will be maintaining TECO? :)

[V***@SendSpamHere.ORG]

Post by V***@SendSpamHere.ORG

Wow. =A0What a morning eye-opener and before I even had a chance to
take my first sip of coffee too...
In my email that arrived during the sleep phase was an email from
Andy Goldstein announcing his retirement. =A0Effective June 5 and co-
inciding with Sue's departure. =A0:(
Good luck in your retirement Andy. =A0Thanks for your years of work
on the best operating system in the known universe.
Will the last person out of VMS Engineering please turn off the
lights?
--
VAXman- A Bored Certified VMS Kernel Mode Hacker =A0 =A0VAXman(at)TMESIS(=

dot)ORG

=A0http://www.quirkfactory.com/popart/asskey/eqn2.png
=A0 "Well my son, life is like a beanstalk, isn't it?"

Any word on who will be maintaining TECO? :)

ROTFLMFAO!!!

[Bob Koehler]

Post by Jerry
Any word on who will be maintaining TECO? :)

TECO need maintenance? I thought all TECO ever got was the
occasional recompile. 8-)

[Michael Moroney]

Post by Bob Koehler

Post by Jerry
Any word on who will be maintaining TECO? :)

TECO need maintenance? I thought all TECO ever got was the
occasional recompile. 8-)

I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed. And the
VESTed image was later AESTed to Itanic.

[John Reagan]

Post by Michael Moroney

In article

Post by Jerry
Any word on who will be maintaining TECO? :)

TECO need maintenance? I thought all TECO ever got was the
occasional recompile. 8-)

I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed. And the
VESTed image was later AESTed to Itanic.

That is correct. The TECO source code uses several VAX Macro-32 "tricks"
that the Alpha/I64 Macro compiler doesn't support. It is VESTed/AESTed.
The Alpha version is reasonable, the I64 version is somewhat slow (I'm being
polite). Some changes are coming for AEST/TIE to help performance. Andy
did some tests on the upcoming changes and say it was actually usable.

Also, somebody here in this newsgroup has been working on a C implementation
of TECO but I don't know the current status.

John (who posts from my home account but still works for HP)

[Richard Maher]

Hi John,

Post by John Reagan
John (who posts from my home account but still works for HP)

Good catch! I was on the chair with noose round neck :-(

Cheers Richard Maher

[IanMiller]

Post by Richard Maher
Hi John,

Post by John Reagan
John (who posts from my home account but still works for HP)

Good catch! I was on the chair with noose round neck :-(
Cheers Richard Maher

Perhaps Richard Maher can start a campaign for a native port of teco.

There are a couple of partial implementations in C around the place
but if HP released the source code of the real teco then people could
port this vital business software to VMS I64.

It could be called teco-64

[Richard Maher]

Hi Ian,

Post by IanMiller
Perhaps Richard Maher can start a campaign for a native port of teco.

Never used teco and am personally not interested in it. I just see the John
Reagans of HP/VMS as life-sustaining forces that are pstponing HP from
flicking off the switch. We'll need people like him to rebuild when/if the
dust settles!

I will look back in Sept/Oct and hope I'm not lighting another candle :-(

Cheers Richard Maher

Post by IanMiller
Hi John,

Post by John Reagan
John (who posts from my home account but still works for HP)

Good catch! I was on the chair with noose round neck :-(
Cheers Richard Maher

Perhaps Richard Maher can start a campaign for a native port of teco.

There are a couple of partial implementations in C around the place
but if HP released the source code of the real teco then people could
port this vital business software to VMS I64.

It could be called teco-64

[Richard B. Gilbert]

Post by IanMiller

Post by Richard Maher
Hi John,

Post by John Reagan
John (who posts from my home account but still works for HP)

Good catch! I was on the chair with noose round neck :-(
Cheers Richard Maher

Perhaps Richard Maher can start a campaign for a native port of teco.
There are a couple of partial implementations in C around the place
but if HP released the source code of the real teco then people could
port this vital business software to VMS I64.
It could be called teco-64

I've used teco ONCE in 30 years! I forget what I did with it but the
alternative was a couple of hours of tedium using EDT. TECO whipped
through the job in seconds AFTER I spent 30 or 45 minutes figuring out
exactly HOW to do it. And AFTER making a backup copy of the file.

If I want power tools without "blade guards" I'll use Unix!!!

[John Smith (not the one @ HP)]

Post by Richard B. Gilbert

Post by IanMiller

Post by Richard Maher
Hi John,

Post by John Reagan
John (who posts from my home account but still works for HP)

Good catch! I was on the chair with noose round neck :-(
Cheers Richard Maher

Perhaps Richard Maher can start a campaign for a native port of teco.
There are a couple of partial implementations in C around the place
but if HP released the source code of the real teco then people could
port this vital business software to VMS I64.
It could be called teco-64

I've used teco ONCE in 30 years! I forget what I did with it but the
alternative was a couple of hours of tedium using EDT. TECO whipped
through the job in seconds AFTER I spent 30 or 45 minutes figuring out
exactly HOW to do it. And AFTER making a backup copy of the file.
If I want power tools without "blade guards" I'll use Unix!!!

TECO was the only way to go when using x.25 as it kept the packet charges to
a minimum.

[Tim E. Sneddon]

Post by John Reagan

Post by Michael Moroney

In article

Post by Jerry
Any word on who will be maintaining TECO? :)

TECO need maintenance? I thought all TECO ever got was the
occasional recompile. 8-)

I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed. And the
VESTed image was later AESTed to Itanic.

That is correct. The TECO source code uses several VAX Macro-32 "tricks"
that the Alpha/I64 Macro compiler doesn't support. It is VESTed/AESTed.

That's putting it lightly :-) I learnt a whole lot about the VAX and
MACRO-32 that I never knew trying to follow that code. I also discovered
quite a few bugs that are due to that "unique" coding style.

Post by John Reagan
The Alpha version is reasonable, the I64 version is somewhat slow (I'm being
polite). Some changes are coming for AEST/TIE to help performance. Andy
did some tests on the upcoming changes and say it was actually usable.

It's much more than that :-) TECO on I64 flys now. Andy's comment was
"Woowza!". Although it is still slower than the Alpha.

Post by John Reagan
Also, somebody here in this newsgroup has been working on a C implementation
of TECO but I don't know the current status.

Yes. It is coming along, slowly. Many other things have cropped up and
I don't get to it as often as I'd like. Unfortunately trying to make
the C code follow the same logical execution path, while still being
readable is a task not to be taken lightly.

Post by John Reagan
John (who posts from my home account but still works for HP)

Glad to hear it. I hadn't heard from you in a while and was beginning
to wonder... :-)

Tim.

[Bob Koehler]

Post by John Reagan
Also, somebody here in this newsgroup has been working on a C implementation
of TECO but I don't know the current status.

I've seen a few re-implmentations of parts of TECO, and I have one
written in C that runs under Windows. I can't vouch for it's
usefullness as I never got past the basics in TECO.

[Bob Eager]

Post by Michael Moroney

Post by Bob Koehler

Post by Jerry
Any word on who will be maintaining TECO? :)

TECO need maintenance? I thought all TECO ever got was the
occasional recompile. 8-)

I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed. And the
VESTed image was later AESTed to Itanic.

Hmmm.I remember reading the TECO source on TOPS-10. It ran loops in the
registers to improve speed! (i.e. used the registers (1st 16 memory
locations) as instruction space).

[Michael Moroney]

Post by Bob Eager

Post by Michael Moroney

Post by Bob Koehler
TECO need maintenance? I thought all TECO ever got was the
occasional recompile. 8-)

I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed. And the
VESTed image was later AESTed to Itanic.

Hmmm.I remember reading the TECO source on TOPS-10. It ran loops in the
registers to improve speed! (i.e. used the registers (1st 16 memory
locations) as instruction space).

I worked on porting some godawful VAX Macro-32 code to run on Itanic.
I wish I could see the VAX TECO code to see which one has the cleverest,
the sneakiest and the stupidest tricks.

I like executing code out of registers, though you can't do that on a VAX.

[Richard B. Gilbert]

Post by Bob Eager

Post by Michael Moroney

Post by Bob Koehler

Post by Jerry
Any word on who will be maintaining TECO? :)

TECO need maintenance? I thought all TECO ever got was the
occasional recompile. 8-)

I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed. And the
VESTed image was later AESTed to Itanic.

Hmmm.I remember reading the TECO source on TOPS-10. It ran loops in the
registers to improve speed! (i.e. used the registers (1st 16 memory
locations) as instruction space).

Some people will do anything to make code run faster or use less memory.
Thirty or more years ago this could sometimes be justified: processors
were dog slow and memory was mostly very expensive magnetic core.
Today, the side effects; e.g. making the code extremely difficult to
understand and maintain, tend to outweigh the benefits.

[Rich Alderson]

Post by Richard B. Gilbert

Post by Bob Eager
Hmmm.I remember reading the TECO source on TOPS-10. It ran loops in the
registers to improve speed! (i.e. used the registers (1st 16 memory
locations) as instruction space).

Some people will do anything to make code run faster or use less memory.
Thirty or more years ago this could sometimes be justified: processors
were dog slow and memory was mostly very expensive magnetic core.
Today, the side effects; e.g. making the code extremely difficult to
understand and maintain, tend to outweigh the benefits.

The ACs on the PDP-6 and PDP-10 have always mapped to the first 16 locations in
memory[1], and the idiom of using that memory space for tight fast loops and
other small routines--like early BOOT programs--has been in place for 45 years.
We still use it on fast modern hardware with lots and lots of memory, because
it is useful.

Code that uses this idiom is no harder to understand or to maintain than any
other on the system, because it's an intentional feature of the architecture,
not an accident.

[1] In fact, the "fast memory" ACs were an option on the KA-10 processor, but
only a single customer ever ordered a system in that configuration.

[Bob Koehler]

Post by Bob Eager
Hmmm.I remember reading the TECO source on TOPS-10. It ran loops in the
registers to improve speed! (i.e. used the registers (1st 16 memory
locations) as instruction space).

Actually, there were no user accessable registers on the PDP-10.
The first 16 locations in memory were known as accumulators, many
instructions had field that could only address them, and they
did tend to be fast (just about always in cache).

So we used them like registers, but had to watch out for 0, sometimes
it was an accumulator address, sometimes it was ignored.

[Phillip Helbig---remove CLOTHES to reply]

Post by Michael Moroney

Post by Bob Koehler

Post by Jerry
Any word on who will be maintaining TECO? :)

TECO need maintenance? I thought all TECO ever got was the
occasional recompile. 8-)

I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed. And the
VESTed image was later AESTed to Itanic.

Wasn't even the venerable EDT vested?

[Bob Koehler]

Post by Michael Moroney
I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed.

I heard that, too.

Post by Michael Moroney
And the VESTed image was later AESTed to Itanic.

I had not heard that, I thought they managed to go back and rework
the Macro-32. If I had an IA64, I'd look.

[Tim E. Sneddon]

Post by Bob Koehler

Post by Michael Moroney
I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed.

I heard that, too.

This is true. In fact, the input files necessary to successfully
translate TECO where generated from the TECO source by TECO
macros. I believe Larry Kilgallen was involved in that.

Post by Bob Koehler

Post by Michael Moroney
And the VESTed image was later AESTed to Itanic.

I had not heard that, I thought they managed to go back and rework
the Macro-32. If I had an IA64, I'd look.

No. TECO is definitely translated on I64 too. It runs pretty
quick now.

Tim.

[John Santos]

Post by Tim E. Sneddon

Post by Bob Koehler

Post by Michael Moroney
I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed.

I heard that, too.

This is true. In fact, the input files necessary to successfully
translate TECO where generated from the TECO source by TECO
macros. I believe Larry Kilgallen was involved in that.

Post by Bob Koehler

Post by Michael Moroney
And the VESTed image was later AESTed to Itanic.

I had not heard that, I thought they managed to go back and rework
the Macro-32. If I had an IA64, I'd look.

No. TECO is definitely translated on I64 too. It runs pretty
quick now.
Tim.

Is there a new TECO for I64 lurking somewhere? I'vee got V8.3 (not 1H1)
with all patches, more or less, and TECO still dies with a register dump
if you search for something that's not there. (And lots of other
"errors" also kill it.) I submitted this as an SPR years ago, and got
"TECO is not supported and it's not surprising it doesn't work,
considering all the VESTing and AESTing..." as a response. Not very
happy about that, but I do have clustered Alphas and VAXes to fall back
on.

[Tim E. Sneddon]

Post by John Santos

Post by Tim E. Sneddon

Post by Bob Koehler

Post by Michael Moroney
I'm not sure it even gets that. I once heard that the code (in Macro-32)
is so convoluted it wasn't ported to Alpha but just VESTed.

I heard that, too.

This is true. In fact, the input files necessary to successfully
translate TECO where generated from the TECO source by TECO
macros. I believe Larry Kilgallen was involved in that.

Post by Bob Koehler

Post by Michael Moroney
And the VESTed image was later AESTed to Itanic.

I had not heard that, I thought they managed to go back and rework
the Macro-32. If I had an IA64, I'd look.

No. TECO is definitely translated on I64 too. It runs pretty
quick now.
Tim.

Is there a new TECO for I64 lurking somewhere? I'vee got V8.3 (not 1H1)
with all patches, more or less, and TECO still dies with a register dump
if you search for something that's not there. (And lots of other
"errors" also kill it.) I submitted this as an SPR years ago, and got
"TECO is not supported and it's not surprising it doesn't work,
considering all the VESTing and AESTing..." as a response. Not very
happy about that, but I do have clustered Alphas and VAXes to fall back
on.

There is a patch kit in the works for TIE and AEST in general. I
have no idea when that is supposed to come out, but I believe it
will be soon.

Tim.

[Bob Koehler]

Post by John Santos
I submitted this as an SPR years ago, and got
"TECO is not supported and it's not surprising it doesn't work,
considering all the VESTing and AESTing..." as a response.

You mean TECO is not specificlaly called out in the SPD anymore?
Horrors.

[Richard B. Gilbert]

Post by Jerry

Post by V***@SendSpamHere.ORG
Wow. What a morning eye-opener and before I even had a chance to
take my first sip of coffee too...
In my email that arrived during the sleep phase was an email from
Andy Goldstein announcing his retirement. Effective June 5 and co-
inciding with Sue's departure. :(
Good luck in your retirement Andy. Thanks for your years of work
on the best operating system in the known universe.
Will the last person out of VMS Engineering please turn off the
lights?
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
http://www.quirkfactory.com/popart/asskey/eqn2.png
"Well my son, life is like a beanstalk, isn't it?"

Any word on who will be maintaining TECO? :)

T. Rex? ;-)

[patrick jankowiak]

Post by Jerry

Post by V***@SendSpamHere.ORG
Wow. What a morning eye-opener and before I even had a chance to
take my first sip of coffee too...
In my email that arrived during the sleep phase was an email from
Andy Goldstein announcing his retirement. Effective June 5 and co-
inciding with Sue's departure. :(
Good luck in your retirement Andy. Thanks for your years of work
on the best operating system in the known universe.
Will the last person out of VMS Engineering please turn off the
lights?
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
http://www.quirkfactory.com/popart/asskey/eqn2.png
"Well my son, life is like a beanstalk, isn't it?"

Any word on who will be maintaining TECO? :)

Sue told me about her departure. The whole thing is rotten. She didn;t
say that or anything like it at all, but I'm saying it.

Good luck Andy, I met you a couple times at DECUS. Thanks for an o/s
that's fearlessly unbroken.

Sue, pls. keep in touch,

Patrick J.

[Elliott Roper]

In article
<41cb8a23-2086-4f0e-a95d-***@i28g2000prd.googlegroups.com>,
Jerry <***@gmail.com> wrote:


<snip>

Post by Jerry
Any word on who will be maintaining TECO? :)

I like to thank that, like in "The Adolescence of P1", one day someone
far in the future will type:-

make love

and get
? Not War ?

or
hkekex$$

and the world shuts down.

Thanks Andy, and thanks from the the nerve endings in my left pinky.