On Mar 2 2005, 20:25, Christian R. Fandt wrote: tests. I anybody part MicroPDP-11/73 They're the standard XXDP disks that came with a microPDP-11 -- they were probably supplied with your microPDP-11/73 when it was new. They're no use for a VAX. Aren't these the same disks you asked about last May? I posted a listing of the directories then. There is a manual for XXDP, but I don't have it (unless it's buried in my microfiche somewhere, which I don't think it is). However, I put my notes and extracts of the help files on my web page a long time ago, and you can still find them here: http://www.dunnington.u-net.com/public/PDP-11/XXDP.pdf http://www.dunnington.u-net.com/public/PDP-11/XXDP.ps (same contents, just different file formats). Those will allow you to work out what most of the files do. There's also a partial list at http://starfish.osfn.org/rcs/pdp-11/xxdp/xxdp25_notes.txt Al and Henk had a discussion some time ago about scanning the documents (program-specific instructions and listings) for each of the diagnostics. Each one is normally known by a name like ZRQBH0, or more often just ZRQB, where the first letter refers to the processor type, the next 2 to the device, the fourth to the test number. The last letter and digit are the revision and patch level -- so ZRQBH0 is to run on any processor ("Z"), to test some part of an MSCP disk system ("RQ"), test "B" -- actually it's the formatter for an RD51 or RD52 on an RQDX1 or RQDX2 controler (ZRQC is the corresponding formatter for an RQDX3). It's therefore slightly unfortunate that Al indexed his by a different scheme, but not too hard to find what you want (if it's in his archive). Look at http://www.bitsavers.org/pdf/dec/pdp11/XXDP/ for some scans. The initial "C" on some of the names refers to the media it was supplied on. It's not really part of the name. Henk has summaries of some that are relevant to his interests, on his web page at http://www.pdp-11.nl (see the menu entry for XXDP on the left) which are fine to get you going, but many of the disgnostics halt on varous errors, and you often need the listings to see what caused the halt, or to do more than simple tests. -- Pete Peter Turnbull Network Manager University of York