<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Glen Smith (General Related category)</title>
  <link rel="alternate" href="http://blogs.bytecode.com.au:80/categories/General" />
  <subtitle>Glen Smith (General Related category)</subtitle>
  <entry>
    <title>Bootcamp Assistant: How to overcome the "files cannot be moved" issue</title>
    <link rel="alternate" href="http://blogs.bytecode.com.au:80/glen/2009/10/28/bootcamp-assistant--how-to-overcome-the--files-cannot-be-moved--issue.html" />
    <author>
      <name />
    </author>
    <updated>2009-10-28T08:53:00Z</updated>
    <published>2009-10-28T08:53:00Z</published>
    <summary type="html">&lt;p&gt;&#xD;
You're busy trying to use the Bootcamp Assistant to install a bootcamp partition on your shiny Macbook, when suddenly you're greeted with the dreaded fragmentation dialog of death:&#xD;
&lt;/p&gt;&#xD;
&lt;p&gt;&#xD;
&lt;img src="images/2009/bootcamp_dialog.png" alt="The disk cannot be partitioned because some files cannot be moved"/&gt;&#xD;
&lt;/p&gt;&#xD;
&lt;p&gt;&#xD;
So what does "The disk cannot be partitioned because some files cannot be moved" actually mean? I mean, I've got 25Gb free and I only want a 10Gb windows partition! The answer lies in fragmentation. OSX seems to want a contigious block of clean disk to write to, and fragments of your files are scattered across it. &#xD;
&lt;/p&gt;&#xD;
&lt;p&gt;&#xD;
I know what you're thinking. "But it's a Mac. I've got this fancy file system that isn't prone to fragmentation". Yeah, yeah. Well, dude, the crushing news is that you can fix the problem by defragmenting your hard disk then trying again, so I guess OSX isn't as committed to defragmentation as you might suspect. &#xD;
&lt;/p&gt;&#xD;
&lt;p&gt;&#xD;
I'm sure there are many ways to defrag an OSX hard disk. I chose to fork out 20 Euro and make the problem go away using &lt;a href="http://www.coriolis-systems.com/iDefrag.php"&gt;iDefrag&lt;/a&gt;. There may well be open source/free alternative out there (feel free to comment if you know of any -- useful for other googlers who come on by).  iDefrag does its best work when it's not defragging the boot disk, so you'll want to generate a bootable DVD to run it from. Fortunately it ships with the tool to generate that bootable DV for you. &#xD;
&lt;/p&gt;&#xD;
&lt;p&gt;&#xD;
iDefrag ships will a free product called "Coriolis CDMaker". Stick your Snow Leopard disk in the drive, run the CDMaker app, and it will get busy generating a bootable DVD for you with iDefrag as the autorun. Stick your bootable DVD in the drive, restart OSX, and hold down the "C" key as the machine boots -- and it will boot up your DVD and run iDefrag.&#xD;
&lt;/p&gt;&#xD;
&lt;p&gt;&#xD;
Defragging takes some time - mine took about 3 hours to run - but that's a lot less hassle than reformatting and restoring my entire drive. After the defrag I could happily run the Bootcamp Assistant without any "some files cannot be moved" drama.&#xD;
&lt;/p&gt;</summary>
    <dc:date>2009-10-28T08:53:00Z</dc:date>
  </entry>
  <entry>
    <title>Recoving your iPhoto collection from an Emptied Trash... (there is hope!)</title>
    <link rel="alternate" href="http://blogs.bytecode.com.au:80/glen/2006/08/31/recoving-your-iphoto-collection-from-an-emptied-trash-----there-is-hope--.html" />
    <author>
      <name />
    </author>
    <updated>2006-08-30T21:08:40Z</updated>
    <published>2006-08-30T21:08:40Z</published>
    <summary type="html">&lt;p&gt;So what *do* you do when your small child erases your iPhoto collection? I guess you undelete from the trash... But what happens if you didn't know your photo collection was in the trash and you emptied it? You go to your most recent backup. But what happens when your most recent backup is&amp;nbsp;6 weeks old (you know, just before your newborn arrived?). You panic.&lt;/p&gt;
