#Bnd Crash
2 messages in this thread
Don,
I know the expansion and sidecar directories are ok because the pc side
works ok when I boot from a floppy, and because I can jlink to a floppy. And I
compared the hard drive directories to those on the floppy and they are
correct. I've been hearing that the "wait / delay" problem I mentioned earlier
is more associated with the 2090 controller than some of the other controllers.
GVP says they have Seagate drives and can't duplicate this problem. However, I
apparently have an early version of their memory/controller board and we are
currently scrutinizing this. The plot thickens…
Dennis
Dennis,
Maybe I'm presuming too much…or you are missing the point of what I'm
saying…
I presume when you boot from a floppy, it loads the JANUS library and
SIDECAR files from the floppy. If so, that's only telling you there's nothing
wrong with your BridgeBoard.
I also presume that when you boot from the HD, that the HD is already
running since you get to give the BindDrivers command…thus slow or not, on
power on….your HD is already running…so the slow startup of SeaGate drives
would have nothing to do with your GURU…the HD is already started at that
point.
You say you've looked at the files…fine, the files are there, but are
they correct? Have they been corrupted? Have you copied the files from your
floppy to the HD just to make sure they are the same (or run a file compare
program against the files)?
Maybe it would be useful to tell you what happens to the Bridge on
power on. Nothing happens to it…it just sits there until you issue the
binddrivers command. You can issue it on bootup…or 20 minutes later and it
will make no difference…it should boot fine. Once you issue the binddrivers
command…the BridgeBoard starts up an internal test routine…and when it gets
to the drives…(the quick flash of the drive light)…it returns control to
the Amiga so your startup continues.
So…with that in mind, and knowing there is nothing wrong with the
BridgeBoard…that leaves the only difference between you getting a GURU and
not getting one is whether your software is on the floppy or the HD. That
tells me something is wrong with the software on your HD. I presume you don't
remove the HD to boot with the floppy…so the way I see it, you need to make
sure the software is exactly the same on the HD and the floppy.
Make sense? Or are my presumptions about what you are doing wrong?
Don