Not sure of the type or kind or whether it's even old enough, but you figure
it out. reply to person below please
begin pasted text:
>Mohawk Data Systems Mainframe SUPER 21
>old mainframe (HD says "Built in 84")
> Haven't started playing with it yet, has two big floppy drives (10 inch?)
>Monitor, keyboard, 2 printers, cabling, lots of other goodies.
>Make me an offer.
>Don't know if it even works... yet. But.. if it does, the price goes up the
longer I work >on it.
> Judging from the size of the cooling fans on it, it could probably be used
as a >space heater also. <grin>
>Jim jpfenske(a)intrex.net
> 1. Drive starts to spin up, but it's obvious by looking at the spindle of
>the drive motor, that the motor never reaches full speed.
> 2. After about 5 seconds, the drive slows some, and the heads attempt to
>load.
If the drive never reaches full speed, then the heads aren't supposed
to come out. This indicates a problem with the servo control board
(the one near the spindle motor) perhaps.
> 3. The heads then chatter back and forth. They appear to move in about .25
>inches and then retract.
> 4. This continues until I spin down the drive.
>
>If I pull the pack out, and hold the switches closed manually, the motor
>does reach full speed (although the heads never attempt to load).
"Full speed reached" (and speed regulation in general) is controlled
by the little magnetic gap sensor you see near the hub spindle and the
notches in the RL01 cartridge's hub.
>If anyone has any suggestions as to what might be the problem, I really
>apprecite some information.
After the simple mechanical checks others have suggested, I'd
recommend trying a replacement servo control board.
Tim.
<I collect core memory, found a lead to you on the Web.
<
<Got some you wanna part with?
<
<Gary Sloane
<SB/US Engineering Inc.
<sloane(a)sbus.com
What do you do with it once you have it? Many of us collect core but it's
to support working system that were designed for it.
Allison
This is one of those times where "winning" an auction is wild. So I tested
pulled the KA650 (I know the KA655) would be better, and the third party
memory boards out of one of the BA213 chassis and replaced the KA630 and
12MB(4+8MB) of RAM.
Question: The KA650 ram linkage cable has slots for four RAM
boards, the KA630 one has slots for two, I used the KA650's
cable and it hangs over the next couple of Q/Q slots, can I use
the KA630's cable? They seem to have the same number of pins but
I haven't counted.
I power up this puppy and right away it's different because it starts at
#40 and starts counting down. The banner says:
KA650-A V5.3, VMB 2.7
Performing normal system tests.
Then I boot the current image of netbsd on it and it reports 64MB of "real"
memory, so these memory boards are 32MB each not 16MB each. Cool!
Then I power it down, and install one of the TK70 drives in place of the
Exabyte that has been giving me some trouble. Reboot and the kernel finds
the drive and all is well.
Power it down again so that I can button it up, go back into another room
where I'll tip into it without the noise, power it up get the >>> prompt
and type 'b' but it isn't echoed. Go back to the machine room and the vax
is dark and the room smells. Yikes! Turn it off, pull all the boards,
inspect them for damage. There isn't any, turn on the power with only the
CPU board installed, and notice a "light" in the TK70 drive. Now since
there aren't any light bulbs in the drive I look closely and sure enough it
is flames around a resistor in there. Off goes the power, out comes the
TK70, try it again, but no go, the DCOK like don't light and there is still
a vague smell coming from the chassis. Kazowie!
So, does anyone have the printset for the BA123 power supply? I'm pretty
sure the boards survived, the TK70 I'm not so sure about. I sure wish I
knew why it lit up like that.
--Chuck
Last time I said I beat up some PCs, many of you were disturbed. So this
time, I'm warning you before I do it. There are 8 DEC LPv+ 425dx and
433dx machines. They are all 486 DX with RAM from 0 to 16 MB, some have
hard drives around 200 MB, some should have OS/2. They are being thrown
away because they have miscellaneous problems, and we haven't been able
to fix them. I haven't tried, so I don't know what the problems are.
Anyway, first come, first served. Price is 1.2 * shipping.
--- sloane <sloane(a)sbus.com> wrote:
> I collect core memory, found a lead to you on the Web.
>
> Got some you wanna part with?
I might have a core stack that is available. I have some planes from
>from a PDP-8L, part of a 4k x 13 bit memory (12 plus parity). It was
built around 1968.
Offers?
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
In einer eMail vom 04.05.99 21:47:46, schreibt Tony:
<<
> I would certainly appreciate the Diablo pinout - if the pin layout is the
> same, I would expect the signals to be the same , at least something
easier
> to check stan starting from nothing !
OK, here you are. The pin layout on the connector is something like :
A B
C D
E F
H J
K L
M N
P R
S T
U V
W X
Y Z
AA BB
CC DD
EE FF
HH JJ
KK LL
MM NN
PP RR
SS TT
UU VV
WW XX
For a total of 42 pins (I am not sure if that's looking at a plug or a
socket, but it should be a start).
A Read Clock
B Write data and clock
C Read data
D Ground
E Read gate
F Ready to read/write/seek
H Write protect input
J Track select 8's
K Erase gate
L Drive select 1
M High density
N Track select 2's
P Write protect status
R Drive select 2
S Pseudo sector mark
T Track select 64's
U Drive ready
V Drive select 3
W Sector marks
X Track select 16's
Y Index marks
Z Drive select 4
AA Head select
BB Track address 128's
CC Sector address 1's
DD ground
EE Write gate
FF Track select 32's
HH Write check
JJ Sector address 2's
KK Sector address 4's
LL Track select 1's
MM Sector address 8's
NN Address acknowledge
PP +5v for cable terminator
RR Track select 4's
SS Strobe
TT Seek incomplete
UU Sector address 16's
VV Restore
WW ground
XX Illegal address
If you need descriptions of any of those, let me know - I have the full
service manual for the Diablo.
>
> Thanks
> John
>
-tony
>>
That is EXACTLY what I need - the connector has the letters above imprinted,
and the meaning of the signals I have from the DEC docs. This is precisely the
RK-11 Drive Bus.
Thank you _VERY_ much!
Regards
John G. Zabolitzky
>I've heard its possible to "upgrade" a uVAX II to a uVAX III by replacing
>the KA-630 with the KA-650 CPU. Now I've looked at a KA-650 and it has a
>metal cover over its end and a small RJ-xx like plug in it. The KA-630 has
<two IDC connectors that go to the 630CNF console plug in the BA123 world
>box. Do I also need a conversion kit for the KA-650 or is the CPU with
>connectors hiding behind this metal facade?
You have the skunk box (BA213-type cabinet) version of the KA650. The
skunk box deals with FCC compliance by having a metal cover over
each board (or board set). As long as you aren't particularly worried
about neighbors turning you in to the FCC, you're welcome to cable
up the console any way you want. The console bulkhead on the skunk
box KA650 uses DEC MMJ connectors (offset-tab modular pluts) for the
serial cable, a rather standard thing in the DEC world.
You'll also need KA650-compatible memory to go along with the CPU;
KA630 memory doesn't work with the KA650 CPU.
--
Tim Shoppa Email: shoppa(a)trailing-edge.com
Trailing Edge Technology WWW: http://www.trailing-edge.com/
7328 Bradley Blvd Voice: 301-767-5917
Bethesda, MD, USA 20817 Fax: 301-767-5927
I've heard its possible to "upgrade" a uVAX II to a uVAX III by replacing
the KA-630 with the KA-650 CPU. Now I've looked at a KA-650 and it has a
metal cover over its end and a small RJ-xx like plug in it. The KA-630 has
two IDC connectors that go to the 630CNF console plug in the BA123 world
box. Do I also need a conversion kit for the KA-650 or is the CPU with
connectors hiding behind this metal facade?
--Chuck