&lt;p&gt;I've had a Mac Mini for over a year, and never had a drama with it. So when all my photos disappeared I felt sick in my stomach. I am so not battletested in this space - I've never had to be. &lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;Anyways after some frantic hunting on the web I bought a copy of &lt;a href="http://www.subrosasoft.com/OSXSoftware/index.php?main_page=product_info&amp;amp;products_id=1"&gt;FileSalvage&lt;/a&gt; for OSX. It's $99USD which is quite a sum... but really a very smart pricing model since the only time you need this tool is when you *really* need this tool. RIght Now. Before your OS starts using all of that &amp;quot;empty&amp;quot; space you just created.&lt;/p&gt;
&lt;p&gt;Anyways, I set it off and a few hours later I had 23000 undeleted images called File001. I only needed ones from the last six weeks, so I ran the sensational &lt;a href="http://www.pixture.com/software/macosx.php"&gt;PhotoToolCM&lt;/a&gt; to rename and redate the files based on the EXIF data that the camera stored inside the image and I was in business. &lt;/p&gt;
&lt;p&gt;This story has a happy ending (not many of these sorts of things do). The newborn shots are back. All of them. Phew!&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;Now I plan to backup weekly...&lt;/p&gt;</summary>
    <dc:date>2006-08-30T21:08:40Z</dc:date>
  </entry>
  <entry>
    <title>Yahoo Desktop is worth a look...</title>
    <link rel="alternate" href="http://blogs.bytecode.com.au:80/glen/2006/05/14/yahoo-desktop-is-worth-a-look---.html" />
    <author>
      <name />
    </author>
    <updated>2006-05-14T05:31:57Z</updated>
    <published>2006-05-14T05:31:57Z</published>
    <summary type="html">&lt;p&gt;
I've played around with Google desktop (and others) in the past and never had much success. They all slurped too much CPU, didn't handle my OpenOffice files or PDFs, and came with interfaces that were either too simple, or far too complex.
&lt;/p&gt;
&lt;p&gt;
My local Aussie PC mag, &lt;a href="http://www.pcauthority.com.au/"&gt;PC Authority&lt;/a&gt; did a feature on desktop search technologies this month and gave the editor's choice to &lt;a href="http://desktop.yahoo.com/"&gt;Yahoo! Desktop&lt;/a&gt;. I didn't have much luck with Google desktop, but based on their review the Yahoo offering looked like it was worth for a spin. And it was...
&lt;/p&gt;
&lt;p&gt;
I've gotta say that I'm pretty impressed. Handles all my OpenOffice docs, and displays them inside the search window just fine (note: you do have to download the filters pack which handles an extra 200 file types - don't know why they didn't just roll it into the base install). Ditto for the PDFs. (Screenshot below)
&lt;/p&gt;
&lt;p&gt;
&lt;img src="images/2006/YahooDesktop.gif"/&gt;
&lt;/p&gt;
&lt;p&gt;
Haven't been able to get it to index my IMAP store yet, but other that than it works a treat. Low CPU impact. Nice UI. Very stable. And I'm actually finding it very handy!
&lt;/p&gt;
&lt;p&gt;
Big props to the Yahoo! Dudes. Very class offering.
&lt;/p&gt;</summary>
    <dc:date>2006-05-14T05:31:57Z</dc:date>
  </entry>
  <entry>
    <title>Iterations considered harmful?</title>
    <link rel="alternate" href="http://blogs.bytecode.com.au:80/glen/2006/03/28/iterations-considered-harmful-.html" />
    <author>
      <name />
    </author>
    <updated>2006-03-28T01:59:45Z</updated>
    <published>2006-03-28T01:59:45Z</published>
    <summary type="html">&lt;p&gt;
