#Bridecard/JLINK
2 messages in this thread
SUCCESSSSSSS!!!!! I was at dealers today looking at the new a2500.He
mentioned that his bridgecard wasn't working since he'd reformatted and
restored his hard drive.I started fooling around and at one point noticed
that during boot when the binddrivers command was executing the IBM sides
drive lite wasn't coming on.
So I went to CLI and ran binddrivers.The Bridges drive lite came on and the
bridge came up.I went to the PCwindow and noticed a line I'd never seen
before "JANUS HANDLER V2.2 FOUND AT E000".I then typed JLINK <return> and
it gave me the status of the drives as it should.Now I ran home with a
bright idea.I deleted JANUS.Library from df0:expansion so the boot
binddrivers wouldn't see the bridgecard.After booting and switching over to
DH1: and assigning all the logical devices to DH1: I placed JANUS.Library
in DH1:Expansion and ran bindrivers.
What do you know!! Upon opening PCWindow I saw "JANUS HANDLER V2.2 FOUND AT
E000". I then managed to jlink to DH2:VIR/msdos /c:2000. What gives? Was
the Amiga System not ready at the original bindrivers command? Does it or
the bridge need time to get their respective **** together before talking
to each other? WHY WASN"T THIS IN THE ALMOST USELESS MANUAL? Anyway I'm
not going to start flaming Commodore.
Next,I seem to remember some threads about filling a JLINKed drive the
first time its used,then throwing out the files you don't need.Is this
correct? I have gone ahead and done so since its such an easy thing to
do.Any other oddities that need mentioning.Also after all of this is
figured out,I'm going to edit together a step by step how and why to upload
here so that some other unfortunate soul dosn't have such a hard time.
Thanks for all the wonderful advice,Allen
Yes…completely fill the JLINKed drive the first time you use it
and then unlink it. Then re-link and delete those files and then start
using the virtual drive normaly.
I suspect what happened is that when you did the binddrivers, right
after that you changed directories and probably made some assigns. As the
bridge starts up, it needs some files…but it takes a while. By the time
it was ready for those files…your assigns now pointed to places where the
files weren't. The thing I'm surpried at is that you were able to use the
Bridge at all. BTW, I also do a separate binddrivers for the bridge once
I'm on the HD. I did it because it was faster than waiting for the floppy
to load the library and boot the Bridge.