test-drb May 2015

test-drb@ccmp.vtda.org

199 participants
259 discussions

by roger.holmes＠microspot.co.uk

On 7 May 2010, at 08:25, cctalk-request at classiccmp.org wrote: > > Message: 2 > Date: Thu, 06 May 2010 16:06:37 -0700 > From: Al Kossow <aek at bitsavers.org> > Subject: Re: Servant .953 > To: cctalk at classiccmp.org > Message-ID: <4BE34B7D.6060902 at bitsavers.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 5/6/10 2:23 PM, Fred Cisin wrote: >>> Al Kossow wrote: >>>> I am interviewing Andy Hertzfeld tomorrow, and had hoped to talk about >>>> Servant, but I can't find a copy of it around anywhere tonight. > > A huge thank you to Nigel Williams who forwarded a working copy of .951 five > minutes before Bill and Andy arrived. We spent an hour talking about MacPaint > and Quickdraw (Apple has finally given CHM approval to make the sources available) > then another hour on Alice, Dali Clock, Servant, Hypercard, and Magic Cap. Could you please clarify, the QuickDraw source is available for what purpose? Could developers modify it any include it in heir commercial 64 bit Intel applications for instance? Is the source Pascal, Assembler, C or something else? Roger Holmes, Director of Microspot who has a Carbon application which compiles with over 10,000 warnings about deprecated QuickDraw calls.

8 years, 6 months

websites on the classiccmp server

by jwest＠classiccmp.org

8 years, 8 months

Any word on the Multics revival front?

by madcrow.maxwell＠gmail.com

When Multics was officially released as free software a couple of years ago, there was a flurry of activity aimed at getting some sort of emulator up and running to run it. Did anything ever come of that or did folks just lose interest (or find out that the needed GE/Honeywell hardware was too poorly-documented to write an emulator of) Mike

8 years, 9 months

M9301-YB Bootstrap/Terminator ROM dumps / listings?

by jnc＠mercury.lcs.mit.edu

> From: Johnny Billquist bqt at update.uu.se > The per-device code are in separate PROMs that are used in both the > 9301 and 9312. Those are the ones with the device code as constants in > the beginning of memory space for the PROM, by the way. As I mentioned, the M9301-YA, at least, does not have this code. (See the listing.) Also, again on the M9301-YA, the various bootstraps, diagnostics, and console, are scattered through both banks (ditto), so one can't just replace a PROM or two to chance the supported devices; one would have to replace the entire set of 4 PROMs. > I hope you also are aware that both the M9301 and the M9312 have > different boot roms for some machines. I know that the 11/70 use > different roms with other tests than other PDP-11s, and I seem to > remember that one or two others do as well. (The 11/60 keeps popping up > in my brain...) I have yet to investigate the M9312's in depth, but I did know there are quite a few different versions of the M9301 (which amount to different ROMs: I know there are two different etch revisions of the card itself, but I think they are programming-wise identical). I don't know of any good list of the variants, but here are the versions I know of (device codes abbreviated to save typing): M9301-YA /04 and /34 OEM version; has basic diagnostics, console emulator, boots from various devices (RK, RP, TC, TM, DL, PC, TA, RX), supports auto-boot on power on, and also power-fail restart M9301-YB /04 and /34 end user version; has basic diagnostics, console emulator, boots from various devices (RK, RP, TC, TM, TA, RX, DL, PC, RJS, RJP, TJU), also power-fail restart M9301-YC /70 version; contains basic CPU, cache and memory diagnostics, boots from various devices (TM, TC, RK, RP, RK06, RJS, RJP, TJU, RX) M9301-YD All models; contains code to allow a terminal attached to the machine to be a terminal on some other line; also has boot code for RX and DDCMP M9301-YE All models; has basic diagnostics, console emulator; boots from low speed paper tape or DECnet; supports auto-boot on power on, and also power-fail restart M9301-YF All models (auto-start not available on /45, /50); has basic diagnostics, console emulator, boots from various devices (RK, RK06, RP, TC, TM, TA, RX, DL, PC, RJS, RJP, TJU) supports auto-boot on power on, and also power-fail restart M9301-YH /60 and /70 version; contains basic CPU, cache and memory diagnostics, boots from various devices (TM, TC, RK, RP, RK06, RJS, RJP, TJU, RX, PC) M9301-YH All models; has basic diagnostics, console emulator; boots from DECnet, and various devices (RX, TU, DL, DMC), also power-fail restart The -YA is the only one I have examined in detail. Noel

