Well I gotta say it's great that someone out there is getting a 2000 up and running! I used to work at HP and know a few good hardware guys who might be willing to help you out. Also, if your interested I could ask a few of my old friends to scour their attics and basements for any paper tapes, sleep/hib tapes, or manuals for you...let me know.
Also, I have a trivia question for you...what commands were used to add and remove files from the drum disk drive?
Mike
On Jan 6, 17:52, Tom Leffingwell wrote:
> On Sun, 6 Jan 2002, Pete Turnbull wrote:
>
> > Many of the QBus processors have a set of terminators on the CPU card,
> I guess this explains why my system has no BDV11 board in it. Although
it
> doesn't completely work either.
What doesn't work about it? What's on the backplane apart from your 11/23
and MSV11-L, and in what order?
--
Pete Peter Turnbull
Network Manager
University of York
On Jan 6, 17:58, Tom Leffingwell wrote:
>
> Does anyone have a list of the function of the switch settings on
> the PDP DRV11-B / M7950 card?
The smaller switch, S1, controls the vector. S1-1 to S1-8 correspond to
bits 9 to 2 of the vector, respectively. ON sets a '1' in the
corresponding bit position. Default is OFF, OFF, OFF, ON, OFF, ON, OFF, ON
= 00010101 which gives a vector of 000124.
The larger switch, S2, controls the base address. The DRV11-B has 5
registers, with factory-standard addresses as follows:
WCR Word Count Register 772410
BAR Bus Address Register 772412
CSR Control and Status Register 772414
IDBR Input Data Buffer Register 772416
ODBR Output Data Buffer Register 772420
Note that the CSR is not the first address.
S2-1 to S2-10 correspond to bits 12 to 3 in the base address. ON sets a
'1' in the corresponding bit position. Bits 15-13 are fixed at '1'.
Default is ON, OFF, ON, OFF, ON, OFF, OFF, OFF, OFF, ON = 1010100001,
which gives 172410 (corresponds to 772410 with 18-bit addressing).
--
Pete Peter Turnbull
Network Manager
University of York
On Jan 6, 22:32, SP wrote:
> * Somebody spoke about a possible modification of the U55 chip.
If that was me, I picked the wrong chip. The one that's usually changed,
to give a different address, is the PROM at U38, 91265D -> 91578A.
> 25U-91353
> 69U-91354A
> 64U-91355
> 21U-91356
> 22U-91357
> 55U-91358
Those all look standard to me. Anyone else got a DQ614 to compare?
> The question is: Could be used some XXDP diagnostic to determine
> the possible problem of the board that I told in my previous message
> about it ?
It might work. It might not. The DEC diagnostics make use of specific
facilities in the RLV (QBus) controllers that aren't in the RL (Unibus)
controllers, and may or may not be in a 3rd party device. The early
diagnostics only cover RL01s and RL11/RLV11:
ZRLA?? Controller Test Part 1
ZRLB?? Controller Test Part 2
ZRLC?? Drive Test Part 1
ZRLD?? Drive Test Part 2
ZRLE?? Performance Exerciser
ZRLF?? Compatibility Test
where ?? means any revision (a single letter) and any patch level (single
digit), as usual for XXDP.
The Performance Exerciser would probably work *once the disk is formatted*,
as it just does a lot of read/write/seek tests. The compatibility test is
pointless for a DQ614 as it tests moving packs between drives.
The later diagnostics are for RLO1s or RL02s and RL11/RLV11/RLV12. There's
an extra program to allow you to read and write the Bad Sector Table which
exists on a real RL02:
ZRLG?? Controller Test Part 1
ZRLH?? Controller Test Part 2
ZRLI?? Drive Test Part 1
ZRLJ?? Drive Test Part 2
ZRLK?? Performance Exerciser
ZRLL?? Compatibility Test
ZRLM?? Bad Sector Utility
Finally, there's a pair of diskless tests written specifically to cope with
differences between Unibus and QBus controllers:
VRLA?? Diskless Test 1
VRLB?? Diskless Test 2
--
Pete Peter Turnbull
Network Manager
University of York
Someone privately wrote:
> Sorry I dont use Winblowz. However, if you send
> me a copy of those I'll convert them to a pdf
> for you.
I gave the filename to both Jay West and Hans B Pufal
so the files should be available soon and anyone can
grab them. I'm limited to email attachments of 2MB or
less. And even uploading them to my web site took 17
minutes at 145 Kbps.
Actually, I asked about compression and generating
.PDFs for use with other documents I have scanned.
I'm up to my hips in scanned pages from manuals
that I would love to compress and wrap. I hate
sending someone scanned pages to use as a reference.
Regards,
--Doug
=========================================
Doug Coward
@ home in Poulsbo, WA
Analog Computer Online Museum and History Center
http://dcoward.best.vwh.net/analog
Analogrechner, calculateur analogique,
calcolatore analogico, analoogrekenaar,
komputer analogowy, analog bilgisayar,
kampiutere ghiyasi, analoge computer.
=========================================
On Jan 6, 15:37, Ben Franchuk wrote:
> Pete Turnbull wrote:
> > suspect that's because the 'bot is too good, and it's actually hard to
post
> > as a newcomer, so interest has dropped off. The last few times I tried
to
> > post, my posts bounced, and attempts to contact the human moderators
> > failed. Maybe I was just unlucky.
> I suspect the bot was there because of all the OT 'PC' posts - buy a
> pentium
> abc computer.The news group is still active, as there was a posting
> yesterday.
achh died because of the huge number of posts from people who had bought a
motherboard, case, and video card and wanted help to make it work. We
referred to them as those who belonged on "alt.fix.my.peecee" or similar.
There were some amazing arguments between newcomers, who thought such
lamers should get a polite answer including a solution, and veterans who
argued that doing so reduced the S/N ratio and encouraged even more OT
crap, and that people should read the guidelines. Doubtless some members
of classiccmp will remember Leon Heller. And, yes, that is exactly why the
'bot was employed (it had been tried on achh, but since that wasn't
moderated, it had to be a retro-active cancelbot, rather than an
approvalbot).
As for active, well, yes, I saw the post. And all the others; there must
have been at least ten posts in the last 6 months. Not a very busy group
these days :-(
--
Pete Peter Turnbull
Network Manager
University of York
In a message dated 05/01/02 mhstein(a)usa.net writes:
> I've got a T3100e, so this may be irrelevant, but FWIW:
>
> Just had to replace the Li battery in mine; cost $15
> the last time, $25 today. Since there was just enough
> room in there for 2 alkaline AAs in a holder, I thought
> I'd give that a try; seems to be working fine so far,
> despite being only 3V instead of 3.6V.
Thanks for the tip Mike. I had intended to fit some NiCds but opted for two
AAA alkaline cells. They've done the job and fit nicely under the keyboard.
> Re the HD: when mine failed a few years back, I heard
> lots of info that it was an ST-512 drive with a special
> connector. Apparently not; installed a standard 80Mb
> (MB? mb? mB? :) IDE drive, Disk Manager to get around
> the fixed drive type, and Bob's your uncle.
>
> Good luck with the cleanup.
>
> mike
>
Luckily the HD is OK. The floppy drive occasionally throws up seek errors
and I haven't been able to clean all of the crud off the head stepper motor.
I've found a source of replacement drives in the UK and at very reasonable
prices.
Cleaned up the mother board with warm water, detergent and a stiff brush,
then let it bake in the oven at 70C for an hour. Had to use a small grinder
and a wire brush on some of the metal work. Installed DOS and I now have
a happy computer :-)
Best Regards
Chris
On Jan 6, 21:44, The Wanderer wrote:
> Pete Turnbull wrote:
> I actually did mean that I exchanged them for 2 other, identical boards.
Ah, I see. Sorry, I made the wrong interpretation there :-)
> I did, all the jumpers are where the are supposed to be.
OK. From what you've written there, and a few other places, I assume you
have some manuals and/or printsets?
> At the bottom of the console in the metal fram, there is a small
> pushbutton made which leads directly to the M9312 tab1 & tab2.
> This looks like a 'push button' bootstrap and the previous owner
> made it apparently to have a quick (re)start of the machine when
> needed.
That makes sense. On an M9312, it simulates a power-down and then
power-up.
> > > Also memory location 400000 through 477777 are accessible via the
> > > console and
> > > I can dump data and read from it.
> >
> > That's an unusual address, and it's only 32K bytes (16KW). You said
you
> > had two 64KW boards. What type are they? They probably have switches
to
> > set their base addresses. Are these set correctly? It would be worth
>
> There are 2 M8728 boards in the memory box.
Are they M8728-AA or M8728-CA? The latter is only 16KW. The easy way to
tell the difference, if there's no -A or -C beside the number, is that on
etch revision B and higher, the 64KW board is fully populated with 64K
DRAM, while the 16KW is only partly populated. I suspect there might once
have been a fully-populated 16KW version that used 4K DRAMs, though.
I was, no surprise to anyone, wrong about their having switches -- showing
my ignorance about the specifics of 11/70's. Most of the things I've
written are gleaned from the meagre information in one or two of the
processor handbooks, or from my (incomplete) collection of microfiche.
Anyway, the memory box has switches on the front (and I assume you've
checked those?) but as far as I can see from the 'fiche, the memory card
base addresses depend only on their position in the box. So the two cards
have to be adjacent, and nearest the other cards, I think. Do you agree?
It looks as though the box might be set to the wrong address -- 400000 is
131072 decimal, or 128K -- and is only showing 16KW (32KB) of memory. I
don't know how you set the address of the box, though.
> > > At 344 (addr) and 116 in the data display. No idea if this a valid
value
> > > though...
[...]
> It is the 23-233F1 diag rom.
OK, I've found some data (actually the listing) for that ROM. It's
assembled at 165000 (but it looks like position-independant code, so that's
possibly not its real address). It ends at 165776, ie 1000 bytes (octal)
later. It is indeed an 11/70 diagnostic ROM for the M9312, probably just a
later version than the 23-616F1 my other docs refer to.
The docs say there's no way to enter the diagnostics directly, only by
entering a bootstrap at the "run with diagnostics" address. They suggest
that would be 173006/173206/173406/173606 depending on whether you're
booting from a bootstrap ROM in socket 1, 2, 3 or 4.
The docs also say that when the 11/70 powers up (or you press a boot switch
attached to TP1 and TP2 on the M9312), it loads the PC from address 773024,
and PSW from 773026. And indeed every boot ROM has a reserved word at that
address for the PC, followed by 000340, which is the usual interrupt mask
to set in the PSW for booting. Every ROM has code (opcode SEC) starting at
173x04 leading to a BCC BDIAG at 173020. In every boot ROM, that branch
goes to an absolute jump, JMP @#DIAG, which in turn leads to a PC-relative
jump at absolute address 165564, which goes to 165000 (the actual code is
165564 000167 177210 DIAG: JMP START).
Why do you think address 777644 is the diagnostics ROM start address?
All the 11/70 tests halt on error (unlike the CPU diagnostics for the 11/34
and other processors, which loop on error). The first section tests
assorted instructions that needn't to use memory, the secondary CPU tests
use the stack (R6 set to 000776). However, the very first instructions in
the diagnostics code store registers at 000700...000704, and use 000706 to
hold a flag which tells the code whether it's running on an 11/60 or an
11/70. If the memory isn't working, this will cause problems later in the
diagnostics.
Address 165344 is one of the error halts partway through the secondary CPU
tests (assuming the diag ROM starts at 165000). What it does is set
SP=776, then does a PC-relative JSR to the address 2 ahead of where it is.
The code there checks to see if the top of the stack contains the correct
return address, and should halt at 165326 if it doesn't (it should halt at
165320 if the JSR didn't execute). If it does see the correect return
address, it adjusts the stack contents, does an RTS, ending up at 165342.
At 165342, it pushes a zero and an address on the stack and then tests
RTI. 165344 is the address of the push instruction, and 165350 is the RTI.
That's folowed by a jump to the next test, which is the memory-sizing
routine.
So having it loop until you stop it, and then halt at some address ending
in 344 doesn't make much sense to me. Either you're not starting at a
sensible address, or there's something wrong that is sending it into a
loop. That could be a CPU fault, or maybe (I've not read all the cache
test code) something to do with not having memory between 000700 and
001000.
--
Pete Peter Turnbull
Network Manager
University of York
On Jan 6, 11:20, John Allain wrote:
> (comp.arch.hobbyist)
> > The last few times I tried to post, my posts bounced
> > -- Pete T
>
> Well, I must say, Pete, that your posts here are among
> the most valuable, from my point of view.
<blush> Thank you! They'd be even better if I learned to always engage
the brain before putting the keyboard in gear...
--
Pete Peter Turnbull
Network Manager
University of York
On Jan 5, 23:24, Lanny Cox wrote:
> I loved alt.comp.hardware.homebuilt... only lurked there, but it was
> sweet... are there any newer alternatives out there these days?
You probably remember that the rapidly-increasing number of off-topic posts
led to a variety of attempted solutions. That culminated in the creation
of a moderated group, comp.arch.hobbyist. The moderation is done by a
'bot, with human backup, but the group traffic level is very low. I
suspect that's because the 'bot is too good, and it's actually hard to post
as a newcomer, so interest has dropped off. The last few times I tried to
post, my posts bounced, and attempts to contact the human moderators
failed. Maybe I was just unlucky. Anyway, you'll find the FAQ and charter
on Mark Sokos' website, http://home.supernet.com/~sokos/cahfaq.htm although
it's seriously out of date and a lot of the links are broken.
--
Pete Peter Turnbull
Network Manager
University of York
