Xref: utzoo comp.sys.amiga.tech:6423 comp.sys.amiga:37701
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!sun-barr!oliveb!amiga!cbmvax!higgin
From: higgin@cbmvax.UUCP (Paul Higginbottom)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga
Subject: Re: Problems with BridgeBoard, Bad Virtual Dirs
Keywords: BridgeBoard Janus Virtual Bugs Dir Keys
Message-ID: <7504@cbmvax.UUCP>
Date: 2 Aug 89 02:29:01 GMT
References: <626@uranus.UUCP>
Reply-To: higgin@cbmvax.UUCP (Paul Higginbottom)
Organization: Commodore Technology, West Chester, PA
Lines: 68

In article <626@uranus.UUCP> esker@abaa.UUCP (Lawrence Esker) writes:
$...having persistent problems with data integrity on 'JLink' virtual
$drives in the IBM side of the bridgeboard.
$Problem Description:
$It seems that when my brother writes some ibm  [insignificant machine gets
$small letters :-)]  data to an established sub-directory then go off and do
$other operations, the directory keys can get screwed up.  The current data
$files and some of the previous files are inaccessible on his next use of the
$machine.  Many times the entire sub-directory can get lost.  The problem may
$not show up for weeks at a time and he can not localize the data loss to any
$specific sequence of operation.  If a user can't depend on the reliability
$of disk storage, the (ibm virtual drive) system becomes useless.  Does
$anyone share this problem.  Can anyone help? 

Yes.  The JLINK software creates a virtual drive file that must grow
if new data added requires it (i.e., there's no more room with the file
at its current size).  When this occurs, the JANUS software has to open
the virtual drive file and append the new data.  THE FILE ONLY GETS CLOSED
IF YOU DO AN UNLINK!!!  The problem may therefore not exhibit itself if
new data was added but the virtual drive file didn't have to grow (there
was still room left in it due to your deleting some other stuff perhaps).

One fix: add tons of dummy stuff to the virtual drive, then delete it all
then unlink it.  From that point forth the virtual drive should not be
required to grow since it's already huge.

Another fix: using the new JANUS 2.0 software, you can create a [bootable]
DOS drive space on the Amiga hard drive that looks like, smells like [etc.]
a real PC hard drive as far as MS-DOS is concerned.  You even specify
cylinders, heads, etc. for the new MakeAB command that creates the space.
This solution does not require the first fix.

$... Why is a virtual drive on
$the ibm a single Amiga file.  A significant reliability issue IMHO.  A
$single problem can destroy a whole (ibm) disk and DiskDoctor can't help.

The manual recommends that you have a separate partition for the PC
data, to prevent accidental removal of the file, etc.  However, most people
have no problem with just allowing it to coexist with other stuff.

$Is there a way to force PCdisk to complete pending writes once the ibm has 
$crashed, before rebooting it and remounting the virtual drives?  Maybe 
$executing PCdisk a second time?

No - I recommend you use the new software.

$Other Possible Bugs:
$The command AREAD does not seem to transfer data between an Amiga file and a
$virtual drive.

Problems with AREAD/AWRITE have been fixed for the new 2.0 software (they
were re-written).

$(flame on)
$His dealer, Systems Plus at Kenrick Plaza St. Louis, has been totally
$useless.  They also have a habit of charging for every visit just to say "We
$can't find any problem and we're charging $100 to swap the bridgeboard." 
$They also told him that Amiga said dealers could NOT copy the 2286 software
$onto his 2088 disk due to difference in documentation despite being informed
$of Paul H.'s post on the net encouraging it.  My brother intentionally went
$to a dealer instead of (my suggestion) of mail order for the support he is
$not getting now.
$(flame off) 

Thank you for this feedback - I will look into it.

	I hope this helps,
	Paul.