X

Mac OS X 10.3.9 (#4): Apple acknowledges Java issues, workarounds; Updating prebinding; more

Mac OS X 10.3.9 (#4): Apple acknowledges Java issues, workarounds; Updating prebinding; more

CNET staff
5 min read

Apple posts Knowledge Base article acknowledging Java issues, solutions Apple has posted a Knowledge Base article confirming issues with Java and Safari under Mac OS X 10.3.9, and has also published two workarounds that were previously reported here on MacFixIt: re-applying Security Update 2005-002 and re-applying the Java 1.4.2 Update 2 package.

More issues solved by using Security Update 2005-002 We continue to receive reports from readers who were successful in resolving a number of issues by re-installing Security Update 2005-002 over Mac OS X 10.3.9.

MacFixIt reader Ian writes: "After installing Mac OS X 10.3.9, I was unable to launch MATLAB v.14 or Maple 9.5, which are both common mathematical applications that I use for my studies. But after following your advice ("The far simpler, and equally effective (in most cases) workaround involves re-applying Security Update 2005-002, which made several significant changes to critical Mac OS X Java components."), I was back up and running."

MacFixIt reader Wiz writes: "Re-applying Security Update 2005-002 has fixed the problem with LiveUpdate. It now runs correctly. No other problems that I can find with Norton AntiVirus at this time."

Updating prebinding Another workaround that has proved useful for a number of Mac OS X 10.3.9 issues is performing a prebinding process with one of a number of maintenance utilities, such as OnyX or sterMachine.

You can also perform this procedure by opening Terminal (located in Applications/Utilities/) and typing this command, followed by the enter key:

sudo update_prebinding -root / -force

MacFIxIt reader Mark writes "I manually updated the prebinding on my 10.3.9 update, and it seems to have resolved a couple of issues listed on the main page... Specifically my java based apps seem to be running OK now (Acquisition, several web based java applets that were not working)."

Checksum error resolved One of the most versatile troubleshooting methods for Mac OS X 10.3.9 and other incremental releases is the re-application of the current combination updater.

Unfortunately, some users initially experienced issues using the Mac OS X 10.3.9 combination updater disk image, receiving a checksum error.

It now appears Apple has rectified the issue, and disk image will download and mount properly without error.

MacFixIt reader Jordan Miller writes:

"The download as of 5 PM (on Tuesday) matches the checksum listed on Apple's page, and verifies and mounts correctly. "

PowerBook/iBook batteries not charging (measuring charge?) properly Several PowerBook and iBook owners are reporting issues with battery charging, or measurement of battery charge.

MacFixIt reader Todd Stubbs writes:

"I set Mac OS X 10.3.9 to install, answered the questions to make sure it was on its way, then went to bed. The next morning my one-month-old 3rd Party battery showed dead. I'm using an old power connection which doesn't have the LED indicators, so I didn't know what was happening, just that it wouldn't charge beyond 1%.

"When I got to work, where I have another power supply WITH the LEDs I could see what was going on. If shut down, then lifted the keyboard of my PowerBook and reset the Power circuits, it would recharge for 3 - 5% then stall. All day long, as I've had time, I've done this to coax it to, currently 70% (It just stalled again. One way I can tell is it reverts to "Calculating" where minutes before it gave a number).

"I have no idea what will happen if I just, unplug it and let it run down to 0% again. Will it let me get it back up to where it was, or will I have to coax it 3 - 5% at a time? Or will it think I only have 3 -5% total power and go to sleep in a few minutes?"

So, it appears in Todd's case that resetting his portable's PMU (power management unit) temporarily resolved the issue.

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

Fix for Norton AntiVirus LiveUpdate issues MacFixIt reader Chris Widmer reports 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.

Chris writes:

"The fix comes via use of the standalone virus definitions installer available on the Symantec site for version 9.0.X. This effectively corrects the Microdefs error that occurs each time if the standalone defs installer is not used."

As noted above, re-applying Security Update 2005-002 has also been a successful workaround for this issue.

Classic: Will not launch, solutions We continue to receive reports from readers who have difficulties launching Classic after upgrading to Mac OS X 10.3.9.

MacFixIt reader John Allen writes:

"I also was unable to launch Classic using my 1 GHz G4 Titanium Powerbook after upgrading from 10.3.8 to 10.3.9 via Software Update. All was well after I reinstalled OS 10.3 from the boot disk and upgraded to Mac OS X 10.3.9 with the full update-combo."

Possible solution #1: Disabling extensions MacFixIt reader Blake Lange reports that temporarily disabling Mac OS 9 extensions -- accomplished by holding down the "Shift" key while Classic is starting up -- allowed Classic to launch properly after initial issues caused by Mac OS X 10.3.9.

Blake writes:

"I have been having the same problem. For some reason holding the Apple + Shift keys while Classic starts up allows it to complete the process. I will do that until a better solution comes along."

After you have disabled extensions and successfully launched Classic, try disabling third-party extensions using the Mac OS 9 Extensions Manager and re-adding them in sets to isolate any potential troublemakers.

Possible solution #2: Re-applying combination updater As noted above, re-applying the Mac OS X 10.3.9 combination updater may resolve this issue in some cases.

FireWire issues A handful of readers are reporting problems with unrecognized, or randomly disconnecting FireWire drives under Mac OS X 10.3.9.

As noted in Apple's upgrade procedure for previous incremental releases, it's best to disconnect any external FireWire drives during installation of the the Mac OS X 10.3.9 update.

MacFixIt reader Spex writes:

"My external firewire drive randomly disconnects itself... despite the fact that I still have disk images mounted from it. (Admittedly they no longer work.)

"The System profile doesn't show the device in its list. If I cycle the power on the drive, it re-mounts. I was foolish enough to leave the drive connected during the update, despite the warnings to the contrary."

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

Resources

  • Knowledge Base article
  • previously reported
  • Security Update 2005-002
  • OnyX
  • sterMachine
  • combination updater
  • let us know
  • standalone virus definitio...
  • Mac OS X 10.3.9 combinatio...
  • More from Late-Breakers