Return to BSD News archive
Newsgroups: comp.os.linux.x,comp.unix.bsd.freebsd.misc,comp.infosystems.www.browsers.x Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news2.acs.oakland.edu!condor.ic.net!news.cic.net!chi-news.cic.net!news.math.psu.edu!news.cse.psu.edu!uwm.edu!news-res.gsl.net!news.gsl.net!news.mathworks.com!uhog.mit.edu!uw-beaver!yeahwell.cs.washington.edu!cbh From: cbh@cs.washington.edu (craig horman) Subject: Fix for Netscape v3.0x java / appletclassloader problem X-Newsreader: TIN [version 1.2 PL2] Sender: news@beaver.cs.washington.edu (USENET News System) Organization: Computer Science & Engineering, U of Washington, Seattle Lines: 28 Message-ID: <Du37Eu.45H@beaver.cs.washington.edu> X-Nntp-Posting-Host: yeahwell.cs.washington.edu Date: Fri, 5 Jul 1996 20:25:42 GMT Xref: euryale.cc.adfa.oz.au comp.os.linux.x:35109 comp.unix.bsd.freebsd.misc:22905 comp.infosystems.www.browsers.x:5855 After fiddling with the now-familiar `couldn't create AppletClassLoader' error issued by Netscape 3.0b* for too many hours (an strace'd Netscape is not a pretty thing to watch), I think I've found a solution to the problem. At least, I was able to cure it on two Linux boxes. Previous posts to comp.infosystems.www.browsers.x, comp.os.linux.x, and comp.unix.bsd.freebsd.misc advised that the fonts directory (fonts.dir) in X11R6/lib/fonts/misc needed to be re-generated (via mkfontdir). This solution did not work for me, although others indicated it worked for them. I did find, however, that my misc/fonts.alias file contained many entries corresponding to fonts I do not have. Renaming the file, rehashing the font path (xset fp rehash), and restarting Netscape resulted in an instance of Netscape that was able to run java applets successfully. Not wanting to lose all my misc font aliases, though, and also not wanting to spend any more time validating each entry, i just stripped out the `jis' fonts from fonts.alias (i have very few japanese fonts). In short, it appears (at least for me) that making sure misc/fonts.alias contains valid entries cures the problem. Drop me a line if this works for you; I'm curious. regards, craig