[Virtualacorn-list] Recent versions Config problem

David Pitt pittdj at pittdj.co.uk
Tue Dec 16 08:05:05 GMT 2008


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

[snip]
 
> 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.

The error will come back if the Resolver configuration tool is used. It is a
while ago now but as I recall when I first installed VRPC I was most
gratified to find its networking just worked straight out of the box. If it
is necessary to use the Resolver configuration then simply remove the
ResolverConfig line at the end of the Resolver file.

> 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.

It may be that other network configuration tools cam mess up VRPC's special
arrangements. VRPC makes use of the underlying host, there should be no need
for the user to do anything from within RISC OS. 

> Done some work.
 
Possibly a bit too much, after the new VRPC install what bit of networking
was not working. 

-- 
David Pitt




More information about the Virtualacorn-list mailing list