So I am still waiting for the install of Windbg. The timing is kind of terrible because everyone’s all a flutter with Firefox 3 and I’m twiddling my thumbs a bit. As I can’t test the source server from the user end yet, I must turn my attention to documentation and also to planning my final “knock your socks off” demo. Instead of 2 demos which would be ridiculous in the short amount of time that is left, I will do one super demo where lots of people (you dear readers?) will come and test out the source indexed builds. This should happen in the week before exams, more info to come soon. If anyone is looking for contrib points (is that like karma?) please come to the demo.

Things have calmed down significantly since the big check-in a couple of weeks ago. Time flies when you’re waiting for someone to install on the ref platform for you. This is the part of Open Source development that I’m not so good at: patience.

What have I done? Well, I filed a bug asking for the install of Windbg on the ref platform/tinderboxen so that we can start pumping out source indexed nightly builds. Once those are coming down the pipe I can download and test them to be sure that everything is working as expected. Based on the few tests from last semester, I anticipate some tweaking will be needed to where the files are stored and possibly to the cvs set up.

In the meantime it’s time to think about what the next few releases will look like. Oh, and I have a demo on Thursday (/me prays for the install to happen before then so there’s something worth demo-ing).

Here’s what I’m thinking:

0.8 – all tests and tweaks for the user side of source server builds
0.9 – docs and tutorial about the source server and how to use it
1.0 – ? need to think more about that.

In a perfect world 1.0 is a pdbstr replacement but that is starting to seem like something out of my league. I really don’t even know where one begins with hacking into a microsoft hex file to deposit information.

Perhaps there will be unforseen bugs or other features that can be added to make the 1.0 of this project sharp and professional.

Okay, it’s time to go pester the build guys some more for that install.

Here’s reason 1,000,001 why I love the internet:

The VMware Fusion Windows XP vm is pretty important to daily life for me and today it decided to hang. Halfway through a “Restoring Virtual Machine State”, the progress bar just stopped moving and I had to force quite Fusion. After many restarts, and other experimenting, I was starting to worry that I was in for a long Saturday of re-creating an XP vm instead of working on a job I’m doing.

Instead, a quick Google search for “restoring virtual machine state hangs fusion” turned up this little nugget of wisdom that I bet will come in handy again someday for me, and maybe for anyone else out there who also depends heavily on Fusion.

Go to ~/Documents/Virtual Machine right click on the .vmwarevm that is causing the issue, right click on it and “Show package contents” then delete the .vmss file.

This gets rid of the session state and when you restart the vm it will boot up as if it was not saved in mid session.

Lose the session, no biggie – lose the vm…well that would be much much worse, right?