Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!doc.ic.ac.uk!sot-ecs!snb90
From: snb90@ecs.soton.ac.uk (Brodie SN)
Newsgroups: comp.sys.acorn
Subject: Re: Free space
Keywords: free space
Message-ID: <7284@ecs.soton.ac.uk>
Date: 22 Mar 91 12:00:34 GMT
References: <7151@ecs.soton.ac.uk> <1991Mar18.231818.10508@comp.vuw.ac.nz>
Sender: news@ecs.soton.ac.uk
Lines: 22

Julian.Wright@comp.vuw.ac.nz (John Julian Wright) writes:

>  2) Know the filing system's SWI prefix, in order to call FSPrefix_FreeSpace,
>     which in turn calls FileCore_FreeSpace.

> (2) is clumsy, as there is no way of knowing the SWI prefix for a new,
> as-yet-unwritten FS is. VKiller suffered from this problem a while ago 
> when guessing the prefix for SCSIFS and getting it wrong!

THERE IS A WAY!!! (but it's a cludj)

  Make a text file for the application containing all the SWI prefixs
known at time of writing.  The user can update the list when new filing
systems are brought out.  However, the clever bit is then using the
OS_ConvertSWINumberFromName or whatever it is with FSPrefix_0 as the
name. If this call succeeds, you know that that particular FS is
present, and can do processing on it!

Not a great solution really, but it can get round the problem a bit.
**
Stewart Brodie
(snb90@uk.ac.soton.ecs)