I thought this was an excellent article on work at CHM on curating,
documenting, and making Apple Lisa software available - thank you Al. Would
be interesting to see other software collection objects curated in this way.
https://computerhistory.org/blog/apple-lisa-still-more-to-uncover/
Enjoy!
--
Lee Courtney
Philip Belben gave me a Philips P2000C luggable CP/M computer some
time back which had not been well-stored. It took a bit of work to get
it going
again. Here's what I did...
The basic desgn is a single-board computer with a Z80A, 64K RAM, 4K
ROM (bootstrap and a machine code monitor), floppy disk controller,
SASI interface and 3 serial port. One for an external printer, one for
communications [1] and one to provide a 19200 baud link to the other
main circuit board. This is an intellegent terminal with another Z80A,
32K RAM, video circuitry, keyboard interface and of course a serial
port
[1] Standards are wonderful, everybody should have one of their own...
This serial port is on a DB25 connectorr with the normal RS232 pinout,
but normal RS232 cables probably won't work. The reason is that
Philips decided to support synchronous operation too. So the serial
chp (Z80A-SIO) clocks come from pins 15 and 17 on the connector via
level shifters. The baud rate generator (one channel of a Z80A-CTC) is
level shifted and comes out on pin 24 of the connector. You therefore
need to strap 15-17-24 in the cable plug for normal asynchronous
operation.
Getting back to the machine, as well as the 2 main boards, there's a
switch-mode power supply, a Misubishi 9" green screen CRT monitor (Why
not Philips, they were certainly making such things at the time), a
pair of Teac FD55 floppy drives (of which more later) anf the'power
distribution PCB' to link them all toghether. Oh, and trivial things
like the keyboard cable and mains input wiirng.
I have the Philips service manual which contains schematcs for the 2
main boards but not the rest. I also have the Teac service manual for
the floppy drives.
Obvious faults on first inspection were that the mains on/off switch
didn't latch properly, there was a lot of corrosion, and the carrying
strap was missing. The last is important as to carry the machine you
put the keyboard over the front panel, then slot the strap end
fittings in place which also retain the keyboard.
I took the machine apart and found that the terminal PCB at the back
had suffered badly from poor storage. So had the disk drives, the
spindle bearings felt very rough. The aluminium chassis had surface
corrosion. Screws were very rusty (but standard M3 and M4 parts are
not hard to get). The rest didn't look too bad.
Time to sort some things out. I traced out the schematics for the
power supply, monitor and the power distibution stuff.
There were some RIFA 'smokebomb' capacitors on the PSU board which I
replaced before they did their antisocial act. Since the mains switch
was out of action I coupled a suicide lead to the power supply input
pins with a chocolate block and carefully powered it up with a light
bulb in series. The power supply worked first time.
Tried the monitor board, running it on the bench supply. This powered
up too, the high voltages came up but were low. As I didn't have the
deflection yoke connected this didn't worry me. So I put the monitor
chassis, PCB and CRT bak togther and connected it and the terminal PCB
to the units power supply.
Powered up, the screen was full of odd characters. It was clear the
terminal processor wasn't doing the right things. Some checks showed
the data lines on the RAMs were not looking right.Well, a couple were,
but not the rest. Cut out the old RAMs, most of the DIL packages fell
apart (!), fitted sockets and new 4116s. Corrected one open-circuit
PCB trace too. Powered up again ,it seemed to work.
Tried connecting the main board. It powered up and even gave the right
startup screen asking for a system disk. Of course no drives or
keyboard at this point, but it was a good sign.
Took the keyboard apart, took off all the keycaps and removed the
dregs of many cups of coffee. Put the keycaps back on.
The keyboard cable, right-angled 6 pin DIN plugs at each end, was a
mess. Insulation crumbling off, green corrosion of the wiring.
Fortunately the plugs are not moulded, so I could open them up, remove
the dead cable and rewire with a length of 6 core screened. It's not
coiled stretchy stuff like the original, but it's electrically fine.
Time to sort out the mains switch. I took it apart. An internal, tiny,
spring was so badly corroded that it fell apart when I touched it.
Other bits didn't look great either. My junk box disgorged an
electrically-suitable switch that was actually a spare for a TV set.
Only problems were that the pushrod to fit the button onto was 1/8"
square (the original one for the P2000C was 3mm) and the mounting was
very different. A file cured te first poblem. Fortunately the switch
mouting was a little plate screwed to the PSU mounting, so I removed
that and milled a block of aluminium to mount the replacement switch.
Soldered the mains harness wires to the new swtich.
While the chassis was apart I measured up and made some suitable end
fittings for the carrying strap. Oriiginals were plastic, I made
aluminium ones. Not too hard in that the tongue that goes into the
P2000C catch is 30mm wide by 2mm thick and amazingly a local-ish DIY
shed had 1m lengths of 2mm aluminium strip 30mm wide in stock. Cut
lengths of that, drilled and milled the hole to engage with the catch,
fitted a metal block to retain the keyboard and an eyebolt into that
to put the strap on.
Now to reasemble the chassis. Fitted the mains wirng, keyboard
connector, distribution PCB, PSU and monitor. Plugged in the terminal
PCB and connected the keyboard. Powered up then reset while holding
<esc> down. This runs a simple self-test of the terminal board. It
failed with a memory problem. I found another bad conneciton, this
time a through-board VIA. Soldered a bit of wire through that and the
terminal board then passed the self-test. I temporarily fitted it to
the chassis so as not to have too many bits hanging on wires. Put the
main PCB on top of the chassis, connected the power, reset, and serial
connectors. Powered up, got the 'system disk' prompt. Pressed <esc>
then and was in the machine code monitor. I could display/change
memory, etc. It was essentially working.
OK, now for the drives. These are Teac FD55A, single sided 40 cylnder.
I took them apart one at a time. Not just to the units in the service
manuak, I also took the head-load unit apart (tiny torsion springs),
the top front chasss (even smaller E-clips), the stepper motor (the
front bearing could not be removed without possibly damaging thngs,
but the rear came off easily with a puller so I fitted a new ball race
here) and the spindle motor (again, new ball races fitted).
Got the drives back togther. They ran nicely on the exerciser. Much
more smooth than they were when I took them out. Connected them to the
Microtest alignment unit and did the head alignment. One oddity was
that both spindle motors were slightly slow (about 295 rpm, not 300)
but a tweak of the pot on the motor PCB cured that
Also set up the disk read VCO on the mainboard as described in the
service manual. It was a little off, I am sure it would have worked,
but I re-set it anyway.
Cabled up drive 0. Powered up and put a 40 cyclnder boot disk in. It
booted. DIR worked too. As did running a program off the disk.
Unplugged things and removed the terminal PCB. Put the 2 drives in
place, fitted their mountings and the chassis top rail. Fitted the
main PCB and terminal PCB to the rear chassis plate. cabled everything
up.
Tried the machine again. It booted. I could format a blank disk in the
second drive and copy the CP/M master too it. The copy then booted
fine.
All that remained was to fit the rear plastic panel and top cover.
Stored the boot disk copy and the keyboard cable in the cubbyhole on
the front panel and put the keyboard on. Clipped on the carrying
strap.
It's not quite over...
I am pretty sure my strap end fittings are strong enough. Not so sure
about the strap itself which is one that came with a sports bag. I
may try to get something stronger.
I was given a few floppies with the machne. The only one it will read
is the 40 cylinder boot disk. Philips, you see made 3 versions of the
machine. One had a pair of 40 cylinder single-head drives (160K each).
The second had a pair of 80 cylinder double head drivs (640K each).
The last had a single 80 cylinder double head drive and apparently you
could fit a 10MByte wnchester internally. I know nothing about that
really..
Confusingly, the manuals call the 160K drive 'single density' and the
640K one 'double densiry' for all both use MFM encoding. But I
digress.
My guess is that at least some of the unreadable floppies are 80
cylinder. It would be worth linking up an external drive to see. Time
to hunt in the junk box again.
Then there's the SASI port. One manual mentioned a hard disk unit to
connect there, a 'Xebec board and 1 or 2 10M drives'. My guess is that
the former is an S1410, the latter a pair of Shugart ST412s or
similar. But it seems crazy to me to try to track down said parts --
the Xebec board has serveral custom ASICs on it, hard drives can
headcrash. Or even worst to use a Xebec controller with a drive
emulator -- why convert bytes to a curious serial stream on the Xebec
board and then back to bytes to store in flash memory on the drive
emulator, or vice versa. It would seem logical to simply make a thing
that connects to the SASI port, accepts the commands set of said S1410
controller and stores the data in flash memory directly. Any
suggestions as to how to do that?
Finally, the terminal board has an external video output It's a 5 pn
DIN socket, separate syncs and analpgue video (not composite). There
is a mention of a 12" monitor in one manual, of course with no model
number. Odd, I wouldn't have thought 12" was much of an improvement
over the built-in 9" unit. I would have expected something larger to
show a group of people at once. But making something to connect to
that output is another project.
-tony
I've skimmed the thread about making images of floppy disks. I want to
do the reverse.
But I had better explain. There are 2 subsets of computers here. The
larger subset -- all but one of the machines -- are classic computers.
These machines tend to hve real floppy drives and RS232 ports and not
much else.These machines I understand. I have service/technical
manuals. I have schematics. I can generally figure out how to program
them.
The other set contains one machine. A modern-ish (for me) PC laptop.
It has USB ports. It gets me on the internet (it is the only
internet-connected machine at the moment). It does not have floppy
drives [1]. I do have a USB-RS232 interface -- first thing I bought
for it. I have no proper manuals for it. I do not know how to program
it or interface it.
[1] I think I have a USB floppy drive somewhere, but it'll be a
'1.44Mbyte' [2] 3.5" thing. A type of drive conspiculously absent on
my classic machines.
[2] In quotes becuase it is, of course, nothing of the sort. Well, not
unless you believe a megabyte is 1000*1024 bytes.
Given that the floppy disk images are going to come on the latter
machine, what is the easiest way to get them onto real floppy disks
for my classics. I think it's reasonable to assume they'll be FM or
MFM encoded at the standard rates and that I will have drives capable
of handling the disk. FM of couse rules out using some PC disk
controllers.
I do of course have no objections to making stuff, but I'd rather not
start trying to interface a WD2793 to a Raspberry Pi if there's a
standard way to do things.
-tony
A couple of questions if anyone has experience of this machine :
1) There is a 5 pin DIN socket for connecting an external video
monitor. The signals seem to be TTL-level separate syncs at European
TV rates (15625Hz horizontal, 50Hz vertical) and separate (not
composite) 4-level analogue video.
I believe Philips sold a 12" monitor to connect there. What was the
model number? Is a service manual availabe?
Has anybody linked other monitors to that socket?
2) There is a 50 pin card edge for a SASI interface. I think the
Philips hard disk unit used the Xebec S1410 controller. I've
downloaded the user manual for that from bitsavers which at least
gives me the command set.
Does anyone have experience of a SASI-flash memory interface? Any
recomendations for things to look at? Or should I design my own, it
doesn't appear too hard?
FWIW to tie in to another thread, I like to keep my classic computers
original inside the box but am happy to link up non-standard
peripherals. So My P2000C will keep its 2 internal floppy drives and
CRT monitor. But I would have no problem with hanging an LCD monitor
off that video output socket.
-tony
I don't even remember signing up for the RetroAbout64K mailing list. I haven't seen any actual dicussion in my remembrance. But I do get once or twice a week an email about COCO Nation or some such. Sounds like a hot chocolate enthusiasts group seeking world domination. Anyway I've had COCOs going back. Or 1 that I scarfed from a friend for 20$ (back in 89 I think). I realize it has a 6809 and all, the successor to the venerable 6800. But what can you do with the things? Is there even a color output, despite the name. I can't remember. I only remember playing Dungeons of Daggorath or whatever. The guy I bought it from claimed he programmed a complex naval similation. Yeah whatever.
As to what can you do with it? A local company was running a homemade NC
drill using the (IIRC) Coco 2 with a pair of disk drives to drive the
thing. I bought it for kicks, but never used it.
To ask another similar question, I have a tektronix 2 axis controller
that uses paper tape. Changing the questions slightly, WHY would I use
such a thing? And ditto for an Intel software development system.
I have more than enough nostalgia items to keep me busy for the next
hundred years or so :).
> Date: Mon, 23 Jan 2023 17:22:06 +0000 (UTC) From:
> skogkatt007(a)yahoo.com Subject: [cctalk] any COCO enthusiasts
> I don't even remember signing up for the RetroAbout64K mailing list.
> I haven't seen any actual dicussion in my remembrance. But I do get
> once or twice a week an email about COCO Nation or some such. Sounds
> like a hot chocolate enthusiasts group seeking world domination.
> Anyway I've had COCOs going back. Or 1 that I scarfed from a friend
> for 20$ (back in 89 I think). I realize it has a 6809 and all, the
> successor to the venerable 6800. But what can you do with the things?
> Is there even a color output, despite the name. I can't remember. I
> only remember playing Dungeons of Daggorath or whatever. The guy I
> bought it from claimed he programmed a complex naval similation. Yeah
> whatever.
So... Here we go.... :-)
For reference, TALOS is my pdp11/83 system from way back long ago. It's
running real hardware, RX02, RL02, a 330mb ESDI disk, TK70, and 4mb of
parity RAM.
Runs with 2,000 blocks of cache, read-ahead of 5, and purrs along pretty
nicely overall.
The next step is to get 4mb of PMI memory as the 1mb board I have *is*
faster than Q bus memory but there's not a lot I can do with DECnet and
TCP/IP in only 1mb.
But finally I can get to my system without an RS232 cable. And fix the
time offset. But progress!
(Now I need to back it up)
Thank you Johnny for writing this code.
Welcome to TALOS, an RSX-11M-PLUS system!
>hello 1,1
Password:
RSX-11M-PLUS V4.6 BL87 [1,54] System TALOS
23-JAN-2023 07:48 Logged on Terminal TT12: as SYS2
Good Morning
*****************************************************************
* *
* Welcome to RSX-11M-PLUS *
* *
* Version 4.6 Base level 87 *
* This is file LB:[1,2]LOGIN.TXT *
* *
*****************************************************************
Last interactive login on Monday, January 23, 2023 21:37:35 (TT1:)
>
Does anyone by chance have a schematic for the 3/110 main board? Its been
running great until recently where my framebuffer died. It boots right up
to where it polls the cgfour and then stalls. I was hoping to do some
troubleshooting.
Thanks,
Kurt
