• On CBS MoneyWatch: Report: DON'T Buy the iPhone 4
advertisement
March 15, 2007 8:30 AM PDT

Mac OS X 10.4.9 (#3): WWAN update included, how to remove; When a startup failure isn't actually a startup failure; more

by CNET staff

WWAN update included, how to remove It appears that Mac OS X 10.4.9 makes the same modifications that are contained in the WWAN Support 1.0 update, which was released February 19th and is intended to enhance support for various EVDO and HSDPA devices.

This is bad news for some Australian and European users of high-speed wireless data networks, for whom device usage problems ensued after applying the WWAN Support 1.0 update: the same device issues are occurring for these users after installing Mac OS X 10.4.9.

As previously reported, the fix for this issue is to remove the following files:

  • /Library/Modem Scripts/WWAN Support
  • /System/Library/CoreServices/Menu Extras/WWAN.menu
  • /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/AppleWWANSupport.kext
  • /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/AppleWWANVerizon.kext

then re-install the driver available from your wireless access device's manufacturer (e.g. Novatel's driver for the Merlin XU870). The last two files are tricky -- the best way to delete them is to navigate to /System/Library/Extensions/, then locate the file IOSerialFamily.kext. Control-click (or right-click) on this file, and select "Show Package contents."

Once inside IOSerialFamily.kext, navigate to /Contents/PlugIns/. Drag both AppleWWANSupport.kext and AppleWWANVerizon.kext to the Trash (you will be prompted for your administrator password).

For a screenshot and more information on this fix, see our previous article.

When a startup failure isn't actually a startup failure As we've stressed numerous times (and in our initial recommendations for applying Mac OS X 10.4.9), the first startup after installing an incremental Mac OS X update can be extraordinarily long -- up to 10 minutes in some cases. Allow a generous portion of time before concluding that your startup process has actually stalled indefinitely on the first restart after updating. If indeed the stall is permanent (you've waited 15 minutes or more), your first course of action should be to attempt startup in safe mode (hold the "shift" key while your Mac is booting), then follow the procedures outline in our tutorial "Startup fails (particularly after a system or security update); solving"

Segmentation faults Some users are reporting segmentation faults -- a fatal application error in Mac OS X -- after the update to 10.4.9.

Joakim Edsjo writes:

"I have a problem with segmentation faults after the update. At least ssh and kinit now dies with 'Segmentation fault'. They worked before the update. I am running on a MacBook Pro 2.33 GHz Intel Core 2 Duo."

This issue may be soluble through re-application of the Mac OS X 10.4.9 combo updater. Download links are as follows:

  • Mac OS X 10.4.9 Update Intel, Combo [310 MB]
  • Mac OS X 10.4.9 Update PowerPC, Combo [163MB]
  • Mac OS X Server Update 10.4.9 Intel, Combo [350 MB]
  • Mac OS X Server Update 10.4.9 PowerPC, Combo [216MB]

iSync issues/general synchronization Several users are reporting problems synchronizing with devices through iSync and other synchronization applications.

MacFixIt reader Les Crozier writes:

"I can no longer sync with my Motorola V3 via bluetooth on my 17 inch Core 2 Duo iMac: '[Motorola V3] An unexpected error occurred. Device 'Motorola V3' synchronization failed'"
Another adds:

"After the update I can't use iSync, or .Mac syncing. What a headache."

David Rizzo reports issues with Mark/Space Missing Sync:

"After upgrading to Mac OS X 10.49 via software update and performing my first sync between my Treo 650 and my Powerbook G4 using Mark/Space's Missing Sync for Palm OS I encountered 24 sync conflicts for items I have been able to successfully sync for months. The conflict dialog does not adequately give enough information to tell the user which item has the correct information, so choosing which is correct is troublesome. The conflicts all occurred with repeating events. The end result is my iCal and my Treo calendars were completely screwed up.  Fortunately I was able to recover my iCal from my iDisk daily back-up and after many syncs got the Palm & iCal to match up again. 

"At the time of this email there were other posts in the Mark/Space forums indicating similar problems, so I know this is not an isolated incident. Only one Mark/Space response recommended choosing iCal to correct all sync conflicts."

In order to potentially obviate some Palm synchronization problems under Mac OS X 10.4.9, set your conduit software (including MIssing Sync) to "Macintosh overwrites handheld" before your first sync.

Microsoft Office Users are reporting a few issues with Microsoft Office applications after the update.

Microsoft Word: Problems saving One MacFixIt reader reports problems saving documents in Word.

"After installing the latest OS X upgrade I cannot get word to save or save as an existing document. Using Microsoft Word 2004 for Mac, Version 11.3 (070131)."

Entourage: Problems synchronizing with devices Another reader reports issues with synchronizing devices with the Entourage database.

"The only problem I have so far is with syncing calendar items between the TREO and Entourage.  For some reason, many appointments now have a different time zone then Central (which they used to). So I needed to clean them up in Entourage.  It didn't occur to every appointment.

"Also - when I create an appointment on my Treo and sync, it now shows up in a different time zone than the TREO shows. The Treo shows CST but in Entourage it appears as Mexico (2 hours different).

"It's easily corrected in Entourage - but a little of pain.  This never occurred before the update."

If you are experiencing similar problems, please let us know.

Previous coverage:

Resources

  • previously reported
  • previous article
  • recommendations
  • "Startup fails (particularly after a system or security update); solving"
  • [310 MB]
  • [163MB]
  • [350 MB]
  • [216MB]
  • let us know
  • Mac OS X 10.4.9 (#2): Prin...
  • Mac OS X 10.4.9 released: ...
  • More from Late-Breakers
  • Recent posts from MacFixIt
    iTunes 10 user interface sees some minor changes
    Apple seeds iOS 4.1 Gold Master to developers
    Possible fix for Harman Kardon iSub problems with PowerPC Macs
    Precautions to take before installing iTunes 10
    A reminder on how to reset your Mac's system password
    Mail messages appearing blank
    Adobe Lightroom update brings direct Facebook publishing; Camera Raw 6.2 released
    Weekly troubleshooting utilities update
    Add a Comment (Log in or register)
    by Budjoco March 15, 2007 2:56 PM PDT
    After update I can no longer iSync my Motorola V551 with my computer flat 15" screen G4 800 512meg ram 10.4.9

    E. C. Spitzer
    Reply to this comment
    by March 17, 2007 12:50 PM PDT
    I have a problem... I installed the OS X 10.4.9 update along with the iTunes update on a G5 PPC desktop. The following is what happened next as far as I can remember. The iTunes update did not go through and sent a message that it was being trashed... Following this I restarted my computer since the OS X update required it. My computer failed to restart... showing a folder with alternating question mark and apple face logo. I proceded to startup from the OS X Tiger CD... it failed to restart instead leading me into the reinstallation of the operating system. From there I accessed the Disk Utility feature and verified my hard disk... it displayed an error "invalid node structure " that needed repair. I proceeded to repair it with the disk utility. Shortly after starting the repair, the process stopped. It displayed Error: the underlying task reported failure on exit (-9972). Unfortunately, this was the last time I saw my hard drive mounted. It has now become invisible at least as far as a reinstall is concerned... I also tried a third party disk utility... "Check It" system performance suite. It was unable to repair the disk. The hard drive seems to pass the 'read write', 's.m.a.r.t.' and 'disk controller' test. The 'surface scan' test finds plenty of bad blocks. That's all I have as of now. I also tried using the HD as a target Firewire HD with a laptop as the host but it failed to mount on the desktop. I would settle for a backdoor way of retrieving my data. Can anyone help?
    Reply to this comment