[Virtualacorn-list] Recent versions Config problem

[Dave Symes]

In article <mpro.kbwys80017hye00es.pittdj at pittdj.co.uk>,
   David Pitt <pittdj at pittdj.co.uk> wrote:
> David Pitt <pittdj at pittdj.co.uk> wrote:

> > David Pitt <pittdj at pittdj.co.uk> wrote:
> > 
> > [snip]
> > > VRPC has its own specific networking setup which is not the same as
> > > that on real RiscPCs. I do not know what has gone wrong in this
> > > case, user intervention or incorrect files on the installation CD.
> > 
> > Belay those suggestions, I have just reproduced the "'ResolverConfig'
> > not found" error on VRPC. Though the Resolver file in Hardware
> > Disabled as supplied is correct in terms of VRPC with no mention
> > ResolverConfig the same is not true if that file was overwritten by
> > the configuration tool, !RslvSetup in R0420Hook.
> > 
> > A solution may be to reinstate the Resolver file I pasted into an
> > earlier post and do not use that tool again. This :-

> [snipped] 

> I must get my act together, just after I posted the above, a thought
> popped up. The "'ResolverConfig' not found" error will terminate the
> execution of that part of the boot and Inet$MimeMappings is not set, so
> I am now also seeing the original Filer_Run syntax error. 

Hehe! What a chucklesome time we are having.
Even though I'm aware of, and have been playing with the stuff you mention
in you recent post collection...Thanks for posting the notes anyway, it's
always useful to have another set of ideas.

I can confirm your conclusions as...
Yesterday evening, I did a new virgin install of VRPV-AdjustSA and the
Boot.Config.MimeMap tool worked as it should, additionally at that time
the boot list didn't show the "File Resolverconfig missing" message.

However, after I'd been through the Network setting the missing message
reappeared on the next boot up.

Manually re-editing the file back to its Virgin state, then brings forth
another error message during the next bootup.

"Machine startup has not completed successfully: 'Route: socket: Protocol
not supported'"

Editing back the file, or re doing it from the Boot.Config.Network tool,
makes the message go away.

Anyway, I got fed up with it all yesterday, and left it as it was.

File ResolverConfig not found, remains.
I've re-modified the
HostFS::HardDisc4.$.!Boot.RO420Hook.Res.Configure.!NetSetup.!MMapSetup.!Run
file to force the Set Inet$MimeMappings...

Done some work.
Dave S

--