Today, let’s get your iPad/iPhone printing from the HP LaserJet 1020. The 1020 isn’t officially supported by Mac OS X but always has been able to print using the 1022 driver. In my case, I’ll have it connected via an Airport Express, but this works fine also if it’s connected directly to your Mac. Having it connected to the Airport Express another place in my house just makes it more fun. ;-)

First of all, we need to have AirPrint Hactivator (make sure that you’re running OS X 10.6.5 or later and have iTunes 10.1 installed) installed to do iOS’ AirPrint. Leave that to last and you have to remove and add your printer once more, and we don’t want that.

Then get the drivers from Apple (~350mb download, ~560mb installed) and install them.

Finally, have the printer connected to the Airport Express (or your Mac) and turned on. Go to System Preferences, and hit the ‘+’ button on the lefthand side. Select your printer (which will have ‘Kind’ say ‘Bonjour’ if it’s connected to the Airport Express, or ‘USB’ if it’s connected to your Mac via USB). Select the printer (HP LaserJet 1020), in the ‘Print Using’ dialog, select ‘Select Printer Software’, and select ‘HP LaserJet 1022,’, not any of the Gutenprint versions. The 1022 printer is virtually the same but also has a network interface of its own. When you’ve selected that, hit ‘Add’ to finish adding your printer.

Congratulations, you can now print from your Mac and your iOS devicie! :-) (assuming, of course, that your device is on the same network as your Mac is)

Wow, the libpd guys make it possible to put Pure Data patches in your iPhone app. I’m definitely going to make an app based on this, if nothing more then just for the heck of it. Time to brush up on my PD skills, I’ve been using Max/MSP for too long ;-) See the article

Ever seen this before? Got fatal error 1236 from master when reading data from binary log: ‘Could not find first log file name in binary log index file’ I had that after a MySQL server in my replication loop went down. When it came up, the next server in line gave this replication state ‘Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave’, which was quite logical since the end of the bin-log had been corrupted due to external circumstances.
This should be a simple
on the node that had stopped replicating, but this is when the 1236 error kicked in. As very often with 1236, the node that had gone down hadn’t updated it’s binary log index file (servername-bin.index in this case, yours might have a different prefix) so I had to manually add that in the index file. One more thing to remember, restart the MySQL server after updating the index file. Then replication should happily resume again once you hit START SLAVE; on the next mysql server in the replication ring.
PS, take care, the CHANGE MASTER seems to flush the tables or something, it doesn’t simply set some variables, so depending on the load on your server this might take several minutes

The new AppleTV with iOS inside has me very excited as a developer and a media consumer. But, unfortunately, after the new AppleTV was announced, the old Apple TV is still on sale here in Denmark, Norway and Sweden. What gives, Apple? You neglect the most technophile part of Europe, both with the iPad and now with the AppleTV, without an obvious reason. I emailed support a few weeks ago, and they asked me to check back when the AppleTV started shipping. So now I guess we’ll have to drive to Germany to pick one up, just like with the iPad. Lucky for me that’s easier than for the Norwegians.