Talking with other BridgeBoard users I have found that some of them have
avoided using JDisks. Partly some have been misled by the BB manual into
thinking that if they don't unlink the JDisk after using it, they will
corrupt it or won't be able to get rid of it. This isn't the case. Once
you do a reboot, it can be relinked or deleted. Most of the time I never
even bother to unlink it when Iam finished using it.

 Another complaint I've heard was that the harddisk based JDisk was too
slow. The secret of using harddrive based JDisks is to use a large number
of disk buffers (500->800). These can be added by using the AddBuffers
command (eg. AddBuffers dh1: 600). You could add this statement to your
startup sequence or just issue the command from CLI when you need it.

 I have found that the big advantage of using JDisks is that I can setup an
Amiga type CLI environment on the BB. I can make a JDisk in Amiga RAM: and
link it to the PC, say to drive D:. Then I can go to drive D: on the PC
and be operating in a RAM disk environment. Since JDisks can easily be made
of any size, they are much more flexible than PC RAM drives and you don't
have to alter config.sys to create them. Also, since you are using Amiga
memory, you don't lose any PC memory like you would if you created a RAM
drive on the PC. I have found that using the Amiga memory via JDisks is
almost as fast as using PC memory.

  I usually create the JDisk in recoverable ram (in my case VD0:). This way
if the PC crashes, I can do a reset, relink to it to the Amiga recoverable
ram and not lose anything. I have also found them to be  useful when running
programs on the PC that insist on writing to your harddisk before they
will run. I just direct them to the JDisk. Using MakeJD, ReadJD and WriteJD
makes it very easy to create JDisks and transfer data between the Amiga
and the PC. So if you have been avoiding JDisks, give them a try, you might
find that they can really enhance your PC computing.

 Milt