It would be pretty insane to argue that regularly delivering running, tested, value-add code is hazardous to any project. But when it comes to iterations, if you're not careful the mojo can get very funky pretty quickly. I've just finished reading a &lt;a href="http://alistair.cockburn.us/crystal/articles/aih/areiterationshazardous.htm"&gt;fantastic article&lt;/a&gt; by Alistair Cockburn on the misuse of iterations in agile projects... and I've just realised that I'm living the nightmare myself! 
&lt;/p&gt;
&lt;p&gt;
Alistair's argument comes down to the fact that shipping iterations is not necessarily the same as delivering real value to the client. And it's not the same as getting you closer to your end-game. A fave quote from the article:
&lt;/p&gt;
&lt;p&gt;
&lt;i&gt;
"Danger grows when the results of the iteration are not directly linked to delivering the product to the end user. Without that linkage, iteration results hang in the air just as badly as the old, pre-agile forms of wandering in the wilderness."
&lt;/i&gt;
&lt;/p&gt;
&lt;p&gt;
Reading this I started to rethink our iterations in line with the big picture of getting our product out the door. I've spent a bunch of time over the last couple of months "tidying" up stuff, refactoring and adding small features that don't (1) add immediate value to the client; and (2) Move us closer to getting 1.0 out the door. Yes I am hitting iterations, but no it's not moving us closer to 1.0. That thinking is changing today. The problem is not the iterations - the problem is that I'm not planning them properly!
&lt;/p&gt;
&lt;p&gt;
In line with Alistair's recommendations, I'm setting aside some time this week to make sure that our monthly iterations are better aligned to our end game. In essence, it's all about &lt;b&gt;delivering&lt;/b&gt;. Not about delivering iterations, but about delivering the features that are adding value and getting us closer to a revenue stream. 
&lt;/p&gt;
&lt;p&gt;
If you haven't read Alistair Cockburn's &lt;a href="http://www.amazon.com/exec/obidos/tg/detail/-/0201699478/103-9563560-4159862?v=glance"&gt;Crystal Clear&lt;/a&gt; - do yourself a favour. I have found this book a really challenging read. This really brought together a whole bunch of agile thinking into my world - and it's the most practical and battle-tested book on small team development methodology I've read. 
&lt;/p&gt;
&lt;p&gt;
Awesome stuff...
&lt;/p&gt;</summary>
    <dc:date>2006-03-28T01:59:45Z</dc:date>
  </entry>
  <entry>
    <title>Two Very Cool Developer Utils for Windows</title>
    <link rel="alternate" href="http://blogs.bytecode.com.au:80/glen/2006/01/21/two-very-cool-developer-utils-for-windows.html" />
    <author>
      <name />
    </author>
    <updated>2006-01-21T09:16:57Z</updated>
    <published>2006-01-21T09:16:57Z</published>
    <summary type="html">&lt;p&gt;
While some of my development is done on Mac, and some on Linux, most of my time is spent on Windows. Not really fussed about operating systems these days, so happy to work on whatever. Anyways, I work with this guy &lt;a href="http://www.dicamillo.net/blog/"&gt;Shayne&lt;/a&gt; who knows more about Windows utilities than anyone, and he keeps showing me cool stuff. 
&lt;/p&gt;
&lt;p&gt;
The first one is a clipboard extender called &lt;a href="http://www.intelexual.com/products/YC3/"&gt;Yankee Clipper&lt;/a&gt;. This beast keeps a running history of your clipboard over time, and gives you a cute dropdown menu to pick from when you use Ctrl-Alt-V. Shayne has a more complete &lt;a href="http://dicamillo.net/blog/?p=5"&gt;review&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
The second cool utility that I just can't live without any more is &lt;a href="http://www.protonfx.com/dirkey/"&gt;Dirkey&lt;/a&gt;. This guy allows you to bring up a picklist of Windows Explorer shortcuts when you are in File Dialogs (or Explorer itself) simply by right clicking on the Close Window button. This turns out to be phenominally useful when navigating the filesystem. 
&lt;/p&gt;
&lt;p&gt;
Both utilities are freeware.... And too cool for school.</summary>
    <dc:date>2006-01-21T09:16:57Z</dc:date>
  </entry>
</feed>

