Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!netcom.com!kientzle
From: kientzle@netcom.com
Subject: Re: Netscape 2.02 or 3.0 on FreeBSD
Message-ID: <kientzleE1C5vt.Mox@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <32865667.232453159@news.qni.com> <328A54AF.35E6@execpc.com> <56ibh2$53m@anorak.utell.net>
Date: Sat, 23 Nov 1996 18:26:16 GMT
Lines: 25
Sender: kientzle@netcom17.netcom.com
In article <56ibh2$53m@anorak.utell.net>,
Brian Somers <brian%anorak.coverform.lan@awfulhak.demon.co.uk> wrote:
>In article <328A54AF.35E6@execpc.com>,
> Con Sultant <jkane@execpc.com> writes:
>: The only "problem" I have is performance. I am am using 3.0 and it
>: takes up to 2 minutes just to start up! Once it gets running, it seems
>: OK, but that wait for it to fire off is boring. It dials out right
>: away, so I know It did start. But, then I have to wait too long for the
>: screen to show up on the screen. I usually don't have something else to
>: do to fill in that time, or I would.
Have you tried changing the default startup?
Under Options -> General -> Appearance -> Startup, I selected
`Browser starts with Blank page.'.
With that, my 486/66 takes only 15 seconds to start NS 3.01. If you're
using auto dialup, you're probably frozen until the dialup completes.
I've noticed that NS completely freezes during DNS lookups(?). If
it's trying to load the first page before it shows the screen, you're
going to be in for a wait.
- Tim