Al 28/11/12 22:47, En/na Paul_Koning at Dell.com ha escrit:
Is Pi big endian? Does KLH10 assume little endian?
Pi is little endian. And, to add some weirdness to this, I have just completed a TOPS-20 boot using the very same binaries...
(It does not use klboot.exe)
Is Pi big endian? Does KLH10 assume little endian?
paul
On Nov 28, 2012, at 4:44 PM, Jordi Guillaumes i Pons wrote:
Al 28/11/12 22:42, En/na Cory Smelosky ha escrit:
Anyone has gone past this?
I've not, but is it possibly related to solftfloat versus hardfloat ABI in some distr
I have built it from sources... I don't think the ABI differences can make any difference. But I could be wrong if KLH10 uses something really tied to the host hardware.
Al 28/11/12 22:42, En/na Cory Smelosky ha escrit:
Anyone has gone past this?
I've not, but is it possibly related to solftfloat versus hardfloat ABI in some distr
I have built it from sources... I don't think the ABI differences can make any difference. But I could be wrong if KLH10 uses something really tied to the host hardware.
On 28 Nov 2012, at 16:40, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
I have compiled KLH10 in the Pi, following the indications in this post:
https://groups.google.com/forum/?fromgroups=#!topic/alt.sys.pdp10/vHcQ49tjM…
After correcting a stupid syntax error I get a mostly clean compilation, but when I try to run TOPS-10 on it (cloning a configuration that works in an intel machine), I get this:
KLH10# load klboot.exe
Using word format "c36"...
Loading aborted, read failed for file page 1, proc page 0
Loading aborted, read failed for file page 2, proc page 448
Loading aborted, read failed for file page 4, proc page 451
Loaded "klboot.exe":
Format: DEC-PEXE
Of course it does not boot...
Anyone has gone past this?
I've not, but is it possibly related to solftfloat versus hardfloat ABI in some distros?
I think you are describing the 3B20S. Looked like a VAX/780 (but had a pull starter ;) for the battery bring up. The duplex 3B20D was the control systems for the 5ESS. After the consent decree was dropped, AT&T tried to market the S (simplex) version as a general purpose computer. IIRC the 3B20 >>architecture<< became the WE32100 microprocessor that was used in the desktop machines.
Clem
On Wed, Nov 28, 2012 at 4:24 PM, Boyanich, Alastair <Alastair.Boyanich at au.fujitsu.com> wrote:
> Hello!
> He's thinking of the WE designed processors that were used in the
> later units. They were not bit slice but were fabricated using the
> normal methods. Not surprisingly enough the devices could not even be
> sold separately.
>
> They were ran an appropriately written release of UNIX as native. One
> of the first applications for them and the later models was in running
> the first and second generation Electronic Switching Services
> otherwise known as exchanges.
>
> There's a whole article online someplace on the RT extensions that
> needed to be written out and added to UNIX for that application.
Hi Greg,
Maybe it wasn't bit-sliced then.. interesting, but this seems to fit as
it was definitely:
a) a different ISA to the m68k stuff. Wouldn't even disassemble.
b) telco gear for very large PABX/exchange switching/management
c) UNIX (tm) based.
Al.
On 11/28/2012 04:20 PM, Boyanich, Alastair wrote:
The "UNIX PC" is the 7300, which is nearly identical to the 3B1.
The
3B1 has a slightly larger top cover to accommodate a full-height hard
drive, while the 7300 will only hold a half-height drive.
They are otherwise identical, using 68010s.
Okay. I've seen one of the 68010 jobs and repaired the psu for a friend
in the early 90's with a discard he'd taken home from work. It's all
pretty vague as this was about 1993, 1994.
I'd sure like to know more about the "proprietary cpu" version
you're
talking about.
Same guy had some "other" VME (Might not've been.. was rack mount and
telco power) AT&T gear at work that I saw a couple of times.
There was at least one VME-based WE32K processor, but most (all?) of
the 3B line (which does NOT include the 3B1) was very much "its own thing".
Moved a
couple of bin's off the system and tried to get it running on the m68k
system he had at home which didn't work. We were pretty in the dark
about these things and doco was scarce and assumed that "AT&T meant they
were compatible".
Not even close. ;) AT&T built computers with a dozen different
processors...if not more...over several decades. AT&T is a BIG company.
The idea behind the home machine was a learning
exercise, fiddle system for home. Old guy that managed a lot of the
esoteric stuff at his work said when we questioned the incompatibility
said "of course not. It's older than the m68k workstation, and it's all
micro-coded off bit-sliced CPU's". Maybe it wasn't? Either way, the rack
stuff's binaries were not runnable on the SysV r3.5 m68k jobs.
It was probably 3B2-family WE32K stuff. Not bit-slice though.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
SS1 and SS1+, maybe sme SS5 also, and got some IPC/IPX on another location
Any of the 1/2/IPX systems have the 80Mhz Weitek SPARC PowerUP! Chips and SBUS ram cards? If so, they make a very nice little hobby machine.
Al.
Hello!
He's thinking of the WE designed processors that were used in the
later units. They were not bit slice but were fabricated using the
normal methods. Not surprisingly enough the devices could not even be
sold separately.
They were ran an appropriately written release of UNIX as native. One
of the first applications for them and the later models was in running
the first and second generation Electronic Switching Services
otherwise known as exchanges.
There's a whole article online someplace on the RT extensions that
needed to be written out and added to UNIX for that application.
Hi Greg,
Maybe it wasn't bit-sliced then.. interesting, but this seems to fit as
it was definitely:
a) a different ISA to the m68k stuff. Wouldn't even disassemble.
b) telco gear for very large PABX/exchange switching/management
c) UNIX (tm) based.
Al.