Leopard

You are currently browsing the archive for the Leopard category.

If you have an old G4 sitting around that’s at the 800mhz mark, you probably should try installing Leopard, because most people agree it actually runs FASTER than Mac OS X 10.4 Tiger. Weird, huh? I guess they’ve optimized the code pretty well.
However, when you try to install the operating system, you are warned that Leopard cannot be installed on your G4. There are a few reasons for this:
1) Leopard requires 512MB of RAM – you have RAM, right?
2) Leopard requires over 867mhz processor

We can fix number 1 by simply getting more RAM. I find Craigslist to be of great use here. Number two is a bit more difficult as G4 processor upgrades are ridiculously expensive once you consider the cost of a Mac Mini, and also requires a bit of tech savvy under the hood as you’d be swapping CPUs.
Not to worry, though. Here’s a way to convince OpenFirmware that your CPU is 867mhz, and allow the installer to boot, install, and get you off and running:
Boot into Open Firmware, I have covered this extensively here:
Once in OpenFirmware, issue the following commands (for single CPU):
dev /cpus/PowerPC,G4@0
d# 867000000 encode-int " clock-frequency" property
boot cd:,\\:tbxi

For dual CPU:
dev /cpus/PowerPC,G4@0
d# 867000000 encode-int " clock-frequency" property
dev /cpus/PowerPC,G4@1
d# 867000000 encode-int " clock-frequency" property
boot cd:,\\:tbxi

Note that all we are doing is over-writing the CPU clock-frequency (speed) property for each CPU installed, at boot time.
Also, if you need to boot another device, try:
printenv boot-device
This will return a list of boot devices to use when booting the installer. I used this in order to boot a Firewire device that had had a disc image (DMG) restored to it, making things a bit easy and faster.

Good luck!

I hear this a lot, and I myself have also gone looking for it…

So without  further ado, here is the script that will install kext files for you – be warned – you’ll need to know how to get the kext file in the first place, as well as the filename.

Easy right?

Let’s get started.

Open the Terminal application by going to Applications / Utilities / Terminal.app – you will see it in the Utilities folder – it looks like a command prompt.

Once terminal has launched, type in the following command:

sudo -s

Enter the root or first user password that you inputted during the setup process.

This tells it to run any other commands after this one as the root or superuser account, allowing you to edit files you normally would not have permission to edit.

Here’s an example using IOATAFamily.kext, a popular ATA driver. You’ll want to replace this by your own driver name. Also, you’ll want to make sure the file is unzipped, and sitting on your desktop. Oh one more thing, you’ll want to edit YOURUSERNAME with… your username :)

mv /Users/(YOUR USERNAME)/Desktop/IOATAFamily.kext /System/Library/Extensions
chmod -R 755 /System/Library/Extensions/IOATAFamily.kext
sudo chown -R root:wheel /System/Library/Extensions/IOATAFamily.kext
cd /System/Library/Extensions
rm -rf Extensions.mkext
rm -rf Extensions.kextcache

Hope that helps!

VMware has just announced support for their 61st OS supported by Fusion 2.0 – Mac OS X Server 10.5 (Leopard). This is great news for those looking to test things like the new Active Directory wizards, calendar server and enterprise blogging that come with the new version of the server. Not to mention that because it’s supported by Fusion 2.0, you can do it on your laptop.

Check out the full blog post on Fusion 2.0 Leopard Server support at the VMware VMTN blog site here.

I’ve been using OS X for a while now, and one thing that really irks me, especially on larger DMG files like a Leopard image, is that OS X automatically tries to verify the checksum of the DMG image file, which could take hours.

There are a few applications out there that will disable this for you, but if you want the quick and dirty method, and don’t mind using the Terminal once in a while, use this one-liner to disable the verification easily:

defaults write com.apple.frameworks.diskimages skip-verify true

Why is it that I always find myself ponying up the small amounts of cash it takes to purchase Mac shareware applications? Black fire and a disco ball? I gotta have it.

Today I fell victim to MacZot’s current promotion (ends in 23 hours!) that saw me gobbling up the public beta of the Disco CD/DVD burning application for Mac OS X, and boy am I content with this lil 700KB number.

Firstly, the hype: when you purchase the beta at the silly-low price, you also get the opportunity to send a free license to someone else. So here goes – the first person to leave an intelligent comment gets the license! (I’ll need a real email address) This is a great marketing idea that see people not only using the beta of a terrifically designed piece of software, but also spreading the word to others so they can try it as well. Good show.

Disco Windows

Next, the features: Disco copies discs in two clicks. Say that ten times fast. Disco can span CDs and DVDs automagically. They call it Spandex, I call it dead sexy. This is extremely handy when backing up iPhoto or iTunes, trust me. Disco can burn VIDEO_TS folders by just dragging them onto the application, which makes it great for burning your DVD backups. Disco has realtime 3D interactive smoke that actually wafts up from the application as you burn discs. If you blow into your microphone, the smoke will dissipate, and if you move your cursor around the smoke itself, it reportedly moves accordingly – but I didn’t get to see this on the low-end test box. Disco has an amazingly simplistic interface that is very easy to follow as it prompts you at every step. Last, but certainly not the least in terms of features, and should really be in caps: Disco remembers every single burn and keeps a catalog of the burn sessions using what it calls “discography” so that you can easily do things like print labels, disk jackets, or simply keep handy for when you need that dot release or the pre-altered code that you can never find. Let Disco be your personal sherpa.

Disco runs very well for a beta application. I have yet to see it crash under Panther, Tiger, or even Leopard (WWDC or the 9a ADC build). Oh, and it worked fine in Tiger server as well. Unfortunately the test box is a 1st generation Mac Mini (PPC), so there was no “smoke” to speak of (anyone have screenshots?), so that will need to be tested later. I burned some mix audio CDs, a backup copy of the disk image for Disco public beta itself, an ISO image of Ubuntu Edgy Eft Beta, and a bunch of Gentoo releases, for good measure. No hiccups. I erased a very old scratched CDRW. I even inserted a scratched blank CDR to see what would happen… Well it wouldn’t burn correctly but Disco kept on keepin’ on – like some sort of Disco inferno – no bouncing beachballs of death here. And you call this a beta? I expected flames, not smoke. No crash and burn here.

picture-1.pngpicture-2.pngpicture-3.pngpicture-4.pngpicture-5.pngpicture-6.pngpicture-7.pngpicture-8.pngpicture-9.pngpicture-10.pngpicture-10.pngpicture-11.png

In these screenshots you see the Disco app in full swing, from installation to a test burn, and a view of all the windows it provides. I really like the design of this app, and it was well worth the 15$ pricetag. If you’re new to MacZot, and need a referrer, feel free to use “blandname”. Now go write some optical media and dance around like a schoolgirl.

Oh and on the topic of Disco, and in the name of Halloween here’s a joke:

“Why didn’t the skeleton dance at the disco?”

“He had no body to dance with”

« Older entries