If anyone is interested in anything listed below, or any DEC parts, please
let me know ASAP and I will try to have them tested and loaded for the trip.
SZ12 expansion box
PE32A-BD DEC 3000/300X
PE40A-B9 DEC 3000/400 ( I HAVE TO FIND A CPU FOR IT)
DEC 3000/400?
VAXSTATION 3100/76 SPX
MICROVAX 3100 KA41
3100 DV31CT2-A
VAXSTATION 4000 60
DECSYSTEM 5000/25
3EA 5000/125
5000/133
2EA 5000/200
I have more in another location and will try to find them later today.
I have a lot of extra boards for the above boxes, mostly for the 5000s and
I am still looking for them.
I have VAX CPU and memory boards for the BA23, and the BA213s boxes. Also
"S" box boards and panels.
TONS of Q-bus, Unibus, and some PDP8 boards.
Robins, Rainbows, DECmates, PROs, and parts
Now it gets weird. I have about a dozen or so brand new CRTs for VT330s.
I'm sure they were used in other terminals, but I have no idea which. I
should have all 3 colors.
Also an OMEGA B22, DII and Bessler enlarger and a ton of darkroom
equipment, audio gear including mixers.
Thanks, Paul
https://devin.ai/cli
Not exactly the image I'd expect to see on a webpage advertising shiny new technology. It even shows that application running on the VT100 (simulated, but the evidence for that is pretty subtle).
Fun.
paul
Hello again,
Yes, this time I am trying to figure out what I'm doing wrong while
creating a C program.
It is still in RSX11M+ on my 11/23+ and PDP-11 C 1.1.
I have a really simple test program like this:
+>type test.c
#include <stdio.h>
main() {
puts("Hello, world!");
}
The following is what I do to compile and task build:
+>type tstbld.cmd
.IFNINS MAC INS $MAC
.IFNINS TKB INS $TKB
PIP TEST.C/PU,TSTBLD.CMD/PU,TSTTKB.CMD/PU
CCC TEST.C
TKB @TSTTKB.CMD
PIP TEST.OBJ;*/DE
PIP TEST.TSK/PU
+>type tsttkb.cmd
TEST/-FP=TEST,LB:[1,1]CFPURSX.OLB/LB
/
UNITS=1
ASG=TI:1
TASK=...TST
LIBR=FCSFSL:RO
/
The code compiles fine and TKB has no issues. I get my test.tsk:
+>dir test.tsk
Directory DU0:[200,2]
2-SEP-2026 21:36
TEST.TSK;2 22. C 02-SEP-2026 21:30
Total of 22./22. blocks in 1. file
I run it as '+>run test' and I just get the prompt back. I expect it to
print to the terminal.
What am I missing? Nothing stands out to me in the manual. I'm sure it's
something stupid.
Any pointers would be greatly appreciated.
- Peter
Yes, I did early development on both. At least the interface to the OS was Pascal. I still have the early documentation buried in a box somewhere.
Sent from my iPhone
> On Jun 20, 2026, at 2:02 PM, Fred Cisin via cctalk <cctalk(a)classiccmp.org> wrote:
>
> On Sat, 20 Jun 2026, ben via cctalk wrote:
>> PL/1 and C are the only two high level languages a operating system is written in, that I can think of that are well documented, and easily found on the WEB.
>
> I heard that all of the Lisa OS, and much of Macintosh, were written in Pascal. (obviously other than some low-level drivers and performance critical routines?)
> Is that correct?
>
> http://pascal.hansotten.com/apple-lisa-pascal/
>
> When did Macintosh development switch to C?
>
> --
> Grumpy Ol' Fred cisin(a)xenosoft.com
Not my auction etc etc but I believe these are hard to find. Also fits
HP500A and maybe B logic analyser (500C used PS/2).
https://www.ebay.co.uk/itm/297932090059
Hey gang, a few months ago I presented about timeshare and some aspects
about operating systems since the 1950s.
To buzz through a PDF or PPT version of the notes:
https://github.com/voidstar78/VCF2026
VCFSW has the talk archived here:
https://www.youtube.com/watch?v=9hE235ti9XQ
Sorry being a bit dull as a speaker, but a few highlights:
- overview of Douglass Ross "Director Tape" for Whirlwind (only "what it
looked like" evidence that I was ever able to find, would be curious if
others knew more about it)
- 1965 Honeywell ADMIRAL OS: while I couldn't find much info about that
specific OS, what I did find what Honeywell went to bat for us all vs RAND
corp, putting an end some concerns about ENIAC hardware patents (that's a
very short version of it)
- today we fight about \ vs / slashes, when MULTICS split the difference
and used > (greater than symbol), at least as far as I could tell from the
manuals
- some verification that UNIX was (sort of) originally called UNICS (see
footnotes in the PPT notes), never formally written down but "verified" in
the past year
- I made a claim that Datapoint CTOS (1972) was the only OS ever on a
cassette tape (not to be confused with the late 1970s CTOS) - that said, I
suppose the MCM/70 did as well; really admires Mattis Lind's work on the
DP2200
I never found too much info about "tymshare" (apparently a late 1960s kind
of "corporate or business-to-business digital exchange" system, maybe for
inventory or check-processing?).
Tons of other OS's, obviously couldn't cover them all in a VCF talk. But
there are a bunch of addendum notes after the end of the slides:
- Mike Muuss ENIAC archive (at a .mil ftp if anyone wants to archive it
more properly?)
- I still claim that the word "operating system" was never used before
1960; the "SOS" or "share OS" was a name applied later (1962ish) to those
pre-1960s concepts [ afaik ]
- I couldn't fit in a bit about squozed :) really wanted to, just couldn't
make it fit
- AOSP, EXEC II, IBM 1800 derivatives (anyone ever see one of these in
the wild?),
Oh, not officially launched yet, but I'm now self hosting oldsayings.info
(with a telnet front-end at port 42525). Kicking around some ideas, but
it's reliably staying up now with Starlink as the ISP. I got tired of
waiting for fiber - but the county workers are getting closer, I see them
running it ranch by ranch.
Cheers, wish could have made it to VCF West this year.
-Steve
There's an EAI Analog computer listed for auction on HiBid. Even has
some docs:
https://hibid.com/lot/317096364/analogue-computer-mod-185-240-eai180
It's in Australia and it's local pick up but for the right person in the
right place.....
As usual: No knowledge or relationship on my part.
Hello! Our office represents the family of a gentleman (Mr. Marsh) who passed away from mesothelioma, a cancer caused from breathing asbestos. Mr. Marsh spent his career working for a contractor that provided third-party installation and maintenance of DEC computer equipment at various customer locations. We are curious if any DEC equipment ever contained asbestos, possibly asbestos lined brakes, gaskets etc. I am wondering if anyone in this forum has personal knowledge or documentation of asbestos use in DEC equipment OR if any of you have a tape drive with a braking mechanism that we can test for asbestos content? I can be reached via email or on my cell phone (925) 639-8593 with your thoughts. Thank you for your time!
Regards,
Jennifer Manibusan
Legal Investigator
Maune Raichle Hartley French & Mudd, LLC
1900 Powell Street, Suite 200
Emeryville, CA 94608
(925) 639-8593 Cell
(314) 241-2003 Office
This communication may be attorney-client privileged or otherwise confidential. If you are not the intended recipient, please delete this message and notify the sender of this error.
