#Bridgeboard Blues
13 messages in this thread
Hello all.
I have a problem here that I'd like some help with. A couple of weeks ago, my
Quantum 210 failed and ate the connector for the +5 Volts. I have since
replaced both the connector and and the hard drive. The power supply seems
fine according to voltage readings under full load.
However, I am left with one problem still. There is something wrong with the
bridgeboard, and I can't figure it out. I have since reinstalled the software
from the Janus 2.1 disk onto a FFS partition and have restored all of the
virtual devices it expects according to aboot.ctrl. So far, no joy on booting
the IBM side of things. When I double-click on my Mono, or any!, icon, I get
the dreaded cannot load Janus.library message. The library file is in the
Expansion directory of my boot drive (as is gvpscsi for the hard drive). The
partition aboot.ctrl points to is a pcdisk.device controlled device. However,
even when I use standard formatting, either via Janus or CrossDos, I still get
the same message.
Things that I have done: I have deleted 2500prefs; I have changed, and
deleted, aboot.ctrl according to circumstances. I have re-installed the Janus
2.1 software (although I can't do that again; the drive ate the disk the
second time around; since replaced). I have editted my startup-sequence from
the current configuration to the default C= s-s, to everything in between.
Frankly, I can't think of anything I missed, but I thought I'd ask around. BTW,
on the hardware front, the BB has proper voltages tp all pins. So, can any of
you think of something I might of missed? Please!?
As an aside, if anyone has a copy of the Janus 2.1 disk for the Amiga side, let
me know. I need a new copy. [And yes, it may be copyrighted, but it is
useless to anyone that hasn't bought a bridgeboard.] I'll pay shipping and
cost of a replacement disk.
Thanks.
Brian,
It doesn't have anything to do with Aboot.Ctrl. The "can't find Janus.Library"
means the Bridgeboard isn't booting, let alone looking for its hard drive. It
sounds as if you have a 2500. Do you have "Enforcer Quiet" or "CPU nodatacache"
in the startup-sequence (before Binddrivers)? Also, have you looked in the
Expansion drawer to make sure the Janus.Library is there and intact? Also, is
it possible the BB shifted in its slot when you replaced the hard drive. You
might try pulling it and reseating it. (The first is the most likely.)
Marion Deland
CROSSINGS – Newsletter for Amiga/PC/Mac compatibility
Marion,
I've pulled and reseated the BB several times. I also cleaned the contacts at
the edge of the board. Janus.library is in the expansion drawer and I have
both enforcer and CPU nodatacache (a bit of overkill ;-). Any other ideas?
Sounds like you've done all the right things. What blew up your drive? I hate
to say it, but could it have taken out the BB too?
Marion Deland
CROSSINGS – Newsletter for Amiga/PC/Mac compatibility
Marion,
the drive itself blew up and tried to eat the +5VDC power supply.
Fortunately, the connector to the motherboard failed before the power supply,
else I'd be looking for one of those as well. I'm beginning to think it took
out something on the bridgeboard, but I can't be certain. It could also be a
motherboard problem. After all, the signals and power comes from there,
although the power provided does look good.
Time to start yanking chips and pray that they fix it. Thanks for your
advice.
Brian,
You're pretty handy with electronics…so try this:
Pull the BB and then one at a time, pull the translator chips (the
large square chips)…SLIGHTLY bend out the ribbon leads on the chips and then
re-install them.
Put you BB back in and make sure the board is fully seated, front and
back in the slot.
Now try it.
If that doesn't work, copy your sys:pc directory off to somewhere else
and delete both janus.library and janus.library.info from your expansion
drawer. Do a re-install of the BB software (yes…I know, you need a new
disk).
See what happens then.
If that doesn't do it…you may have lost your dual-ported RAM. on the
BB.
Don
Don,
I have no idea which chips are the translator chips. All of the square
chips on my A2386 are soldered down, so removal would be problematic <grin>. I
did blow away the Sys:PC directory, so I don't think that is a problem. I'm
working from a backup for now, although it'd be nice to have a 2.1 Janus
diskette.
As for your suggestion wrt the dual-port ram, it wouldn't suprise me if it
was at fault. It was, afterall, the +5VDC line that took the hit. I'm going to
try to swap around the chips, as much as possible, before I write this off.
Thanks. Very good suggestions.
Brian,
Ok…I was thinking of the older BB's with the non-socketed chips, with
the soldered chips…it's not an issue <grin>.
Don
Brian,
Is it possible that the original short problem might have damaged the
BB? Do you know that the BB is actually undamaged? Although the power supply
may be operating, the electrical problem may have resulted in serious chip
damage on the BB. I'd check it out. If someone else has a BB setup, you might
try swapping the card and see if yours is even alive.
Steven,
that is what I'm beginning to suspect. I have a few chips to swap and
try, but it is probably dead. Thanks.
Steven,
I'm tacking this on here, but it is for ALL. I've yanked all of the
memory chips and the problem still persists. It is obviously a BB problem well
out of the scope of fixing it by hand. Thanks all for the help.
I do hope the rest of the restoration will be easier.
Brian,
It sounds like "BINDDRIVERS" is missing from your startup.
Les from Bayonne, NJ via Auto Pilot 1.77
-TTFN
Les,
nope, it is there and it is a virgin copy, so that isn't it. Thanks
though.