test-drb February 2016

test-drb@ccmp.vtda.org

203 participants
239 discussions

by ed＠groenenberg.net

On Wed, February 17, 2016 06:59, Arno Kletzander wrote: >> Hi, >> >> Is anyone interested in PCS Cadmus/QU68000 systems? We at Hack42 have no >> idea what to do with them. We need to downsize and these take up a >> significant amount of our space. >> >> See http://dev.ramdyne.nl/IMG_2750.JPG for photograph of the stack. >> >> If you know other people who are interested in beasts like these, please >> pass this information on. >> -- >> Andreas > > Looks like interesting machinery from a German manufacturer! > > There is a short blurb about them on de:wp > (https://de.wikipedia.org/wiki/Cadmus_Workstations) saying the PCS QU68000 > were based on (who'd have guessed...) a 68000 processor on a QBus (!) > while the later models sold under the CADMUS trademark held 68020/030 and, > from 1985 on, MIPS RISC processors. They ran MUNIX, a V7 UNIX derivate, > with some quite sophisticated cluster integration (network boot, > "Newcastle connection" common superroot namespace, networked block > devices) enabled by a board called the Intelligent Communications > Controller. > The outfit even still seems to stick around here > (https://www.pcs.com/en/company/history/the-history-of-pcs/), albeit > manufacturing access/time registration/industrial data terminals nowadays. > > As usual, if somebody from Germany conducts an operation on those and > doesn't know where to put all of them, I'm willing to help out with > collecting and re-homing. (I may also have an opportunity to collect a > couple of them in the Netherlands if there are any left by/can be held > onto until end of May 2016. I'd wish for one of each significantly > different type but this is not a reservation but a "last resort" deal if > they'd go to trash otherwise. Basically, if anyone else comes along > offering a good home for them, I'm happy to stand back.) > > TIA, > > Arno > Yes, those were nice machines. I worked with these systems in '84 - '87 and did visit their premises in Munich a few times. It was a small office/factory building in the mids of a housing area. Ed -- Ik email, dus ik besta. BTC : 1J5fajt8ptyZ2V1YURj3YJZhe5j3fJVSHN LTC : LP2WuEmYPbpWUBqMFGJfdm7pdHEW7fKvDz

8 years, 10 months

PDP-11 COBOL-11 or COBOL-81? (was Re: Anyone have DIBOL-11, CTS-300, or CTS-500?)

by spacewar＠gmail.com

DIBOL-11 seems quite rare these days. Is COBOL-11 or COBOL-81 any easier to find?

8 years, 10 months

For sale PDP 11/45 + TU56 + more

by jasper.wijnands＠gmail.com

Hello, For sale rare PDP 11/45 mini computer Included: - TU56 Tape transport - Cardbuses - Original DEC Schematics Accepting offers. Please mail to jasper.wijnands at gmail.com. Located in The Netherlands. Kind regards, Jasper Wijnands pictures: [image: undefined] [image: undefined] [image: undefined] [image: undefined] [image: undefined] [image: undefined]

8 years, 10 months

Couple of Xerox 6085 questions

by tmfdmike＠gmail.com

1. Anyone who has played with Xerox systems will have encountered the dreaded 0937 code at boot time; it means "I have been configured for network operations. I abjure the world and will wait until hell freezes over before continuing the boot - unless I get the time from a network time server!" This is inconvenient and frustrating at times. Netware IPX/SPX is basically Xerox XNS implemented pretty much unchanged; does anyone happen to know if a Netware server can provide network time server functions - and in a way that a Xerox workstation would grok? 2. I haven't powered up my 6085s in a long time - at least 5 years; maybe 10 for some of them. The results have been most disappointing. They won't even *start* POST - and/or they give a rolling screen with no sync - and/or a blank screen - and/or they pass POST but won't boot with an 0151 error. I've tracked these down in most cases to flaky IOB boards. These boards hold the system PROMs. Anyone else seen similar issues? Could it be bit rot in the PROMs? Is that a known thing with 6085s? Thanks Mike

8 years, 10 months

Looking for printers: Epson Stylus Pro 9000, Epson 9500, Lexmark 7000 Z11

by sieler＠allegro.com

Hi, I'm looking for some old inkjet printers for a legal partner: Epson Stylus Pro 9000 Epson 9500 Lexmark 7000 Z11 They're from about 1998 or 1999. They probably have fixed nozzles across the page, no moving head. Assuming they're of the correct vintage / acceptable, a bounty will be paid. thanks! Stan Sieler sieler at allegro.com Cupertino, CA

8 years, 10 months

Apple Lisa 2/10 for sale

by ramdyne＠gmx.net

Hi, We at Hack42 have an Apple Lisa 2/10 for sale at http://www.ebay.nl/itm/121893065311. When we powered it up for the last time 18 months ago, it appeared to be working (no nasty smells etc) but we didn't test it very much. What has happened since is anybody's guess. Note: shipping to the US is *really* expensive, but within Europe is only slightly less painful (with packaging it'll reach 25kg easily). Pickup is an option. -- Andreas

8 years, 10 months

VAX/VMS media

by auringer＠tds.net

