Since Palm released the Mojo SDK, I’ve been spending some time tinkering with it and developing some basic applications.  I’m hoping to start work on a bigger webOS project soon, though I’m not entirely sure what that will be (I do have some ideas). I’ve also been playing around with several of the apps in Precentral’s homebrew section. In particular, I really love the Prepod app, which is a podcast streamer/downloader that lets me listen to my podcasts over the air, specifically in my car.  It needs just a *little* more polish, but then it’s easily worth a few dollars on the official app store (whenever Palm decides to open that up).

Lately, I’ve been drooling over the new 13″ unibody Macbook Pro, but there are a couple of things keeping me from pulling the trigger on one, not the least of which is my current lack of money.  However, the upcoming release of Snow Leopard and (supposedly) Core i7 mobile are keeping me from buying one just yet.

I’ve been spending my Thursdays for the last couple of months at Flanagan’s, a pub over on Baxter Ave. that has a weekly Pint Night, where two special beers are rolled out, including glasses from the brewery that you get to take home with you (and are already taking over all my available cabinet space).  So far, all the beers I’ve tried there have been fairly interesting, and it’s been a great way to discover new beers.  At first, it was just 3 or 4 of us going every week, but it’s slowly been growing and now we actually have a pretty good crowd, mostly members from Speed’s ACM.

That’s pretty much all I’ve been up to lately, besides burning through my Netflix queue and poking around online, maybe I’ll write something again when I have something more interesting to report.

I’ve really only messed with two apps so far, Gimp and Evernote.  Gimp is, of course, preinstalled in Ubuntu and allows pen input just fine, although it doesn’t automatically map the eraser to the Erase tool.

Evernote doesn’t have a native Linux version, but it runs quite well in Wine.  The only issue I’ve come across so far is that I cannot drag and drop files from Nautilus into a notebook.  My plan is to use this to handwrite notes for school, and I’ve already been typing my notes into Evernote for the last few days.  Evernote is nice because it automatically keeps your notes synced between multiple installations (for me, that’s Evernote/Wine Evernote/VistaVM and Evernote/W7) and also has a web interface for when I’m not at one of my computers.  This syncing allows me to drag files to Evernote either by opening a VM or remoting to my desktop and then they will automatically be synced back to the copy of Evernote I’m running in Wine.

For the most part, I’m working on the same things as last summer, and I’ve seen some of my own code while looking through the latest source checkout, which was cool.

As usual, there’s some gadget I’m drooling over, and for the time being, it’s the Palm Pre.  The Pre is the first phone I’ve been interested in that will actually be debuting on the Sprint network (the iPhone and G1 were on AT&T and T-Mobile).  Unfortunately, there’s no release date known other than H1 09.

In addition to running web and mail servers, I could also virtualize the backends to some other applications, namely Deluge and MythTV, so that the computers they ran on didn’t need to be on 24/7.  MythTV is a little tricky due to the lack of support for PCI passthrough in VMware, but I could of course use USB tuners.  I could also use a virtual machine as my primary desktop, and use a small, low powered, thin client to access it over VNC or SSH.

I recently looked into the hardware I’d want for such a server and came up with the following:

• Intel Core 2 Quad Q6600 2.4GHz CPU
• Intel BOXDG31PR Micro ATX Motherboard
• Kingston 4GB (2x2GB) DDR2-800 Memory
• Seagate 1TB SATA2 Hard Drive
• APEX DM-387 Slim Micro ATX Case

The build would be another slim micro ATX build, similar to Cervantes and have a quad-core CPU, 4GB of ram, and a terabyte of storage.  In total, it came to a little under $600 for the entire build (I love how cheap hardware is getting) but I think I’ve decided to hold out for Nehalem before I build it.  With native quad cores and hyper threading, Nehalem should work well for this kind of project.

The interns whose posters receive the most votes get a free trip to VMWorld, this September in Las Vegas.

CS:S ran pretty well at the default settings, and got an average of 35fps for the stress test.

Lost Coast, however, managed to completely crash the virtual video card, I’m giving it another go now.  I’m guessing that HDR was too much for the virtual machine to handle.

