test-drb

test-drb@ccmp.vtda.org

101090 discussions

by mattislind＠gmail.com

I have now finally concluded the PDP-15 documentation scanning project. Many year ago my father saved a big lot of PDP-15 documentation that was thrown out from Philips in Stockholm. I have over the years scanned documents on request which has ended up at bitsavers. Some docuements were already present on bitsavers. Now I took a stab and finalised this project. All the remaining PDP-15 has now been scanned and I put them here: http://www.datormuseum.se/documentation-software/pdp-15-documentation Many documents already has made its way to bitsavers but many remains. There are DOS-15, XVM/DOS and various general documents such as operators guide, course handouts etc. The only remaining document to scan is the RSX PLUS III reference manual which will be tricky to scan without damage it. Happy reading!

7 years, 10 months

DG microNOVA in Cleveland on CL

by jfoust＠threedee.com

https://cleveland.craigslist.org/sys/d/data-general-free-for-good/671412126…

7 years, 10 months

Source code listings from REDAC PDP-based PCB layout system.

by mattislind＠gmail.com

I have a set of around 5 to 8 binders with printed source code listings >from a PDP-15 system. The listings appear to be from a REDAC SOFTWARE LIMITED PCB CAD system. The name of the software seems to be REDAL 3 MARK 7. There are dates on the listings in the range 74 and 75. https://i.imgur.com/m1ji9uR.jpg https://i.imgur.com/SzaiH78.jpg First of all does anyone has more info on the REDAL software from REDAC? Then secondly is there anyone interested in these binders with listings? I think the quality of printout is good enough to do OCR on. Note that there is no guarantee that these are the complete set of binders with listings. /Mattis

7 years, 10 months

Rack-mount or tabletop version of DEC RX50 floppy drive?

by spacewar＠gmail.com

Did DEC offer a rack-mount or tabletop box version of the RX50 floppy drive, as they did with e.g. the TU58 and TK50 tape drives? I'm wondering how they expected the RX50 drive to be packaged when used with a Unibus PDP-11 via the RUX50 controller.

7 years, 10 months

HP1000 A600 Boards available

by holm＠freibergnet.de

Hi, two weeks before I was asked from a friend if it's worth to rescue an HP1000 A600 computer from the stuff available at a local scrapp seller in Erfurt. Of course I've answered yes! Unfortunately someone at the scrap site has pulled some cards and at least in one case a chip fom a card. There is to much missing to rescue this computer..at least my friend has saved some of the pcb's: hier die HP-Kartennummern: 12103-60004 1MB RAM , 2x vorhanden 12005-60012 Ser. Interface 12005-60001 Ser. Interface 02430-60009 drop me a mail if you are interested on buying those cards and give a hint what you want to pay for them. The stuff is located in Weimar, Germany ..Europe. Regards, Holm -- Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, Freiberger Stra?e 42, 09600 Obersch?na, USt-Id: DE253710583 info at tsht.de Fax +49 3731 74200 Tel +49 3731 74222 Mobil: 0172 8790 741

7 years, 10 months

Ethernet names...

by w9gb＠icloud.com

Grant - Occasional vague references to ?I?, when Ethernet II was used (as I remember). I assumed the reference was for initial 3 Mbps work at PARC. Gateway Communications started in Irvine, CA (1981?) offering G/Net (~double the 3 Mbps), I remember installing their demonstration system (1982 or 1983?) By 1983, 3Com ThinNet (10-Base-2) released for IBM PCs. University of Iowa graduate college installed one of their first LANs with an Altos sever (8086, 10 MHz). greg == From: Grant Taylor <cctalk at gtaylor.tnetconsulting.net> Subject: Ethernet names... Does anybody know names / terms that correspond to the original 3 Mbps Ethernet? I.e. 10 Mbps Ethernet is also knows as Ethernet II (2) and D.I.X. (for Digital, Intel, and Xerox). Was the first 3 Mbps Ethernet simply called "Ethernet" with an implicit "I" (1)? Was there a name to differentiate it from D.I.X.? Grant. . . . unix || die Sent from iPad Air

7 years, 10 months

Ethernet names...

by jnc＠mercury.lcs.mit.edu

