[comp.sys.amiga] Jlink and Supra HDs

DMasterson@cup.portal.com (David Scott Masterson) (03/27/89)

Howdy,

I've just recently started hooking my B2000 up with a Supra controller to an
Adaptec 4070 and two RLL drives (ST277 & ST238).  I had some problems
originally with connections, but now its seems to be going quite well (boots
quite fast! :-).  I also have a Bridgeboard in my system and am now trying to
reset that up (originally, I was using an RLL controller on the Bridge side)
with Jlink.  That's where I seem to be running into trouble.

Following the Users Guide for the 2088, I can Jlink to a RAM file with no
problem (at least that I've run into so far), but talking to the hard drive
is another problem.  Using the following command causes Jlink to start
accessing the Bridge A: drive (for Jlink, I guess) and then it starts slowly
writing over the PC window (while still accessing the A: drive):

		jlink e: di2:vd /c:1000

At this point, the Bridge side locks up (CTRL-ALT-DEL won't reset it), but
the Amiga side is still ok.  After resetting the Amiga, I find an empty file
for di2:vd.  As I said, though, the above jlink command with 'ram' instead of
'di2' works fine.

Anyone have any ideas?  Is Supra's methodology for the hard drive
incompatible with Jlink (I noticed no new device drivers in the Expansion
directory).  Is Jlink just not as solid as the Users Guide would make you
think? (that's not a flame, just an honest question).

David Masterson
DMasterson@cup.portal.com