Mac OS X 10.3.9 (#6): Terminal fix for Safari Java issues; Problems starting Classic (cont.); more

Safari 1.3

Terminal fix for Java issues Since the release of Mac OS X 10.3.9, we've been covering significant issues with Java -- both in Safari and in Java applications -- caused by the update. After our initial coverage and posting of some successful workarounds, Apple acknowledged the issue with a Knowledge Base article that offers some limited fixes, including those published here.

Now, MacFixIt reader Camillo Lugaresi offers a workaround that can be executed through the Terminal (located in Applications/Utilities), and replicates the fixing mechanism utilized by previous workarounds.

The Terminal commands are as follows (press the "Return" key after each line):

• cd /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Libraries/
• sudo ../Commands/java -Xdump

Camillo explains why this fix works:

"The reason why Java 1.4.2 Update 2 and Security Update 2005-002 can be used to fix the Java issue is that they include the JavaStartup startup item. This startup item rebuilds the Java Shared Archive on the first reboot after the upgrade, and then deletes itself. The commands I suggested above reproduce the exact steps taken by JavaStartup to update the JSA, with the advantage of avoiding a reboot and not requiring any downloads."

iGetter fix coming We previously reported that the iGetter 2.2 Input Manager Bundle is incompatible with the new release of Safari (1.3, included with Mac OS X 10.3.9), causing crashes. To avoid crashing of Safari v1.3 you must uncheck "Add Contextual menu support for Internet browsers" option at iGetter preferences, Integration panel.

Now, the developers of iGetter report that an updated, Mac OS X 10.3.9-compliant release is on the way:

"We're working on a fix of this problem and will release a new version as soon as possible. Note that the 'Integrate with Internet browsers (Watch for URL clicks)' option works well with Safari v1.3."

File saving changes As noted by a number of readers, Safari 1.3 changes the default option from save as to save to download folder. You can still specify the download location by holding down the option key while control-clicking a link.

Flash problems Readers continue to note problems with Macromedia Flash content in Safari 1.3.

One reader writes: "I too am having flash problems. The file just downloads but will not play even though Safari plugins show the Flash plugin is registered. Reinstalling Flash player/plugin doesn't solve the problem either."

For some readers, however, re-installing Flash does provide resolution.

Problems starting Classic (cont.) We previously noted that some users are having problems launching the Classic environment after updating to Mac OS X 10.3.9.

One of our previously suggested workarounds was to temporarily turn off all extensions (by holding down the Shift key while Classic is starting up), then isolate any potentially problematic extensions by restarting Classic with limited sets enabled. However, some readers now report that simply starting Classic with Extensions off once is enough to eliminate subsequent startup problems.

MacFixIt reader David McKinnon writes:

"I also couldn't get Classic to start after installing the 10.3.9 updater on my G4 400 (Sonnet 1Ghz upgrade). However, after successfully starting Classic with extensions off, I restarted Classic with my usual set of extensions no troubles at all."

Meanwhile, MacFixIt reader Don Seher reports that, in his case, the Apple Menu Options extension was causing problems:

"Booted Classic into Extensions Manager. Disabled Apple Menu Options - Classic booted fine. Shut down Classic.

"Trashed Apple Menu Options prefs. Booted Classic into Extensions Manager; enabled 'Apple Menu Options' - Classic wouldn?t boot. Shut down Classic.

"That's enough! I decided that the user can just run Classic without Apple Menu Options."

Symantec releases 10.3.9-compliant LiveUpdate Earlier in the week we noted that using the standalone virus definitions installer from Symantec's Web site fixes a previously reported issue where Norton AntiVirus' LiveUpdate component does not function.

Symantec has now informed us that they have released LiveUpdate 3.0.3, which company representatives say "resolve the problems people were having with updating their Virus Definitions once they upgraded to (Mac OS X) 10.3.9."

To obtain the LiveUpdate 3.0.3 patch (this patch is currently only available for the English version of LiveUpdate 3.0.x):

1. Launch LiveUpdate.
2. Click Customize this Update Session.
3. When a list of available updates appear, remove check marks from all products except LiveUpdate (make sure that the text that appears when you highlight LiveUpdate mentions version 3.0.3).
4. Click Update.
5. When the Summary window appears, quit LiveUpdate (the old

QuickTime stalls We've received reports from a handful of readers who report difficulties playing QuickTime movies after applying the Mac OS X 10.3.9 update.

MacFixIt reader Louis Klidonas, for instance, writes:

"All of a sudden after the update, when I open a movie in Quicktime, I get into the program, but the movie won't play, just that spinning cursor of death.

"Things I've tried: repairing permissions, prebinding, removal of cache, reinstalling 10.3.9, reinstalling Java and that security update that everyone's suggesting. I've also reinstalled Quicktime, nothing!"

If you are having a similar issue please let us know.

Mail service issues (users cannot log in) in Mac OS X 10.3.9 Server; possible solution Several readers have reported a problem where, after applying the Mac OS X 10.3.9 update, the mail server doesn't recognize any user accounts except the administrator. The log says "mail is not enabled for this user" when the user's mail client tries to log in.

Now MacFixIt reader Rob Lews reports a possible solution:

"I had to use Directory Access to make sure the LDAPv3 server was included in the Authentication pane. This fixed the problem."

In order to perform this workaround, first launch Directory Access which is located in the Applications/Utilities folder. Next, click on the "Authentication" pane and change the "Search" option from "Automatic" to "Custom path." Finally, click "Add" and select "/LDAPv3/127.0.0.1" from the resulting pop-up. Apply the settings.

For some users, a restart is required after performing this procedure.

Mail.app performance problems In a problem separate from the one mentioned above, several users are reporting degraded performance in Mail.app under the client version of Mac OS X 10.3.9.

David Miller writes:

"Like others in a Discussion group on Apple's site, I, too, am experiencing horrors using Apple's Mail application under 10.3.9. It worked flawlessly for me under 10.3.8, but it slows down and sometimes comes to a screeching halt when checking for mail. (I am IMAPing to an Exchange server on our campus.)

"My iBook G4 laptop, still using 10.3.8 (thank goodness!) accesses email instantly, while my desktop G4 (using 10.3.9) churns away trying to grab the mail. So, the problem is not with our Exchange server, but, rather, with 10.3.9. I wish I could figure out how to get that system back to 10.3.8." (Ed. -- For reversion instructions, see our tutorial "Reverting to an earlier version of Mac OS X").

If you are experiencing a similar issue, please let us know.

Battery issues (cont.): Third-party units affected We continue to receive reports from users who are experiencing odd battery behavior (unrecognized, not measuring charge, etc.) after upgrading to Mac OS X 10.3.9.

In particular, third-party batteries appear to be affected more than standard Apple units.

MacFixIt reader Les Clark writes:

"I have a Pismo PowerBook that has be operating with 10.3.x with no problem. On Sunday I updated to 10.3.9 and my Newer Tech 7200mAh battery that I purchased in January has stop being recognized. Nether Apples Battery Monitor or the shareware Slim Battery Monitor can recognize the battery any longer. I have a High Capacity Power Products 4800mAh that was purchased a couple of years ago that is still be recognized and charged by the PowerBook. I still have one of my original Apple Batteries and it is also still being recognized by both software programs. When I installed the update to 10.3.9 the Newer Tech was fully charged and I have not run the computer on Battery since that time. [...] I have tried doing a PMU reset and it did not help. Also the LED lights show the battery to not have any charge."

Previous Mac OS X 10.3.9 coverage

• Mac OS X 10.3.9 (#5): FireWire drive mounting problems; More Safari fixes; Firefox; LimeWire; more
• Mac OS X 10.3.9 (#4): Apple acknowledges Java issues, workarounds; Updating prebinding; more
• Mac OS X 10.3.9 (#3): Fixes for Safari crashes, slow performance; Multiple user account issues, solutions; more
• Mac OS X 10.3.9 #2: Safari crashes on launch; Broken JavaScript, java; solutions
• Apple releases Mac OS X 10.3.9, Mac OS X Server 10.3.9

Resources