On Jun 24, 2016 1:11 PM, Jay West <jwest at classiccmp.org> wrote:
>
> Mike wrote...
> -----
> ??? HP 262x terminals don't ship well.? The "ET" terminals must be packed
> carefully.
> ----
> That is very true. I could use one of those large black plastic pieces that
> hold the monitor open. Mine broke'ted.
>
If you have the broken pieces and or a complete one I could possibly model it and 3D print it depending on size...
We have the technology ;)
-Connor K
This thread reminded me that I recently got shipped what the person told me
was a CDC 6000 Central Memory core.
(it matches what's on this page :
http://www.museumwaalsdorp.nl/computer/en/6400hwac.html ). He told me that
the console looked like this :
http://research.microsoft.com/en-us/um/people/gbell/craytalk/sld031.htm
I got it along with a box other parts (mostly Sun things) and a single
"plane" of core memory from another module.
(It connects the 6000 to the Sun 1's that I picked up in the past... some
interesting history...good "over a beer" stories :-) )
I'm coming to VCF MW this year so if there is interest, I can bring it
along...
Earl
Spotted this at a local surplus place today. it's an acoustic coupler/modem,
white plastic case, manufacturer is "MI2" (with the 2 as a superscript, so I
guess "MI Squared"). Never heard of them.
No clue if it works, appears to be in fair condition, they have a price tag
of $25 on it.
J
You guys must have much larger apartments (or houses I'm guessing) than
me.... I would really like a vt220 largely because it seems like it
wouldn't occupy much space. I'm guessing they withstand shipping better too.
--
Greg
Someday I want to have a PDP11 even if it is a QBUS version
I can get a clean RX02 for about $150. When my life involved PDP11's
starting with 34A and ending with 44's I never used one.
-pete
Heh! Especially if an upper case only terminal
I can just imagine the cry arising from the little whiners!
QUIT SHOUTING QUIT SHOUTING!
(as they stamp their feet and rent their clothing....)
In a message dated 6/24/2016 7:50:46 A.M. US Mountain Standard Time,
emu at e-bbes.com writes:
On 2016-06-24 08:23, Swift Griggs wrote:
> However, I think most folks these days would faint if they were forced to
> work on a terminal.
Just don't tell them, that they do ;-)
If you really think about it, the terminals just got faster and
got more colors. (and you call them smartphone, thin clinet, tablet, win
PC, ...)
Otherwise:
a.) most data is somewhere in the cloud (before it was called mainframe)
b.) a lot of applications are running in the cloud (before, mainframe)
c.) you connect now via wireless internet (before: modem)
d.) ...
So, just Emperor's new clothes ;-)
To my sorrow, I'd never heard of the CDC 6600 and I barely knew who
Control Data was (whippersnapper, I know). I see a lot of traffic about
them on the list and I went out to discover "why so cool?" Wikipedia and
other spots talk about the features, but I'm trying to understand from
folks who put hands to the metal, why they liked them so much.
I'm a total igmo concerning this bit of kit. Is this about right?
- It has dual "calligraphic" displays. Geeze! Very freakin' cool
- It was RISC nearly before folks could even articulate the concept
- It had some wicked cool "demos", to cop a C64 term. (ADC, PAC, EYE)
- It wasn't DEC and it wasn't IBM and it was faster than both when it hit
the street?
- It has a cool OS? Dunno. Not much info on "SCOPE"
- Made in the USA baby! Back when we actually made things.
- It used odd sized (by todays standards) register, instruction, and bus
sizes. 60 bit machine with 15/30 bit instructions. But, didn't it cause
a bunch of alignment issues for you ?
I dug into the CPU instructions for about 20 minutes and it was actually
pretty straightforward. The so-called "COMPASS" ASM code was oh-so-cool. I
can't believe they had so many of the features now considered "modern" or
"clever" (at least by me) in the 1960s! This code:
https://en.wikipedia.org/wiki/COMPASS/Sample_Code
... Is super-readable, in fact, probably a bit more than several
much-newer dialects on different platforms. There was one instruction
"PROTECT" I found pretty interesting, too. Was that similar to noodling
with the control registers CR0, CR2, CR3, and CR4 on x86 to mark memory
protection from segmentation violations? I remember that being the
protection mechanism on my 386 SX/16 (and I remember it being a PITA),
however the COMPASS "way" looks much easier/cooler and must have some
hardware assistance to do that so easily.
-Swift
I have been going through our library of documentation and found some items
that are duplicates.
There are a LINC-8 programming manual, PDP-8 DecTape programming manual,
PDP-8/L maintenance manual, PDP-8/e maintenance manual volume I and volume
III.
http://i.imgur.com/YEAdnZV.jpg?1http://i.imgur.com/pvsypvY.jpg?1
Trade for something interesting!
Other things that is also for trade:
http://www.datormuseum.se/available
/Mattis
> On Jan 3, 2016, at 4:56 PM, Paul Koning <paulkoning at comcast.net> wrote:
>
> ...
> This Forth implementation is a port of Fig-FORTH by John S. James, with some RSTS-specific magic added. I just realized the file header says that it is in the public domain, so I suppose I should post the source...
Done. Thanks to Al Kossow, it now lives on Bitsavers, in bits/DEC/pdp11/forth/forth.mac
This is the RSTS run-time system, from V9.6 and later. I haven't tried building it on older versions; the comments say it works back to V7.2. I don't remember why that version is mentioned. Run time systems existed before then, though a few details did change over time.
The original version was for RSX and RT-11. I did the RSTS port, and Kevin Herbert added some more stuff to it later on. The biggest change is to make the vocabulary machinery match the ANSI Forth 83 standard, which allows for lots of separate vocabularies and arranging their search order. This was needed to allow SDA to define a set of 32 bit replacements for the standard (16 bit) arithmetic operators of native Forth, without getting itself all confused.
Build instructions are in the comments near the top of the file. There's very little to it.
Enjoy.
paul