Well, LC is clearly unhappy, it’s refusing to start now…

And now CS:S won’t start either, great.  Time to do some debugging…

Creating the virtual hardware component is pretty straightforward, and follows the same general process as my previous guide.  For your convenience, I’ve uploaded my component that I created running XP on ESX.

vmware4.sld

However, just the component isn’t enough for ESX.  ESX 3.x doesn’t support virtual IDE hard drives.  Likewise, Windows XPe doesn’t support SCSI drives.  So, you’ll have to install the VMware SCSI driver.  During a normal XP installation, you can do this by pressing F6 during installation and loading the drivers from a floppy, but because you build XPe rather than installing it, you have to componetize the driver.  Again, I’ve already done this for you.

vmscsi.zip

If this doesn’t work for you, you can download the floppy image containing the driver from VMware.com, extract it, and then import the vmscsi.inf file into the XPe Component Designer.

Once you have both the vmware4 and vmscsi components added to your XPe profile, run dependency checks to pull in the required components and build the image like you did in the last guide.  After that, move the Virtual Machine onto your ESX box (assuming you didn’t create it there) and fire it up.

XP Embedded Studio isn’t actually a horrible application at it’s core.  Now, the user interface and documentation are God-awful, which is why I’m writing this post.  As you saw in my last two entries, I’ve been working with XPe for the last few days, and there has been plenty of frustration to go along with it.  What should have been a fifteen minute task wound up taking several days.  However, one week and a few dozen BSODs later, I present this how to:

The idea here is to use VMware to not only run, but create your XPe images, though you could easily do the development in your host environment with only minor changes to these directions.

Step 1: Prepare your development environment

First, let’s get the virtual machines set up.  You’ll need at least two, one for doing the development, and another to test the image.  The first image is just a regular Windows XP virtual machine.  I already had a Windows XP Pro virtual machine that I use on a daily basis, so I just used that.  You’ll need to set up the Windows XP Embedded development environment.  If you don’t already have it, you can download a 30 day evaluation copy from Microsoft.

Now, go ahead and create the second virtual machine, which you will use to run your XPe image.  Create a new VM in VMware and choose Windows XP Professional as the Guest OS. (Note: If you are using WS 6.5 or later, you don’t want to use easy install.  Choose to install the guest OS later.)  I selected some pretty basic specs for the VM:

• Memory: 256MB
• Processors: 1
• Hard Disk (IDE 0:0): 512MB

It doesn’t take much to run XPe, and those listed specs should be fine unless you’ll be putting a lot of data on the image.

Now that your VM is created, you need to add it’s hard drive to your original XP VM.  Make sure your XP VM is shut down, then open the Virtual Machine Settings dialog and click Add.  Choose to add a new Hard Disk, and when prompted, choose to add an existing virtual disk.  Navigate to your XP Embedded Virtual Machine and choose the vmdk associated with it.  After it has been added, open the Advanced properties for that disk and make it Independent and Persistent.

Step 2: Load a profile of your virtual hardware

This was the part that gave me grief.  Fortunately for you, you can benefit from my experience.  You need a profile of the hardware you will be running XPe on so that XPe knows which drivers to load.

Step 2a: The easy way

I have prepared a component for Windows XPe that will automatically load in a set of generic drivers that are capable of running on VMware virtual hardware version 6, which is the version used in Workstation 6.0.  If you are using Workstation 6.5, it uses version 7 of VMware’s virtual hardware.  Chances are you’ll still be able to use my component, and you should definately try it.

Download my XPe VMware Component

You’ll need to install the .sld file using the Component Database Manager.

If you ultimately wind up with an unbootable XPe image, you’ll want to come back and perform the steps in 2b, but for now, proceed to step 3.

Step 2b: The not-so-easy way

So, you need to create your own profile for your virtual machine.  First, you’ll want to create a third VM.  Again, it should be Windows XP Professional, and the hardware should be as similar to your XPe VM as possible, though you’ll need more hard drive space.  I wound up needing about 1.5GB of disk space for this step, but it wouldn’t be a bad idea to allocate more just in case.

