UPDATE: I've created a short video to help people with settings for VMWare, DX and PKR.
View the new post here

At long, long, last, with the new VMWare Fusion 1.1 PKR works on my MacPro if I run it in 'min spec' mode (launch it from the start menu). It runs fairly well on my 3.0GHz Mac Pro. I only give one core to VMWare. I didn't stay for long because to be honest I've gone off poker. It even runs in Unity mode so it's doesn't look quite so windows and crap.

Congrats to the VMWare guys and I guess congrats to the PKR Guys, maybe they should be offering cash players free copies of VMWare fusion.

 
    lookupd -flushcache
 

but on Leopard (OSX 10.5) its

 
    dscacheutil -flushcache
 

As my ADSL connection goes up and down i find my DNS cache is getting screwed with.

I'll admit it's an expensive way for me to be lazy. I could test regular expression in the python command line. I'm just to lazy Anyway, to get to the point. There is a good google tech talk by one of the authors of VMWare Fusion. He goes in to the ins and outs of OSX development touching on the 'Apple creates API's for it's own needs' which I think most OSX developers know. For some reason embedding is disabled so here is the link.

The new release supports downloading individual files. So imagine you are downloading a free operating system but the torrent contains files you just don't need, well just check the ones you want and uncheck those you don't want..schweet

So I wondered how I was going to eject the second drive. After installing the drive and rebooting this is what I discovered.

A new menubar tool has appaeared with a familiar eject logo on it. When it's clicked on you see this

So now I can eject the two drives either via the menu option or option-eject it. I'm not sure why it says F12 as I have an eject key on my keyboard. Maybe because it's not an apple keyboard something has gone wrong.

What I love about this is that the interface for all of this is hidden from me when I have one drive. I don't need to know how to eject a second drive when I have one.

This sounds obvious but if you use KDE/Gnome/XWindows/Windows machines you start to feel like there are options for EVERYTHING even if you don't know why they are there. Often they are there and they don't even do anything with no feedback to the user. This where apple excel. Vista, LDE and Gnome all look nice but their vendors don't go as far as Apple to hide meaningless interface options. More choice is not a good thing it's just noise. Sure you tune it out over time but it still takes hidden brain cycles to work with.

I'm not certain of why Apple succeeds where others fail but I can tell you what they do is hard. Any vendor can make a menu, decide on keyboard shortcuts, work with standards groups to decide on a code for eject. But it takes lateral thinking, time and space to be able to sit back and say "You know what: when the user has got one drive, let's hide all the work we've done". Maybe that's the key. If you've spent a few weeks making a menu. You, as an engineer, want the world to see it. You have after all slaved over the details. You have lovingly crafted a piece of code, submitted yourself to code reviews, checkin reviews, standards compliance tests and internationalization reviews. After all that 'they' want to HIDE the menu! Maybe Apple's design isn't driven by engineers. Maybe that's why it works. For once maybe it's not about you but about a greater good?

Update: I got it working with VMWare

It seems that VMWare is some way behind parallels as well. It seems a lot more sluggish then Parallels. To be fair, when you run vmware they do warn you that there is a lot of debug code still in the virtual machine. Lets hope it gets better as competition between Parallels and VMWare can only be good for everyone.

The author doesn't mention it but rather then pass the path to the scripts to svn via the --diff-cmd option to can edit ~/.subversion/config and enter the full path to the scripts in the diff-cmd variable. Note it needs to be the full path as shell variables wont be expanded (so ~/bin/fmdiff will fail with error 255)

PS: I have nothing against the text based diffing tools so please don't flame me. After all I'm a Mac user so what do I know of suck magic.