[Rootman]

I could never get iCal .Mac publishing to work before but this update has fixed.

[lastcookie]

My update went smoothly, BUT now I am having problems with corrupted CS3 Photoshop files and it is no fun at all!
Also, I am not the only one.
CS3 users beware and check the Apple Leopard discussion posts regarding this issue.

[jeffmccord]

Sorry...



I have the latest AEBS and the latest firmware. I use a WD Book (360gb) that I bought from the Apple Store plugged into my AEBS. It worked flawlessly w/ Time Machine (wirelessly) and now (as mentioned) it won't work because it says "The backup volume could not be mounted."

I've even started completely fresh w/ my backup and still has the problem. It did work once when I plugged in my WD Book via firewire (started a brand new backup with Time Machine). I then unplugged the connection, went wireless, mounted my WD Book via Finder and it backed up. Only once. I then rebooted and the same error started all over again and now I can't get it to work at all wirelessly.

[medelegant]

Best and the most appreciated fix I have seen immediate benefits from is the fixes for proxies and ISA servers.

I can now use Safari again without worrying or being frustrated but sudden quits and disappearing acts whenever it was looking to hit any HTTPS address outside of the corporate network. For anything like that, I had to resort to FireFox and it is sooooo freeeking slow I would seek to just avoid it altogether and wait till I got home.

Dashboard works well again without always asking for proxy server passwords etc and the number of calls to have the password reset by the IT help desk has dropped from 3-4 events per day to zero.

[graxxor]

It's nothing to do with the AEBS.

I am using Leopard server and was happily backing up to a leopard client. (yes, my server is backing up to an OS X client over AFP shared volume).

Upgraded both and got the "cannot mount volume" error.

I switched off Time Machine, then file sharing on the client. Reset the client, switched AFP back on and manually mounted the sparsebundle myself once from the server. It mounted fine.

Then I enabled Time Machine and ran the "backup now" option.

That seemed to fix it.

http://lloydie.homeip.net/blog/?p=350

[jucarueda]

What about the FrontRow bug on MacBooks Pro, is it fixed too??

[Namdlog]

One bug that wasn't fixed is the hardware stereo bug. We in the scientific community who have bought the incredibly expensive MacPro+NVidia 4500/5600 stereo card combination are incredibly p....ed. We are still stuck at Tiger - and the longer this continues, the less of an argument we have for MAC. We have to go back to Windows/Linux dualboot systems, one for science, the other for word.
Paint me unhappy.
Adrian Goldman

[jpp_zoso]

moving files (under path finder) bug still not fixed (files do not move). setting preferences for default browser/email/ftp client/news reader bug still not fixed (preferences lost between reboots, always default to apple's clients). i think both are related to using file vault if i recall previous threads on these issues.


mail on my system no longer quits. worked fine before 10.5.3.

network and webdav drives still don't always show up in finder.

[freddmeyer]

I installed Time Capsule to back up my iMacG5 and MacBook Air. For a while no problem. Then, the iMacG5 kept freezing (like a PC!) and black curtain would come down and say: you need to erstart your computer. hold down the power button for several seconds or press the restart button.

after doing so, it would display:

the computer has restarted after MacOSX quit unexpectedly.

well, after all atempts, I formated the disk a couple of times but the problem persists.

any hint pls write to freddmeyer@mac.com

[mmnh]

Mac update went fine. Then there was an update for Parallels, and that seemed to go fine. But now when I run Parallels, apps go crazy, programs won't quit, windows flicker and flutter without warning, etc. So now it's a matter of determining where the problem lies--with the Mac update or the Parallels update or both or somewhere in between...

[Martian]

Try toggling between Coherence, Single Window, Full Screen. Just toggling fixed the Parallels problem for me.
BTW, I added Keyboard Shortcuts (System Preferences) OPTION 0, OPTION 1, OPTION 2 for the three modes respectively.

[K4thwright]

I've had problems since day one with 10.5.3 on my MDD 1.25 MHz DP G4. I finally tracked the problem to overheating caused by the fact 10.5.3 runs both processors at nearly full capacity a lot of the time, particularly when downloading updates. You can verify this on your machine this by checking the activity monitor. If the processor runs too long it appears to raise the temperature of the heat sink high enough to cause a component on the logic board immediately below the heat sink to overheat, causing one of the processors to lock up and run at full bore while the other coasts at about 20% of max. I verified this by shooting this part of the logic board with freeze solution from a pressure spray can.

I fixed the problem with a new copper heat sink that is used on the later 1.42 GHz DP MDD. I also acquired a 2nd 1.25 MHz DP, which has a different (apparently stainless steel) heat sink from the aluminum heat sink on my original MDD. This 2nd machine has never overheated like the first one did.

Back to your question. I've tried 10.5.3 on the MDD and find that, in general, 10.4.11 runs better for my applications on both machines. Specifically, Photoshop CS3 runs about 5% slower on 10.5.3 than on 10.4.11, using my own speed benchmarks that I developed way back on OS 9.2.2 with Photoshop 7. In fact, it was not until CS2 came out with OS X 10.3 that the MDD would run as fast on OS X as PS 7 on OS 9.2.2 Also, CS2 runs significantly faster than CS3, although I use the latter most of the time because it has more features. 10.3.5 runs most of the software that I normally use, such as Microsoft Office (the original OS X version that I bought with the MDD in 2002), iTunes (of course) and Adobe Lightroom, but I don't use 10.5.3 very often because 10.4.11 works well. Also 10.5.3 does not support my Epson Stylus Color 3000 printer, although it does support my 1280 and R 340 printers.

In short, My opinion of 10.5.3 is that for me it gives me 300 new features and 200 secrets that I don't want or care about because these goodies don't help me work any faster or better than 10.4.11. I keep up with 10.5 just because I want to know about the latest, but newer is not necessarily better. If you want the new eye candy, go for it, bearing in mind that you may have the overheating problem if you fully load your box with four hard drives and two optical drives, as I do.

Kent

[mr_rsu]

Kent, thank you so much for that insightful information! That has exactly reinforced my correct decision NOT to upgrade to 10.5 (and its recent update) for my Mac MDD/1.25 Ghz (1 CPU), running with 1.75 GB of RAMS and a third party video card ATI Radeon 9800 Pro, which was put together by a talented Mac technician (bought it on eBay from him... wanted the name? just ask!). I knew 10.5.3 would be too much for my Mac and I still cannot afford a new Intel-based Mac. :(

Look like I'm going to be sticking with 10.4.11 for the time being, since I don't have Kent's expertise and tools to verify the differences.

If anyone still having problem running 10.5.3 under a similar model like I have (or a DP version), your best option is to simply downgrade back to 10.4.11 until Apple actually address the problems like other users have reported so far.

[mr_rsu]

Your best option is to downgrade back to 10.4.11 if you wanted to play it safe without further problems under 10.5.3. It's totally up to you.