8 years, 11 months

IBM PS/2 Model 70 HARD DRIVE NEEDED

by mokuba＠gmail.com

Got a hard down situation and need to re-install/recreate the BBS system I had running. HDD makes swishy noises when shaken, haven't tried stirring yet. I /guess/ a bootable MCA SCSI card would work too... ;) I had the 160MB drive, but anything above 30 would work - i guess i'll just have to use a SCSI Drive for the file storage area once i get an MCA SCSI card .... -- Gary G. Sparkes Jr. KB3HAG

9 years

Large batch of DEC flip chips

by j_hoppe＠t-online.de

Here's the opportunity to buy&save batches of DEC flip chip modules. It must be several thousands, I estimate the total weight of the boxes to over 100kg. Most are "red" logic series, but other colors are there too. Apparently they are plugged from different machine types, maybe even PDP-10s or -12s. Of course I'm greedy! But while we have a PDP-12 and some DECtapes here, this amount is mostly useless and will occupy much precious space until the end of my days. So question: Is there any reasonable demand for flip chips in the community? And more difficult: any hint about the price I can offer? Thanks for your opinion, Joerg

9 years

Announcing TCP/IP for RSX-11M-PLUS

by bqt＠softjar.se

Well, it's been a long time project, but I'm happy to finally announce a more public initial release of TCP/IP for RSX-11M-PLUS. This is the result of over 20 years of development. Needless to say, I've been doing a lot of things over the years, and this code have been through four reimplementations over the years. What I now release is something that I believe is a nice and useful piece of software. I am aware of the fact that most people do not use these machines any longer, but if someone actually wants to talk to me about support for this or other RSX software, let me know. Also, feel free to spread this information to anyone who might be interested, anywhere. So - what is in this release? It is a complete implementation of ARP, IP, UDP, and TCP for RSX-11M-PLUS. It has been tested on RSX-11M-PLUS V4.6, but should work on any V4 release. There might be some small tweaks or fixes required, but nothing major. It do require a system with split I/D-space, or else at least the TCP part will not fit. For Unibus machines, it should be possible to run without any additional software except what is in a base RSX distribution. For Q-bus machines, DECnet is required for ethernet networking. The TCP/IP stack can co-exist with DECnet. Some utilities also utilize RMS for file access. A bunch of tools, utilities and libraries are also included. These include: . IFCONFIG network configuration tool. . NETSTAT network information tool. . PING . TRACEROUTE . DNS client . FTP daemon . FTP client . HTTP server . TELNET client (rudimentary) . TFTP client . TFTP server . INET server that can do SINK, ECHO, DAYTIME, QUOTE, and IDENT . NTP client . LPR client that sits in the queue manager (rudimentary) . FORTRAN-77 library . BASIC+2 library . PDP-11 C library The implementation fulfills most of the requirements put forth in RFC 1122. There are a few limitations because of restrictions in the PDP-11, but none of them should really cause any problems. Documentation is still on the thin side, but example configs are also provided, along with installation scripts. A bunch of test programs and example programs are also included, as well as the sources of all tools and libraries. The TCP/IP stack itself only comes in binary form. All tools are also included precompiled in the distribution, so an installation only have to build the stack itself for your system, and then you should be ready to go. The API only have a slight resemblance to the Unix sockets API. However, if someone sits down to write code to use TCP/IP under RSX, I'm sure they will discover that it is extremely easy to use the libraries, or the basic functions. The TCP/IP implementation is mostly written as device drivers. This also have some other interesting implications, such as it is possible to access TCP as a normal file. You can, for instance do something similar to the Unix netcat command by issuing the MCR command: > PIP TI:=TC:"foo.com";4711 which would open a connection to foo.com, on port 4711, and any data sent from that machine will be shown on the terminal. The resources used by TCP/IP are modest. A memory area (size selectable at generation/startup) is used internally. The amount of memory in the private pool limits the amount of data that can be buffered. Normal pool is used in a small quantity for each TCP port that is open. People are welcome to play around with this, and make improvements. Contributions of code is most welcome. There are still lots of things to do. The programs marked as rudimentary should be rewritten. The most obvious thing still missing is a telnet daemon, which probably is my next step. However, the reason for now announcing the release is that it can finally be distributed natively from an RSX host. The main locations to download the TCP/IP for RSX are: Madame.Update.UU.SE (anonymous ftp). This is one of my development systems for this software. It runs under E11, and if things are down, I blame E11. :-) When connected, you are already in the right directory. There is both an RL02 disk image there, which can be downloaded by anyone. If you happen to have an RSX system which you are conneting from, you can also try getting the BQTCP.TAP tape image. Such an image will not transport cleanly to a non-RSX system, however. Sorry. ftp.Update.UU.SE (anonymous ftp) - /pub/pdp11/rsx/tcpip The disk image is normally duplicated to ftp.update.uu.se as well, so the same file can be found there. I hope some people will find this useful/amusing. :-) Johnny Billquist -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

