Besides link cleanups and custodial changes, there is now a model-specific
page for the Eagle 450, one of the earliest ColdFire systems extant, plus
performance statistics for many of the machines and several more newly uploaded
freeware games. Hosted on an Alpha Micro Eagle 300.
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser at floodgap.com
-- It's not an optical illusion. It just looks like one. -- Phil White --------
> From: Josh Dersch
> how is the backplane in the H11 currently configured? (i.e. what boards
> are in what slots?) Could the issue here be something as simple as a
> break in the qbus due to a misplaced board?
He did mention that he had the console card in the slot next to the CPU, which
I think is what you're referring to - but it shouldn't matter for ODT, which
doesn't use interrupts, only programmed I/O.
A QBUS system will work fine without continuity of grant (interrupt, DMA)
lines to boards which only respond to DATI/DATO (memory, non-interrupt I/O,
etc). Just for grins, I took my -11/03, and plugged the console card in a
bunch of slots down, leaving several empty slots between it and the CPU, and
it worked 'fine': ODT was fine, and it would run "BR ." programs fine, too.
So unless there's actually a break in one of the 'broadcast' bus lines (e.g.
BDALxx, etc) on that backplane, between the CPU slot, and the slot the console
card is in, or something like that...
I suppose it would be worth while checking BDALn, BSYNC and BDIN _on the
console card_ (I'm not sure where he was looking at them, before) just to
rule out the broken bus line possibility.
One thing that's bugging me, though; he said "BDAL3-13 .. are all active and
jump around in some manner". But for the ODT microcode loop trying to read the
console CSR, i.e. 0177560, BDAL7 (0200) and BDAL3 (010) should be 0, i.e.
So why are they jumping around too? Is this somehow related to the odd behaviour
I was seeing on my machine with no console card, where the BDAL line was behaving
in a way I couldn't understand?
I'm going to look into that more, to try and understand what I'm seeing there,
but it won't be today, which is 'crane day'!
Apologies for cross-posting. I've added a few new bits and pieces to the
Dick Smith System 80 site. If anyone is interested, take a look at the
first three entries under this link.
Incidentally, this month is somewhat of a milestone. It's 20 years since
the site went live!
Terry Stewart (Tez)
The M7264 CPU thread reminded me of the collection of LSI-11 CPU's that
I have and want to get up and running.? A very useful thread.
This may have been covered some time in the past, but, my question is
"What is the minimum load for the power supply in the BA11-M, -N and
Is it possible to create a load board, like the board you find in the
sbox BA213 VAX's that ensure a minimum load on the power supply?
???? Well we are moving forward.
The 160336 alternate RQDX3 address and vector have been confirmed as OK
by one of our Techno Mages.
So rather than an RX50 I'll give an RX33 whirl. A floppy disk way in
means I can enhance the baseline RT system.
Time to dig out all of the Q-bus controllers and see what else we can add.
I have a Viking SCSI controller. That might be interesting as an
alternative to the CQD.
I think I may have Q bus controllers for my RX01 and RX02. AKA as 'Clonk
11/93 is no end of fun. Best thing since my brother fell in the slurry
pit 60 years ago.
If anybody is interested in building? Jorge Hoppe's Uniprobe, I have some PCB's available. I made a few extra to keep the price down. Price is $40 ea shipped in the CONUS. These have Silver fingers rather than Gold but should still hold up well. Build information is on Retrocomp.
> From: Holm Tiffe
>> The "--list" command to 'dd' gives a whole bunch of stuff:
> $ dd --list
> dd: unknown operand --list
I was talking about the program I had mentioned in the previous email, "dd
for Windows". The "--list" command to it produced that long list of devices
(the list you edited out of the reply), so it definitely works there.
> Nobody in a PDP11 is interested what Windows thinks about partitions.
Understood, but in my previous email I had given an example using a uSloth
>> dd-removable if=UnixRoot of=\\?\Device\Harddisk2\Partition0 count=4872 seek=131072
so when your reply mentioned "partitions" ("You have to have an already
existing parition structure on the disk") it was natural to assume you meant
those - especially since there was a plausible reading of your comment
involving them (i.e. 'does "dd for Windows" only work on a disk with an
existing uSloth partition structure on it').
> Most of the PDP11 SCSI Controllers could build two or more PDP11 disks
> out of one physical device. That is what I meant with partition in this
> case .. There is some logical information on the device, you simply
> don't get the entire raw device on the pdp as you possibly think.
That's a good point, and perhaps there's no existing way to write a SCSI disk
>from a Windoze box in a way that the PDP11 SCSI controllers can grok. I don't
know enough about how they work to answer that.
> Tapes have no such restrictions
Right, but one has to have a tape drive; the OP may not.
I'm in the process of cleaning and hopefully restore to operation of a DEC
The unit has some minor sign of corrosion, however it's VERY dirty, even
inside the hood.
The filters are obviously to be removed and replaced, as they are
Also foam parts between the boards must be replaced.
Aside from obvious parts, there's something that should be replaced /
cleaned inside the HDA (foams, filters or rubbers), which could damage the
disk permanently in case it's turned on after decades if not "cured" before?
Anybody has some good pictures of the HDA inside, after cover removal?