On 26 Jan at 12:40, Rob Kendrick <rjek@netsurf-browser.org> wrote:
> On Sat, Jan 26, 2013 at 09:26:25AM +0000, Tim Powys-Lybbe wrote:
> > On 26 Jan at 1:04, "Alan & Sally" <jared.r@xtra.co.nz> wrote:
> > > The problem is that all the recent versions don't connect to the
> > > internet. The message I get is "Resolving timed out after 30000
> > > milliseconds." The settings are the same ones that 2.9 is using,
> > > so I am at a loss with what to do. Has any one got a fix for this?
> >
> > I have the same problem with RISC OS 6.2 on a Mac OS 10.8.2. My
> > guess is that the modules are not up to date but I have yet to look
> > into it.
>
> I seem to recall that at least at some point that there was an issue
> with VARPC configuring networking correctly, specifically the
> resolver. NetSurf reads the resolver configuration at start up and
> uses its own internal DNS code rather than using the OS's provided
> one. If VA does not set this variable promptly enough (or it gets
> unset somehow) then NetSurf may struggle to resolve.
>
> Are you launching NetSurf at boot? If so, try launching it after
> boot?
>
> I don't recall the names of the environment variables involved to ask
> you to see what they're set to, sorry.
I have disabled Netsurf from being Run at Boot time, then rebooted
VARPC. I then had to revert to version 2.09 of Fetch_NS to avoid
problems with the Download directory. Then I downloaded 833, extracted
and ran it but it still gave the same error about timing out after 3000
millisecs.
--
Tim Powys-Lybbe tim@powys.org
for a miscellany of bygones: http://powys.org/
No comments:
Post a Comment