Skip to content

Archive for August, 2009

29
Aug

Snow Leopard on 965P-DS3 or DS4 – 64 Bit goodness!

It’s here, and it is spectacular. The proof is in the pudding. More details to follow – installation guides, and kexts etc. In the meantime, search for 965P-DS4 on InsanelyMac. W00t.


23
Aug

Finally, Retail Leopard on Gigabyte 965P-DS3

Not a how-to A lot has happened in the OSX86 world. From its humble beginnings back in 2006, when it was the playground of the extremely talented few, and OSX installations were wrought with issues, to the “boom” period when large number of “distros” were the call of the day, and industrious users created their brand of 10.5 flavors for the masses. iPC, iAtkos, iDeneb, and others will be familiar to anyone who has expressed interest in installing OSX on their non-Apple boxes. Where it once was the realm of the adventurous few, it became the turf of every person with the Apple gleam in their eye. And now, when installing retail OSX is the cool thing to do.

No “distros”, no flavors, just plain vanilla OS installed directly from a retail Leopard DVD (10.5.6) bought from the Apple Store. That is the project I decided to undertake this weekend. Laid low by chronic back pain and neck muscle ache, I decided to sit back and take the hours out to install retail OSX on my system that I built back in 2007. A few specs:

  • Gigabyte GA-965P-DS3 ver. 3.0 Motherboard
  • Intel Core2Duo E6600 CPU (OC’d to 3.6 GHz)
  • 4 GB of DDR2 800 MHz RAM
  • SATA-2 HDD’s 4.0TB in AHCI
  • S-ATA DVD/CD Writer LiteOn
  • XFX nVidia 7600GT (512 MB)
  • Gateway FPD2485W S-IPS LCD
  • Apple Aluminium Keyboard
  • Logitech MX Revolution Mouse

Here is a list of things I did need.

  • A retail Leopard DVD. I used 10.5.6.
  • Boot 132 Disk for your system or a generic one.
  • Chameleon Bootloader 2.0 (RC1) or better.
  • KEXTs for your graphics card (you can go EFI strings later).
  • A LOT of patience.

The basic challenge is that Leopard won’t boot on a non-Apple machine without some coaxing. Enter the Boot 132 disc. I won’t go into details, but basically you can create a flat DMG with the KEXTs in a folder and the Boot 132 bootloader will load them for you at boot time. KEXTs are kernel Extensions that allow extended functionality to be added to the Kernel without the need to compile all the extensions for devices, etc., directly in the kernel. Boot 132 allows KEXTs for non-Apple hardware to be loaded at boot time and extend the base Apple kernel so that a retail Leopard DVD can be booted. More details here.

Here’s how I went about the installation. I inserted the Boot 132 disc and on being prompted, the retail Leopard DVD. The Installation was straightforward, and understandably the OS installation gave a “Failed” notice at the end. This is because a bootloader hasn’t been installed on the OSX partition.

Next up, I booted from the Boot 132 disc, but chose instead to boot from the newly installed OSX Partition. Leopard welcome and setup screens later, I was in! I didn’t have QE/CI though, as I hadn’t yet edited the com.apple.boot.plist with my EFI string (easily extracted via GFXUtil). I quickly installed Chameleon 2.0 (RC1, as RC2 just doesn’t seem to work for me) and copied a whole list of KEXTs to the /Extra/Extensions folder, and com.apple.boot.plist to /Extra. These are the KEXTs I used.

  • AHCIPortInjector.kext
  • AppleACPIPlatform.kext
  • AppleAHCIPort.kext
  • Disabler.kext
  • dsmos.kext
  • IOAHCIBlockStorageInjector.kext
  • IONetworkingFamily.kext
  • OpenHaltRestart.kext
  • SMBIOSEnabler.kext
  • UUID.kext

I deleted the Extensions.mkext in that folder, and corrected the permissions.

sudo chown -R root:wheel /Extra/Extensions; sudo chmod -R 755 /Extra/Extentions

Rebooted, and this one’s important – typed in -v -f to force compile the KEXTs at the Chameleon Boot screen, and voila, Bob’s your chum!

I did however have to install AppleHDA.kext manually, as it can’t be copied to the /Extra/Extensions folder (due to multiple dependencies). I am just so impressed with the performance and stability. Uptime of three days and counting. Again, this is not meant to serve as a how-to, but rather a brief insight into the installation process. . Bring on Snow Leopard!


19
Aug

Textmate and SVN

The shift was overdue. Although Coda, my dev app of choice, offers everything a hobbyist programmer would need, it fails miserably on one aspect. Namely, code folding. For a long time, this trade-off seemed to still justify the use of this app for day-to-day development needs, in light of its other features, e.g. easy integration with SVN, about which I have written in the past.