> From: Eric Smith > 3 Mbps was sometimes referred to as experimental Ethernet, but AFAIK > the only official name was "Ethernet". > The best way to refer to it is probably "3 Mbps Ethernet". I was trying to remember what we called it at MIT (which had one), but my memory was hazy, so I want back and looked at the sources for the packet switch I wrote (which supported the first Ethernet, before the 10Mbit version even came out), and I found (slightly to my suprise) that it was "3Mbit Experimental Ethernet", or just plain "Exerimental Ethernet". (Of course, that was just MIT - other sites may have had different terminology.) No doubt we renamed it once the 10Mbit version showed up - I can probably search for early versions of the code to confirm this, if anyone cares. Anyway, I'd vote for the latter, short name. > From: Bill Degnan > See where wizards stay up lote by Katie Halner and matthew lyon. Interesting! It looks (from the Notes) like this was gleaned from an interview with Metcalfe, and she was _very_ careful (I helped her with the technical details - you can find me in the Acks), so I'd tend to believe it. My _guess_ is that was his early, 'in his head' name for the thing, and when they set out to actually build it, it was re-named 'Ethernet' (as Al's memo search seems to indicate). Noel

7 years, 10 months

Looking for HP 1000 A990 backplane jumper board and memory frontplane

by glen.slick＠gmail.com

I have an HP 1000 A900 20-slot box with a working 4 card CPU set (sequencer, data path, cache control, memory controller). I also have a 12990-60102 A990 CPU card that would replace the 4 A900 CPU cards and install in place of the A900 memory controller card. What I don't have is the 12990-60020 jumper board that would install in the A900 backplane instead of the A900 sequencer, data path, and cache control cards, nor a 12230-60001, 12230-60002, 12230-60003, or 12230-60004 memory frontplane to connect the A990 CPU to one or more memory array cards. I'm not very hopeful, but is there any chance anyone on the list happens to have a spare HP 1000 A990 12990-60020 jumper board, and/or a 12230-60001, 12230-60002, 12230-60003, or 12230-60004 memory frontplane that they would be willing to part with? Not expecting these for free. These might be parts that 360 Technologies had before they recently closed up shop, although if they did they probably expected business critical prices for them. (For reference, the HP Museum site has a copy of the HP 1000 A990 Upgrade (HP 12990C) Installation and Service Manual, 12990-90011).

7 years, 10 months

PDP-11 in russia?

by jwest＠classiccmp.org

Someone has contacted me about a pdp-11 that controls a "measuring machine dea epsilon". It appears that they want to replace the pdp-11 with a "ibm" (I'm guessing a pc), and then they would give the pdp-11 as a gift. That is all the info I have. Are there any listmembers in Russia who would be able to take on a project? J

7 years, 10 months

6809 Monitor

by guykd＠optusnet.com.au

At 12:24 PM 2/10/2018 -0700, you wrote: >Does anyone have source to a 6809 monitor program? > >I'm looking for something I can make work in a CoCo. > >Functionality I'm looking for is something that will let me read and >write to memory. Attached is the zipped C source code for a 6809 monitor I wrote in the early 1990s. Compiler used was HiTech C. Build files included. It worked, but of course 'there may be bugs.' :) It's fairly generic, so not many changes needed for other CPUs. I also did an 80C196 ver. If the zip file attachment fails, it's online here: http://everist.org/texts/6809_Mon_V2.zip Doco from the MONITOR.C file: /* File: MONITOR.C For machine: Dual 6809 game board. Compiler: Hitech 6809 C. Written: Guy Dunphy, 4/9/94, derived from an earlier version. (by me) This file contains all code for a versatile serial monitor. It is event driven, and time sliced, so it can operate in the background with other CPU tasks. All data is stored big-endian. All serial I/O is via the functions aux_get_ch(), aux_put_ch(). Serial Tx is polled, while Rx can be either polled, or buffered interrupt driven with hardware handshaking (via RTS). See monitor_init(). This monitor can be used in multi CPU systems, where only one CPU has a serial comms interface, and each has different IO/mem maps and codespaces. If there is a means for passing strings between the CPUs, then the one with serial IO is used to run a 'master' copy of the monitor, and the other CPU(s) runs a 'slave' monitor version. The master CPU does all command line entry/edit operations, and can be set to pass complete command lines on to other CPU(s). It also will echo text returned from the slave CPU(s) to the serial interface. To use this file:- * For single CPU operation, just compile it as is. * As a 'master' (talks to a slave), predefine symbol MON_MASTER. * As a 'slave', predefine symbol MON_SLAVE. Monitor commands (See also mon_help_text[] ) ---------------- Multiple cmds allowed on a line, use ';' to separate. Upper/lower case of commands and parameters is not significant. A 'range' may be:- start start end start length (Shorthand form: if length is small and < start.) start L length space (as 1st char) Repeat last command. Execute or re-edit. tab (as 1st char) Repeat 'saved' command. Execute or re-edit. tab (not 1st char) Copy cmd to 'save' buffer. esc (as 1st char) Allow re-edit of following 'repeat' cmd. (... twice ) Kill 'pass cmds to slave' mode. D range Dump mem. D (no other chars) Dump another 64 bytes F[W][I] range data Fill memory. W=word, I=increment. G addr Go (call) to addr M start [data]... Modify mem. data ::= hex_byte | string | char string ::= "text" char ::= 'c R [reg_name = value] Optionally modify register(s), then display all regs. reg_name ::= cc a b d dp x y u pc Z [flag_val] Zot! Set operation mode. Bit flags set are:- b0 Halt system (no return from monitor). b1 Inhibit serial echo. b2 Inhibit serial prompt output. b3 Inhibit all monitor output (incl help). b4 Pass all cmds to slave CPU. ESC,ESC to exit. Examples:- Z Re-initialize monitor. Lose trailing cmds. Z 0 Restore normal operation, continue. Z F Just accept commands, no system, echo, etc. Z 2 Normal, but no echo (ie half duplex). S1ccaaaadddddd....ddss<CR> Motorola data record. Load to memory. Each hex line is treated as a command, so there is no special 'load' cmd. Before sending hex, best to do a Z6 or Z7 to stop all other time consuming tasks. When finished, do a Z 0 to restore normal ops. An ASCII ACK ($06) is sent when line processing is complete and no error found. This can be used as an acknowledge. If an error is found, a '?' is returned. See s19_decode(). S0.... and S9.... Header and end records: ignored.

7 years, 10 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