In article <acdcd54550.old_coas...@old_coaster.yahoo.co.uk>, Tony Moore <[email protected]> wrote: > On 2 Apr 2009, Dave Symes <[email protected]> wrote:
> > Updated Netsurf to Yesterdays (1st April) version. > Running the same version here, no problem. > > The message reads "Scanning fonts-please wait" So how many hours does > > one wait while the machine is frozen literally, for this scan to > > finish. > > > > After a substantial amount of time at Times.New.Roman and 88% showing > > on the hourglass the only way I could get control of the machine was a > > back button reset. > Try removing that font from your !Fonts directory. If that solves the > problem it means that something is amiss with the font. Having scanned > the fonts when it is first run, NetSurf stores the result in !Scrap. > Thus, to avoid font-scanning at every start-up, !Scrap should not be > kept in a RAMdisc. After the fonts have been scanned, NetSurf normally > loads in about ten seconds, on a SARPC. > Tony Thanks for the thoughts. But. This is the first time Netsurf has constipated itself with a font scan, and I've been using Netsurf for a long time, updating usually once a week. The font in question has been there for a long time also. I never have !Scrap in a Ramdisk, probably because I *never* have a Ram disk activated. As I mentioned, temporarily switching all my fonts off in EFP, then running Netsurf, then switching the fonts back on sorted that bit 'o constipation. Dave --