However, of late as I start to work with larger projects with a lot of embedded logic, and process flows, it has become a pain in the proverbial behind to switch from Coda to an app that will fold code. The forums and blogs are abuzz with developers’ dissatisfaction with the lack of Code folding, and the staff at Coda don’t seem to care. If only I could configure SVN with TextMate, and that too in a comprehensive, intuitive way, I could move away from Coda, forever. It seemed to be a pipe dream, i.e. till now. I have successfully set up SVN with TextMate and in a way that mirrors the ease of COMMIT, REVERT, DIFF found in Coda. Here’s a how-to.

This is what you’ll need at the get go.

  1. TextMate editor (of course)
  2. SVN Frontend (if you don’t want to finagle with the terminal). I use CornerStone.
  3. FileMerge (from XCode dev tools – recommended) or Changes.
  4. SVNMate Plugin for TextMate.
  5. FileMerge Plugin for TextMate.

Create a SVN repository with the software of your choice. I usually create one on an external drive (as I need access to my code offline from time to time). Note down the local or remote URL. In my case it is

file:///Volumes/ExternalHDD/CodeRepo/MyProj/.

Double click the SVNMate.tmbundle file, and it will insitall itself in your

~/Library/Application Support/Textmate/Bundles/.

Do the same for the FileMerge Plugin as well. Now is the time to configure. Open a blank file with Textmate and in the Bundles Menu

Bundles->Subversion->CheckOut.

Enter the local or remote SVN URL, and choose a folder in which you’d like to check out the files. That was easy. At this point you are pretty much set with SVN on TextMate. You will see icons displayed next to the files in the file browser, indicating their subversion status. That’s the beauty of the SVNMate plugin we just installed. Any changes you make to your files will alter the icon status to signify changed content. You can fire up the commands using CTRL-SHIFT-A to bring up SVN commands. But – you could make your life easier by setting up the following options as well. This is a matter of choice of course.

Changing the default icons for SVNMate
Change the default SVN status icons by going to TextMate preferences. Preferences->SVNMate and choose a set that catches your fancy.

Using FileMerge
Instead of using the TextMate SVN diff file viewer to see the changes since the last commit, use FileMerge. It is included in XCode developer tools, and is perhaps the best viewer, with split side-by-side views.

Use Tab Triggers in TextMate
Perhaps the BEST feature so far – use TextMate tab triggers to trigger SVN events. Tab Triggers are used in TextMate by assigning a set of letters followed by a TAB key press, to trigger an associated event. You can pretty much do anything you like with Tab Triggers, from inserting pieces of Code in TextMate to SVN file commits. To set up a Trigger for an SVN Commit, go to Bundles->Bundles Editor->Commands. Choose Subversion from the list. Choose a command from the list, and in the right pane choose a method of Activation from the Drop down – Tab Trigger. To it, assign any combination of words. I chose “commitsource” for COMMIT.

If you prefer to view the differences in FileMerge instead of the inbuilt diff viewer, in the same window (Bundle Editor) choose FileMerge in the list and edit the Revision Command.

Voila, it just works. To see the new Tab Triggers at work, type the keyword inline with the code, and press Tab.

Don’t worry, the keyword disappears from the code as soon as you close the FileMerge (or the associated app window). Simply wunderbar.

So indeed, it is time to move to TextMate and stop bemoaning the lack of Code Folding.


17
Aug

Open or Export CHM files on OS X

CHM files are the de-facto distribution standard of e-books in some circles (O’Reilly) etc, and though these can be opened natively on a Windows machine, the same cannot be said for OSX. One of the best (though certainly not the most popular for some reason) app for opening CHM files on OSX is iCHM. I found this app after having tried a number of commercial apps and finding them wanting in one department or the other.

iCHM is a one stop shop for opening/printing CHM files. Visually pleasing and quite intuitive, iCHM also prints directly to PDF. Perfect. And best of all, this app, is free! Try it today.


9
Aug

OS X 10.5.8 is out – Choppy performance is back

Apple released Leopard 10.5.8 a few days back. The update went without a hitch on my MacBook Pro. The story on my Hackintosh isn’t so great. The choppy performance issues are back, after having been wiped clean in 10.5.7. Argh. I reinstalled OSX to no avail. I nearly borked my system in the process.

Here’s the story. I usually OC my system to thy kingdom come. Because I wanted to install it all from scratch, I decided to switch off my system after a span of nearly 22 days. Bad decision. When I did restart it wouldn’t OC for nuts. I tried looking in the BIOS, and there in RED letters – VCORE: FAIL. Great. I thought it was a faulty CPU fan – replaced. It could’ve been the SMPS’s fault – replaced. Reseated RAM, CPU. All permutations and combinations – to no avail. And then I decided to just switch it off and worry about it later. This morning I switched it on, and voila, everything back to normal. Explain that. Blah. Here’s the obligatory screenie.


Premium WordPress Themes
WordPress Themes