art's abode

Archive for the ‘works-for-me(tm)’ Category

Upgrading Live Mesh to Live Sync on Vista – workarounds.

without comments

We saw the following error messages when trying to get Live Sync working under a Vista laptop.

If you are unable to install Live Sync because it says Live Mesh is installed for other users on the computer.


Login to as many of the other accounts as you can, and uninstall Live Mesh.

If there are accounts you can’t access, or it’s been removed and still not being recognized, you may have to manually run the installer to repair or uninstall Mesh. Note that this exercise was fruitless under our Vista install due to being unable to run with elevated permissions.

You may also have to remove registry keys manually. See this article and work through the steps:

Type Regedit and hit Enter (if you are on Vista you will need to agree to a UAC prompt)
In the Registry Editor remove the following Registry entries:



NOTE:  <YOURSID> value will be unique to you.

You should do this for each SID you see in the UserData hive. Take care as this may botch things up for the other accounts. In our case it wasn’t an issue as they were non-active accounts.

Live Sync has an error on login: “Sorry, Windows Live Sync isn’t accepting new users right now. please check back later.”


  • Go to Start > Control Panel > Programs.
  • Find Windows Live Sync if it’s in the list of installed programs and uninstall it.
  • Uninstall/repair Windows Live Essentials, and remove Live Mesh if it’s showing as installed.
  • Download the Windows Live Essentials 2011 installer, and install Live Mesh/Live Sync.

After these steps, Live Sync was able to startup and login to LIVE successfully. This also added the device to the Sync Devices which you can confirm via the LIVE website (LIVE icon > Devices).

Hope this helps!

Written by art

November 13th, 2010 at 4:21 pm

OpenSolaris, Netbeans and rubygems.

without comments

If you are stuck trying to get rubygems installed in your OpenSolaris environment, the following may help. I ran into these issues while installing bcrypt-ruby and sqlite3-ruby gems.

  • First off, get the SUNWruby18 package, not the netbeans or jruby one. You can setup netbeans to use the  SUNWruby18 binary rather than jruby.
  • Install GCC, for example package name gcc-432.
  • Using “pfexec ln -s” for example, make symbolic links to GCC from /usr/bin/gcc-4.3.2 to /usr/bin/gcc and /usr/sfw/bin/gcc. Take note of which gcc version you have and construct your ln -s command appropriately.
  • Update your rubygems installation: “pfexec gem update –system”.
  • If you are compiling gems, you will need rake: “pfexec gem install rake”.
  • If you need sqlite3-ruby gem, you will need to download and compile a newer version of sqlite3 from the website as the OpenSolaris package is currently too old to build the gem.

That should be enough to get you going. Try installing gems now either from shell or netbeans with superuser privileges. If you run into errors, take close note of the error messages while compiling the gem, and the output logs. You can generally work out what is required from the fairly verbose errors.

You may see this type of error:

art@sol:~$ irb
irb(main):001:0> require “bcrypt”
LoadError: no such file to load — bcrypt
from (irb):1:in `require’
from (irb):1

One way to resolve this is to run ruby or irb with the -rubygems option:

art@sol:~$ irb -rubygems
irb(main):001:0> require “bcrypt”
=> true

Hope this helps!

Written by art

November 11th, 2010 at 7:45 pm

Turning a Physical Machine into a Virtual Machine

without comments

This morning my work laptop died a horrible and painful death. Suffice it to say that burning smell was not the smell of bacon on the pan but rather my poor work laptop melting internally.

Luckily, I was able to pull out the hard drive and plug it in elsewhere to ensure that I hadn’t lost any hard drive data. What little fortune I had today was in discovering that the hard disk itself was fine.

This left me with a dead computer, a good hard drive, and no way to run the drive.

CaptureEnter P2V. Using WinImage or any other tool that can convert a drive into a .VHD file, I managed to create an image of my notebook’s drive into a standard VHD.

At this point you may have read about HAL issues when using the VHD, blue screens and other horrific stuff. I was able to ignore all of these issues simply by creating a virtual machine in VirtualBox (not VMWare, Virtual Server or Hyper-V). VirtualBox now supports VHDs, so it’s simply a matter of creating a new VM, and using your VHD as an existing drive.

I was able to boot up without problems, and Windows 7 in the VM automatically downloaded all the new drivers I needed (such as the VM audio card, network card, etc.). Installing virtual additions also works. It doesn’t get any easier than that!

Written by art

November 11th, 2009 at 7:45 pm

Windows and Linux Seamlessly

without comments

Look ma, two OSes, one Desktop (and I ain’t talking Cygwin cheese either…):


Yes yes… I know you’re scared… let the VM frenzy begin!

Written by art

September 30th, 2009 at 7:35 am

if (dd-wrt + xbox 360 == fail) then tomato;

with one comment


Having had problems with my ISP’s modem/router/firewall/wireless device, I wanted to bridge to a separate device to handle the routing, firewall and wireless.

I have been using a Linksys WRT54G version 1 for this task. The firmware had to be flashed with DD-WRT, which is a pretty good firmware all in all, but seemed to be stretching the limits of the version 1 WRT54G.

The vintage DD-WRT build, which is the appropriate flavour for the WRT54Gv1 is a stripped-down version of DD-WRT which doesn’t contain some of the newer features. Although it was fairly stable, it got slow and unresponsive at times over wireless, and had some trouble maintaining long-term RDP sessions over wireless, dropping the connections maybe twice an hour for a minute or so each time. Although QoS may have been an issue, my clever rebuttal is that “it doesn’t work for me out of the box”: I’m lazy as fuck, what do you expect?

All in all, DD-WRT worked better than the Speedtouch 780 as a router, and better than the stock Linksys or OpenWRT firmwares. My main problem with DD-WRT was that for some black magic voodoo reason, the XBox 360 was unable to join the wireless network. It could detect it, discover encryption method, but was unable to connect to the network no matter how hard I tried, no matter how hard I cried into my pillow.

After acquiring some expert/professional advice (i.e., googling the interwebs), I installed tomato the other day, and lo and behold—the XBox was able to connect without problems. Tomato seems more responsive than the DD-WRT thus far, which is another bonus.

I’m not sure about the newer WRT54G models, but if you have a version 1, you may want to consider using tomato rather than the stock Linksys, DD-WRT or OpenWRT firmwares.


Written by art

April 21st, 2009 at 12:27 pm