@MSGID: <5ae5ef3375mec@npost.uk> 356ef271
@REPLY: <mpro.s14vmt01az1u4092d.news@stevefryatt.org.uk>
1d8ad126
@REPLYADDR Chris Newman <mec@npost.uk>
@REPLYTO 2:5075/128 Chris Newman
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: <5ae5ef3375mec@npost.uk>
@RFC-References: <5ae42b0daedave@triffid.co.uk>
<11d139e45a.chris@mytardis> <5ae47e494dmec@npost.uk> <192bc3e45a.chris@mytardis>
<mpro.s12u5r00wh2g8042z.news@stevefryatt.org.uk> <5ae556602bmec@npost.uk>
<mpro.s14vmt01az1u4092d.news@stevefryatt.org.uk>
@TZUTC: 0100
@PID: Pluto/3.18 (RISC OS/5.29) NewsHound/v1.54
@TID: FIDOGATE-5.12-ge4e8b94
In article <mpro.s14vmt01az1u4092d.news@stevefryatt.org.uk>, Steve Fryatt
<news@stevefryatt.org.uk> wrote:
> On 17 Sep, Chris Newman wrote in message <5ae556602bmec@npost.uk>:

> > In article <mpro.s12u5r00wh2g8042z.news@stevefryatt.org.uk>, Steve
> > Fryatt <news@stevefryatt.org.uk> wrote:
> > 
> > 
> > 
> > > What matters is where the Inet$MimeMappings variable is pointing:
> > > that`s the *only* file that MimeMap will be using. On the RO5
> > > machine here, it`s set to InetDBase:MimeMap; consequently, looking
> > > up InedDBase$Path
>                                                            
> ^^^^^^^^^^^^^^ Ahem. That should be InetDBase$Path, of course...

> > > tells me where the file is located.
> > 
> > Thanks for the info Steve et al.
> > 
> > How does one go about checking this variable.? Is it a search
> > involving the Task Window?

> (Ctrl-)F12 and then

>   Show Inet*

> should probably cover both variables (and a few others, too). Or you
> could type them out in full, as

>   Show Inet$MimeMappings Show InetDBase$Path

Ta.

-- 
Chris
--- Pluto/3.18 (RISC OS/5.29) NewsHound/v1.54
 * Origin: None (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441