9 years, 2 months

Opening a DECserver 90M External PSU

by robert.jarratt＠ntlworld.com

One of my DECserver 90M PSUs got dropped and stopped working as a result, possibly because it got pulled by the cable. That sounds like the kind of damage that might be repairable. I tried to open the enclosure and I found a hole under one of the labels, expecting it to be a screw hole, but it isn't. I am guessing you just have to pry the halves apart, but without knowing where the clips are inside it is easy just to break the thing. Does anyone know how you open these PSUs? Thanks Rob PS Yes I know these PSUs are notoriously unreliable, and that you can make a PSU with a DIN plug and a wall wart, but I would still like the original to work if possible.

9 years, 2 months

Aresco Newsletters

by mikolaym＠yahoo.com

Hi all, Out of curiosity, did anybody on here subscribe to any of the newsletters published by a company called Aresco back in the late 70s and early 80s? These newsletters were VIPER (Cosmac VIP), Paper (Commodore PET), Source (Exidy Sorcerer), and Rainbow (Apple II). Aresco also published a series of books by Tom Swan titled PIPs for VIPs. I own several issues of VIPER, but I'm still looking for copies of the others. Does anybody have these newsletters in their collection? Matt

9 years, 2 months

Still seeking 3B2 information

by lists＠loomcom.com

Hi everyone, I've made tremendous progress on my 3B2 emulator. It's being implemented under the SIMH simulator platform, which has been a huge help. My WE32100 core is getting closer to being complete. I'd consider it alpha quality right now, but it has enough instruction coverage to pass the 3B2's power-on self tests and to (barely) run some of the 3B2 firmware mode tools. Implementing the WE32100 core has been thanks to the processor manual and assembly language manuals that are available on BitSavers, but outside of the CPU, virtually all of my understanding of the 3B2's architecture has come from studying the ROMs and the SYSVR3 source code. I've also been helped by having remote access to a running 3B2 so I can assemble and disassemble code using the real AT&T tools. Beyond that, I have found precious little documentation. I'm at the point now where I'm pretty well stuck until I can find more information. I understand large chunks of the memory map now and should be able to do things like simulate the floppy and hard disk controller, but there are large gaps in my understanding. There are many undocumented registers that are used by the firmware, but don't appear in the SYSV source code anywhere. What they mean and what they're for is anybody's guess. I've just stubbed them out for now. If anybody has access to schematics, architecture docs, or other memory map information, I'd be eternally grateful if you could share it! -Seth

9 years, 3 months

Jump to page:

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 May 2015