* [TUHS] Surviving System V/VME Artifacts?
@ 2025-05-01 21:01 segaloco via TUHS
2025-05-01 21:07 ` [TUHS] " Kevin Bowling
0 siblings, 1 reply; 3+ messages in thread
From: segaloco via TUHS @ 2025-05-01 21:01 UTC (permalink / raw)
To: The Eunuchs Hysterical Society
So part of Western Electric/AT&Ts developer support for the WE32x00 CPU line was
the WE321SB VME-bus single-board computer. The official operating system for
this was UNIX System V/VME. This version is referenced in several document
catalogues and literature surrounding this VME module. I was curious if anyone
on list happens to know of any surviving System V/VME artifacts floating around
out there. All I've been able to find are references to the system in other
WE32x00 and UNIX documentation.
Thanks for any info!
- Matt G.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [TUHS] Re: Surviving System V/VME Artifacts?
2025-05-01 21:01 [TUHS] Surviving System V/VME Artifacts? segaloco via TUHS
@ 2025-05-01 21:07 ` Kevin Bowling
2025-05-01 21:35 ` segaloco via TUHS
0 siblings, 1 reply; 3+ messages in thread
From: Kevin Bowling @ 2025-05-01 21:07 UTC (permalink / raw)
To: segaloco; +Cc: The Eunuchs Hysterical Society
On Thu, May 1, 2025 at 2:01 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
>
> So part of Western Electric/AT&Ts developer support for the WE32x00 CPU line was
> the WE321SB VME-bus single-board computer. The official operating system for
> this was UNIX System V/VME. This version is referenced in several document
> catalogues and literature surrounding this VME module. I was curious if anyone
> on list happens to know of any surviving System V/VME artifacts floating around
> out there. All I've been able to find are references to the system in other
> WE32x00 and UNIX documentation.
I would also be interested if anyone has ever seen that hardware. VME
stuff tends to be durable because it is used in machinery with long
lifetimes so it doesn't usually go the way of commercial computer
disappearing.
> Thanks for any info!
>
> - Matt G.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [TUHS] Re: Surviving System V/VME Artifacts?
2025-05-01 21:07 ` [TUHS] " Kevin Bowling
@ 2025-05-01 21:35 ` segaloco via TUHS
0 siblings, 0 replies; 3+ messages in thread
From: segaloco via TUHS @ 2025-05-01 21:35 UTC (permalink / raw)
To: The Eunuchs Hysterical Society
On Thursday, May 1st, 2025 at 2:08 PM, Kevin Bowling <kevin.bowling@kev009.com> wrote:
> On Thu, May 1, 2025 at 2:01 PM segaloco via TUHS tuhs@tuhs.org wrote:
>
> > So part of Western Electric/AT&Ts developer support for the WE32x00 CPU line was
> > the WE321SB VME-bus single-board computer. The official operating system for
> > this was UNIX System V/VME. This version is referenced in several document
> > catalogues and literature surrounding this VME module. I was curious if anyone
> > on list happens to know of any surviving System V/VME artifacts floating around
> > out there. All I've been able to find are references to the system in other
> > WE32x00 and UNIX documentation.
>
>
> I would also be interested if anyone has ever seen that hardware. VME
> stuff tends to be durable because it is used in machinery with long
> lifetimes so it doesn't usually go the way of commercial computer
> disappearing.
>
> > Thanks for any info!
> >
> > - Matt G.
Details about the module can be found here:
https://archive.org/details/bitsavers_westernEleocessorsandPeripheralsAug87_47936355/page/n467/mode/2up
In addition other WECo/ATTIS publications from the mid 80s describe this and
other bits like the WE321EB eval board and WE321AP analysis pod.
- Matt G.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-05-01 21:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-05-01 21:01 [TUHS] Surviving System V/VME Artifacts? segaloco via TUHS
2025-05-01 21:07 ` [TUHS] " Kevin Bowling
2025-05-01 21:35 ` segaloco via TUHS
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).