So long and thanks for all the fish! In Apple’s eternal quest for your money, they are continuing their disrespect for Mac OS 10.5 Leopard users less than two years after 10.6 came on to the market. forcing you to upgrade your OS at an increasing pressure rate that would make Microsoft blush.
In seven days, Mobile Me will no longer support iCal push to Leopard clients. F*** the What?
I run a shed load of Power PC macs which refuse to die…. And their OS was only superseded only in June 2009, less than two years ago… At which point all updates ceased abruptly, with only security patches from that point on.
I always remembered the adage…. “You don’t need a new PC because the old one will always continue to do what it always has done…”
Bah humbug. Not any more… With the cloud centred life that we are all starting to live, they can rescind anything they want at any time…. And with MobileMe, they’re doing just that… already…
I’ve reported here on Office:Mac 2008 being the worst version of Office ever released for any platform. It’s buggy, runs slower than the previous version runs in emulation and it still lacks database software and is also missing Visual Basic, a key feature for any serious Excel user. In a word. Office:Mac 2008 is a lemon, and I want my money back.
But if you really, no, I mean REALLY want to talk about crap software produced by a world class company for another world class company’s operating system, then let’s not beat around the bush.
Quicktime for Windows is a dog. It’s an old dog, a mangy, old, lame dog which you just can’t seem to have put down despite serious, room filling flatulence.
It’s slow, buggy and is missing lots of features that many serious media users find indispensable.
Adrian Kingsley-Hughes blogging for ZD-Net has shown that Quicktime on his old 512MB RAM Mac Mini on OS X outperforms his 8GB Quad Core Vista system.
Ah, Vista, I hear you say. But before you click the reply button, he states that using VLC or a real media player blows the Mini to smithereens, so it is a Quicktime for Windows issue.
So I’d make that a 1-1 Apple-Microsoft draw.
I’d like to thank a couple of my readers for telling me how to remedy the problem of the ARD Screen Sharing toolbar function hack that can no longer be applied once one upgrades to OS X 10.5.5.
The solution is glaringly obvious and I’m a bit annoyed I didn’t spot it myself.
Just use Time Machine and search for the Screen Sharing application, located in /System/Library/CoreServices/Screen Sharing.app and return to an older version of the app!
You gotta love Apple for handing you the solution on a plate.
Alternatively, dig out your Leopard DVD and pull it off there.
You’ll apparently get bugged by an upgrade screen.
I had read that Apple were trying to cut down on “Frankenbuilds” using software from different versions of the OS, but I guess this is still OK.
I’d like to try this, but since I have a nice, fully functional ARD 3.2 installed there’s not much point for me!
Still, I may try it one day. Let me know how you get on with these tips.
My iMac has gone back to Apple for an inspection and hopefully, a new screen.
I backed up my 24″ iMac using Time Machine and formatted and secure erased the HDD, reinstalled the factory supplied Tiger install before sending it back to Apple.
Just for old time’s sake, and just scientific curiosity, I played with the Tiger installation (10.4.9) for an hour or two before switching it off and shipping it back.
I’ll state my final impression right up:
I could not believe how much progress Leopard has made and how much a retrograde step it was moving back to Tiger!
There, I said it. For all the (all the? a bit of an overstatement, perhaps, when compared to Vista) bad press that Leopard received, Tiger is a bit of a dog to use compared to Leopard for all the things I tend to do, and I have gained a new level of respect for the newest, occasionally troubled OS.
The old sidebar is much less useful than the new one, and the dynamically scaling icons to fit extra stuff in appears a bit unnecessary. As for speed. Crikey, it was much slower than I remembered, often beachballing when performing a task.
It seems that every time I double clicked on a network share the computer would beachball. How did I live with that?
Then up would come the prompt for the computer I was connecting to. After entering the password, The drive mount selector would appear. I’d double click on that only to have the icon mount on the desktop, the finder.
Repeat for each mount and with eight mounts, things start to get out of hand!
Tiresome, tedious and not at all intuitive.
Then there’s the strange Network icon that appear with an alias to my server that when you click on it throw an error saying the original file cannot be found etc. etc. do I want to fix it…
As for stability, I’d forgotten how finicky the Disk Utility was when it came to mounting my four drive raid combi on Firewire. It locked up immediately and permanently on opening and preventing me from logging out. It then required me to forcibly turn off the computer and restart, with the Firewire drive switched off.
Nearly a year after launch, Leopard is rock solid. OK, so a few apps have memory leaks, but I can now leave my Leopard Server running 24/7 only restarting for updates and patches.
There was some good bits to Tiger though
The lighter, more translucent appearance of Tiger was fresh and bright, like an Apple Store, after the dull grey of Leopard and the blue apple and rounded corners of the menu bar are much softer and more gentle.
Also, shadows subtly handled in Tiger, with delicate, subtle shadows rather than the the crazy-arsed SHADOW!!! that surrounds each window in Leopard.
There was less memory usage off the bat.
The Calendar application had its sticky inspector panel, which required only one click to edit each entry. The thrice damned Leopard Calendar drives me up the wall! Bring back the drawer is what I say!
All in all, I’d give Tiger a respectable 8 and Leopard a superb 9 out of 10!
I am using Leopard Server and was happily backing up to a Leopard Client. (Yes, my server is backing up to a Firewire mounted external volume on an OS X client machine, shared over ethernet with AFP!!)
After months of trouble free operation, I upgraded both to 10.5.3 and got the “cannot mount volume” error.
I tried several times, but it would time out with an exclamation mark icon after a few minutes, each time.
- I switched off Time Machine
- Disabled file sharing on the client
- Reset the Client
- Switched AFP sharing back on
- Manually mounted the .sparsebundle once on the server – It mounted fine.
- I then reenabled Time Machine, ran the “backup now” option.
In my case, the above steps fixed the problem. I now have hourly backups working again.
First I checked the system profile on the Apple menu, but that showed that the graphics card was correctly recognised as ATI Rage Pro 128
Just in case, I checked the /System/Library/Extensions folder. There were no ATI Rage drivers there at all!
I hopped on over to OSX86 at Insanely Mac and read their forums, remembering my Hackintosh days of dragging drivers over and found that it was a trivial task.
Since I used Archive and Install so I had my whole Previous System folder available, I mosied on over to:
and grabbed all the ATIRage kexts bundles and plugins I could find. I spotted the ATIcellerator, too so I brought that over to/System/Library/Extensions folder, also.
I had to change the permissions of the files, delete the old extensions cache and reboot.
This needs to be done as root (using sudo) so be careful, a mistyped command will be executed without complaint by your computer, potentially hosing your entire system.
In terminal, type:
type your password at the prompt and you are now root. You can seriously shag your system up if you’re not careful. So be careful 🙂
chown -R root:wheel /System/Library/Extensions/ATIRage*.* rm -rf /System/Library/Extensions.mkext reboot
After the reboot I found that my system was much, and I mean that honestly, more responsive! The slow screen updates, windows resizes, dragging, Safari page scrolling, everything was much faster.
I imediately ran X Bench to see if the results reflected the performance differences I felt and here are the results:
A convincing win for Leopard with the Tiger driver installed! It is a shame that OpenGL performance is not affected, however.
Just to remind us, let’s have a look at Leopard running with Tiger’s ATI driver versus Tiger itself.
This is extremely interesting. It shows us surprisingly that far from having an overhead, Quartz graphics actually show a very slight increase in performance compared to Tiger (averaged over three runs)! Of course, X bench is fickle, so take this with a pinch of salt.
Unfortuantely, the OpenGL (spinning squares) test shows us that it not receiving any benefit from the new driver. That’s too bad.
Well, I can now reverse my original post with the following shout:
I CAN NOW HEARTILY RECOMMEND LEOPARD FOR ATI RAGE USERS WITH >1GB RAM AND A DECENT CPU!
I benchmarked my Leopard on G4 Cube installation this morning and the results are not pretty. As I mentioned yesterday, the system feels sluggish, especially the UI. Although many feel that X Bench is not very representive, I feel that the results bear out my experiences very well as you can see in the chart below:
It’s basically a clean sweep for Tiger, with a couple of statistically irrelevant results in favour of Leopard.
Note the far left column is X Benche’s overall result which shows a 50% decline!!! This is in line with my impression that day to day use is about half as fast as it was under Tiger.
Key areas to note are the OpenGL and UI sections which have lost almost 70% of their performance while Quartz is about half the speed!
This clearly shows that Leopard users pay a heavy price in the graphics department with older hardware. It looks to me that the system is using generic drivers for the ATI card, since all other results vary by mostly insignificant margins.
Full benchmark results
The only major differences in benchmark scores other than graphics are Memory allocation speed which is doubled (tested repeatedly) and thread lock contention which is about 30% slower.