Hello all, I have a bunch of VAX/VMS media that need a new home. I must move them very soon and I have little time for shipping. Pickup from 53714 (Madison, Wi) preferred. 16MT9: VMS V5.3 BIN 1/2 & 2/2 in shipping box with docs VMS V5.3.1 BIN 8" floppy media: VAX/VMS 3.4 5 disks VAX/VMS 3.6 VAX/VMS 3.7 VAX/VMS 4.0 3 disks VAX/VMS V4.1 UPD BIN 4 disks VAX/VMS V4.2 BIN RX01 MANDATORY UPDATE VAX FORTRAN 3.4 VAX PASCAL 2.3 Microfiche: VAX/VMS 3.6 SRC LST VAX/VMS 4.2 SRC LST -Jon

8 years, 10 months

IBM (Sony) PowerDisplay 20

by stefan.skoglund＠agj.net

Howdy. I connected one of theese (i have two) to an PC last night. Blemishes: the text is blurry wrong color tones (a little bit red) so how much can i do with the display picture setting buttons ? I'm thinking about connecting one of them to a Sun 10 (but i do have a bunch of RS 6000 PPC machines.)

8 years, 10 months

Tool to convert between Motorola FFP and IEEE754 float formats?

by classiccmp＠philpem.me.uk

Hi, Does anyone know of a tool which can convert between Motorola's FFP (Fast Floating Point) float format and IEEE754? I'm trying to reverse-engineer some ancient 68k code which uses the FFP library, but a load of the floating point constants have been hard-coded as hex constants, which is making things hard to interpret... I've tried to convert the 68k assembler in FFPIEEE.SA to C, but I must have missed something because it just isn't working... Thanks, -- Phil. classiccmp at philpem.me.uk http://www.philpem.me.uk/

8 years, 10 months

Stuck bits on 11/73 Clearpoint 4MB memory - how to repair?

by jnc＠mercury.lcs.mit.edu

> From: Jacob Ritorto > I struggled for hours with inadequate eyesight, tools and materials, > but I think I got this mod done! That was quick! I had an 11/23 on my workbench that had had that backplane mod, so I took it apart to take a picture, to help you, but I guess that's OBE... :-) > the machine's stuck in self-test at error 47, Memory CSR error. It's not clear that that's really a hardware problem. DEC makes assumptions about how many memory CSRs there will be, etc, and some third-party board 'fail' when they don't meet those expectations. I have a Clearpoint QED1 (I think that's the one, didn't check) that does that. > What I assume is the parity light on the third party "Clearpoint QRAM-2 > SPB-1 88B" lights during self test. I've found no documentation for this > sucker as yet.. I have a PDF of the "User Information Manual" for the Clearpoint Q-RAM 88B. (Oh, I see, later message says you found it.) No prints, alas. Anyone have any we can scan and put online? > I'll have to find my rl02 controller and build the system up some more > so I can run xxdp and find out what exactly died. I would tend to use diagnostics as 'help', not my main tool in diagnosing faults. This is particular true as really bad issues can prevent the diagnostics from loading/running, so if you get skilled at fault analysis without depending on them, you're better situated to deal with the failures that prevent using them. > Can anyone offer hints as to how to identify which component is broken > and how to go about repairing this? As other have said, lacking the prints, pulling chips (if they are socketed) ought to enable you to work out which chips goes where. (I'v worked out the chip layout for a number of un-documented memory cards this way.) I don't know about your 88B, but the one I have photos of, and my other Clearpoint cards, the chips are in sockets. With luck yours will be too... If not, ask if someone has one with sockets (alas, I don't have an 88B), who can do the mapping for you. Important: once you have worked it out, pass it along! I'm trying to upload all the data I've collected about cards for which no documentation is available to the Computer History wiki. > It's the only memory board in this machine, so I guess the problem > might actually be a bus or processor board, right? Could be. I have an KDJ11-B which has stuck bits, and that's the CPU board, so yours could be to. > I have no other q-bus memory to test with, so can't do swapping / > process of elimination to be sure. It's definitely worth having another small QBUS memory card to use in fault isolation when debugging. M8044's are readily available on eBay for about $20. They are only Q18, so not usable in the same machine as Q22 memory, but they are useful for debugging. I would definitely invest in one. (If you luck out and get a bad one, send it to me, and I'll swap it for a known good, tested, one. I've fixed a whole bunch of them, got to the point where the last one I did for someone I didn't even have to pull out my 'scope! I could tell from the symptoms exactly which chip to replace! :-) > From: Jay Jaeger > Well clearly it is only affecting certain address bits - or the > diagnostic would not run at all Well, like I said, I do have a KDJ11-B which will run the on-board startup diagnostic, but which has a bit stuck hard on the QBUS interface! So those machines seem to be pretty resilient. Although as you point out, if he can load and run the diagnostic, it's probably not the CPU. > note that it is starting at 010000000, so that points to the memory Yup. If some locations work, and others don't, it's almost certainly the memory. And since he's only dealing with a single memory card, it's probably not the bus drivers/receivers on that card, either. One can use ODT on the KDJ11-B to poke around, and find the envelope of the problem. (See comments above about not relying on diagnostics! They are better for saying something's busted, than for accurately telling what _is_ broken.) With that, and a chip->memory map, it should be fairly easy to replace the offending chips. Noel

8 years, 10 months

← Newer
1
...
11
12
13
14
15
16
17
...
24
Older →

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 February 2016