Posted by Kasper Tidemann on Monday 8th of March 2010 07:23:28 AM
If you’re running both Mac OS X and Windows 7, you might have encountered the problem of your USB key(s) either working on the Mac OS X or the Windows 7, and not on both of them.
Following the below guide will fix the problem:
Step 1) Partition the USB key using Disk Utility on Mac OS X. Make a single partition using the format “free space” and the partition scheme “Master Boot Record” (under Options).
Step 2) Insert the USB key in the Windows 7 machine. This will result in Windows 7 telling you that the key needs to be formatted. Ignore this message for now, and access Control Panel -> System and Security -> Create and format hard disk partitions (under Administrative Tools). Now, the Disk Management window should show up.
Step 3) You should be able to see the USB key here, possibly with the text being lined through. Right-click on the USB key tab and choose “New Simple Volume…”. Then, choose to use the entire disk, choose FAT32, choose to use the standard allocation size and then, choose an appropriate name for the USB key.
Now, all you need to do is finish the actual formatting and the USB key should work both on Mac OS X and Windows 7.
Posted by Kasper Tidemann on Monday 8th of March 2010 03:17:36 AM
Having worked hard on Meeho!™, it is really great to get positive feedback from the users of the system. Here is an example from Facebook:

Screenshot from Facebook.
Thank you so much, Kenneth, and a big thank you to the many users we communicate with daily. Thank you for your support, your great ideas and input, and your love towards Meeho!™. It is greatly appreciated!
Posted by Kasper Tidemann on Saturday 6th of March 2010 10:59:44 PM
After having finished an update of your RubyGems installation, you might receive the following error:
uninitialized constant Gem::GemRunner (NameError)
If you get the above when trying to use gem, first of all, you need to find out which gem you’re using. Open up your shell and type in the following:
which gem
This will print out which gem you’re using and the location of it, typically being /usr/bin/gem or /usr/local/bin/gem.
Next, open up the actual gem file in your favourite text editor. If you’re using TextMate for Mac OS X, this can be accomplished directly from your shell by issuing the mate /usr/bin/gem command (you might need to change the path to gem to reflect your system setup).
Here, you’ll see a line reading require ‘rubygems’. Just below this line, add require ‘rubygems/gem_runner’, save the file and try to use gem again. It should work fine now. The change you need to do is shown below:

This showns the gem file brought up in TextMate. Line 10 is the fix.
Posted by Kasper Tidemann on Thursday 4th of March 2010 02:43:08 AM
If you’re up for a bit of fun, go check out the work of Tim de Koning: a JavaScript Commodore C64 emulator. It’s done in JavaScript and makes use of HTML5 elements for rendering graphics, plus it comes with a few ROMs. Good old C64, it really takes you back…

A screenshot of the JavaScript emulator.