On the off chance that someone on the list wants it and doesn't like the
idea of shipping, I'll be going to VCFMW in September and could bring it
along. My route will be Santa Barbara, Las Vegas, north to I-80, and
I-80 to the Chicago area. After that, I'll be headed to Pittsburgh, PA
and it can be dropped off along the way.
I can also head out to Goleta (basically Santa Barbara) and check out
what this person has.
Marvin
>> On Mar 3, 2019, at 10:35 AM, Ray Arachelian via cctalk <cctalk at classiccmp.org> wrote:
>>
>> On 03/03/19 12:58, Marvin Johnston via cctalk wrote:
>>> I just ran across this and while I'm not interested, someone on the
>>> list might be.
>>>
>>> https://santabarbara.craigslist.org/sys/d/apple-512k-lisa-computer-valuetec…
>>>
>>>
>>> It was posted about 14 days ago, and looks to be in Santa Barbara, CA.
>>>
>> That doesn't look like it's a Lisa, it may be a tempest hardened Mac 512.
>
> An interesting system. Someone needs to save this. Based on the description, and the way it looks, I think you?re right about it being designed for TEMPEST hardening. There were some TEMPEST versions of the Mac II.
>
> Zane
Hi all,
I recently got one of these DECtalk-PC ISA cards from eBay (
https://www.ebay.com/itm/183684666377, no affiliation with seller other
than a happy customer) and was wondering, does anyone have a schematic for
this?
Thanks!
Kyle
Hello Everyone,
We found a PDP-11 QBUS card cage with a KDF11 and some other cards (RAM,
ROM, some basic peripherals) which included a DSD-4140 card.
Unfortunately, the DSD-4140 is missing one of it's microcode PROMs for
some reason.
Does anyone else have one of these cards? It'd be really helpful if we
could get some dumps of the 4 microcode PROMs so we can compare what we
have and look into replacing what we don't have with an adapted modern
part. (and if anyone goes to the trouble to read the 4 microcode PROMs,
there's also an 82S137 that deserves to be dumped).
Here's a picture of the card in question: https://i.imgur.com/tzYjPYF.jpg
Regards,
Joe Zatarski
On Sat, Mar 2, 2019 at 3:16 PM Glen Slick via cctalk
<cctalk_at_classiccmp.org> wrote:
>On Sat, Mar 2, 2019 at 12:02 PM Joseph Zatarski via cctalk
><cctalk at classiccmp.org <http://www.classiccmp.org/mailman/listinfo/cctalk>> wrote:
>>//>>/On a somewhat related note, I don't suppose anybody knows or has />>/documentation on the pinout of the C/D interconnect on these RAM boards? />>/The pinout for the ribbon cable is in the manual, but the C/D />>/interconnect doesn't seem to be documented in any of the manuals that />>/are online. />
>650QS Field Maintenance Print Set, MP-02538-01, Rev C1
>http://www.bitsavers.org/pdf/dec/vax/650/MP02538_650QS_Sep88.pdf <http://www.bitsavers.org/pdf/dec/vax/650/MP02538_650QS_Sep88.pdf>
>
>Page 65 of the PDF, KA650 Circuit Schematics Page 23 of 40
>MA0 - MA9
>CAS0 - CAS3
>RAS0 - RAS3
>WE
>SE
>XADDR20, XADDR21
>+5
>GND
>
>Page 47 of the PDF, Page 5 of 40 is an overview block diagram of those
>signals originating at the DC357 CMCTL Memory System Controller.
OK, thanks, that's great. Now I won't have to bother tracing things out if I decide to go that route. Didn't realize there was a printset for the KA650, but I guess I didn't even bother to check.
Hello Everyone,
I've got a KA650 with a MS650-AA 8MB memory module. When we initially
started messing with this VAX, it was giving a memory error. We were
able to track down first the bad bank, and later the individual bad ZIP
RAMs with the help of my logic analyzer. For now, I kludged an SOJ DRAM
in there that seems to be working without issue. The machine no longer
gives memory errors during POST, but if you run one of the more thorough
memory tests like #48 (MEM_Addr_shrts), it fails. My initial thought was
that this RAM test checks for shorted address lines, which would cause
writing to one location to change another location perhaps. However, I
haven't been able to replicate the error with DEPOSITs and EXAMINEs on
the console.
Without having to disassemble the VAX ROM, does anybody know what this
test does? Once I know what I'm looking for, I can probably convince the
logic analyzer to see the error with some fancy triggering, and get this
board 100% fixed before I order some ZIP DRAMs.
On a somewhat related note, I don't suppose anybody knows or has
documentation on the pinout of the C/D interconnect on these RAM boards?
The pinout for the ribbon cable is in the manual, but the C/D
interconnect doesn't seem to be documented in any of the manuals that
are online. With the price of MS650's these days, it seems like the
cheaper route (albeit more work) is to build a new RAM board rather than
buy one (especially if a single 64MB board could be made). I suspect
it's not too complex anyway, and it can probably mostly be traced out,
and the rest inferred and then verified with a logic analyzer.
Thanks,
Joe Zatarski
Hello everyone,
I've got two unrelated things I'm looking for:
The first is an HP logic analyzer interposer for the emulation adapter
for an MC68332. This would have a PGA socket on it, and sort of a
reverse socket for the QFP132 package (attaches to a chip from the top,
to interface to a chip soldered onto a board). I believe the part number
would be HP E3417A. I already have the QFP160 adapter, but the chip I
want to interface to is a QFP132. This adapter supposedly exists, but
I've had no luck trying to find it through the usual channels.
The second that I'm looking for, is if there's someone out there that
owns and can dump the microcode ROMs from a DSD-4140 QBUS floppy
controller. We've got a card here that's missing one of the ROMs, and
we're also not sure if the ROMs are mixed up, so a dump of all 4 ROMs
would be appreciated. They are 82S181, but they should read in any EPROM
burner with a breadboard and some wiring to adapt the pinout. Burning
them is another story, but we'll worry about that later... Here's a
picture of the card in question: https://i.imgur.com/tzYjPYF.jpg
And if anyone has one of these and is kind enough to dump it for us,
there's also an 82S137 on the card that probably deserves a dump as well.
Thanks,
Joe Zatarski
Hi all
I have a couple of near identical Sun Enterprise M4000 servers fitted with SPARC64 VI 2.1GHz CPUs, 16GB and I think 2 x 146GB disks.
I *think* these are working but have never powered them up. I purchased them surplus a year or so ago.
Available free of charge to any Sun fans - these are collection only sorry.
I?m not too far from Cambridge location wise in the UK.
PM me if interested. First come first served.
Thanks
Ian
So, I've been having some fun playing around with V6 Unix on my 11/45 a bit after that last repair.
I've just been tripped up for a little over the fact that the C compiler barfs if there is whitespace/comentary before the first #include; the workaround seems to be to add a lone '#' at the beginning of the file. It took me a while to notice that this was done, for example, in all of the device driver sources.
I found this curious. Anybody know what the story is there?
--FritzM.