- cctalk - classiccmp.org

by Paul McJones

As a matter of fact, I had already sent Scott an email, but did not get a reply. > Date: Fri, 26 Jun 2026 08:57:24 -0400 > From: Ken Seefried <seefriek(a)gmail.com <mailto:seefriek@gmail.com>> > Subject: [cctalk] Re: Looking for a paper in COMPCON '83 > > You might reach out to the authors. I'm pretty sure S.B. Baden is Scott > Baden @ UCSD. > > https://cseweb.ucsd.edu/~baden/ > > KJ

2 months

1
0
0 0

Looking for a paper in COMPCON '83

by Paul McJones

I’m trying to get a copy of this paper: S. B. Baden and D. R. Patel. “Berkeley FP — Experiences with a Functional Programming Language. Conference Record of COMPCON ’83, San Francisco, California, pp. 274–277, March 1983. and wonder if anyone on this list has a copy of the proceedings? The source code is available in the tuhs.org archives and the manual is available in the supplementary documentation for BSD 4.2, but I am interested in what the author wrote about their experiences. (I’m working on a history of John Backus’s functional programming project; Berkeley FP is based on Backus’s work.) Paul McJones

2 months

3
2
0 0

Harold S. Stone, Please contact Jeffrey Worley

by Jeffrey S. Worley

This is irregular, and I beg your indulgence, as it at least in light of the recent Alpha EV6 discovery. I have a story to tell you Mr. Stone, that you will be very glad, amazed and fulfilled to hear and to know. This is not the forum for such things, but I am a very little person and could not hope to reach you in any other way. Thank you gentlemen for your forbearance. I ask further of you even, if you know Harold S. Stone, the author of High-Performance Computer Architecture, please ask him to message me on facebook or call me. I'm not hard to find, I'm @Technoid_Mutant on Youtube... Again, my thanks. Jeff

2 months

1
0
0 0

Compuwriter IV Going for Cheap

by Cory Heisterkamp

Too far north for me, but hopefully it doesn't get scrapped out. No relation. -C https://bid.schmalzauctions.com/Vintage-The-CompuWritter-IV_i60266313

2 months

2
1
0 0

System/38 update

by Joe George

We've been working on restoring and powering up a fairly rare bird of IBM Midrange machine, the IBM System/38. We had some good success this past weekend that I'd like to share. https://crusty.computer/?p=89 June Work Recap: Edith – The Crusty Computer Club crusty.computer tl;dr: she powered up and no smoke came out and no sparks came out! There are several repairs needed but they are known and fixable.

2 months

4
4
0 0

Intel 3086

by Murray McCullough

Intel's x86 technology as in the 8086 came into existence for the microcomputer-user at this time back in June 1978. It was a response to Motorola's and Zilog's move to 16-bit processing. Still in use today...the basic tech so to speak. Can it be unseated by RISC(Apple and such) and Nvidia? Happy computing. Murray 🙂

2 months

42
156
0 0

Burroughs DCALGOL vs tapes [from dead computer language thread]

by paul.kimpel＠digm.com

Yes, DCALGOL is still around and actively used. It is a superset of the standard Extended ALGOL, and originally exposed some special APIs and data types for talking to the Datacom Processor front-end. Those APIs are still used, although the "front end" is now TCP/IP. The language has since been extended with numerous other APIs for use primarily by system-programmer types. There is also a DMALGOL compiler primarily used internally with the DBMS, DMSII. All three ALGOL variants have been compiled from the same source code since sometime in the '70s. DCALGOL would have been no different than ALGOL for dealing with tapes, and I'm surprised you found it harder to do with the MCP than with OS/360 EXCP I/O. Depending on the block and tape label formats, you may have had to do your own deblocking, and possibly read the tape as unlabeled, but the MCP I/O Logical I/O subsystem was quite rich even in 1975. You had to understand how the file attribute settings worked when dealing with non-native tape formats, however -- I've seen that trip a lot of people up. As an alternative, a variant of Logical I/O called Direct I/O was available, which is user-mode asynchronous I/O that reads and writes raw blocks. It's basically a thin wrapper around the MCP's internal Physical I/O mechanism. I know this is water long over the dam, but I'd be interested in hearing what kinds of issues you encountered, and if possible, a reference to the DEC formats you were trying to read.

2 months, 1 week

3
2
0 0

Re: What constitutes a dead computer language

by Mark Kahrs

As a fan of BCPL (from the Alto), I only wish it was better documented. For example, Tripos has next to no documentation on it including how to compile and load it. Documentation on the runtimes is also lacking (and that's where the rubber meets the road). Unfortunately, the Alto changes were not picked up so it remains an isolated branch (and *dead* by the definitions put forward).

2 months, 1 week

7
8
0 0

m4 model 9914 tape drive and 800dpi 9track tapes

by Bill Degnan

I have found that a modernish Dell PC (win 7 era) when attached to a m4 9914 tape drive has issues when attempting to read 800dpi 9track tapes. I/O errors that seem to be centered around variable block size microcode of the modern scsi controller (?) I've spent a number of hours on it and I could not even pull raw data off an 800dpi tape. 1600 no problem. works fine. is there a tweener box or scsi controller that will work in this situation? what do other people do? Bill

2 months, 1 week

2
2
0 0

Re: What constitutes a dead computer language

by Paul McJones

On 6/20/2026, ben <bfranchuk(a)jetnet.ab.ca> 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. Additional examples: Pilot (the embedded operating system for the Xerox Star office automation system) was written in Xerox's proprietary Mesa language. History and documentation of Mesa (and some Pilot documentation and early source code) are available here: https://softwarepreservation.computerhistory.org/mesa/ Taos, the operating system for the DEC Systems Research Center Firefly multiprocessor workstation, was written in Modula-2+, which added threads, garbage collection, and runtime type dispatch to Modula-2. History and documentation of Modula-2+ (and Taos) are available here: https://softwarepreservation.computerhistory.org/modula2+/ SPIN, an extensible operating system written at the University of Washington, was written in Modula-3 (with small extensions). History and documentation for Modula-3 are available here: https://softwarepreservation.computerhistory.org/modula3/ and information on SPIN is available here: https://softwarepreservation.computerhistory.org/modula3/#SPIN_M3 .

2 months, 1 week

3
2
0 0

2026

2025

2024

2023

2022

cctalk