a. Java problems Many, many readers are reporting problems with loading pages that use Java. Some, although not all, of the problems appear to relate to a conflict (previously reported with the beta version of Communicator) between Communicator and Norton Utilities' CrashGuard - that is still not fixed.
A reader reports that Netscape tech support confirmed this problem, claiming that they just discovered it yesterday. Maybe they should check MacFixIt occasionally! :)
b. Slow launch time and menu dropping speed Two readers (Gregory Morin and Jody Hewell ) commented on how slow Communicator is - especially its launch time and the time it takes for it to drop down a menu. For example, Greg writes: "Using a 12 MB memory allocation in Navigator 4.0.1, after viewing a couple of pages, it takes literally 3 seconds from the time you click on the menu bar to the time the menu actually drops down. I've done this several times and it is very consistent." This has now been confirmed by several other readers.
c. ATR conflict Two readers (Edward Grabner and Vincent Jalby ) report a conflict between Netscape Communicator and Adobe Type Reunion Deluxe 2.0. In particular, you may get a crash if you try to modify the Fonts preferences in Communicator. The work-around is to set Communicator as an incompatible application in the ATR control panel.
d. And more... Robert La Follette reports problems with Communicator displaying colors correctly. Another reader claimed that he was unable to get password-protected pages to load with Communicator. In both cases, reverting back to Navigator worked.
Finally, today's MRP has an extensive item on issues and problems surrounding Communicator.