jacobson@uxe.cso.uiuc.edu.UUCP (11/21/87)
I have sent some email to Dave H. but wanted to post this just in case
the mail does not make it (as it many times tends to).
I have a bridgeboard with my 2000 and have a couple of questions about
the use of the virtual drives on the unit. I was wondering if anyone
else had this problem and wondering if it is a bug in vlink?
1) First when I format a virtual drive with the/c switch I don't
seem to get a true listing of bytes free for the dir command. For
example I create a virtual drivvlink c: df1vd /c:870. I should
get 870 bytes free with the dir listing of c: But I get around
1.1 megs of free space. This is not there, for in reality I only
have the 870 I asked for. (I know because I tried to copy more
files beyond 870 K and crashed the system or got a disk full
error every time I tried it).
2) When I have two virtual drives in both my 2010 3.5 inch drives
I also have another problem. I change to the 3.5 assigned to the
C: virtual drive and run a database type program from it. I have
the option of specifying several drives for it to use to look for
data files on. It has no problems reading files on the current
virtual drive C: the program was run from, or reading the A:
drive. But when it reads the D: drive for data it tells me it
cannot find the files and disk it is looking for and to please
put it in. What gives here? MS-DOS recognizes both virtual drives
concurrently as C: and D:. And I can copy files between the two.
But for some reason my database cannot access the files in the
virtual drive unless it is the current directory. I also ran the
program from my A: drive and then it cannot access data in either
C: or D: so it seems that only the MS-DOS A: 5.25 drive and any
current directory on a virtual drive are accessable to this
particular database. It is almost as if the non-current virtual
drive is recognized by my database program as something other than
the volume D: or whatever virtual drive I have assigned it too. Is
there some other sort of volume identification being attached to the
system that the bridge/Amiga recognize as being merely D: or C: but
that some software won't??????
Any help suggestions would bmost appreciated. I supposed once I can
afford a hard drive or another external for the bridge that I will be
able to avoid this bug(limitation?) of the virtual drives created by
VLINK, but til then it would be nice to be able to use two 3.5 virtual
drives rather than putting in many more floppies in A: with my database
Russ Jacobson
Illinois Geological Survey
rm 203, Natural Resources Bldg.
615 E. Peabody Drive
Champaign, IL 61820
217-244-2425
USENET: [ihnp4,pur-ee,convex]!uiucdcs!uiucuxc!uiucuxe!jacobson
ARPANET: jacobsonuiucuxe@a.cs.uiuc.edu
CSNET: jacobsonuiucuxe@uiuc.csnet
:wq