[Virtualacorn-list] Second virtual Hard drive

[Jeremy Nicoll - ml virtualacorn]

Dave Symes <dave at triffid.co.uk> wrote:

>In article <mpro.m29j7b000wa7d0090 at wingsandbeaks.org.uk.invalid>,
>   Jeremy Nicoll - ml virtualacorn <jn.ml.vac.83 at wingsandbeaks.org.uk>
>wrote:
>> Brian Jordan <brian.jordan9 at btinternet.com> wrote:
>
>> >Mine is at:
>> >
>> >C:\ProgramFiles\VirtualAcorn\VirtualRPC-AdjustSA\HardDisc5
>
>> Mine used to be but I moved it out, to a Dropbox folder.  The location of
>> such drives is defined in 
>
>> C:\Program Files\VirtualAcorn\VirtualRPC-AdjustSA\Models\StrongARM RISC
>> OS Adjust (Jit)\Model.cfg
>
>> (or another architecture's corresponding file), in the "[HostFS]"
>> section.
>
>Ah! I think a light is dawning.
>My assumption was, from my obvious misreading of the manual. (Or is it).
>
> Boot-Configure-Discs and set hardDisc to an extra one, and yes up pops a
> new Hardisc icon of 50 Mbytes. Name that as HD5 and Bob's me wotsit...
>
>So what you guys are saying is, created a HD5 directory in the VRPC Win 
>install directory, then point the HostFS Mount/Path at it.

I'm not quite saying that.  There's no need to create anything for a HostFS
mount to exist, because the folder you'll be pretending is a drive is just
an ordinary, already extant, Windows file-system folder.  You can mount any
of your existing Windows folders as a HOSTFS mount if you want; you just
need an entry for each one in the [HostFS] section of the file.  For a while
I had about 6 of them...  

When I moved my HD4 out of C:\Program Files\... to somewhere else all I did
was move the folder (or more accurately its contents) to its new location,
and change the path part of the entry in the config file to point at the new
location.  The mount name (ie "HardDisc4") is just a label for the actual
folder, which need not be named that.  For example I also have:

  mount1 = "PCmyDocs 'C:\Documents and Settings\Laptop\My Documents'" 


ADFS / IDE drives (ie those where one Windows .hdf file represents the whole
drive) are described by a different entry in the config file.  For some
reason VRPC seems to come with only one such file actually defined but has
that file's path described in 'relative' terms (ie starting with ".." which
means go up a directory and then work down into a different one) so eg here
the Risc PC model uses a .hdf stored inside another model's folder.  These
'drives' do need created because, I assume, something has to write their
initial content into them so they can pretend to have an ADFS structure.

-- 
Jeremy C B Nicoll - my opinions are my own.