Apple releases Mac OS X 10.4.6 Update - Page 2

Unless someone beat me to it.... Obligatory "It's snappier!" post

They still havent fixed the dmproxy bug though. It happened to me once sometime after I upped to 10.4.6.
http://www.macosxhints.com/article.p...&query=dmproxy

Strange, my serial is still there on this G4 Mac mini.

'Wierd' was a typo right? Weird indeed.

Um, okay. I and a colleague of mine have bought several MacBook Pro's, and none exhibit any of the problems.

Maybe you are wrong, and only the 1% of people who are experiencing these problems complain? At any rate, it's still under warranty and Apple will fix it. The MacBook Pro basically uses an Intel architecture and mainboard now, so any problems are more likely to be Intel problems than Apple problems per se. Anyway, I haven not yet seen a MacBook Pro that exhibits these serious problems. I'm not saying there are none, clearly some people have experienced problems (though some seem to be due to flakey third party memory). All I can say is that 100% of the MacBook Pro's I have seen have been fine and have not experienced any of these issues, not even the inverter problem.

i dont know if it was me re-installing mac osX or this update but my spotlight finally works after a year of having tiger!

THANK YOU!!!

Wow, were you deprived. Congratulations

And I noticed this:


Maybe that means I'll get better response times when monitoring my guitar through GarageBand with all the distortion (I use iMic).

Edit: Huge spelling correction.

Originally posted by livatlantis
...Maybe that means I'll get better response times when monitoring my guitar through GarageBand with all the distortion (I use iMic)


Hey there... With audio latency sometimes the hardware box thingy itself is the "culprit" not the USB interface. It could be related to the latency of iMic (Griffin Tech right?). Or maybe it be both. Or maybe the software as well. Anyways, good luck, hope it's better overall for ya... 8)

WTF? NO SPOTLIGHT FOR A YEAR? Sorry to hear that, dude.

I'll post how things turn out

That normally means that your logic board was replaced. Did you send your Mini for repair recently?

Well I'll probably update in a day or two, after waiting for you guinea pigs to test the waters a little bit more.

The big thing is that I hope Spotlight fucking works in Mail. It's really, REALLY stupid that it won't turn up any results with 90% of the words I type in to the Find field. Sure hope that's rectified.

Also if I installed a hacked Front Row on my PB...do you guys think 10.4.6 will make it go away? I actually want it to go away since the battery in my keyspan remote died.

hit command esc.

I've had .Mac syncing issues most of the day and I'm still on 10.4.5. Browsing the Apple support site shows I'm not the only one.

This feature is great when it works, but once you start depending on it it's a nightmare when it starts misbehaving.