Install Windows XP Professional (Professional is important here) on the new virtual machine.  It’s very important that you DO NOT install VMware tools on this VM (This gave me trouble during my experimenting).  This means that if you’re using VMware 6.5 or later, you need to install the OS manually and not use Easy Install. (Note: You don’t need to bother activating this VM if you don’t want to, you’ll only need it for a minute.)

Once you have a vanilla installation of XP Pro up and running, you’ll need some of the XPe tools.  Go back to that link I posted near the beginning of this post and download and run the XPe downloader again.  This time, you only need the Windows XP Embedded SP1 Tools package, which is around 7 MB.

Let that download and start(You may get a warning, ignore it), then choose to Browse the CD.  Open the fodler named XPE and look for a file named TAP.EXE (Or probably just TAP, as XP will hide the file extensions by default).  Double-click it and it will run, leaving behind a file named devices.pmq in that same directory.  Now you need to get that pmq file back to your original XP VM where you’re doing the XPe development.  I just opened Internet Explorer and Gmailed it to myself.  Once you have the pmq file, you don’t need this extra VM anymore and you can delete it.

Back in your original VM, grab your devices.pmq file and put it somewhere on the hard drive.  Now open Microsoft Component Designer and choose File > Import and open devices.pmq.  Go through the import process, then if you want you can give your component a name and other info.  Finally, save the component as a *.sld file and then import that sld using the Component Database Manager.  Now your component should be available when building XPe images.

Step 3: Create the Image

Open the XPe Target Designer and start a new project.  On the left hand side of the window, you should see a list of components, including the VMware hardware profile that you either downloaded from me or created yourself.  Double click it to add it to the project.

Now, press F5 to perform a dependency check.  It will run through and automatically add most of the needed components, but it will need your input on a few of them.  If you are using my profile, you should wind up with 6 errors, which will be displayed at the bottom of the screen.  For each item, double click the icon next to it to see the list of available components that will satisfy that dependency.  Choose the components that best suit your need, but for a standard set up, I recommend using the following whenever they come up as options:

• NT Loader
• FAT
• Windows Logon

After all of the dependencies are taken care of, it’s time to… run another dependency check!  For some reason, Microsoft doesn’t do recursive dependency checking here.  Press F5 again, and wait for it to finish.  At this point there should be one more error, the shell.  Handle this one just like the last set.  For a standard set up, I’d recommend just using the Explorer Shell.

Continue to run dependency checks until it comes back with no errors.

You’re almost there.  At this point, it’s a good idea to save your work.

Step 4: Prepare the virtual disk

Open up XP’s built in disk manager and find your XPe VM’s hard drive that you attached to your original XP VM.  Make sure it is initialized, then partition and format the entire disk as FAT32.

You’ll also need to make sure that the partition is marked as bootable.  You can do this however you like, I booted the VM to an Ubuntu Live CD and used the built in partition editor.

Step 5: Build XP Embedded

Back in the Target Designer, you need to build the XPe image.  To do this, press F7.  For build type, choose Release.  For Destination, enter the path where your XPe VM’s is mounted, for example, D: or E:.  Note that it will be mounted at C: in XPe.  Finally, press Build.  If all goes well, you will get no errors, and maybe a warning or two.

Step 6: Run it

Only one VM can access a particular vmdk at a time, so you’ll want to suspend your XP VM now.  Once that’s done, switch over to your XPe VM and power it on.  If you’ve done everything correctly, you should be a Windows XP Embedded loading screen, then the First Boot Assistant, after which it will boot into your embedded environment.

Congratulations! You now have a minimal XPe system that is capable of running on virtual hardware.  In order to add additional components to your XPe image, shut down the VM and resume your original XP VM.  Modify the image as you see fit, then reformat the target disk and build again.  There shouldn’t be a need to mark the partition as bootable again.

If your XPe image crashed, you’ll need to do some debugging.  If you were using my pre-made profile, go back to Step 2b and create a profile yourself.  This should be guaranteed to work, but if not, I’d start by checking for information on MSDN.  If your image is crashing with a BSOD, try Googling the error number and seeing what you get.