test-drb

test-drb@ccmp.vtda.org

101090 discussions

Start a nNew thread

GT-40 etc.

by aek＠bitsavers.org

this is going to go for an insane amt of money https://www.ebay.com/itm/232628720694

8 years, 7 months

Yet More S-100 stuff from Sellam's collection listed for sale

by sellam.ismail＠gmail.com

Hello again, Folks! I've listed yet another batch of S-100 goodies: http://www.vcfed.org/forum/showthread.php?61192-Sellam-s-S-100-Hardware-Sof… The latest batch includes a new Processor Technology kit, a BYT-8 front panel, a Commodore PET to S-100 interface board, a couple Wameco backplanes, a gaggle of Cromemco boards, and much more. Thanks! Sellam

8 years, 7 months

Reviving ARPAnet

by jnc＠mercury.lcs.mit.edu

> From: Lars Brinkhoff > - Multics NCP has not been located. Really? It wasn't in the code dump at MIT? > - Unix? For V6 NCP, we have several versions: http://minnie.tuhs.org/cgi-bin/utree.pl?file=SRI-NOSC http://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6 (The latter includes NCP as well as TCP/IP.) > - VMS? I'm not sure a VMS machine was ever on the NCP ARPANet? Hmm, looking at a 'Hosts' table from 3-Mar-82 (NCP was only turned off in January of '83), I see two machines with "xxx-VMS"names, and directly connected to IMPs, _but_ no OS is given. So maybe they were front-ended somehow? > Does anyone have any host tables between 1975 and 1981? There's a July '77 one at the end of this: http://www.walden-family.com/dave/archive/bbn-tip-man.txt and a January '79 copy of the MIT-SAIL one at the end here: https://tools.ietf.org/rfc/rfc752.txt Starting around '82, they are more common: stick a phrase from the header of the above into the "this exact word or phrase" box in Google's Advanced Search, and you get things like this: http://pdp-10.trailing-edge.com/BB-H137D-BM/06/new-system/hstnam.txt.html https://trac.common-lisp.net/mit-cadr/export/274/trunk/lisp/chaos/hosts.text Noel

8 years, 7 months

New TestFDC Results Registry

by systems.glitch＠gmail.com

I'd been trying to reach Dave Dunfield with new TestFDC results since apparently August with no results. So, I wrote a new TestFDC registry into my site: https://services.theglitchworks.net/ng/testfdc_results This registry currently includes Dave's last registry update from 2007. There's now a form for entering your results, you can find it as a link >from the registry, or here: https://services.theglitchworks.net/ng/testfdc_results/new Result submissions have to be manually approved currently so that the registry doesn't get spammed. Text export forthcoming. Any suggestions welcome! Moderators, if someone wants to sticky this (here or in other forums), I think this would be a valuable resource for anyone wanting to use ImageDisk on non-PC formats. Thanks, Jonathan

8 years, 7 months

Reviving ARPAnet

by jnc＠mercury.lcs.mit.edu

> From: Warner Losh > I'm curious: does it inter-operate with modern TCP/IP implementations? This just a guess, but 'sort of'? It _is_ TCP/IPv4, so it's got compatible headers, but I don't know if other parts have changed enough to make it not work. E.g. it probably only supports class A addresses, for instance, which is going to influence the code for picking the first-hop router. Also, the only driver is, IIRC, for an ARPANET interface. Noel

8 years, 7 months

IP address classes vs CIDR (was Re: Reviving ARPAnet)

by spacewar＠gmail.com

On Thu, Jan 18, 2018 at 10:39 AM, Grant Taylor via cctalk < cctalk at classiccmp.org> wrote: > I was not aware that there was code that supported /only/ Class A (/8) > addresses and /not/ Class B (/16) or Class C (/24) addresses. > > I /thought/ that everything was either classful (as in supports all three > classes: A, B, and C) or classless (as in supports CIDR). > Years ago I added a configurable "bozo-arp" feature to the Telebit NetBlazer router, which would respond to ARP requests for non-local addresses and reply with the router's MAC address (on that interface), specifically in order to make classful-only hosts work on a CIDR network. Later someone paid me to write a NetBSD daemon ("anyipd") to do the same thing, though for an entirely different reason. Recently I've needed that functionality on Linux, as I have multiple old systems that only understand classful, including the AT&T UnixPC (7300 or 3B1). I suppose I should rewrite and open-source it.

8 years, 7 months

Reviving ARPAnet

by jnc＠mercury.lcs.mit.edu

> From: Grant Taylor >> It is TCP/IPv4, so it's got compatible headers > Are you referring to the 802.3 Ethernet (vs Ethernet II) frame type No, I meant the IP and TCP headers. Those are end-end; the Ethernet stuff is just a local wrapping, and can be substituted. > I was not aware that there was code that supported /only/ Class A (/8) > addresses and /not/ Class B (/16) or Class C (/24) addresses. > I /thought/ that everything was either classful (as in supports all > three classes: A, B, and C) or classless (as in supports CIDR). > Is my networking history missing something else? Yes. There was a stage before A/B/C. See RFC-760. > Please clarify ... what you mean by ARPANET interface? Are you > referring to host specific hardware that was used to communicate > with an IMP? Basically, yes. The ARPANET supported several different kinds of interfaces between the IMPs (the switching nodes in the ARPANET) and hosts, but the 'usual' one was either 'Local Host' (LH) or 'Distant Host' (DH) which were _basically_ identical except at the very lowest level - LH was TTL, and DH was differential pair. Those interfaces were a custom bit-serial thing with a handshake (with "there's-your-bit", "ready-for-next-bit" lines, etc); see BBN Report #1822: http://www.bitsavers.org/pdf/bbn/imp/BBN1822_Jan1976.pdf So the "ARPANET interface" in the host is a piece of custom hardware (some were DMA; I also used one which was interrupt per byte) which went on the host, which talked 1822 (as it was called), of either the DH or LH physical form. (There was also an Host/IMP interface called VDH, but that used a modem, and a _lot_of software; see here: https://en.wikipedia.org/wiki/Talk:Network_Control_Program#Layer_locations for a bit more about it.) > Do the necessary emulators support the ARPANET interface? Dunno, but they shouldn't be too hard to add. The real problem is going to be 'what do you hook the simulated ARPANET interfaces up to, and how'? I know they have IMP code running in simulators: http://mailman.trailing-edge.com/pipermail/simh/2013-November/007672.html but I dunno how one would hook _that_ simulation up to a simulated host running a simulated ARPANET interface. Easier, to get this old TCP/IP running, might be to write a Unix V6 driver for an Ethernet card (one the simulators do support - I know Ersatz-11 does the Interlan NI1010A/2010A, which is nice and simple) and write an Ethernet network interface module for that TCP, which talks to said driver; i.e. just replace the ARPANET interface stuff completely. Noel

8 years, 7 months

help id a chip

by billdegnan＠gmail.com

Can someone tell me what chip this is? http://vintagecomputer.net/pictures/2017/Objects/P1010114.JPG http://vintagecomputer.net/pictures/2017/Objects/P1010093.JPG http://vintagecomputer.net/pictures/2017/Objects/P1010094.JPG (note ..94/94 show the item in a sealed in storage material) the underside consists of 4 sets of 12 pins plus the corner 3 pins, as shown on the top of the chip. thanks

8 years, 7 months

DL10 documentation

by jnc＠mercury.lcs.mit.edu

> From: Lars Brinkhoff > Richard Cornwell wants to implement DL10 for his KA10/KI10 simulator, > but he doesn't have any documentation for it. Any leads? Well.... The "decsystem10 System Reference Manual (DEC-10-XSRMA-A-D) - available online: http://bitsavers.org/www.computer.museum.uq.edu.au/pdf/DEC-10-XSRMA-A-D%20D… has a definition for the -10 side of the interface on pages C-21 and following (page 365 of the PDF). It just specifies the I/O instructions and bits, there's no description of how it works. Still, that will help understand code that uses it; the complete ITS code is available. I couldn't find anything on the PDP-11 side of the interface; ITS' IOELEV > does define a "DLXCSR", and the bits in it, but ... it seems to be a memory location, not a register? The DL10 was used in two DEC system products, the DC76 Asynchronous Communication System, and the DN87 and DN87S Universal Communication System Front Ends. I couldn't find any documentation on the former, but complete prints for the latter are available: http://www.bitsavers.org/pdf/dec/pdp10/periph/MP00068_DN87_Universal_Comm_S… http://www.bitsavers.org/pdf/dec/pdp10/periph/MP00109_DN87S_Universal_Comm_… It includes a complete set of prints for the DL10. From this, and also from: http://pdp-10.trailing-edge.com/bb-d549g-sb/01/boot11.mem.html it appears that the PDP-11's connected to the DL10 have a special console which has a cable which goes to the DL10 which allows the PDP-10 to start and stop the PDP-11; the PDP-11's UNIBUS runs into the DL10 and is plugged into the DL10. Anyway, it's going to be some hard work to create a DL10 programming manual >from those dribs and drabs, but there is enough info there that it can be done. Noel

8 years, 7 months

Convergent AWS machines (formerly Sold on eBay: Convergent Technologies S/50 a.k.a. Unix PC, AT&T 3B1 Unix Workstation)

by microtechdart＠gmail.com

Alan, my apologies for the confusion here. The email subject still said S/50, but I believe we had switched topics mid-thread. On Mon, Jan 15, 2018 at 6:16 AM, dwight <dkelvey at hotmail.com> wrote: > Years ago, we used one of the Convergent machines. I recall playing rats > on it. It had a green screen. It was a 8086 processor and had some > Multibus slots in it. > I was replying to Dwight with a link to my AWS machine when Dominique chipped in with the Burrows comment. I believe that Dominique was referring to my AWS that I show at http://mightyframe.blogspot.com/2017/03/convergent-technolog ies-workstation.html And I agree with you wholeheartedly on your points. They look nothing alike, and are based on totally different processors. |Alan Perry via cctech <cctech at classiccmp.org> | |As I mentioned elsewhere, I worked on software for them at Burroughs ('86-'89). I |picked up a bunch of B25 stuff in '03, but I could never find any software for |them. In retrospect, I wish that I has stashed away B25 (and B1000 (I was one |of the last people in the office supporting software onthe B1000)) stuff, rather |than return everything, when I left the company. | |alan That's very cool that you worked on the software. And, yes, Alan, agreed about wishing to keep a few of them around...But, I may be able to get the one that I have running soon. I'll be working on it on and off this year. I plan on trying trying to restore the Convergent CTOS on this, rather than the Burroughs BTOS, at least at first anyway... I'll keep you posted here on my progress on that. Thanks, all! Best, -AJ On Wed, Jan 17, 2018 at 11:02 AM, Alan Perry via cctech < cctech at classiccmp.org> wrote: > Are you sure? > > The B20, B21, B22 looked like this - http://www.computerhistory.org > /collections/catalog/102662660 - and nothing like the 3B1 or the S/50. > The B25 and subsequent models (which are often referred to as B20s) are > modular systems that are box-shaped and got wider as "slices" were added. > The B20s were x86-based and the 3B1 (and presumably the CT S/50) was > 68k-based. > > alan > > > On 1/17/18 2:41 AM, Dominique Carlier via cctech wrote: > >> It's interesting, I had exactly the same machine a long time ago, but >> with a different label. It was a Burroughs B20 distributed by Unisys >> >> Dominique >> >> On 17/01/2018 06:45, AJ Palmgren via cctalk wrote: >> >>> Did it happen to be one of these older-style Convergent AWS machines? >>> >>> http://mightyframe.blogspot.com/2017/03/convergent-technolog >>> ies-workstation.html >>> >>> >>> > -

8 years, 7 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

test-drb