[QUOTE]But, yes, they should at least do that. I see all the guys here who have already used update to install the incremental version. Even after all the years it's been said that that's NOT the preferred way to do it.[/QUOTE

What do you mean by this? That we should download it manually?

Also, to clarify, I think SU should fix permissions and Verify. Then notify you if Verification failed. Why can't Apple do what TechTool does, do trickery under the hood to create an "eDrive" partition, so that we don't need boot from another machine to repair our drive? I don't care if it's a "Unix thing" it's annoying and if it isn't too difficult should be addressed. Hey, they got Verify to work...half way there!

Hmm, About This Mac doesn't open on this iBook G3 after installing 10.4.6, it just generates a couple console messages:

2006-04-04 09:20:06.414 loginwindow[88] *** Assertion failure in -[NSThemeFrame initWithFrame:], AppKit.subproj/NSView.m:710
2006-04-04 09:20:06.415 loginwindow[88] Uninitialized rectangle passed to [View initWithFrame:].

Will check that later on my other two systems.

First thing I noticed was improved AirPort reception. Mostly 3-4 whatevers in the menubar icon and no more connection flapping(!), just an occasional drop to 2.

[QUOTE]Originally posted by Aquatic

Actually? Yes. Often problems are seen by people who use the incremental upgrade. Many of those problems are fixed with combo.

I always just go for the combo. It wipes out all of the incremental updates installed and installs from the base system.

Well, this is the first I've read about using combos instead of incremental upgrades and repairing permissions before upgrading.

Safari was giving me beach balls the last couple of days and I was hopeful the upgrade my address that. The download went well. I hit restart and it stopped at the gray Apple screen with no swirly. For a good 30 minutes my iMac G5 1.8 fans roared. I finally shut it off by holding the button and tried to reboot three or four more times with the same result.

I've downloaded MacOSXSrvrUpdCombo10.4.6.dmg and MacOSXUpd10.4.6PPC.dmg at work and burned them. I plan to head home with my Diskwarrior and Tech Tools CD and hopefully get things running.

Grrr!

It's kind of sad that my Quicksilver 9.2.1 at work is a more stable platform. And here I've been bitching and moaning about upgrading (and getting new systems) for a few years.

Me thinks it was your re-install that did it. I can't imagine that 10.4.6 fixed whatever your problem was. Spotlight has worked FLAWLESSLY on my aged 450 MHz. G4 Cube since day one!

I don't know of any reason to repair permissions before updating. But, verifying, and repairing your HD, is a must.

Be careful with Tech Tools, it can cause serious problems.

Why is verifying and repairing your HD a must before updating?

Originally posted by Gene Clean
Why is verifying and repairing your HD a must before updating?


Just one of those Mac weirdness. Some people claim it's just voodoo and some people claim it always helps to verify-repair your HD before any sort of upgrading.

I've got no problems 10.4.6 software update (not combo) works like a charm for me The only thing like I mentioned above is the dmproxy* issue that still seems to be around.

Melgross it's the first time I've heard about installing combo is better than software update but an interesting theory nonetheless. I like the idea that it's a "fresher, cleaner" kind of update rather than a "patching" kind of update.

*http://www.macosxhints.com/article.p...&query=dmproxy

Because little errors pile up. Sometimes they are rectified by the simple task of checking the drive, and Disk Utility doesn't let you know. But, if your drive does have a real problem, no matter how minor, when you install and update, that error can corrupt part of the install. Sometimes it's subtle, sometimes it's major.

An example. Right before 10.4.5 came out, my machine seemed a bit sluggesh. Just by a tiny amount. I check my drives once a week, so I didn't think much of it.

When the update came out, I verified my drive, but Disk Utility said that it couldn't finish because the wrapper was corrupted (I don't recall the exact wording). It stated this in BOLD red type. Back up the drive etc.

I restarted from another drive that has all of my tools on it (and a CLEAN OS), and tried Disk Utility again, but this time set to fix the drive. Same notice.

I went to the current version of DiskWarrior (3.0.3) and tried again. It failed to replace the directory!

After turning the machine off and on a few times, waiting for the RAM to drain down each time, I tried DW again. This time it worked. I tried Disk Utility again. Fine. I then installed the update.

Many disk problems do not show any trouble during daily use, but if you don't check before an OS update (or upgrade), you are just asking for trouble.

Anytime you install anything at all on a drive with any kind of directory trouble, you can install over some other bits of code, causing anything to happen. Or the code could have the wrong information, information the update needs to know.

And, you also have to remember to unmount all firewire drives, turn them off, and unplug them from the machine before doing any OS upgrade as well. Then after all is finished, you can turn them on, and plug them in again, before turning the machine back on.

I'm VERY surprised. If you go to both Macfixit.com, and Macintouch.com, you will find that this recommendation has been standard for years. Even back with System 9 and earlier. It's known to fix many problems that crop up after someone installs the Software Update version.

Even if we DIDN'T know that this should be done, if you think about it, you will realize that it makes sense.

Both drive verification and combo updates will save many a headache.

Drive verification, likely. Combo updates, perhaps. Like John Gruber, I just use Software Update.

On the topic of Repair Disk Permissions, there's much discussion here:

Exercises in Futility Part 2: Repairing Permissions is Useless

Well, after trying to boot with the option key and selecting the hard drive and the Tech Tools CD, I called. They had me try to boot in safe mode which also failed. Then they said to take it to the nearest repair place, 45 minutes away.

This sucks.

Well, I guess this answers the questions about a firmware update on the intel macs. We knew they were up to something. Looks like they have come out with a beta for dual booting windows XP. I thought they weren't going to spend time on this. Also, it looks like this capability will be in the next public release of OSX 10.5. I bet they also include some VM solution.

I'm a little upset, but not really. It's much better to have an apple solution than a 3rd party one.

But this means I have to backup ALL of my data AGAIN, remove the windows partition that I had made. reinstall OSX, and then install Boot Camp. Oh well, at least now I'll have a USEABLE windows partition, rather than one that I can't even get to connect to the internet.

We KNEW this was coming months ago. Apple's patent application for the Intel Mac anti piracy software spelled it out right up front.

I've been wondering ever since why everyone didn't understand this. I'veposted it all over the place. I'll post it again. Read down towards the bottom of the page, you can't miss it.

http://www.macsimumnews.com/index.ph...esistant_code/

I agree. I've been having synching problems since Tuesday. It happened just after I had upgraded one of my Macs to 10.4.6. I then synched a change I made to my Calendar, went to my 10.4.5 Mac, synched it, and the change posted correctly. However, the next morning when I was upgrading my Mac at work, synching no longer worked.

I called AppleCare and they said they were unaware of any .Mac synching problems, but referred me to their email .Mac support page. I sent an email off to the .Mac support staff and received a reply that basically said some .Mac users were reporting connectivity problems and to try this: shutdown all your Macs for 10 minutes, then restart one, and try synching again. I did and the problem persisted, sort of. Synching wasn't working, but the network errors became more sporadic. Basically, the synching appeared to run successfully (wheel spins, completes, says synching completed), but upon checking another Mac, the change didn't update.

The problem I have been having went like this: I tried to synch, it would start, but then fail with various network/connectivity/authentication errors. I even went so far as to ask our work network guys to check out the router and firewall, but nothing had changed there.

This morning at work I tried synching again, and it appears that things are looking up. I was able to synch successfully with my .Mac Address Book, but changes to my Bookmarks aren't posting yet. Since .Mac doesn't offer a way to look at your Calendar online, I haven't been able to check whether Calendar synching is working yet. When I get home and restart my home Macs I should be able to test that.

Even though AppleCare knew nothing of the .Mac synching issue, I got an email reply from the .Mac support staff in only a few hours after my posting. Late last night I sent a follow-up reply with additional info about my experience, but haven't heard anything back. Ironically, i think that's good. It's now clear that Apple is aware of the issue and working on it.

It'll be interesting to see if I get a follow-up from them when they think the issue is resolved.

Originally posted by Dave Marsh
Since .Mac doesn't offer a way to look at your Calendar online, I haven't been able to check whether Calendar synching is working yet....


Maybe I misunderstood you but... "Keep your friends and family in the loop. With a .Mac account (or your own WebDAV server), iCal lets you publish your calendar on the Internet so others can see when youre available. And if theyre iCal users themselves, they can subscribe to your calendars."

http://www.apple.com/macosx/features/ical/

That's only if you publish your calendars, which makes them viewable to the public. Unpublished calendars are inaccessible.

Yes. That be it. So guess it's a question if Dave wants his calendars public.

Hi all, thanks for the comments. I actually do publish my calendars for selected users, but that's merely a copy of the calendar on my individual Mac, which then gets copied and updated somewhere to my .Mac iDisk space to be accessed by the third party.

That's not what I mean. I want to be able to go online to .Mac and see what the .Mac synchronization server has as the master copy of my calendar that's being used to synch all my Macs. That copy is NOT the same one I've published from an individual Mac to my .Mac iDisk space for sharing.

In fact, these published calendars have been working fine all this week, even though synching has not. Normally, when everything is working, they will certainly have the same content. When things are not working, as this week, they're not.

Only by making a change to my Mac's local calendar, selecting synch, and then logging online to .Mac to check the master calendar could I then determine that the synch server is working properly. At the present I have to go around to each of my Macs and resynch to see if the calendar updates.

You might ask why this is important. At the moment I am in fact publishing the local calendar on each of my Macs so that I can see events I posted at home while at the office. Normally, when I post a change at home and synch, that UPDATES the master calendar at .Mac and then updates that copy on my other Macs when they're next synched. So, I have only ONE copy of my Home calendar on each Mac, and one copy of my Work calendar on each Mac. This week I've had to publish these two calendars to see any changes between iCal at each of my Macs. So, I currently have multiple repetitive events on each day...one for each Mac's published calendar. With this setup, I'll only know the .Mac master calendar is synching properly when all the published calendars are the same.

It would be much easier for me to check if I could log into .Mac, select my calendar, and compare that to my local iCal calendar. I could then make a change, resynch, and check if the change posted to .Mac. If it did, I could then Unpublish the local calendars and return to having just ONE copy of each Home and Work calendar appear in iCal on each Mac, a copy that I could edit from any of my Macs and then view automatically on any of my other Macs later, as I've done just fine for the past couple of years.

[QUOTE]Originally posted by Dave Marsh
[B]Hi all, thanks for the comments.

Dave, I assume you were privy to this info posted on Apple support page

If you use iSync, you should perform a full sync with your devices before installing this update. Mac OS X 10.4.6 Update includes a later version of iSync with several improvements. For more information and before-you-install steps, see iSync 2.2: Read before updating to Mac OS X 10.4.6 or later, or before first sync.

at:http://docs.info.apple.com/article.html?artnum=303410

cheers

Yes, before my first upgrade to 10.4.6 my .Mac synching worked fine. I even tested it just afterwards, and it still worked fine. I then went to another Mac still running 10.4.5 and synched it, and it recorded the changes I made to the first Mac after upgrading to 10.4.6. I then went back to the first Mac, resynched, and it caught the changes I'd just posted from the 10.4.5 Mac. In short, everything was working fine, just before and just after upgrading my first Mac to 10.4.6.

It was the next morning at work when I was attempting to do a special synch on that Mac in prep for upgrading it to 10.4.6 that I discovered synching was no longer working. I went ahead and upgraded to 10.4.6 without incident, although synching still failed after upgrading that Mac. Back at home that afternoon, I found that synching wasn't working there anymore either. That's when I began to suspect the problem was at the .Mac synchronization server end.

I called AppleCare and they were unaware of the issue, and pointed me to the .Mac email support address. I entered into email discussions with them over the next two days before it became crystal clear that the problem wasn't at my end. The forums were filling up with synching issues and people were blaming it on 10.4.6. I didn't agree with that assessment because synching had worked both before and after my 10.4.6 upgrades the first evening. I suspected a concurrent action that occurred with the 10.4.6 rollout.

When the smoke cleared, it became obvious that some synching changes were posted to the .Mac syncronization server at the time of the 10.4.6 rollout, probably to support the upgrade to iSync 2.2 on the Mac.

In any case, I ceased synching on my Macs, and instead published my work/home calendars to .Mac so I could subscribe to them from my other Macs. That permitted me to see items I had posted to my other Macs in the interim as a temporary solution, and it worked fine.

After the outage was resolved, I unpublished my calendars and deleted them from my .Mac iDisk. Everything's back to normal, and the only thing I lost were the Notes I had posted to Address Book records. That annoyed me, but it wasn't catastrophic. If I had chosen the Backup Database option instead of the Save to vCards option, I probably wouldn't have lost those notes either. It appears vCards don't support Notes, but I didn't know that then.